Many BMW riders want to use a RiderNav Display (R7M/R7X) for CarPlay or Android Auto, while keeping their phone connected to the BMW TFT to use BMW Motorrad Connected / ConnectedRide app features.
Please note: running these connections at the same time can cause unexpected conflicts. This is not a RiderNav-specific issue—it's usually caused by how your phone and Bluetooth system prioritize multiple simultaneous audio/control connections.
Why This Happens
To use CarPlay / Android Auto on RiderNav, your phone must connect to the RiderNav Display.
At the same time, BMW TFT also wants a phone connection (Bluetooth) to enable ConnectedRide-related functions.
On Android Auto, it gets even more complex because your helmet headset/intercom usually must connect to the phone for audio/mic. When your phone is trying to manage RiderNav + BMW TFT + headset simultaneously, the system may re-route audio, change profiles, or drop functions.
Common Issues You May See
When your phone is connected to RiderNav + BMW TFT (and on Android, also a headset), you may experience:
Siri / Google Assistant not responding or failing to activate
Audio routing problems (music, calls, or navigation prompts going to the wrong device)
Mic input issues (others can’t hear you, or voice assistant can’t hear you)
BMW TFT information becoming incomplete or inconsistent
Random disconnects or unstable CarPlay / Android Auto sessions
No official workaround
There is currently no official RiderNav step-by-step process or official workaround for using the RiderNav Display and the BMW TFT connection at the same time. The points above explain why conflicts can happen.