ADB not detecting Lenovo Android device in kiosk after enabling USB debugging policySolved

Hello,

Thank you for reaching out to Hexnode Connect!

You are running into a common point of confusion regarding how policy restrictions manage USB debugging on Android Enterprise Device Owner devices.

Checking the standard USB Debugging policy checkbox does not forcibly turn on USB debugging on the device. Instead, it merely grants permission—allowing the user to toggle USB debugging on or off from the device’s Settings menu. Because your device is locked in a kiosk profile and the Settings app is inaccessible, the underlying Android OS setting remains off, causing adb devices to fail.

To force USB debugging to remain active on a kiosk-restricted device, you need to use the granular policy controls:

1. Open your Hexnode policy and locate the USB debugging restriction options.
2. Change the selection from Users can Choose to Always On.
3. Save and re-apply the policy to your device.

(Note: If your policy view only provides a single checkbox, the immediate workaround is to temporarily exit kiosk mode on the tablet, open Settings, and enable USB debugging manually before returning to kiosk mode).

Once the Always On setting is enforced by policy, the device will keep USB debugging active in the background, allowing adb devices to recognize your Lenovo tablet while it remains in single-app kiosk mode.

I hope this helps you get your debugging setup working smoothly! Please feel free to reach out if you have any further questions.

Best regards,
George
Hexnode UEM.