Search results

I got these errors after the most recent update made my R1T almost undrivable. Support had me restart but that didn't do anything. I was able to make it home which I had only gotten about a block away, then they did a sleep cycle on it. That fixed it for about 36 hours then it popped up again...

Ugh, still hurts that I bought my stock shortly after it was released. What a loss...

Youtube music would be great that shouldn't need to be parked for...

Totally. I am back to using Google Nav on my phone. I had 30 miles of range and was 10 miles from a fast charger, it wanted to detour in the opposite direction and do a precharge when I made it to my primary charger with plenty to spare. Not the first time its done this. Not a fan of the builtin...

I have to park in a pretty tight garage and the beeps tend to be way too sensitive. I'm talking a good 18" from whatever before it starts going crazy and I just need to ignore it as it isn't helping. I know I've come really close around a corner driving 10-15mph and maybe 3" away from another...

Well, I don't know about your area, but the Supercharger stations in the NE corridor are always full, while the EVgo/Electrify America station are half full at the same time. It will be nice having that option, in the end we just need more charging stations everywhere.

Only reason I'd like it separate from a watch is, I like to rock climb, float down rivers, hike. I've bricked my Fitbit doing some of these things, one smack against a rock and the watch is dead. I'd hate that to be my only way in if I wanted to live my phone in the truck, ie, while floating...

So, I hate to say this, but upgrading from the Pixel 5 to Pixel 7 seems to have resolved the issue for me so far. I haven't had to toggle anything since I made the change. :(

This is working for me! Weird, but thanks.

I'll try the airplane mode toggle tomorrow.

I've had a mobile tech out twice to try and figure this out, The devs seem to have given up too. I currently have a Pixel 5, the tech is convinced it's the phone and I need to try another phone. The only way I can get the phone key to work is after "repair"ing and then it only works for about 8...

Good to know. I remember when I was in delivery and the guide recommended I treat it rough, like any truck, and slam everything, which is against my nature normally.

That is good to hear. But 27 for such a huge area and the most densely packed part of the country doesn't sound like much. I'd for sure love to make a road trip up to Vermont or Maine in my R1T, but eh, I really want more reliable networks. Hoping the Telsa network works well for us when it opens.

Sad how underrepresented the NE is, or really most of the map. I'd thought they'd have 10x as many charging stations planned, if not more.

Great updates for sure, but who was asking for Tidal? I've only see YouTube Music, or other options like Pandora to be added.

After I complained to my service agent she got back to me and said he was out for the last week with COVID, but I hadn't heard back from her on open issues for 6 weeks, so yes, felt more like ghosting me.

After the patch, it worked for a few days. Did the standard rekey setup and it only works for about a day and a half now, until Saturday... I can't even setup my phone as a key now. Opened a ticket with support on it.

Yup, it didn't work this morning. PITA. :(

Yup, Pixel 5 updated to Android 13 when I was gone. I just worked with support and they had me do a number of steps. Ultimately I think the above comments were what fixed it. Delete the phone key, forget all Rivian Bluetooth connections, cycle Bluetooth and NFC, un/reinstall the Rivian app...

I just spoke with support, and he explained to me that it's to be expected, primarily because of battery conditioning, and cooling the battery during the summer to increase the life of the battery. Makes sense but his recommendation was to keep it plugged in all the time, as even a 120v outlet...