Turn screen on (and OFF)? automatically

[P Wat]

In Settings, Navigation settings (Profile specific settings), Cycling, you find “Turn screen on – Turn on device screen (if off) when approaching a turn”.

Then; “Time - Set the time for which the screen will turn on.”

In there you find; “Time” offers eight options; “Never”, “5 seconds”, “10 seconds”, etc, to “60 seconds”.

It seems that whatever value I select between 5 and 60, the screen COMES ON (if off) when approaching a turn (as indicated in one of the forgoing menu stages0, but it REMAINS ON indefinitely.

 

1)  Is anyone else having the same problem?

2)  Am I doing something wrong?- If so, would someone kindly explain how to make it work.

3)  Is this feature known to (STILL) be non-functional? – If so, would it be a good idea to modify the menu text to the effect of “We are sorry this feature is temporarily not available.  We hope to restore it before Christmas”. – (2020?)

 

This brilliant feature had formerly been one of the great selling points of this excellent app.  Who else would like to see it working again?

 

I’m using Osmand+ version 3.4.6 on Android 7.0

Apologies for seemingly resuscitating an earlier topic under a new guise, but the previous one appears to have lost impetus.

Thanks

Paul W

[Xavier]

On Sat, Aug 10, 2019 at 07:01:45AM -0700, 'P Wat' via Osmand wrote:
>This brilliant feature [screen on/off automatically] had formerly been

>one of the great selling points of this excellent app. Who else would
>like to see it working again?

Don't blame OsmAnd, blame Google:

https://github.com/osmandapp/Osmand/issues/6675

Specifically these notes:

dmpr0 commented on Mar 14

Hello @bluescreen303!

The current release doesn't include this feature, we had to remove
this option because of Google Play rules about the permission
needed to that action. We are trying to find a solution to get it
back.

Somewhere else (that I can't locate at this time) I had also found
reference to the Google Play Store rules change resulting in OsmAnd
being removed from the Play Store because it used the permission that
Google is now upset about.

The current version you have is the dev's first attempt at restoring
the feature without utilizing the permission setting that Google is
upset about, and it seems that not all of the bugs have been found and
fixed yet.

So your best way to let the dev's know of the problem you see is to
post a note on Github about the problem.

[P Wat]

Hi Xavier - You (quite rightly) say; "Don't blame OsmAnd".  -  Indeed, I don't.  My purpose was to question the logic of offering a range of "Turn Off" times, without mentioning that they are (currently) not available.

Your reference to https://github.com/osmandapp/Osmand/issues/6675 is useful, thanks, and right down the bottom it links to #7315 on which max-klaus said 2 days ago "It ... ... don't work on all devices."

One can at least hope the gurus are still working on a solution for all devices.

Meanwhile, I'd love to know if there is a (fairly simple) way for me to make it work on mine.

Thanks

PW

[Xavier]

On Sun, Aug 11, 2019 at 09:40:03AM -0700, 'P Wat' via Osmand wrote:
>On Saturday, August 10, 2019 at 4:33:45 PM UTC+1, Xavier wrote:
>>
>> On Sat, Aug 10, 2019 at 07:01:45AM -0700, 'P Wat' via Osmand wrote:
>> >This brilliant feature [screen on/off automatically] had formerly been
>> >one of the great selling points of this excellent app. Who else would
>> >like to see it working again?
>>
>> Don't blame OsmAnd, blame Google:
>>
>> https://github.com/osmandapp/Osmand/issues/6675

>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fosmandapp%2FOsmand%2Fissues%2F6675&sa=D&sntz=1&usg=AFQjCNHLUJx9UUtgWJPEso1kyEXydxuIvw>

>>
>> Specifically these notes:
>>
>> dmpr0 commented on Mar 14
>>
>> Hello @bluescreen303!
>>
>> The current release doesn't include this feature, we had to remove
>> this option because of Google Play rules about the permission
>> needed to that action. We are trying to find a solution to get it
>> back.
>>
>> Somewhere else (that I can't locate at this time) I had also found
>> reference to the Google Play Store rules change resulting in OsmAnd
>> being removed from the Play Store because it used the permission that
>> Google is now upset about.
>>
>> The current version you have is the dev's first attempt at restoring
>> the feature without utilizing the permission setting that Google is
>> upset about, and it seems that not all of the bugs have been found and
>> fixed yet.
>>
>> So your best way to let the dev's know of the problem you see is to
>> post a note on Github about the problem.

>Hi Xavier - You (quite rightly) say; "Don't blame OsmAnd". - Indeed, I
>don't. My purpose was to question the logic of offering a range of "Turn
>Off" times, without mentioning that they are (currently) not available.

Best guess -- the range of times for 'on time' worked on the devices
the developers tested against. They just missed that not all deviced
worked. So best is to file a report indicating device, android
version, etc. in hopes that such can help them further enhance the
feature.

>Your reference to https://github.com/osmandapp/Osmand/issues/6675 is
>useful, thanks, and right down the bottom it links to #7315

><https://github.com/osmandapp/Osmand/issues/7315> on which max-klaus said 2

>days ago "It ... ... don't work on all devices."
>One can at least hope the gurus are still working on a solution for all
>devices.

I would expect so. But adding a report for your device would, at
least, give them another data point to work with.

>Meanwhile, I'd love to know if there is a (fairly simple) way for me to
>make it work on mine.

Unknown. Although for "fairly simple" I'd say that answer is most
likely a no. There might be a very complex way involving writing Java
and compiling it for Android, but that's far from 'fairly simple'.

[P Wat]

> Xavier - Yes to all that.  Thanks.  Paul W