I have a few android phones enrolled in Hexnode with a kiosk policy applied. The phone app works fine while the device is unlocked, but once the screen locks, the app seems to disconnect or close. I need this phone app to stay active in the background at all times while in kiosk mode.
After checking the device inventory in the portal, I can see a related package listed under the “Blocked packages” section. What is the correct way to allow this package so it stops getting killed by the kiosk?
16 Views
Hi @mo-chou,
In Android kiosk mode, any background apps or services that are not explicitly allowed by your policy are strictly blocked from running. Since you have already identified the package being blocked, you just need to add it to your Hexnode inventory and whitelist it in your policy.
Here are the steps to allow it:
Once the device syncs the updated policy, the package will no longer be killed when the device locks.
Best regards,
Eden Pierce
Hexnode UEM
Just to clarify step 2, when adding it as an app, does the blocked package name go exactly as-is into the Bundle ID field? I wasn’t sure if I needed to use the Play store app ID or some other identifier.
Hi @mo-chou,
Yes, use the exact package string shown under the “Blocked Packages” section as the Bundle ID. The name you enter for the app itself does not matter; it can be any customized name that helps you easily identify it later in your Hexnode app inventory.
Once it is added to your inventory as a custom app, you will be able to select it from the Local Apps list when configuring your Background Apps.
Best regards,
Eden Pierce
Hexnode UEM
Don't have an account? Sign up
What's new 
