This object is in archive! 

The phone locks instead of just turning off the screen.

40° shared this problem 3 years ago
Closed

The locus can turn off/on the screen using gestures or a hardware button, as well as when driving along the route. But in fact, instead of turning off the screen, the phone becomes locked. It seems to me that such an action is excessive and unjustified. In addition, this approach in some cases causes (https://help.locusmap.eu/topic/25680-erroneous-lock-of-the-locus-screen) significant inconvenience when using Locus.


Is it possible to just turn off the screen instead of locking the phone?

Replies (10)

photo
1

I'm a little confused because I can turn off the screen without locking the phone. At the same time, security features are enabled on the phone. I can do it with my own hands by pressing the power button. I can also do this with tasker, and for me that means it can be done from the program.

photo
1

Yes, this is a time delay. And this time delay is set in the phone settings.

Thus, I claim that the functions of turning off the screen and locking the phone are different and independent functions, and they can be used separately.

photo
1

I have turned off the lock of the phone. I have been doing this for 5 years sol. It makes a lot of things easier, even with Locus.

photo
1

If you completely disable the phone lock, banking applications will not work. And it's very inconvenient. In addition, all security settings in banking applications will be cleared. Setting up the security of banking applications is a very time-consuming process.

photo
1

It seemed to me that the solution was very simple. All you have to do is send the code of pressing the power button (26) to the phone, and the screen will either turn off or turn on. This is exactly what I do with tasker when Locus is running. And everything works fine.

photo
1

Hi, Zdeněk informed me about your suggestion with the key event.

Anyway, any idea how to send key events on Android? Because I was able to find out only one solution so far, that requires special system permission INJECT_EVENTS, that is not available for the Locus Map app. I'm surprised if Tasker is able to do this, as it looks to me like a big security hole if any app should without warning send any key events to the whole system.

photo
1

I will probably be able to do this because the phone has ROOT installed.

photo
1

Heh, oki. This is the correct reason :).

photo
1

I can't calm down.:-)

Tasker turns off the display using the "Turn off []" command, and at the same time the phone is NOT locked. And you don't need ROOT to perform this operation.

photo
1

Hmm, thanks. I was digging a little more and found one old hack ... modify system settings to turn the screen off to 1 sec and after a while, return this back. I made this system into the Beta version, so try the next Beta and let me know. This change have to be enabled in the "Expert settings" at the bottom.

photo
1

I am using version 3.55.1

Will these changes happen in the beta version of Locus Pro?

photo
1

There are no Beta versions of the Locus Map Pro, sorry.

photo
1

I opened "https://play.google.com/store/apps/details?id=menion.android.locus ", but there are no updates yet.

photo
2

You tried the release URL, not beta.

Try this one: https://drive.google.com/file/d/13g9p2lHs0sBqwcctrnF0-eqDQbLDbvry/view?usp=drivesdk

Mind, this is Locus 4, not LMP.

photo
1

does not work. the display does not turn off.

photo
1

but... let me remind you I have android 7

photo
1

stop stop stop. don't turn anything off for one second. I've already turned everything off for 30 minutes. maybe that's the problem?

photo
1

I did everything I could. :-(

photo
1

A. I understood how it should work.


And it works like an idea.


But my phone allows you to set a minimum screen shutdown time of 15 seconds. In practice, this is hardly applicable.


Still, let me remind you once again that the Tasker "Turn off" command is executed instantly.


Maybe ask the Tasker developer how this is done programmatically?

photo
1

Hi, I'm looking at this problem a little more. Only a single hack work +- reliable > method is also used by the tasker with a short timeout. It does not matter if your phone supports only 15 sec. The app may over API set even shorter time and this is used here.

I'll let you know if this works when I and users on the forum do some field testing. Anyway, watch the news in the next version. If all went well, this may be an official method that may solve the reported issue.

Menion

photo
1

Thanks. I'm very interested.

Replies have been locked on this page!