this post was submitted on 12 Jun 2025
542 points (98.7% liked)

Technology

71371 readers
3484 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 2 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
L4s@hackingne.ws
542
AOSP isn't dead, but Google just landed a huge blow to custom ROM developers (www.androidauthority.com)
submitted 2 days ago by lzfm@lemmus.org to c/technology@lemmy.world
91 comments fedilink hide all child comments
 

TL;DR

  • Google has made it harder to build custom Android ROMs for Pixel phones by omitting their device trees and driver binaries from the latest AOSP release.

  • The company says this is because it’s shifting its AOSP reference target from Pixel hardware to a virtual device called “Cuttlefish” to be more neutral.

  • While Google insists AOSP isn’t going away, developers must now reverse-engineer changes, making the process for supporting Pixel devices more difficult.

you are viewing a single comment's thread
view the rest of the comments
[–] ocassionallyaduck@lemmy.world 11 points 1 day ago (1 children)

Yes, but that shouldn't explicitly opt in, and they shouldn't marry that product to Gmail and Google Drive if they are going to push it to enable by default.

Again, it's really insidious. They push it so aggressively I had to disable it on my personal device twice, and I can't just not use Google Photos app because it's tied to the camera itself on pixel phones.

[–] tiramichu@sh.itjust.works 1 points 1 day ago* (last edited 1 day ago) (1 children)

I agree with you, it's insidious.

Given you've got a Pixel phone, you can save at least yourself from this problem by running Graphene or Calyx on it.

[–] ocassionallyaduck@lemmy.world 1 points 19 hours ago

I'm not worried about me. I can manage. But I had to intervene and make it a Project for my immediate family. Which is always unfun, because who wants to expose all their personal data that way, especially photos.

Crazy that Google just screwed over GrapheneOS like this.