releases VS rattlesnakeos-stack

Barbet should be in 11, you can see the tag android-11.0.0_r42: https://android.googlesource.com/platform/manifest/+/refs/tags/android-11.0.0_r42/default.xml#59. The part it's failing on here is parsing the latest.json file which by default points at: https://github.com/RattlesnakeOS/releases/blob/11.0/latest.json and this doesn't have the barbet device entry in there.

Answered this in our Matrix room, but just to share here as well, the new replacement repo is here (https://github.com/RattlesnakeOS/releases) and used from v11.0.7 onwards. The old repo is deprecated.

* new: add support for custom config repos and deprecate old customization methods (custom-patches, custom-manifest-remotes, custom-manifest-projects, custom-prebuilts). see the updated section in the readme to learn more about custom config repos and how to use them. * new: also add support for core config repos that can be used to build an OS with plain AOSP rather than using the default RattlesnakeOS core. * new: add support for Pixel 4a 5G. * deprecate: Pixel 2 and Pixel 2 XL are no longer supported * deprecate: encrypted-keys option (for now) to reduce build script complexity * deprecate: hosts-file (can be added in custom config repo) * move version checking to lambda function and base everything on a 'release' now rather than individual components, and add version pinning of core components. releases url is by default here https://github.com/RattlesnakeOS/releases, but is also configurable now. * move templates out into individual files with new go embed functionality and move rendering of these to it's own function * start breaking apart shell script into generic raw shell script (that can be shellchecked) and the more dynamic pieces that would change across clouds * have lambda function poll and wait for a spot instance to launch rather than immediately returning success * change from building fdroid to using prebuilt (https://github.com/RattlesnakeOS/platform_prebuilts_fdroid) and use the default privileged extensions without any changes * add an option to disable building Chromium (should provide your own webview with customizations in this case) * add option to disable cron by setting schedule to empty string * for deploy command add --dry-run flag that will just render the files to disk * automatically backup config file to s3 bucket * move to using gp3 storage for build instances and bump to 300gb of storage * cleanup makefile, add shellcheck, add tests * upgrade to ubuntu 20.04 AMI * move to go 1.16 * move to aws go v2 sdk * update readme

download 11.0.15 (https://github.com/dan-v/rattlesnakeos-stack/releases/tag/v11.0.15) and use this binary to 'deploy' and then kick off a 11.0 build and update your phone

I'm not interested in the current android-prepare-vendor drama, so until an alternative is built, I've made a change that requires you to specify an android-prepare-vendor to use in your local config file. This release will require that you update to 12.0.3 and add three new config entries for specifying details of android-prepare-vendor. Here is an example of what that might look like (do not copy as is - it will not build):

There is a new stack version 12.0.2 required for this update. The 12.0.2 update fixes an issue with new stacks on 12.0 that was causing a build failure; thanks u/caasi-dev for reporting the issue.

First release of 12.0. You'll need updated stack release 12.0.1. Highly recommend backing up your device before attempting upgrade.

This release is still 11.x and next release with 12.x will depend on how long it takes to get everything up and working. It requires a stack update this month to 11.0.14, as there were two minor build issues with Chromium 94.x.

There were no stack changes required this month, unless you need support for Pixel 5a and then you should be on 11.0.13.

Adding support for it in rattlesnakeos-stack, which is very minor, an example of adding Pixel 5 is here: https://github.com/dan-v/rattlesnakeos-stack/pull/178

There are some tools already which support automated builds such as https://github.com/dan-v/rattlesnakeos-stack and https://github.com/danielfullmer/robotnix - however they'll need work to support both CalyxOS and also Android Auto.

CalyxOS is an awesome project. I have worked with the lead developer a bit over the past few years and it's been such a pleasure. We share some bits of code between our projects here: https://github.com/AOSPAlliance.

If anyone is interested in building their own custom android OS in the cloud (AWS) with same ability to lock your bootloader like CalyxOS, you can checkout my project I've been maintaining for a few years now called RattlesnakeOS: https://github.com/dan-v/rattlesnakeos-stack.

And if you prefer to not build in the cloud, there is also a really great project called robotnix (https://github.com/danielfullmer/robotnix) which provides a way to build many flavors of OS (AOSP, GrapheneOS, LineageOS, etc).