Open
Conversation
…n is off (using AlarmManager)
|
+1 |
|
You commit crash if there are non-valid or no server information. Just get a fresh emulator go to settings and wait for some minutes. |
Author
|
Thank you for testing that. I will take a look at this. But I am wondering why it crashes after a few minutes when it tries to connect every 5s (default). Maybe something else is wrong. |
t-h-e
added a commit
to t-h-e/pyload-android
that referenced
this pull request
Nov 12, 2016
- pull request from tonsense (pyload#10) - updated to thrift 0.9.3 - synchronized access to thrift client
|
|
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
4 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.
Added (optional) Notification Service to check for new Captchas in Background even when screen is turned off.
This is done by using the AlarmManager, which starts the Service repeatedly (using the interval from the preferences) when leaving the App.
The Service can be enabled/disabled very easily with a checkbox in the menu.
The implementation is done in a pretty simple way. So maybe it could be done in a more efficient way by using the background thread which holds the connection? As far as I know the Threads won't be alive for a long time when the screen was turned off.