Ignore battery optimization settings to prevent suspension #1216
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
ghost
approved these changes
Aug 15, 2019
Member
|
Really nice work @danog! This will be in v0.74 of the app, to be released in an hour or so. |
Contributor
Author
|
Thanks <3<3<3! Thanks again. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixes #377 by whitelisting termux when the user clicks on the wakelock button for the first time.
Even if the android docs say a foreground service is enough to prevent suspension, on my devices running CLI services stop sending UDP/TCP packets and get suspended if the app is reduced or the device is locked.
This is especially noticeable when running a simple
time ping 192.168.1.1; on resume, the ICMP sequence number is way lower than the number of elapsed seconds, indicating a suspension of the process.Anyway, I encountered this issue on my devices and noticed that manual whitelisting fixed it, thought I could contribute with an automated fix.