Data roaming disabled after scheduled device restart: use app-level enforcement, not JSON global settings

Android

If your Lenovo M10 or K11 devices go offline after a scheduled restart and don't automatically reconnect, data roaming may be disabled. This article explains why this happens and how to fix it using app-level enforcement.

Why data roaming disables after restart

When you configure data roaming through Blueprint JSON global settings, Android resets this setting to its default value during device restart. On many Lenovo devices—especially those configured for roaming markets—data roaming defaults to disabled. This causes devices to lose connectivity after a nightly restart and remain offline because they cannot restore the setting without already being online.

This issue only affects some devices with the same Blueprint and firmware, depending on carrier configuration and SIM settings on individual devices.

How to fix this

Enforce data roaming at the application level on every app launch. This ensures the setting is restored even after a restart, before your app attempts any connectivity-dependent operations.

1. In your application's startup logic, add a call to enable data roaming before any internet connectivity checks or SDK activation flows. Use the Esper Device SDK's settings API:

   esperDeviceSDK.changeSettings(settings -> {
    settings.setGlobalSetting("data_roaming", "1");
   });

2. Ensure this call executes early in your app's launch sequence, even if the device is offline after restart.
3. Keep your existing Blueprint JSON configuration with "data_roaming": "1" as a secondary enforcement layer. It will apply when the device reconnects and converges with Blueprint settings.
4. After the next scheduled nightly restart, verify that previously affected devices come back online automatically without manual intervention. Check Devices & Groups → [Device Name] → Device Details to confirm the device shows as Online.

If devices still go offline

Collect diagnostic information immediately after the next restart event:

1. Request a bug report from an affected device: Devices & Groups → [Device Name] → Actions → Request Bug Report. For detailed steps, see Collecting device logs.
2. Note the following information:
   • Device IDs (affected and unaffected devices, if applicable)
   • Blueprint name
   • Esper Agent version
   • Device firmware build number
   • SIM card type and carrier for affected devices
3. Contact Esper Support and provide the bug report and information above. Include a comparison of affected vs. unaffected device configurations if you have multiple devices.

Still need help?

If you continue to experience issues or have questions about implementing app-level data roaming enforcement, submit a support ticket.