Lucario1829 printf im just repeating whats been said by the grapheneos official project account on social media/discord in response to the same questions
__Blank__ printf https://discuss.grapheneos.org/d/21315-explanation-of-recent-changes-to-aosp-and-the-lack-of-major-impact-on-grapheneos
Lucario1829 __Blank__ thats not what most people are worried about anymore, most concern recently comes from android not providing device trees anymore, thus graphene has to maintain their own
__Blank__ hmop https://discuss.grapheneos.org/d/21315-explanation-of-recent-changes-to-aosp-and-the-lack-of-major-impact-on-grapheneos
userofgos Lucario1829 it's been repeatedly discussed at length in a mother thread. Every other OEM has to build their own device trees. Google is no longer publishing the device trees for Pixel devices because they are instead using their "Cuttlefish" virtual device as the reference target for AOSP. Previously, the Pixel devices were the AOSP reference target. https://discuss.grapheneos.org/d/23080-aosp-and-pixel-device-support/31
userofgos hmop now that source code is not available on pixel 10 /android 16 and beyond hmop i read they closed the source code for android 16 beyond Where are you getting this misinformation?
Lucario1829 userofgos i know that, thus its nothing to be concerned about, i was just saying people are often concerned about it
other8026 Here's an existing thread: https://discuss.grapheneos.org/d/23080-aosp-and-pixel-device-support Also, here's a thread about this on Mastodon by the project account: https://grapheneos.social/@GrapheneOS/114721666000552094. It covers this question and the misinformation about GrapheneOS's future.