Hi everyone, I’m facing a small issue and wanted to check if anyone has seen this before.
One of our managed Android devices seems kind of “locked” when we try to enable Developer Options. We tapped the Build Number multiple times in Settings like usual, but nothing happens.
Is there something that could be blocking it?
37 Views
Hello @sammyy,
This behavior typically occurs when Developer Mode has been restricted through a device policy in Hexnode UEM.
When the Developer Mode option is disabled in the policy applied to a device, users cannot enable Developer Options from the device setting, even if they tap the Build Number multiple times.
To allow access, you can modify the assigned policy using the following steps:
Once the device receives the updated policy, the user should be able to enable Developer Options normally.
Best Regards,
Chloe Edison
Hexnode UEM
Ahh that explains it. I just checked the policy and yeah, Developer Mode was disabled there. Didn’t realize that would block the Build Number trick entirely.
I enabled it and now it’s working fine. Thanks @chloe_edison !
Yeah, be a bit careful with that. We once enabled Developer Mode for testing on a few devices and forgot to turn it off afterward. One of the users ended up turning on USB debugging and installed a random tool from their laptop that messed with the device configuration.
Nothing catastrophic, but it caused a lot of troubleshooting for our team. 😅
Since then, we only enable it temporarily in Hexnode UEM, finish whatever testing or debugging we need, and then disable it again right away. Saves a lot of headaches later.
Don't have an account? Sign up
