Technology

71415 readers

3241 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.

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

544

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

93 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

[–] ocassionallyaduck@lemmy.world 1 points 1 day ago

I'm not worried about me. I can manage. But I had to intervene and make it a Project for my immediate family. Which is always unfun, because who wants to expose all their personal data that way, especially photos.

Crazy that Google just screwed over GrapheneOS like this.