Why the app asks for these, and how to fix the common issues · This page grows as we hear from more riders — if yours isn't covered, tell us.
The app checks Location and Bluetooth before every ride, and again every time you come back to it — if either is off, it'll stop you and point you at the fix. Battery optimization is checked too and strongly recommended, but it never blocks you from riding, since not every phone needs it and this app can't always confirm you've fixed it. You can check the status of all three any time in the app: Settings → Permissions.
Why:turn-by-turn navigation needs to know where you are. On Android 11 and below, it's also what makes Bluetooth scanning work at all — the OS treats a Bluetooth scan as a location operation on those versions.
If it's off:the app will show a system prompt asking to allow it. If you've already said "Don't allow" once, Android stops showing that prompt automatically — in that case, open your phone's Settings → Apps → Navrider → Permissions → Location, and set it to "Allow only while using the app".
Location toggle off entirely: a separate system switch from the app permission — pull down your notification shade and check the Location quick-toggle, or Settings → Location.
Why: this is how your phone talks to your Navrider handlebar device — routing directions, speed, and turn-by-turn all travel over this link.
If it's off:turn on Bluetooth from your phone's quick settings or Settings → Bluetooth. If the app says permission is denied, go to Settings → Apps → Navrider → Permissions and allow "Nearby devices".
Connected but not linking to your device:that's usually a pairing issue, not a permission one — see the in-app manual's pairing chapter (Settings → User Manual).
Why:some phones (especially ColorOS, HyperOS/MIUI, FuntouchOS, and similar) aggressively kill apps running in the background to save power — including navigation apps mid-ride. Exempting Navrider from battery optimization, and where available, allowing it to "autostart", keeps your handlebar display alive for the whole ride.
Why we can't just fix this for you:the vendor-specific "autostart"/"app launch" toggle on these phones is a private setting with no public Android API — we can open the settings page for you and give written steps, but we can't confirm from code that you've actually flipped it. The app will keep recommending it if your phone is a known aggressive one, but it will never block you from starting a ride over it.
If your screen goes dark mid-rideeven after setting this: open Settings → Permissions in the app and tap Fix on the battery row — it links straight to your phone's specific settings page where possible.
Optional — used for ride/pairing/firmware-update alerts. Nothing about navigation itself depends on this one; if you skip it, everything else still works.
This page will keep growing as we hear about more phones and edge cases. Tell us what happenedand we'll add it here.