Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For those about to flash..... I salute you!
With AICP 15 fueled by Android Q.
NOTE: TESTBUILD. SELINUX DISABLED.
Since I build this ROM, I might as well upload it here for other to enjoy.
You should get to know how to flash before you download this (and potentially softbrick your phone). I may create detailed instructions later, but for now just search xda.
The basics are:
ZF6 has 2 slots (A/B) for ROM, Boot, Vendor and many other partitions. To start with we want the same version in both slots. We get that by flashing the full stock ROM two times. Remember: every time you flash a ROM, it will automagically change to the other slot. The recovery(TWRP) will swap slots when rebooting to recovery (but only after flashing a ROM).
Do not change slots yourself, let the installer manage!
Do not wipe system partition or other partitions unless it is specified!
Installing AICP Q:
Initially, you must have Android Q installed and working in both Slot A and B. Verify that it works, then use mauronofrios twrp to flash AICP. In short:
- Get Android Q running on both slots
- Remove all fingerprints from current ROM.
- Remove all locks on lockscreen.
- Boot TWRP 3.3.1-24 Q Unofficial by mauronofrio from your PC (or boot directly to twrp if already installed).
- Flash AICP Q
- Flash TWRP 3.3.1-24 Unofficial Installer by mauronofrio
- reboot to TWRP (this will activate the other slot, where AICP just got installed)
- Optionally Flash gapps
- Optionally Flash magisk if you want root
- Wipe data
- ReBoot to system
Don't panic if things go wrong. I have never seen a device being hard bricked due to wrong flashing.
EXPECT soft bricks if this is your first flash! A/B devices are tricky.
If you are uncertain of anything, make sure you have access to help (I will not be around much).
SOURCE with everything you need to build yourself.
The kernel used is from the LineageOS project. It can be found by following the manifest above or direcly HERE.
DOWNLOAD for Pie
If ^^ is too slow, try here.
HAVE FUN
The official introduction:
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS) we became LineageOS based with some tweaks from AOSP, for Android Pie we based on the "Ground Zero Open Source Project" (GZOSP), and now for Android 10 we are fully based on AOSP
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 14.0
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
(link the best one for your device, there are several variants out there right now, nano/micro GApps from opengapps.org is almost always a good choice though)
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. Xposed is not yet released for android 10.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution and reboot. Or just use the OTA app to preform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to loose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
Q. I installed a bad theme and now I'm getting a bootloop, how do I fix it?
A. In TWRP, flash the substratum rescue zip that's in the substratum folder on the internal storage.
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android 10. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Reboot and set up your device, enable developer settings and in them OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.1 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
Put the Github link to your kernel HERE (mandatory), not posting the kernel source violates the GPL, and also violates the rules on XDA ...
Device tree source:
Put the Github link to your device tree HERE.
Vendor source:
Put the Github link to your used vendor HERE.
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)
The following information is ONLY needed if you are not opening up a devdb thread on XDA!
ROM OS Version: 10.x
Kernel: Linux x.z.y (for example: 3.18.y)
Version Information:
Status: WEEKLY
Release Date: mm-dd-yyyy
You want to see a "normal" night at the "DEV office", click here!!
Hi
thank you VM @teemo for your work. AICP best rom i ever had. i hope i have time to flash it on my 6z as soon™ as possible
any issues you know yet? and how about re-flashing TWRP each time after flashing rom?
Greetings
135Shadowsoul
PS: First
135Shadowsoul said:
Hi
thank you VM @teemo for your work. AICP best rom i ever had. i hope i have time to flash it on my 6z as soon™ as possible
any issues you know yet? and how about re-flashing TWRP each time after flashing rom?
Greetings
135Shadowsoul
PS: First
Click to expand...
Click to collapse
Safety Net need help from Magisk or similar. Will try to fix for next build.
I would love to have Quick Settings to dismiss when using the Camera Tile with gCam.
Asus camera gets slow in pro mode with slow shutter speeds.
Other than that, I don't know what to fix. You tell me :laugh:.
EDIT1: Oh yeah, the Google key need to be reassigned to something more useful...
EDIT2: Not an issue but yes, flash TWRP after the ROM.
teemo said:
Safety Net need help from Magisk or similar. Will try to fix for next build.
I would love to have Quick Settings to dismiss when using the Camera Tile with gCam.
Asus camera gets slow in pro mode with slow shutter speeds.
Other than that, I don't know what to fix. You tell me :laugh:.
EDIT1: Oh yeah, the Google key need to be reassigned to something more useful...
EDIT2: Not an issue but yes, flash TWRP after the ROM.
Click to expand...
Click to collapse
Thank you for this Rom. This seems to be the best Rom for this Device after the first Day of using it.
One little Thing: I am using two Simcards, but in the Statusbar I can see only Simcard 1 and also there is no LTE and Volte Sign.
teemo said:
Safety Net need help from Magisk or similar. Will try to fix for next build.
I would love to have Quick Settings to dismiss when using the Camera Tile with gCam.
Asus camera gets slow in pro mode with slow shutter speeds.
Other than that, I don't know what to fix. You tell me :laugh:.
EDIT1: Oh yeah, the Google key need to be reassigned to something more useful...
EDIT2: Not an issue but yes, flash TWRP after the ROM.
Click to expand...
Click to collapse
Thanks for reply m8,
about EDIT1: is it possible to reassign the key? like on stock rom? or do we need any special app/magisk module/whatever?
is asus camera built in? and any idea how to solve the camera thing you mentioned?
whats the stuff about safetynet? any problem with magisk and hide props conf module?
nnamless said:
Thank you for this Rom. This seems to be the best Rom for this Device after the first Day of using it.
One little Thing: I am using two Simcards, but in the Statusbar I can see only Simcard 1 and also there is no LTE and Volte Sign.
Click to expand...
Click to collapse
I've set mine to show 4G in stead. It works, but only if I'm not on WiFi.
SIM cards are both showing for me, but I have seen some strange things like showing the wrong card. I am currently only using SIM, the other one disabled.
135Shadowsoul said:
Thanks for reply m8,
about EDIT1: is it possible to reassign the key? like on stock rom? or do we need any special app/magisk module/whatever?
is asus camera built in? and any idea how to solve the camera thing you mentioned?
whats the stuff about safetynet? any problem with magisk and hide props conf module?
Click to expand...
Click to collapse
Yes it's possible, micky387 is already doing it for in OmniRom on Q if I'm not wrong.
Asus camera and gallery built in. If I knew how to fix the pro camera I had done it already.
I don't know if this latest build has SN working out of the box, as it just got feb security update. But Safety net is fine with Magisk props module.
I will probably be super slow to fix stuff, but any help is welcomed
Will update OP with links to the source, which I forgot.
IDK if I'm missing something, but when I click the link to download, I'm told access is denied. What's up?
Sraichvold said:
IDK if I'm missing something, but when I click the link to download, I'm told access is denied. What's up?
Click to expand...
Click to collapse
No, I added the wrong dl address, sorry. You can try again now. If still not working, just search for user teemo, then it's easy to find.
Sweeeet. Thank you kindly!
Quote:
Originally Posted by nnamless
Thank you for this Rom. This seems to be the best Rom for this Device after the first Day of using it.
One little Thing: I am using two Simcards, but in the Statusbar I can see only Simcard 1 and also there is no LTE and Volte Sign.
teemo said:
I've set mine to show 4G in stead. It works, but only if I'm not on WiFi.
SIM cards are both showing for me, but I have seen some strange things like showing the wrong card. I am currently only using SIM, the other one disabled.
It works if i install it over the latest LOS 16.0 instead of Stock Pie Rom. Use it now as daily Driver, very good! Thank You
Click to expand...
Click to collapse
nnamless said:
Quote:
Originally Posted by nnamless
It works if i install it over the latest LOS 16.0 instead of Stock Pie Rom. Use it now as daily Driver, very good! Thank You
Click to expand...
Click to collapse
That's good info. Thanks!
Q update in OP.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team Bliss is pleased to present to you
BlissRoms based on Android 10
Our focus is to bring the Open Source community a quality OS that can run on all your devices as a daily driver, syncing your apps + settings + customizations across all platforms you run Bliss on.
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.
Code:
[CENTER][B][COLOR=DeepSkyBlue][SIZE=4][U][URL="https://github.com/BlissRoms"]BlissRoms Sources[/URL][/U][/SIZE][/COLOR][/B]
[B][COLOR=DeepSkyBlue][SIZE=4][U][URL="https://github.com/BlissRoms-Devices"]BlissRoms Device Sources[/URL][/U][/SIZE][/COLOR][/B][/CENTER]
Bliss Device Downloads
TWRP Flashable SourceForge
Fastboot Images
Team Bliss is not responsible in any way for anything that happens to your device in the process of installing
Code:
[B]Please familiarize yourself with flashing and custom rom use before attempting to flash the rom. Please make sure you download the correct version of Bliss for your specific device. The links are labeled clearly.[/B]
[LIST]
[*][B]Make sure you have UNLOCKED BOOTLOADER[/B]
[*][B]Make sure you are on Official MIUI Latest Stock Release ( Do not use any custom modified one)[/B]
[*][B]Download the latest BlissRom package[/B]
[*][B]Boot into recovery[/B]
[*][B]Wipe Data (Else you will be stuck in bootloop)[/B]
[*][B]Flash BlissRom using EU TWRP Recovery[/B]
[*][B] Reboot to System and #StayBlissful :good:[/B]
[*][B]First boot may take up to 1 or 2 minutes. This is due to Gapps and root optimization.[/B]
[B][U][I]Important Notes:[/I][/U][/B]
[*][B] You should be on latest Miui Stock Release for Poco X2[/B]
[*][B] DO NOT FLASH ANY GAPPS SINCE GAPPS ARE INBUILT WITH ROM[/B]
[/LIST][/CENTER]
Code:
[B]If you have a major bug to report that has not been reported already, please take the following steps to report it to us. It will save you and our team quite some time.[/B]
[LIST]
[*][B][COLOR="Red"] DO NOT Report bugs if you're running a custom kernel or you installed Xposed[/COLOR][/B]
[*][B]Download the [URL="https://play.google.com/store/apps/details?id=com.nolanlawson.logcat&hl=en"][COLOR=DeepSkyBlue][U]Catlog[/U][/COLOR][/URL] app from the Play Store.[/B]
[*][B]There is also a donate version which you can purchase to show appreciation.[/B]
[*][B]After downloading the Catlog app, go to the app settings, and change the log level to Debug.[/B]
[*][B]Clear all previous logs and take the exact steps to produce the error you are receiving.[/B]
[*][B]As soon as you receive the error (probably a force close), go straight into Catlog and stop the log recording.[/B]
[*][B]Copy and paste the entire log either to [URL="http://hastebin.com"][COLOR=DeepSkyBlue][U]Hastebin[/U][/COLOR][/URL] or [URL="http://pastebin.com"][COLOR=DeepSkyBlue][U]Pastebin[/U][/COLOR][/URL][/B]
[*][B]Save the log, and copy and paste the link into the forum with a brief description of the error.[/B]
[/LIST]
Code:
[COLOR=DeepSkyBlue][B]
@Jackeagle
@electrikjesus
@Rohan purohit
@rwaterspf1
@Makaveli_da_dev
@ElfinJNoty
@BitOBSessiOn
@customworx
@nilac
@sixohtew
@aclegg2011
@Roger.T
@T.M.Wrath
@kanttii
@rev3nt3ch
@techfreak243
@SuperDroidBond
@USA_RedDragon
@bcrichster
@deadmanxXD
@krittin98
@BlackScorpion
@techexhibeo
@droidbot
@siphonay
@pacer456
@nitin1438
@theGeekyLad
@kunalshah912
@lordarcadius
@AryanAA
[/B]
[/COLOR]
A huge thanks to Chainfire, CM/LineageOS, Android-x86, Jide, @farmerbb & all the other developers who work hard to keep all the great features coming!
We really appreciate all your knowledge & hard work!
About BlissROMs
Team membership consist of and provides:
Training, development opportunities, design opportunities, build servers when available, download servers, design & development software, as well as a stress free team oriented community of professionals and mentors in all fields revolving around Android development. To join our team, please visit either of our websites, and find the Join Team Bliss link.
If someone wants to donate, please do so via this PayPal link:
PayPal Link
WE ARE A U.S. FEDERAL NON-PROFIT ORGANIZATION (501c3)
We receive a small donation each time you make a purchase with “Amazon Smile”:
https://smile.amazon.com/ch/82-3580195https://smile.amazon.com/ch/82-3580195
Notice
The OP and most recent discussions will generally help to answer any questions you will encounter. If not, we will do our best to answer your questions & concerns as soon as possible.
We will also simply direct you to the OP if the answer is contained there. We encourage community minded interactions: users helping fellow users allows Team Bliss to focus on the work involved to make things Blissful.
Please do not ask for ETA's
We will not tolerate any rudeness or anyone being disrespectful in this thread. Moderators, feel free to enforce anything you feel is necessary to stop bad posts
Team Bliss will allow some minor off-topic comments in our development threads. Please post in the general forums for off-topic comments and/or questions. Overall, please keep comments relevant to development, as this better helps you and our teamwhen trying to determine problems that users are having. We appreciate all levels of knowledge in our threads, and therefore we ask that the seasoned members be helpful to those with less knowledge. Most importantly, do NOT troll those with less knowledge than yourself.
Should you feel inclined to not abide by our request, the XDA Moderators may be called in to remove posts. We thank you for adhering to our thread rules.
Code:
[COLOR=DeepSkyBlue][B][U][SIZE=5][URL="https://blissroms.com"]Website[/URL][/SIZE][/U][/B][/COLOR]
[COLOR=DeepSkyBlue][B][U][SIZE=5]Official Platform Links[/SIZE][/U][/B][/COLOR]
[URL="https://www.facebook.com/BlissFamilyOfROMs"]BlissRoms Facebook[/URL]
[URL="https://twitter.com/Bliss_ROMs"]BlissRoms Twitter[/URL]
[URL="https://www.instagram.com/blissroms"]BlissRoms Instagram[/URL]
[URL="https://t.me/Team_Bliss_Community"]BlissRoms Telegram[/URL]
Thank you for using Bliss! And as always: #StayBlissful
XDA:DevDB Information
BlissRoms, ROM for the Xiaomi Poco X2
Contributors
jackeagle
Source Code: https://github.com/BlissRoms-Devices/android_kernel_xiaomi_sm6150
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Miui Stock Official V11.0.6.0
Version Information
Status: Stable
Current Stable Version: v12.10
Stable Release Date: 2020-04-02
Created 2020-04-02
Last Updated 2020-07-27
Changelogs and Releases
Known Issues
- So far none! You tell me if any
Installation
Coming from Stock / Other Rom's
- Unlock Bootloader
- Wipe Data else you will face bootloop
- Install Bliss Zip using EU Recovery (Permanent)
- Reboot to System and allow it boot completely (Bliss builds have inbuilt gapps)
- Set up device and then reboot to recovery and install Magisks if needed
Already on BlissRoms
- Download BlissRoms Zip
- Flash it via TWRP Recovery
- Reboot to system
- Set up device and then reboot to recovery and install Magisks if needed
Fastboot Installation Instructions
Stock recovery is required. Restore stock recovery if you have TWRP installed.
PC with the latest fastboot is required. Download fastboot from here.
Download all files from the link above and extract it to plain "img" files.
Enter fastboot mode by holding down Volume-down and Power button upon rebooting.
The device will show "FASTBOOT" with a blue font.
Enter fastbootd mode by entering the following:
Code:
fastboot reboot fastboot
The device will show "FASTBOOTD" with a yellow font.
Flash the images by entering the following:
Code:
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash product product.img
fastboot flash system system.img
fastboot flash boot boot.img
This will take about 2 minutes.
Enter recovery by entering the following:
Code:
fastboot reboot recovery
Use the stock recovery and wipe data
Reboot and enjoy
Thank you for urs hard-work @jackeagle
What are you referring to by the European Union TWRP? Is it that 128MB Chinese TWRP that you’re talking about?
Ya_SG said:
What are you referring to by the European Union TWRP? Is it that 128MB Chinese TWRP that you’re talking about?
Click to expand...
Click to collapse
So far i have tested with EU Version of TWRP and has worked fine without any issues
From next release i will be releasing Fastboot images with zip so that if anyone wants to use fastboot method they can use those
Thanks mate nice work!
Nice Work!!
Few things, First You can enable Notification LED somehow, it is enabled in AOSiP ROM. And do you know when SELinux be enforcing and it will pass SafetyNet?? It is working good without any major issues!
Jyotirmay Goldsmith said:
Nice Work!!
Few things, First You can enable Notification LED somehow, it is enabled in AOSiP ROM. And do you know when SELinux be enforcing and it will pass SafetyNet?? It is working good without any major issues!
Click to expand...
Click to collapse
LED Notification works on Bliss too and Selinux is currently Enforcing.
Regarding SafetyNet i will try to sort it out in next build its mostly from Poco side issue. GPay works fine
jackeagle said:
LED Notification works on Bliss too and Selinux is currently Enforcing.
Regarding SafetyNet i will try to sort it out in next build its mostly from Poco side issue. GPay works fine
Click to expand...
Click to collapse
OH.. Thank You for reply, I couldn't find LED working... GPay was also not working... maybe cause I installed Magisk... Will try after uninstalling Magisk maybe!
---------- Post added 3rd April 2020 at 12:15 AM ---------- Previous post was 2nd April 2020 at 11:40 PM ----------
Also, Can you make the camera cutouts separate? I reinstalled the ROM, can confirm, LED not working while charging. Half the settings are greyed out. Ambient Display is not working, double-tap to raise not working, No option to hide HD; for VoLTE enabled(hid through tweaks ). Other than this it's working pretty darn cool!
jackeagle said:
So far i have tested with EU Version of TWRP and has worked fine without any issues
From next release i will be releasing Fastboot images with zip so that if anyone wants to use fastboot method they can use those
Click to expand...
Click to collapse
Could you link the EU version of TWRP here? Since I don't find it anywhere.
I did everything as said.. I installed Poco X2 latest ROM, went into default recovery and wiped all data then i went into twrp chinese version then flashed this ROM as instructed then when i boot my device shows white screen for a seconds and turns off. I can't boot to twrp either.. basically my device is bricked. So i don't know whats going on and also what is this EU twrp? sorry i am not being clear here.
This doesn't boot.
- I was on the latest stock MIUI. (11.0.4)
- Booted into the Chinese TWRP for Redmi K30.
- Wiped data (did not format) Edit: Formatting data doesn't do anything either.
- Copied the ROM package to internal storage and flashed it.
Now whenever I try to reboot it tries to boot into TWRP and shows a white screen and then goes black instead.
Ya_SG said:
This doesn't boot.
- I was on the latest stock MIUI. (11.0.4)
- Booted into the Chinese TWRP for Redmi K30.
- Wiped data (did not format) Edit: Formatting data doesn't do anything either.
- Copied the ROM package to internal storage and flashed it.
Now whenever I try to reboot it tries to boot into TWRP and shows a white screen and then goes black instead.
Click to expand...
Click to collapse
prabin__ said:
I did everything as said.. I installed Poco X2 latest ROM, went into default recovery and wiped all data then i went into twrp chinese version then flashed this ROM as instructed then when i boot my device shows white screen for a seconds and turns off. I can't boot to twrp either.. basically my device is bricked. So i don't know whats going on and also what is this EU twrp? sorry i am not being clear here.
Click to expand...
Click to collapse
Ya_SG said:
Could you link the EU version of TWRP here? Since I don't find it anywhere.
Click to expand...
Click to collapse
First of all i own this device so without testing myself i wouldnt release here. Secondly if you are coming from Miui Stock u have to format data wipe wont work it will just reboot back to recovery or fastboot.
EU Version TWRP cannot be linked on XDA due to GPL Violation as TWRP source comes under GPL Chinese / EU version have not released its sources hence we cannot link that TWRP here. The one i'm using is POCO-X2_TWRP-TBCN.img.
Next update will have fastboot images along with zip so that those who want to go by fastboot method they can do so
Steps what i had done since i was on 11.04 Global was
- Flashed 11.06
- Flashed TWRP via fastboot
- Booted Miui (Didnt setup or anything)
- Rebooted to TWRP
- Format Data (This will wipe off internal storage)
- Reboot to recovery
- Flashed Bliss zip
- Reboot and Done.
Waiting for fastboot images here.
I can't trust unknown source things.
thanks for your hard work，this ROM is very good，but could you fix the safetynet please？
Really very feature full and stable rom. Fan of ur work bro
All good. Just one simple problem. There is no switch to toggle notch and display hz.
Sometimes the display goes to 60hz idk why.
But to fix that i always do restart and wolla all good.
I know its an initial build. No worry
Loved this rom and ur work @jackeagle
Martensite said:
Waiting for fastboot images here.
I can't trust unknown source things.
Click to expand...
Click to collapse
Download official 11.0.4 fw and 11.0.6 OTA zip
Install fw followed by ota
Nope OP sir, this does not boot at all. I have tried exactly what u said the result is same. This ROM does not boots up, i keeps showing white screen for a second and goes blank again and again. In other words this hard bricks the phone you cant do anything except flashing stock rom from MI-Flash. So thats it, i dont know about how some of the people or even you got it booted successfully but i can't. I am thinking its because of proper TWRP not being available for Poco X2 which could replace stock mi-recovery permanently. Yes me including lot of people can't install TWRP permanently on Poco X2. This is a huge bummer.
ALSO, every other custom ROM boots up for me but this does not no matter how many times i try. So i think OP sir should try and fix whats going on for all of the users and update the ROM file again....
prabin__ said:
Nope OP sir, this does not boot at all. I have tried exactly what u said the result is same. This ROM does not boots up, i keeps showing white screen for a second and goes blank again and again. In other words this hard bricks the phone you cant do anything except flashing stock rom from MI-Flash. So thats it, i dont know about how some of the people or even you got it booted successfully but i can't. I am thinking its because of proper TWRP not being available for Poco X2 which could replace stock mi-recovery permanently. Yes me including lot of people can't install TWRP permanently on Poco X2. This is a huge bummer.
ALSO, every other custom ROM boots up for me but this does not no matter how many times i try. So i think OP sir should try and fix whats going on for all of the users and update the ROM file again....
Click to expand...
Click to collapse
Well then you are either using wrong firmware or I m not aware of it what steps you are doing. because you can clearly see up there they have used and booted it fine so nothing on rom side issue but your steps the way you are attempting to install. If you are using some custom skymi firmwares then it wont boot. Like i mentioned in OP you have to be on Global firmware release of Poco X2 and you have to format data if you are coming from MIUI. There is nothing wrong in ROM as if it was then it should not boot on my device and so as other devices.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-R with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
Pixel Experience Team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 16.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Google Apps:
We recommend MindTheGapps as it has been thoroughly tested and it works well with the ROM, some other minimal GApps packages still have issues, however feel free to try other GApps if you want to, just try MindTheGapps if you have any GApps related issues
MindTheGapps: https://androidfilehost.com/?w=files&flid=322935
Mirror: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases these apps include proprietary libs/code and cannot be included in the device trees on Github or we risk having the ROM banned from Github. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from github and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behavior on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android R. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
On Clean Flash: mandatory for first install !!!At the beginning, if you are on Stock OOS 11 ROM with locked bootloader, please follow the instructions for unlocking bootloader here: https://wiki.lineageos.org/devices/kebab/install
1. Download the ROM and GApps to your PC with proper adb & fastboot setup.
Also download to your PC kebab-recovery.img from HERE
2. Boot to bootloader and run in cmd (windows) / terminal (linux)
fastboot flash recovery kebab-recovery.img
4. Boot to recovery. Tap on Factory Reset (this will erase everything on your device) then return to main menu
3. Connect your device to your PC and tap on Apply Update -> Apply from ADB and
4. Flash the ROM zip file using
adb sideload aicp_kebab_r-16.1-WEEKLY-{date}.zip
5. Once its finished, reboot to recovery to flash the GApps (optional, needed for e.g. Google Playstore to work). This is mandatory becoz will switch automatically current slot and will flash GAPPS.
Once it boots to recovery, tap on Apply Update -> Apply from ADB then run
adb sideload GAPPS.zip
6. Reboot and set up your device.
7. Reboot back into recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The main workflow for flashing via recovery:
reboot to recovery -> adb sideload ROM.zip -> reboot recovery -> adb sideload GAPPS.zip -> reboot to system
Click to expand...
Click to collapse
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 21.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
Go to Aicp Extras -> Update Centre then install new Weekly Build.
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source: We are building Neutrino Kernel adopted to our sources with permission by Kernel Dev
GitHub - AICP/kernel_oneplus_sm8250
Contribute to AICP/kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Kebab Device tree source:
GitHub - AICP/device_oneplus_kebab
Contribute to AICP/device_oneplus_kebab development by creating an account on GitHub.
github.com
Common Device tree source:
GitHub - AICP/device_oneplus_sm8250-common
Contribute to AICP/device_oneplus_sm8250-common development by creating an account on GitHub.
github.com
Vendor source:
AICP/proprietary_vendor_oneplus
Contribute to AICP/proprietary_vendor_oneplus development by creating an account on GitHub.
github.com
GAPPS source:
Semavi Ulusoy / android_vendor_gapps · GitLab
GitLab.com
gitlab.com
Kernel source: We are building Netrino Kernel adopted to our sources with permission by Kernel Dev.
GitHub - AICP/kernel_oneplus_sm8250
Contribute to AICP/kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Device tree source:
GitHub - AICP/device_oneplus_kebab
Contribute to AICP/device_oneplus_kebab development by creating an account on GitHub.
github.com
Common device tree source:
GitHub - AICP/device_oneplus_sm8250-common
Contribute to AICP/device_oneplus_sm8250-common development by creating an account on GitHub.
github.com
Vendor source:
AICP/proprietary_vendor_oneplus
Contribute to AICP/proprietary_vendor_oneplus development by creating an account on GitHub.
github.com
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Join us on our Discord Channel
Contributors:
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)
Information:[/U[
ROM OS Version: 11.1
Kernel: Linux 4.19.176 (for example: 4.19.y)
ROM {Firmware|Vendor} Latest Stock Required:
Status: {STABLE}
Release Date: 28-02-2021
You want to see a "normal" night at the "DEV office", click here!!
semdoc said:
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-R with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
@LuK1337 and LineageOS Team
@maxwen and the rest of the OmniRom Team
@chandra1.jd from Pixel-Experience Team
@firebird11 from crDroid Android Team
DU team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 16.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Unofficial builds can be found on 2nd post.
Google Apps: Included in ROM. Extracted from latest OnePlus 8 Pro dump available at: https://git.rip/dumps/oneplus/oneplus8pro
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behavior on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android R. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
GAPPS are included in ROM. As we still don't have TWRP for eleven builds, flashing process is a "little bit" different than usual.
If you are comming from Stock ROM.
** Be sure you have adb enabled from Developper Settings
** Download AICP Recovery from HERE
** Boot to Download mode.
$ fastboot flash recovery recovery.img
** Now boot to recovery
-- 1. Factory Reset
-- 2. Apply Update -> Apply from ADB
-- 3. flash your build using adb sideload ROM.zip from your PC
If you are comming from other Custom ROM:
** boot to recovery
-- Factory Reset
-- Apply Update -> Apply from ADB
-- flash your build using adb sideload ROM.zip from your PC. Please note that it will ends with following error: "adb: failed to read command: Success" Ignore it.
-- Reboot and Enjoy !!!
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
For flash using the built-in OTA app: Till we start official builds from AICP servers:
** Connect your device, enable USB debugging and Adb Root under Settings -> Developper Options
** move the downloaded build to your internal sdcard
** Open cmd window (for Windows) or terminal (for Linux systems) - make sure you have adb drivers installed !!!
** $ adb root
$ adb shell setenforce 0 (your device will switch to Permissive selinux mod till Updater finishes flashing local update)
** Go to AicpExtras -> Update Center -> Click on 3 dots on right upper corner -> Choose File.. -> Choose your builld from local storage -> Start update
** After reboot your device will boot in Enforcing Selinux mode again.
or Flash via adb sideload:
** reboot to recovery
** enable ADB and flash downloaded build using adb sideload
** Please note that it will ends with following error: "adb: failed to read command: Success" (becoz of recovery itself). Ignore it.
** Reboot and Enjoy !
No need to flash clean on every update from older builds.
Currently supported Root Solution: Only ADB ROOT !!!
Magisk versions >= Magisk 21.1 zip is the key.
ADB Root is working fine, but you can flash, test and report your experience with Magisk
** Check 2nd post for further information.
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source: We are building Netrino Kernel adopted to our sources with permission by Kernel Dev
GitHub - AICP/kernel_oneplus_sm8250
Contribute to AICP/kernel_oneplus_sm8250 development by creating an account on GitHub.
github.com
Kebab Device tree source:
GitHub - AICP/device_oneplus_kebab
Contribute to AICP/device_oneplus_kebab development by creating an account on GitHub.
github.com
Common Device tree source:
GitHub - AICP/device_oneplus_sm8250-common
Contribute to AICP/device_oneplus_sm8250-common development by creating an account on GitHub.
github.com
Vendor source:
AICP/proprietary_vendor_oneplus
Contribute to AICP/proprietary_vendor_oneplus development by creating an account on GitHub.
github.com
GAPPS source:
Semavi Ulusoy / android_vendor_gapps · GitLab
GitLab.com
gitlab.com
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Join us on our Discord Channel
Contributors:
(mention all the devs who have contributed to your device tree, kernel, vendor, etc,
only mention the main ones though, probably the top four or so, otherwise this list will be a mile long xD)
Information:[/U[
ROM OS Version: 11.1
Kernel: Linux 4.19.176 (for example: 4.19.y)
ROM {Firmware|Vendor} Latest Stock Required:
Status: {STABLE}
Release Date: 28-02-2021
You want to see a "normal" night at the "DEV office", click here!!
Click to expand...
Click to collapse
The download link doesn't have the link for OnePlus 8T
New build guys
10.04.2021 UPDATE
Download aicp_kebab_r-16.1-WEEKLY-20210410.zip from HERE.
Changelog: link HERE.
What's new:
1. April '21 ASB merged
2. Added ALipay fingerprint payment support
3. Screenbrightness fixes for all 3 devices
4. Many fixes including SafetyNet (fixed again)
All feedbacks are appreciated, as always.
Dirty flash is enough. Flash it via Updater or adb sideload in recovery.
Or.... you can flash aicp_kebab_r-16.1-FASTBOOT-20210410.zip in fastbootd mode using
$ fastboot update aicp_kebab_r-16.1-FASTBOOT-20210410.zip
Download the build from HERE
Cheerz
-----------------------------------------------------------------------------------------------------------------------------
As we still have issues with sideload installation, with big thanx to @RayInkube for his patience with testing, I want to introduce a temporary solution for flashing our kebab builds.
Please download kebab-recovery.img from HERE and aicp_kebab_r-16.1-FASTBOOT-20210404.zip build from HERE
Then...
1. Boot to Download mode.
2. fastboot flash recovery kebab-recovery.img
3. Boot to recovery
3. Factory reset (for clean flash). Not needed if you will flash dirty over our previous builds.
4. switch to fastbootd mode
5. fastboot update aicp_kebab_r-16.1-FASTBOOT-20210404.zip
6. fastboot reboot.
Enjoy !!!
--------------------------------------------------------------------------------------------------------------
For those who want to root their devices:
Download Magisk 21.4 zip: link HERE
Please go for this once you are fully booted.
** boot to recovery
** flash via adb sideload magisk.zip:
** reboot.
** Note that you HAVE to do this on every update.
** Safety Net is fixed !!!
Enjoy !!
------------------------------------------------------------------------------------------------------------------
Which Camera we can use:
1. Using this Camera: GCam_7.3.018_Urnyx05-v2.1_Wichaya_V3.1.1_snapcam.apk
2. Also I have thix xml file under GCam/Configs7 : nrG Wichaya 7.3.018_v3.1.1.xml
_idiosyncratic_313 said:
The download link doesn't have the link for OnePlus 8T
Click to expand...
Click to collapse
2nd post dude..
The download link will work when we start official builds... Soon I hope
semdoc said:
AICP recovery: link HERE
--------------------------------------------------------------------------------------------------------------
Initial Build:. aicp_kebab_r-16.1-WEEKLY-20210228.zip link HERE.
--------------------------------------------------------------------------------------------------------------
SAfetyNet fixed build will be posted later today
-------------------------------------------------------------------------------------------------------------
For those who want to root their devices:
Download Magisk 21.4 zip: link HERE
** boot to recovery
** flash via adb sideload magisk.zip:
** reboot.
** Note that you may need to do this on every update.
** Safety Net is broken currently !!!
Enjoy !!
Click to expand...
Click to collapse
Thanks!!
3rd post updated with the link for new, updated build:
** SafetyNet fixed:
aicp_kebab_r-16.1-WEEKLY-20210301.zip link HERE
-------------------------------------------------------------------------------------------------------------
Does this rom have faceunlock?
Does this ROM has OnePlus Settings and DC dimming?
yyws2012 said:
Does this ROM has OnePlus Settings and DC dimming?
Click to expand...
Click to collapse
Yes.
abalam said:
Does this rom have faceunlock?
Click to expand...
Click to collapse
Nope. This feature needs proprietary libs from sone manifacturers which may cause violation of GPL.
Great Day!
Is the weekly build has GMS or Pixel Default apps? Or AOSP one?
Looking forward to Flashing AICP on my 8T.
EmperorEye said:
Great Day!
Is the weekly build has GMS or Pixel Default apps? Or AOSP one?
Click to expand...
Click to collapse
GAPPS are included in the build. Except Markup Google & SetupWizard (they are extracted from latest RedFin dump), all apps are extracted from latest Op8 Pro dump.
Well... After trying all the other roms for the 8t i went back and decided to stay on OOS.
But now I'm tempted
@semdoc hi. I would like to ask you if it's possible to you make feature builds working on the other 8 series. I like very much aicp rom and I have the 8P version. It would be very nice and cool to have this rom to all 8series. I'm sure many people would join to it. Please think about it ( and make it )
Thanks keep strong, healthy and keep doing your stuff
alex moymoy said:
@semdoc hi. I would like to ask you if it's possible to you make feature builds working on the other 8 series. I like very much aicp rom and I have the 8P version. It would be very nice and cool to have this rom to all 8series. I'm sure many people would join to it. Please think about it ( and make it )
Thanks keep strong, healthy and keep doing your stuff
Click to expand...
Click to collapse
which version are you talking about ? Oneplus 8 Pro ? Or instantnoodle (OnePlus 8) ?
semdoc said:
which version are you talking about ? Oneplus 8 Pro ? Or instantnoodle (OnePlus 8) ?
Click to expand...
Click to collapse
8Pro. I wrote it in my last post (8P). You missed it
Delete. Gonna try it. Tnx for the rom
can use pixel rom installer?
kuto232 said:
can use pixel rom installer?
Click to expand...
Click to collapse
Dont know what this is... Why do you need it ?
Just go to recovery and flash using adb sideload ROM.zip....
Everything working on my 8t..very smooth
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has addressed it already. Especially if you're even close to new at this.
2) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
3) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
You should start off with the latest Android 11 OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery by flashing the boot.img using
Code:
fastboot flash boot enchilada-YYYYMMDD-HHMM-boot.img
followed by booting to recovery through the bootloader.
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-enchilada-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
Great ROM!
Running really well for the past day.
However, video playback is not working on instagram. Thanks for the ROM.
emil_515 said:
Great ROM!
Running really well for the past day.
However, video playback is not working on instagram. Thanks for the ROM.
Click to expand...
Click to collapse
Thanks for the feedback, will take care of the videoplayback ASAP. No idea how I missed that during testing, sorry.
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
Myself5 said:
Found and fixed the issue with video playback in Apps. New builds coming within the next 2 hours.
Click to expand...
Click to collapse
AOD While Charging Available?
i am on lineageos18.1 rom is there any way to switch to this rom without using MS download tools ?
I mean switch to this rom and just use twrp recovery
Thank a lot
kecodoc said:
i am on lineageos18.1 rom is there any way to switch to this rom without using MS download tools ?
I mean switch to this rom and just use twrp recovery
Thank a lot
Click to expand...
Click to collapse
Format data and flash Carbon. If you want to go the safer router, use official TWRP, flash the latest stable OxygenOS zip, reboot TWRP (to switch slots) flash the zip again (to have it installed on both slots), then flash Carbon.
Wipe data (/data, no need for factory reset and format the internal storage) somewhere in between and you're good to go.
Myself5 said:
Format data and flash Carbon. If you want to go the safer router, use official TWRP, flash the latest stable OxygenOS zip, reboot TWRP (to switch slots) flash the zip again (to have it installed on both slots), then flash Carbon.
Wipe data (/data, no need for factory reset and format the internal storage) somewhere in between and you're good to go.
Click to expand...
Click to collapse
while on lineageos rom like now can i use twrp recovery and flash the latest oxygenos through 2 slots A and B without fear of errors ?
i am using twrp 3.4.0.0
Thank you very much
kecodoc said:
while on lineageos rom like now can i use twrp recovery and flash the latest oxygenos through 2 slots A and B without fear of errors ?
i am using twrp 3.4.0.0
Thank you very much
Click to expand...
Click to collapse
Yes, but like @Myself5 said, much better if you use TWRP for flashing the latest "STABLE" OOS build. And personally, this is what I always use as well.
And use the latest (3.5.2_9-0) "official" TWRP instead of your 3.4.0.0.
Todays update will "require" Oxygen 11 as a base ROM. 10 will still work, but dash charging and some bluetooth devices will not work with it.
If you upgrade your Base ROM to 11, these will work again.
The best way to upgrade without losing data is:
Download latest Oxygen zip, TWRP, Carbon zip, and optional Gapps/MicroG.
Fastboot boot to recovery
Flash Oxygen OS zip
reboot to bootloader, fastboot boot TWRP
flash oxygen zip again
without rebooting, flash the latest Carbon zip
Optional: reboot to bootloader, fastboot boot TWRP
Optional: Flash Gapps/MicroG
Reboot to system and find yourself on an updated Carbon installation
Make sure that you do NOT reboot to Oxygen in between as that could cause issues afterwards.
If you want to go the fully "clean" route, clean install the latest Oxygen (to both slots) and clean install Carbon. The above method has worked fine for me so far though
The OP has been updated with the new requirements.
Myself5 said:
Todays update will "require" Oxygen 11 as a base ROM. 10 will still work, but dash charging and some bluetooth devices will not work with it.
If you upgrade your Base ROM to 11, these will work again.
The best way to upgrade without losing data is:
Download latest Oxygen zip, TWRP, Carbon zip, and optional Gapps/MicroG.
Fastboot boot to recovery
Flash Oxygen OS zip
reboot to bootloader, fastboot boot TWRP
flash oxygen zip again
without rebooting, flash the latest Carbon zip
Optional: reboot to bootloader, fastboot boot TWRP
Optional: Flash Gapps/MicroG
Reboot to system and find yourself on an updated Carbon installation
Make sure that you do NOT reboot to Oxygen in between as that could cause issues afterwards.
If you want to go the fully "clean" route, clean install the latest Oxygen (to both slots) and clean install Carbon. The above method has worked fine for me so far though
The OP has been updated with the new requirements.
Click to expand...
Click to collapse
Bro, Please mention OOS Version in 2nd and 4th step..
New people will still ask so make it clear..
Hey! I just wanted to thank you for this amazing ROM, works like a charm!
However, one feature I do miss a lot from OOS is the Alarm booting up the phone itself. I've read a bit on the topic and i know it's not that simple to implement it, but would it be possible to add such a feature down the line?
Also I can remember CR having Pie Controls implemented back in the day but I can't find them on this ROM. Has this feature been stripped?
Myself5 said:
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has addressed it already. Especially if you're even close to new at this.
2) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
3) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
You should start off with the latest Android 11 OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery by flashing the boot.img using
Code:
fastboot flash boot enchilada-YYYYMMDD-HHMM-boot.img
followed by booting to recovery through the bootloader.
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-enchilada-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
Click to expand...
Click to collapse
if i update through local update means did it will wipe my twrp to carbon recovery? and will it remove my root?
Myself5 said:
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled ROMs, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best ROM we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub...
What is R?
Our release of Android 11, titled CR-9.0.
It provides you with the features you need while keeping the focus on delivering an elegant, smooth, and well polished experience. R delivers a set of unique features, like a system-wide font engine that also allows for applying fonts on user apps while supporting user fonts through custom APKs generated on fonts.carbonrom.org. We are confident you'll love it, and there's many more things to discover
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! As always, make sure to do backups.
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has addressed it already. Especially if you're even close to new at this.
2) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
3) Join our Discord server or Telegram group! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Install Instructions:
You should start off with the latest Android 11 OxygenOS stable build on both slots and then proceed to flash Carbon.
The easiest way to do that is by installing the latest Version and then copy it by flashing the copy-partitions script made by LineageOS in the recovery. (See install Instructions for the recovery)
The recommended way to install is using the CarbonRecovery linked below.
Download the ROM and optionally GApps, reboot to recovery by flashing the boot.img using
Code:
fastboot flash boot enchilada-YYYYMMDD-HHMM-boot.img
followed by booting to recovery through the bootloader.
Sideload the ROM. (Apply Update -> Apply from ADB -> Connect to PC ->
Code:
adb sideload CARBON-CR-9.0-R-WEEKLY-enchilada-YYYYMMDD-HHMM.zip
Reboot recovery (to switch between slots)
Flash GApps/MicroG through sideload like above (optional)
Factory reset -> Format data/factory reset (Make sure to have a backup of your data)
Done
Followup builds can be updated through the builtin CarbonDelta Updater or by dirtyflashing.
Download
Download CarbonRecovery
Homepage
Join the CarbonROM Discord server
Meet us on Telegram
GitHub
Kernel source
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
Click to expand...
Click to collapse
incoming call sound is not hearing. my speeker is ok and its not on mute condition also.... anyone please help pls
vyshnav said:
if i update through local update means did it will wipe my twrp to carbon recovery? and will it remove my root?
Click to expand...
Click to collapse
TWRP will be gone, Magisk has, depending on how it was installed, different ways to survive an OTA.
vyshnav said:
incoming call sound is not hearing. my speeker is ok and its not on mute condition also.... anyone please help pls
Click to expand...
Click to collapse
Did you make sure you had installed the latest stock builds of Android 11 on both slots before flashing Carbon?
P.S. please don't qoute the entire OP for a 1 line question, it clutters up the thread a lot.
Myself5 said:
TWRP will be gone, Magisk has, depending on how it was installed, different ways to survive an OTA.
Did you make sure you had installed the latest stock builds of Android 11 on both slots before flashing Carbon?
P.S. please don't qoute the entire OP for a 1 line question, it clutters up the thread a lot.
Click to expand...
Click to collapse
yes i installed letest on both slots before and sry for qoute
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
AICP
Android Ice Cold Project
AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!!
Until Android Lollipop, the ROM has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM.
With the re-brand of CM to LineageOS (LOS), we became LineageOS based with some tweaks from AOSP and then changed to be based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
We changed again for Android Q-R with a base of AOSP repositories and some additions from LineageOS for device-specific repositories.
If there are any bugs we will sort them out if it concerns our codebase. This ROM isn't LineageOS supported, so there is no need to report errors/bugs to them!!
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications and if
* you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
*
*/
Feature list (rough overview)
In the beginning we would like to thank:
GZOSP team
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
Resurrection Remix team
AOSiP team
Community
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
We are paying for servers that build weeklies and everything that comes with this, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 16.1
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
Starting with AICP 15 we will be storing a copy of the most recent release here: https://media.aicp-rom.com/vault/.
Full Changelog link: https://dwnld.aicp-rom.com/
(Just click the changelog button next to the download link in the list of builds available for your device)
Camera mods are not and will not be supported
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look here to see what day your device is built on.
Q. Does this ROM support custom kernels officially?
A. No. You can still use them, but the discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Does this ROM include GApps or do I have to flash them separately?
A. No, we do not include prebuilt GApps, because of possible licensing issues with Google Software and because some users do not want GApps preinstalled as they want to use alternative services like MicroG or just prefer flashing a GApps "flavor" of their liking.
Q. Does this ROM use the camera or gallery app from stock?
A. It depends on the device. In most cases these apps include proprietary libs/code and cannot be included in the device trees on Github or we risk having the ROM banned from Github. In this case, we might try to make them installable (separate from the ROM zip), or we might provide a version of these apps with the ROM that doesn't include any proprietary libs. It's also sometimes the case that these apps are simply not included because we didn't feel the need to do so for the device in question.
Q. Does this ROM have Extended/Scrolling screenshot?
A. No, extended screenshot was implemented using an app extracted and modified from manufacturer firmware/system images and is proprietary as well. It led to the closing of many ROM's sources on GitHub.
Q. Does this ROM have FaceUnlock?
A. No, FaceUnlock was also an app extracted and modified from some manufacturers. Even Google removed the Trusted Face (FaceUnlock) feature for security reasons on Android 9.0/10.x. Adding the modified feature did the same to ROM sources as described above.
Q. Can you add (insert favorite weather provider)?
A. No, we cannot add more weather providers as the implementations change and we (the ROM) now have to pay for most services, and that is not cheap, so we decided to use the best free service that we could find, the only way to add your own is for users to apply for their own API key to use their preferred service.
Q. Does this ROM have private official builds with the above proprietary libs included?
A. No, we believe in open source software, this way users know what's in the build and can replicate it themselves, all official builds are built on our build servers using the public sources from github and no one can (or would) add their own private sources to the build.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the flashing instructions...
Q. Can the builds be dirty flashed over each other?
A. Yes, this is the usual behavior on flashing a new official build by (or using) the build-in updater service.
Q. How do I 'dirty flash' builds?
A. Wipe the System, Cache, and ART/Dalvik cache. Flash the ROM, GApps (only needed if you wipe the system), your preferred root solution, and reboot. Or just use the OTA app to perform that task for you.
Q. How do I flash kernel builds?
A1. If it's a .img file, boot into TWRP and go to the install page in TWRP, in the bottom right corner select "install image", select the desired kernel, then select "boot" as the destination, then swipe to flash, then go back to the install screen and install your root method again, if you don't want to lose root and reboot.
A2. If it's a flashable ZIP, you can flash it together with a ROM update or separately. Go to the install page in TWRP, choose the kernel zip (or add it to the flash queue right after the ROM zip). Then add your root method to the queue if you don't want to lose root. Now swipe to flash and reboot afterward.
Using the ROM:
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat AND the model name. (Note: Please just link the logcat from your GDrive, Dropbox, etc. Do not post the content here. Thanks.)
Q. How do I get a logcat, what type should I get, and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (Root needed).
A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the others section on the AICP Extras main page.
The ROM should contain everything you need to enjoy Android R. You don't need to install any Add-ons, simply download the latest ROM and GApps, then follow the flashing instructions and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM zip file.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup (or with any backup/restore app) as this can cause stability issues that are very hard to debug, restoring regular apps is fine though.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash for the first time:
(Again: Don't do it if you don't know!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, and Data (you might need to format the data partition!).
4. Flash the ROM zip file.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work)
6. Reboot and set up your device, enable developer settings and in them, OEM unlock/Advanced reboot/USB tethering.
7. Reboot back into TWRP recovery.
8. Flash the root solution of your choice (optional).
9. Reboot your device.
The procedure may vary from device to device and is a bit different on system updates!
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once! This might differ on AvB Devices.
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.4 don't usually need to be flashed on every dirty flash.
Depending on the device, you may need to flash it every time, unless your maintainer says otherwise, you should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
TWRP recovery is needed to be able to flash using the built-in OTA app.
Please make sure that you are on the latest TWRP recovery, keep in mind that this could also be an unofficial version!
On encrypted devices, you will have to enter your PIN/password in TWRP before the process starts.
If you want to contribute to AICP, or if you want to see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
GitHub - AICP/kernel_motorola_msm8953 at r11.1-albus
Contribute to AICP/kernel_motorola_msm8953 development by creating an account on GitHub.
github.com
Device tree source:
GitHub - AICP/device_motorola_albus at r11.1
Contribute to AICP/device_motorola_albus development by creating an account on GitHub.
github.com
Vendor source:
Follow this guide if you want to extract the vendor blobs
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
AICP Download page for official builds and media content
AICP Discord Community
AICP Telegram channel for server notifications on official builds
Contributors:
erfanoabdi, npjohnson, jeferson1979, jarlpenguin
Information:
ROM OS Version: 11.x
Kernel: Linux 3.18.140
ROM Firmware required: ALBUS_PPS29.133
Status: STABLE
Release Date: 09-18-2021
You want to see a "normal" night at the "DEV office", click here!!
Reserved
What's your idle battery drain? Overnight I have 5-6% with disabled internet. In other roms it's around 2% so not great. Is there any setting that can cause it? I have mostly default settings, "pocket mode" disabled, no apps installed (just trying it out).
Hey guys good work! i've installed on my old moto z2 play and it works great! only a question... when i attach the moto mod soundboost the JBL app is crashing always... any ideas? Thanks
giobbe71 said:
Hey guys good work! i've installed on my old moto z2 play and it works great! only a question... when i attach the moto mod soundboost the JBL app is crashing always... any ideas? Thanks
Click to expand...
Click to collapse
You need this APK for it to work; because it's designed to only work in the original stock rom it needs some modifications to work under customs
Great!!! It Works!!! Thank you
Hi!
On my device (motorola moto z2 play) I have the following rom installed: [ROM] [10.0] [OFFICAL] AICP 15.0 [Albus]:
[DISCONTINUED][ROM][10.0][OFFICAL] AICP 15.0 [Albus]
AICP Android Ice Cold Project AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!! Until Android Lollipop, the...
forum.xda-developers.com
My question is: Can said rom be updated by installing this rom?
Sorry for my bad English
No, unfortunately unlike OEM's we can't give support for version upgrades; you'd have to clean flash to install this update
5130walter said:
Hi!
On my device (motorola moto z2 play) I have the following rom installed: [ROM] [10.0] [OFFICAL] AICP 15.0 [Albus]:
[DISCONTINUED][ROM][10.0][OFFICAL] AICP 15.0 [Albus]
AICP Android Ice Cold Project AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago (2012) and since then has evolved into a mature ROM with the BEST community that you can find!!! Until Android Lollipop, the...
forum.xda-developers.com
My question is: Can said rom be updated by installing this rom?
Sorry for my bad English
Click to expand...
Click to collapse
marcost22 said:
No, unfortunately unlike OEM's we can't give support for version upgrades; you'd have to clean flash to install this update
Click to expand...
Click to collapse
Is it necessary to flash the original android pie firmware before installing this rom?
5130walter said:
Is it necessary to flash the original android pie firmware before installing this rom?
Click to expand...
Click to collapse
If you were using AICP 15.0, then no; you are already using it. If you are coming from Android 8.0 or a custom rom based on it, then yes
Moto Mods 360 Camera does not work.
Is there any way?
leonthorn12 said:
Moto Mods 360 Camera does not work.
Is there any way?
Click to expand...
Click to collapse
If you read the "Known issues" you'd know this, camera mods are not and WILL NOT be supported; the android camera system wasn't designed to have cameras plugged in and out like it's nothing and moto did a lot of dirty code to make it work. There isn't a single rom out there that will merge that code so you will get no luck trying to find an official rom that supports camera mods
Hey guys great work, nice rom!
I've installed on my old Moto Z2, work very well.
Only an issue, bluetooth don't work, I can't activate it, it would appear that bt crash when it tries to activate.
Rom version aicp_albus_r-16.1-WEEKLY-20211016
ozlacs said:
Hey guys great work, nice rom!
I've installed on my old Moto Z2, work very well.
Only an issue, bluetooth don't work, I can't activate it, it would appear that bt crash when it tries to activate.
Rom version aicp_albus_r-16.1-WEEKLY-20211016
Click to expand...
Click to collapse
Really sounds like your phone is using the old O modem/firmware; all modern Q+ roms require P modem (you just need to flash NON-HLOS.bin from the P RETAIL release)
marcost22 said:
Really sounds like your phone is using the old O modem/firmware; all modern Q+ roms require P modem (you just need to flash NON-HLOS.bin from the P RETAIL release)
Click to expand...
Click to collapse
I come from lineageos 16, so android 9, and previously stock Oreo.
Anyway, where i can find it?
Thanks
Yeah, you are still on O firmware; you can find all the albus firmware here: https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
You can either fully flash P and then flash everything again or just flash NON-HLOS.bin and that should fix your issues. I assume you know how to flash stock ROM since you are flirting with customs
marcost22 said:
Yeah, you are still on O firmware; you can find all the albus firmware here: https://mirrors.lolinet.com/firmware/moto/albus/official/RETAIL/
You can either fully flash P and then flash everything again or just flash NON-HLOS.bin and that should fix your issues. I assume you know how to flash stock ROM since you are flirting with customs
Click to expand...
Click to collapse
Flashed only NON-HLOS.bin, now bluetooth work, thanks!
Hi, rom works fine, but i have random reboot, and after restarting the battery has dropped to about 20-30%.
When it reboot it is as system freezes
ozlacs said:
Hi, rom works fine, but i have random reboot, and after restarting the battery has dropped to about 20-30%.
When it reboot it is as system freezes
Click to expand...
Click to collapse
Could you explain how the random reboot happens? Is it reproducible? Also, the battery drop is a calibration issue with the battery, it's well known on the z2 play and rebooting normally will also cause this
totally random, doing nothing in particular.
and last time, at restart, don't ask me for sim pin, but mobile network still work.
no, i can't reproduce it, sorry