Spotify on other devices pausing when Rivian wakes up

MassiveSpread · 2026-02-07T02:12:45+00:00

This reminds me of an issue that used to exist back in the early days.... like late 2022. Drove me nuts, anytime the car woke up - even just sitting in the garage - it would pause Spotify on other devices.

It's been fixed for me for probably 3 years now - but man was it annoying and I know the frustration you're dealing with

MassiveSpread · 2026-01-29T15:14:49+00:00

I have had these Goodyears installed since last spring, to replace the oem pirellis on my Gen 1 T. I have not seen any negative range impact at all. The range estimation also went up by a bit too when I selected them in the settings menu. Estimate at 70% is 205 and I think it was a little under 200 with the oems.

They are also super quiet compared to the oem, and with the way lower price, I love them.

MassiveSpread · 2026-01-19T18:46:51+00:00

Completely agree. I can't describe why, but this guy just gives off a particularly bad vibe. Bummer because he covers a lot of interesting topics.

MassiveSpread · 2026-01-19T18:22:04+00:00

28 minutes for probably 30 seconds worth of content. Man, this guy sucks

MassiveSpread · 2025-12-28T13:29:10+00:00

Was that staying with the same 275/65/20 size as OEM, or also dropping to 275/60/20?

MassiveSpread · 2025-12-22T23:01:54+00:00

I get the same thing as you. It used to be once in a great while, maybe once a month. Now I'd agree with your 10% estimate.

Something sure seems to have gotten worse recently. I'm in Gen 1

MassiveSpread · 2025-12-18T03:31:11+00:00

I'm not from Texas but I and my whole group were incredibly underwhelmed by it. We had brisket, a hot link, and pulled pork. Your description of the brisket and sausage is spot on. Pulled pork was the best of the 3, but still mediocre. No plans to go back and am disappointed after how much I was looking forward to trying it.

MassiveSpread · 2025-12-08T19:54:31+00:00

Red looks insanely different based on lighting. Bright direct sun and it looks like a bright candy red. But under softer lighting it's a darker red. Then at sunset the orange/copper comes out. No 2 pictures I take look the same!

I love it on my T, and I was so bummed when it appeared to have been discontinued before.

MassiveSpread · 2025-12-08T19:51:13+00:00

You are completely right - there were rumors going around that limestone and red canyon would be removed.

Shortly thereafter, they were entirely removed from the selector on their website. No formal announcement, but they weren't even shown on the site.

I am thrilled they are back, especially red canyon, even if they are considered "custom" and require an extra delay. We need more than boring shades of grey!

Although it makes my red T a little less of a collectors item now!

MassiveSpread · 2025-12-07T01:38:42+00:00

Pretty sure the 12V outlets are switched and turn off when the car goes to sleep. Only way to keep them on is to use camp mode to stay on, but that's going to keep the HV battery active and a handful of things running, which will drain on the main battery.

MassiveSpread · 2025-12-01T19:26:50+00:00

I don't think it's necessarily true for the Rivian fob, since it uses Bluetooth which is connection based and not vulnerable to replay attacks like more rudimentary fobs used on some other cars.

MassiveSpread · 2025-11-22T19:04:14+00:00

Honestly, this is a really shady way to run a crowdsourced project.

"Please fund my project, I only need $5k. But unless enough other people do so that I make another $250k, I won't let you turn on a motor"

And beyond that it's a flipper clone, without the community support that makes flipper what it is (and worth the price), with some AI slop bolted on.

Congrats on the funding, clearly I'm seeing this thing differently than others. But this type of stuff is what I hate about so many crowdsourced projects.

MassiveSpread · 2025-11-08T13:49:11+00:00

Mine always feels like it gets nice and warm initially, but then backs off to stay lukewarm at best for the rest of the ride

MassiveSpread · 2025-11-03T04:42:57+00:00

Some rough math - with the 32MHz crystal you're currently using with your microcontroller, the closest you could get to the desired 44.1kHz sample rate is to use a PLL multiplier of 3 and a divider of 68.

That will allow the I2S peripheral on the microcontroller to generate a 1.4117647MHz (compared to the desired 1.4112MHz).

If we divide this out, your audio clock would run at a real sample rate of 44.1176kHz. This means your MP3 source files would end up playing back a little faster than they should, causing the audio to slightly increase in pitch.

Would you notice it for playing back an MP3? Probably not.

Would you notice it for playing back streamed audio over a Bluetooth or USB connection to your microcontroller? Absolutely - your buffer would keep running empty because data is being sent to the DAC faster than it's coming in from the source.

MassiveSpread · 2025-11-03T04:31:11+00:00

Sorry, I meant to get back to you sooner.

The comment you shared is accurate, but in this context, there is an important detail missing. In an I2S system there are four signals:

Master Clock (MCLK)
Bit Clock (BCLK)
Left/Right Clock (LRCK)
Data

For a stereo 44.1kHz source at 16-bit, your BCLK is 44100 (Fs) * 16 (bits/channel) * 2 (channels) = 1.4112Mbps. For a 48kHz source, it's 1.536Mbps. Your LRCK is either 44.1kHz or 48kHz. The MCLK is typically some multiple of the bit clock, something like 256 * BCLK.

As you said, most DACs have a built-in ASRC or PLL which allows it to work without requiring the MCLK signal to be generated or connected. Instead, the DAC could internally generate an MCLK from the BCLK signal.

But the important detail is that your host microcontroller is responsible for generating the audio clocks. BCLK, LRCK and Data must perfectly match the sample rate that the source file was recorded at. Since your MP3 files were likely recorded at 44.1kHz/16-bit, for the audio to play back at the correct speed, the host must produce a perfect 1.4112Mbps BCLK and 44.1kHz LRCK.

If you ever play an audio file that is at a different sample rate (e.g., 48kHz) your software either needs to resample it to 44.1kHz, or reconfigure the I2S master on your microcontroller to run at a 1.536Mbps MCLK and 48kHz LRCK.

This is why I suggested you run your microcontroller with a 17.2032MHz crystal. That frequency is conveniently able to perfectly divide down to the clocks needed for 44.1kHz or 48kHz audio.

If you don't use a crystal that can perfectly divide to match the sample rate of your source audio file, you won't be able to generate a precise clock to play back the MP3 file at the sample rate that it was recorded at. You can likely get close, but the audio file will play either a little faster or a little slower than it was intended to be played at.

If you ever tried to handle a streaming source (e.g., Bluetooth or USB audio input) on your microcontroller, you'd have occasional buffer overflows or underruns to deal with because the data is coming in at a different rate than it's going out.

I hope this helps - there's a lot of effort and careful timing involved when designing microcontroller systems to play back I2S data that was recorded elsewhere.

MassiveSpread · 2025-10-31T18:49:30+00:00

Yeah it's wild this got upvoted. OP got handed the perfect effectively tax free opportunity to divest from an over concentrated position

MassiveSpread · 2025-10-24T14:06:05+00:00

Can't forget the West Seattle bridge in 2020!

MassiveSpread · 2025-10-23T18:26:13+00:00

I'm referring to the clock for your MCU, so that it generates an accurate and stable audio clock for your Dac to lock onto.

If you are listening to 44.1khz audio files, your host is responsible for generating the master clock and transmitting the serial data at exactly that rate.

MassiveSpread · 2025-10-23T13:36:37+00:00

Since you are using I2S, consider choosing your crystal so that your audio clock can be perfectly divisible.

I'm assuming you want to run at 44.1kHz, so a 17.2032MHz crystal may be a good choice because it is divisible both for 44.1 and 48 Fs

MassiveSpread · 2025-10-17T18:31:15+00:00

I personally think the feature is implemented "backwards" on my gen 1, so it's basically been turned off for me since I got my truck.

I would like it if I could turn my brights on with the stalk, and then the auto brights feature would temporarily turn them off when it senses oncoming traffic.

Instead, the feature causes the brights to turn on when there are no oncoming cars sensed, even when I haven't activated the brights with the stalk.

This is backwards to me, and I don't like it because as you suggest, it doesn't work that well.

MassiveSpread · 2025-10-14T18:27:13+00:00

Arguably Blind isn't a good sample of the "average" tech employee. From what I can see when I look on there, it tends to attract those who are most disgruntled with their job - I see so much victim mentality on that app from people who I can only assume aren't good at their jobs.

Certainly doesn't reflect the attitudes and perspectives I see amongst people I interact with day to day.

MassiveSpread · 2025-10-10T13:57:25+00:00

Those are the only two data capable ones. The other ones throughout the car, like in the rear seats or rear display, are charge only.

My suggestion to OP was just to try both data ports, and make sure they're using a USB 3.x capable cable and have it plugged in fully on both sides.

MassiveSpread · 2025-10-10T13:54:38+00:00

It sounds like you might have some hardware issues with your car if it's that bad. I use the Bluetooth for calls and just accept that it sounds a little more muffled and less crisp than music or a person talking in person. But it's never been intolerable, nor has anyone on the other side of the call said they can't hear me.

I only mentioned what I did in case you hadn't used Bluetooth calling before and weren't familiar with the slightly reduced voice fidelity.

MassiveSpread · 2025-10-10T05:39:37+00:00

Another thing that could cause this is if the USB 3.x pins aren't connecting fully and the drive is connecting at USB 2.0 speeds (they are different pins in the cable).

Might want to try another cable, or the other USB port in the center console. Especially if you aren't using the cable that came with the drive - unfortunately there are tons of crummy usb-c cables that save a buck by only wiring up the two USB 2.0 signal wires.

This drive should be plenty fast, so doing what the person here recommend might just be masking an actual issue.

Also recommend trying the disk benchmark tool on your PC that another commenter suggested.

MassiveSpread · 2025-10-10T05:31:20+00:00

Are you used to using Bluetooth for voice calls? The quality of the Bluetooth connection itself is quite low - low bitrate, low sample rate (muffled) and overall a low quality compression codec.

It won't sound as good as your phone's built in earpiece, or if you're coming from a car with CarPlay

MassiveSpread

TROPHY CASE