WAI
Status Update
Comments
ra...@gmail.com <ra...@gmail.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.
gf...@gmail.com <gf...@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.
gf...@gmail.com <gf...@gmail.com> #5
componentid:190923 status:open
[Deleted User] <[Deleted User]> #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
xa...@android.com <xa...@android.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
xa...@android.com <xa...@android.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
[Deleted User] <[Deleted User]> #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!
[Deleted User] <[Deleted User]> #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.
an...@gmail.com <an...@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.
[Deleted User] <[Deleted User]> #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.
ih...@gmail.com <ih...@gmail.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.
dv...@gmail.com <dv...@gmail.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
be...@gmail.com <be...@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?
dv...@gmail.com <dv...@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!
Description
Java: 1.8.0_65-b17x64 Oracle Corporation
OS: Windows 7(amd64) v6.1 Service Pack 1 (1920x1200, 1920x1200)
Gradle version: 2.8
Android Plugin Version: 2.0.0-alpha1
SDK Version: 24.4.1
Module Compile Sdk Version: API 22
Module Build Tools Version: 23.0.2
****
I updated to the latest preview build of Android Studio and during the build process (with "instant build" enabled) for my project, received this error:
Error:Execution failed for task ':app:transformResourcesWithMergeJavaResForDebug'.
> com.android.build.api.transform.TransformException: com.android.builder.packaging.DuplicateFileException: Duplicate files copied in APK META-INF/maven/com.squareup.okhttp/okhttp/pom.properties
File1: C:\Users\kyleparker\.gradle\caches\modules-2\files-2.1\
File2: C:\Users\kyleparker\.gradle\caches\modules-2\files-2.1\com.squareup.okhttp\okhttp\2.4.0\40340c0748190fe897baf7bffbc1b282734294e5\okhttp-2.4.0.jar
****
The project compiled properly on Android Studio version 1.5, Gradle plugin 2.2.1.
In order to circumvent the problem, I had to add this to my build.gradle for the project:
packagingOptions {
exclude 'META-INF/maven/com.squareup.okhttp/okhttp/pom.properties'
exclude 'META-INF/maven/com.squareup.okhttp/okhttp/pom.xml'
}