Granting Fleetworthy GO (Drivewyze) App Permissions via Esper: Standard vs. Special Permission Limitations

Android

Title: Fleetworthy GO permissions — grant remotely or configure manually

When deploying Fleetworthy GO (Drivewyze) to managed Android devices, most required permissions can be granted remotely through the Esper Console, but the "Display over other apps" permission must be handled separately because Android classifies it as a special permission outside the scope of standard device management policies.

Why this happens

Android divides app permissions into two categories: standard runtime permissions, which device management solutions can grant remotely, and special permissions such as SYSTEM_ALERT_WINDOW ("Display over other apps"), which Android intentionally restricts from being granted through management policies. Fleetworthy GO requires at least one permission from each category, so a mixed approach is necessary.

Grant standard permissions through the Esper Console

Fleetworthy GO requires the following standard permissions, all of which can be granted remotely:

• android.permission.ACCESS_FINE_LOCATION
• android.permission.ACCESS_COARSE_LOCATION
• android.permission.ACCESS_BACKGROUND_LOCATION (Android 10 and later only)
• android.permission.POST_NOTIFICATIONS

1. In the Esper Console, navigate to Devices & Groups → [Device or Group Name] → Apps.
2. Locate Fleetworthy GO in the installed apps list and select it.
3. Select Manage → Permissions.
4. Set each of the four permissions listed above to Allowed. Setting these to Allowed at this level pushes the grant silently to the device without requiring any user interaction.
5. Save the configuration.

Verify: On the device, open Settings → Apps → Fleetworthy GO → Permissions and confirm all four permissions are listed as granted. Changes typically reflect within 2–5 minutes of saving.

Grant the "Display over other apps" permission

The SYSTEM_ALERT_WINDOW permission cannot be granted through the Esper Console's standard permission management. Use one of the following approaches based on your fleet size and device hardware.

Option 1: OEMConfig (recommended for supported devices)

Some manufacturers — including Samsung and Rhino — provide an OEMConfig application that extends device management capabilities to include special permissions.

1. Confirm whether your device manufacturer offers an OEMConfig app that supports SYSTEM_ALERT_WINDOW. Contact your manufacturer's support team if this is unclear.
2. In the Esper Console, navigate to Apps & Configuration → [Your Blueprint] → OEMConfig and open the managed configuration for your OEMConfig app.
3. Locate the special permissions or overlay permissions section and set SYSTEM_ALERT_WINDOW to granted for com.drivewyze.fleetworthygo.
4. Save and push the Blueprint to your target devices or group.

Verify: On the device, open Settings → Apps → Fleetworthy GO → Display over other apps and confirm the toggle is enabled.

Option 2: ADB command (recommended for larger fleets without OEMConfig)

If ADB access is enabled on your devices, this command grants the permission programmatically without requiring manual navigation on each device.

adb shell appops set com.drivewyze.fleetworthygo SYSTEM_ALERT_WINDOW allow

1. Ensure ADB is enabled on the target devices. In the Esper Console, navigate to Devices & Groups → [Device Name] → Settings and confirm ADB access is turned on.
2. Run the command above for each device, or incorporate it into your provisioning or fleet management scripts.

Verify: Launch Fleetworthy GO. The app should display overlays without prompting the user to grant any additional permissions.

Option 3: Manual configuration (small fleets or one-time setup)

1. On the device, open Settings → Apps → Fleetworthy GO.
2. Select Display over other apps and toggle the setting to On.

Verify: The toggle should remain enabled after closing Settings. Launch Fleetworthy GO to confirm overlay functionality works as expected.

Troubleshooting

Background location permission is not applying

ACCESS_BACKGROUND_LOCATION was introduced in Android 10. If your devices are running Android 9 or earlier, this permission does not exist as a separate grant — background location access is included within ACCESS_FINE_LOCATION on older OS versions. Remove ACCESS_BACKGROUND_LOCATION from the permission configuration for any device group running Android 9 or below.

OEMConfig does not show a "Display over other apps" option

Not all OEMConfig implementations include special permission controls. If the option is absent, contact your device manufacturer's support team to confirm whether their OEMConfig version supports SYSTEM_ALERT_WINDOW management. If it does not, use the ADB or manual option above.

If this doesn't resolve it

Before contacting Esper Support, collect the following information to speed up the investigation:

• Device make, model, and Android OS version
• Esper Agent version (visible under Devices & Groups → [Device Name] → Device Info)
• Screenshot of Settings → Apps → Fleetworthy GO → Permissions on the affected device
• The exact permission names showing as denied or missing
• Whether OEMConfig is installed, and if so, the version

Contact Esper Support with this information and reference the device serial number shown in the Esper Console.

Still need help?

If the steps above don't resolve the issue, submit a support ticket with your device model, Android version, Esper Agent version, and a description of what you've already tried — this helps the support team investigate without a follow-up.