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

Technology

71396 readers
6386 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
 

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

Have a couple OP 9pros and they'll be the last OP devices I buy.

There are severe bugs that OP never fixes and make using the phone for something like navigation unreliable. Battery life can be great one day and terrible the next when not even using the phone. Also OP sells carrier specific hardware. My TMO phones can't be used at AT&T or Verizon, severely limiting our options. My understanding is unlocked Pixel phones can be used on any carrier.

I really wanted to load Graphene, but even without it I'll consider a Pixel device.