The LineageOS team 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 initiative as a way to combat malicious APKs and fraudulent schemes. According to the company's plan, by September 30, 2026 the verification will start in Brazil, Indonesia, Singapore, and Thailand, and by 2027 the restrictions will gradually expand globally. This 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 support).
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, standard LineageOS builds will not block the installation of applications from unverified developers (LineageOS).
Even the installation of GApps, in LineageOS's estimation, should not automatically turn the firmware into a Google managed APK verification system. The developers anticipate that Google might eventually transfer part of the mechanism to Play Services, but in such a case, LineageOS intends to disable this feature just like it already disables certain components of Google Play Services updates that are incompatible with the project's policy (LineageOS).
At the same time, Google asserts that sideloading applications is not going away: advanced users will be able to install applications from unverified developers through a special 'advanced flow' or via ADB. However, this process will become significantly more complex: Google describes it as a separate procedure with warnings, verifications, and protections against scenarios where a scammer calls the victim to disable security (Android Developers Blog, Google support).
This is precisely what has drawn discontent from F-Droid, EFF, FSFE, Brave, KDE, and other participants in the Keep Android Open campaign. In an open letter from F-Droid It is said that the mandatory developer registration is turning Android from an open platform into a system where app distribution depends on Google's permission. The petition authors Keep Android Open demand the cancellation of mandatory registration for third-party distribution and seek ways to enhance security without making Google the sole controller of the Android ecosystem.
Source: linux.org.ru
