u/ChrisLawsGolden

This is my gf's BMW, on a lease in the 2nd year with around 30k miles. I'm really puzzled by what's going on here.

I was actually the one driving, when the check engine coolant light came on. I pulled over and checked for a leak but saw nothing. We drove home. The light reset and I didn't see anything the rest of the day.

A couple days later the light came back on and she took it to BMW.

First, they recommended brake service "due to mileage". Why? There's not a single problem with the brake pads (and BMW did not identify a problem other than "mileage"). The brake pad sensor has obviously not been cut through.

Second, they came back and said "so technician saw no coolant leaks and the only thing he is recommending is a coolant flush due to the mileage and coolant was just low."

"No coolant leaks" BUT "coolant was just low".

How? How does the car lose coolant without a leak? If coolant came low from the factory, shouldn't they just top it up to the proper level, charged to the warranty?

They want to charge her $399.95 with coupon for the coolant flush.

What the hell is going on with BMW?

EDIT: got some feedback here and elsewhere.

This looks to be a clear ripoff by this particular dealership. I wasn't really aware that the dealership interests are not aligned with BMW's (the company itself). The reason the service advisor keeps using "due to mileage" is that the car is still under BMW's New Vehicle Limited Warranty for 4 years/50k miles, so any services the dealer wants to charge us for must be framed as either "due to mileage" or customer requested.

The coolant leak itself appears to have at least one service bulletin (SIB 11 10 25 in December 2025).

We'll be taking the car to another dealership.

I've found a defect in the Wi-Fi radio of the 2nd gen Onn 4K Pro (2026 version, internally codenamed jarvis2, model JS620K4).

If you have the Onn 4K Pro V1 box, or your Wi-Fi is slow or not connecting, this is not the same problem. Mine connects fine and sustains 400+ Mbps on Wi-Fi (measured with iperf3).

The defect is easy to miss but simple to describe: every 10–25 minutes, the box's wireless radio silently stops sending data for about 20 seconds, while still showing as "connected" with full bars. Nothing in the interface indicates a problem, and Android's own network logs record no disconnection, because technically there isn't one: the radio stays associated with the router the whole time. But kernel-level traffic counters show data flow collapsing to zero, every active connection through the box freezes simultaneously, and then (roughly 20 seconds later) everything resumes at once, as if nothing happened. The evidence points to a bug in the box's Realtek Wi-Fi driver/firmware: when Android runs a routine background scan for nearby networks, the radio tells the router "I'm going to sleep for a moment, hold my traffic" (a normal power-saving courtesy), and then, if the scan is aborted mid-stream, it sometimes forgets to say "I'm awake." The router, behaving correctly, keeps holding the box's traffic for a phantom sleeper; twenty seconds later an internal recovery timer kicks the radio back to life.

The reason this defect ships without complaint is that mainstream streaming apps are accidentally built to hide it. Netflix, YouTube, and Disney+ keep a minute or more of video pre-loaded, so a 20-second silent gap is simply absorbed, playback never visibly hiccups. But anything that can't buffer past 20 seconds gets hurt: live sports and Twitch streams (which by definition can only buffer a few seconds behind the live broadcast) will freeze and stutter, video calls freeze or drop, and high-bitrate home-media playback (Plex/Kodi/Jellyfin from a local server) can fail outright. Some players interpret the strangled connection as "the file ended" and stop the movie mid-scene. In other words: the better your use case fits the box's marketing (casual streaming apps), the less likely you'll ever see the flaw, and the more likely you'll blame your router or ISP when you do. Every other device on the same network, tested side by side, is unaffected.

Replicating it yourself is straightforward: unlock Developer options, enable Wireless debugging, connect with adb, and pull the logs off the box while streaming something high-bitrate (full trace available upon request).

For what it's worth, I've ordered a Google TV Streamer as the replacement, but this bug notwithstanding, I actually like the Onn 4K Pro more: better remote, HDMI cable included in the box, and a more conveniently designed wall wart. That's what makes the defect a shame.