• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

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

Search This thread

ozlacs

Member
Oct 31, 2015
37
2
Italy
It's still that same usb stuff, i don't get it. I've been completely unable to reproduce this even trying to fill the ram by hand. Either you've got a bad charger or your ram is somehow bad. I will continue to look into this however

ok stupid question:
can dirty on the usb connector cause the problem?
because it is very dirty, the cable has difficulty entering, I absolutely have to clean it
 

marcost22

Senior Member
Jun 26, 2019
82
15
ok, but when it happens usb it is not connected.
can i test the ram somehow?
First of all, terribly sorry about the delay; life got in the way as usual. Yeah, i know, but that's all im seing in the logs, so it's all i can work with. Not "safely" no, i did it and even tho it went fine it was after softbricking once already, so dont recommend
ok stupid question:
can dirty on the usb connector cause the problem?
because it is very dirty, the cable has difficulty entering, I absolutely have to clean it
It very well could be causing issues where it puts the phone in a state of allocating and never releasing the ram by exploiting some 3.18 bug; but doubtful. Anyways, it's always a good idea to clean it, cleaner means less possibility of something going wrong. My recommendation? Try some of the other excellent roms, they all use a different kernel and that might jsut fix ti
Disregard the above...
Last night was again 5%, wakelock blocker didn't work at all.
It is as it is, I guess 😉
BR!
That's android for you; why do you think i ask for bbs stats? A rogue app can throw everything into disarray, or a cpu core that got stuck doing something. It's a pain to diagnose those last few percentages
 

ozlacs

Member
Oct 31, 2015
37
2
Italy
First of all, terribly sorry about the delay; life got in the way as usual. Yeah, i know, but that's all im seing in the logs, so it's all i can work with. Not "safely" no, i did it and even tho it went fine it was after softbricking once already, so dont recommend

It very well could be causing issues where it puts the phone in a state of allocating and never releasing the ram by exploiting some 3.18 bug; but doubtful. Anyways, it's always a good idea to clean it, cleaner means less possibility of something going wrong. My recommendation? Try some of the other excellent roms, they all use a different kernel and that might jsut fix ti

first of all you must not apologize, it is I who must thank you for the time devoted to me, and for the work on this splendid rom.

ok clean connector, and let's see how it goes.
if the problem persists, I will reluctantly go to another rom (suggestions?)

thanks!
 

kontemp

Senior Member
Nov 8, 2019
94
16
That's android for you; why do you think i ask for bbs stats? A rogue app can throw everything into disarray, or a cpu core that got stuck doing something. It's a pain to diagnose those last few percentages
Understood.
I've got one last idea about that: Screen -> Pocket Mode is disabled, and Screen -> Active screen gestures is disabled. But when you hold proximity sensor for 3-4 seconds, and then release it - the screen wakes up, like if there the pocket mode was active after all... Maybe this is the reason. Don't worry, I don't have more ideas about that, I understand the difficulty. Unfortunately couldn't help with bbs logs - you saw yourself, that bbs didn't show any wakelocks on my device...

Like ozlacs wrote above - the rom is splendid!
 

meelten

Senior Member
Nov 21, 2018
59
13
I've got one last idea about that: Screen -> Pocket Mode is disabled, and Screen -> Active screen gestures is disabled. But when you hold proximity sensor for 3-4 seconds, and then release it - the screen wakes up, like if there the pocket mode was active after all... Maybe this is the reason.
I confirm that happens.
 
  • Like
Reactions: kontemp

marcost22

Senior Member
Jun 26, 2019
82
15
Understood.
I've got one last idea about that: Screen -> Pocket Mode is disabled, and Screen -> Active screen gestures is disabled. But when you hold proximity sensor for 3-4 seconds, and then release it - the screen wakes up, like if there the pocket mode was active after all... Maybe this is the reason. Don't worry, I don't have more ideas about that, I understand the difficulty. Unfortunately couldn't help with bbs logs - you saw yourself, that bbs didn't show any wakelocks on my device...

Like ozlacs wrote above - the rom is splendid!
Eh, that's not pocketmode, that's attentive display, the setting is hidden somewhere else. PocketMode is just that when the phone is in your pocket/proximity is covered the fp sensor is disabled so you dont accidentally burn your fp attempts by just having the phone in your pocket
 

kontemp

Senior Member
Nov 8, 2019
94
16
Oh, I got it. But the issue could be somewhere around screen wakeup procedures, I guess. Yesterday all of the sudden my screen woke up (clock appeared), phone lying on the table, no movement nor gestures - strange. It was like the result of waving the hand over it, but this function I have disabled. This could explain overnight consuption a bit above normal - a dozen or more such wakeups could eat a couple percent, I guess.

Just saying, not a big deal for me. I'm super-satisfied with all the rest of this rom, digging this topic just out of curiosity.

BR!
 

5130walter

Member
Jul 2, 2018
8
0
Hello! I'm having some problems: some streaming apps don't work well, videos won't load.

Sometimes the applications in the background stop every 5 minutes having to start them again from the beginning (this problem has happened with whatsapp, poweramp, youtube music)

When it drops to less than 50% of the battery the phone turns off and when I put it to charge it says that the battery is charging more than 54%. When I unplugged the phone charger I get a low battery notification with the current battery percentage. for example, if I charge it up to 95% battery, I get a low battery notification with the same percentage that is 95%

The camera does not focus well
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    I've got one last idea about that: Screen -> Pocket Mode is disabled, and Screen -> Active screen gestures is disabled. But when you hold proximity sensor for 3-4 seconds, and then release it - the screen wakes up, like if there the pocket mode was active after all... Maybe this is the reason.
    I confirm that happens.
  • 3


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

    Flashed only NON-HLOS.bin, now bluetooth work, thanks!