Google withheld the release of the Pixel device trees and hardware repositories, which are crucial for makers of custom ROMs, when Android 16 was released earlier this week. Some began to speculate that “AOSP is being discontinued” as a result of this. Despite Google’s denials, the Pixel modification appears to be deliberate.
Google made the source code for Android 16 available to the Android Open Source Project on Tuesday. In a significant departure from previous releases, the Pixel device trees and other code that were utilized to modify the AOSP release to fit particular (made by) Google hardware were not made available.
Custom Android ROMs will struggle to produce their OS updates without the Pixel hardware repos, which contain the device trees, driver binaries, and other components. Security (vulnerability) researchers may also be affected by this.
As a result, some community members conjectured that AOSP was being phased out. Seang Chau, the vice president and general manager of Android, said on Wednesday night that “AOSP is NOT going away” in general. Google has stated that it will continue to be “dedicated to AOSP updates,” speaking directly to developers.
The Android team’s statement does appear to indicate that Pixel device trees will no longer be available. A “reference target” that is “independent of any particular hardware, even those from Google” is what AOSP hopes to provide in the future.
AOSP needs a reference target that is flexible, configurable, and affordable – independent of any particular hardware, including those from Google. For years, developers have been building Cuttlefish (available on GitHub as the reference device for the project) and GSI targets from source. We continue to make those available for testing and development purposes.
Once more, Google is “dedicated to AOSP,” but the future will be more difficult for people who run custom ROMs.
Stay connected with the latest from Droid Tools—follow us on X @droid_tools, like our page on Facebook, check out our updates on Instagram, and follow us on Google News for real-time news, device tips, and mobile tech insights.
The 2 XL’s update end-of-life date was in December of last year, just a few months after Google introduced Android 11. Even though they’re getting on in years, these phones are still adequate for basic day-to-day use. If you have a Pixel 2 XL and want to try Android 12 out, you can do so right now if you’re ready to take matters into your own hands. The first Android 12-based custom ROM for the Pixel has been launched, and it includes all of the important new features such as Material You, a redesigned Quick Settings panel, new system animations, and privacy improvements.
While you can always install the GSI build of Android 12 on your Pixel, the experience isn’t stable enough for everyday use because it’s designed for developers. This is where ProtonAOSP comes in, since it provides a relatively stable option for Pixel 2 XL owners to try out the latest Android update on their aging hardware. The ProtonAOSP Android 12 ROM is currently only available for the Pixel 2 XL, but a build for the smaller Pixel 2 is on the way.
Installing the ProtonAOSP’s Android 12 release is different from other ROMs as it is available as a factory image (see how over at XDA Developers). You’ll need to unlock the bootloader on your Pixel 2 and use the bundled flash-all script to install the ROM. If the installation fails, you may need to repartition and allocate more storage to various system partitions.
If you do install the ProtonAOSP ROM on your Pixel 2 XL, be prepared to run into some bugs and occasional performance issues. The major ones are non-functional Wi-Fi and Permissive SELinux permission in the current build. There are likely other issues as well that haven’t been reported yet. Nonetheless, if you want to try out Android 12 on your Pixel 2 XL, this is your best bet right now.
Manual install ProtonAOSP
This is a guide for installing ProtonAOSP manually, using the command line. The web installer is recommended if you don’t have a specific need for this. Check the list of common misconceptions if you’re not sure.
You can only use a Windows, macOS, or Linux computer for this manual installation; use the web installer if you want to install from a Chromebook or another phone.
Download a build
Download the build you want to install in factory images format.
Prepare your phone
Put your device into bootloader mode by restarting it and holding the volume down button until you see a red warning sign or green Android robot.
Once your device is in bootloader mode, plug it into the computer or device you’re installing from. Make sure you use a high-quality USB cable, as many cables will cause issues. Avoid USB hubs if possible.
Your USB cable needs to be able to copy files. Charging-only cables won’t work.
If you’re switching from the stock OS or another ROM, make sure all your important data is backed up. You’ll need to wipe all your data in order to use ProtonAOSP.
Prepare your system
First, open the “Command Prompt” app from the Start menu.
Next, download the Android SDK Platform Tools and extract them. Navigate to the extracted platform-tools folder in the terminal by typing cd (with the space at the end) and dragging the folder into Command Prompt. Then run the following command:
set PATH=%CD%;%PATH%
If it’s your first time installing from this computer, you also need to install drivers:
Open Settings → Windows Update
Click “Check for updates” and wait
Click “View optional updates”
Select the “Android Bootloader Interface” update (ignore the brand name; it doesn’t matter)
Click “Download and install” and wait for it to finish
If you’re switching from the stock OS or another ROM, you need to wipe all data before installing ProtonAOSP:
fastboot -w
Otherwise, ProtonAOSP won’t boot and your phone will get stuck on the boot animation after the installation.
DANGER
All data on your phone will be lost, so make sure your important files are backed up before doing this.
Install the build
Factory images
Extract factory images
Extract the downloaded factory images package (e.g. proton-aosp_redfin-factory_11.5.0.zip). Navigate to the new folder (e.g. redfin-rq2a.210505.003) by typing cd (with the space at the end) and dragging the folder into your terminal.
Flash factory images
Run the following command to flash the factory images:
Windows
macOS
Linux
./flash-all.sh
Copy
Don’t touch, unplug, or press any buttons on your device during the install. Your phone will restart several times, but don’t touch it. It will automatically boot into ProtonAOSP once the installation process completes.
Finish
You can now delete the factory images package, but don’t delete the platform tools — you’ll need them for updating in the future.
For security, you may also wish to re-lock the bootloader to enforce verified boot, which improves physical security and resistance against persistent attacks.
Realme1 is a legendary device which disrupted the market with its performance to price ratio back in 2018. Today also this old gun can compete any budget device in terms of performance. Since the official support has ended months ago I wanted you guys to be aware of the Custom ROM developments going on. So below is a list some the custom ROMs designed for Realme 1. A huge thanks to all hardworking developers behind these ROMs .
Installation process
Please familiarize yourself with flashing and custom rom use before attempting to flash the rom. Please make sure you download the correct version of ROMs for your specific device. Make sure you have TWRP installed.
➼Download the latest Rom & the latest GApps package
➼Boot into recovery
➼Backup your current ROM (optional)
➼Perform a FULL factory wipe and wipe /system and dalvik cache as a precaution
➼First boot may take up to 10 minutes. This is due to Gapps and root optimization.
BlissRoms based on Android 10
Bliss ROMs comes with a wide selection of customization options from around the Android community as well as unique options developed by our team. With so many options available, you’ll find it hard not to enjoy the Blissful experience.
????BUGS????
➼SELinux is permissive
➼VoLTE
➼Video codec issues in all Chromium-based browsers.
Project Sakura is a custom ROM built around Lineage OS 17.1, It tries to remain true to it while also providing some more functionality and UI changes.
????BUGS????
➼SELinux is permissive
➼VoLTE
➼Video codec issues in all Chromium-based browsers.
LineageOS is a free and open-source operating system for set-top boxes, smartphones and tablet computers, based on the Android mobile platform. It is the successor to the custom ROM CyanogenMod.
????BUGS????
➼ Selinux is permissive.
➼ Video codec issues in all Chromium based browser.
AOSP Extended is an AOSP based ROM which provides stock UI/UX experience with useful customizations. Being based on AOSP it provides a smooth experience. We have added useful customizations from various other open-source projects and have tried to keep our things simple. A ROM by a user, for a user. #BeExtended
????BUGS????
➼ Selinux is permissive.
➼ VoLTE.
➼ Video codec issues in all Chromium based browser.