Skip to main content

How to configure an Android phone in kiosk mode with Hexnode

Purpose of this article​

This article guides partners on how to configure an Android phone in kiosk mode with Hexnode for use with the Dersalis App.

Use this guide when the project uses Polar 360 or Polar Verity Sense sensors and the Android phone is provided as a dedicated device for the Dersalis App.

To understand when MDM applies, see MDM Configuration, When Applicable.

Before you start​

Kiosk mode should be used when the Android phone will be dedicated to the Dersalis flow, typically to support:

  • shift start;
  • operator identification;
  • Polar sensor selection;
  • Bluetooth connection with the sensor;
  • data transmission;
  • shift pause or end, when applicable.

In this model, the phone is not the primary sensor. Data collection is done by the Polar sensor. The phone works as the operational interface and connectivity layer.

Responsibilities​

Dersalis uses Hexnode as the MDM for Android phones configured in kiosk mode.

The partner may help with physical preparation and operational validation of the device, but must not change Hexnode policies, profiles, or advanced settings without guidance from Dersalis.

If there's any doubt about permissions, applied policy, kiosk profile, or device behavior, involve Dersalis before delivering the device to the customer.

Official Hexnode reference​

The procedure below adapts Hexnode's use to the Dersalis flow. For additional technical reference, Hexnode's official documentation explains that Single App Kiosk mode restricts the device to a single application and keeps that application in the foreground, even after shutdown or restart.

The official documentation also describes the general path in the Hexnode portal to create an Android Kiosk policy under Policies > Device Policies, selecting the Kiosk type and configuring Kiosk Lockdown > Android Kiosk Lockdown > Single App.

When to use this procedure​

Use this procedure when:

  • the project uses Polar 360 or Polar Verity Sense;
  • the Android phone will be dedicated to the Dersalis App;
  • the device will be used as a kiosk;
  • the customer will not use their own corporate phone;
  • the flow needs to be standardized;
  • the operator should not access other apps or device settings;
  • Dersalis or the partner needs to reduce the risk of unauthorized changes to the phone.

Do not use this procedure for the i.safe Mobile IS-SW1.1 smartwatch. That device has its own screen and connectivity and doesn't rely on an Android phone as an operational interface.

Prerequisites​

Before configuring the phone, confirm:

  • Android phone available;
  • device charged;
  • internet access available;
  • Bluetooth functional;
  • Dersalis App available for installation;
  • Hexnode portal access authorized;
  • Hexnode policy defined or approved by Dersalis;
  • Polar sensor available for testing;
  • operation or customer defined in the project;
  • focal point responsible for validation.

If the phone is the customer's corporate device and is under the customer's own MDM, this article should not be applied directly. In that case, validate the device requirements according to the Phone, Sensor, Wi-Fi, Bluetooth, and GPS Requirements article.

Process overview​

Kiosk mode configuration involves these steps:

  1. physically prepare the phone;
  2. install or make the Dersalis App available;
  3. register or associate the device with Hexnode;
  4. apply the kiosk policy;
  5. restrict the device to the Dersalis App;
  6. validate required permissions;
  7. test the connection with the Polar sensor;
  8. test shift start;
  9. validate data submission to the platform;
  10. confirm the charging, storage, and support routine.

Step 1: prepare the phone​

Before applying MDM or kiosk policy, check the device.

Validate:

  • device turns on correctly;
  • screen works;
  • battery charges;
  • charger available;
  • Wi-Fi or mobile network connection working;
  • Bluetooth working;
  • system with no access blocks;
  • device identified for the project;
  • date, time, and language configured as needed.

If the device shows physical failure, unstable battery, or connectivity issues, do not proceed.

Step 2: make the Dersalis App available​

The Dersalis App must be available on the phone before operational validation.

Confirm:

  • Dersalis App installed or available via defined policy;
  • app opens correctly;
  • app is on the expected version;
  • app accesses the correct environment;
  • initial permissions can be granted;
  • app is not blocked by the system or by MDM policy.

Hexnode's official documentation states that, to configure an app in single-app kiosk mode, the application needs to be installed on the device, except in specific scenarios where a corporate app in Hexnode's repository can be installed automatically before the policy is applied.

Step 3: register or associate the phone with Hexnode​

The phone needs to be registered in the correct Hexnode environment to receive the MDM policy.

The partner must follow the procedure defined by Dersalis for the project.

Validate:

  • phone appears in the Hexnode portal;
  • device name or identification is correct;
  • device is associated with the correct customer, group, or project;
  • device status is active;
  • communication with Hexnode is working;
  • device can receive the policy.

If the phone doesn't appear in the portal or doesn't receive commands, involve Dersalis before proceeding.

Step 4: apply the kiosk mode policy​

The kiosk mode policy must restrict the phone to the Dersalis App.

In Hexnode, this corresponds to using an Android Kiosk policy in single-app mode. The official documentation describes that the policy can be created via Policies > Device Policies > Create/New Policy, choosing Android as the platform and Kiosk as the policy type, then configuring Single App under Android Kiosk Lockdown.

In practice, for the Dersalis flow, the policy must ensure that:

  • the Dersalis App is the main application;
  • the user cannot access other unnecessary apps;
  • the app remains available after restart;
  • critical settings cannot be changed by the operator;
  • the device returns to the Dersalis App when idle or restarted;
  • essential permissions are not blocked.

The policy should only be applied following Dersalis's guidance.

Step 5: associate the policy with the phone​

Once the policy is created or selected, it needs to be associated with the correct device or group.

Hexnode's official documentation describes policy association via Policy Targets, adding devices, or via the Manage > Associate Targets menu for already saved policies.

In the Dersalis flow, confirm:

  • correct policy selected;
  • correct device selected;
  • correct group selected, if applicable;
  • policy applied successfully;
  • device received the policy;
  • Dersalis App entered kiosk mode;
  • user cannot freely exit to other functions.

Step 6: validate essential permissions​

After applying MDM, validate whether the Dersalis App still has the necessary permissions.

Check:

  • Bluetooth active;
  • Bluetooth permission granted;
  • location permission granted when necessary;
  • internet access working;
  • notifications enabled, when applicable;
  • background operation allowed, when applicable;
  • battery saver does not interrupt the app;
  • the app remains operational after screen lock or restart.

The goal is to prevent kiosk mode from blocking resources essential for connecting with Polar sensors.

Step 7: test the connection with the Polar sensor​

With the device in kiosk mode, test with the sensor that will be used in the project.

Validate:

  • Polar sensor charged;
  • sensor turned on;
  • sensor close to the phone;
  • Bluetooth active;
  • Dersalis App open;
  • sensor appears for selection;
  • sensor can be selected;
  • connection remains stable;
  • app is not interrupted by kiosk mode.

If the sensor doesn't appear, check Bluetooth, permissions, sensor charge, and proximity before involving Dersalis.

Step 8: test shift start​

After validating the connection, test the operational flow.

Confirm:

  • operator can start a shift;
  • ID or identifier is accepted, when applicable;
  • correct sensor is selected;
  • shift starts correctly;
  • data starts being transmitted;
  • pause or end works, when applicable;
  • app doesn't close or exit the expected flow;
  • data appears on the platform.

This test must be done before delivering the phone to the customer or using the device in training.

Step 9: test behavior after restart​

Restart the phone and confirm kiosk mode continues working.

Validate:

  • device turns on normally;
  • Dersalis App opens or is available as expected;
  • user cannot access disallowed apps;
  • Bluetooth remains usable;
  • sensor can be connected again;
  • shift can be started;
  • policy remains applied.

Hexnode's official documentation states that, in single-app kiosk mode, the configured app becomes auto-launch and stays in the foreground; it also warns that on Android 10+ devices, three-button navigation may be required instead of gesture navigation.

Step 10: define usage, charging, and storage routine​

Before delivery to the customer, define:

  • where the phone will be kept;
  • who turns on and checks the device;
  • who charges the phone;
  • when charging will happen;
  • where the charger will be kept;
  • who should be called if the app doesn't open;
  • who should be called if the sensor doesn't connect;
  • who can request support;
  • how the device will be stored when not in use.

The kiosk phone should be treated as part of the operation, not as a loose accessory.

Configuration checklist​

Before considering the phone ready, confirm:

  • phone charged;
  • phone identified;
  • Dersalis App installed;
  • phone registered or associated with Hexnode;
  • correct policy applied;
  • kiosk mode active;
  • Dersalis App opens correctly;
  • user doesn't access apps outside the flow;
  • Bluetooth active;
  • permissions granted;
  • connection with Polar sensor tested;
  • shift start tested;
  • data reaching the platform;
  • behavior after restart validated;
  • charging routine defined;
  • usage location defined;
  • focal point briefed.

Common problems​

Dersalis App doesn't open​

Check:

  • whether the app is installed;
  • whether the policy allows the app to open;
  • whether the phone received the correct policy;
  • whether the device is associated with the correct group;
  • whether there was a failure after restart.

Phone doesn't enter kiosk mode​

Check:

  • whether the policy was applied;
  • whether the device is registered in Hexnode;
  • whether the device is in the correct group;
  • whether there's communication with the portal;
  • whether the policy was saved and correctly associated.

Sensor doesn't appear in the Dersalis App​

Check:

  • sensor turned on;
  • sensor charged;
  • sensor close to the phone;
  • Bluetooth active;
  • permissions granted;
  • whether the sensor is trying to connect to another device;
  • whether kiosk mode blocked a permission.

Shift doesn't start​

Check:

  • ID or identifier;
  • connection with sensor;
  • phone connectivity;
  • operation or customer configured;
  • app permissions;
  • whether the app is in the correct environment.

App works before MDM, but fails afterward​

Check:

  • permissions changed by the policy;
  • Bluetooth restrictions;
  • internet restrictions;
  • background operation restrictions;
  • battery saver blocks;
  • applied kiosk policy.

In this case, involve Dersalis to review the policy.

What to avoid​

Avoid:

  • changing Hexnode policies without guidance from Dersalis;
  • applying the policy to the wrong device;
  • delivering the phone without testing with the Polar sensor;
  • validating only that the app opens, without starting a shift;
  • ignoring Bluetooth permissions;
  • using a phone with an unstable battery;
  • leaving the device without a charging routine;
  • releasing the phone to the customer without testing behavior after restart;
  • considering MDM configuration complete without data reaching the platform.

When to involve Dersalis​

Involve Dersalis when:

  • the phone doesn't receive the policy;
  • the Dersalis App doesn't open after MDM is applied;
  • the app works without MDM but fails with MDM;
  • Bluetooth or permissions become blocked;
  • the sensor doesn't connect after basic checks;
  • the shift doesn't start;
  • data doesn't reach the platform;
  • the device exits kiosk mode;
  • there's doubt about Hexnode policy, group, or profile;
  • the partner cannot validate the complete flow.

When contacting Dersalis, send:

  • customer;
  • operation;
  • phone model;
  • Android version;
  • device identification in Hexnode;
  • applied policy;
  • sensor used;
  • description of the problem;
  • screenshots, photos, or videos, if any;
  • steps already tested.

Expected outcome​

At the end of the configuration, the Android phone should be locked in kiosk mode for use with the Dersalis App, with permissions granted, Bluetooth working, connection with the Polar sensor validated, shift tested, and data reaching the platform.

The device should only be delivered to the customer after the full flow — Dersalis App + Polar sensor + platform — has been validated.

Next step​

After configuring the Android phone in kiosk mode with Hexnode, proceed to Technical Checklist Before Customer Delivery to confirm that all technical and operational items are ready before delivery or first use.

Summary​

The Android phone in kiosk mode is used in projects with Polar sensors when the device must be dedicated to the Dersalis App.

Configuration is done with Hexnode, using a kiosk policy to restrict the phone to the Dersalis App. The partner must validate the app, permissions, Bluetooth, sensor connection, shift start, data submission, and behavior after restart before releasing the device for operational use.