Samsung Android kiosk mode call app disappears after dialingSolved

Participant
Discussion
5 days ago Jul 22, 2026

I have a Samsung Android device running in Hexnode kiosk mode. The Phone app opens and I can dial a number, but as soon as the call starts, the call screen disappears. Because of that, the user cannot get back to the in-call screen to hang up.

I checked the blocked packages list, but it did not seem to show the correct package every time. I also saw an Access Denied message once, but I could not find a matching entry in the blocked packages list afterward. What is the right way to allow the call screen in kiosk mode?

Replies (4)

Marked SolutionPending Review
Hexnode Expert
5 days ago Jul 22, 2026
Marked SolutionPending Review

For Samsung Android devices in kiosk mode, the visible Phone/Dialer app and the in-call interface may be handled by different system packages. If only the dialer is allowed in kiosk, the call can start, but the in-call UI may be blocked, causing the call screen to disappear.

Try the following:

  1. Reproduce the issue on the device so the blocked component is triggered.
  2. In Hexnode, run a Scan Device action.
  3. Go to Manage > select the device > Applications > Blocked Packages.
  4. Look for call-related packages around the time the Access Denied event occurred.
  5. If the required call UI package is not already available as an app in Hexnode, add it manually:
    – Go to Apps.
    – Click + Add Apps.
    – Choose Upload as Bundle ID.
    – Add the Samsung Phone/Dialer package and the Samsung in-call UI package using their bundle IDs.
  6. Open the kiosk policy and go to Kiosk Lockdown > Background Apps.
  7. Add both the Phone/Dialer package and the in-call UI package to Background Apps.
  8. Save the policy and confirm that it is successfully associated with the device from the device Action History.

This allows the supporting call interface to run in the background while the device remains in kiosk mode.

Marked SolutionPending Review
Participant
4 days ago Jul 23, 2026
Marked SolutionPending Review

I was looking for the suggested apps in the normal app list and could not find them. The blocked packages list also seemed inconsistent for me. Does this mean I need to add them manually instead of searching for them like regular apps?

Marked SolutionPending Review
Hexnode Expert
4 days ago Jul 23, 2026
Marked SolutionPending Review

Yes. If the package is not listed as a regular app in the Apps tab, add it using the Bundle ID option.

On Samsung devices, the in-call screen is usually a separate system component from the app used to start the call. That component may not appear as a normal app that you can search and select. Adding it as a Bundle ID makes it available for selection in the kiosk policy.

Also, if the blocked package does not appear immediately, recreate the Access Denied behavior first and then run Scan Device again. The blocked packages list is most useful after the device has recently attempted to open the restricted component.

Marked SolutionPending Review
Participant
4 days ago Jul 23, 2026
Marked SolutionPending Review

Got it. Thanks a lot for the help!

Save