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
 

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
[–] JasonDJ@lemmy.zip 5 points 2 days ago* (last edited 2 days ago) (1 children)

Idk man.

I love my OP12. But we're switching carriers to a Verizon MVNO which "won't work" with my OP12, so I bought a Pixel 8 Pro on sale last week and need to switch over.

I'm starting to wonder if that "it won't work" is bullshit tho...I've got a Verizon SIM in slot 2 and it works fine. Maybe I'd be missing out on 5G speeds? I got 5 bars on my tmo sim and my vz sim...but my Tmo got 1.1Gbps down, and my Vz sim only got 70Mbps.

Verizon MVNO

Christ, why?