this post was submitted on 12 Jun 2025
102 points (100.0% liked)

Android

19414 readers
218 users here now

The new home of /r/Android on Lemmy and the Fediverse!

Android news, reviews, tips, and discussions about rooting, tutorials, and apps.

πŸ”—Universal Link: !android@lemdro.id


πŸ’‘Content Philosophy:

Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.


Support, technical, or app related questions belong in: !askandroid@lemdro.id

For fresh communities, lemmy apps, and instance updates: !lemdroid@lemdro.id

πŸ’¬Matrix Chat

πŸ’¬Telegram channels / chats

πŸ“°Our communities below


Rules

  1. Stay on topic: All posts should be related to the Android OS or ecosystem.

  2. No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to !askandroid@lemdro.id.

  3. Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to !androidmemes@lemdro.id.

  4. No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.

  5. No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.

  6. No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.

  7. No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.

  8. No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.

  9. No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!

  10. No affiliate links: Posting affiliate links is not allowed.

Quick Links

Our Communities

Lemmy App List

Chat and More


founded 2 years ago
MODERATORS
 

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.

all 15 comments
sorted by: hot top controversial new old
[–] chemicalwonka@discuss.tchncs.de 8 points 1 day ago (1 children)

it both sounds horrifying, and fantastic.

I wish they wouldn't have had to try figuring that out in these circumstances

[–] henfredemars@infosec.pub 19 points 2 days ago* (last edited 2 days ago)

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.

[–] Lazycog@sopuli.xyz 20 points 2 days ago (2 children)

Hope this gives Fairphone plenty of new customers and allows them to start selling more globally.

[–] Sunshine@lemmy.ca 12 points 2 days ago (2 children)

I’m begging Fairphone to expand into Canada πŸ‡¨πŸ‡¦

If they join the EU its basically guaranteed :D

[–] Lazycog@sopuli.xyz 1 points 2 days ago

Yeah I really hope so too!!

[–] Heathcliff@lemm.ee 5 points 2 days ago (1 children)

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.

[–] Lazycog@sopuli.xyz 5 points 2 days ago* (last edited 2 days ago) (1 children)

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

[–] voracitude@lemmy.world 4 points 2 days ago* (last edited 2 days ago) (1 children)

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.

[–] hashferret@lemmy.world 4 points 1 day ago

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.

[–] 0x0@lemmy.zip 11 points 2 days ago

Oh no, Google is EEEing their phones, color me shocked.

[–] sunzu2@thebrainbin.org 4 points 1 day ago

Damn... This class war is heating up.

I guess we shoulda have known it was a matter of time.

Mega corpos see freedom enjoyers as a threat to their profits.

[–] possiblylinux127@lemmy.zip -3 points 1 day ago

Graphene and Calyx OS should rebase on Lineage OS