Android kiosk closes Mobile Networks settings when enabling data roamingSolved

Participant
Discussion
10 hours ago Oct 14, 2026

Android devices are locked in multi-app kiosk mode. Users need to enable data roaming from Settings > Connections > Mobile Networks, but when they tap Mobile Networks the settings page immediately closes and they are returned to kiosk. What needs to be allowed in Hexnode so users can turn roaming on without exiting kiosk?

Replies (1)

Marked SolutionPending Review
Hexnode Expert
2 hours ago Oct 14, 2026
Marked SolutionPending Review

Yes. For regular technician accounts, 2FA settings can be managed from the assigned technician profile. However, if the account uses the default Super Admin profile, changing or assigning a newly created profile may not affect it.

To update the 2FA setting for the Super Admin profile:

  1. Go to Admin > Technicians and Roles > Profile.
  2. Search for and open Super Admin Profile.
  3. Click Edit.
  4. Locate the 2FA option.
  5. Disable or adjust the 2FA requirement as needed.
  6. Save the profile.

The change applies to technicians associated with the Super Admin profile. If SSO is used for portal login, the same profile settings area can also be used to enforce SSO depending on your configuration.This usually happens when Android kiosk blocks either the Settings app itself or one of the background packages launched by the Mobile Networks screen.

Try the following:

  1. Open the kiosk policy associated with the affected devices.
  2. Go to Kiosk Lockdown > Android Kiosk Lockdown > Multi App Kiosk.
  3. Add the Android Settings package: com.android.settings.
  4. Save the policy and sync it to the devices.
  5. Confirm from the device Action History that the policy association or sync completed successfully.

If Settings opens but Mobile Networks still closes, check whether another package is being blocked:

  1. Go to Manage > Devices and select the affected device.
  2. Run Actions > Scanning & Monitoring > Scan Device.
  3. After the scan completes, open the Applications sub-tab.
  4. Check Blocked packages for entries logged around the time the user tried to open Mobile Networks.
  5. Add the relevant blocked package identifiers to the kiosk policy under Kiosk Lockdown > Android Kiosk Lockdown > Background Apps.

If a blocked package is not listed as an available app, create it from Apps > Add app > With Bundle ID, enter the package name as the bundle ID, and then add it to Background Apps. Sync the policy again after saving.

Regards,

Mary Romero

Save