Volkswagen blocked its own app on GrapheneOS — and the charging data is hostage

What VW actually changed

The story surfaced on the GrapheneOS discussion forum: Volkswagen's app stopped working for users of GrapheneOS, the hardened, de-Googled Android build that runs on Pixel hardware. VW's own answer, quoted in the thread, is blunt:

"Please note that the use of the Volkswagen app is only supported on iOS devices and Android devices with supported operating system versions." — VW support, quoted in the thread

Under the hood, this is a Play Integrity story. Google's attestation API doesn't recognize GrapheneOS as compliant — it isn't a GMS-licensed OS, and Google controls what "passes" — so any app that gates on Play Protect certification will reject it. GrapheneOS clears every meaningful security bar and still fails Google's checkbox.

The API lockdown that killed the community tools

The block isn't limited to the official app. A user who'd built around VW's setup described the wider damage:

"What they did is, they locked their api entirely for anything that is not play protect certified. That means, all the cool stuff that was doable via community-driven projects is now dead in the water. The 'app' they provide is 60% advertisement, 30% features… This also means, that charge control from the cars side is not possible to automate anymore." — an owner who automated charging through Home Assistant

That's the practical loss: scheduling when to charge, when to preheat the cabin — automations people had running through Home Assistant — gone, because the unofficial API got sealed behind the same attestation wall.

The detail that reframes the whole thing

The sharpest observation in the thread isn't about Google or GrapheneOS at all. It's about where the data lives:

"VW blocking third party to access their servers is one thing, the thing that I find shocking is that you need to access VW servers to obtain your charging data while this should be directly available locally from the car." — a longtime forum member with a strong reputation score

That reframes the lockout. The car already knows its own charge state. Routing that fact through a cloud round-trip — then gating the cloud behind Google's certification — turns a local sensor reading into a permissioned service. As the founder of Neocities put it after years of VW ownership: "it's weird that cars have to be connected to the Internet anyways."

"It's not your car anymore"

The thread split between two fixes. One camp wants regulation: not to force VW to support GrapheneOS, but to compel it to publish the API so owners can build their own front end.

"The solution is not to try to shame or force Volkswagen to support GrapheneOS, the solution is to (legally) force them to allow the car to run a custom CarOS, for which the community can write their own app." — a commenter arguing for a legal mandate, not a workaround

The other camp is voting with wallets, and it's not abstract. One shopper described the exact sequence that lost VW a sale:

"Volkswagen brands were at the top of my list… I got an offer from a dealer three weeks ago and was going to order the car, then the API for the community integration got turned off. I decided to hold back… Now this, which ultimately — since I am a GrapheneOS user — makes me completely cancel my plans." — a GrapheneOS user who walked away mid-purchase

Underneath both is a colder summary of where connected cars are heading:

"It's not your car anymore, you're just renting someone else's hardware and access to their restricted platforms." — a commenter on the ownership shift

For a GrapheneOS user shopping for an EV, the rule that emerges is concrete: the question is no longer "does this car drive well," it's "does the manufacturer gate basic telemetry behind Google's attestation." VW just answered that, and at least a handful of buyers in this thread answered back.