Phone-key issue after being gone for 3 weeks.

[happyjohn14]

I just got back from a 3-week trip without touching my truck. I opened the app, walked up to the truck and it took a good minute to recognize me and open it. But getting in the truck was even weirder, it wanted me to use one of the cards to start the truck. I hadn't had to do that yet, the last two days have been the same, the phone-key doesn't work like it did in my first month. Was there an update that broke this when I was gone? My guide has been non-responsive lately.

Sponsored

 

[Christopher]

There was an update a few weeks ago and I did notice degraded performance with my key fob and app since that update. Think because they are now putting the truck in what appears to be a deeper sleep, it is causing issues with waking and delays with opening.

At this point I completely abandoned the phone key.

But with all that said, it doesn't make sense on why it forced you to use the key card over the phone.

 

[bd5400]

I had a similar experience about a week ago. It happened the morning after I updated to iOS 15.6.1 (could be a coincidence). I deleted the phone key, re-paired it, and my phone as a key has been working (*knocks on wood*) pretty much perfectly ever since.

 

[PastyPilgrim]

Are you using an Android 13 phone? There was a bug that broke some Bluetooth behaviors that has been fixed in the upcoming September patch.

 

[happyjohn14]

Are you using an Android 13 phone? There was a bug that broke some Bluetooth behaviors that has been fixed in the upcoming September patch.

Yup, Pixel 5 updated to Android 13 when I was gone. I just worked with support and they had me do a number of steps. Ultimately I think the above comments were what fixed it. Delete the phone key, forget all Rivian Bluetooth connections, cycle Bluetooth and NFC, un/reinstall the Rivian app. Enter setup on the phone, and repair Bluetooth. That eventually did it for me. Not sure if all the steps mattered, like the cycling of NFC, but happy that my phone is working again.

 

[PastyPilgrim]

.

Yup, Pixel 5 updated to Android 13 when I was gone. I just worked with support and they had me do a number of steps. Ultimately I think the above comments were what fixed it. Delete the phone key, forget all Rivian Bluetooth connections, cycle Bluetooth and NFC, un/reinstall the Rivian app. Enter setup on the phone, and repair Bluetooth. That eventually did it for me. Not sure if all the steps mattered like the cycling of NFC, but happy that my phone is working again.

Hate to break it to you, but that will work for maybe a day before it stops again.

Here's my thread on it: https://www.rivianforums.com/forum/...he-vehicle-but-cannot-ready-activate-it.7415/

The good news is that the September patch should be pushed to you soon, so keep an eye out.

 

[happyjohn14]

.

Hate to break it to you, but that will work for maybe a day before it stops again.

Here's my thread on it: https://www.rivianforums.com/forum/...he-vehicle-but-cannot-ready-activate-it.7415/

The good news is that the September patch should be pushed to you soon, so keep an eye out.

Yup, it didn't work this morning. PITA.

 

[PastyPilgrim]

Yup, it didn't work this morning. PITA.

Mine continues to work perfectly since the patch, so there's a ray of light right around the corner ?

 

[happyjohn14]

Mine continues to work perfectly since the patch, so there's a ray of light right around the corner ?

After the patch, it worked for a few days. Did the standard rekey setup and it only works for about a day and a half now, until Saturday... I can't even setup my phone as a key now. Opened a ticket with support on it.

 

[ERguy]

Recent Android update seems to be causing issues for some people.

On a side note... What's up with this?

My guide has been non-responsive lately.

There seem to be a lot of guides that ghost their customers after delivery. I recognize Rivian is trying to hire more employees as they grow, but this is an essential part of their customer service model that needs to work well in order for Rivian to have long term success. They need plenty of responsive responsive guides.

 

[happyjohn14]

Recent Android update seems to be causing issues for some people.

On a side note... What's up with this?



There seem to be a lot of guides that ghost their customers after delivery. I recognize Rivian is trying to hire more employees as they grow, but this is an essential part of their customer service model that needs to work well in order for Rivian to have long-term success. They need plenty of responsive responsive guides.

After I complained to my service agent she got back to me and said he was out for the last week with COVID, but I hadn't heard back from her on open issues for 6 weeks, so yes, felt more like ghosting me.

Sponsored