This repository has been archived by the owner on May 21, 2022. It is now read-only.
Improve explanation for "Active App Notification" setting #563
Conversation
This file contains 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
ammgws
changed the title
added 2 commits
June 16, 2020 09:33
If you turn this off (persistent notification) then ensure battery optimizations are enabled.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
For me, it wasn't immediately 100% obvious that this setting controlled the persistent notification.
Also, the warning message was discouraging me from trying out the setting as I do not want to skip scrobbles, though I found out later that the warning is for when battery optimisations are not disabled for the app.
Hence rewrote both to make it more clear.