Google has yet to release the source code for Android 16 QPR1
This article is more than a month old. Sadly, it is still up do date. We’re six weeks after the release, and I still haven’t seen any reports on the source release.
I haven’t updated my Pixel to 16 yet, specifically because of this shitshow. Once Calyx drops a release, I’m going full degoogled.
Why calyx if you dont mind me asking?
I like their ethos.
Right on.
Don’t they owe the kernel code to anyone with the kernel binaries under GPL? Anyone with a Pixel running this release has a right to get the code on demand from Google, right? The news coverage doesn’t seem to consider this.
Everyone with a pixel should write in and ask for the code. Anyone know who you would contact.
Must be a reason why they don’t want us to see the code. Maybe it’s whatever they’re changing to attempt to build a walled garden to keep the app protection money rolling in.
I may keep using Android because there is no better solution but quite frankly im not sure if I can really keep recommending it over Apple.
And the FSF wants to piggyback on Android. Screw that. Every FOSS org should be lining up behind Linux for phones. I don’t care if we don’t get popular apps, freedom comes first.
This is frankly a bad take
Creating an ecosystem from the ground up is a huge undertaking that many people have failed to do in the past.
Why waste developer time when you can start with a solid base
They were talking about cracking the hardware LineageOS has to use, what’s wrong with that? Linux phones use all kinds of hacky workarounds. Until open source hardware really takes off, the goal is to make stuff work on these malicious devices.
Why not both? Android is open source, an organization can hardfork it if there is demand for it.
Some dev must have put some EPic SensiTive filE IN it.
Yes, with android 17. F google. Thank you for ruining aosp