Phone-as-key PAAK issues

[trmaier]

Currently Pixel 7a. Also had the same issue on the Pixel 6a.

I have tried all of the tricks I googled from clearing caches, resetting networks (ie removing all Bluetooth devices), various developer options, including some adb commands related to Bluetooth. I may have also done a full factory reset (but don't recall for sure).

I do suspect it is a Bluetooth stack issue rather than a "Rivian" issue. I like the Pixel phones, but my next phone will probably be a different android brand. I am just afraid the issue is just me though, given I don't see a lot of people complaining about it and whatever phone I pick (iPhone is not an option) will exhibit the same behavior.

I definitely think you are right about a Bluetooth issue and not a "Rivian" issue, as I experienced similar problems with PAAK with both the R1T and Mach-e. Sorry to hear about your issues with the Pixel phones. I've had great luck with them (with the exception of this PAAK!) and am on my 4th iteration. Will probably upgrade to the 9 at some point in the near future. And then hold my breath that my PAAK trick still works for me :-D

Sponsored

 

[s0ysauce]

Yeah I think that's something with the Pixel specific phones. I daily a Sony Xperia phone and have no issues using it as PAAK. Even using an older Samsung Note 20 Ultra or Samsung Flip phone on occasion doesn't yield any issues.

 

[dduffey]

I had a 6a (wife still does), I upgraded to the 7a specifically hoping the PaaK worked . Fool me once ...

 

[trmaier]

I had a 6a (wife still does), I upgraded to the 7a specifically hoping the PaaK worked . Fool me once ...

That's a real bummer! I wonder if there are any bluetooth hardwear differences between the 6a and 6 pro?

 

[trmaier]

FWIW I am having the same issues on my Gen 2 and it’s really frustrating. SC has no solve. Basically I had to plead with them to get me a key fob. They said they’ll have them available in Oct and I am “first in line”. Not being able to unlock the vehicle reliably with 2 kids under 4 will really test your patience and make you despise an otherwise pretty great vehicle…

I think it's crazy that they stopped including the key fob with new R1 Gen 2s! Particularly since the carabiner-style key fob was originally featured prominently in all the advertising for the R1's. Sorry to hear about your problems!

 

[Gyrosntzatziki]

I think it's crazy that they stopped including the key fob with new R1 Gen 2s! Particularly since the carabiner-style key fob was originally featured prominently in all the advertising for the R1's. Sorry to hear about your problems!

Couldn't agree more. Thought it was a great branding element of the Rivian. TBH I had no idea the Gen 2's didn't have one / when I went to pick up my car at the SC the rep there initially thought they lost my car key until someone told him they Gen 2's don't come with it...

 

[Beachbum]

Since the latest update (.27), while at home, the R1T will now automatically unlock/lock as I approach/leave the vehicle despite selecting the appropriate setting to only lock at home.

Anyone else have this issue post update? Any resolution?

Thank you!

 

[mpshizzle]

I miss the touch to unlock keyless entry door handle on my 8 year old F-150.

Gen 2 DOES have this feature and it was enabled by the last update. That's what the little dimple is for on the driver's door handle. Whether this feature is actually working and bug free is a different discussion

 

[s0ysauce]

That and the wrist band key. They pivoted from, no supply to coming soon at Gear Shop and then Launch Edition only. I know they have them in stock, because they always ask me if I have a launch edition vehicle before saying no.

I think it's crazy that they stopped including the key fob with new R1 Gen 2s! Particularly since the carabiner-style key fob was originally featured prominently in all the advertising for the R1's. Sorry to hear about your problems!

 

[samharden]

Really glad I found this thread after wondering if it was just me and my Pixel 7a. I have a 22 R1T Adventure and have had a hell of a time with the PAAK on the Pixel 7a. Currently trying the phone dev mode trick, but it hasn't solved it all the way. The truck seems to just forget that my phone is present after an hour or so. I like having a key fob, just wish an extra was cheaper...(or maybe 3rd party sellers can pair one?)

 

[Gyrosntzatziki]

Gen 2 DOES have this feature and it was enabled by the last update. That's what the little dimple is for on the driver's door handle. Whether this feature is actually working and bug free is a different discussion

Yes, but it only unlocks the vehicle (when it works) it does not lock the vehicle. And proximiy locking must be turned off. Why, I have no idea. So the only way to lock your vehicle would be to go through the app...

 

[Cycliste]

I’ve noticed that if I have a delay, tapping the phone while in my pocket makes it work. I think that wakes it as if you were going to use it.

Like this?

 

[XLR8R]

Okay, I was about to post on this exact topic in a new thread, when I stumbled onto this. I *think* I may have an answer (after almost a year of looking and almost two years of ownership). I had the same finicky response with my R1T as to the lock/unlock as you approach and the dreaded 'no key detected' message that would show up at what seemed random intervals, only to have to restart my Pixel 6 Pro and have it magically detected by my R1T.

What clued me into my potential answer was for the very same "no key detected" problem to occur on my wife's new Mach-e. Thus set me to the internet, looking through multiple forums, until I stumbled onto a post in a Polestar forum. This person was describing the same PAAK problem happening to them, their Polestar 2 and their Pixel 7. They were lead to believe it was a Bluetooth LE problem, as some have metioned, but they fould the following Google Pixel forum post:

support.google.com/pixelphone/thread/203735099/bluetooth-devices-keep-disappearing-on-pixel-7-pro?hl=en

The problem in this post was solved by disabling Bluetooth LE Audio hardware offload in developer options in Bluetooth settings.

Not daring to hope, I held me breath as I went into my own Pixel 6 Pro and turned on Developer Options. For your own device, you may need to google how to turn on Developer mode, but for me it was this:

Enable Developer Options

• First go to Settings/About Phone
• At the bottom you will find Build Number, tap it 7 times and a message will appear telling you that you have become a developer (!)

Access Developer Options

• Now go to the new Settings item in Settings/System/Developer Options;
• You will find a large number of options, I repeat: DO NOT TOUCH ANYTHING YOU DO NOT KNOW.

What I turned on was the following (also see screenshot):

Disable Bluetooth LE Audio hardware offload

Again, turn ON the Disable function, kind of weird way to put it...

I then had to restart my phone to enable changes.

I know I am daring all sorts of fates by actually posting this, but it has been almost a month and I have had absolutely NO problems with PAAK. (Ducks and crosses self)

If anything changes, I will let everyone know, but for now, so far, so good!

Apparently, the problem seems to lay in the Bluetooth Low Energy mode, which I'm guessing puts the necessary hand-shake to sleep so that the R1T does not see it. Open to other interpretations.

I hope this helps others out there!

Please share if it does.

I was out of town for a week, but so far this work-around seems to be working well for me. I have only driven a handful of times, but I am happy to report no issues. In fact, I noticed that I am now receiving push notifications that I never received before, like the other night my phone dinged to tell me that the Rivian had completed charging. I did not change any other settings, yet this had NEVER happened before within a year of ownership. I also have not noticed any negative impacts to the phone after changing the settings. As a reminder, I have the Pixel 8 Pro.

 

[trmaier]

I was out of town for a week, but so far this work-around seems to be working well for me. I have only driven a handful of times, but I am happy to report no issues. In fact, I noticed that I am now receiving push notifications that I never received before, like the other night my phone dinged to tell me that the Rivian had completed charging. I did not change any other settings, yet this had NEVER happened before within a year of ownership. I also have not noticed any negative impacts to the phone after changing the settings. As a reminder, I have the Pixel 8 Pro.

Interesting! Glad this is working for you, although it sounds like it's only really working for you and I so far. Come to think of it, I think I am receiving push notifications that I don't remember seeing before (i.e. Rivian has completed charging) as well. Fingers crossed this can work for some others as well!

 

[wtong0830]

FWIW I am having the same issues on my Gen 2 and it’s really frustrating. SC has no solve. Basically I had to plead with them to get me a key fob. They said they’ll have them available in Oct and I am “first in line”. Not being able to unlock the vehicle reliably with 2 kids under 4 will really test your patience and make you despise an otherwise pretty great vehicle…

Especially in the mornings, I have my phone with me, and when I press the door handle, I can start to hear the fan or some other sound, and it feels like the car has been awakened. Then I just stand there like an idiot for 10s, 20s, 30s.... Sometimes the door handle can pop open, and sometimes it can't. I don't know if I have something set up wrong or what..... I'm guessing it might be related to some kind of sleep mode? After the first time I open the door, if I go to the side, the handle will open by itself....

Sponsored