Continue logging while app is in background

Question

Continue logging while app is in background

tjanson opened this issue 9 years ago · 6 comments

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.

Answer 1 · 2015-03-13T22:46:01.000Z

This seems to be working fine. I’ll keep this open for the following improvements:

somehow make sure the app does not get killed by Android while in the background
display a permanent notification while logging

Answer 2 · 2015-03-15T11:24:10.000Z

see also #9 which is related

Answer 3 · 2015-03-16T13:26:49.000Z

One possible problem:

Ach ja, da vermute ich: bekanntes Wlan gefunden!
Wenn nämlich das Android ein auf "automatisch verbinden" gestelltes Wlan sieht, dann geht es in die DHCP&Co-Prozedur... und das bringt Wifi-Scanner ins Straucheln. Aber der Wifianalyzer und die Wiggle-App erkennen das und recovern einige Sekunden später wieder.

Answer 4 · 2015-03-16T14:14:38.000Z

Android Reference: Processes & Threads

Answer 5 · 2015-03-16T21:24:41.000Z

please have a look at Open W-LanMapp Aplication
http://sourceforge.net/p/libwlocate/code/ci/master/tree/master/

Answer 6 · 2015-03-16T21:47:29.000Z

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.
On my own devices, I’ve never seen the app be killed. Then again, this might be different on other devices and Android versions.

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)