BT connection no longer works after May update

[bmehling]

Error on Pixel8 BT connection for Rivian Audio: "problem connecting to device. turn device off & back on". G2 R1S. The symptom is no audio, no phone control, etc.

Anyone else facing this issue?

I've:
- unpaired, repaired multiple times*
- reset the phone
- reset infotainment a couple of times
- reset the truck once

I've done the unpair/pair cycle 10+ times between and after the resets.

* The pairing process works perfectly, no issues. But once Rivian Audio is connected, the error message above appears on the phone's BT setting.

fwiw, this phone and vehicle have been paired and working fine for 1+ years previous to the May update.

Thanks

Sponsored

 

[VSG]

I updated my R1T last week - no issues with the Bluetooth. I just tried a phone call and playing music, both worked. Maybe try a soft reset to see if that fixes the issue.

 

[SteveInBend]

Have you tried deleting all your Rivian devices from your phone and retrying the repairing process?

 

[bmehling]

Have you tried deleting all your Rivian devices from your phone and retrying the repairing process?

Hmm, good question. I looked and only see Rivian Audio. I think the other BT connection went away when they released the "digital key" update. I don't see any other Rivian connections. Thank you for the suggestion.

 

[Dasoss]

Hmm, good question. I looked and only see Rivian Audio. I think the other BT connection went away when they released the "digital key" update. I don't see any other Rivian connections. Thank you for the suggestion.

Setting up UBW for the phone key disables the Bluetooth phone connection. Check to see if your phonr has UWB capability. If you perchance have a Samsung phone, there is a known bug in Samsung Wallet that causes problems. UWB services are managed by Samung⁷Wallet. Turn in a service ticket.

 

[bmehling]

Setting up UBW for the phone key disables the Bluetooth phone connection.

Thank you -- The Pixel 8 is UWB compatible (UWB since the P6).

The digital key has been set up and working since whatever OTA shipped the digital key feature (and is still working now).

I *think* the set up process back then removed the other BT connection. I noted that in response to Steve's suggestion to delete other Rivian BT connections and reconnect -- I only have the one Rivian Audio BT connection at this point (which I've deleted / reset many times w/out any luck).

Seems like this is a one off issue, so I'll put in a service ticket. Thank you.

 

[bmehling]

Okay -- this has been resolved. Definitely could be considered user error. I'm documenting it here because it was a little non-obvious (to this idiot).

tl;dr: Someone had changed the source in the Music app to Radio w/out me knowing. The source needs to set to BT for BT audio to play.

Long update: I received and took a call in my Rivian even though the BT connection on my Android Pixel said "problem connecting to device. turn device off & back on". The fact the connection said it wasn't working, but was (at least partially) working encouraged me dig around. I didn't have to look far. The Music app was set to Radio.

The moment I switched the Rivian to BT as the source, the error disappeared (and I could play media from my phone). The moment I switched it to another source (e.g., Spotify), the error reappeared on the phone.

Hopefully this helps some future soul.

 

[jrproli]

I'm having issues with my phone, talking basic phone calls. Everyone complains about getting an echo whe i connect to the car.

 

[Weck]

Okay -- this has been resolved. Definitely could be considered user error. I'm documenting it here because it was a little non-obvious (to this idiot).

tl;dr: Someone had changed the source in the Music app to Radio w/out me knowing. The source needs to set to BT for BT audio to play.

Long update: I received and took a call in my Rivian even though the BT connection on my Android Pixel said "problem connecting to device. turn device off & back on". The fact the connection said it wasn't working, but was (at least partially) working encouraged me dig around. I didn't have to look far. The Music app was set to Radio.

The moment I switched the Rivian to BT as the source, the error disappeared (and I could play media from my phone). The moment I switched it to another source (e.g., Spotify), the error reappeared on the phone.

Hopefully this helps some future soul.

What do you mean by Music app? The audio source in the truck?

I'm having this exact same issue again (had it before and a forget/repair and restart on both sides got it working), but that's not fixing it this time. Assistant can't read my contacts or do texts at the moment, I haven't tried a phone call yet but doubt that will work either.

 

[bmehling]

What do you mean by Music app? The audio source in the truck?

Exactly -- in may case, I went into the Music App (I don't know if it's officially called that, but the icon is a music note). The selected source was Radio. I switched it to BT and (a) audio from my device started playing through the Riv's speakers and (b) the error message in the Android BT settings panel disappeared. I tested again -- changing the source to Spotify -- and the BT error immediately appeared (and audio stopped).

In my situation, I think it was just before the Assistant update.

Is it only the msgs and contacts? Does audio work if you play something from your phone? Can you take calls?

Perhaps you've not allowed the phone to share contacts/messages during the BT pairing process?

 

[Weck]

Exactly -- in may case, I went into the Music App (I don't know if it's officially called that, but the icon is a music note). The selected source was Radio. I switched it to BT and (a) audio from my device started playing through the Riv's speakers and (b) the error message in the Android BT settings panel disappeared. I tested again -- changing the source to Spotify -- and the BT error immediately appeared (and audio stopped).

In my situation, I think it was just before the Assistant update.

Is it only the msgs and contacts? Does audio work if you play something from your phone? Can you take calls?

Perhaps you've not allowed the phone to share contacts/messages during the BT pairing process?

It was working fine last weekend, including calls and texts, all the toggles on both ends are checked. When it pairs, it shows "connected" for a few moments, then shows the error message on the connected device list on my phone, but the truck still shows the connected checkmark.

I've never streamed off my phone, but I wonder if switching to bt as the audio source might get the connection working again.

 

[bmehling]

@Weck

I definitely had the experience of the "connected" checkmark on the Riv side.

Something is reminding me there were additional Rivian side settings to get messaging working right. I wonder if you can completely reset the connections (forget/re-add) on both sides that would prompt you to "allow" those permissions again?

 

[Weck]

@Weck

I definitely had the experience of the "connected" checkmark on the Riv side.

Something is reminding me there were additional Rivian side settings to get messaging working right. I wonder if you can completely reset the connections (forget/re-add) on both sides that would prompt you to "allow" those permissions again?

I recall a reset was an option on the Rivian side last time, but I couldn't find the option this time. I already did the forget/re pairing both ends. I'll try another soft infotainment reset tomorrow.

FWIW I still get a "Bluetooth key has been added" notification in the Rivian app after each OTA update, despite both my phone and my wife's phone having digital UWB keys in the wallet, so I must have some residual profile junk somewhere...

 

[Weck]

Aaand... When I got in the truck this morning text integration was magically working again. I had done nothing other than letting the truck go to sleep overnight.

Sponsored