this post was submitted on 12 Jun 2025
570 points (98.8% liked)

Technology

71396 readers
3673 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
570
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
97 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
[–] nintendiator@feddit.cl 15 points 2 days ago (2 children)

or a brand whose phones support their requirements other than google.

Wasn't Graphene's "selling point" for long being that nothing but Pixels can match their reqs? I don't see why any current band would want to make it easier for them, and I also don't see new brand significantly entering the market.

Graphene boiled themselves in their own frogpan.

[–] passepartout@feddit.org 28 points 2 days ago (1 children)

This is not a selling point but rather a unfortunate but comprehensible circumstance. Nexus and later Pixel phones have not been anything more than reference hardware without significant sales until the Pixel 6. Google has been a software company that has greatly benefited by android being an "open" platform you could contribute to and use their services on.

The App / Cloud ecosystem has gained a lot of competitors, so Google is doing their best to reverse this course of action by pulling more and more functionality out of AOSP into Play services and now into Cuttlefish. We can only wait and see how other phone manufacturers react to this.

[–] nintendiator@feddit.cl 2 points 4 hours ago

We can only wait and see how other phone manufacturers react to this.

Honestly, it's obvious how they will react. After all, they'd have to pass a certification process if they want to be able to ship Google stuff.

[–] noxypaws@pawb.social 6 points 1 day ago (1 children)

Nah, you have it backwards. GrapheneOS didn't choose Pixels for any reason other than they're the only acceptably secure devices out there. I can't imagine they want this to be the case.

[–] nintendiator@feddit.cl 1 points 4 hours ago (1 children)

That still sounds like choosing to me. Like, if your project requirements are so strict that it only works on the mornings of a Tuesday that falls in a prime number day that has a blue moon and where there are no ATP tennis matches going on (all pre-existing things you have no vote on), maybe you should re-evaluate if you actually want your proyect to have a viable audience.

[–] noxypaws@pawb.social 1 points 3 hours ago

Is it really so outlandish to want my phone to be unbreakable by cops?