Home
General
Why does the screen remain always on when Lock Task Mode is activated?

Why does the screen remain always on when Lock Task Mode is activated?Solved

Participant

2 days ago

Hi team,

I’ve recently enabled lock task mode through policy because I wanted to disable the navigation bars on the device. After doing this, I noticed something odd…whenever I tap the power button, the screen automatically turns back on. It feels like the device isn’t respecting the usual sleep behaviour.

I double-checked the settings to make sure nothing else was interfering. The “Keep screen on” option isn’t enabled, and the screen timeout is set to five minutes. I even tried restarting the device and reapplying the policy, but the behaviour hasn’t changed at all.

Has anyone else come across this issue or found a workaround?

Replies (5)

Marked SolutionPending Review

remy-parker

Participant

1 day ago

Marked SolutionPending Review

Yeah, I’ve seen that happen. Lock task mode can behave differently depending on the device model. Mine also wakes up with button presses even though the timeout is set. At first, I thought it was a bug.

Marked SolutionPending Review

amelia-smith

Participant

1 day ago

Marked SolutionPending Review

Same here. I tested on Sonim units and the screen wakes up no matter what. Didn’t matter if the timeout was two minutes or ten. I suspected it had something to do with remote sessions but wasn’t sure.

Marked SolutionPending Review

mary_romero

Hexnode Expert

1 day ago

Marked SolutionPending Review

Hi @aitana , thanks for reporting this!

From what you’ve described, the behavior seems to be what happens when a remote session is active. The device awakens once a session starts. It is allowed to enter sleep mode only when the session ends or when the unattended remote policy is removed. After the session ends, the Remote View app sends a broadcast to the Hexnode app, which then allows the device to enter sleep mode.

This feature was introduced in the latest version of the Hexnode Remote Assist app. Previously, if the device was locked, remote control wasn’t possible until it was turned on.

Marked SolutionPending Review

yuudai

Participant

1 day ago

Marked SolutionPending Review

That makes sense now. I thought my timeout settings were being ignored. I’ll check if it still happens after the session ends and let you know.

Marked SolutionPending Review

akemi

Participant

1 day ago

Marked SolutionPending Review

Honestly, I like the change. Before, remote sessions would just die if the device was locked. Now at least it stays controllable. But yeah, I get why customers might think it’s a bug if they don’t know about the new flow.