Technology

88,303 readers

14,837 active

2,984 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

[–] malwieder@feddit.org 44 points 1 year ago (2 children)

That was bound to happen at some point. Buying a Google device to then "degoogle" it never sit quite right with me.

[–] Takios@discuss.tchncs.de 17 points 1 year ago

I bought mine secondhand because I had a bad feeling about giving google money just to degoogle as well but still really wanted to use GrapheneOS

parent

[–] ryannathans@aussie.zone 6 points 1 year ago

Amen but here we are

parent