android-prepare-vendor
DISCONTINUED
rattlesnakeos-stack
DISCONTINUED
Our great sponsors
android-prepare-vendor | rattlesnakeos-stack | |
---|---|---|
14 | 16 | |
25 | 556 | |
- | - | |
0.0 | 5.3 | |
over 1 year ago | about 2 years ago | |
Shell | Go | |
- | MIT License |
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
- 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...
- Release 20211112: Breaking APV changes and Pixel 5a fix
- Mckay of GrapheneOS Denies Calyx's Code Use by Creating a Non-Permissive Licence
- GrapheneOS demands takedown of code from CalyxOS
-
New Pixel 5a
Adding support for it in android-prepare-vendor, which has an open (untested) PR for it here: https://github.com/AOSPAlliance/android-prepare-vendor/pull/71
-
Pixel 5 Support
FYI I was able to build ROS for redfin using the android-prepare-vendor branch by sdh4. Once his PR is approved, adding Pixel 5 support to ROS should be easy.
rattlesnakeos-stack
-
Release 20211112: Breaking APV changes and Pixel 5a fix
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):
-
November 2021 Update
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.
-
New Pixel 5a
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
-
Add Android Auto to Calyx OS before flashing ROM
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 – De-Googled Android Alternative
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).
-
LineageOS 18.1 Released
I've been using LineageOS since the good ol' CyanogenMod days and I am very grateful for how much work the developers put into it day in and day out.
Thanks to them, I managed to get rid of Google Apps in my day-to-day life almost[0] entirely and drastically improve privacy for me: Instead of Google Play Services I use MicroG[1] and instead of Play Store, I use Aurora Store[2] and F-Droid. For syncing files there is Syncthing[3] and for backups there is Seedvault[4]. To isolate apps I don't trust I use NetGuard[8] and Shelter[9] and practically no internet-facing app has access to my internal "SD card" on which my photos and documents reside. As a bonus, getting rid of GApps and using LineageOS has increased my phones' battery life and their overall lifetime tremendously. (I've only owned three smartphones in my entire life, the original T-Mobile G1, the HTC One M8 and the BQ Aquaris Pro.) I couldn't be happier.
That being said, I've closely been following GrapheneOS[5] because I find its additional security guarantees very attractive. In fact, just a few hours ago my new Pixel 5 arrived and I'm looking forward to giving it a try. Though I already know I will miss MicroG… Maybe I'll end up building my own custom Android ROM, using Hashbang or RattlesnakeOS[6, 7]?
Overall, I don't really understand people who criticize Android for not being open while loudly claiming a "pure" Linux phone would be so much better. (There was yet another discussion here on HN just a few days ago.) Yes, Android is a not your typical open-source project and clearly in the hands of Google. Yes, most phone and chip manufacturers still haven't open-sourced their hardware binary blobs. We definitely have to fight these fights. But with a Linux phone I'd probably be struggling with window-manager-related bugs in the worst possible moments (say, an emergency call) and risk all my data getting stolen whenever I install a new app.
As much as I like Linux – I dabbled with it the first time almost two decades ago and have been using it as a daily driver for more than a decade – but its stability and, especially, security guarantees are orders of magnitude worse than Android's.
I secretly hope that Fuchsia will find its way to the desktop at some point and be able to replace my Linux system.
[0]: I still use Google Maps every now and then
[1]: https://microg.org . See https://lineage.microg.org/ for LineageOS images that come with MicroG pre-installed.
[4]: https://github.com/seedvault-app/seedvault
[6]: https://github.com/hashbang/aosp-build
[7]: https://github.com/dan-v/rattlesnakeos-stack/
[8]: https://netguard.me/
-
Mar 2021 Update and v11.0.7
This is a fairly significant update that includes some backwards incompatible changes specifically around how customizations are done. I initially had planned to support v11.0.6 for one more month to allow time to migrate, but v11.0.6 is not able to build the March 2021 update without a fix, so I decided to just move forward with v11.0.7 only. You can read more about the new approach of using custom config repos here https://github.com/dan-v/rattlesnakeos-stack#customizations. As with any large update, I'd recommend backing up everything just in case.
-
January 2021 Update
Since the PR on android-prepare-vendor has been merged, I sent you a PR for redfin.
What are some alternatives?
calyxos
opengapps - The main repository of the Open GApps Project
NewPipe - A libre lightweight streaming front-end for Android.
GmsCore - Free implementation of Play Services
robotnix - Build Android (AOSP) using Nix [maintainer=@danielfullmer,@Atemu]
aquatone - A Tool for Domain Flyovers
cloudfront-autoindex - AWS Lambda to work around index.html S3/CloudFront mess
android-prepare-vendor - Set of scripts to automate AOSP compatible vendor blobs generation from factory images
treble_experimentations - Notes about tinkering with Android Project Treble
chrome-session-dump - A program for extracting information from chrome session files.
samfirm.js - TypeScript implementation of a streaming downloader, decryptor and extractor of Samsung firmware.
android_vendor_lineage