Android app - pls fix PAAK change in latest update

[jimboski93]

Looks like latest update was March 16

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.

Please undo whatever changes you made to the app regarding PAAK

Sponsored

 

[strykerwsu]

No issues on Galaxy 25.

 

[Nixapatfan]

No new issues here just the usual inconsistent wake up delays. I'm not understanding why you need to place the phone on the tray PAAk uses Bluetooth so close proximity should not matter.

Galaxy s22 ultra

 

[R1ship]

Same on Galaxy s25 ultra with gen2 rivian r1s

 

[ebellinder2]

Looks like latest update was March 16

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.

Please undo whatever changes you made to the app regarding PAAK

Agree need to roll back whatever is causing Paak inconsistencies

 

[Muir]

Pixel 9 plus here using digital key using UWB (ultra wide band) instead of Bluetooth and I find it works great. I turned off Bluetooth access in settings since all drivers in our household have UWB capable devices. This setup is 100x better than the old Bluetooth keys.

 

[iamnid]

I'm only occasionally being told to put my phone on the console to start.... But that's been happening for at least a couple weeks now and not only since March 16. Sometimes, it starts if I try to take it out of park without putting the phone there and other times I have to put the phone there . I think it's a bug

 

[SteveInBend]

Pixel 7 Pro. Keep phone in front pants pocket and have had no problems. Only time I have a problem is when I've accidentally turned off Bluetooth.

 

[badger4149]

Looks like latest update was March 16

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.

Please undo whatever changes you made to the app regarding PAAK

I 2nd that request.

 

[HaveBlue]

Check battery and permission revoke settings. Sounds like the app is getting paused. Also you should state vehicle and phone. Appears you have a Gen2 since you said center console

 

[2kwik4u]

Pixel 9 plus here using digital key using UWB (ultra wide band) instead of Bluetooth and I find it works great. I turned off Bluetooth access in settings since all drivers in our household have UWB capable devices. This setup is 100x better than the old Bluetooth keys.

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).

 

[SlaterGS]

Not just Android, been happening on my iPhone for the last 2 updates.

 

[VandalSibs]

Bluetooth behavior is always going to be dependent on both the vehicle and the phone - it's a two-way street after all.

My previous phone was a Pixel 6. PaaK worked about 80% of the time. It also never unlocked my R1T in my detached garage (about 25 feet from the nearest point of the house). I then jumped up to a Pixel 9a, and Paak performance improved right away - I even had to turn of "lock only at nome", because my phone kept unlocking the truck in the garage.

Nothing changed in my behavior between the two phones. Only differences were the phone & their cases (my Pixel 6 was in a harder case than my 9a).

@jimboski93 - what kind of phone do you have, and what case do you have?

 

[2kwik4u]

Bluetooth behavior is always going to be dependent on both the vehicle and the phone - it's a two-way street after all.

My previous phone was a Pixel 6. PaaK worked about 80% of the time. It also never unlocked my R1T in my detached garage (about 25 feet from the nearest point of the house). I then jumped up to a Pixel 9a, and Paak performance improved right away - I even had to turn of "lock only at nome", because my phone kept unlocking the truck in the garage.

Nothing changed in my behavior between the two phones. Only differences were the phone & their cases (my Pixel 6 was in a harder case than my 9a).

@jimboski93 - what kind of phone do you have, and what case do you have?

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?

Sponsored