Status Update
Comments
re...@advantagebenefitconsultants.com <re...@advantagebenefitconsultants.com> #2
Any suggestions on where such an interface might live? I don't think it makes sense for the interface to be in the drawerlayout artifact if you're specifically going to use the interface to *not* use DrawerLayout.
ar...@gmail.com <ar...@gmail.com> #3
androidx.customview would be a good candidate. This is used by all of the widget libraries.
fe...@gmail.com <fe...@gmail.com> #4
Project: platform/frameworks/support
Branch: androidx-master-dev
commit 3ed3fb003fa6c1244f923202859a616225b5b2fa
Author: Ian Lake <ilake@google.com>
Date: Fri Feb 14 11:17:46 2020
Create an interface for layouts that can be opened
Create a common interface that represents layouts
that have two states: open and closed. This allows
higher level libraries to rely on the interface,
rather than concrete implementations such as
DrawerLayout, making them more resilient to
changes in the current recommended implementation.
Fixes: 129979320
Test: ./gradlew checkApi
Change-Id: I0f2a1414977825aa053c6555261f2b7d4417bd19
M customview/customview/api/1.1.0-alpha02.txt
M customview/customview/api/current.txt
M customview/customview/api/public_plus_experimental_1.1.0-alpha02.txt
M customview/customview/api/public_plus_experimental_current.txt
M customview/customview/api/restricted_1.1.0-alpha02.txt
M customview/customview/api/restricted_current.txt
A customview/customview/src/main/java/androidx/customview/widget/Openable.java
M drawerlayout/drawerlayout/api/1.1.0-alpha03.txt
M drawerlayout/drawerlayout/api/current.txt
M drawerlayout/drawerlayout/api/public_plus_experimental_1.1.0-alpha03.txt
M drawerlayout/drawerlayout/api/public_plus_experimental_current.txt
M drawerlayout/drawerlayout/api/restricted_1.1.0-alpha03.txt
M drawerlayout/drawerlayout/api/restricted_current.txt
M drawerlayout/drawerlayout/build.gradle
M drawerlayout/drawerlayout/src/main/java/androidx/drawerlayout/widget/DrawerLayout.java
M jetifier/jetifier/migration.config
M slidingpanelayout/slidingpanelayout/api/1.1.0-alpha01.txt
M slidingpanelayout/slidingpanelayout/api/current.txt
M slidingpanelayout/slidingpanelayout/api/public_plus_experimental_1.1.0-alpha01.txt
M slidingpanelayout/slidingpanelayout/api/public_plus_experimental_current.txt
M slidingpanelayout/slidingpanelayout/api/restricted_1.1.0-alpha01.txt
M slidingpanelayout/slidingpanelayout/api/restricted_current.txt
M slidingpanelayout/slidingpanelayout/src/main/java/androidx/slidingpanelayout/widget/SlidingPaneLayout.java
https://android-review.googlesource.com/940787
Branch: androidx-master-dev
commit 3ed3fb003fa6c1244f923202859a616225b5b2fa
Author: Ian Lake <ilake@google.com>
Date: Fri Feb 14 11:17:46 2020
Create an interface for layouts that can be opened
Create a common interface that represents layouts
that have two states: open and closed. This allows
higher level libraries to rely on the interface,
rather than concrete implementations such as
DrawerLayout, making them more resilient to
changes in the current recommended implementation.
Fixes: 129979320
Test: ./gradlew checkApi
Change-Id: I0f2a1414977825aa053c6555261f2b7d4417bd19
M customview/customview/api/1.1.0-alpha02.txt
M customview/customview/api/current.txt
M customview/customview/api/public_plus_experimental_1.1.0-alpha02.txt
M customview/customview/api/public_plus_experimental_current.txt
M customview/customview/api/restricted_1.1.0-alpha02.txt
M customview/customview/api/restricted_current.txt
A customview/customview/src/main/java/androidx/customview/widget/Openable.java
M drawerlayout/drawerlayout/api/1.1.0-alpha03.txt
M drawerlayout/drawerlayout/api/current.txt
M drawerlayout/drawerlayout/api/public_plus_experimental_1.1.0-alpha03.txt
M drawerlayout/drawerlayout/api/public_plus_experimental_current.txt
M drawerlayout/drawerlayout/api/restricted_1.1.0-alpha03.txt
M drawerlayout/drawerlayout/api/restricted_current.txt
M drawerlayout/drawerlayout/build.gradle
M drawerlayout/drawerlayout/src/main/java/androidx/drawerlayout/widget/DrawerLayout.java
M jetifier/jetifier/migration.config
M slidingpanelayout/slidingpanelayout/api/1.1.0-alpha01.txt
M slidingpanelayout/slidingpanelayout/api/current.txt
M slidingpanelayout/slidingpanelayout/api/public_plus_experimental_1.1.0-alpha01.txt
M slidingpanelayout/slidingpanelayout/api/public_plus_experimental_current.txt
M slidingpanelayout/slidingpanelayout/api/restricted_1.1.0-alpha01.txt
M slidingpanelayout/slidingpanelayout/api/restricted_current.txt
M slidingpanelayout/slidingpanelayout/src/main/java/androidx/slidingpanelayout/widget/SlidingPaneLayout.java
si...@gmail.com <si...@gmail.com> #5
Give me a way to make applications that I bought working again!
Blocking this kind of permission by default is good. Making it definitely unavailable is just an idiot decision against users needs. Has a user, I am now hungry about Android behavior. It's like an iPhone, it works against the user!
Blocking this kind of permission by default is good. Making it definitely unavailable is just an idiot decision against users needs. Has a user, I am now hungry about Android behavior. It's like an iPhone, it works against the user!
ko...@gmail.com <ko...@gmail.com> #6
Most of the duplicates have so many comments on them that they are full, so I'm just going to comment here.
I bought a new phone yesterday that has Android 9 on it, and so my call recording software stopped working.
Tomorrow I'm going to see if I can return the phone.
There are literally thousands of comments giving you reasons why this is stupid, so I'm just going to say "me too"
I bought a new phone yesterday that has Android 9 on it, and so my call recording software stopped working.
Tomorrow I'm going to see if I can return the phone.
There are literally thousands of comments giving you reasons why this is stupid, so I'm just going to say "me too"
do...@gmail.com <do...@gmail.com> #7
I have spent my money on apps using functionality you just banned I need it back!
If there are some stupid ppl allowing all perms to all apps and that is you concern, provide us some "Pro" mode for advanced users.
I see the only option now is to root my phone and try to fix the problem myself. But this really pisses me of because I need not only to spend my money on android device but then make it work as it should and my Galaxy is far from being cheap.
If there are some stupid ppl allowing all perms to all apps and that is you concern, provide us some "Pro" mode for advanced users.
I see the only option now is to root my phone and try to fix the problem myself. But this really pisses me of because I need not only to spend my money on android device but then make it work as it should and my Galaxy is far from being cheap.
ni...@gmail.com <ni...@gmail.com> #8
This is crap!
I updated an app, and now it can't send the automated text command. Well, the app writes the text and opens the text app, but I have to press send myself. How do I install the old version app again? (TrueGuard SMS APP)
I have a similar app, sending text commands. I still working great. I'll never update the app!
I updated an app, and now it can't send the automated text command. Well, the app writes the text and opens the text app, but I have to press send myself. How do I install the old version app again? (TrueGuard SMS APP)
I have a similar app, sending text commands. I still working great. I'll never update the app!
br...@gmail.com <br...@gmail.com> #9
I have been an Android OS user since the first Droid smartphone came out, and have consistently refused to jump on the Apple/ iPhone train because Google's apps and user interface were infinitely more customizeable and democratic. Now the apps I have come to rely on are crippled by permission restrictions, even though I have already, knowingly granted them; such as my call recorder app that needs call log access to identify each recording file, and sms automation apps that keep me safe, and my loved informed. Meanwhile, I understand that Google itself shares my private information, without hesitation and to my detriment, by subverting my anonymity and tranquility, exclusively to make money for Google.
Further, even UI has become vile and unfriendly. My eyes are constantly blinded by brightness that, even at dimmest setting, is often blindingly bright, and then keeps resetting most every night. My device, and the options for its use, have truly become an evil, which increases with every update. Adding further insult, for this evil presence and the bait-and-switch duplicity, I must continue to pay??!!
Don't be evil, Google.
Further, even UI has become vile and unfriendly. My eyes are constantly blinded by brightness that, even at dimmest setting, is often blindingly bright, and then keeps resetting most every night. My device, and the options for its use, have truly become an evil, which increases with every update. Adding further insult, for this evil presence and the bait-and-switch duplicity, I must continue to pay??!!
Don't be evil, Google.
Description
While this might protect users who for some reason give permissions to apps that shouldn't request them, it also harms a lot of apps that use those permissions in ways that aren't mentioned on the websites, and can never fit into a table, because of so many possible cases.
For example, automated tools apps, like Tasker. Why should it be restricted now and have to be a Phone/SMS app ? It doesn't make sense.
Another example is CallerID apps. On the table, it's mentioned that such an app is only allowed to use "READ_CALL_LOG" permission, but this is really not enough. Such apps also monitor incoming and outgoing calls, to show who it is, so "PROCESS_OUTGOING_CALLS" is also required.
And I'm sure there are other cases too.
Please stop this hunt of apps usage of permissions. Android is supposed to be free of these things.
If you wish developers to have a good reason, just force them to explain the reason for each permission usage in the app description, and then decide if it's legitimate or not.
Each case and its own. Rules shouldn't exist so broadly .