WAI
Status Update
Comments
am...@google.com <am...@google.com>
am...@google.com <am...@google.com> #3
Thank you for reporting this issue. For us to be able to investigate this issue it would be helpful if you could provide the following additional information:
Android build
Which Android build are you using? (e.g. OPP1.170223.012)
Device used
Which device did you use to reproduce this issue?
Steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Provide Screen Record of the Issue for better understanding. Please show all necessary settings as well.
You can consider the apphttps://play.google.com/store/apps/details?id=org.neotech.app.tinycore&hl=en for issue demonstration
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Expected output
What do you expect to occur?
Current output
What do you see instead?
Android bug report
After reproducing the issue, press the volume up, volume down, and power buttons simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach this file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.
Android build
Which Android build are you using? (e.g. OPP1.170223.012)
Device used
Which device did you use to reproduce this issue?
Steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Provide Screen Record of the Issue for better understanding. Please show all necessary settings as well.
You can consider the app
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Expected output
What do you expect to occur?
Current output
What do you see instead?
Android bug report
After reproducing the issue, press the volume up, volume down, and power buttons simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach this file to this issue.
Alternate method:
After reproducing the issue, navigate to developer settings, ensure ‘USB debugging’ is enabled, then enable ‘Bug report shortcut’. To take bug report, hold the power button and select the ‘Take bug report’ option.
Screen capture of the issue
Press the volume down and power buttons simultaneously. The image will appear in your gallery. Attach the screenshot file to this issue.
lu...@gmail.com <lu...@gmail.com> #4
I am trying to reproduce it on Emulator with Android O Preview1 image, but blocked by another issue (https://code.google.com/p/android/issues/detail?id=260167 )
I'll bring more info when be able to run the app.
For now our complains based on official Preview1 docs
herehttps://developer.android.com/reference/android/view/WindowManager.LayoutParams.html#TYPE_APPLICATION_OVERLAY
and herehttps://developer.android.com/reference/android/view/WindowManager.LayoutParams.html#TYPE_SYSTEM_OVERLAY
I suppose it's better to make API change decision as early as possible before 'O' is released, so that is why i posted ticket even before i able to run the actual app.
I'll bring more info when be able to run the app.
For now our complains based on official Preview1 docs
here
and here
I suppose it's better to make API change decision as early as possible before 'O' is released, so that is why i posted ticket even before i able to run the actual app.
te...@gmail.com <te...@gmail.com> #5
componentid:190923 status:open
lu...@gmail.com <lu...@gmail.com> #6
Here is additional info:
Android build
Android O
OSR1.170321.002 3834619 test-keys
Device used
Android Emulator
sdk_gphone_x86-userdebug O
Steps to reproduce
Run Cool Tool app
Press 'Show Panel Button'
Try to move the panel with virtual joystick
See video in attach
Expected output
The overlay window should be placed on top of status bar
Current output
The app overlay window has been overlapped with status bar
Android build
Android O
OSR1.170321.002 3834619 test-keys
Device used
Android Emulator
sdk_gphone_x86-userdebug O
Steps to reproduce
Run Cool Tool app
Press 'Show Panel Button'
Try to move the panel with virtual joystick
See video in attach
Expected output
The overlay window should be placed on top of status bar
Current output
The app overlay window has been overlapped with status bar
am...@google.com <am...@google.com> #7
Hi,
I have tried to reproduce the issue with the info @ comment#6 , but facing few issues as below
1. If the app is installed on the device then the "Show Panel" and "close settings" buttons are not visible
2. On the emulator, the app is crashing immediately after launch
The app version used is 5.6.2
So could you please provide below information for further analysis
Android bugreport:
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Or any other info which helps to reproduce the issue
I have tried to reproduce the issue with the info @
1. If the app is installed on the device then the "Show Panel" and "close settings" buttons are not visible
2. On the emulator, the app is crashing immediately after launch
The app version used is 5.6.2
So could you please provide below information for further analysis
Android bugreport:
After reproducing the issue, press the volume up, volume down, and power button simultaneously. This will capture a bug report on your device in the “bug reports” directory. Attach the bug report file to this issue.
Or any other info which helps to reproduce the issue
lu...@gmail.com <lu...@gmail.com> #8
I guess you faced this problem:
https://issuetracker.google.com/issues/36581808
To workaround try to disable Google Play Services app in the applications settings.
Also you need more ancient app version since last version crashes with disabled Services.
See the attach
To workaround try to disable Google Play Services app in the applications settings.
Also you need more ancient app version since last version crashes with disabled Services.
See the attach
fd...@gmail.com <fd...@gmail.com> #9
I'm a bit worried this regression might get ignored due to the lack of a proper description. I find it quite confusing how the issue reports are spread over two issue trackers. I also don't understand why you request for additional information although this regression is listed in O's Behavioural Changes.
Apps targeting Android O are now forced to use a new type of window flag for overlays that is forced to display below system UI such as the system bars and IMEs.
While forcing screen overlays below system UI might seem a good idea for apps that just use screen overlays for chat heads (eg Facebook Messenger), other apps are useless if their windows are restricted to certain areas of the screen:
My own app DeskDock uses a screen overlay for displaying a mouse cursor, which obviously needs to be in front at all times. Apps like Twilight will also be rendered behind UI windows, meaning that eg the Keyboard will not be dimmed. Navigation bar customisation apps or Status bar overlays won't work either.
I actually think there's tons of apps that will become useless with this change, given screen overlays were a great option for third-party developers to improve and customize Android's user experience (a great advantage over iOS).
I am aware this only affects apps targeting Android O for now, but this means apps that make use of screen overlays as they used to be will never be able to target Android O and make use of the otherwise great new features. For me as a developer, it is incredibly frustrating to see OS changes make one of my apps nearly useless. I enthusiastically spent hundreds of hours developing it, trusting in the stability of the platform and its public API.
I would be totally happy if you added another permission for apps that display windows _above_ the system UI and users would have to explicitly enable it.
I just hope such kind of functionality will make its way back into the final release of O and future versions of Android!
Apps targeting Android O are now forced to use a new type of window flag for overlays that is forced to display below system UI such as the system bars and IMEs.
While forcing screen overlays below system UI might seem a good idea for apps that just use screen overlays for chat heads (eg Facebook Messenger), other apps are useless if their windows are restricted to certain areas of the screen:
My own app DeskDock uses a screen overlay for displaying a mouse cursor, which obviously needs to be in front at all times. Apps like Twilight will also be rendered behind UI windows, meaning that eg the Keyboard will not be dimmed. Navigation bar customisation apps or Status bar overlays won't work either.
I actually think there's tons of apps that will become useless with this change, given screen overlays were a great option for third-party developers to improve and customize Android's user experience (a great advantage over iOS).
I am aware this only affects apps targeting Android O for now, but this means apps that make use of screen overlays as they used to be will never be able to target Android O and make use of the otherwise great new features. For me as a developer, it is incredibly frustrating to see OS changes make one of my apps nearly useless. I enthusiastically spent hundreds of hours developing it, trusting in the stability of the platform and its public API.
I would be totally happy if you added another permission for apps that display windows _above_ the system UI and users would have to explicitly enable it.
I just hope such kind of functionality will make its way back into the final release of O and future versions of Android!
lu...@gmail.com <lu...@gmail.com> #10
> I am aware this only affects apps targeting Android O for now
Correction: My app targeted to api 22 and still overlapped by status bar on Android O. So it doesn't matter which target version to use.
Correction: My app targeted to api 22 and still overlapped by status bar on Android O. So it doesn't matter which target version to use.
fd...@gmail.com <fd...@gmail.com> #11
That's interesting and even more concerning! I have not yet been able to test my own app on O as I am seeing the same Signature check issue as linked above. I am sorry if my description does not fit your issue, I am not even sure what specific issue this report is about: Seems there is #1 The intended removal of system UI overlays for apps targeting O and #2 The issue that system UI overlays don't work on O even when targeting lower API versions.
I am hoping for clarification by the Original Issue Reporter and will create a separate issue if required.
I am hoping for clarification by the Original Issue Reporter and will create a separate issue if required.
jm...@gmail.com <jm...@gmail.com> #12
The developer preview removes TYPE_SYSTEM_OVERLAY from the platform. It doesn't matter which API you target. The compatibility behavior is to remap TYPE_SYSTEM_OVERLAY to TYPE_APPLICATION_OVERLAY, which doesn't have the same behavior.
am...@google.com <am...@google.com> #13
Thank you for reporting this issue. We have passed this to the development team and will update this issue with more information as it becomes available.
am...@google.com <am...@google.com> #14
We have followed up with the product and engineering team and got suggestion that developers can use SHOW_WHEN_LOCKED activities to show when the device is locked, but it is intentionally no longer possible to show over the lockscreen / over the notification shade
nw...@gmail.com <nw...@gmail.com> #15
As far as I can tell, this means that apps like Cornerfly and Twilight will no longer function correctly. Are there any plans for a new API to allow for these apps to continue functioning like they do?
fd...@gmail.com <fd...@gmail.com> #16
Can someone official please confirm that even apps not targeting O won't be able to display anything above the notification shade? After all, that's not how I understood the Behavioural Changes document. That would mean dozens of apps will stop working with Android O! I'm sure that's not in the interest of the majority of Android's users!
lu...@gmail.com <lu...@gmail.com> #17
LayoutParams.FLAG_SHOW_WHEN_LOCKED doesn't solve the issue. Window still being rendered beneath the status bar
> That would mean dozens of apps will stop working with Android O
That is actually why i posted this ticket. There is no way to draw on top of status bar. AT ALL!
> That would mean dozens of apps will stop working with Android O
That is actually why i posted this ticket. There is no way to draw on top of status bar. AT ALL!
st...@gmail.com <st...@gmail.com> #18
I need system overlay to use my accessibility applications.
lb...@gmail.com <lb...@gmail.com> #19
Google, this is an important feature of Android. Why replace it for something that can do less? Instead of giving more features, you remove previous ones?!
in...@gmail.com <in...@gmail.com> #20
This can't be true, give us an option, I will not upgrade to Android O otherwise, and I think many others won't either
lb...@gmail.com <lb...@gmail.com> #21
@20 Sadly it is. Google doesn't listen to users or developers about removed features.
It was this way for SD-card support (very poor implementation on their side), was for the annoying permissions model and forcing of encrypted storage, and now with new restrictions on global intents and system-UI.
Sadly, Google decides that instead of providing better alternatives, it just removes them. All for the sake of "security". Instead of being creative and support both developers and users, they choose the easy way of ditching the features.
No matter how many times I tried to convince them, they never chose to use an alternative path.
It was this way for SD-card support (very poor implementation on their side), was for the annoying permissions model and forcing of encrypted storage, and now with new restrictions on global intents and system-UI.
Sadly, Google decides that instead of providing better alternatives, it just removes them. All for the sake of "security". Instead of being creative and support both developers and users, they choose the easy way of ditching the features.
No matter how many times I tried to convince them, they never chose to use an alternative path.
lb...@gmail.com <lb...@gmail.com> #22
Google please reconsider this restriction and others. There are plenty of apps that will get affected by this:
Status (500,000 – 1,000,000 installs)
Material Status Bar (1,000,000 – 5,000,000 installs)
Cool Tool – System Stats (500,000 – 1,000,000 installs)
Telecine (50,000 – 100,000 installs)
Clean Status Bar (100,000 – 500,000 installs)
Tinycore (100,000 – 500,000 installs)
Twilight (5,000,000 – 10,000,000 installs)
HeadsUp (100,000 – 500,000 installs)
Resource Monitor Mini (50,000 – 100,000 installs)
Network Monitor Mini (1,000,000 – 5,000,000 installs)
ADV screen recorder (1,000,000 – 5,000,000 installs)
And so many other popular apps
Why do you do this to the developers and users? This permission was already very clear to users using a confirmation screen, that it can draw on top of everything, and should cover all security concerns...
Status (500,000 – 1,000,000 installs)
Material Status Bar (1,000,000 – 5,000,000 installs)
Cool Tool – System Stats (500,000 – 1,000,000 installs)
Telecine (50,000 – 100,000 installs)
Clean Status Bar (100,000 – 500,000 installs)
Tinycore (100,000 – 500,000 installs)
Twilight (5,000,000 – 10,000,000 installs)
HeadsUp (100,000 – 500,000 installs)
Resource Monitor Mini (50,000 – 100,000 installs)
Network Monitor Mini (1,000,000 – 5,000,000 installs)
ADV screen recorder (1,000,000 – 5,000,000 installs)
And so many other popular apps
Why do you do this to the developers and users? This permission was already very clear to users using a confirmation screen, that it can draw on top of everything, and should cover all security concerns...
ch...@aviate-solutions.de <ch...@aviate-solutions.de> #23
I agree with my predecessors that this behaviour is wrong and will cause a lot of anger and discontent for both developers and users, too.
it was the case for Android to be fully customizable and now even already existing apps won't be useful anymore because Google tries to lock Android inside Googles world. It may be ok for Google to change this for better control and more revenue opportunities, but is not very user and developer friendly. It will cause all the work developers has done and maybe their whole business to diminish or even to break up with this upcoming update.
it was the case for Android to be fully customizable and now even already existing apps won't be useful anymore because Google tries to lock Android inside Googles world. It may be ok for Google to change this for better control and more revenue opportunities, but is not very user and developer friendly. It will cause all the work developers has done and maybe their whole business to diminish or even to break up with this upcoming update.
lu...@gmail.com <lu...@gmail.com> #24
Still not sure what the reason to abandon this api? If it's all about security than i just don't get how this "improvement" can improve security? Battery performance improvements? Don't think so. User experience improvements? Well, i guess not. Could Google guys give us reasonable answer?
he...@gmail.com <he...@gmail.com> #25
Have to agree with what everyone has said above me, there should be some kind of alternate functionality to draw over the status bar.
lb...@gmail.com <lb...@gmail.com> #26
If anyone here post a new request for an alternative solution that Google might consider, please post here so that we could all star it.
an...@gmail.com <an...@gmail.com> #27
Completely agree with all of the comments above.
Google really need to start listening to developers, if it wasn't for them; Android would not exist in its current form.
What happened to the mantra "don't be evil", Google? This regression has the potential to destroy businesses that have spent thousands of hours developing and relying on this.
For once, just once Google, reassess your position on this.
Google really need to start listening to developers, if it wasn't for them; Android would not exist in its current form.
What happened to the mantra "don't be evil", Google? This regression has the potential to destroy businesses that have spent thousands of hours developing and relying on this.
For once, just once Google, reassess your position on this.
te...@googlemail.com <te...@googlemail.com> #28
As this issue effects what I consider an essential app for me, I will not be able to upgrade to O unless and alternative is found. As a developer and a user I find this very frustrating.
so...@gmail.com <so...@gmail.com> #29
I really hope that this doesn't break SwipePad's ability to open with a pull down gesture from the upper left and right corner. This is such an important feature to me.
so...@gmail.com <so...@gmail.com> #30
If the problem they think they are resolving with it is the one of some important system dialogs possibly getting overlayed, like the packet installer's "install" button, then why don't they just disable temporarily all overlays when a security relevant UI interaction has to be done, and leave everything else as-is. Give the developer a broadcast when the overlays become disabled, and another one when they can be re-enabled.
lb...@gmail.com <lb...@gmail.com> #31
@29 You can already try it on the emulator. Google released an Android O emulator that has Play Store in it.
so...@gmail.com <so...@gmail.com> #32
@31 For Android Studio 3.0 canary only...
lb...@gmail.com <lb...@gmail.com> #33
@32 It has nothing to do with Android Studio because you can use any version of the emulator while having any version of the IDE, but if you want, you can have 2 versions of Android Studio anyway.
The new canary version seems to work fine on my PC at home, so I switched to it, but the gradle version causes issues in signing (wrote about it here:https://issuetracker.google.com/issues/38473781 ) so I didn't use it.
The new canary version seems to work fine on my PC at home, so I switched to it, but the gradle version causes issues in signing (wrote about it here:
md...@gmail.com <md...@gmail.com> #34
Please don't fall into offtopic. This is not a chat room. This is issue tracker for Google folks.
[Deleted User] <[Deleted User]> #35
Really sad to see this marked as Won't Fix. I'm one of the users who enjoys Twilight and I hoped that the overlay drawing under the system UI was a temporary bug. Sad to see that it's intended by Google. Hopefully, there will be an alternative for developers.
wa...@gmail.com <wa...@gmail.com> #36
This would effect handcent and other sms pop up texting apps that show over other apps and the lockscreen? This is much more useful than the reply from notification as more options are available with a pop up.
oc...@gmail.com <oc...@gmail.com> #37
This pretty much cripples a couple applications that are part of my daily workflow. Please fix.
ac...@gmail.com <ac...@gmail.com> #38
This is a serious issue. I would have to move to a custom rom if main android loses this functionality or does not provide an alternative.
so...@gmail.com <so...@gmail.com> #39
For Christ's sake! This is beyond ridiculous!
I've upgraded to Android O, and have accepted the stupid fact that I can no longer use SwipePad's two upper hotspots.
But now that my Amazon App wants to upgrade by showing me the packet installer and the OS then giving me a "warning" "can't do that because other apps are layering on top", now I have to find those two apps in the OS settings and disable them manually, then install, then re-enable them manually, it shows me that NOTHING has changed for the better.
If there is ONE THING this new limitation could have fixed, then it would have been EXTACTLY THAT ONE.
I get it that you don't want apps to be able to layer on top of the Notification Bar in order for them not to be able to screenshot SMS-verification tokens and perform some super-sophisticated hacking, but while you're at it, WHY DON'T YOU JUST FIX THE EFFEN BASICS??!
Honestly, I'm starting to doubt that all this "Googlers are the best" and "the interviews are the hardest" and "we only accept the best" is really true, sometimes it feels like they have the worst interns working on the most important stuff, sorry to say that!
Now I will go FIND WHERE THAT SETTING IS in order to dissallow those two apps, SwipePad and Swapps, access to the UI, disable it, just tu upgrade one app... It could be so FDSJH easy to tag the installer and layer it on top of everything else... But no... We're gonna disallow overlays because... uh, we don't know, security? At least do it right!
I've upgraded to Android O, and have accepted the stupid fact that I can no longer use SwipePad's two upper hotspots.
But now that my Amazon App wants to upgrade by showing me the packet installer and the OS then giving me a "warning" "can't do that because other apps are layering on top", now I have to find those two apps in the OS settings and disable them manually, then install, then re-enable them manually, it shows me that NOTHING has changed for the better.
If there is ONE THING this new limitation could have fixed, then it would have been EXTACTLY THAT ONE.
I get it that you don't want apps to be able to layer on top of the Notification Bar in order for them not to be able to screenshot SMS-verification tokens and perform some super-sophisticated hacking, but while you're at it, WHY DON'T YOU JUST FIX THE EFFEN BASICS??!
Honestly, I'm starting to doubt that all this "Googlers are the best" and "the interviews are the hardest" and "we only accept the best" is really true, sometimes it feels like they have the worst interns working on the most important stuff, sorry to say that!
Now I will go FIND WHERE THAT SETTING IS in order to dissallow those two apps, SwipePad and Swapps, access to the UI, disable it, just tu upgrade one app... It could be so FDSJH easy to tag the installer and layer it on top of everything else... But no... We're gonna disallow overlays because... uh, we don't know, security? At least do it right!
so...@gmail.com <so...@gmail.com> #40
Also, why is the UI-access permission not shown in the "App-Permissions" category? What? Is it not a permission???
lb...@gmail.com <lb...@gmail.com> #41
@40 for some reason, Google decided to show there only "normal" runtime-permissions. I have requested to show all kinds of permissions, including all that require a user confirmation, here:
https://issuetracker.google.com/issues/38065269
And, about this permission in particular, I agree. This is sad news.
And, about this permission in particular, I agree. This is sad news.
so...@gmail.com <so...@gmail.com> #42
Where did the Amazon App download the APK to? I don't know... How do I find it? I've searched, can't find it! How to I tell the Amazon App to restart the process to upgrade again? No, there is no way to do that manually... So now what?? Leave Swapps and SwipePad deactivated until I get lucky? And what if it was another app which had UI-Access? Then I will restart the entire process again?
How are my parents supposed to deal with this issue if they encounter it? Get an iPhone?
How are my parents supposed to deal with this issue if they encounter it? Get an iPhone?
so...@gmail.com <so...@gmail.com> #43
@41 I've starred it. I found it under "special permissions" after backing out one level... Thanks.
lb...@gmail.com <lb...@gmail.com> #44
@42 I don't know. If you wish, you can try my app to manage APK files. It might help you find them (if it can't find, you can try making it look in more places, via the settings) :
https://play.google.com/store/apps/details?id=com.lb.app_manager
About the rest, I have no idea.
About the rest, I have no idea.
so...@gmail.com <so...@gmail.com> #45
There are 20 apps that have the permission to draw over other apps. It took me some time to find out which apps were responsible for me not being able to install/upgrade apps via the package installer. That's an order of magnitude! 20 to 2. If that isn't a problem, then what is?
Now I won't update the Amazon app because I DON'T KNOW HOW! So if it has security fixes, then this super-change to overlays has done NOTHING to make me more secure, on the contrary!
Now I won't update the Amazon app because I DON'T KNOW HOW! So if it has security fixes, then this super-change to overlays has done NOTHING to make me more secure, on the contrary!
to...@gmail.com <to...@gmail.com> #46
> Status: Won't Fix (Intended Behavior)
This is very unfortunate, one of my apps that depend on this feature has over 4 million downloads, are you actually telling me and my hundreds of thousands of users who will "upgrade" to Android O to go screw ourselves?
This is very frustrating, if you feel like drawing over the lockscreen is suddenly unsafe you can let users grant an extra permission to allow it for certain apps.
I really don't understand why would you intentionally kill hundreds of apps that rely on this feature.
This is very unfortunate, one of my apps that depend on this feature has over 4 million downloads, are you actually telling me and my hundreds of thousands of users who will "upgrade" to Android O to go screw ourselves?
This is very frustrating, if you feel like drawing over the lockscreen is suddenly unsafe you can let users grant an extra permission to allow it for certain apps.
I really don't understand why would you intentionally kill hundreds of apps that rely on this feature.
lb...@gmail.com <lb...@gmail.com> #47
Guys, I don't know what will work to change Google's mind, but please do whatever you can. Write them about this on the Google Developer Console. Find other solutions they might consider and publish here. Find anyone from inside of Google that might have the power to raise this topic...
To me it's very sad news. For each feature that exists before, I think there should always be an alternative, to keep apps have their potential over versions. Better security doesn't have to mean less features.
To me it's very sad news. For each feature that exists before, I think there should always be an alternative, to keep apps have their potential over versions. Better security doesn't have to mean less features.
ja...@gmail.com <ja...@gmail.com> #48
Please add a similar function in the new Android O to allow power users to continue to embrace the future that is made possible with systems like Android.
sz...@gmail.com <sz...@gmail.com> #49
If they are going to restrict this, then offer customisable status bars, I'm sick of seeing a block of notifications on the status bar that I don't need to see! I want it in the notifications drop down, but I don't need every damn icon there. I swear this is written by people that don't have real jobs in a real world.
lb...@gmail.com <lb...@gmail.com> #50
js...@gmail.com <js...@gmail.com> #51
At least provide an option (advanced / developer options?) for apps to utilize this functionality!
th...@gmail.com <th...@gmail.com> #52
This change and other notification shade updates as part of the O release make this the first update that feels like a step back on Android.
rs...@gmail.com <rs...@gmail.com> #53
This is insane. I've updated to O and now my phone lost some very useful features! Ambient display is useless now, and so are Twilight and Deskdock. We need this feature back!
lb...@gmail.com <lb...@gmail.com> #54
Guys maybe instead of writing to a closed bug report that won't be fixed on Android O, which is already published, write a new post of the next Android version, with alternative solutions that Google might consider.
Even asking for this to return can be a good idea.
Just post here your posts, and people will consider starring them. I know I will.
:)
Even asking for this to return can be a good idea.
Just post here your posts, and people will consider starring them. I know I will.
:)
te...@googlemail.com <te...@googlemail.com> #55
Good idea. I would say alternative would be to make this something covered
under permissions that have to be accepted.
On Sep 22, 2017 15:50, <buganizer-system@google.com> wrote:
Replying to this email means your email address will be shared with the
team that works on this product.
https://issuetracker.google.com/issues/36574245
*Changed*
*lb...@gmail.com <lb...@gmail.com> added comment #54
<https://issuetracker.google.com/issues/36574245#comment54 >:*
Guys maybe instead of writing to a closed bug report that won't be fixed on
Android O, which is already published, write a new post of the next Android
version, with alternative solutions that Google might consider.
Even asking for this to return can be a good idea.
Just post here your posts, and people will consider starring them. I know I
will.
:)
_______________________________
*Reference Info: 36574245 regression: can no longer draw over system ui*
component: Android Public Tracker > Android Developer Preview
status: Intended Behavior
reporter: jm...@gmail.com
assignee: am...@google.com
cc: jm...@gmail.com
type: Customer Issue P3 S3
blocked by: 36847968 <https://issuetracker.google.com/issues/36847968 >
duplicate issue: 62081223 <https://issuetracker.google.com/issues/62081223 >
hotlist: Dev-Preview-O <https://issuetracker.google.com/hotlists/461170 >,
Platform <https://issuetracker.google.com/hotlists/461195 >
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google
IssueTracker issue 36574245
<https://issuetracker.google.com/issues/36574245 > where you have the role:
starred.
under permissions that have to be accepted.
On Sep 22, 2017 15:50, <buganizer-system@google.com> wrote:
Replying to this email means your email address will be shared with the
team that works on this product.
*Changed*
*lb...@gmail.com <lb...@gmail.com> added
<
Guys maybe instead of writing to a closed bug report that won't be fixed on
Android O, which is already published, write a new post of the next Android
version, with alternative solutions that Google might consider.
Even asking for this to return can be a good idea.
Just post here your posts, and people will consider starring them. I know I
will.
:)
_______________________________
*Reference Info: 36574245 regression: can no longer draw over system ui*
component: Android Public Tracker > Android Developer Preview
status: Intended Behavior
reporter: jm...@gmail.com
assignee: am...@google.com
cc: jm...@gmail.com
type: Customer Issue P3 S3
blocked by: 36847968 <
duplicate issue: 62081223 <
hotlist: Dev-Preview-O <
Platform <
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google
IssueTracker
<
starred.
al...@gmail.com <al...@gmail.com> #56
My screen dimmer apps no longer work and Night Filter + Brightness is not powerful enough. I will be going back to pre-8.0 for this simple reason.
lo...@gmail.com <lo...@gmail.com> #57
Hey @#56, I found a way to make a screen dimmer / night filter app that works on Android 8.0+ (and below), and also on Android Wear. The app is not quite production ready yet, but I'll do my best to get it on the Play Store by early February. You send me a Twitter DM so I keep you in the loop: https://twitter.com/Louis_CAD (and anyone else who wants to be notified when my app is ready)
lb...@gmail.com <lb...@gmail.com> #58
@57 You should make a POC and publish it on Github and Android-Arsenal, then.
Plenty of apps depend on this permission.
Plenty of apps depend on this permission.
dd...@gmail.com <dd...@gmail.com> #59
Please do not disrupt accessibility features to the detriment of those with disabilities. My issue is not serious as many people, but I will now need to refrain from using Android devices at night.
ja...@gmail.com <ja...@gmail.com> #60
As someone that suffers from brightness related issues, my best advice is to investigate fully the minimum brightness of a device before purchase. The site http://www.displaymate.com helps enormously with this, as they have tested many popular devices and reported the minimum brightness.
For instance, before purchasing the Galaxy S8, I checked the brightness on their site (http://www.displaymate.com/Galaxy_S8_ShootOut_01.htm ). If you scroll down about 3/4 you will see a "Lowest Peak Brightness" mentioned. This is the minimum brightness of the display in cd/m3 (nits). You want this to be as low as possible, ideally single digit numbers. The S8 has an excellent minimum brightness of 2 cd/m3. In fact, it is so low that I don't have it at minimum, even in complete darkness.
For instance, before purchasing the Galaxy S8, I checked the brightness on their site (
lb...@gmail.com <lb...@gmail.com> #61
@60 Wrong thread
ja...@gmail.com <ja...@gmail.com> #62
@61 Charming
ja...@gmail.com <ja...@gmail.com> #63
So are you people gonna restore my phone and get off of it i am jakobromeo72@gmail.com restore my s8+ to I'm sick off you people you are to smart for your britches get the hell off my phones put all default programs back on and remove your selves from my phone is there a contact number for a supervisor or someone that cares
lb...@gmail.com <lb...@gmail.com> #64
@63 You write in a thread that's not related to the problem you are seeing, and it's even a relatively closed thread, because Google marked it as "won't fix".
ja...@gmail.com <ja...@gmail.com> #65
How come my email address is not missing charictors like all of your why is my web sites all blocked why are u people/user in a public domain able to infultrate my phone what r u cops or something cause if you a are what you people are doing is eligal all of you should go to jail for this or send me a home address and I will come see you
ja...@gmail.com <ja...@gmail.com> #66
So what thread do I get on so I can fix this
lb...@gmail.com <lb...@gmail.com> #67
@65 For the rest of the users, they can't read your email. All I see is this:
ja...@gmail.com
@66 Here:
https://issuetracker.google.com/issues/new
Also, if it's related to Galaxy S8+, and not Android itself, you should contact Samsung and not Google. Google is not responsible for issues that other companies have created. Well at least for most of the cases.
ja...@gmail.com
@66 Here:
Also, if it's related to Galaxy S8+, and not Android itself, you should contact Samsung and not Google. Google is not responsible for issues that other companies have created. Well at least for most of the cases.
ja...@gmail.com <ja...@gmail.com> #68
Really cause at beginning of this you people were talking about tracker issues and seemed like you they or someone was or were talking or posting about. So is someone gonna give me some advice or contact number to someone who cares instead of telling me I'm on wrong thread
ja...@gmail.com <ja...@gmail.com> #69
I will keep commenting until someone helps please help or send me in right direction unless your all full of it and are liars cheers and Theves an like to mess with people's lives
lb...@gmail.com <lb...@gmail.com> #70
@68 Sorry I can't help you with this. I'm not working at Google and have no phone number to provide. Please stop spamming here. It's not nice.
de...@gmail.com <de...@gmail.com> #71
@69: As #67 said, you need to contact Samsung. The best way to get in touch with them would be to contact the person or company who sold you your Galaxy phone and file a complaint / bug report.
This forum (issuetracker.google.com ) is only meant for for pure Android (Pixel, Nexus, AOSP) and other Google products made *by* Google themselves, not Samsung or Motorola or HTC or LG or anyone else.
This forum (
ch...@googlemail.com <ch...@googlemail.com> #72
This is unbelievable from Google and has effectively rendered my phone unuseable at night as I rely on Twilight filtering the entire screen. Every release Google screws something new up (cf. bluetooth, do not disturb / silent mode, more and more useless notifications) why do they continue to make android worse and worse? Unless this is fixed it's goodbye to Android.
th...@gmail.com <th...@gmail.com> #73
Thank you, Google! Because of this stupidity in "the sake of security", now I have a burned-in screen on my Galaxy S7 because of the material design status bar and I cannot replace this crap and not downgrade the system version to Nougat from Oreo. Congratulations Mountain View, you will end with a brand new copy of iOS!
Now, I need to search another platform when the screen of this device finally turns useless.
Now, I need to search another platform when the screen of this device finally turns useless.
0j...@gmail.com <0j...@gmail.com> #74
Uh, subscribing?
qu...@gmail.com <qu...@gmail.com> #75
I have tried on the following devices: HTC 10, HTC one m7, Moto G3, moto G4, Moto G4 Play, and LG G6. All of the apps that I want to use originally worked on these devices, but after the security update the HTC 10 and LG G6 didn't properly work with the apps I want (like Twilight https://play.google.com/store/apps/details?id=com.urbandroid.lux ). Both the HTC 10 and LG G6 use Android 8.0, updated from Android 7.0 This garbage that Google did is actually making me consider switching to iOS
qu...@gmail.com <qu...@gmail.com> #76
I think over a year ago Google said they would close this bug, so maybe start a new one?
ke...@gmail.com <ke...@gmail.com> #77
@73
please go
@76
This is a proven security feature
please go
@76
This is a proven security feature
tr...@gmail.com <tr...@gmail.com> #78
@76 As the consumer I'd like to choose what level of security is acceptable for me. This is a major usability regression for the sake of security.
tr...@gmail.com <tr...@gmail.com> #79
Sorry, @77 not 76.
da...@gmail.com <da...@gmail.com> #80
I'm speaking as a user that wants control of the device they paid for. I'm shopping for apple product as MS repeatedly destroys my productivity and bank account with forced reboots/upgrades and a system that's trashed until I submit to the downtime. The same we know best is NOT what I pay for. I'll choose my own security and control of the device is paramount. Put the functionality needed for these apps to do what we love them to do or push us to other solutions and retributions.
pi...@gmail.com <pi...@gmail.com> #81
Is there any chance to consider this again? People are complaining not only here.
st...@gmail.com <st...@gmail.com> #83
There is a bigger issue !
After the last July security update of Oreo on Samsung Note 8, the CPU meter stays at 0%, and Cool Tool says that Selinux is detected !!
SeLinux was always in Enforcing mode all the time sice last year on Note 8, even with May and June security updates on Oreo, CPU meter was working OK !!
So from the last update - 1 July security update, Cpu meter always shows 0%
After the last July security update of Oreo on Samsung Note 8, the CPU meter stays at 0%, and Cool Tool says that Selinux is detected !!
SeLinux was always in Enforcing mode all the time sice last year on Note 8, even with May and June security updates on Oreo, CPU meter was working OK !!
So from the last update - 1 July security update, Cpu meter always shows 0%
ja...@gmail.com <ja...@gmail.com> #84
yep, i noticed that after updating S8. Had to ditch the CPU meter app I had.
Its a real shame. One of the things I always liked about Android was that it didn't "hide" system information like iOS.
Its a real shame. One of the things I always liked about Android was that it didn't "hide" system information like iOS.
Description