The RiderNav R7M brings wireless Android Auto to your BMW motorcycle on a 7-inch touchscreen. Navigation, music and calls run from your Android phone, and the R7M shows 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, 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 shows Android Auto-compatible apps, including:
Note: The R7M shows your phone's Android Auto interface. It does not run apps on its 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, 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 a 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.
The R7M has no built-in speaker. The audio path depends on which phone platform you use.
With Android Auto, the R7M works as the audio bridge between your phone and your headset:
With Apple CarPlay, the R7M shows only the visual interface. Audio goes directly from your iPhone to your headset over Bluetooth, without passing through the R7M. See our motorcycle display guides for CarPlay setup.
|
|
Android Auto on R7M |
Apple CarPlay on R7M |
|
Screen |
Phone → R7M (Wi-Fi) |
Phone → R7M (Wi-Fi) |
|
Audio path |
Phone → R7M → Headset |
Phone → Headset |
|
Headset pairs with |
R7M |
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. That single connection is enough to hear navigation, music and podcasts.
A dual-channel headset is not required for Android Auto on R7M. 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 for Android Auto audio. Use Channel 2 for a device that needs calls only, or leave it unused.
Insert the R7M into your BMW Navigation Cradle until it clicks, then lock it with your BMW key. Start your motorcycle. The R7M powers on automatically.
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 your BMW TFT display. This is not needed for Android Auto audio.
Once your headset connects to the R7M, 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.
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 have a speaker?
No. In Android Auto mode, the R7M receives audio from your phone and sends it to your Bluetooth headset. It does not play 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, 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 may support only HFP/HSP. These profiles carry calls but not media audio. Pair the R7M with the channel that supports A2DP.
Do I need to pair my headset with my phone?
Not for Android Auto on R7M. Audio reaches your headset through the R7M.
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.
Does R7M need mobile data?
No. It uses your phone's mobile data for maps, streaming and Google Assistant.
Can I install apps on R7M?
No. Apps run on your phone. The R7M 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 on an A2DP channel, and that navigation voice is not muted in the app.
Android Auto won't connect
No audio in the headset
Audio cuts out or lags
Google Assistant does not respond to "Hey Google"
Android Auto disconnects after short stops
8 comments
デイトナの DT-S2 の Device２が A2DP に対応していないことが原因で、音声がDT-S2に出力されないと書きましたが、出力することができました。
R7M のセットアップ項目に音声出力という項目があり、そこで考えすぎた結果の誤りでした。
音声出力で、R7M と DT-S2 をペアリングしなければ良いということだけです（ペアリングしてあれば、削除する。）。
ペアリングするのはスマートホンと DT-S2 だけです。
スマートホンでつくられる画像はアンドロイドオート経由で R7M に伝わり、スマートホンでつくられる音声は直接 DT-S2 に伝わるということです。
直接の方が音声の遅延が生じないのでかえって良いことになるようです。
もし考えすぎなければ、ペアリングしないでそのままこんなことも知らずに使っていたかもしれません。
やはり、DT-S2 の Device２が A2DP に対応していなことが原因と分かりました。
R7M との接続は Device１では可能ですが、Device２では接続できません。
DT-S2側で、「接続されました。」とアナウンスされますが、接続されていません。
ちなみに、BMW TFTディスプレイ でも Device １ は接続できますが、Device ２ は接続できませんでした。
ソロツーリングがメインのため、DT-S2を買いましたが、残念です。
ヘッドセットを買い換えたところ、ナビの音声を聴くことができなくなってしまいました。
マニュアルの Audio routes: Phone → R7M → Bluetooth → Headset という仕組みが全く働きません。
この仕組みが働くならば、ヘッドセットはR7Mのみに接続すれば良いことになりますが、よくわからない状況です。
ヘッドセットは、デイトナのDT-S2ですが、Channel 1: Headset ↔ R7M Display、 Channel 2: Headset ↔ Android Phone という接続ができないようです。
Channel 2 （デイトナではDevice ２）は、R7Mとペアリングはできますが、接続されません。
DT-S2 のDevice １ は HSP/HFP/A2DP/AVRCP のモードが使用できますが、Device ２ は HSP/HFP のモードのみということが原因でしょうか。
ヘッドセットを買い換えたところ、ナビの音声を聴くことができなくなってしまいました。
マニュアルの Audio routes: Phone → R7M → Bluetooth → Headset という仕組みが全く働きません。
この仕組みが働くならば、ヘッドセットはR7Mのみに接続すれば良いことになりますが、よくわからない状況です。
ヘッドセットは、デイトナのDT-S2ですが、Channel 1: Headset ↔ R7M Display、 Channel 2: Headset ↔ Android Phone という接続ができないようです。
Channel 2 （デイトナではDevice ２）は、R7Mとペアリングはできますが、接続されません。
DT-S2 のDevice １ は HSP/HFP/A2DP/AVRCP のモードが使用できますが、Device ２ は HSP/HFP のモードのみということが原因でしょうか。
以前のコメントに追加します。
私のヘッドセットは日本の「デイトナ」の製品で、Dual-Channel に対応しています。
以下の接続を試したところ、うまくいくようです。
１．ヘッドセットは、スマートホンには接続しないで、R7M と BMW TFT/ICC ディスプレイ に接続する。
２．当然ながら Andorid Auto のために、スマートホンと R7M を接続する。
３．BMW Motorrad Connected との連携と BMW TFT でスマートホンのバッテリー残量と電波状況を確認するため、スマートホンと BMW TFT/ICC ディスプレイ を接続する。
（今のところ、Android Auto でのナビゲーション画面では、バッテリー残量と電波状況の表示が小さくて確認しづらいです。）
Leave a comment