In this article, you will find helpful tips for running the Onfleet mobile app on your device.
While the Onfleet driver app is both iOS and Android compatible and carrier-agnostic, you should become familiar with some of the most common issues that can impact connectivity and performance.
Hardware
For optimal experience, we recommend that drivers invest in the newest model Android/iPhone available, running the latest OS. If that's not possible, minimum hardware requirements are as follows:
iPhone 6 and above (OS version 16+)
iPad 2 and above (OS version 16+)
Newer Android models (OS version 8.0+ running at least 1GHz processor and 1GB RAM)
CDMA vs. GSM Networks
If the driver is using a CDMA network (Sprint, Verizon, etc.), temporary disconnections can occur due to inbound or outbound phone calls. Frequent disconnections can make it difficult for dispatchers to view driver locations, and for Onfleet to accurately calculate estimated arrival times. As this is a characteristic of the network type (voice disconnects the data connection on CDMA), it is difficult to avoid if your drivers make or receive frequent voice calls while on the road.
GSM network providers (AT&T, T-Mobile, etc.) currently support simultaneous data and voice connections. If you know your drivers will be regularly making voice calls, GSM carriers are definitely the preferred option as their data connection will not be compromised.
Additionally, the app can keep operating in areas with low or no service using Offline Assist. Drivers can keep starting and completing tasks during short connectivity gaps, and their activity syncs to Onfleet once a stable connection returns. Learn more in Complete a Task.
Routes with Known Dead Zones
If your routes regularly pass through areas with no coverage (rural roads, remote sites, or underground locations), the default 2-minute offline window may not be enough. Contact Onfleet Support to request an extended offline duration for your organization.
Memory and Battery Life
Older devices, or ones with multiple resource-heavy applications (navigation, messaging, music streaming, etc.) running simultaneously, can experience chronic connectivity and performance disruptions.
To avoid these types of issues we always recommend upgrading driver phones to the latest available OS and ensure they're using the latest version of the Onfleet app. We also recommend closing all non-essential apps. Keeping the device plugged in and charging during use is always best practice, as location tracking software is inherently battery intensive.
If the app freezes, force quit it and relaunch to clear temporary glitches.
Restart your device periodically to clear system memory and improve overall functionality.
If, after reviewing the above troubleshooting guide, your drivers are still having difficulties using the Onfleet mobile application, please advise them to first check for updates to the app in their respective app store. If the issue persists, they should delete the app and reinstall it via this link: