Volkswagen owners using privacy-focused Android operating systems are finding themselves locked out of key connected car features after recent changes to the company’s mobile app. Drivers running custom Android versions such as GrapheneOS, LineageOS, and /e/OS can no longer use the Volkswagen app to monitor their vehicles or access remote functions.
The change has sparked criticism from users who rely on alternative Android platforms for better privacy and security. While Volkswagen says it is reviewing the issue, the company has made it clear that affected users should not expect a quick solution.
Essential Vehicle Features No Longer Accessible
For many Volkswagen owners, the mobile app is an important extension of the driving experience. It allows drivers to check battery charge levels, view the remaining driving range, schedule service appointments, and remotely control charging or cabin preconditioning.
Following backend changes introduced by Volkswagen, these features are now unavailable on devices that do not include Google’s Play Services. As a result, users of custom Android operating systems have effectively lost access to services that many consider part of the connected vehicle experience.
Google’s Play Integrity API at the Centre
Volkswagen says the issue stems from changes in its software architecture, which now requires Google’s Play Integrity API for authentication.
The Play Integrity API is designed to verify whether an application is running on what Google considers a trusted and uncompromised device. Because privacy-focused operating systems such as GrapheneOS intentionally avoid Google’s proprietary Play Services, they fail this verification despite often offering strong security features.
The move also affects third-party applications and home automation tools that previously connected with Volkswagen vehicles. Developers of software such as Home Assistant integrations and EV charging management platforms have reported losing access after Volkswagen restricted its backend interfaces.
Privacy Community Pushes Back
Developers behind GrapheneOS have strongly criticised Google’s Play Integrity system, arguing that it serves business interests more than genuine device security.
According to the GrapheneOS team, the current verification method excludes secure, independently developed Android operating systems while failing to provide meaningful protection against all security threats. They believe hardware-based attestation would offer a more reliable and platform-neutral alternative.
Their criticism reflects a growing debate over whether companies should require Google’s ecosystem to access services that are otherwise unrelated to Google’s software.
Industry Working on an Alternative
Several European technology companies are already trying to solve the problem.
Murena, the developer of /e/OS, along with Volla, Iodé, and Switzerland-based Apostrophy, is developing a project called UnifiedAttestation. The initiative aims to provide an independent verification framework that would allow secure Google-free Android devices to access apps requiring device attestation.
The group’s immediate focus is banking applications, but the technology could eventually help restore compatibility with connected car services and other apps that currently rely on Google’s verification tools.
Hyundai Shows Another Approach
Volkswagen’s decision stands in contrast to Hyundai and Kia, whose connected vehicle applications continue to work with GrapheneOS. Their approach suggests that secure compatibility with alternative Android operating systems is possible without forcing users into Google’s software ecosystem.
As connected vehicles become increasingly dependent on smartphone apps, manufacturers face growing pressure to balance cybersecurity with customer choice. For Volkswagen owners who deliberately chose privacy-focused Android devices, that balance has yet to be found.
