Remote Control Not Working on Knox DevicesSolved

Participant
Discussion
2 months ago Jan 06, 2026

We’re managing a batch of Samsung Knox devices enrolled using Generic Android enrollment. All of them are running Android 15.

Remote View works fine, we can see the screen without issues. But Remote Control isn’t functioning. We’re unable to interact with the device remotely.

Is there something specific about Android 15 that affects remote control on Knox devices?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
2 months ago Jan 06, 2026
Marked SolutionPending Review

Hey there!

Thank you for reaching out to Hexnode Connect. This behavior aligns with recent platform-level changes introduced with Android 15 on Samsung Knox devices.

For Knox devices, Hexnode relies on the APIs from the Knox SDK to enable remote control functionality within the Remote View application.

Starting with Android 15, Samsung Knox has introduced stricter security controls affecting devices enrolled using Generic enrollment (Device Administrator mode) without Device Owner (DO) or Profile Owner (PO) status. On such devices, access to certain Knox SDK methods is restricted. This includes the RemoteInjection API, which is required for remote control functionality.

As a result:

  • Remote View (screen viewing) continues to work.
  • Remote Control (input injection) is blocked on Generic-enrolled Knox devices running Android 15.

At present, the recommended approach for customers managing Knox devices under Generic enrollment is to use the Remote Assist application to enable remote control functionality.

If remote control is a critical requirement for your deployment model, you may also want to evaluate enrollment methods that grant Device Owner status, as this avoids the SDK restriction introduced at the OS level.

Please let us know if you’d like assistance reviewing your enrollment configuration.

Best Regards,
George
Hexnode UEM

Save