android-prepare-vendor
Set of scripts to automate AOSP compatible vendor blobs generation from factory images (by AOSPAlliance)
releases
This repo maintains metadata about RattlesnakeOS releases. (by RattlesnakeOS)
| android-prepare-vendor | releases | |
|---|---|---|
| 14 | 3 | |
| 25 | 4 | |
| - | - | |
| 0.0 | 4.7 | |
| over 3 years ago | over 4 years ago | |
| Shell | Python | |
| - | - |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
android-prepare-vendor
Posts with mentions or reviews of android-prepare-vendor.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-30.
- Daniel Micay steps down as the leader of GrapheneOS. My thoughts and why you should keep using it.
-
GrapheneOS: The private and secure mobile OS
The developer of GrapheneOS is openly hostile to other similar projects (https://github.com/bromite/bromite/issues/2141 and https://github.com/AOSPAlliance/android-prepare-vendor/issue... are concrete examples). He's done things like relicensing one of his repos to GPLv2-only because a project he had a dispute with is GPLv3-or-later, and that way they can't use his code anymore, but he still gets to call his project FOSS.
-
Daniel Micay from GrapheneOS tells Bromite to pull patches
Strcat has a long history of these disputes. Most recently he requested the AOSP Alliance also stop using "his" code.
https://github.com/AOSPAlliance/android-prepare-vendor/issue...
-
has CalyxOS relevant advantages over GrapheneOS?
This was due to a sabotage from the GrapheneOS project. See: https://github.com/AOSPAlliance/android-prepare-vendor/issues/78
- Release 20211112: Breaking APV changes and Pixel 5a fix
- Mckay of GrapheneOS Denies Calyx's Code Use by Creating a Non-Permissive Licence
- CalyxOS Devs Appreciation Post
- GrapheneOS Android-prepare-vendor Android 12 port must not be used by CalyxOS
- GrapheneOS demands takedown of code from CalyxOS
releases
Posts with mentions or reviews of releases.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2021-08-26.
-
New Pixel 5a
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.
-
latest.json is out of date?
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.
-
Mar 2021 Update and v11.0.7
* 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
What are some alternatives?
When comparing android-prepare-vendor and releases you can also consider the following projects:
rattlesnakeos-stack - Build your own privacy and security focused Android OS in the cloud.
example-custom-config-repo - This is an example custom config repo which is used to customize RattlesnakeOS builds.
android-prepare-vendor - Set of scripts to automate AOSP compatible vendor blobs generation from factory images
custom-config-repo
AppStore