{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
*
*/
Feature list (rough overview)
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
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
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!!
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/.
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
You tell...
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.
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.
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!!
This same hidden SSID connection bug on LineageOS also exists on AICP on harpia: https://gitlab.com/LineageOS/issues/android/-/issues/2678
@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.
mmortal03 said:
@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.
Click to expand...
Click to collapse
You can try mentioning this in aicp discord.
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 )
Edit: I eventually got data working with the T-Mobile SIM (see below), but it's still not completely clear what must be done when flashing these ROMs to guarantee it will work. It's also not clear now that VoLTE was truly working in some of the above: https://forum.xda-developers.com/t/...or-moto-g4-play-harpia.4340943/#post-86957107
mmortal03 said:
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.
Click to expand...
Click to collapse
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???
UlricGrave34 said:
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???
Click to expand...
Click to collapse
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.
mmortal03 said:
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 )
Click to expand...
Click to collapse
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.
PPbyte said:
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.
Click to expand...
Click to collapse
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.
@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.
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.
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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 with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. 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.
*
*/
Feature list (rough overview)
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
...
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
...
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!!
Latest Stable Release Version 15.0
Download link: https://dwnld.aicp-rom.com/
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
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:
(link the best one for your device, there are several variants out there right now, nano/micro GApps from opengapps.org is almost always a good choice though)
You tell...
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 discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. 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. Information about Xposed, EdXposed or Riru Core can be obtained from the XPosed General forums .
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 behaviour 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 preform 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 loose 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 loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
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 that's in the substratum folder on the internal storage.
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 AND the model name. (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 (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 in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Q. 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 Zipfile.
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 Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work), GApps are already included for some a/b devices.
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.3 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.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
https://github.com/AICP/kernel_motorola_msm8974.git
Device tree source:
https://github.com/AICP/device_motorola_victara.git
Vendor source:
https://github.com/AICP/proprietary_vendor_motorola.git
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:
ROM OS Version: 10.0.x
Kernel: Linux 3.4
Version Information:
Status: WEEKLY
Release Date: 05-01-2020
You want to see a "normal" night at the "DEV office", click here!!
Status:
Selinux enforcing
You kept Victara Alive Bro, Congratulations to achieve this milestone
OP Updated:
Source updated;
Recovery related updates;
Under the hood performance changes.
Download
Update is out:
- Merged March security patches
- Improved graphic performance and compatibility
- Fixed offline charge
Download
AICP is now official and with all updates been released weekly at sundays
Great work. I have recently replaced the screen of my victara , and woke up it for the first time since 2016. This android 10 rom let it a new phone.
I have a issue, I insert my china telecom (FDD-LTE B3 B1, CDMA2000) sim card into it, but no mobile network. The SIM card is taken from my other phone, should be fine.
Any one please help me make my old "new" phone work again, thanks a lot.
iSingle said:
Great work. I have recently replaced the screen of my victara , and woke up it for the first time since 2016. This android 10 rom let it a new phone.
I have a issue, I insert my china telecom (FDD-LTE B3 B1, CDMA2000) sim card into it, but no mobile network. The SIM card is taken from my other phone, should be fine.
Any one please help me make my old "new" phone work again, thanks a lot.
Click to expand...
Click to collapse
Can you check in network, access point names if there is a setting for your provider? Else in this setting, three dots, try reset to default.
Ping me in any results you got, please?
jeferson1979 said:
AICP is now official and with all updates been released weekly at sundays
Click to expand...
Click to collapse
You Kept Victara Alive
jeferson1979 said:
Can you check in network, access point names if there is a setting for your provider? Else in this setting, three dots, try reset to default.
Ping me in any results you got, please?
Click to expand...
Click to collapse
I have tried exactly what you told. There was nothing at APN page, after reseting to default, there were china telecom APNs.
I recalled my memory, I had turned my victara from xt1085 (china version ) to xt1095.
I think my issue is not related with your ROM, ( It is on Lineage 17.1, no lucky). So I am thinking about flash correct baseband maybe a solution.
Thanks for your reply, I will report ASAP.
does it working with sim on XT1093
Faize_Lohar said:
does it working with sim on XT1093
Click to expand...
Click to collapse
Yes of course
4G
zahidm said:
Yes of course
Click to expand...
Click to collapse
Well thanks for the reply i got the sim working but i have 2 issues at hand one speaker is not working during calls and how can i get 4g in Pakistan. only getting 3g (H+). thanks. do i need to unlock base band.
Faize_Lohar said:
Well thanks for the reply i got the sim working but i have 2 issues at hand one speaker is not working during calls and how can i get 4g in Pakistan. only getting 3g (H+). thanks. do i need to unlock base band.
Click to expand...
Click to collapse
Join in TG for quick support
I can not send any messages in telegram group. Well can you guide me here. How can i unlock 4g in pakistan
Faize_Lohar said:
I can not send any messages in telegram group. Well can you guide me here. How can i unlock 4g in pakistan
Click to expand...
Click to collapse
4G is working in Pakistan on all Android custom ROMs, but if you have H+ even on stock then it's impossible, it links to the variant you have in your hand. It might be a CDMA only.
Please confirm your mobile model & Variant and stock version you flashed or working
zahidm said:
4G is working in Pakistan on all Android custom ROMs, but if you have H+ even on stock then it's impossible, it links to the variant you have in your hand. It might be a CDMA only.
Please confirm your mobile model & Variant and stock version you flashed or working
Click to expand...
Click to collapse
i have XT1093 and it's 4g i guess
https://www.phonemore.com/specs/motorola/moto-x-2014/xt1093/
Faize_Lohar said:
i have XT1093 and it's 4g i guess
https://www.phonemore.com/specs/motorola/moto-x-2014/xt1093/
Click to expand...
Click to collapse
Do you have 4G while using stock firmware?
No that's why i am asking
Faize_Lohar said:
No that's why i am asking
Click to expand...
Click to collapse
Ok, First you have to flash right baseband to your device,
Go at https://mirrors.lolinet.com/ and find your device specific latest stock firmware and flash via RSD lite.
Try retail one if you are confused
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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 with a base of AOSP repositories and some additions from LineageOS for device specific repositories.
If there are any bugs, either we will sort them out, if it concerns our code base. 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.
*
*/
Feature list (rough overview)
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
...
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
...
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!!
Latest Stable Release Version 15.0
Google Drive
Please note that official builds will be deleted from our servers every month due to maintenance services.
We advise everyone to keep at least the latest or best working build on their device as a backup.
Maybe copy it to a cloud service or USB too.
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:
Tested on OpenGAPPS nano
Native screen recording broken
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 discussion should go in the thread of the respective kernel. We don't offer support for bugs you might encounter while using them!
Q. Why doesn't this ROM support Xposed?
A. Xposed is a hack that is geared towards AOSP. Custom ROMs modify the framework a lot, so Xposed can cause a ton of issues on custom ROMs. 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. Information about Xposed, EdXposed or Riru Core can be obtained from the XPosed General forums .
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 behaviour 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 preform 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 loose 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 loose root. Now swipe to flash and reboot afterwards.
Using the ROM:
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 that's in the substratum folder on the internal storage.
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 AND the model name. (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 (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 in the AICP Extras main page.
The ROM should contain everything you need to enjoy Android Q. 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 Zipfile.
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 Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work), GApps are already included for some a/b devices.
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!
Optional install instructions: Download images.zip, decompress, flash in fastbootd
images.zip
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.
If you want to contribute to AICP, or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Kernel source:
GitHub - Odin1101/Project-Sofia: Main branch is Vache's 4.14.170 Kernel. Upstream branch is the 4.14.202 Kernel.
Main branch is Vache's 4.14.170 Kernel. Upstream branch is the 4.14.202 Kernel. - GitHub - Odin1101/Project-Sofia: Main branch is Vache's 4.14.170 Kernel. Upstream branch is the 4.14.202 Ke...
github.com
Device tree source:
GitHub - asineth0/android_device_motorola_sofiar: Device tree for Moto G8/G8 Power
Device tree for Moto G8/G8 Power. Contribute to asineth0/android_device_motorola_sofiar development by creating an account on GitHub.
github.com
Vendor source:
GitHub - asineth0/android_vendor_motorola_sofiar: Vendor tree for Moto G8/G8 Power
Vendor tree for Moto G8/G8 Power. Contribute to asineth0/android_vendor_motorola_sofiar development by creating an account on GitHub.
github.com
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:
Vache, Asineth, Beetle, for help with device sources and building help.
Odin for his kernel, and some changes that really helped the build!
ROM OS Version: 10.x
Kernel: 4.14.x
Version Information:
Status: Stable
Release Date: 12-22-20
Reserved
You are amazing! I was just about to try to dive into the world of ROM building, but you beat me to it! I'm going to try this one.
Update.
Device changes: Add apns to config.
Links updated in OP.
Thank you for you work on this ROM. It's super stable and the best one I have tried on the moto g.
Also, I was able to do an update to 010621 (by dirty flashing) using TWRP. The only quirk was that I had to flash it twice in order to get it to boot?? Once to the A slot and the second time to the B slot.
tcaudill01 said:
Thank you for you work on this ROM. It's super stable and the best one I have tried on the moto g.
Also, I was able to do an update to 010621 (by dirty flashing) using TWRP. The only quirk was that I had to flash it twice in order to get it to boot?? Once to the A slot and the second time to the B slot.
Click to expand...
Click to collapse
Yeah, I'm still learning about the dynamic partitions too. Its a learning curve for sure.
Edit: double post
I'm not seeing any deepsleep with this ROM, is this normal with "Q"?
(This isn't a complaint about the ROM, I've been using it for several weeks without any issues or faults)
Thank you for this ROM. Does it support signature spoofing? I'm planning to flash NanoDroid instead of GApps. @mad_fitter
Using successfully on Sofiar XT2041-1
Only two details (so far):
1° Whatsapp voice notes randomly sound glitchy when switching between applications.
2° Got Device is not certified in PlayStore
Thanks for this nice ROM!!!
It also worked on Moto G8 Power (not Lite) Sofiar XT2041-1, installed via fastboot using images.zip, it didn't work with TWRP 3.5.0.0 in my case (no boot, even changing A / B partitions, etc).
-Fixed original rom issues like: intermittent GPS, stock keyboard typing delay, (Incredible that he comes with these problems), 100% root over system files.
-This did not solve Screen Sharing via Wifi, which did not work in the stock, now it restarts directly.
-It only allowed me to flash GApps nano, with higher versions TWRP showed insufficient space
-The original camera with support for all cameras (wide angle, telezoom and macro cam) was recovered by installing Moto 2 Camera from the Play Store, deactivating before this ROM camera (App Dissabler [root]).
-The rest all excellent! Thanks for the ROM and return the gestures to switch between apps to the bottom! The new side gestures were horrible
You should put in the information that there is a AICP 16.1 also available which is an Android 11 build and works well as far as I have tested it.
mad_fitter said:
AICP
Android Ice Cold Project
Click to expand...
Click to collapse
Greetings from the Appalachians. I just wanted to thank you for building this ROM. I haven't had aicp available for a device in a long long time. I had tried damn near every ROM available for the sofia devices.
I have the sofiap and I found it nice that some of the moto apps were here like the one that supposed to open the note app or whatever we set it up to. I don't have that working but it's definitely not a deal breaker.
It's been a while like I said earlier and fur me it seems very polished right now from the aicp app to the launcher to the very cool live wallpaper(I never use these but love the AICP custom live paper).
As most people know I could go on and on so let me end by saying thanks again and that I hope you continue this endeavor!
Also for me only this and another ROM will even flash in TWRP. So again thanks!
If you haven't tried this, give it a whirl folks. You won't regret it if you're looking for a particular feature that's not in a more stripped down ROM(and i like these as well}.
Is there a degoogled version of this rom? Also since the Moto stylus stuff is already installed is there a way to get them working?
Hey good work !
does anyone know if this ROM work with Sprint mobile?
I have tried almost every ROM but can't get LTE to work
thanks
Am I missing something? Sorry for the noob question. How do I check official builds for updates
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
*
*/
Feature list (rough overview)
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
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
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!!
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/.
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
You tell...
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.
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.
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:
GitHub - AICP/kernel_xiaomi_lavender
Contribute to AICP/kernel_xiaomi_lavender development by creating an account on GitHub.
github.com
Device tree source:
https://github.com/AICP/device_xiaomi_lavender.
AICP/proprietary_vendor_xiaomi
Contribute to AICP/proprietary_vendor_xiaomi development by creating an account on GitHub.
github.com
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
You want to see a "normal" night at the "DEV office", click here!!
is gcam supported?
Walden0 said:
is gcam supported?
Click to expand...
Click to collapse
yes it is, try parrot v5
Hii dev I'm facing network issue with jio 4g in my device redmi note 7.
While other ROMs like pixel and LineageOS have no issues with internet speed but when I switched to aicp it's network speed is not good now.
Please have a look sir.
Works great and very stable.
Thanks.
Vaibhavyadav932 said:
Hii dev I'm facing network issue with jio 4g in my device redmi note 7.
While other ROMs like pixel and LineageOS have no issues with internet speed but when I switched to aicp it's network speed is not good now.
Please have a look sir.
Click to expand...
Click to collapse
No issues with my lavender
I have a problem I can activate wificalling but nothing happens
Does anyone have a solution?
thank you
@letsmakecakes
There is problem with the built in camera for months now. On lineage this problem has been Solved. Will AICP also solve the built in camera problem soon?
Hi guys, good rom but the shortcut key do not appear in lockscreen. Is there any solution?
Thanks.
Hey. Very fast and stable rom. However, I have one problem. I can't set my messenger bubbles to appear.Everything seems to be set, but they don't show up, while for example from the sms app they normally show up.
Hello there, is safety net supported in this ROM? I want to make the switch but I need to use some bank apps. Thanks in advance!
Everything worked fine for me. Camera, rotation, auto brightness. proximity sensor, etc. I did not installed magisk. Using today build; 07/04/2022. Stable, fast. Just one thing.. I know is not rom related, but for some reason MindTheGapps didnt work for me. Instead i used gapps (I choosed mini). Thanks for sharing and hard work
ncmz said:
Hello there, is safety net supported in this ROM? I want to make the switch but I need to use some bank apps. Thanks in advance!
Click to expand...
Click to collapse
I dont use it anymore but if i remember correctly i think yes, just flash some Gapps on it.
I read this on Discord. What will that mean for lavender. I saw there is a Android 12 lineage version but don't know if it is stable yet.
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
discord.com
dkoek said:
I read this on Discord. What will that mean for lavender. I saw there is a Android 12 lineage version but don't know if it is stable yet.
Discord - A New Way to Chat with Friends & Communities
Discord is the easiest way to communicate over voice, video, and text. Chat, hang out, and stay close with your friends and communities.
discord.com
Click to expand...
Click to collapse
I think they have ended support for the Redmi Note 7 (
linux.alucard said:
I think they have ended support for the Redmi Note 7 (
Click to expand...
Click to collapse
Most likely yes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
*
*/
Feature list (rough overview)
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
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
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!!
Latest Stable Release Version 16.1
Download link: https://roms.expressluke.workers.dev/AICP/
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/.
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
You tell...
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.
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.
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: https://github.com/8890q/android_kernel_samsung_universal8890
Device tree source: https://github.com/8890q/android_device_samsung_universal8890-common
ROM & Additional links:
AICP's Homepage
AICP Gerrit Code Review
AICP sources on Github
Download for hero2lte from here
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 3.18.x
Status: Stable
You want to see a "normal" night at the "DEV office", click here!!
Thanks!
Any screenshots or feedback (LOS user here) ?
I will try this ROM, interesting. while waiting for DotOS 5.2. thankss
Switched back to DotOS. Much better experience.
Excellent ROM. Works great. Having issues playing videos in Google TV app, it stutters...then stops.
ekspresluk hello....Off topic but I want to ask a question...on your page Amy 2.2 Hero2lte ROM an excellent rom....the only problem is the echo problem...i am amy 2.2. I've never seen a rom that uses so little battery...excellent smooth stable rom amy 2.2...The best rom I've ever tried....please it will be great if you can fix the echo problem from this rom...we love you ekspresluk.....
I don't think the echo problem can be fixed that easily. Because it depends on your CSC/AP and others types of service providers. Also, you could be experiencing this because of your VOiP. Or something else. It happens to most of us who uses A11 ROMs for S7 Edge. Maybe you could check with your service provider and ask them which network they use, such as traditional or VoLTE. Anyway, not sure.
CertifiedWeeb said:
I don't think the echo problem can be fixed that easily. Because it depends on your CSC/AP and others types of service providers. Also, you could be experiencing this because of your VOiP. Or something else. It happens to most of us who uses A11 ROMs for S7 Edge. Maybe you could check with your service provider and ask them which network they use, such as traditional or VoLTE. Anyway, not sure.
Click to expand...
Click to collapse
I don't have any echo on Los 18 and my provider don't use Volte.
I put all the informations about my device on Los18 thread..
Some users actually report that they don't have any echo while others do. I'm not sure anyway. I'm not having any echo.
excuse me sir i have problem installing MindTheGapps
error Unable to mount /system
my device : samsung s7 edge G935FD indonesia
I had that same problem too. I believe it has to do with CSc things. What you can do is, search for GApps and I believe you can install the latest package for A11. I believe it's Micro or Nano. No sure. Try it out, it worked for me.
Update me when you have installed them.
Great ROM that has tons of customization options whilst being as smooth as stock LineageOS 18!
However I have 3 issues:
1- Settings crashes from time to time.
2- Long pressing the QS tiles doesn't take you to the corresponding setting, it just leaves you on the home screen. Perhaps it's related to the Settings crashing issue?
3- Pressing the home button doesn't wake the device up, instead nothing happens at all.
Anybody else having the same issues or is the problem on my end?
Cheers!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
*
*/
Feature list (rough overview)
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
@LorD ClockaN
@eyosen
@semdoc
@SpiritCroc
@wartomato
@Miccia
plus the rest of the crazy bunch that we call "team"
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!!
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/.
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)
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.
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.
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:
GitHub - AICP/kernel_motorola_msm8953 at r11.1-albus
Contribute to AICP/kernel_motorola_msm8953 development by creating an account on GitHub.
github.com
Device tree source:
GitHub - AICP/device_motorola_albus at r11.1
Contribute to AICP/device_motorola_albus development by creating an account on GitHub.
github.com
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!!
Reserved
What's your idle battery drain? Overnight I have 5-6% with disabled internet. In other roms it's around 2% so not great. Is there any setting that can cause it? I have mostly default settings, "pocket mode" disabled, no apps installed (just trying it out).
Hey guys good work! i've installed on my old moto z2 play and it works great! only a question... when i attach the moto mod soundboost the JBL app is crashing always... any ideas? Thanks
giobbe71 said:
Hey guys good work! i've installed on my old moto z2 play and it works great! only a question... when i attach the moto mod soundboost the JBL app is crashing always... any ideas? Thanks
Click to expand...
Click to collapse
You need this APK for it to work; because it's designed to only work in the original stock rom it needs some modifications to work under customs
Great!!! It Works!!! Thank you
Hi!
On my device (motorola moto z2 play) I have the following rom installed: [ROM] [10.0] [OFFICAL] AICP 15.0 [Albus]:
[DISCONTINUED][ROM][10.0][OFFICAL] AICP 15.0 [Albus]
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...
forum.xda-developers.com
My question is: Can said rom be updated by installing this rom?
Sorry for my bad English
No, unfortunately unlike OEM's we can't give support for version upgrades; you'd have to clean flash to install this update
5130walter said:
Hi!
On my device (motorola moto z2 play) I have the following rom installed: [ROM] [10.0] [OFFICAL] AICP 15.0 [Albus]:
[DISCONTINUED][ROM][10.0][OFFICAL] AICP 15.0 [Albus]
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...
forum.xda-developers.com
My question is: Can said rom be updated by installing this rom?
Sorry for my bad English
Click to expand...
Click to collapse
marcost22 said:
No, unfortunately unlike OEM's we can't give support for version upgrades; you'd have to clean flash to install this update
Click to expand...
Click to collapse
Is it necessary to flash the original android pie firmware before installing this rom?
5130walter said:
Is it necessary to flash the original android pie firmware before installing this rom?
Click to expand...
Click to collapse
If you were using AICP 15.0, then no; you are already using it. If you are coming from Android 8.0 or a custom rom based on it, then yes
Moto Mods 360 Camera does not work.
Is there any way?
leonthorn12 said:
Moto Mods 360 Camera does not work.
Is there any way?
Click to expand...
Click to collapse
If you read the "Known issues" you'd know this, camera mods are not and WILL NOT be supported; the android camera system wasn't designed to have cameras plugged in and out like it's nothing and moto did a lot of dirty code to make it work. There isn't a single rom out there that will merge that code so you will get no luck trying to find an official rom that supports camera mods
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
ozlacs said:
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
Click to expand...
Click to collapse
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)
marcost22 said:
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)
Click to expand...
Click to collapse
I come from lineageos 16, so android 9, and previously stock Oreo.
Anyway, where i can find it?
Thanks
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
marcost22 said:
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
Click to expand...
Click to collapse
Flashed only NON-HLOS.bin, now bluetooth work, thanks!
Hi, rom works fine, but i have random reboot, and after restarting the battery has dropped to about 20-30%.
When it reboot it is as system freezes
ozlacs said:
Hi, rom works fine, but i have random reboot, and after restarting the battery has dropped to about 20-30%.
When it reboot it is as system freezes
Click to expand...
Click to collapse
Could you explain how the random reboot happens? Is it reproducible? Also, the battery drop is a calibration issue with the battery, it's well known on the z2 play and rebooting normally will also cause this
totally random, doing nothing in particular.
and last time, at restart, don't ask me for sim pin, but mobile network still work.
no, i can't reproduce it, sorry