New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wakelock.enable()
changes system Ui overlay style on Android
#161
Comments
Wakelock.enable
changes system Ui overlay style
Wakelock.enable
changes system Ui overlay styleWakelock.enable()
changes system Ui overlay style
This is similar to my issue, so I will just post within this issue. My issue is the status bar text color is changing and it occurs with enable or disable calls. Attached is simple program with the issue. I have also put in an issue with Flutter since this appeared with the 2.8.x Flutter update. |
Wakelock.enable()
changes system Ui overlay styleWakelock.enable()
changes system Ui overlay style on Android
hi :) I am not sure why this happens exactly - the only call that happens is setting the wakelock flag natively. This will require further investigation. |
Yeah. I can confirm this. I called Wakelock.enalble() then it changes status bar icon brightness to Brightness.light and i have noticed this only occurs in android 11. This is a major problem. |
On Flutter 3.0.1, the problem is more relevant than ever. |
I will soon discontinue this repository. Please use wakelock_plus: ^1.1.6 instead. |
Calling Wakelock.enable changes system Ui overlay style to the one default of the system. In particularly, this changes the status bar icon brightness.
This was tested on Android. Simply call Wakelock.enable after setSystemUIOverlayStyle with a different status bar icon brightness from the one of the system.
I suspect this isn't due to the Android plugin or the Flutter interface but due to the Android system and it's wakelock flag. Currently, I circumvent this by setting my custom overlay style based on my own app theme before and after the Wakelock call, since I enable it with low priority later in the initialization.
EDIT: I wasn't able to solve it by setting the overlay after the Wakelock call, I was forced to disable Wakelock (not call Wakelock.enable).
The text was updated successfully, but these errors were encountered: