Technology

88,303 readers

14,837 active

3,027 users here now

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

Our Rules

Follow the lemmy.world rules.
Only tech related news or articles.
Be excellent to each other!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
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.
Check for duplicates before posting, duplicates may be removed
Accounts 7 days and younger will have their posts automatically removed.

founded 3 years ago

moderators

submitted 1 year ago by lzfm@lemmus.org to c/technology@lemmy.world

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

[–] timbuck2themoon@sh.itjust.works 8 points 1 year ago* (3 children)

I really want to give furios phone a shot. It's apparently close to supporting my carrier.

That and a sailfish phone. The community one though didn't support my carrier (think it's mainly EU specced only.)

What I find missing most of the time though is any esim support. Makes me wonder if the hardware one that you can program an esim on works.

parent