Replying to Avatar mrecheese 🧀

nostr:nprofile1qqstnr0dfn4w5grepk7t8sc5qp5jqzwnf3lejf7zs6p44xdhfqd9cgspzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctcnv0md0 keeps us in the loop on how they deal/dealt with it. For example, here:

nostr:nevent1qqs0r6dt0zpcmlxat8pyq0awx0x7wvnwkk4kmwgzmnyau7zgcqr6gvqpzemhxue69uhhyetvv9ujucm0d9hx7uewd9hj7q3qhxx76n82ags8jrduk0p3gqrfyqyaxnrlnynu9p5rt2vmwjq6ts3qxpqqqqqqzdccten

Avatar
Final 5mo ago

GrapheneOS is fully Android 16 and gets security updates in a timely fashion since this post. Google only seized to publish the device trees, which means that AOSP was no longer built to run on Pixels mostly OOTB.

All the other Android devices do not have their device trees published and so many AOSP distribution developers are familiar with that. This only disrupted us doing a port to Android 16 super quickly like we would do with 14, 15 etc.

We use a script called adevtool that automates a lot of the port and building process. You can check it out here:

https://github.com/GrapheneOS/adevtool

Reply to this note

Please Login to reply.

Discussion

Avatar
Final 5mo ago

adevtool downloads factory images / OTA packages and extracts the firmware, overlays, and more from them. Also supports Beta builds of future Android versions, so it's helpful in porting firmwares from them if they have an early security fix or something. The original developer created it for their distribution but with GrapheneOS input and some funding.