In order to minimize battery impact on the device when recording a track while the screen is off, MyTrails uses the standard method offered by Android where the application is woken up by the OS only when a new track point is ready to be recorded.
- On some phones, Android may occasionally lose track of this, and forget to wake MyTrails up. This would result on a track where no recording takes place during some stretches where the screen was off. Because this is a platform bug and so far has been reported only once, I do not intend to add a potentially harmful work-around to MyTrails.
You can implement the work-around on your phone by downloading Wake Lock from the Play Store and using it to keep a PARTIAL_WAKE_LOCK when running MyTrails.
- Some phones may incorrectly stop recording the track when the Temporal resolution preference in MyTrails is set to something other than 1s.
- You can even use the
TRACKER_OPTIMIZATIONhidden option (disable it).
- System optimizers such as Juice Defender may also stop the GPS when the screen is turned off. Disabling that dubious optimization restores the recording functionality.
- Some users have reported that using GPS Test to clear and reload the AGPS data may help restore GPS operation for all apps.
- Android Marshmallow and later have the ability to stop background apps (to save battery) when the device is not moving. This shouldn’t affect MyTrails, except some versions of Android do this incorrectly and also stop apps when you’re hiking. In these cases, allowing MyTrails to keep running in the background may help: Android Settings > Apps > gear icon (Configure apps) > Battery optimization > All apps > MyTrails > Don’t optimize. Because this is a bit convoluted, I made short animation below.
If you do experience this, please contact me or add a comment below so I can keep track of the affected users and phone models.