Database Develop

[ROM][10.0][UNOFFICIAL][kenzo/kate] AICP 15.0 for Redmi Note 3

{
"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: AICP
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.
Changelog:
- Initial build
- March Security Patch
- Source Upstream
- Added Gcam (Works without GApps)
- Added DevOtag App
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. 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:
Kernel Sources
Device tree source:
Device Tree
Common-Device tree source:
Device Tree
Vendor source:
Device Tree
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:
- trkzmn
- NaytSeyd
Our Telegram Group
Xiaomi Redmi Note 3
ROM OS Version: 10.0.x
Kernel: Linux 3.10
Version Information:
Status: UNOFFICIAL
Release Date: 03-20-2020​

Hi,
I can't use my earphones on phone calls from Phone application on my Kenzo.
It is just possible to chose between Speaker or Phone.
Could someone verify it?
Thanks

mvarejao said:
Hi,
I can't use my earphones on phone calls from Phone application on my Kenzo.
It is just possible to chose between Speaker or Phone.
Could someone verify it?
Thanks
Click to expand...
Click to collapse
Dirty flash or clean flash ?

NaytSeyd said:
Dirty flash or clean flash ?
Click to expand...
Click to collapse
Reset factory and format. This issue is on Lineageos 17 unofficial too.

mvarejao said:
Reset factory and format. This issue is on Lineageos 17 unofficial too.
Click to expand...
Click to collapse
Take log

NaytSeyd said:
Take log
Click to expand...
Click to collapse
Is there any log? I just try to select Bluetooth earphone connection and it just don't change at all.

mvarejao said:
Is there any log? I just try to select Bluetooth earphone connection and it just don't change at all.
Click to expand...
Click to collapse
Without the log, I can't tell where the error is.

Installed in Redmi Note 3 Pro (Kate)
Everything is working fine, super smooth and responsive.
The only problem right now is the camera, freezes my phone.
I will be testing more, thanks for the room! (btw, sorry for my english im from mexico)

[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​

Reserved

You are amazing! I was just about to try to dive into the world of ROM building, but you beat me to it! I'm going to try this one.

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

Thank you for you work on this ROM. It's super stable and the best one I have tried on the moto g.
Also, I was able to do an update to 010621 (by dirty flashing) using TWRP. The only quirk was that I had to flash it twice in order to get it to boot?? Once to the A slot and the second time to the B slot.

tcaudill01 said:
Thank you for you work on this ROM. It's super stable and the best one I have tried on the moto g.
Also, I was able to do an update to 010621 (by dirty flashing) using TWRP. The only quirk was that I had to flash it twice in order to get it to boot?? Once to the A slot and the second time to the B slot.
Click to expand...
Click to collapse
Yeah, I'm still learning about the dynamic partitions too. Its a learning curve for sure.

Edit: double post

I'm not seeing any deepsleep with this ROM, is this normal with "Q"?
(This isn't a complaint about the ROM, I've been using it for several weeks without any issues or faults)

Thank you for this ROM. Does it support signature spoofing? I'm planning to flash NanoDroid instead of GApps. @mad_fitter

Using successfully on Sofiar XT2041-1
Only two details (so far):
1° Whatsapp voice notes randomly sound glitchy when switching between applications.
2° Got Device is not certified in PlayStore
Thanks for this nice ROM!!!

It also worked on Moto G8 Power (not Lite) Sofiar XT2041-1, installed via fastboot using images.zip, it didn't work with TWRP 3.5.0.0 in my case (no boot, even changing A / B partitions, etc).
-Fixed original rom issues like: intermittent GPS, stock keyboard typing delay, (Incredible that he comes with these problems), 100% root over system files.
-This did not solve Screen Sharing via Wifi, which did not work in the stock, now it restarts directly.
-It only allowed me to flash GApps nano, with higher versions TWRP showed insufficient space
-The original camera with support for all cameras (wide angle, telezoom and macro cam) was recovered by installing Moto 2 Camera from the Play Store, deactivating before this ROM camera (App Dissabler [root]).
-The rest all excellent! Thanks for the ROM and return the gestures to switch between apps to the bottom! The new side gestures were horrible

You should put in the information that there is a AICP 16.1 also available which is an Android 11 build and works well as far as I have tested it.

mad_fitter said:
AICP
Android Ice Cold Project​
Click to expand...
Click to collapse
Greetings from the Appalachians. I just wanted to thank you for building this ROM. I haven't had aicp available for a device in a long long time. I had tried damn near every ROM available for the sofia devices.
I have the sofiap and I found it nice that some of the moto apps were here like the one that supposed to open the note app or whatever we set it up to. I don't have that working but it's definitely not a deal breaker.
It's been a while like I said earlier and fur me it seems very polished right now from the aicp app to the launcher to the very cool live wallpaper(I never use these but love the AICP custom live paper).
As most people know I could go on and on so let me end by saying thanks again and that I hope you continue this endeavor!
Also for me only this and another ROM will even flash in TWRP. So again thanks!
If you haven't tried this, give it a whirl folks. You won't regret it if you're looking for a particular feature that's not in a more stripped down ROM(and i like these as well}.

Is there a degoogled version of this rom? Also since the Moto stylus stuff is already installed is there a way to get them working?

Hey good work !
does anyone know if this ROM work with Sprint mobile?
I have tried almost every ROM but can't get LTE to work
thanks

Am I missing something? Sorry for the noob question. How do I check official builds for updates
Thanks

[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

[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

[ROM][RAV*/SOFIA*][11][UNOFFICIAL] AICP-16.1

{
"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://drive.google.com/drive/folders/10gRJuNekzUdFitQCdXZviQzWFNIf9Fxe?usp=sharing
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
- FM Radio doesn't work
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 - S4muel007/kernel_motorola_trinket
Contribute to S4muel007/kernel_motorola_trinket development by creating an account on GitHub.
github.com
Device tree source:
GitHub - ph4n70m-404/device_motorola_sofiar: Older device tree repo that might get experimental updates before they are added to the main device tree repo
Older device tree repo that might get experimental updates before they are added to the main device tree repo - GitHub - ph4n70m-404/device_motorola_sofiar: Older device tree repo that might get ex...
github.com
Vendor source:
GitHub - ph4n70m-404/vendor_motorola_sofiar
Contribute to ph4n70m-404/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:
ph4n07m for trees, fixes and building help.
Beetle84 for fixes and building help.
S4muel007 for kernel.
Thanks awesome peeps!
Information:
ROM OS Version: 11.x
Kernel: Linux 4.14.x
Status: STABLE
Release Date: 11-07-2021
You want to see a "normal" night at the "DEV office", click here!!​

CHANGELOG
11/7/2021 - Initial Build.
11/10/2021 - November 2021 Security Patch, Synced with latest AICP sources.

Hello,
I discovered by chance your aicp release for the Motorola G8 Power on this forum: so I took my G8 Power out of the drawer and installed it. TWRP 3.4.0.0 was already present so no problem. Everything is working fine, I haven't done all the customization possibilities yet.
With TWRP, impossible to decrypt the data, even by giving the right password I always have the message 'incorrect password'.
Perhaps the incompatibility of this version with Andoid 11. I found an alternative with the installation of a SD card where I don't have problem of reading -for the implementation of future releases I will use this process-.
In any case 'Bravo' and thank you for the work done.
I will keep you informed of the problems encountered (if any ....).
As this is an unofficial release I guess we will be kept informed via this forum.
Good day to you.
Regards,

Tintin62 said:
Hello,
I discovered by chance your aicp release for the Motorola G8 Power on this forum: so I took my G8 Power out of the drawer and installed it. TWRP 3.4.0.0 was already present so no problem. Everything is working fine, I haven't done all the customization possibilities yet.
With TWRP, impossible to decrypt the data, even by giving the right password I always have the message 'incorrect password'.
Perhaps the incompatibility of this version with Andoid 11. I found an alternative with the installation of a SD card where I don't have problem of reading -for the implementation of future releases I will use this process-.
In any case 'Bravo' and thank you for the work done.
I will keep you informed of the problems encountered (if any ....).
As this is an unofficial release I guess we will be kept informed via this forum.
Good day to you.
Regards,
Click to expand...
Click to collapse
Did you format data (where you have to type yes) in twrp, or just wipe it?

Beetle84 said:
Did you format data (where you have to type yes) in twrp, or just wipe it?
Click to expand...
Click to collapse
I did format the data before installing via TWRP.
I can do it again.

I have just redone the complete installation with prior formatting the datas, now the decryption of the data with TWRP is OK. No explanation....