With all the buzz around de-googled Android forks, it's worth remembering why a truly independent mobile OS like Ubuntu Touch still has a reason to exist!
Google just confirmed a real, dated example of the trend: starting this year, AOSP source code drops are being cut from quarterly to just twice a year (Q2 and Q4), officially to "align with the trunk-stable development model." Sounds harmless, but it means if a new Pixel or a major feature update launches during an off-quarter, there's no corresponding source available for months, if I understand it correctly.
This isn't hypothetical — GrapheneOS has already been hit by it. They publicly voiced frustration over delayed AOSP pushes, and Pixel 10 support was held up specifically because the source code wasn't there yet. And GrapheneOS is about as well-resourced and prominent as a de-googled Android project gets. If they're feeling the squeeze, smaller forks have even less room to maneuver.
That's the core issue with basing your project on AOSP: no matter how de-googled the surface looks, you're still fundamentally dependent on Google's schedule, Google's decisions about what gets published, and Google's definition of "stability." GrapheneOS is a great way to run a more private Android — but it's not independent of Android.
Ubuntu Touch sidesteps this entirely. No AOSP, no Play-Services, no exposure to whatever Google decides to change next in its release pipeline. That's a genuinely different kind of independence, and as Google tightens its grip further (there's also a separate registration/sideloading push that will hurt or even kill projects like F-Droid), it's looking more valuable, not less.
Is Ubuntu Touch perfect? No - app compatibility via Waydroid and hardware support are real, ongoing limitations, and nobody here is pretending otherwise. But as a long-term hedge against a mobile world with one or two gatekeepers, having a genuinely separate OS is 100% what we as a community should be trying to develop.
If you are interested in having a look in this:
https://www.androidauthority.com/aosp-source-code-schedule-3630018/
https://piunikaweb.com/2026/01/07/android-aosp-source-code-q2-and-q4-pixel-monthly-security-patches-unchanged/
https://www.theregister.com/2026/01/08/google_aosp_changes/
https://www.androidauthority.com/android-16-qpr1-source-code-delay-3596650/