In an attempt to replace a Garmin GPS by a smartphone, I would like to follow a turn by turn biking navigation using a gpx file with direction waypoints (based on Client Brouter).
Not perfect but this works (with some adjustments). When navigating, I can hear voice instructions corresponding to the OM icons.
I would like the screen to be turned on when arriving at a Wpt. The screen will be off after the Android "screen timeout". If I leave the screen always on, my battery will be quickly out of service (my target is a 5 hour trip).
But the screen behavior is not as expected: the screen stays off after passing Wpts
I don't know whether it is an OM bug or a feature such as "disable screen lock" not available on my Samsung/Android system (or a bad configuration/usage). I tried with S6 with same OM version, and the problem is still on.
Any way to fix or bypass this issue?
My configuration:
Oruxmaps GP 10.7.4
S20/Android 13
Screen timeout 15s
OM:
No permission denied (prevent phone from sleeping On)
Allow Background data usage
Allow data usage while data saver is on
Battery Unrestricted
OM Global settings:
Application
Screen Always ON No
Screen not switched off in track logging mode
Display Brightness Yes
Unlock screen automatically Yes
Disable screen lock while the app is recording a track or following a route
Unlock screen automatically Yes
ALWAYS disable screen lock for this app
Turn on display with alerts Yes
Turn on screen when receiving an alarm from Oruxmaps
Text To Speech/Sounds Waypoints
Near waypoint alarm Yes
TTS waypoint voice message Yes
TTS waypoint name Yes (No S6)
TTS waypoint description Yes (No S6)
Play waypoint extensions No
Max. Waypoint alarm warnings 2
Waypoint Distance 80
Hello, it should simply work with the configuration you have. It works for me in oppo A9 and LG k30. Samsung is a peculiar system I always read Samsung-OruxMaps incidents. Do you have any kind of screen unlock (pin, pattern, etc.)? Try to leave the phone without any lock, in case Samsung does not obey this configuration.
Hi,
Thanks
I forgot to mention that I have "None" for Screen Lock Type. I will try using my wife's Oppo Find X3 (when available).
Any third application for bypassing this issue?
Follow-up: works as expected with Oppo Find X3 Android 13.
So it seems that the common factor of the error is Samsung?