UnsungZero_OldTimeAdMan
Well-Known Member
Whatever it is, you can count on a bazillion complaint threads.
Sponsored
I really can’t understand why this is so problematic to some and not for others. My Phone as Key has worked perfectly 100% of the time since day 1. Literally, I can’t remember a single time I’ve ever had to take my phone out, or even had to wait. It’s been instantaneous and perfect. iPhone 16 Pro and iPhone Air.I'll take Phone as a Key improvements for $100 Alex.
Half the time, I still have to take my phone out of my pocket, open the app and by then the vehicle unlocks (I don't need to click unlock in the app). Otherwise, I can press on the driver's door handle until the end of time with the phone in my pocket and, many times, nothing will happen. iPhone 17 Pro, same issues when I had the 16 Pro since I just upgraded phones a few weeks ago.
Luxury... This feature is in basically standard in every car above $30kAmen. Everyone out here hoping for text messages and launch control...I'd settle for HVAC that doesn't go completely bananas, ignoring my fan speed setting and/or attempting to cook us alive despite being set to Auto 68F. Oh, and would be great if they can throw in automatic heated seats/steering wheel, like basically every luxury car (and even many mainstream brands) has had for the last 10 years.
I don't think it is a charge curve bug. I'll post on your thread why I think that. Regardless, it is an issue isolated to your use case, and not a bug. IMO.I'm hoping this fixes the Max Pack charge curve bug that I uncovered. But I think that may have been too recent to make it into this update.
Context: https://www.rivianforums.com/forum/...-pack-service-has-not-seen-this-before.55431/
Meh. Not excited now.Here's what's coming: https://riviantrackr.com/2026-03/
Hmm. Rivian Service confirmed that it was abnormal behavior and a bug, and that it affected a brand new Max Pack that they took to the RAN alongside mine. They claimed it affected "all Max Packs" (they did not specify generation.) They said senior engineering leadership was aware, and promised a fix in "an upcoming software release", which is why I was posting on this thread.I don't think it is a charge curve bug. I'll post on your thread why I think that. Regardless, it is an issue isolated to your use case, and not a bug. IMO.
I wonder if most people with issues have it in their back pocket. I’ve never had an issue in the 3 years I’ve had my R1S unless my phone is in my back pocket. I do not drive with it in my pocket so 99% of the time it is in my hand or gym bag as I approach and unlocks as I walk up.I really can’t understand why this is so problematic to some and not for others. My Phone as Key has worked perfectly 100% of the time since day 1. Literally, I can’t remember a single time I’ve ever had to take my phone out, or even had to wait. It’s been instantaneous and perfect. iPhone 16 Pro and iPhone Air.
You’re all leaving the app running at all times?
Agreed, not a huge list of new features, just committed development to the existing feature set. Okay, and we get Launch Mode now tooGen 1 R1T Quad owner here:
This is a pretty massive update to be honest. It’s not Rivian Assistant but I’m impressed with the list of enhancements.