Closed lead-legs closed 4 years ago
I have 3.4.6 installed. If you leave voice on and mute the volume on the phone the screen switches off properly.
This solved my problem. Screen turned now on and off automatically! Thanks!
People suggesting solutions: please specify which OS and which version you are using. The issue seems to depend on which version of Android you use so claiming a 'fix' is likely to confuse people - especially the devs.
Andy
I have 3.4.6 installed. If you leave voice on and mute the volume on the phone the screen switches off properly.
Not really a fix, workaround at its best but does the trick. Runs on Android 8.0.0
I have 3.4.6 installed. If you leave voice on and mute the volume on the phone the screen switches off properly.
Doesn't work on Android 4.4.4.
Same issue on my older navigation device, screen turns on but NOT off. (However, will turn off after approx 30 sec. inactivity time out) Did work with older OsmAnd+ version. Now OsmAnd 3.4.8, Android 4.4.2 Samsung S4Mini (no more updates on Android) Works fine on Samsung S10E, Android 9 OsmAnd+ 3.4.8 So, to me it seems related to Android version. I want to keep using the S4Mini because it fits the holder on my racing bike.
On my last bicycle trip i used Osmand Nighty and Osmand +. By both the screen turned off, but before it turned off, i saw the unlock screen for some seconds.
Apart from this it was so terrible to navigate with Osmand because the screen don't turned on when you had to change the direction, just some seconds before. When turn, screen off. Also all turning commands came to late, like lags in a game, even i had about 18 satellites for recieving. I was so angry to you deveopers. Next thing, nearly every time when a new update comes, you have to make again your personal preferences in the app. Can not be true.
Additional info: same problem on other device: Samsung tablet S2: OsmAnd 3.4.8 Android 7.0 Screen turns on, but NOT off after selected time out (5sec). So far the only correct working device is my S10E with Android 9.
OsmAnd 3.4.8 Android 6.0.1 on Motorola G3; no unlock screen. No improvement. Screen comes on at right times, but never goes off.
Same issue on my older navigation device, screen turns on but NOT off. (However, will turn off after approx 30 sec. inactivity time out) Did work with older OsmAnd+ version. Now OsmAnd 3.4.8, Android 4.4.2 Samsung S4Mini (no more updates on Android) Works fine on Samsung S10E, Android 9 OsmAnd+ 3.4.8 So, to me it seems related to Android version. I want to keep using the S4Mini because it fits the holder on my racing bike. You should be able to flash a more recent version onto the S4 Mini, I'm sure had something else on mine before it got pinched. But, yes, the OS version does make a difference because Google significantly changed the way permissions were handled in Android 6 (I think it was this). I think things have changed again with Android 9, particularly if something like facial recognition is active.
Having only just recently switched from my S5 for a similar reason - having a good case and bike holder is far more important than the latest shiny, shiny - I would suggest you think about getting a case for the S10. I already had a quadlock (Ottercase + adapter for the S5), Quadlockcase for S10e. The newer screens are definitely more legible in bright sunlight and, more importantly where I live, they're less susceptible to water droplets. With the S5 if it was raining when the screen was on, the phone would think it was being operated on. None of those problems with the S10e, though, of course, I still had all the problems with the screenlock not switching off. I really think the only way to solve these is with a debug build.
This has now been fixed for me in both devices Motorola G3 (Osprey) Android 7.1.2. Osmand 3.4.8 (2019-08-20) Motorola E (Surnia) Android 7.1.2 Osmand 3.4.8 (2019-08-20)
Fixed on S4 mini Android 4.4.4 OsmAnd 3.4.8
with the new version 3.5.2 the issue came back for me on S4 mini Android 4.4.4: the screen doesn't turn on, with the version 3.4.8 it worked
with the new version 3.5.2 the issue came back for me on S4 mini Android 4.4.4: the screen doesn't turn on, with the version 3.4.8 it worked
Same here, though I've not had it work properly on the S10e at all.
with the new version 3.5.2 the issue came back for me on S4 mini Android 4.4.4: the screen doesn't turn on, with the version 3.4.8 it worked
after a quick check with the version 3.5.3 it seems to be fixed for me
Upd.: I've checked the "Turn display on" setting and it works for me. It turns on on navigation event, then it switches to lock screen after the "Wake Time" seconds if next event does not reset timer. And then, after a few seconds screen turns off. Not sure it is supposed to work this way but seems to be logical and expected for my phone model. The time gap between switching to lock screen and turning it off increases if Intelligent Scan (unlock by face and eyes) enabled.
Proximity sensor setting does not work when Smart Stay is enabled, should be true for all Samsung Galaxy devices with this function. Probably it monopolizes sensor so OsmAnd can't use it.
Not sure the issue below is the related, but looks similar. I'll make some further research on existing tickets and behavior of old OsmAnd versions and will move it to the new feature request if necessary.
When Osmand app is active it prevents the screen to turn off. Whether it just shows the map, any settings screen, in navigation mode or not - the screen never turns off automatically. There is NO problem with screen locking or turning screen off manually using power/lock button. If I turn off screen manually and then turn it on Osmand shows instead of the lock screen. It prompts password or unlock id when trying to switch to another app or open system settings etc - seems to work properly. Also there is NO problem with background process: when osmand is not the active app and home screen, settings or another app is currently active even when navigation currently active screen turns off automatically according to system timeout setting. Voice prompts works properly even id screen is turned off. In 3.5.5 I can't find the option to toggle OsmAnd appearing above the lock screen - was it removed?
P.S. For sure defaults are of my personal preference and should be guided by some observation like usage statistics, survey or voting.
Upd.: Looks like it's done with xml layout files so it need to be reworked with flags to have an option to turn it off https://github.com/osmandapp/Osmand/search?q=keepScreenOn&unscoped_q=keepScreenOn.
Not to confuse with too many requests on same issue, I will open a different request for keep screen on option and close this one.
I had a similar problem on android 10... not sure it is exactly the same, but you can have a look at my comment on #8034 (se link above) regards Ess Bee
Screen wake-up using the proximity sensor does not work on Samsung Galaxy S22 and Android 14. When you try to manually unlock the screen, the Osmand navigation screen does not show, only the lock screen (biometric lock set using fingerprint)
Turn screen off no longer works - Since the update, I can set the screen to turn on automatically but no matter what seconds I set the screen doesn't tun off. #7315