Team LineageOS has stated that the new Android Developer Verification system will not affect users of this firmware. It concerns Android Developer Verification â a mechanism by which applications on certified Android devices must be linked to developers with verified identities.
Google explains the innovation as a fight against malicious APKs and fraudulent schemes. According to the company's plan, starting from September 30, 2026 the verification will begin in Brazil, Indonesia, Singapore, and Thailand, while in 2027 restrictions will gradually expand globally. The regulations will apply not only to applications from Google Play but also to APKs installed from third-party stores or downloaded directly, if the device is a certified Android device with Google Services (Android Developers Blog, Google Help).
For LineageOS, the situation is different. The project emphasizes that it does not provide Google Mobile Services, does not undergo Google certification, and does not include the AndroidDeveloperVerification component through which the new verification should operate. Therefore, regular LineageOS builds will not block the installation of apps from unverified developers (LineageOS).
Even the installation of GApps, according to LineageOS, should not automatically turn the firmware into a Google-managed APK verification system. Developers allow that Google might someday transfer part of the mechanism to Play Services, but in that case, LineageOS intends to disable this feature just as it already disables certain components of Google Play Services updates that are incompatible with the project policy (LineageOS).
At the same time, Google claims that sideloading does not disappear: advanced users will be able to install apps from unverified developers through a special âadvanced flowâ or via ADB. However, this route will become noticeably more complicated: Google describes it as a separate procedure with warnings, checks, and protection against scenarios where a scammer on the phone leads the victim to disable security (Android Developers Blog, Google Help).
This is precisely what has caused discontent among F-Droid, EFF, FSFE, Brave, KDE, and other participants in the Keep Android Open campaign. In an open letter from F-Droid it is stated that mandatory developer registration turns Android from an open platform into a system where app distribution depends on Google's permission. The petition authors Keep Android Open krÀver att den obligatoriska registreringen för tredjepartsdistribution upphÀvs och söker sÀtt att öka sÀkerheten utan att göra Google till den enda kontrollanten av Android-ekosystemet.
KĂ€lla: linux.org.ru
