SOTI Pulse Logo

SOTI Agent from Requiring Lock Screen PIN After Reboot

Solved
J
JH

Hi,

We’re experiencing an issue with Zebra devices (TC57x) running Android 14 during a OS update from A11 to A14 and re-enrollment into SOTI MobiControl. To get the device to connect to MobiControl, we’ve had to remove the lock screen PIN before updating. Once the PIN is removed and the lock screen is bypassed, the SOTI agent starts and connects automatically after OS reboot.

However, when the PIN is re-enabled after enrollment, the agent does not start until the user manually unlocks the device. This creates a problem where devices may restart, and users are not always available to unlock them. Is there a known workaround or configuration that allows the SOTI agent to start and connect automatically even when a PIN is set in Android 14? Any advice or experience with similar setups would be greatly appreciated.

Regards

JH

2 months ago
SOTI MobiControl
ANSWERS
RS
Rafael Schäfer
2 months ago

The problem is that the agent needs to have the "direct boot support" included which we requested also several times just because of this issue.

An app does need this to be able to communicate with systems outside of the device when device was rebooted and not yet unlocked (for example the phone app).

Last time we requested this, we got to know that the way the agent is designed, it's not possible to do this. So i don't know if this feature will ever arrive as the possibility in general is there from Google side (and we would like to have it as well).

Solution
K
KKMod
2 months ago

Thank you Rafael for providing the answer and your insights on this query.

Similar Discussions