When Motorcycle Navigation Video Stops: HUD and Offline Maps Explained
Understand navigation video, HUD prompts and route-area maps, including phone and instrument responsibilities, map readiness, position updates and offline-routing limits.
Separate a stopped video stream from an ended navigation session
When motorcycle navigation video stops, an instrument can continue receiving HUD turn prompts if the navigation session and authenticated Wi-Fi business connection remain active. An instrument with a completed route-area map transfer and map rendering support can also display the base map, route and Wi-Fi business-session position. A stopped video stream does not mean navigation has ended, and it does not make every device switch to a map automatically.
In Infinite Ride, the phone owns route planning and navigation data, the SDK connects the phone and instrument, and the manufacturer implements terminal connectivity, decoding and display. Continued map display depends on device capabilities, map readiness, connection state and whether the current location remains inside the cached area.
How do video, HUD and offline maps differ?
| Mode | What the instrument displays | Requirements and limits |
|---|---|---|
| Navigation video | Navigation imagery generated by the phone | Receive video over Wi-Fi, then decode and display it on the instrument |
| HUD prompts | Structured turns, road names and distances | Receive updates over the Wi-Fi business session and render them in the instrument UI; HUD does not include a base map |
| Route-area map | A prepared base map, route and current position | Receive the map over Wi-Fi, then use Wi-Fi business-session positions for display; the entire city is not transferred to the instrument |
Large screens integrate both video and HUD as separate paths. Use HUD alone only when a compact display cannot show video. Map display requires the Core map port and display drivers. Managed exposes route/position events but no basemap storage port. Successful pairing does not establish map support.
What must happen before locking the phone?
Follow the offline-map guide:
- Download published road regions covering the route in the APP under Me → Offline maps.
- Connect to device Wi-Fi before navigation and keep the APP in the foreground.
- Wait for “Device map ready”, then validate lock-screen behavior on the target phone and firmware combination.
Regional road archives stay on the phone. The instrument receives nearby road windows and draws road lines, the planned route and a position arrow. The current vector path needs matching r25 SDK and firmware; it generates no map images and contains no place labels or POIs. Download more regions when leaving local coverage. Validate window updates and location after locking on the target phone.
Do offline maps include offline search and route calculation?
No. This feature caches and displays road geometry; it does not provide offline routing. Destination search, route planning and rerouting remain the responsibility of the phone navigation service. Downloading a road region is therefore not a guarantee of fully offline navigation.
See the map integration documentation for transfer and rendering requirements, and the navigation guide for HUD and end events, and the projection guide for video.
Does navigation audio travel with the picture?
Not automatically with video or HUD. Built-in navigation uses system / A2DP routing. Wi-Fi audio requires separate integration and user authorization, and only captures permitted sources. AMap text callbacks supply no original PCM, and the APP neither embeds TTS nor generates replacement speech. See audio integration.
How should a manufacturer validate navigation?
Test normal video, video-only loss, video recovery, Wi-Fi business disconnection and recovery, stale positions, deviation from the route and explicit navigation end separately.
- When only video stops, do not clear HUD data that remains valid. Devices with a ready map can enter map display.
- When video returns, verify the intended transition back to video.
- Pause position updates when positions expire. Clear maps and positions on navigation end, disconnection or unpairing so old session data does not remain visible.
- When rerouting or leaving the cached area, verify phone-side route updates, map replenishment and device display. An old base map is not proof that the new route is ready.
Use the ESP32-P4 reference project to understand board adaptation, then define acceptance criteria for your own display, wireless hardware and memory resources.
Discuss navigation integration for your instrument hardware.