It appears Google has stopped publishing device-specific source code for Pixel phones
-
cross-posted from: https://lemmy.world/post/31229844
As noted by the news release from CalyxOS and Mastodon thread from GrapheneOS, Google did not release the Pixel device-specific source code alongside their Android 16 AOSP release like they usually do. I think many of us, including myself, are hoping this will be published in the near future, but considering they moved AOSP development behind closed doors earlier this year, it's more likely Google has stopped publishing this section or their code altogether, making development of custom ROMs for Pixel devices significantly more difficult. Sad news for the Android ecosystem, and for open source in general.
-
cross-posted from: https://lemmy.world/post/31229844
As noted by the news release from CalyxOS and Mastodon thread from GrapheneOS, Google did not release the Pixel device-specific source code alongside their Android 16 AOSP release like they usually do. I think many of us, including myself, are hoping this will be published in the near future, but considering they moved AOSP development behind closed doors earlier this year, it's more likely Google has stopped publishing this section or their code altogether, making development of custom ROMs for Pixel devices significantly more difficult. Sad news for the Android ecosystem, and for open source in general.
Hope this gives Fairphone plenty of new customers and allows them to start selling more globally.
-
Hope this gives Fairphone plenty of new customers and allows them to start selling more globally.
I’m begging Fairphone to expand into Canada
-
I’m begging Fairphone to expand into Canada
Yeah I really hope so too!!
-
Hope this gives Fairphone plenty of new customers and allows them to start selling more globally.
Not buying a Fairphone as long as they aren't sold where they are being made. As much as people here hate anything marketing I just don't get why so many fall for Fairphone's greenwashing.
-
cross-posted from: https://lemmy.world/post/31229844
As noted by the news release from CalyxOS and Mastodon thread from GrapheneOS, Google did not release the Pixel device-specific source code alongside their Android 16 AOSP release like they usually do. I think many of us, including myself, are hoping this will be published in the near future, but considering they moved AOSP development behind closed doors earlier this year, it's more likely Google has stopped publishing this section or their code altogether, making development of custom ROMs for Pixel devices significantly more difficult. Sad news for the Android ecosystem, and for open source in general.
Oh no, Google is EEEing their phones, color me shocked.
-
cross-posted from: https://lemmy.world/post/31229844
As noted by the news release from CalyxOS and Mastodon thread from GrapheneOS, Google did not release the Pixel device-specific source code alongside their Android 16 AOSP release like they usually do. I think many of us, including myself, are hoping this will be published in the near future, but considering they moved AOSP development behind closed doors earlier this year, it's more likely Google has stopped publishing this section or their code altogether, making development of custom ROMs for Pixel devices significantly more difficult. Sad news for the Android ecosystem, and for open source in general.
wrote last edited by [email protected]Google’s decision to now discontinue the Pixel as an AOSP reference device is unfortunate, as it has pulled the rug from under developers like the teams at LineageOS and GrapheneOS who build Android for Pixel devices. These developers will still be able to build AOSP for Pixel devices, but it will now be more difficult and painful to do so than before, as they will need to build their own device trees from scratch. This also brings Pixels down to the same level as other Android devices[.]
Yep, looks like Pixel is just another Android to ROM developers. A sorry shame indeed. There goes another reason to bother with the Pixel. Just go buy Samsung if support was your reason. They bench better anyway.
-
Not buying a Fairphone as long as they aren't sold where they are being made. As much as people here hate anything marketing I just don't get why so many fall for Fairphone's greenwashing.
wrote last edited by [email protected]Fair, but is your current phone truly made in your home country?
Fairphone is arguably doing a lot of good for the consumers and (even if its not perfect) for the environment compared to other phone manufacturers. And most people in my country need a (smart)phone.
I highly recommend the book "The Book of Hope" from Jane Goodall to truly understand "Don't let perfect be the enemy of good" when it comes to climate action.
Edit: added full title of the book
-
Fair, but is your current phone truly made in your home country?
Fairphone is arguably doing a lot of good for the consumers and (even if its not perfect) for the environment compared to other phone manufacturers. And most people in my country need a (smart)phone.
I highly recommend the book "The Book of Hope" from Jane Goodall to truly understand "Don't let perfect be the enemy of good" when it comes to climate action.
Edit: added full title of the book
wrote last edited by [email protected]I run GrapheneOS. Stock Fairphone doesn't fit my security requirements, but if I can put a hardened OS on it I'd consider it.
-
I’m begging Fairphone to expand into Canada
If they join the EU its basically guaranteed
-
I run GrapheneOS. Stock Fairphone doesn't fit my security requirements, but if I can put a hardened OS on it I'd consider it.
Yeah. The linked Mastodon thread by GrapheneOS mentions them potentially making a phone themselves. I'd love if they partnered with fairphone to build it. Though it sounds like we'd need to accept a higher price than a standard fairphone.
-
cross-posted from: https://lemmy.world/post/31229844
As noted by the news release from CalyxOS and Mastodon thread from GrapheneOS, Google did not release the Pixel device-specific source code alongside their Android 16 AOSP release like they usually do. I think many of us, including myself, are hoping this will be published in the near future, but considering they moved AOSP development behind closed doors earlier this year, it's more likely Google has stopped publishing this section or their code altogether, making development of custom ROMs for Pixel devices significantly more difficult. Sad news for the Android ecosystem, and for open source in general.
Graphene and Calyx OS should rebase on Lineage OS
-
cross-posted from: https://lemmy.world/post/31229844
As noted by the news release from CalyxOS and Mastodon thread from GrapheneOS, Google did not release the Pixel device-specific source code alongside their Android 16 AOSP release like they usually do. I think many of us, including myself, are hoping this will be published in the near future, but considering they moved AOSP development behind closed doors earlier this year, it's more likely Google has stopped publishing this section or their code altogether, making development of custom ROMs for Pixel devices significantly more difficult. Sad news for the Android ecosystem, and for open source in general.
-
it both sounds horrifying, and fantastic.
I wish they wouldn't have had to try figuring that out in these circumstances
