Locus Map - forum

Support => Troubles & Questions => Topic started by: deelite on July 07, 2020, 13:06:50

Title: Screen locked with PIN when navigation
Post by: deelite on July 07, 2020, 13:06:50
Hello, I have to raise this subject again.
When I navigate with LM, my S10e is locked after the screen is turned off (although automatic locking is disabled in general and disabled in my presets) and I can ONLY unlock it with the PIN. Not with Face Unlock and also not with the fingerprint.
Since the screen does not always turn on reliably before a turn, I have to stop before it every time or enter the PIN while driving.
This gets on my nerves so much that I use other apps for navigation, which I don't really like, since I'm tracking with LM anyway.

In another thread I've already been told that this is a Samsung specific problem. This is not so. My wife has the same problem on her P30 lite new edition. And other navigation tips (Komoot, Maps.me) also stay on during navigation and the phone can be unlocked with Face Unlock or fingerprint after turning off the screen.

So the problem must be with LM. And I know that I am not the only one with this problem.

Please try to solve it.

Thanks a lot already.
Title: Re: Screen locked with PIN when navigation
Post by: GusGF on July 07, 2020, 22:24:03
Yes I also have the same problem on a Honor 8X
Title: Re: Screen locked with PIN when navigation
Post by: 0709 on July 16, 2020, 21:24:27
*Fingerprint Unlock Tests. What I found.

A. Display OFF by Android only. (Screen Sleep time out or by short push power button )

Komoot Android screen time out > Display OFF > Fingerprint unlock > Display ON (complete unlock)
Locus Android screen time out > Display OFF > Fingerprint unlock > Display ON (complete unlock)

B. Display OFF by a Locus map Pro action. (Locus Device Administrator /Locus Map as service )

(Settings > Controlling > Display > Screen ON/OFF control)

When Locus map Pro triggers a Display OFF,  than Fingerprint unlock asks PIN.

By the actual Locus map Pro version.

1. Display OFF > Push Power button > Display ON. (Partial unlock, Locus map, no keyboard)
2. Display OFF > Proximity Wave Unlock > Display ON. (Partial unlock, Locus map, no keyboard)
3. Display OFF > Fingerprint Unlock > Phone asks PIN > Tap Return Button > Display ON. (Partial unlock, Locus map, no keyboard)
4. Display OFF > Fingerprint Unlock > Phone asks PIN > Enter PIN > Display ON > (Complete unlock, keyboard activ)

Enter PIN if you need other Android app, e.g the keyboard app.
Title: Re: Screen locked with PIN when navigation
Post by: jonny.blue on July 16, 2020, 23:38:55
Quote
Fingerprint Unlock Tests.

I have this problem too 🙄... but never examined in that way. 😎
Title: Re: Screen locked with PIN when navigation
Post by: GusGF on July 17, 2020, 00:20:05
Yea really good information I'll be checking next time I'm out.

Thank you
Title: Re: Screen locked with PIN when navigation
Post by: michaelbechtold on July 17, 2020, 16:43:35
Very good indeed, 0709!
It also tells that Locus does it right. Because Locus must not enable other apps to work in foreground.
Title: Re: Screen locked with PIN when navigation
Post by: GusGF on July 18, 2020, 14:44:05
Is this in the Locus documentation?   ::)

Should be, very beneficial  :)
Title: Re: Screen locked with PIN when navigation
Post by: deelite on July 21, 2020, 22:45:31
Did you test all these scenarios while navigating with LM?
All unlocks are working as expected and as you explained when NO navigation is running. I can unlock with no problems by fingerprint or there is no lock.

But there is a lock when locking is of and fingerprint isn't working WHEN navigation is running.
It's all about the navigation.
Title: Re: Screen locked with PIN when navigation
Post by: 0709 on July 22, 2020, 08:44:45
QuoteDid you test all these scenarios while navigating with LM?
Did you ?

General rule: "The app that turns the display OFF must turn the display ON".

Locus Pro Panel: "Display (de)activate" SET @ navigation.

- @ navigation display OFF by auto screen turn-off function in that panel. (You have set)
- Than display ON should be triggered only by function (gesture) in that same Panel.

If you do not like, you should not use display OFF function by the Locus panel.
Than only use the standard Android display time out.  Example 15 sec or 30 sec etc.
- Locus Panel: "Display (de)activate" > Auto screen turn-off: SET: 0.
- Locus Panel: "Always Screen On": SET: OFF

Display OFF by the Android time out > Fingerprint will reliably open Display without entering PIN @ navigation.

By the way. A function NOT offered by Locus.  Nice to have for (walking) users with a flip case ?
I do not need...so I do not suggest in New Idea. See a video how it could look like.

https://youtu.be/odWv_dptYUI
Title: Re: Screen locked with PIN when navigation
Post by: Henk van der Spek on July 22, 2020, 09:37:02
Don't go hiking with a flipcase. It will impact your compass reading.

Verstuurd vanaf mijn Armor_2 met Tapatalk

Title: Re: Screen locked with PIN when navigation
Post by: 0709 on July 22, 2020, 09:56:31
I agree Henk with that warning. Also the one I do use as is shown in the demo video, does have a magnetic closure. (And I suppose most such flip cases do have).  I know also "GusGF" does not use a flip case  ;)
Title: Re: Screen locked with PIN when navigation
Post by: deelite on July 23, 2020, 15:23:47
Quote from: 0709 on July 22, 2020, 08:44:45
QuoteDid you test all these scenarios while navigating with LM?
Did you ?

Yes, several hundred times.

QuoteGeneral rule: "The app that turns the display OFF must turn the display ON".

Okay, that makes sense to me.

QuoteLocus Pro Panel: "Display (de)activate" SET @ navigation.

- @ navigation display OFF by auto screen turn-off function in that panel. (You have set)
- Than display ON should be triggered only by function (gesture) in that same Panel.

Sorry, I don't know what you mean with "Locus Pro Panel" and with "display OFF" -> I don't know any setting that looks like this.

But: thank you very much first of all for the explanations, if I still find the settings in question, this might be a solution for me.
Title: Re: Screen locked with PIN when navigation
Post by: 0709 on July 23, 2020, 17:09:24
See attachment.  Display on/off feature in Locus Pro  ;)
https://docs.locusmap.eu/doku.php?id=manual:user_guide:settings:control#screen_on_off_control
See auto screen turn off. (Set to 0)

Auto screen turn-off
setting of the interval before turning the screen off again
is set in 5 second steps from 0 to 120 seconds. 0 = screen turning off is disabled (until the system (Android) turns the screen off)
Title: Re: Screen locked with PIN when navigation
Post by: deelite on July 23, 2020, 17:26:33
OK, the 0 seconds for auto turn off I always had set. But I used "Display always on" when charging. In all used presets and in Locus' global settings. This I turned off and now a dry run at home works. I will ride my bike for a while to test it.

Vielen Dank für die Erklärung!

However, it seems to me a very sensitive function when these two settings influence each other.
Title: Re: Screen locked with PIN when navigation
Post by: jonny.blue on July 23, 2020, 19:27:04
Quote
General rule: "The app that turns the display OFF must turn the display ON".

I wasn't aware of that ... thanks for explanation.

Now ... after two years 🙄 I finally found all my settings to use LM with moto bike👍 without touching the screen (or even stop and be forced to interact)😎
Title: Re: Screen locked with PIN when navigation
Post by: 0709 on July 23, 2020, 19:40:59
OK fine...problem hopefully solved by these complex settings.

Well I must admit that I was a bit surprised by the nature of the original question and especially by the reference to the Komoot app and others.

Locus Pro (if allowed) IS Device Administrator.
So I assumed that Locus Pro users always use the practical Gesture control for manual display control. For a cyclist with gear mounted on the handlebars by a single wave, and for walking by a double wave. No PIN, even if set to display always on. I recently even had a small discussion about this subject with the Locus team to simplify the entire display setting, so I better keep quiet now ;-)

But first here another hidden treasure and secret by changing the config.cfg file setting.

By a (single) gesture wave set the display continuously ON (gesture wave action ON than has the highest priority). This until by a subsequent (single) wave you set the display back to OFF. The standard ON/OFF sequence is than continued, so steered by the navigation instructions and the auto display off time out setting.

Interesting mode, as when you are approaching complicated street patterns, you can leave the map activ for a while. When the difficult part is over then you just go back to normal by a next (single) Gesture Wave. Very usefull imo.

It concerns a setting in the config.cfg.  Change default setting 0 to 1.
With the current Locus version config.cfg you will find the item on line 204.

# Disable "Turn off if idle" when screen was turn on by gesture (default: false)
turn_on_screen_by_gesture_disable_auto_screen_off = 1

Close Locus then edit the config.cfg (notepad ++). Then restart Locus and ready.
Title: Re: Screen locked with PIN when navigation
Post by: deelite on July 24, 2020, 15:38:26
So, I have now tested the navigation on several trips and I must say: it works perfectly!

Thank you very much!

In the course of this, I have also tried out the gesture control, as I did not think it was necessary until now. But actually it makes sense.

But unfortunately it does not work for me. Do I understand correctly that I simply have to wave 1 or 2 times over the smartphone to switch it off or on? But it does not work for me. Do I have to set anything else in my Smartphone?
Title: Re: Screen locked with PIN when navigation
Post by: 0709 on July 24, 2020, 19:30:54
The proximity Gesture sensor.
I have experiences with 2 (old) Samsung, 2 THL and a Xiamo Mi A2 Lite Phone.
On these phones the method was and is perfectly functional.
See a wave action in use in an old video recording here.
By very low memory Samsung Ace (gps use only).
No Google services nor play, no fingerprint, no PIN, no SIM.
Locus Free apk install and external gesture proximity app name DTSO.
There is not shown any display activation at turns because operating Locus Free !

https://youtu.be/NM59pgl3ZAU  Goto 48 sec for the first wave display OFF action.

Samsung S10.
I do read some phones have a very unsensitiv sensor, and the S10 sensor is one such a troublemaker. :-((
https://help.locusmap.eu/topic/display-activation-samsung-galaxy-s10#comment-85870
https://help.locusmap.eu/topic/gesture-screen-control-not-working
Title: Re: Screen locked with PIN when navigation
Post by: jonny.blue on July 24, 2020, 20:00:36
Quote
Now ... after two years 🙄 I finally found all my settings

Ohhh 🙄 this was a little bit to fast ... 😪

Changed my settings so android (should ) turn off the screen ...

Yesterday on the couch everything worked well ... today during my outdoor biking:
- startet recording and navigating along a route
- screen turned off after 30 seconds (as expected 👍)
- next navigation command turned screen on 👍
.... and it never turned off again🤔
Stopped navigating ... no change.
Stopped recording ... no change.

After 20 minutes I went back to my old settings ( LM turns off screen).
This works good ... the only problem which remains:
When I use LM and open another window/panel/screen like 'geocaching' a pin is asked.
Despite my device being connected with my 'trusted' bluetooth.🙄
Title: Re: Screen locked with PIN when navigation
Post by: 0709 on July 24, 2020, 20:49:21
I tested....The Android time out does turn the screen off. Android time out set for this test = 15 seconds.
Observe the turn alert display ON action, than the DIM action soon followed by total display OFF.
The typical Android time out sequence. By the screen recorder the dim is not optimally displayed. In real direct screen view is observable nicely. Compare with display OFF by Locus Pro: Is immediately without dim action.
All next turn alerts notice always the same sequence. (I did not record the turn instruction sound).
Need other app than the Locus active one ?  For example Geocaching app =  asks the PIN.

Video: https://youtu.be/2yHtJBKCZDo
Settings: See picture. (login to the forum)
Title: Re: Screen locked with PIN when navigation
Post by: jonny.blue on July 24, 2020, 21:28:54
Quote
I tested....

Looks pretty good ... I'll check it with the next outdoor trip.


Quote
Need other app than
No I don't use the Geocaching App ... I meant the Locus build in functions.
Title: Re: Screen locked with PIN when navigation
Post by: jonny.blue on July 24, 2020, 21:48:38
Boaahh ... just did a couch test ... and:

My phone doesn't turn off when looking at the display. And at bike it's mounted in front of me ... maybe that caused the problem.🤔

I'll check it next time with 'smart stay - off' ...
Title: Re: Screen locked with PIN when navigation
Post by: jonny.blue on July 25, 2020, 20:59:38
And Ooops 🙄 ... today the field test shows me the real problem.
I have an app running only with car and bike ... and this prevents (since some time🤔) display to turn off.
That's it ... 😐
Title: Re: Screen locked with PIN when navigation
Post by: plu-irin on October 03, 2020, 16:53:36
Hi,

I want to get back to this statement:

QuoteGeneral rule: "The app that turns the display OFF must turn the display ON".

I find this behavior really annoying as I quite often change to other apps when locus is in navigation mode – think of taking photos, web-browsing, messengers, etc.

Since Android P there appears to be an alternative method for apps to lock the screen – https://www.xda-developers.com/android-p-action-lock-screen/ (https://www.xda-developers.com/android-p-action-lock-screen/).

So it seems the rule above is not general anymore and I really would like to see the new method implemented in Locus. What do you think – is it worth to make a feature proposal for this?

Title: Re: Screen locked with PIN when navigation
Post by: Menion on October 05, 2020, 08:20:52
Hi,
thanks for the tip. Seems it should help. The method anyway needs some work because it used the so-called AccessibilityService, I've never used before.

Anyway, idea added to the to-do list, I'll look at it later.