-
Notifications
You must be signed in to change notification settings - Fork 10
Continue logging while app is in background #1
Comments
When the app goes out of foreground while logging to disk, e.g., because the screen turns off or another app is started, acquire partial wake-lock and continue logging. If not logging to disk, behavior is unchanged, i.e., updates are suspended. This feature is (particularly) experimental and definitely needs testing and/or a review. See #1
This seems to be working fine. I’ll keep this open for the following improvements:
|
see also #9 which is related |
please have a look at Open W-LanMapp Aplication |
I scanned some of the code. They also use a wake-lock, but that’s not surprising. I’m suspecting that the issue of interruptions in the log is generally not because the app is killed, but because the Wifi scan has problems and doesn’t return within a reasonable time. I think we should focus on implementing a warning if no scan result arrives in a certain amount of time. That way, no matter what caused the interruption, at least the user will be informed. (see #9) |
Currently location updates & wifi scans are suspended
onPause
. This is impractical for real-world usage. The user should not be forced to have the app in the foreground; instead, logging should continue (until stopped by the user) and a notification should be displayed.The text was updated successfully, but these errors were encountered: