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

Search This thread

Agusti94

Member
Mar 31, 2015
25
2
Lanus
Moto Z2 Play
had a weird issue. on first setup after connecting wifi the screen went black. cuold bring up the reboot menu but nothing more.
changing from open gapps to NikGapps solved it
 

paed808

Senior Member
Mar 17, 2012
180
143
Does 911 work on this rom? I heard in the past some custom roms have issues with calling emergency numbers...
 

kontemp

Senior Member
Nov 8, 2019
103
18
I don't know what exactly has changed, but after last update standby battery consumption has significantly improved! Before last update it was 5% overnight, now it is 1% - well done, thanks!
 

carlosmessala

Member
Feb 19, 2013
13
8
First of all, I loved this version of AICP for Albus. It's extremely light and fast, it don't even compare to others custom roms I've tested before for Albus that run older Androids still with poor performance. It brought this phone back to the life! Many thanks to the team!

Oddly, after installing this AICP 16.1 on my Z2 Play, the recharge feature started to bug:

Image 01:
View attachment 5622871
The phone stopped to recharge when it is turned on. It shows the little lightning indicating the power input, but at the battery config menu, it shows the message: "Not charging" (or "Não está carregando", in portuguese as you can read in the image).

Addly, in the instant I remove the recharge cable with the phone turned on, it abruptly turns off (just like if I removed the battery).

Image 02:
View attachment 5622873
With the phone turned off, it recharges the battery normally. It shows the big image indicating the rechargement (with the lighting icon in the middle, indicating the power input).

Image 03:
View attachment 5622875
But when I remove the recharger cable with the phone turned off, the big image that indicates the rechargement do not disappear. It get stuck in the screen without the lighting part, but the stand-by mode keeps working normally (the screen continues to turn off for inativite, and turns back on if I click any button, but always at this recharging screen without the lightning icon).

Once stucked at this recharging mode, I have to hold the power buttor for many seconds to force the phone to reboot into the Android system.

Additional information:
1. I have changed the battery recently. Unfortunately, I didn't tried to recharge the new battery with the stock rom before to flash the AICP 16.1, battery experts may say if it could be a battery flaw rather than the rom.

2. I'm not using generic rechargers (I tested in multiples newer original Motorola chargers).

The problem is solved by changing the boot mode (thanks to user 4903000 on this post): put the phone on bootload mode and run the command:

Code:
fastboot oem config bootmode " "
fastboot reboot
 

kontemp

Senior Member
Nov 8, 2019
103
18
Hm, I don't see any difference.
I was over-enthusiastic, sorry about that... But first night after update battery consuption really was 1%, unfortunately later on it went back to 3-4% percent as usual... Apparently some app was loaded next day, or some process was activated again, I don't know.
 

Mugdha246

Member
Mar 2, 2020
13
1
hi, my sim cards are detected but no signal at all. No volte no gsm nothing. i am from india and using airtel bsnl and jio. nothing works
 

carlosmessala

Member
Feb 19, 2013
13
8
Wow, the latest update crashed Google Play Services, the only service capable to crash everything else! Clean up cache and app storage didn't solve it.

Now I'm trying reinstall the service manually. I'll keep this post updated.

Important tip: always keep a secondary non-google relative browser installed.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2


    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

    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!!
    2
    oh alright. i was just curious since i couldnt find any device trees for albus on 12, i think ill try experimenting with gsi, although a full custom rom would be better.
    anyways thanks for all the great work you do on this device, the z2 play would be no where without your work.
    I am working on a 4.9 port, just it's tricky to give timelines. For example, it took me 2 months to get to userspace, 2 weeks to bring up nfc, half of usb, camera, touchscreen,audio. And now it's taking me 3 months to fix the other half of usb and fighting the front camera
    1
    Great!!! It Works!!! Thank you
    1
    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
    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)
    1
    Thanks for reply. I'll look for that.
    @marcost22, do you know if there's any way to mock this sensor data or anything like that to avoid this problem?
    I think i could spoof the data in kernel, but i wouldn't recommend doing this; if your battery gets too hot you can just have a fire in your hands. Li-Pol batteries are extremely sensitive to heat which is why these devices have a dedicated battery temp sensor