The RiderNav R7M and R7X bring wireless Android Auto to your motorcycle on a 7-inch touchscreen. The R7M is designed for compatible BMW motorcycles with factory navigation cradles, while the R7X offers universal mounting for a wide range of motorcycles. Navigation, music and calls run from your Android phone, and both displays show them on a screen built for riding.
Most setup questions come down to one topic: audio. Where does the sound come from, and what does your Bluetooth headset need to connect to? This guide explains how it works on both R7M and R7X, starting with the basics of wireless Android Auto and Bluetooth audio, then moving to a step-by-step setup.
After your Android phone connects wirelessly, the R7M or R7X shows Android Auto-compatible apps, including:
Note: Both R7M and R7X show your phone's Android Auto interface. They do not run apps on their own. App availability depends on your region, Android version and app updates. Check each app's own documentation for Android Auto support.
Text messages: On R7M and R7X, Android Auto does not show SMS notifications or read messages aloud.
Wireless Android Auto uses two radio links at the same time. Each one has a different job.
Bluetooth starts the session. It finds the display, pairs the phone and starts Android Auto. Phone calls are also handled over Bluetooth, using the Hands-Free Profile.
Wi-Fi carries the heavy data. After the Bluetooth handshake, the phone switches to a direct 5 GHz Wi-Fi link with the display. This link carries the screen image, touch input and streaming audio, because Bluetooth alone does not have enough bandwidth for live video.
This is why Google lists a phone with 5 GHz Wi-Fi support as a requirement for wireless Android Auto. Any phone running Android 11 or later supports wireless projection. In the EU, phones must also meet extra regulatory rules to use 5 GHz Wi-Fi in a vehicle, so check with your phone maker if the connection will not start.
In practice, this means both Bluetooth and Wi-Fi must stay on while you ride. Turning off either one ends the Android Auto session.
A Bluetooth headset does not use one single "audio connection." It uses several profiles. Each profile is a standard set of rules for one type of task, defined by the Bluetooth Special Interest Group (SIG).
|
Profile |
What it does |
Direction |
Typical use on a ride |
|
A2DP (Advanced Audio Distribution Profile) |
Streams high-quality stereo or mono audio |
One-way |
Music, podcasts, navigation voice prompts |
|
AVRCP (Audio/Video Remote Control Profile) |
Sends play, pause and skip commands |
Control only |
Media buttons on your headset |
|
HFP (Hands-Free Profile) |
Carries two-way voice |
Two-way |
Phone calls, voice assistant |
|
HSP (Headset Profile) |
Basic two-way voice |
Two-way |
Simple calls on older devices |
The key point: only A2DP carries media audio. The A2DP specification defines how high-quality audio is sent from a source device (the sender) to a sink device (the receiver, such as your headset). If a connection supports only HFP or HSP, you can make calls, but you will not hear music or navigation prompts through it.
Many motorcycle communication systems can connect to two devices at once. These connections are often called Channel 1 and Channel 2, or Device 1 and Device 2.
However, the two channels do not always support the same profiles. On some headsets:
A channel like this can pair with an R7M or R7X display and may even announce "connected." But it cannot receive media audio, so you hear nothing. Before you pair, check your headset manual to see which channel supports A2DP.
Neither R7M nor R7X has a built-in speaker. The audio path depends on which phone platform you use.
With Android Auto, the R7M or R7X works as the audio bridge between your phone and your headset:
With Apple CarPlay, the R7M or R7X shows only the visual interface. Audio goes directly from your iPhone to your headset over Bluetooth, without passing through the display. See our motorcycle display guides for CarPlay setup.
|
|
Android Auto on R7M/R7X |
Apple CarPlay on R7M/R7X |
|
Screen |
Phone → R7M/R7X (Wi-Fi) |
Phone → R7M/R7X (Wi-Fi) |
|
Audio path |
Phone → R7M/R7X → Headset |
Phone → Headset |
|
Headset pairs with |
R7M or R7X |
iPhone |
|
Channel needed |
One channel with A2DP |
One channel with A2DP |
For Android Auto audio, your headset needs one channel that supports A2DP, paired with the R7M or R7X. That single connection is enough to hear navigation, music and podcasts.
A dual-channel headset is not required for Android Auto on either display. A second channel is useful only when you also want to connect another device, such as:
Example: Your headset's Channel 1 supports A2DP, and Channel 2 supports only HFP. Pair Channel 1 with the R7M or R7X for Android Auto audio. Use Channel 2 for a device that needs calls only, or leave it unused.
For R7M (BMW motorcycles):
Insert the R7M into your compatible BMW Navigation Cradle until it clicks, then lock it with your BMW key. Start your motorcycle. The R7M powers on automatically.
For R7X (universal motorcycles):
Install the supplied RiderNav quick-release cradle in a suitable position on your motorcycle and connect the power cable to the motorcycle's electrical system. Attach the R7X securely to the cradle and power it on.
Once powered, both displays are ready for wireless Android Auto setup.
RiderNav is not affiliated with BMW Motorrad. BMW is a trademark of BMW AG.
This step decides whether you hear audio.
If your headset has a second channel, you can pair it with another device, such as an intercom or, for BMW riders, your BMW TFT display. This is not needed for Android Auto audio.
Once your headset connects to the R7M or R7X, you can use Google Assistant during Android Auto sessions. Whether you can wake it by saying "Hey Google" depends on your headset model, not on the R7M or R7X.
Supports the "Hey Google" wake word:
Manual activation only:
Why voice activation can seem inconsistent: When you are stopped with the engine off, your phone's own microphone may hear "Hey Google," even from a tank bag. This can make it seem like the headset triggered it. Once you ride, wind and engine noise make this unreliable. Check with your headset maker before relying on hands-free wake words while riding.
After the first setup, everything reconnects automatically:
RiderNav is not affiliated with BMW Motorrad. BMW is a trademark of BMW AG.
Does the R7M or R7X have a speaker?
No. In Android Auto mode, the R7M or R7X receives audio from your phone and sends it to your Bluetooth headset. Neither display plays sound on its own.
Do I need a dual-channel headset?
Not for Android Auto audio. One channel that supports A2DP, paired with the R7M or R7X, is enough. A second channel is only needed if you want to connect another device at the same time.
My headset says "connected," but I hear nothing. Why?
The channel you paired with the R7M or R7X may support only HFP/HSP. These profiles carry calls but not media audio. Pair the display with the channel that supports A2DP.
Do I need to pair my headset with my phone?
Not for the Android Auto audio route described here. Audio reaches your headset through the R7M or R7X.
Is the audio setup the same with Apple CarPlay?
No. With CarPlay, audio goes directly from the iPhone to your headset. Pair your headset with the iPhone instead of the R7M or R7X.
Does R7M or R7X need mobile data?
No. Both displays use your phone's mobile data for maps, streaming and Google Assistant.
Can I install apps on R7M or R7X?
No. Apps run on your phone. The R7M or R7X shows the Android Auto interface.
The map is on screen, but I hear no voice guidance. Why?
Check that your headset is paired with the R7M or R7X on an A2DP channel, and that navigation voice is not muted in the app.
Learn more about the RiderNav R7M for BMW motorcycles and the RiderNav R7X universal motorcycle display.
9 comments
〇Andorid Auto とヘッドセットの Bluetooth のチャンネルについて RiderNav の説明がわかりにくいので、簡単に説明します。
・ヘッドセットは必ず Dual Channel である必要があります。
・ひとつの Channel が A2DP に対応していれば、もうひとつの Channel は A2DP に対応してなく、HFPかHSPに対応していれば問題ありません。
・A2DP に対している Channel を R7M に接続し、A2DP に対応していない Channel をスマートホンに接続してください。
・スマートホンと R7M の間で Andorid Auto の接続が行われると、画像は Wi-Fi でスマートホンから R7M に送られ、音声はスマートホンから Bluetooth でヘッドセットに送られます。この場合でも、音声はスマートホンから Bluetooth でR7M にも送られています。
・ヘッドセットのふたつの Channel が A2DP に対応していれば、両方の Channel を R7M に接続できます。この場合、音声はスマートホンから Bluetooth で R7M を経由してヘッドセットに送られます。
デイトナの DT-S2 の Device2が A2DP に対応していないことが原因で、音声がDT-S2に出力されないと書きましたが、出力することができました。
R7M のセットアップ項目に音声出力という項目があり、そこで考えすぎた結果の誤りでした。
音声出力で、R7M と DT-S2 をペアリングしなければ良いということだけです(ペアリングしてあれば、削除する。)。
ペアリングするのはスマートホンと DT-S2 だけです。
スマートホンでつくられる画像はアンドロイドオート経由で R7M に伝わり、スマートホンでつくられる音声は直接 DT-S2 に伝わるということです。
直接の方が音声の遅延が生じないのでかえって良いことになるようです。
もし考えすぎなければ、ペアリングしないでそのままこんなことも知らずに使っていたかもしれません。
やはり、DT-S2 の Device2が A2DP に対応していなことが原因と分かりました。
R7M との接続は Device1では可能ですが、Device2では接続できません。
DT-S2側で、「接続されました。」とアナウンスされますが、接続されていません。
ちなみに、BMW TFTディスプレイ でも Device 1 は接続できますが、Device 2 は接続できませんでした。
ソロツーリングがメインのため、DT-S2を買いましたが、残念です。
ヘッドセットを買い換えたところ、ナビの音声を聴くことができなくなってしまいました。
マニュアルの Audio routes: Phone → R7M → Bluetooth → Headset という仕組みが全く働きません。
この仕組みが働くならば、ヘッドセットはR7Mのみに接続すれば良いことになりますが、よくわからない状況です。
ヘッドセットは、デイトナのDT-S2ですが、Channel 1: Headset ↔ R7M Display、 Channel 2: Headset ↔ Android Phone という接続ができないようです。
Channel 2 (デイトナではDevice 2)は、R7Mとペアリングはできますが、接続されません。
DT-S2 のDevice 1 は HSP/HFP/A2DP/AVRCP のモードが使用できますが、Device 2 は HSP/HFP のモードのみということが原因でしょうか。
ヘッドセットを買い換えたところ、ナビの音声を聴くことができなくなってしまいました。
マニュアルの Audio routes: Phone → R7M → Bluetooth → Headset という仕組みが全く働きません。
この仕組みが働くならば、ヘッドセットはR7Mのみに接続すれば良いことになりますが、よくわからない状況です。
ヘッドセットは、デイトナのDT-S2ですが、Channel 1: Headset ↔ R7M Display、 Channel 2: Headset ↔ Android Phone という接続ができないようです。
Channel 2 (デイトナではDevice 2)は、R7Mとペアリングはできますが、接続されません。
DT-S2 のDevice 1 は HSP/HFP/A2DP/AVRCP のモードが使用できますが、Device 2 は HSP/HFP のモードのみということが原因でしょうか。
Leave a comment