Draw-Over Permission Missing? Fix the Map Chip from Your PC

Your driver calls from the road: the map chip that floats over Google Maps is missing. They can't see the next stop without switching apps. You try walking them through settings, but the draw-over-other-apps toggle simply isn't there. Some Android phones hide it. That's a dead end over the phone — and it costs you time, calls, and a driver who's now navigating blind.

This article shows you how to fix it from the office PC in a few minutes. No separate ADB install, no developer tools beyond what the phone already has. You'll grant the permission directly, confirm it worked, and send the driver back out.

How it works

The Fix tab uses web USB in your browser to talk to the phone over a cable. Think of it as a direct line from your PC to the phone's permission settings. You plug the phone into the same computer running Chrome or Edge, open Fleet → Fix, and click a button. The browser sends the command that turns on draw-over-other-apps for StopSorted.

It only works when the phone is physically plugged into that PC. You can't do this over the internet to a remote driver. The phone must be on the office desk.

When to use Fix

• The driver app shows a warning about draw over other apps or the map chip.
• The phone's settings won't show a working toggle for StopSorted.
• You have the phone in the office and can plug it into a PC.

Before you start

1. On the phone: Settings → About phone → tap Build number seven times.
2. Settings → Developer options → USB debugging — turn On.
3. Plug the phone into the office PC with a data USB cable (not charge-only).
4. Open Fleet Login → Fix in Chrome or Edge on that PC.

Connect USB

1. On Fix, tap Connect USB.
2. In the browser picker, choose the Android phone.
3. 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

1. Tap Check permission to see the current state.
2. Tap Grant permission — this runs the ADB command for StopSorted.
3. Tap Check permission again — it should report allowed.
4. 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.

What the driver sees vs what you see

Once the permission is granted, the driver opens StopSorted and starts their run. The map chip appears as a small floating bubble on top of Google Maps or Waze. It shows the next stop number and address. The driver taps it to open turn-by-turn directions or the in-app turns. They never need to leave the navigation app to see what's next.

From the office, you see the same run on the live map. You can check progress, arrival times, and proof of delivery as it happens. The Fix tab itself is a one-time setup per handset — once it's done, you won't need it again for that phone.

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.

Worked example

A fleet controller in Sydney gets a call from a driver: "The chip isn't showing over Maps." The driver is already on the road, so the controller asks them to swing by the depot. The driver arrives, hands over the phone, and the controller plugs it into the office PC. They open Chrome, go to Fleet → Fix, and follow the steps. The phone's settings had hidden the draw-over toggle entirely — a common quirk on some Vivo models. Within three minutes, the permission is granted, checked, and confirmed. The driver unplugs, opens the app, and the map chip appears. They leave for the next stop. Before the fix, the driver was stopping to check the app manually, adding minutes to every drop. After, they keep moving and the office sees accurate arrival times.

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 |

FAQ

Can I do this remotely if the driver is on the road? No. The phone must be physically connected to the office PC with a USB cable. Fix does not work over the internet.

Will USB debugging affect normal driving? No. Once the permission is granted, you can leave USB debugging on or turn it off. It doesn't change how the app works on the road.

What if the phone doesn't show the draw-over toggle at all? That's exactly when Fix is needed. Some Android phones hide the toggle. Fix grants the permission directly, bypassing the hidden setting.

Do I need to install anything on the PC? No. Fix runs in Chrome or Edge using web USB. Just make sure you're on a desktop browser that supports it.

Ready to fix it?

If you're already on a fleet plan, head to Fleet Login and open the Fix tab. For step-by-step details, see our guide: Fix phone permissions. Not yet using StopSorted? Start a free account and see how sorted stop order and live maps keep your drivers moving. Check pricing for fleet and solo options, or learn more about how it works.