Android app - pls fix PAAK change in latest update

[VandalSibs]

When you turned off proximity lock on the vehicle, did you turn it off all the way, or did you set it to "lock only"? I did the latter, and I unlock it with the app (home screen widget), get in & drive off. Phone is still detected as a key for putting it into gear.

Sponsored

 

[Muir]

Are you in a 1st gen or 2nd gen truck?

I've been debating on moving to a newer PIixel anyway (I'm on a P5), and this would be a nice additional perk.

I currently don't use my phone for anything other than app access because PaaK is so awful. Fob only (which still isn't great).

gen 2

 

[Muir]

I'm on a Pixel 5 and debating an upgrade.

PaaK was working pretty well for me until we moved to a new house. I had proximity lock OFF at the old house because the truck was in the garage and I didn't care if it was unlocked all night. New house truck is in the driveway and I want proximity lock to work. The problem is, it's unreliable there at best, and I'm unsure why. SO, I disabled proximity lock and used the app. NOW.....Anytime I unlock with the app (or the widget) the key doesn't work. So I have to restart the phone to drive the truck (or use the card). Which calling it an agitation is an understatement.

If I could leave Proximity lock OFF at home, AND not have the phone lose it's "key" every time I unlocked I would be a happy camper. I don't mind manually locking the truck, but the constant loss of key connectivity is terrible.

Any thoughts? I mean, aside from "upgrade your old phone, dummy" to help?

I also have a keyfob and I usually use it as the lock/unlock tool for around my house as I have proximity unlock turned off at home so I can safely keep the car in the driveway. The Keyfob is a very dependable alternative and I like having it just in case I accidently let my phone die on a hike or something far from home.

Everywhere other than home, the phone key with UWB works very well.

 

[2kwik4u]

I also have a keyfob and I usually use it as the lock/unlock tool for around my house as I have proximity unlock turned off at home so I can safely keep the car in the driveway. The Keyfob is a very dependable alternative and I like having it just in case I accidently let my phone die on a hike or something far from home.

Everywhere other than home, the phone key with UWB works very well.

I agree, the fob works pretty reliably on my gen1. The response time is slow, but it always works. The PaaK doesn't' work more often than it does work.

I have proximity lock for the phone disabled in the truck, then the BT permissions disabled in the phone.

Also, fun fact, when the phone connects to the truck, it drops my Garmin watch. Have to re-pair the Garmin to get that connection back. Another reason I'm considering a phone upgrade.

 

[2kwik4u]

When you turned off proximity lock on the vehicle, did you turn it off all the way, or did you set it to "lock only"? I did the latter, and I unlock it with the app (home screen widget), get in & drive off. Phone is still detected as a key for putting it into gear.

I've tried both "lock only" and "off" for the home location.

I've also tried multiple combinations of that setting and turning the fob and phone proximity off to see if the two were "fighting" each other.

So far the most reliable combination is to leave proximity fully on at home, with only the fob enabled. Then to remove BT permissions from the phone. This works like 99% of the time. Have to carry the fob this way, but it's the same as every other car I've owned for the last 25yrs, so doesn't bother me too much.

Still get some wierdness though, like this morning I loaded the little one in the back seat, and as I walked around the back of the truck to get to the drivers door. The truck locked with the fob in my front pants pocket. Had to take the fob out and press the button to "re-unlock" and get it. Never fails, it's in the rain too.

 

[mkhuffman]

Check the permission and battery settings on the Google Wallet. Not the Rivian key, but the wallet app itself.

After I added permissions for nearby devices and location and also changed the Wallet battery setting from Optimize to Unrestricted, my PaaK issues went away. Before I did that, I had the same issues as reported by the OP.

I made a thread about it here:
https://www.rivianforums.com/forum/threads/gen2-paak-failures-solved-w-phone-setting-changes.57040/

Apparently the iPhone does not have similar settings, so it appears iPhone failures are a different cause.

 

[DuncIT]

New behavior is that the phone must be placed in the tray, and it takes like 15 seconds for phone and car to sync. I am hitting the brake multiple times, "no key found", open my phone, open the Rivian app, still nothing, then a few seconds later the key shows up from Google Wallet and the car starts. Awful.

Previously, I would step into the car, maybe phone is in my pocket, step on the brake, good to go.

Are you getting into an unlocked car? Because if it unlocks the car then you should be able to put the phone anywhere you want - it should be ready to drive.

What phone are you using? I have my share of issues in the past, but I'm not experiencing any PAAK problems with my Moto Razr 25 and the current update.

Sponsored