Testing CRDroid A16 Go Edition on my own device. I expected the Go Edition to kill background apps, and I thought only one app would run in the background. After the ROM settled for 30 minutes on my device, the result was actually different, even on my 4GB device. I was able to run 5 apps at the same time without any reloading like a13. The UI also feels better than A13.
π₯33β€8π±3π2
The Go Edition build will be released in this channel, especially for 4GB users. I think it's time to switch to Android 16 Go Edition, but the problem is that some features and apps are limited.
π±16π₯11β€5
crDroid v12.10 - UNOFFICIAL | Android 16 Go
build: 02/06/'26
βͺοΈ Download
crDroidAndroid-16.0-20260602-spes-v12.10.zip
β’ Optimized For: 4GB RAM variants.
β’ 6GB / 8GB RAM Users: You can safely flash and use this build, but it is NOT recommended. The system framework has been highly tuned to maximize memory retention and performance for tight 4GB RAM configurations, which might underutilize higher-tier hardware configurations.
Changelogs
* Initial Go edition Build for spes
* Updated dalvik props for 4gb/6gb/8gb ram variants
* Cleanup camera blobs.
* Switch to QTI AIDL memtrack HAL
Notes:
* This build requires a minimal GApps package. You MUST flash CORE GAPPS ONLY (NikGapps Core) link . Do NOT flash heavy Mini, Macro, or Stock GApps packages, or the system configuration will choke.
* Find Working keybox config for get play integrity fix
Credits
@sayann70 - For base a16 devicetree
@crDroidAndroid for crdroid base rom source
@Penguin421 - For server
By @muralivijay9845
build: 02/06/'26
βͺοΈ Download
crDroidAndroid-16.0-20260602-spes-v12.10.zip
β’ Optimized For: 4GB RAM variants.
β’ 6GB / 8GB RAM Users: You can safely flash and use this build, but it is NOT recommended. The system framework has been highly tuned to maximize memory retention and performance for tight 4GB RAM configurations, which might underutilize higher-tier hardware configurations.
Changelogs
* Initial Go edition Build for spes
* Updated dalvik props for 4gb/6gb/8gb ram variants
* Cleanup camera blobs.
* Switch to QTI AIDL memtrack HAL
Notes:
* This build requires a minimal GApps package. You MUST flash CORE GAPPS ONLY (NikGapps Core) link . Do NOT flash heavy Mini, Macro, or Stock GApps packages, or the system configuration will choke.
* Find Working keybox config for get play integrity fix
Credits
@sayann70 - For base a16 devicetree
@crDroidAndroid for crdroid base rom source
@Penguin421 - For server
By @muralivijay9845
β€25π’3π2β‘1π―1
[UPDATE] crDroid v12.11 - UNOFFICIAL | Android 16 Go
Build Date: 06/09/2026
βͺοΈ Download
crDroidAndroid-16.0-20260906-spes-v12.11.zip
β’ Optimized For: 4GB RAM variants.
Changelog
* ROM: Updated crdroid to version 12.11
* ROM: Applied August security patch
* Device: Removed unused camera blobs
* Device: Resolved slow fast-charging issue
* Device: Reoptimized swapiness and VFS cache for enhanced memory management
* Device: Updated and cleaned up Dalvik properties
* Device: Fixed issue where ringtones and alarms did not play when Bluetooth or wired headphones were connected
* Device: Switched to AOSP WFD
* Device: Set FCM level to 7
* Device: Removed Samsung debug tools
* Device: Resolved several SELinux denials
* Device: Switched to common AIDL IR service
* Kernel: Upstreamed BPF patches up to 4.19.325-cip135-st19
* Kernel: Implemented memory management fixes for 4GB variants
Notes:
* This build requires a minimal GApps package. It is mandatory to flash only CORE GAPPS (BITGApps Core) via link. Do not flash heavy Mini, Macro, or Stock GApps packages, as this may cause system instability.
* Do not flash Nik GApps, as this will cause the device to boot into fastboot mode.
* Locate a working keybox configuration to obtain a Play Integrity fix.
Credits
@sayann70 - For base A16 devicetree
@crDroidAndroid - For crdroid base ROM source
By @muralivijay9845
Build Date: 06/09/2026
βͺοΈ Download
crDroidAndroid-16.0-20260906-spes-v12.11.zip
β’ Optimized For: 4GB RAM variants.
Changelog
* ROM: Updated crdroid to version 12.11
* ROM: Applied August security patch
* Device: Removed unused camera blobs
* Device: Resolved slow fast-charging issue
* Device: Reoptimized swapiness and VFS cache for enhanced memory management
* Device: Updated and cleaned up Dalvik properties
* Device: Fixed issue where ringtones and alarms did not play when Bluetooth or wired headphones were connected
* Device: Switched to AOSP WFD
* Device: Set FCM level to 7
* Device: Removed Samsung debug tools
* Device: Resolved several SELinux denials
* Device: Switched to common AIDL IR service
* Kernel: Upstreamed BPF patches up to 4.19.325-cip135-st19
* Kernel: Implemented memory management fixes for 4GB variants
Notes:
* This build requires a minimal GApps package. It is mandatory to flash only CORE GAPPS (BITGApps Core) via link. Do not flash heavy Mini, Macro, or Stock GApps packages, as this may cause system instability.
* Do not flash Nik GApps, as this will cause the device to boot into fastboot mode.
* Locate a working keybox configuration to obtain a Play Integrity fix.
Credits
@sayann70 - For base A16 devicetree
@crDroidAndroid - For crdroid base ROM source
By @muralivijay9845
mega.nz
1.6 GB file on MEGA
π₯14β€4π1
Muralidharan | Redmi note 11 | Releases pinned Β«[UPDATE] crDroid v12.11 - UNOFFICIAL | Android 16 Go Build Date: 06/09/2026 βͺοΈ Download crDroidAndroid-16.0-20260906-spes-v12.11.zip β’ Optimized For: 4GB RAM variants. Changelog * ROM: Updated crdroid to version 12.11 * ROM: Applied August security patchβ¦Β»
Hi everyone,
i wanted to give you an official, technical update regarding our kernel strategy and our evaluation of the 5.15 kernel bringup.
Over the past few months, our developers community has made impressive progress on 5.15βincluding camera fixes thanks to halt for his efforts. However, after evaluating long-term stability, user safety, and hardware compatibility, i have officially decided to keep our primary/stable releases on our optimized 4.19 kernel with backported BPF support, while maintaining 5.15 as an experimental side project.
Here is a detailed breakdown of why this decision was made for the long-term health of our device:
1. Installation Complexity & Hardware Safety
Running 5.15 requires users to manually repartition their internal storage using parted commands to create a dummy init_boot partition. Requiring manual GPT partition modifications carries a high risk of hard-bricking devices for average users and permanently breaks clean Recovery and OTA update workflows.
2. Firmware Swapping & Downgrade Risks
To run 5.15, users are required to flash ADSP/DSP firmware files ported from another device. If a user ever decides to switch back to stock or 4.19-based ROMs without manually restoring the stock DSP/ADSP firmware, the device will fail to boot entirely.
3. Bootloader Limitations & Broken Root (Magisk)
Because our legacy bootloader does not natively parse the init_boot structure, the dummy init_boot partition cannot be utilized correctly during the bringup process. As a result, attempting to patch init_boot with Magisk will fail, breaking root access.
4. Upstream Kernel Lifecycle (EOL)
Linux 5.15 is nearing its official End-of-Life (EOL) status in upstream Linux. Moving our main codebase to an EOL kernel creates heavy long-term maintenance overhead for security backports without providing true mainline longevity.
5. Hardware IPC & Security Compromises
Due to underlying vendor firmware limits (ADSP / FastRPC), core hardware integrations like the virtual proximity sensor remain unstable on 5.15. Furthermore, achieving functional decryption requires forced downgrades from Keymint HAL to legacy Keymaster 4.1.
6. Peak Performance on 4.19 + eBPF
With upstream eBPF (clsact/cgroup) successfully backported to our 4.19 kernel, our builds fully meet modern Android networking requirements while retaining 100% hardware functionality, native root support, peak battery efficiency, and zero-risk installation.
Roadmap Going Forward:
β’ Stable ROM Releases: Will strictly use the 4.19 + eBPF kernel for complete reliability, safety, and seamless flashing.
β’ Experimental 5.15 Project: Will remain active on GitHub for developers and advanced testers who wish to contribute toward FastRPC,audio and sensor IPC research.
Thank you all for your continued patience, testing, and support as we prioritize daily-driver stability for our device!
i wanted to give you an official, technical update regarding our kernel strategy and our evaluation of the 5.15 kernel bringup.
Over the past few months, our developers community has made impressive progress on 5.15βincluding camera fixes thanks to halt for his efforts. However, after evaluating long-term stability, user safety, and hardware compatibility, i have officially decided to keep our primary/stable releases on our optimized 4.19 kernel with backported BPF support, while maintaining 5.15 as an experimental side project.
Here is a detailed breakdown of why this decision was made for the long-term health of our device:
1. Installation Complexity & Hardware Safety
Running 5.15 requires users to manually repartition their internal storage using parted commands to create a dummy init_boot partition. Requiring manual GPT partition modifications carries a high risk of hard-bricking devices for average users and permanently breaks clean Recovery and OTA update workflows.
2. Firmware Swapping & Downgrade Risks
To run 5.15, users are required to flash ADSP/DSP firmware files ported from another device. If a user ever decides to switch back to stock or 4.19-based ROMs without manually restoring the stock DSP/ADSP firmware, the device will fail to boot entirely.
3. Bootloader Limitations & Broken Root (Magisk)
Because our legacy bootloader does not natively parse the init_boot structure, the dummy init_boot partition cannot be utilized correctly during the bringup process. As a result, attempting to patch init_boot with Magisk will fail, breaking root access.
4. Upstream Kernel Lifecycle (EOL)
Linux 5.15 is nearing its official End-of-Life (EOL) status in upstream Linux. Moving our main codebase to an EOL kernel creates heavy long-term maintenance overhead for security backports without providing true mainline longevity.
5. Hardware IPC & Security Compromises
Due to underlying vendor firmware limits (ADSP / FastRPC), core hardware integrations like the virtual proximity sensor remain unstable on 5.15. Furthermore, achieving functional decryption requires forced downgrades from Keymint HAL to legacy Keymaster 4.1.
6. Peak Performance on 4.19 + eBPF
With upstream eBPF (clsact/cgroup) successfully backported to our 4.19 kernel, our builds fully meet modern Android networking requirements while retaining 100% hardware functionality, native root support, peak battery efficiency, and zero-risk installation.
Roadmap Going Forward:
β’ Stable ROM Releases: Will strictly use the 4.19 + eBPF kernel for complete reliability, safety, and seamless flashing.
β’ Experimental 5.15 Project: Will remain active on GitHub for developers and advanced testers who wish to contribute toward FastRPC,audio and sensor IPC research.
Thank you all for your continued patience, testing, and support as we prioritize daily-driver stability for our device!
β€36π3π1
crDroid v9.37 - UNOFFICIAL | Android 13
Updated: 07/09/'26
βͺοΈ Download
crDroidAndroid-13.0-20260907-spes-v9.37-Gapps.zip
Changelogs
* ROM: June 2026 security patch
* Switch back aperture camera as default camera app
* Kernel: Upstreamed BPF patches up to 4.19.325-cip135-st19
* Kernel: Implemented memory management fixes for 4GB variants
Notes:
* Find Working keybox config for get play integrity fix
* Dirty Flash users may face pif props detection. to fix it reset the props by reset guide-here with root. if you not rooted then clean install only solution.
Credits
@crDroidAndroid for crdroid base rom source
Project matrixx, Axion, for some features initial implementation and fixes
By @muralivijay9845
Updated: 07/09/'26
βͺοΈ Download
crDroidAndroid-13.0-20260907-spes-v9.37-Gapps.zip
Changelogs
* ROM: June 2026 security patch
* Switch back aperture camera as default camera app
* Kernel: Upstreamed BPF patches up to 4.19.325-cip135-st19
* Kernel: Implemented memory management fixes for 4GB variants
Notes:
* Find Working keybox config for get play integrity fix
* Dirty Flash users may face pif props detection. to fix it reset the props by reset guide-here with root. if you not rooted then clean install only solution.
Credits
@crDroidAndroid for crdroid base rom source
Project matrixx, Axion, for some features initial implementation and fixes
By @muralivijay9845
mega.nz
1.21 GB file on MEGA
β€22π₯1