[ARM64][ROM][11.0][OFFICAL] AICP 16.1 [Addison]

Search This thread

marcost22

Senior Member
Jun 26, 2019
254
63
Moto Z Play
Moto Z2 Play


logo_black.png


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.
*
*/

features.png

Feature list (rough overview)


credits.png


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

team.png


@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"



donations.png


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!!



downloads.png


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/.



changelog.png


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)

issues.png


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.


instructions.png


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.

sources.png


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:
Device tree source:
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,alberto97

Information:
ROM OS Version:
11.x
Kernel: Linux 3.18.140
ROM Firmware required: ADDISON_OPNS27.76
Status:
STABLE
Release Date: 19-12-2021

You want to see a "normal" night at the "DEV office", click here!!​
 

germanchop

New member
Dec 20, 2021
3
0
solved, ask me for unlock code...
i forget format data....
Thx
Running on android 11 Now!!!
Thx!!!!!!
 
Last edited:

BloodyPorra

Member
Aug 6, 2014
12
0
Brazil
Reported random reboots and sound is too loud and burst. But in AOSP this problem does not appear. I'm not sure if the random reboots part has to do with the AICP, I brought my cell phone in for assistance today, battery was changed. But on AOSP the sound was normal. I'll test for more days and send a logcat.
 

BloodyPorra

Member
Aug 6, 2014
12
0
Brazil
Good customizations and performance. Free ram at 800-1300mb. Screens of the ROM:
 

Attachments

  • Screenshot_20211221-045013_Aicp_Launcher.png
    Screenshot_20211221-045013_Aicp_Launcher.png
    1.4 MB · Views: 330
  • Screenshot_20211221-045029_Aicp_Launcher.png
    Screenshot_20211221-045029_Aicp_Launcher.png
    294.9 KB · Views: 306
  • Screenshot_20211221-045038_Configurações.png
    Screenshot_20211221-045038_Configurações.png
    167.5 KB · Views: 285
  • Screenshot_20211221-045057_AICP_Extras.png
    Screenshot_20211221-045057_AICP_Extras.png
    190.4 KB · Views: 266
  • Screenshot_20211221-045102_AICP_Extras.png
    Screenshot_20211221-045102_AICP_Extras.png
    120.5 KB · Views: 251
  • Screenshot_20211221-045107_AICP_Extras.png
    Screenshot_20211221-045107_AICP_Extras.png
    134 KB · Views: 260
  • Screenshot_20211221-045631_Configurações.png
    Screenshot_20211221-045631_Configurações.png
    128.4 KB · Views: 329

marcost22

Senior Member
Jun 26, 2019
254
63
Moto Z Play
Moto Z2 Play
Reported random reboots and sound is too loud and burst. But in AOSP this problem does not appear. I'm not sure if the random reboots part has to do with the AICP, I brought my cell phone in for assistance today, battery was changed. But on AOSP the sound was normal. I'll test for more days and send a logcat.
Can you get me a log for the crashes? I'll investigate the audio too, but a more detailed description would help
 

BloodyPorra

Member
Aug 6, 2014
12
0
Brazil
Can you get me a log for the crashes? I'll investigate the audio too, but a more detailed description would help
In AOSP (arm64) rom my speaker is not that loud. But in AICP i listening noise in full volume and popping sound. After install Magisk my sound is very low and solved this, but this problem comming back and sound is loud again. After shake my phone for flashlight my phone reboots. Follow the matlog:
 

Attachments

  • logs-2021-12-21-09-05-15.zip
    151.5 KB · Views: 15
  • logs-2021-12-21-09-05-42.zip
    153.5 KB · Views: 4
  • logs-2021-12-21-09-07-42.zip
    197.7 KB · Views: 6

marcost22

Senior Member
Jun 26, 2019
254
63
Moto Z Play
Moto Z2 Play
In AOSP (arm64) rom my speaker is not that loud. But in AICP i listening noise in full volume and popping sound. After install Magisk my sound is very low and solved this, but this problem comming back and sound is loud again. After shake my phone for flashlight my phone reboots. Follow the matlog:
I can see some things that might cause that audio issue; altho it's weird that i cant notice it; it might just be the opalum speaker protection being all wonky.
You are gonna have to get me a console-ramoops from after the reboot, just pull /sys/fs/pstore, because those have no info for me
I even have a XT1635-02 myself as my test device, the only thing different is that i have an ever so slightly newer firmware version; M8953_10238.63.04.83R vs M8953_10238.63.04.83.01R on mine
 

BloodyPorra

Member
Aug 6, 2014
12
0
Brazil
Sound is low and fixed and back again very loud with noise, distortion and popping. After notification in whatsapp. Ok i want to check this.


(Edit):

console-ramoops isn't available after kernel panic​

 
Last edited:

BloodyPorra

Member
Aug 6, 2014
12
0
Brazil
I take the logcat in ADB after shake several times my device is shutdown again, but only the last line appears:

Code:
12-21 10:21:44.628     0     0 I         : [ 1520.174098,4] motosh 4-0043: Sending disp_rotate(x)value: 0
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Ah its for 7.1.1, i thought i can make android 11 out of it, same with AOSP ? if i follow AOSP guide to build it (android 11 based rom)? and later i can add the files from your github!
    Yes, that is correct. However, i'd advise against building AOSP as your first proyect because the LOS build system automates a TON of stuff that aosp has you do by hand (kernel building, dtbo merging etc)
    1
    @marcost22 hi i need your help, i accidently typed
    fastboot getvar max-sparse-size
    fastboot oem fb_mode_set
    fastboot flash partition gpt.bin
    fastboot flash bootloader bootloader.img
    this command since then when ever i reboot my phone, it enters to bootloader, can you please help me fix this ? appreciate your help
    First of all, you didn't "accidentally" type 4 very specific commands


    And if you stopped panicking you would have read the tutorial fully and learnt that the command you seek is
    fastboot oem fb_mode_clear
    1
    Hello, there! I've looked through the AICP extra. But just couldn't find the start button or the main button option. There's only a home button customization (intended for the hardware button I suppose?) that would show up when the on screen navigation is disabled, but that options wouldn't work.
    I've flashed the 20220326 version as well, neither of these versions' settings gave that option for the start button.
    Well that part IS a bug, it should be showing that the button is configured to go to sleep on long press.

    Anyways, in the meantime you can mount vendor from twrp and delete the file vendor/usr/keylayout/fpc1020.kl

    That will remove the fp gesture functionality
    1
    hi! is there a way to fix it? just happened after recent update.
    This is not a bug, you just changed the default clock. You hold tap on the clock until it starts shaking and then you just swipe right or left to change it
  • 6


    logo_black.png


    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.
    *
    */

    features.png

    Feature list (rough overview)


    credits.png


    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

    team.png


    @LorD ClockaN
    @eyosen
    @semdoc
    @SpiritCroc
    @wartomato
    @Miccia
    plus the rest of the crazy bunch that we call "team"



    donations.png


    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!!



    downloads.png


    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/.



    changelog.png


    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)

    issues.png


    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.


    instructions.png


    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.

    sources.png


    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:
    Device tree source:
    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,alberto97

    Information:
    ROM OS Version:
    11.x
    Kernel: Linux 3.18.140
    ROM Firmware required: ADDISON_OPNS27.76
    Status:
    STABLE
    Release Date: 19-12-2021

    You want to see a "normal" night at the "DEV office", click here!!​
    2
    First of all thank you for this ROM. I installed it today on my Moto Z play. Everything working fine except
    1. Google Cam keeps on crashing.
    2. No 4K video option
    3. As video play progresses, main speaker volume automatically begins to fade and remains somewhere at half even though I push the buttons to make it at maximum level it does not increase.

    Motorola never used the front LED as an indicator. Thanks it lits up while charging and on notifications.
    Awesome.
    1. GCam is not officially supported, you are going to have to ask around and find which one works fine with this device
    2. SnapCam doesn't support 4k; using something like OpenCamera 4k recording works just fine
    3. This seems to be an evolution of the same issue some other people have found that i just can't track down; have you had your screen/battery replaced by any chance?

    Yep, which is why i thought it was pretty dumb and just marked it as a white indicator LED
    2
    that means my phone has a 3rd party touch screen, I didn't know such thing could be possible, so that means my mobile will be stuck with custom 7.1 forever?
    If you get me a logcat i might be able to patch the kernel to kinda support 3rd party screens; it really just sounds like the knockoff touch chip needs some extra time to wake up or needs to be waken multiple times
    1
    19-12-2021: Initial release
    1
    hi! is there a way to fix it? just happened after recent update.
    This is not a bug, you just changed the default clock. You hold tap on the clock until it starts shaking and then you just swipe right or left to change it