Database Develop

[ROM][Unofficial][Testing] AICP 15 (Q) [2020-04-06]

{
"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.

[ROM][RAV*/SOFIA*][10][UNOFFICIAL] AICP-15

{
"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 with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. 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 15.0
Google Drive
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:
Tested on OpenGAPPS nano
Native screen recording broken
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. Information about Xposed, EdXposed or Riru Core can be obtained from the XPosed General forums .
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 behaviour 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 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 AND the model name. (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 Q. 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), GApps are already included for some a/b devices.
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!
Optional install instructions: Download images.zip, decompress, flash in fastbootd
images.zip
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.
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:
GitHub - Odin1101/Project-Sofia: Main branch is Vache's 4.14.170 Kernel. Upstream branch is the 4.14.202 Kernel.
Main branch is Vache's 4.14.170 Kernel. Upstream branch is the 4.14.202 Kernel. - GitHub - Odin1101/Project-Sofia: Main branch is Vache's 4.14.170 Kernel. Upstream branch is the 4.14.202 Ke...
github.com
Device tree source:
GitHub - asineth0/android_device_motorola_sofiar: Device tree for Moto G8/G8 Power
Device tree for Moto G8/G8 Power. Contribute to asineth0/android_device_motorola_sofiar development by creating an account on GitHub.
github.com
Vendor source:
GitHub - asineth0/android_vendor_motorola_sofiar: Vendor tree for Moto G8/G8 Power
Vendor tree for Moto G8/G8 Power. Contribute to asineth0/android_vendor_motorola_sofiar 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
Contributors:
Vache, Asineth, Beetle, for help with device sources and building help.
Odin for his kernel, and some changes that really helped the build!
ROM OS Version: 10.x
Kernel: 4.14.x
Version Information:
Status: Stable
Release Date: 12-22-20​

works fine on my sofiar. I had trouble with crdroid and wasn't able to get it to boot with gapps for some reason. and I'm tired of factory resetting every update

UPDATE:
Fixed overlay detection on RAV (G8, G Fast). No need to enter code to enable overlay.
Enjoy the new boot animation!
Links updated in OP
Changelog: Changelog.txt

Is location not working a problem for anyone else?

billard412 said:
Is location not working a problem for anyone else?
Click to expand...
Click to collapse
I haven't seen any location issues. Make sure all of your perms are set correctly and all location services are turned on.

mad_fitter said:
I haven't seen any location issues. Make sure all of your perms are set correctly and all location services are turned on.
Click to expand...
Click to collapse
Yup I did that. Initially Waze and gmaps were having trouble but the issue seemed to fix itself. However, I deliver for doordash and postmates and can't get either to work because they never find my location.

Update.
Device changes: Add apns to config.
Links updated in OP.

I need help, no matter what i do with my moto G fast xt2045-3 I can never figure out how to install the custom rom after the bootloader has been unlocked, i hace done every step but i get pre verification error

dandu3 said:
works fine on my sofiar. I had trouble with crdroid and wasn't able to get it to boot with gapps for some reason. and I'm tired of factory resetting every update
Click to expand...
Click to collapse
how did you get it to work twrp throws me errors moto gfast xt2045-3

hmm it looks like my xt2045-2 is stuck on boot screen do i need stock android 10

Demed333 said:
hmm it looks like my xt2045-2 is stuck on boot screen do i need stock android 10
Click to expand...
Click to collapse
Yeap! All the custom roms need the Stock Android 10 base. If you mess up something you must flash stock Android-10. Be carefull because downgrading is not possible due to bootloader lock. On Moto G8 the bootloader is not totally unlocked. It is unlocked in the sense that you can flash all the other things BUT not another engineered bootloader. So the bootloader can only be same version or newer, never older, never unofficial.

siokara said:
Yeap! All the custom roms need the Stock Android 10 base. If you mess up something you must flash stock Android-10. Be carefull because downgrading is not possible due to bootloader lock. On Moto G8 the bootloader is not totally unlocked. It is unlocked in the sense that you can flash all the other things BUT not another engineered bootloader. So the bootloader can only be same version or newer, never older, never unofficial.
Click to expand...
Click to collapse
is it even possible? If it's can you make a video or something to do that

Demed333 said:
is it even possible? If it's can you make a video or something to do that
Click to expand...
Click to collapse
motorola added antirollback in january 2022 update so if youre on it (or newer) sadly you cant downgrade to older firmware.

Demed333 said:
is it even possible? If it's can you make a video or something to do that
Click to expand...
Click to collapse
If you flashed stock Android-11 you are in trouble because you now have a very new bootloader version and I don't know if you can revert to stock Android-10. Personally I haven't done this because I was paying attention to the requirements the various rom developers were describing in their posts. You must try it. I hope you get lucky.

siokara said:
If you flashed stock Android-11 you are in trouble because you now have a very new bootloader version and I don't know if you can revert to stock Android-10. Personally I haven't done this because I was paying attention to the requirements the various rom developers were describing in their posts. You must try it. I hope you get lucky.
Click to expand...
Click to collapse
Yez i did that and bricked my device but Blank flash works. And i Sony think i wanna try doing ut again

[DISCONTINUED][ROM][10.0][OFFICAL] AICP 15.0 [Albus]

{
"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 with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. 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 15.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.
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:
OpenGapps
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. Information about Xposed, EdXposed or Riru Core can be obtained from the XPosed General forums .
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 behaviour 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 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 AND the model name. (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 Q. 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), GApps are already included for some a/b devices.
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.3 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:
https://github.com/marcost2/kernel_motorola_msm8953
Device tree source:
"https://github.com/marcost2/android_device_motorola_albus
Vendor source:
https://github.com/marcost2/proprietary_vendor_motorola
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:
EmaMaker, erfanoabdi, vacheounet, Npjohnson, JeanGraff30, jefferson1979, JarlPenguin
ROM OS Version: 10.0.x
Kernel: Linux 3.18.124
Version Information:
Status: WEEKLY
Release Date: 02-26-2021
You want to see a "normal" night at the "DEV office", click here!!​

02-27
Went official
02-26
Initial Release

It's official now.

I tried this rom, it installed fine, but during setup (and after setup) it keeps rebooting after only ca 30 sec uptime.

Аnd just like on other rom on Android 10 does not work WearOs app

lungan said:
I tried this rom, it installed fine, but during setup (and after setup) it keeps rebooting after only ca 30 sec uptime.
Click to expand...
Click to collapse
Weird, are you using latest twrp (3.4 or 3.5)?

marcost22 said:
Weird, are you using latest twrp (3.4 or 3.5)?
Click to expand...
Click to collapse
Actually not, Iwas using 3.2.2-r23. As said, it installed fine, and I can even boot and run, but then again it reboots after 30 second uptime everytime.
Do you think an old version of TWRP could mess up the installation, and thus, even if the installation runs fine, the ROM is corruptively installed afterwards?

That really sounds like you were using Oreo firmware. But assuming that you are using pie modem, yes, old twrp could cause some issues. Also, we are official again for twrp, so you can just download from there

Dear developer.
The Wear Os application does not start on your firmware,
and when theJBL mode is connected, the alarm clock does not play

I'll look into wearos
I know, this is a issue that plagues all Z devices on custom roms, and we are trying to fix it

Ah, so refreshing to see an official rom for our device! Works flawlessly, thank you!

Greetings from Germany
Thanks for your work!
My bluetooth doesnt work. When i start it, it doesnt run and an info box opens with the text " Bluetooth terminates repeatedly " and three choices...app information, close app and Copy the url of the crash report .
bluetooth is not important to me, I just wanted to point out the problem to you ... maybe others have the same
ad astra
Hack

You need to be on Pie firmware for this rom, otherwise you get, well, that

oh...ok...thanks for the fast answer

This looks pretty cool, great job! I have a few questions:
1) Does encryption work?
2) What about Always on Display? Is it the same experience as in stock ROM?
3) And finally, does one-button navigation work? (The gesture navigation using the fingerprint sensor.)
Thanks!

1) Yes! It does
2) You can enable it yeah; I like to use it only when it's charging and there's an option for that too. I can't say it's the same as stock as i haven't been on stock in like 2 years
3) Yes, yes it does

is wear os app not working issue resolved yet?

Hi. Today I've installed this rom and later I've updated to 20210327 WEEKLY. Camera doesn´t work and when I plugged the charger or the usb cable front flash enables. Any solution?
Thx

ddhernandez said:
Hi. Today I've installed this rom and later I've updated to 20210327 WEEKLY. Camera doesn´t work and when I plugged the charger or the usb cable front flash enables. Any solution?
Thx
Click to expand...
Click to collapse
Hi!, what do you mean camera doesn't work? Could you be a bit more specific about what app you are using, errors?
Also that's not the front flash, that's the notification LED, and it turning on during charging can be disabled under Settings -> AICP Extra -> Notifications -> Battery LED

[ROM] [11.0] [OFFICAL] AICP 16.1 [lavender]

{
"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)
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!)
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_xiaomi_lavender
Contribute to AICP/kernel_xiaomi_lavender development by creating an account on GitHub.
github.com
Device tree source:
https://github.com/AICP/device_xiaomi_lavender.
AICP/proprietary_vendor_xiaomi
Contribute to AICP/proprietary_vendor_xiaomi 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
You want to see a "normal" night at the "DEV office", click here!!​

is gcam supported?

Walden0 said:
is gcam supported?
Click to expand...
Click to collapse
yes it is, try parrot v5

Hii dev I'm facing network issue with jio 4g in my device redmi note 7.
While other ROMs like pixel and LineageOS have no issues with internet speed but when I switched to aicp it's network speed is not good now.
Please have a look sir.

Works great and very stable.
Thanks.

Vaibhavyadav932 said:
Hii dev I'm facing network issue with jio 4g in my device redmi note 7.
While other ROMs like pixel and LineageOS have no issues with internet speed but when I switched to aicp it's network speed is not good now.
Please have a look sir.
Click to expand...
Click to collapse
No issues with my lavender

I have a problem I can activate wificalling but nothing happens
Does anyone have a solution?
thank you

@letsmakecakes
There is problem with the built in camera for months now. On lineage this problem has been Solved. Will AICP also solve the built in camera problem soon?

Hi guys, good rom but the shortcut key do not appear in lockscreen. Is there any solution?
Thanks.

Hey. Very fast and stable rom. However, I have one problem. I can't set my messenger bubbles to appear.Everything seems to be set, but they don't show up, while for example from the sms app they normally show up.

Hello there, is safety net supported in this ROM? I want to make the switch but I need to use some bank apps. Thanks in advance!

Everything worked fine for me. Camera, rotation, auto brightness. proximity sensor, etc. I did not installed magisk. Using today build; 07/04/2022. Stable, fast. Just one thing.. I know is not rom related, but for some reason MindTheGapps didnt work for me. Instead i used gapps (I choosed mini). Thanks for sharing and hard work

ncmz said:
Hello there, is safety net supported in this ROM? I want to make the switch but I need to use some bank apps. Thanks in advance!
Click to expand...
Click to collapse
I dont use it anymore but if i remember correctly i think yes, just flash some Gapps on it.

I read this on Discord. What will that mean for lavender. I saw there is a Android 12 lineage version but don't know if it is stable yet.
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
discord.com

dkoek said:
I read this on Discord. What will that mean for lavender. I saw there is a Android 12 lineage version but don't know if it is stable yet.
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
discord.com
Click to expand...
Click to collapse
I think they have ended support for the Redmi Note 7 (

linux.alucard said:
I think they have ended support for the Redmi Note 7 (
Click to expand...
Click to collapse
Most likely yes

[Discontinued][ROM][11.0][OFFICAL] AICP 16.1 [Albus]

{
"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