Fix phone permissions (USB)
Grant draw-over-other-apps from the Fix tab when the phone Settings screen will not.
Some Android phones (especially Vivo and similar) hide the draw over other apps toggle. Without it, the driver cannot use the map chip while Google Maps is open. The Fix tab lets you grant that permission from the office PC — no separate ADB install.
When to use Fix
- The driver app shows a warning about draw over other apps or the map chip.
- Settings on the phone will not show a working toggle for StopSorted.
- You have the phone in the office and can plug it into a PC.
Fix uses web USB ADB in your browser. The phone must be connected to the same computer running Chrome, Edge, or Chromium — it does not work over the internet to a remote driver.
Before you start
- On the phone: Settings → About phone → tap Build number seven times.
- Settings → Developer options → USB debugging — turn On.
- Plug the phone into the office PC with a data USB cable (not charge-only).
- Open Fleet Login → Fix in Chrome or Edge on that PC.
Connect USB
- On Fix, tap Connect USB.
- In the browser picker, choose the Android phone.
- On the phone, tap Allow when asked about USB debugging (tick Always allow if offered).
The status line should show Connected.
Grant draw-over permission
- Tap Check permission to see the current state.
- Tap Grant permission — this runs the ADB command for StopSorted.
- Tap Check permission again — it should report allowed.
- On the phone, open StopSorted → menu → turn on the map chip if needed.
If Grant permission fails, try Open overlay settings on the phone and toggle manually, or Open app settings to confirm the app is installed.
After the fix
- Unplug the phone and send it back on the run.
- USB debugging can stay on; it does not affect normal driving.
- If the driver gets a new phone, repeat onboarding under Devices — Fix is per-handset, not per fleet login.
Troubleshooting
| Problem | What to try | |--------|-------------| | USB picker works, then Access denied | Another program has the cable. Close Android Studio / scrcpy / Cursor device tools, run adb kill-server, unplug and replug, then Connect USB again. On Linux, Snap Chromium often cannot open USB — use Google Chrome. | | No device in the USB picker | Different cable; unlock the phone; revoke USB authorisations in Developer options and reconnect | | WebUSB unavailable | Use Chrome, Edge, or Chromium on desktop over HTTPS — not Safari or Firefox | | “usb is disallowed by permissions policy” | Hard-refresh the page (Ctrl+Shift+R). If it keeps failing, contact support. | | Connect failed | Accept the RSA prompt on the phone; try another USB port | | Grant still not working | Some builds block appops — use Open overlay settings or contact support |
Security: ADB access is limited to phones physically plugged into your PC. Only fleet users with Fix tab access can open this page.