Overview of GrapheneOS features differentiating it from the Android Open Source Project (AOSP).

Origin

We’ve got some important news to share about changes happening in the Android world that affect all custom ROMs, including iodéOS. Don’t worry – we’re not going anywhere, and we’ve got your back. Let’s break down what’s happening and what it means for our community. ## Google shakes things up (again) Earlier this year, Google made some significant changes to how Android development works. They moved all their development work behind closed doors and stopped providing the technical blueprints that made it easy for custom ROM developers to support Pixel devices. As LineageOS contributor Nolen Johnson put it, ROM makers now have to “blindly guess and reverse engineer from prebuilt binaries what changes are needed each month.” ## What changed **March 2025:** Google moved all Android development to private internal systems. Previously, much of the development happened in the open where custom ROM developers could see what was being worked on. Now, everything happens behind closed doors until Google decides to release it publicly. **June 2025:** The bigger blow came with Android 16’s release. Google stopped providing device-specific configurations and driver binaries for Pixel devices in their open-source releases. These are the technical blueprints that tell custom ROMs how to work with specific hardware – like knowing which buttons do what, how the camera works, or how to manage battery life. Google says this shift is about moving to “Cuttlefish,” a virtual Android device, as their primary reference. While this might make sense for Google’s internal development, it creates real challenges for the custom ROM community. ## What this means for custom ROMs These changes make developing custom ROMs more complex. Previously, supporting new Android versions was like following a well-documented recipe. Now, it’s more like reverse-engineering a secret sauce by tasting the final product. For Pixel devices specifically, this means: * Longer development times for new Android versions * More complex debugging processes * Higher technical barriers for device maintainers * Potential delays in rolling out updates For LineageOS, building ROMs for Pixel devices will become harder. And since iodéOS is a fork of LineageOS, we’re facing the same upstream challenges. ## Why iodéOS will be fine Here’s some good news: iodéOS supports many devices, not just Google Pixels. **The majority of iodéOS-supported devices use Qualcomm Snapdragon processors, and these are much less affected by Google’s changes.** Qualcomm maintains their own Code Aurora Forum (CAF), which provides optimized Android source code specifically for Snapdragon devices. This means our support for popular devices like many Xiaomi, Samsung, and OnePlus phones remains stable. CAF continues to provide the technical foundations we need to keep these devices running smoothly with iodéOS. ## We’ve got your back At iodé, we’re not just passive observers of these changes – we’re actively adapting to ensure our community continues to get the privacy-focused, Google-free Android experience you like and trust. We’ve always been prioritizing device support based on technical feasibility and community demand. This means focusing our efforts where we can deliver the best experience with the most stability. We’re streamlining our development processes to handle the increased complexity efficiently, ensuring that while things **might** take a bit longer, the quality and reliability you expect from iodéOS remains uncompromised. ## What this means for iodéOS updates We want to set realistic expectations: **iodéOS 7, based on Android 16, may arrive later than previous major updates.** As always, iodéOS 6 (and older versions) continues to receive **monthly** security updates and improvements, so you’re not left hanging. For most of our supported devices (especially those with Snapdragon processors), the impact will be minimal. For Pixel devices, we’re working on solutions but **might** expect longer development cycles. We’d rather take the time to do it right than rush out updates that compromise your privacy or device stability. ## Why this matters for digital freedom These changes highlight exactly why we do what we do. When one company like Google controls the entire ecosystem, they can change the rules overnight. But the beauty of open-source development is that the community adapts, innovates, and finds new ways forward. While the technical landscape is shifting, your privacy and security remain our top priorities. The core features that make iodéOS special – our built-in blocker, MicroG integration, and Google-free environment – continue to work exactly as they always have. Your current iodéOS installation will continue receiving security updates and improvements. If you’re running iodéOS 6, you’re on a solid, secure foundation that will serve you well for years to come. ## The bottom line While Google’s changes create new technical challenges, they don’t change our mission or our commitment to you. We will navigate this new landscape successfully. Things **might** move a bit slower sometimes and we **might** need to be more selective about device support. But we’re not going anywhere, and neither is your privacy-focused Android experience. We’ve built something special together – a community that values privacy, digital freedom, and the right to control our own devices. These Google changes are just another obstacle to overcome, not a roadblock that stops us. ## What You Can Do Keep using iodéOS, keep sharing your experiences, and keep believing in the importance of digital privacy. Your support – whether through purchasing devices from our shop, spreading the word, or contributing to our community – directly funds the development work needed to overcome these challenges. Most importantly, trust that we’re working harder than ever to ensure your iodéOS experience remains smooth, secure, and Google-free. We’ve got your back, just like you’ve got ours. Stay tuned for more updates as we continue this journey.

Just days ahead of the new rules, Samsung quietly removed the bootloader unlock feature in its OneUI 8 update. Clearly, they’re getting ahead of compliance.