wildlife R1T
Member
- Joined
- Feb 24, 2025
- Messages
- 46
- Reaction score
- 7
- Rivian
- 2024 R1T
I have been using my Trip B since day 1 to help separate my business and personal mileage. Yesterday morning, I somehow managed to accidentally hit the A/B selector in the gauge view as I was reaching for the reset button right next to it. In typical recovering former Windows user fashion, I tapped the confirm button as I always do, not realizing I'd tapped the A/B button enroute to reset until I saw the large numbers at the bottom and zero miles on the trip.
Sad day...13.5k miles of data was gone.
I know Rivian already added Trip C and Trip D but I'd like to see them add a Lifetime meter that can't be reset easily. I do reset my Trip A every time I charge so I have a record of what I've pulled out of the pack vs what went in to better judge range remaining. I think I just need a software update to get this fixed.
In other news, does anyone have a concrete way to submit either bug info or feature requests to Rivian? I've sent some to my guide before, but as much as they have on their plate that doesn't feel like the right move anymore. For example, I had a nasty phantom braking event about a month ago nowhere near an intersection with someone behind me. Been a while since I've had one that didn't have any obvious trigger and I captured a diagnostic log, but was unsure how to communicate that with Rivian.

I know Rivian already added Trip C and Trip D but I'd like to see them add a Lifetime meter that can't be reset easily. I do reset my Trip A every time I charge so I have a record of what I've pulled out of the pack vs what went in to better judge range remaining. I think I just need a software update to get this fixed.
In other news, does anyone have a concrete way to submit either bug info or feature requests to Rivian? I've sent some to my guide before, but as much as they have on their plate that doesn't feel like the right move anymore. For example, I had a nasty phantom braking event about a month ago nowhere near an intersection with someone behind me. Been a while since I've had one that didn't have any obvious trigger and I captured a diagnostic log, but was unsure how to communicate that with Rivian.