[SHARE] [ROM] [OFFICIAL] [11.0] [WEEKLIES] OFFICIAL AICP 16.1 for Moto G4 Play [harpia]

Search This thread

Prabhat_Proxy

Member
Jun 1, 2021
16
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)

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

issues.png


You tell... :p

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:
Put the Github link to your kernel HERE (mandatory), not posting the kernel source violates the GPL, and also violates the rules on XDA ...
Device tree source:
Put the Github link to your device tree HERE.
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:

(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 xD)

Information:
ROM OS Version:
11.x
Kernel: Linux x.z.y (for example: 4.14.y)
ROM {Firmware|Vendor} required:
Status:
{ALPHA|BETA|STABLE}
Release Date: mm-dd-yyyy

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

mmortal03

Senior Member
Apr 15, 2014
249
41
@Prabhat_Proxy , who is building these? I did some further testing, and one thing I've just noticed with the phone just sitting on a table, connected to WiFi but otherwise doing nothing -- it just randomly restarted itself. I'm not sure how many times it has done that today, as I just happened to be sitting near it to hear it vibrate when it restarted.
 

Prabhat_Proxy

Member
Jun 1, 2021
16
3
@Prabhat_Proxy , who is building these? I did some further testing, and one thing I've just noticed with the phone just sitting on a table, connected to WiFi but otherwise doing nothing -- it just randomly restarted itself. I'm not sure how many times it has done that today, as I just happened to be sitting near it to hear it vibrate when it restarted.
You can try mentioning this in aicp discord.
 
  • Like
Reactions: mmortal03

mmortal03

Senior Member
Apr 15, 2014
249
41
I Just tested LTE data on AICP 16.1 on a XT1607, separately testing a SIM from a T-Mobile MVNO, and a SIM from a Verizon MVNO. Unfortunately, LTE data is broken on AICP 16.1 with the T-Mobile SIM.

I think this is likely the same bug as the following, from LOS 17.1: https://gitlab.com/LineageOS/issues/android/-/issues/2099


I did a comparison of:

Stock ROM:
LTE data works on both the T-Mobile and Verizon SIMs.
VoLTE calling works on T-Mobile. (VoLTE calling with Verizon is not supported on the XT1607 -- this is not a bug.)

LOS 14.1:
LTE data works on both the T-Mobile and Verizon SIMs.
VoLTE calling works on T-Mobile.

LOS 17.1:
LTE data *does not* work on the T-Mobile SIM, but works on the Verizon SIM.
VoLTE calling works on T-Mobile.

AICP 16.1:
LTE data *does not* work on the T-Mobile SIM, but works on the Verizon SIM.
VoLTE calling works on T-Mobile.

I've triple checked the APN settings.

There was a special build of LOS 17.1 that helped some people get data working, but it doesn't help in this case. (Just for reference: https://forum.xda-developers.com/t/...geos-17-1-harpia.4070601/page-8#post-83552695 )
 
  • Like
Reactions: UlricGrave34
I Just tested LTE data on AICP 16.1 on a XT1607, separately testing a SIM from a T-Mobile MVNO, and a SIM from a Verizon MVNO. Unfortunately, LTE data is broken on AICP 16.1 with the T-Mobile SIM.
Hello dear friend, really nice review.

In addition to the SIM Data and VoLTE comparison, what about the performance and battery draining between those ROMs???
 

mmortal03

Senior Member
Apr 15, 2014
249
41
Hello dear friend, really nice review.

In addition to the SIM Data and VoLTE comparison, what about the performance and battery draining between those ROMs???

Battery life would require more in-depth testing that I don't have time to do right now. The nice thing about this phone is that the battery *is* replaceable.

Frankly, I'm more interested in just getting to the bottom of this LTE data bug on current builds, because it's an old bug in harpia, and this phone could do perfectly fine for people on the T-Mobile network for the foreseeable future if that could get fixed.

As far as performance, LOS remains smoother and more responsive than AICP on this phone, but, with more dev focus on AICP right now, AICP is probably where you need to be if you care about future security updates and bug fixes.
 
  • Like
Reactions: UlricGrave34

PPbyte

New member
May 27, 2022
1
0
I Just tested LTE data on AICP 16.1 on a XT1607, separately testing a SIM from a T-Mobile MVNO, and a SIM from a Verizon MVNO. Unfortunately, LTE data is broken on AICP 16.1 with the T-Mobile SIM.

I think this is likely the same bug as the following, from LOS 17.1: https://gitlab.com/LineageOS/issues/android/-/issues/2099


I did a comparison of:

Stock ROM:
LTE data works on both the T-Mobile and Verizon SIMs.
VoLTE calling works on T-Mobile. (VoLTE calling with Verizon is not supported on the XT1607 -- this is not a bug.)

LOS 14.1:
LTE data works on both the T-Mobile and Verizon SIMs.
VoLTE calling works on T-Mobile.

LOS 17.1:
LTE data *does not* work on the T-Mobile SIM, but works on the Verizon SIM.
VoLTE calling works on T-Mobile.

AICP 16.1:
LTE data *does not* work on the T-Mobile SIM, but works on the Verizon SIM.
VoLTE calling works on T-Mobile.

I've triple checked the APN settings.

There was a special build of LOS 17.1 that helped some people get data working, but it doesn't help in this case. (Just for reference: https://forum.xda-developers.com/t/...geos-17-1-harpia.4070601/page-8#post-83552695 )

I also faced the problem of no data with my XT1602 using AICP16 and a T-Mobile MVNO.
But the apn settings provided by the official website of the MVNO, which are also used in AICP16, and the settings used by LOS14, which is working, differ. In my case, LOS14 runs on another device, but this should make no difference, since LOS14 also works on harpia.
Configuring the apn settings according to those of LOS14 solved my problem of no data.

I think you already tried this option, but maybe it will help some other out here.
 

mmortal03

Senior Member
Apr 15, 2014
249
41
Configuring the apn settings according to those of LOS14 solved my problem of no data.

I think you already tried this option, but maybe it will help some other out here.

Yeah, I actually don't think I wrote down the APN settings from when I tested LOS 14.1, but I wrote down the APN settings from an LOS 18.1 hima that I'm also testing the SIM with, where data works, both with the various APN settings from online, and, I believe those already on the phone. It *just worked™*, lol.

Here on harpia, none of the various APN combinations work. It's clearly a ROM issue, as data does work on LOS 14.1 on harpia for T-Mobile. I won't have this SIM card activated for too much longer, but if I get the chance, I'll go back into LOS 14.1 for some further tests, and copy down the APN settings if there happens to be a discrepancy.
 
Last edited:

mmortal03

Senior Member
Apr 15, 2014
249
41
@PPbyte , I just checked, and LOS 14.1 actually didn't have a default APN with this SIM card (even tried resetting the APN settings). So, I plugged in the APN settings from the web with this MVNO, and then data worked. So, it's definitely a bug in these harpia ROMs since then.
 

mmortal03

Senior Member
Apr 15, 2014
249
41
Update: After installing LOS 14.1, I did some further testing with the Verizon MVNO SIM, and then some further testing with the T-Mobile MVNO SIM. With T-Mobile, data was working and VoLTE was provisioned, but it would actually switch to GSM when making a call, so I don't know if I'm actually getting VoLTE. I thought proper VoLTE stayed on LTE when making a call?

Anyway, after the further LOS 14.1 testing, I did a regular wipe in TWRP and then restored my AICP 16.1 backup, and, *drumroll*, now data is working there!

I swear this has got to be a bug in how the dual SIM card logic is being handled on harpia phones. When I had Verizon data working a couple of days ago, on the phone information screen, the Current subId was 1, and the SubId of the default data SIM was 1. Now that I have T-Mobile data working, the Current subId is 2, and the SubId of the default data SIM is 2. Maybe I'm wrong on this, but it deserves further investigation.
 
Last edited:
  • Like
Reactions: UlricGrave34

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    @Prabhat_Proxy , who is building these? I did some further testing, and one thing I've just noticed with the phone just sitting on a table, connected to WiFi but otherwise doing nothing -- it just randomly restarted itself. I'm not sure how many times it has done that today, as I just happened to be sitting near it to hear it vibrate when it restarted.
    You can try mentioning this in aicp discord.
    1
    I Just tested LTE data on AICP 16.1 on a XT1607, separately testing a SIM from a T-Mobile MVNO, and a SIM from a Verizon MVNO. Unfortunately, LTE data is broken on AICP 16.1 with the T-Mobile SIM.

    I think this is likely the same bug as the following, from LOS 17.1: https://gitlab.com/LineageOS/issues/android/-/issues/2099


    I did a comparison of:

    Stock ROM:
    LTE data works on both the T-Mobile and Verizon SIMs.
    VoLTE calling works on T-Mobile. (VoLTE calling with Verizon is not supported on the XT1607 -- this is not a bug.)

    LOS 14.1:
    LTE data works on both the T-Mobile and Verizon SIMs.
    VoLTE calling works on T-Mobile.

    LOS 17.1:
    LTE data *does not* work on the T-Mobile SIM, but works on the Verizon SIM.
    VoLTE calling works on T-Mobile.

    AICP 16.1:
    LTE data *does not* work on the T-Mobile SIM, but works on the Verizon SIM.
    VoLTE calling works on T-Mobile.

    I've triple checked the APN settings.

    There was a special build of LOS 17.1 that helped some people get data working, but it doesn't help in this case. (Just for reference: https://forum.xda-developers.com/t/...geos-17-1-harpia.4070601/page-8#post-83552695 )
    1
    Hello dear friend, really nice review.

    In addition to the SIM Data and VoLTE comparison, what about the performance and battery draining between those ROMs???

    Battery life would require more in-depth testing that I don't have time to do right now. The nice thing about this phone is that the battery *is* replaceable.

    Frankly, I'm more interested in just getting to the bottom of this LTE data bug on current builds, because it's an old bug in harpia, and this phone could do perfectly fine for people on the T-Mobile network for the foreseeable future if that could get fixed.

    As far as performance, LOS remains smoother and more responsive than AICP on this phone, but, with more dev focus on AICP right now, AICP is probably where you need to be if you care about future security updates and bug fixes.
    1
    Update: After installing LOS 14.1, I did some further testing with the Verizon MVNO SIM, and then some further testing with the T-Mobile MVNO SIM. With T-Mobile, data was working and VoLTE was provisioned, but it would actually switch to GSM when making a call, so I don't know if I'm actually getting VoLTE. I thought proper VoLTE stayed on LTE when making a call?

    Anyway, after the further LOS 14.1 testing, I did a regular wipe in TWRP and then restored my AICP 16.1 backup, and, *drumroll*, now data is working there!

    I swear this has got to be a bug in how the dual SIM card logic is being handled on harpia phones. When I had Verizon data working a couple of days ago, on the phone information screen, the Current subId was 1, and the SubId of the default data SIM was 1. Now that I have T-Mobile data working, the Current subId is 2, and the SubId of the default data SIM is 2. Maybe I'm wrong on this, but it deserves further investigation.