• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[ROM] [ ANGLER ] AICP 14.0 | Pie 9.0.rX | OFFICIAL WEEKLIES

Search This thread

widakdi

Member
Oct 29, 2017
17
2

Attachments

  • Screenshot_20200102-131221_Settings.png
    Screenshot_20200102-131221_Settings.png
    146.9 KB · Views: 157
Last edited:
  • Like
Reactions: Lawlrus

Lawlrus

Senior Member
Nov 20, 2013
10,692
6,599
its work fine. not crash or something wrong, just swipe lockscreen and rom work fine. but i can't set lockscreen with pin or pattern and fingerprint, just can set to "none" and "swipe".
sorry for my english ?

video https://drive.google.com/file/d/1-8hBYjc8oIwmDZ4Dh3kyiU7RWSWx8d5i/view?usp=drivesdk

I see what you mean, I never use pattern, but I do use pin and FP which you said doesn't work either.

I haven't gotten on the new build and I had to do some **** for work outside of work so I don't have time to flash the new build and try it today. So I'll flash the new build tomorrow and see if I have the same issue if no one else reports back before then.
 

CYoung234

Senior Member
Feb 8, 2010
866
286
Villarrica, Paraguay
I see what you mean, I never use pattern, but I do use pin and FP which you said doesn't work either.

I haven't gotten on the new build and I had to do some **** for work outside of work so I don't have time to flash the new build and try it today. So I'll flash the new build tomorrow and see if I have the same issue if no one else reports back before then.

I am using the latest build with pin and fp. No problems. I do see a problem periodically where on a reboot, I am stuck at the lockscreen. In other words, I enter my pin or fp, and it just goes back to the lockscreen. But that is an easy fix - just boot into TWRP and delete Data-System-locksettings.db.
 

Lawlrus

Senior Member
Nov 20, 2013
10,692
6,599
I am using the latest build with pin and fp. No problems. I do see a problem periodically where on a reboot, I am stuck at the lockscreen. In other words, I enter my pin or fp, and it just goes back to the lockscreen. But that is an easy fix - just boot into TWRP and delete Data-System-locksettings.db.

That "periodic problem" has been going on since 8.1 and no developers have any idea why it happens. I'm aware of the fix, I've posted it in different threads about a dozen times.

Based off the video he uploaded. That is not what he is talking about.
 

CYoung234

Senior Member
Feb 8, 2010
866
286
Villarrica, Paraguay
That "periodic problem" has been going on since 8.1 and no developers have any idea why it happens. I'm aware of the fix, I've posted it in different threads about a dozen times.

Based off the video he uploaded. That is not what he is talking about.

Okay. He was talking about not being able to use a pin or pattern, but only swipe. That was what I was replying to. I did not look at his video. Sorry, I should have replied to him instead of you. I know you are aware of the problem I described. Interestingly, I never saw that problem on AOSIP, just here.
 

Lawlrus

Senior Member
Nov 20, 2013
10,692
6,599
Guess I'll try tomorrow to verify this issue. Yesterday was 2 hours to DL it. Earlier when I got off work an hour and a half and now, 4 hours lol.

Too many people must be downloading aicp
 

widakdi

Member
Oct 29, 2017
17
2
Guess I'll try tomorrow to verify this issue. Yesterday was 2 hours to DL it. Earlier when I got off work an hour and a half and now, 4 hours lol.

Too many people must be downloading aicp

my problem has ben solved now. previous, i'm flashing aicp with twrp 3.2.3.1 fbe and work but has problem with security lockscreen, so i'm trying flash aicp last build with twrp 3.3.1.0 fbe and its succeed but when i flash gapps it getting "error : 20 incompatibel android rom", so i flashing twrp 3.2.3.1 again and it succeed.
now aicp on my angler work fine for me, dont have issue anymore.

thank you ?

sorry for my english.
 

Attachments

  • Screenshot_2020-01-02-21-45-02.png
    Screenshot_2020-01-02-21-45-02.png
    194.9 KB · Views: 85
Last edited:

Lawlrus

Senior Member
Nov 20, 2013
10,692
6,599
my problem has ben solved now. previous, i'm flashing aicp with twrp 3.2.3.1 fbe and work but has problem with security lockscreen, so i'm trying flash aicp last build with twrp 3.3.1.0 fbe and its succeed but when i flash gapps it getting "error : 20 incompatibel android rom", so i flashing twrp 3.2.3.1 again and it succeed.
now aicp on my angler work fine for me, dont have issue anymore.

thank you ?

sorry for my english.

You're using the wrong twrp. This ROM is FDE.
 

fobtob387

Senior Member
Jan 28, 2017
249
58
Redmi Note 9 Pro
Any reason why the screen recorder would turn itself on while the screen is off, and how can I remove that function from the system? I can't find a system app, or menu option anywhere to disable or remove.

Happens on new build as well. I seen a post similar to this but it happens regardless of lock method

Anyone found a solution for this? Apart from this issue, this is easily the best ROM I've come across for any of my phones.
 

CYoung234

Senior Member
Feb 8, 2010
866
286
Villarrica, Paraguay
Just a note - the January 7 AICP has a bad problem with extremely low call volume. I found this out the hard way the other day, when a brick wall collapsed on my car during torrential rain. I was not in the car, and no one was injured, but it was maddening that the phone call volume was incredibly bad. I reverted to one of the December builds, and voila - no more problem... Not sure about the January 14 build. I am downloading it now...

EDIT: Just checked the changelog for the 1/14 build, and no changes, so I will take a pass on this. I believe that others have reported the same problem for the first build of 2020, so I will hold off on updates for a while.
 
Last edited:

wartomato

Senior Member
Aug 31, 2015
2,068
1,814
Essen
www.aicp-rom.com
Just a note - the January 7 AICP has a bad problem with extremely low call volume. I found this out the hard way the other day, when a brick wall collapsed on my car during torrential rain. I was not in the car, and no one was injured, but it was maddening that the phone call volume was incredibly bad. I reverted to one of the December builds, and voila - no more problem... Not sure about the January 14 build. I am downloading it now...

EDIT: Just checked the changelog for the 1/14 build, and no changes, so I will take a pass on this. I believe that others have reported the same problem for the first build of 2020, so I will hold off on updates for a while.
There were no changes even on December builds. Just saying...
 
  • Like
Reactions: CYoung234

fobtob387

Senior Member
Jan 28, 2017
249
58
Redmi Note 9 Pro
I installed the latest weekly updated from the AICP Extras app and it's resulted in an unusable phone sadly. The phone is so sluggish that I can barely open Whatsapp or other simple apps and even just loading the launcher or scrolling in it takes forever, sound and microphone doesn't work in most apps either, when the phone is off and charging the charging animation is stuck at 0% and lastly, the recents menu is stuck on the Oreo layout no matter what I set it to.

Can I dirty flash an older version over this? Will I run into any issues if I do so? This is just horrible in its current state.
 
Last edited:

Lughnasadh

Senior Member
Mar 23, 2015
2,052
1,345
Google Nexus 5
Huawei Nexus 6P
I installed the latest weekly updated from the AICP Extras app and it's resulted in an unusable phone sadly. The phone is so sluggish that I can barely open Whatsapp or other simple apps and even just loading the launcher or scrolling in it takes forever, sound and microphone doesn't work in most apps either, when the phone is off and charging the charging animation is stuck at 0% and lastly, the recents menu is stuck on the Oreo layout no matter what I set it to.

Can I dirty flash an older version over this? Will I run into any issues if I do so? This is just horrible in its current state.

I'm running the latest weekly as well and not experiencing any of the issue you have described. It's running great as usual. And as wartomato mentioned, there hasn't been any changes in quite a while. Maybe you need a clean flash if you haven't done one lately.
 
  • Like
Reactions: wartomato

CYoung234

Senior Member
Feb 8, 2010
866
286
Villarrica, Paraguay
There were no changes even on December builds. Just saying...

Okay thanks. I checked again, and the other report of low call volume was from a year ago, so not applicable here. I am not sure what to say. I updated the phone using the OTA mechanism. All I know is that the call volume was fine until I OTA updated to the 1/7/2020 build. The phone function was pretty much unusable on that build. I clean flashed back to the last December build, and the phone call volume is perfect again.

Obviously, I believe you about the changes, as you are one of the developers. I will try to OTA update again when I have time.
 

Bobbaloo

Senior Member
Jul 7, 2016
1,691
886
New York
Just a note - the January 7 AICP has a bad problem with extremely low call volume. I found this out the hard way the other day, when a brick wall collapsed on my car during torrential rain. I was not in the car, and no one was injured, but it was maddening that the phone call volume was incredibly bad. I reverted to one of the December builds, and voila - no more problem... Not sure about the January 14 build. I am downloading it now...

EDIT: Just checked the changelog for the 1/14 build, and no changes, so I will take a pass on this. I believe that others have reported the same problem for the first build of 2020, so I will hold off on updates for a while.
Did you try speaker, headset? All three low volume?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Didn't realize people were still downloading this. Try this...

  • 66


    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 evolved into a mature ROM with the BEST community you can find!!!

    Until 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 when it comes to hardware, drivers and some features.
    With the rebrand of CM to LineageOS (LAOS) we are now actually LAOS based with some tweaks from AOSP.

    If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors or 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


    W. I. P.

    credits.png


    In the beginning we would like to thank:

    LineageOS & CM (R.I.P.) team
    @Maxwen and the rest of the OmniRom team
    @razorloves and @sam3000 for their awesome work with all Nexus devices & LineageOS
    DU team
    Community
    ...

    team.png


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


    donations.png


    We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
    Thank you!!



    downloads.png


    Latest Stable Release Version 13.1

    Download link: AICP Downloads



    changelog.png


    By the download link


    issues.png


    It's a Nexus - You tell... :p


    FAQ:
    Before using the ROM:
    Q. Can I have an ETA for the next build?
    A. Yes, just look in the OP to see, if your device is build on a nightly or weekly schedule.

    Q. Does this ROM support custom kernels?
    A. No. You can still use them (as long as they are LOS based), but discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter using them!

    Q. Why doesn't this ROM support Xposed?
    A. Xposed is a hack that is geared towards AOSP, custom ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.

    Q. Alright, but I still want to flash Xposed, so which version do I need to install?
    A. Xposed is not yet available for nougat (officialy), however there are unofficial versions. You will need to use the version arm64/arm for SDK 25.

    Flashing the ROM:
    Q. What do I need to know before flashing?
    A. Check the install instructions in the first post...

    Q. Can the builds be dirty flashed over each other?
    A. Yes, however make a nandroid first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.

    Q. How do I dirty flash builds?
    A. Wipe System, Cache and ART/Dalvik cache. Flash the ROM, your preferred root solution and reboot. Or you might just use the OTA app to preform that task for you.

    Q. How do I flash kernel builds?
    A1. 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", 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 then reboot.
    A2. LOS based kernels sometimes come as a flashable ZIP file too. You can flash them 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, clear Cache & ART/Dalvik cache and then reboot.

    Using the ROM:
    Q. How do I enable software buttons?
    A. Settings -> Navigation -> Enable navigation bar. The bar can be configured separately in its settings.

    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 in the substratum folder on the internal storage.

    Q I keep losing root with Magisk, how do I fix it?
    A Check this out, if that doesn't work for you ask for help in this thread, read or ask in the Magisk thread on XDA or just flash Magisk again!

    Q I'm having issues with WhatsApp, how do I fix it?
    A Read this

    Q. Do I need to provide a logcat if I'm reporting a bug?
    A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.

    Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
    A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog
    A2. If you are already rooted, you can use the built-in feature to make a logcat and provide that. Just look into the root section in the AICP Extras menu.

    instructions.png

    The ROM should contain everything you need to enjoy Android Oreo. You don't need to install any Add-Ons, simply download the latest ROM, GApps, flash it 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 if possible avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
    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:

    (Again: Don't do it if you don't know it!)

    1. Download needed Factory Images from Google (bootloader, radio and vendor) OR from my 2nd post (Current: 8.1.0 (OPM7.181205.001, Dec 2018)) and flash them via FASTBOOT in Bootloader Mode.
    2. Download the ROM, GApps and Magisk 18.0 (or higher) (Optional) then transfer them to your device
    2a. Google Apps: I'm using micro package from OpenGAPPS. Also you can find the link for latest GAPPS in my 3rd post.
    3. Boot to recovery (TWRP recommended)
    4. Wipe system, Cache, data and ART/Dalvik cache
    5. Flash ROM Zipfile
    6. Flash/Install GApps (optional, needed for e.g. Google Playstore to work)
    7. Flash/Install the root solution of choice (optional) - Magisk 18.0 or higher versions works pretty nice!
    8. Reboot to system


    PREREQUISITE FOR OTA:

    To be able to flash using the buildin OTA app that needs TWRP recovery installed to work.
    You can still use LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery.
    Zip gets saved in the "AICP_ota" folder on your internal storage.
    Please be sure that you are on the latest TWRP recovery.​

    The ROM has GApps persistance in between dirty flashes, so you only have to flash them once!
    No need to flash root solution on every OTA update (= ROM Update) If you are on Magisk 18.0 or higher!


    Supported Root Solutions:



    sources.png


    KERNEL:
    The kernel in this ROM follows LineageOS source with custom additions from AICP, AOSP and Android Community.
    https://github.com/AICP/kernel_huawei_angler

    If you want to contribute to the AICP or wanna see what is being worked on/merged, feel free to visit our Gerrit review system. (Link is at the bottom!!!)

    ROM & Additional links:
    Gerrit Code Review
    Github


    IceColdJelly AICP G+ community

    Contributors
    (mention all the devs who have contributed to your device tree, kernel, vendor, etc,
    only mention the main ones though, probably the top four or so, otherwise this list will be a mile long unless if you're a huge kanger xD)

    ROM OS Version: 9.0.x Oreo
    ROM Kernel: Linux 3.10.xxx

    Version Information
    Status: NIGHTLY
    Stable Release Date: Not released yet

    Creation date: 04-10-2017
    Last Updated: Nightly

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

    XDA:DevDB Information
    [ROM] [ ANGLER ] AICP 14.0 | Pie 9.0.rX | OFFICIAL WEEKLIES, ROM for the Huawei Nexus 6P

    Contributors
    semdoc, GreekDragon, LorD ClockaN, wartomato
    Source Code: https://github.com/AICP

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.10.x
    ROM Firmware Required: 8.1.0 (OPM7.181205.001, Dec 2018)
    Based On: GZOSP

    Version Information
    Status: Nightly
    Stable Release Date: 2019-03-03

    Created 2017-10-04
    Last Updated 2019-03-13
    31
    Reserved

    Notice: We are shipping vendor.img into ROM.zip. No need to flash any stock image on new ASB's with Pie Builds !!!


    Just make sure you are on Dec 2018 Stock images while you are starting....


    ******************************************************************************************************************************************************

    For Oreo Builds (AICP 13.1):

    Stock Images to be flashed via FASTBOOT

    ASB Dec 2018 Stock Images: 8.1.0 (OPM7.181205.001, Dec 2018)





    ******************************************************************************************************************************************************


    How to get my Fi Project SIM Discovered ? all credits goes to @flashblue. Please go and thank him :)

    I'd suggest these steps to get your Project Fi SIM discovered:

    1. Go to post #1 and install the ROM completely following the instructions.
    2. Setup your phone, but skip the window about inserting the SIM card.
    3. When your phone is setup (it will be without Fi service) go to settings and choose security.
    4. Make sure you select "none" as the security option. You don't want a pin for sure.
    5. Reboot into "Recovery" and follow the steps in post #1 to install the ROM and Vendor image.
    6. Your phone should boot normally and discover the Fi SIM card.

    As you can see from my post count I am new at helping anyone. Hopefully I did this right:)
    28
    New build is on the way guys....


    Build link: HERE

    Changelog: HERE

    * Fixes here and there for angler trees...

    It's awesome to have ya back @razorloves :good:
    24
    New build is uploading :highfive: (will be done in 15 minutes)

    Build link: here

    Changelog: here



    Enjoy :)
    22
    Hey guys;

    New build is up to my BB folder: https://basketbuild.com/devs/semdoc/angler-pie

    The change proposed by @razorloves - http://gerrit.aicp-rom.com/79217 - is included and this change fixes hopefully the issue mentioned by @Toutatis_ some posts ago....


    Also changes from http://gerrit.aicp-rom.com/#/q/topic:QS-brightness-slider+(status:open+OR+status:merged) topic are included too...

    Build: Link HERE
    Changelog: http://haste.aicp-rom.com/heluzenipu.vhdl



    Just flash it dirty if you are on any of my previous angler Pie buidls....

    Btw; I'll keep posting these test buidls as far as you want to test and report back your thoughts....

    Cheerz :)