Technology1 min read

GrapheneOS, LineageOS, /e/OS and Others Are Now Officially Supported

By · Published by Everything Blog

In short

The unified deployment model verifies Google Play dependencies at runtime before executing calls to Firebase, Play Core, or Play Services. When running on de-Googled devices, applications substitute proprietary utilities with open solutions such as UnifiedPush, framework LocationManager, and Vector MapView. However, developers must account for remaining limitations, as features like Google Play Billing, integrity attestation, and native reviews cannot function on these environments. To ensure long-term stability, continuous integration pipelines are configured to safeguard this alternative operating system support during future updates.

Key points

  • Developers can package a single APK that automatically adapts to both Google and de-Googl…: Developers can package a single APK that automatically adapts to both Google and de-Googled Android environments.
  • Core device features switch to open alternatives like framework LocationManager and Vecto…: Core device features switch to open alternatives like framework LocationManager and Vector MapView when Google Play is absent.
  • The platform compiles native Android Studio components directly into target equivalents a…: The platform compiles native Android Studio components directly into target equivalents across iPhone, desktop, and web environments.

Sources checked by our analysis pipeline: 1

This post is mostly about phones that don’t have Google at all: GrapheneOS, LineageOS, CalyxOS, /e/OS and other Android builds. Codename One now supports them officially. After that, a shorter update on the Android compatibility layer, which runs existing Android apps on iPhone, desktop and the web.

GrapheneOS, LineageOS, CalyxOS and /e/OS

I was a member of Team OS/2. I know what it’s like to use an operating system the big vendors forgot, and to find that half the apps you need just don’t start. People choose GrapheneOS, LineageOS and other AOSP builds for good reasons, usually privacy, and they deserve apps that work. There’s a business case too: when you support a niche operating system its users have learned to live without, you get the most loyal advocates your product will ever have. They notice, they remember, and they tell each other.

Codename One apps mostly worked on these phones before. But mostly isn’t support: call the wrong API and you could hit a failure, or behavior nobody could predict. Now it’s official, with a clear boundary. One APK…

Technology