Add caveat in README #30
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using this on Android 10 I get the screen brightness changed, but the brightness control is also locked from making other changes (the effect is as described in https://support.google.com/android/thread/43144590?hl=en ). I found some more info in https://stackoverflow.com/questions/4544967/get-preferred-screen-brightness-in-android and I know that apps for blue light filtering or automatic night time dimming use GPU-related screen filtering rather than touching the screen brightness setting.
It seems the WRITE_SETTINGS permission could theoretically allow changing the system-wide setting, but I've not seen this work in practice on Android 10.