Oh God, no!

nostr:nprofile1qqstnr0dfn4w5grepk7t8sc5qp5jqzwnf3lejf7zs6p44xdhfqd9cgspzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctcnv0md0 can you expand more on this topic?

nostr:nevent1qqsddx5gyfe3g7p8x22drq5jveznx4qy76dpypscklj0fdhqxrukf5qpzemhxue69uhhyetvv9ujumt0wd68ytnsw43z7q3qcp2rxt39auw2plhte4vqvgnp80kcrlkrreql2te85ezvny7dv7hqxpqqqqqqz9e2vq4

Reply to this note

Please Login to reply.

Discussion

The above is a Reddit post screenshotting a cut discussion about what we received from a journalist. It even says we don't really believe it, but Google claims they won't get rid of AOSP. Last messages are what we think would happen if Android is to be forcibly split away from Google due to their legal cases.

AOSP for Pixels, however, is gone. They say they want to encourage people to move towards their virtual / emulator environment. Still, this is a blow for OS development or for having a target device to build on.

Google has made it harder to build for Pixel phones by omitting their device trees and driver binaries from the latest AOSP releases. We have had to do a tough reverse engineering effort to even get porting.

GrapheneOS will continue work on existing devices, even if there's shortcomings. We'd have to focus more work on keeping a stable port than adding great things.

A better article would be:

https://www.androidauthority.com/google-not-killing-aosp-3566882/

does this also affect non pixel devices?

Non-Pixels never had official AOSP support.