S Pen error message keeps showing in Kiosk LockdownSolved

Participant
Discussion
3 days ago

Hey everyone. I have set up kiosk lockdown in Android devices via the Hexnode portal and it’s working well overall. But for devices using S pen, users are complaining that they are unable to use it properly as they keep getting an error message on the device saying Can’t use air commands. Touch and hold the Recents and Back buttons to unpin app, then try again.”, when they are trying to use the S-pen. Does anyone have any suggestions or workarounds to resolve this issue? 

Replies (3)

Marked SolutionPending Review
Participant
3 days ago
Marked SolutionPending Review

Hi @Roosevelt , I think you can overcome the issue by adding the Settings app (com.android.settings) in Background Apps under android kiosk lockdown in the portal.

Marked SolutionPending Review
Hexnode Expert
3 days ago
Marked SolutionPending Review

Hello @roosevelt , the error message that you are seeing occurs because the device is in the Lock task mode where the S Pen Air commands will not work. To solve this problem, make sure that you have disabled the Lock task mode option in the Peripheral Settings under Android Kiosk Lockdown through the Hexnode UEM portal. As you have already set up the devices in Single App or Multi App Kiosk Lockdown here’s how you can proceed to disable the Lock task mode:

    1. Navigate to the Policies tab in the portal and select your existing policy.
    2. In the policy, select Kiosk Lockdown. Then go to Android Kiosk Lockdown and select Peripheral Settings.
    3. Click on Configure.
    4. Go to the Advanced Lock settings under Peripheral Settings and disable the option Lock task mode.
    5. Go to Policy Targets and click +Add devices to choose the specific devices for this policy. You can also associate it with device groups, users, user groups, or domains.
    6. Finally, click on Save to apply the policy.

 

Marked SolutionPending Review
Participant
3 days ago
Marked SolutionPending Review

Thank you for the help! It’s working fine now.