Search results

Downgrading to OxygenOS 14 fixed PaaK on my OnePlus 11. A mere factory reset/data wipe and re-install of the Rivian app alone on OxygenOS 15 did not. But the process to downgrade to 14 was a huge pain, requiring not just the data wipe but also a bunch of scouring to find packages on an...

My OnePlus 11 took a major OS update to Android 15 in January, after which point phone-as-a-key has worked maybe only 50% of the time. Cycling Bluetooth always makes it work for a while, but often 15 minutes or so into the drive I'll often get the "Key no longer detected" warning on the driver...

Thanks, I'm running them on my new truck, they're saving wear on the 20s it came with so I'm not in a big rush to get rid of them either. Maybe check in with me in the spring?

Mine can do wifi+hotspot at the same time, but I don't want hotspot always on for other reasons e.g. my other devices connecting to it when I don't want them to, it drains more battery etc.

I have a OnePlus which doesn't have anything like routines natively hence the 3rd party app approach with Automate. I did develop a flow that triggers solely on the Rivian Audio BT device, attached (.flo file in the .zip). But in my case my wife has her own Rivian that I don't want to trigger...

I have an android phone that usually connects to the Rivian Audio device at home even when I am 20+ feet from the car and I don't want the hotspot on then. But the PaaK beacons being above thresholds should be a good trigger.

I've been dabbling on a LlamaLab Automate flow to auto-enable my phone's hotspot whenever signal from some subset of the Rivian's PaaK BLE beacons are strong enough. Making slow progress but wondering if anyone has this working and would be willing to share their work.

Look into keysavvy.com, they will handle your lien for the buyer. https://www.rivianforums.com/forum/threads/keysavvy-is-great-for-private-party-sales.15878/

These are still for sale but I've swapped them onto my new R1T which I expect to drive ~8k miles/year.

I'm interested in trading these for a set of 4 OEM 20" dark AT's, scratches/dings ok and tires can have some wear. Could be willing to travel, especially if you'd meet me halfway.

I appreciate the interest but not yet anyway

Rejoice! https://www.rivianforums.com/forum/threads/interesting-r1-abrp-live-integration-posted-on-riviantracker.29373/

Still available; am also willing to trade for a set of winter tires/wheels

The live data enables features that are useful to me even if the calibrated reference computation isn't reliable. Still, while I'm not spending a lot of time on it at the moment, I'm not giving up on the derivative power approach. The power estimates mine generates seem too noisy/spiky given...

Sorry I forgot the timers, I just pushed a new commit with them.

I moved my code into a gist forked off that original one from earlier in this thread. Basically I have a "R1S Pack Energy template" sensor that multiplies SoC by large pack useful capacity, also multiplied by my wild guess of SoH, plus a wild guess of how much is left if SoC were to reach 0...

I've got a lead. Last night I updated my code to provide an occasional power parameter to the API and also erased all the prior calibration data, and now today I have calibration reference consumption confidence in the 20s and 30s for all 3 speed ranges. The actual consumption number it has so...

My calibrated reference consumption number has gone too high so I filed a bug report: https://abrp.upvoty.com/b/report-a-bug/bad-calibrated-reference-consumption-w-confidence-0-except-for-low-speed

I don't have premium either, but I can still go to My Drives > View All and see data from drives over the last 24 hours. I can't see any drives older than that, and I can't export or save any data -- will get nagged to upgrade to premium if I try. I see the same, the charging power in ABRP is...

I do see the same on that screen, I e. "Low speed" is the only non-zero number. But the speeds and consumptions that show up in drive history seem right, and the reference consumption number it seems to be converging to is basically the same as what the center display gauges app is showing...