You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While recording, TrackRecordingService grabs a Wakelock.
It seems to be a leftover from ancient times as GPS locations are reported using a callback and for the rest, we use handlers.
Note: We might get some problems after for BLE sensor data only (i.e., after merging #1033).
While recording, TrackRecordingService grabs a Wakelock.
It seems to be a leftover from ancient times as GPS locations are reported using a callback and for the rest, we use handlers.
Note: We might get some problems after for BLE sensor data only (i.e., after merging #1033).
Documentation: https://developer.android.com/training/scheduling/wakelock
Got the idea from here: https://gpslogger.app/#howisthisdifferentfromotherloggingapps
The text was updated successfully, but these errors were encountered: