This object is in archive!
Erroneous lock of the locus screen
Closed
1. Launch Locus
2. Enable or check the settings-Control-Screen-Screen Unlock-enabled
3. Turn off the screen with the power button.
4. Turn on the screen with the power button. The screen should turn on, but access to other applications will be blocked.
5. Select any track and enable "track navigation".
The screen starts to quickly switch between the "Locus Screen" and "Graphic Key Input Screen" states. This will continue indefinitely.
Video:
https://drive.google.com/file/d/1Wb9p93EBEwEDgtH1gKc4k82QDMesEd2d/view?usp=drivesdk
The same problem 
Hello,
my colleague Michal also had the exact same issue for a few years and we were not yet able to find out why this happens. What device and Android version do you have? I looked that Michal is the only one with this issue, but seems there is now a bigger reason to find out how to hack this. I'll try to find out more and will inform you here. Thanks.
Menion
Hello,
my colleague Michal also had the exact same issue for a few years and we were not yet able to find out why this happens. What device and Android version do you have? I looked that Michal is the only one with this issue, but seems there is now a bigger reason to find out how to hack this. I'll try to find out more and will inform you here. Thanks.
Menion
Lenovo P2a42, Android 7.0 stock firmware.
The phone is rooted.
This error was present in all earlier versions, at least since 2016. I have suffered from this for a long time, but only now I realized how it occurs.
Lenovo P2a42, Android 7.0 stock firmware.
The phone is rooted.
This error was present in all earlier versions, at least since 2016. I have suffered from this for a long time, but only now I realized how it occurs.
Hello Vyacheslav,
even after two months, with the help of my colleague Michal who has the device with exactly the same issue, I'm unable to find any working solution, sorry. For me, it looks like a problem on certain devices. So the only suggestion is not to use this functionality.
Sorry and thanks for the understanding.
Jiří M. aka Menion
Hello Vyacheslav,
even after two months, with the help of my colleague Michal who has the device with exactly the same issue, I'm unable to find any working solution, sorry. For me, it looks like a problem on certain devices. So the only suggestion is not to use this functionality.
Sorry and thanks for the understanding.
Jiří M. aka Menion
This weekend I took part in a night rogaine that lasted 8 hours. A month before this event, I installed Locus Silver and used this version on rogaine. The error described above constantly haunted me and not only when calculating the route, but also when calling other functions. For example, bringing to a point or calling another mapping application.
Based on your suggestion above, it turns out that I don't need to use Locus? :-) But I strongly disagree with this. :-)
Maybe CatLog can somehow help you find the error? I could reproduce this error, save the Catalog and send it to you.
This weekend I took part in a night rogaine that lasted 8 hours. A month before this event, I installed Locus Silver and used this version on rogaine. The error described above constantly haunted me and not only when calculating the route, but also when calling other functions. For example, bringing to a point or calling another mapping application.
Based on your suggestion above, it turns out that I don't need to use Locus? :-) But I strongly disagree with this. :-)
Maybe CatLog can somehow help you find the error? I could reproduce this error, save the Catalog and send it to you.
I found a workaround for this problem. If you are interested, I will write in more detail.
I found a workaround for this problem. If you are interested, I will write in more detail.
I have the same issue since years (LM3, LM4), so I'm interested in your workaround.
(Huawei Mate 9, Android 7.0)
Best, Lucas
I have the same issue since years (LM3, LM4), so I'm interested in your workaround.
(Huawei Mate 9, Android 7.0)
Best, Lucas
My phone is on Android 7.
I use the phone on the handlebars of the bike and I don't need to lock my phone. But I need to turn off the phone screen to save battery power.
Before using Locus:
1. Go to Phone Settings - Security - Screen Lock Settings and disable the "Power Button Lock".
2. Go to Phone Settings - Screen - Sleep Mode and set the maximum idle time.
After using Locus, you can reset the settings back, these actions do not take much time.
Thus, when using Locus, when the screen is off, the phone will not be locked.
Note:
You need to turn the screen on and off ONLY with the power button.
Using gestures to turn off the Locus screen will lock the phone.
If you use the remote control to turn off the Locus screen, it will lock the phone. (In this case, there is a solution to control the screen using a Tasker.)
I will try using the tasker to automatically change the phone settings when the Locus window is active.
My phone is on Android 7.
I use the phone on the handlebars of the bike and I don't need to lock my phone. But I need to turn off the phone screen to save battery power.
Before using Locus:
1. Go to Phone Settings - Security - Screen Lock Settings and disable the "Power Button Lock".
2. Go to Phone Settings - Screen - Sleep Mode and set the maximum idle time.
After using Locus, you can reset the settings back, these actions do not take much time.
Thus, when using Locus, when the screen is off, the phone will not be locked.
Note:
You need to turn the screen on and off ONLY with the power button.
Using gestures to turn off the Locus screen will lock the phone.
If you use the remote control to turn off the Locus screen, it will lock the phone. (In this case, there is a solution to control the screen using a Tasker.)
I will try using the tasker to automatically change the phone settings when the Locus window is active.
Thank you, Vyacheslav for your explanations.
That's also what I learned - that this issue has something to do with Android's "admin mode" (don't know the correct name) where only Locus is open and all the other apps are locked. This mode is activated as soon as Locus has "display activation" enabled and a) a navigation hint is shown or b) the screen was turned on by gesture.
If I understood correctly, with your workaround you prevent your phone from switching into this "admin mode". This works as long as you don't need the screen switching on with every navigation hint.
Best, Lucas
Thank you, Vyacheslav for your explanations.
That's also what I learned - that this issue has something to do with Android's "admin mode" (don't know the correct name) where only Locus is open and all the other apps are locked. This mode is activated as soon as Locus has "display activation" enabled and a) a navigation hint is shown or b) the screen was turned on by gesture.
If I understood correctly, with your workaround you prevent your phone from switching into this "admin mode". This works as long as you don't need the screen switching on with every navigation hint.
Best, Lucas
Yes. That's right. As soon as the locus turns off the screen itself, the phone will lock immediately.
We need to think about how to get around this with tasker.
Yes. That's right. As soon as the locus turns off the screen itself, the phone will lock immediately.
We need to think about how to get around this with tasker.
The solution is not to use the locus to turn off the screen when driving along the route. It is convenient to do this manually using the remote control button, which sends the power button code to the phone via tasker.
Here is a description for the task setter:
Profile: DisplayTurnOn
Settings: Restore: no
State: Media Button [ Button:Play Held Down:Off Grab:On Stop Event:Off ]
Enter Task: Anon
A1: Run Shell [
Command: input keyevent 26
Timeout (Seconds): 0
Use Root: On ]
The solution is not to use the locus to turn off the screen when driving along the route. It is convenient to do this manually using the remote control button, which sends the power button code to the phone via tasker.
Here is a description for the task setter:
Profile: DisplayTurnOn
Settings: Restore: no
State: Media Button [ Button:Play Held Down:Off Grab:On Stop Event:Off ]
Enter Task: Anon
A1: Run Shell [
Command: input keyevent 26
Timeout (Seconds): 0
Use Root: On ]
Thank you, Vyacheslav!
Thank you, Vyacheslav!
Hi Lucas,
maybe this topic and my latest answer may be interesting for you. Thanks to the friendly push from Vyacheslav, I made an alternative method to turn the screen off. Unfortunately, it does not seem to work 100% reliable behind the desk. Needs a field test ...
Hi Lucas,
maybe this topic and my latest answer may be interesting for you. Thanks to the friendly push from Vyacheslav, I made an alternative method to turn the screen off. Unfortunately, it does not seem to work 100% reliable behind the desk. Needs a field test ...
Replies have been locked on this page!