[DEPRECATED][ROM][UNOFFICIAL][N|14.1][SM-T285] LineageOS for Samsung Galaxy Tab A 7.0 LTE (gtexslte) - Samsung Galaxy Tab A series ROMs, Kernels, Recover

[DEPRECATED][ROM][UNOFFICIAL][N|14.1][SM-T285] LineageOS for Samsung Galaxy Tab A 7.0 LTE (gtexslte) - Samsung Galaxy Tab A series ROMs, Kernels, Recover

Frequently Asked Questions (FAQ)
Q #01: I want to report an issue. What is the proper way to do so?
I'm glad that you are asking: before doing so check the KNOWN ISSUES topic in the OP and ofc the other FAQ's listed here!
If you encountered a kernel panic follow FAQ #6 in this post instead.
If you have issues with "just" the boot process follow FAQ #7 for a very easy way to grab the boot logs.
if you have an audio issue follow FAQ #10 instead.
If your issue is not listed there click here to proceed:
If your issue is not listed there follow the directions here briefly and I may can fix it.
Often selinux can cause issues so try that at very first:
Code:
adb shell
su
(or "adb root" when enabled in developer settings)
setenforce permissive
Try again and if the issue is gone when in permissive mode: provide me a logcat as described here -> on step 3 I need the SELINUX log (option D)
If that does not solve your issue follow the logcat GUIDE to provide a valid log depending on what your issue is.
Ensure you have done a full CLEAN install before doing so (refer to FAQ #2 for what that means).
Warning: NO SUPPORT when:
- magisk is installed (known to cause issues sometimes - regardless of the ROM or version)
- Xposed is installed (known to cause issues sometimes - regardless of the ROM or version)
If you have installed any of these UNINSTALL or better do a FULL CLEAN install (see FAQ #2) before doing anything else. Often enough these above causes several issues like battery draining, problems on booting and much more. Even when they may work properly you should re-produce your issue without them first and follow the above to grab the log.
Magisk is a great piece of software and besides that it is Open Source which SuperSu never was.
I just saying I do not "support" issues with LOS when you have Magisk installed. Why? It is (like Xposed) extendable with modules (made by whoever) and those can cause billions of issues.
Other then that magisk was sometimes the reason for battery drain etc. Magisk modifies the boot "process" and sits very deep in the system (which is needed to make it work ofc) but that has the potential to make a system/ROM unstable or result in strange behaviors.
so in order to support a specific issue I have to be sure the ROM is in a "clean" state, no magisk, no xposed. The LOS root-addon is tested with LOS and made for it so that is not an issue but for the rest there are so many things which can going wrong..
Q #02: I want to install clean, how? What is a clean install? What is the recommended way to flash a new ROM version?
A clean install ensures that there are no leftovers from any previous install. One can say that there are 2 phases of a clean flash:
1) regular
2) full - when you (still) encounter issues
Usually the regular one is fully ok when flashing a new ROM version but if you encounter strange issues nobody else is reporting or if a release post is recommending it you should do a full clean install instead.
A regular clean install can be done like this:
WIPE -> Advanced -> select: System + Cache
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
A full clean install needs 2 steps more then the regular:
follow the steps for regular clean
go back in WIPE -> touch the "FORMAT data" button and type "yes" to format the internal storage (you will LOOSE ALL YOUR DATA - obviously)
REBOOT -> Recovery
Flash the ROM
reflash root addon/magisk if you want root
reflash opengapps if you want to use Google crap
It is absolutely recommended to create a backup before and COPYING IT to your PC(!) before doing the above.
Q #03: Are there any plans or a chance of official LOS builds?
no.
Q #04: Google Play shows that my device is not "certified" - how can I fix that?
First of all you must be on the latest build.
If your issue persists click here to proceed:
The second thing is you must not be rooted by the LOS root addon (afaik). Magisk has its own protections to ensure you stay certified but I hadn't the time to test the LOS root-addon.
You also need to know that google play remembers your devices last state so if you are on the latest build and still having that issue do this and it will be certified again:
android settings -> apps -> find play store -> clear data (yes data, not cache) -> reboot -> open play store -> wait 2..5 minutes -> check certified state again
Q #5: A life without Google?! Read here how:
A life without Google ? Is that possible ? ...and why you should consider it ?
So why? That's easy to answer and if those are worth it depends totally on your personal needs:
1) BATTERY. Google services are draining a LOT of your battery, so to get the most out of your battery you should abandon Google gapps
2) PRIVACY. Almost all Google apps phoning home to Google! You don't care about that? You really should. You have nothing to hide? Oh dear believe me you have no idea how much of your private data you do NOT want to share. Keep also in mind that you give your private data not to a company only , there are always humans behind and what they do.. You do not believe me? Read on
BREAKING NEWS:
You can go on with the following steps or simply head-over to /e/ OS which is LOS but completely Google-Free + microG fully working pre-installed:
check it out here!
Q #6: issues with audio (e.g. echo's, silence on one or the other site, ..)? Read here how to provide a specific log for that:
Do the following steps:
1) Ensure you have adb set up on your PC, and have adb debugging and adb root enabled in developer options on your phone
2) Then perform the following (all one command)
On Linux:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver" && sleep 10 && adb logcat -b all |egrep -vi "(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)"
Click to expand...
Click to collapse
On windows:
adb root ; adb shell "stop audioserver; logcat -c -b all; start audioserver && sleep 10 && logcat -b all |egrep -vi '(dialer|telecom|ril|gsm|touch|brightn|dct|QC-time-services|SST|sensors|AlarmMan|Lights|perfp)' "
Click to expand...
Click to collapse
3) Then re-produce your audo issue and cancel the logcat from step 2 before hanging up!
4) Share the logcat output from the console screen using paste.omnirom.org

reserved

Finally new living for my old tablet, gonna review thing later after flashing it.
Smoothest rom ever performance better than stock or any other rom that i had tried. Except the bug u mention above but thats no big deal. Well finally can instal youtube and google map.

Really love it!
The most stable build for t285!would recommend to everyone who is looking for a custom ROM for t285.But the audio is really low can barely hear it any type of help will be appreciated using it with gapps mini package works as a charm

Gtexlte user said:
Really love it!
The most stable build for t285!would recommend to everyone who is looking for a custom ROM for t285.But the audio is really low can barely hear it any type of help will be appreciated using it with gapps mini package works as a charm
Click to expand...
Click to collapse
Are their any plains for adding oms support?

Gtexlte user said:
Really love it!
[..] the audio is really low can barely hear it any type of help will be appreciated
Click to expand...
Click to collapse
I guess you mean the speaker?
Gtexlte user said:
Are their any plains for adding oms support?
Click to expand...
Click to collapse
nope. oms is a deep hack in the sources and this will never be implemented by me

Yes I mean the speaker
Is there any way to increase it I can root the device.

Gtexlte user said:
Yes I mean the speaker
Is there any way to increase it I can root the device.
Click to expand...
Click to collapse
For me its loud enough, maybe try enable audio fx built in apps

kaishi12 said:
For me its loud enough, maybe try enable audio fx built in apps
Click to expand...
Click to collapse
Yes I enabled it and there was only a slight boost in audio about 10% boost.It was always a problem in steadfasterX builds could be because I upgraded from one LOS build to another.I could try by flashing the stock ROM and then flash the LOS build.In the stock ROM audio was really loud.If Any one else have this issue could you tell about how did you flash the ROM you upgraded from a previous ROM or were on stock and flashed Did you did a clean install or a regular?I flashed Dolby it seem to have increase a bit and had become more hearable.

Gtexlte user said:
Yes I enabled it and there was only a slight boost in audio about 10% boost.It was always a problem in steadfasterX builds could be because I upgraded from one LOS build to another.I could try by flashing the stock ROM and then flash the LOS build.In the stock ROM audio was really loud.If Any one else have this issue could you tell about how did you flash the ROM you upgraded from a previous ROM or were on stock and flashed Did you did a clean install or a regular?I flashed Dolby it seem to have increase a bit and had become more hearable.
Click to expand...
Click to collapse
I do clean instal from stock rom, well i forgot to mention i using max volume, but strangely theres no noise

kaishi12 said:
I do clean instal from stock rom, well i forgot to mention i using max volume, but strangely theres no noise
Click to expand...
Click to collapse
What do you mean by max volume you set the volume to the max or is it the name of an app or something.thanks for replying.

Gtexlte user said:
What do you mean by max volume you set the volume to the max or is it the name of an app or something.thanks for replying.
Click to expand...
Click to collapse
Set volumw to the max

Gtexlte user said:
Yes I enabled it and there was only a slight boost in audio about 10% boost.It was always a problem in steadfasterX builds could be because I upgraded from one LOS build to another.I could try by flashing the stock ROM and then flash the LOS build.In the stock ROM audio was really loud.If Any one else have this issue could you tell about how did you flash the ROM you upgraded from a previous ROM or were on stock and flashed Did you did a clean install or a regular?I flashed Dolby it seem to have increase a bit and had become more hearable.
Click to expand...
Click to collapse
You don't have that issue in jedlds build?

steadfasterX said:
You don't have that issue in jedlds build?
Click to expand...
Click to collapse
Yes I don't have it in jedld builds

Gtexlte user said:
Yes I don't have this issue in jedld builds
Click to expand...
Click to collapse
I switched to your LOS builds because some stuff was broken there.but the speaker was the same as stock over there

Is there any way to fix the camera recording issue.

I notice update but it say installation blocked, its for the device?

Clean installed your rom. Everything was smooth but i cant use face unlock in this rom. it keeps showing starting up.i think its because of the recording bug.i installed face unlock in jedld cm 13 build it worked in that rom but it didnt worked in yours. Other than that thi rom is perfect.

steadfasterX said:
You don't have that issue in jedlds build?
Click to expand...
Click to collapse
i Had this issue in jedld build too

Related

[ROM][Oreo][SM-T550][UNOFFICIAL] AICP for the Samsung Galaxy Tab 9.7 Wifi

{
"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 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 (LAOS) we are now LAOS based with some tweaks from AOSP.
If there are any bugs, either we will sort them out or the LAOS team will if it concerns their code base. This rom isn't LAOS supported, so no need to report errors/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:
LineageOS & CM (R.I.P.) team
@maxwen and the rest of the OmniRom team
DU team
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...
We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!
Latest Stable Release Version 13.1
Download link: https://www.androidfilehost.com/?w=files&flid=274850
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: http://dwnld.aicp-rom.com/
Google Apps:
select ARM + Android Oreo 8.1 here: https://opengapps.org/
- SELinux is permissive
- The current builds are "incompatible" with some apps in the Play Store > You can download the last build without this issue here
You tell
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. Yes, just look in the OP to see if your device is built on a nightly or weekly schedule.
Q. Does this ROM support custom kernels?
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 ROM's modify the framework a lot, so Xposed can cause a ton of issues on custom ROM's. Now it might work for you, however it is not to be discussed in this thread, and you should refrain from posting bug reports.
Q. Alright, but I still want to flash Xposed, so which version do I need to install?
A. You will need to use the version arm64/arm/whatever for SDK 27.
Flashing the ROM:
Q. What do I need to know before flashing?
A. Check the install instructions in the first post...
Q. Can the builds be dirty flashed over each other?
A. Yes, however make a nandroid backup first as there is a chance of getting a bootloop or encountering bugs. Also bugs may only be reported on a clean flash.
Q. How do I dirty flash builds?
A. Wipe 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", 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 then reboot.
Using the ROM:
Q. How do I enable software buttons?
A. Go to Aicp Extras/Navigation bar, and enable it.
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 keep losing root with Magisk, how do I fix it?
A. Check this out. If that doesn't work for you, ask for help in this thread, read or ask in the Magisk thread on XDA or just re-flash Magisk!
Q. I'm having issues with WhatsApp, how do I fix it?
A. Read this
Q. Do I need to provide a logcat if I'm reporting a bug?
A. If you want it to be fixed faster (or at all) then yes, you should definitely provide a logcat. (Note: Please just link the logcat from your GDrive, Dropbox, etc. and do not post the content here. Thanks.
Q. How do I get a logcat, what type should I get and more questions that can conveniently be answered by my pre-determined answer?
A1. Read this thoroughly. Also, here's a good app for getting logs: https://play.google.com/store/apps/details?id=com.tortel.syslog (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 Oreo. You don't need to install any Add-on's, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.
It is STRONGLY recommended to fully wipe your device before flashing and please avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.
How to flash:
(Again: Don't do it if you don't know it!)
1. Download the ROM and GApps and transfer them to your device.
2. Boot to recovery (TWRP recommended).
3. Wipe the System, Cache, Data and ART/Dalvik cache.
4. Flash the ROM Zipfile.
5. Flash the GApps (optional, needed for e.g. Google Playstore to work).
6. Flash the root solution of your choice (optional).
7. Reboot your device.
The ROM has GApps persistence in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)
Currently Supported Root Solutions:
Magisk stable
Magisk versions higher than 14.0 doesn't require flash on every dirty flash depending on the device, some devices need you to flash it every time, unless your maintainer says otherwise it should be fine
KERNEL:
The kernel in this ROM follows LAOS source with custom additions.
PREREQUISITE FOR OTA:
To be able to flash using the built-in OTA app, TWRP recovery is needed.
You can still use the LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. The Zipfile gets saved in the "aicp_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery. Keep in mind that this could also be an unofficial version!
If you want to contribute to the AICP or want see what is being worked on/merged, feel free to visit our Gerrit code review system. (Link is at the bottom!!!)
Sources:
Kernel source
Device tree
Vendor tree
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
Contributors:
@deadman96385
@Galaxy-MSM8916 team
@elginsk8r
ROM OS Version: 8.1.0 Oreo
Kernel: Linux 3.10.x
Version Information:
Status: NIGHTLY
Release Date: 25-6-2018
You want to see a "normal" night at the "DEV office", click here!!

Can it be installed on t555?

Mihai14 said:
Can it be installed on t555?
Click to expand...
Click to collapse
Since I don't own a SM-T555, I can't tell you whether it boots or not. This build is designed for the Wifi-only variant, so your tablet definitely won't support LTE/telephony. Maybe I'll publish a SM-T555 build in the future.

virsys said:
Since I don't own a SM-T555, I can't tell you whether it boots or not. This build is designed for the Wifi-only variant, so your tablet definitely won't support LTE/telephony. Maybe I'll publish a SM-T555 build in the future.
Click to expand...
Click to collapse
I don't really care about ril but it just doesn't boot. Like the other roms and i just can't find the problem. Lineage os 14.1 should boot on t555 too but without ril and it ij stuck in the boot logo refusing to boot into /system.

Mihai14 said:
it just doesn't boot.
Click to expand...
Click to collapse
Have you fully wiped the cache & data partition?
What does "it doesn't boot" mean:
Does it pass the samsung splash screen & shows a stucking boot animation?
Are there tombstones in the data/tombstones folder present?

virsys said:
Have you fully wiped the cache & data partition?
What does "it doesn't boot" mean:
Does it pass the samsung splash screen & shows a stucking boot animation?
Are there tombstones in the data/tombstones folder present?
Click to expand...
Click to collapse
Yes clean flashed the rom. No it doesn't pass the samsung logo it's not a bootloop. There is no tombstones folder in /data

Mihai14 said:
Yes clean flashed the rom. No it doesn't pass the samsung logo it's not a bootloop. There is no tombstones folder in /data
Click to expand...
Click to collapse
I guess you know what you're doing and have enabled OEM unlocking. When TWRP is able to boot, the rom is probably not compatible with the SM-T555. I can message you when I've compiled a SM-T555 testversion. Only if you would like to help me making the SM-T555 compatible.

virsys said:
I guess you know what you're doing and have enabled OEM unlocking. When TWRP is able to boot, the rom is probably not compatible with the SM-T555. I can message you when I've compiled a SM-T555 testversion. Only if you would like to help me making the SM-T555 compatible.
Click to expand...
Click to collapse
Of course i would want to help. I can PM you my telegram.

Hi all,
I tested the ROM on SM-T550 and it boots quiet well.
Initial google (nano opengapps) setup was broken for me, but the setup
via "Google app" and my phone worked.
Another thing is that when installing a browser it
crashes right after starting it.
Opera says that I have no space free
Chrome says something like an unexpected error.
Buildin browser just appears short and closes immediately.
The game little wars and Netflix app shows the same behaviour.
So right now I can't use the ROM but I am very Happy that this device is not abandoned!
Thank you for your work and if I can help testing, just drop me a line.

I have SM-T550
Its great ROM, but.. Problem, has error browser, for example: I can't open Google chrome, opera, ... Pls fix? You are the best! ??

Ok so apparently it boots but the screen is always black. I just found a screenshot i've taken accidentally after i flashed the rom and it seems to boot.

ramaxcalmax said:
Another thing is that when installing a browser it
crashes right after starting it.
Click to expand...
Click to collapse
Thanks for your report. The latest build should work.

My Model: SM-T550
I have one problem... The ROM is great working with all browser (Google Chrome, Opera, ...) Very Good.
But... Please you read.
- It's very laggy the security (for example: PIN, password and Sequence). I'm ready PIN, it's fine.
When my tablet is lock PIN (Off). I'm watching TV or other. My tablet lets off 1 hour. After, I go my tablet open "On" it's very laggy and PIN too, all..
I hope you understanding? I'm a deaf, sorry!

I'm fighting against selinux right now. I'll update the build soon, thanks for your hint.

I think I found why the screen is not working on t555: might be because of a problem in the kernel. More precise the dt. You can use the kernel from the stock firmware as base to fix this. Also for the ril take look at samsung galaxy j5 2015/2016 sources. They have the same chip as t555/t550. Especially the 2016 version as it have almost the same base firmware (7.1.1).

Mihai14 said:
You can use the kernel from the stock firmware as base to fix this.
Click to expand...
Click to collapse
Maybe you should build it on your own. The entire building process is basically very simple.
It's actually quite easy to port it from the gt510wifi device tree. The kernel sources are available and the only thing to worry about is the RIL.

virsys said:
Maybe you should build it on your own. The entire building process is basically very simple.
It's actually quite easy to port it from the gt510wifi device tree. The kernel sources are available and the only thing to worry about is the RIL.
Click to expand...
Click to collapse
I would but my laptop is quite s**t. I have tried to build roms before but ot was a fail.

Thanks for keeping this device relevant. Working great!

Could this be ported to the 8" variant SM- T350 ? We have no Oreo development

vin_001 said:
We have no Oreo development
Click to expand...
Click to collapse
That's not true.
There's oreo development.

[ROM][OFFICIAL][CrDroid][PIE]

crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today. We're mainly based on LineageOS so use custom kernels compatible with them!
{
"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"
}
Features
Click for feature list (helps shorten the OP.)
Always Have a full functional Backup. Just in case!
DOWNLOAD ROM
*****Disclaimer*****
Important note before proceeding!!!
The copy A/B partions zip is crucial in order to prevent bricks. It only needs to be done if your coming from the stock ROM or you recently restored stock firmware manually. Other wise without it you can brick due to Motorola's A/B partition scheme.
Preparation for A/B Roms:
01. Download TWRP.
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
06. While in TWRP choose Reboot > bootloader
07. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Wipe data, dalvik, system and internal storage, then format userdata.
04. Flash ROM.zip + TWRP_installer
05. Reboot > Recovery
06.Install Gapps + Magisk (if you choose)
07. Reboot > System
Updating (AKA 'dirty flash'):
01. Download the updated ROM
02. Boot into recovery
03. Install ROM.zip + TWRP_installer
04. Reboot > Recovery
05. flash gapps + Magisk (if you choose)
06. Reboot > System
Notes:
Any time your internal storage aka "Userdata" is from a stock install you must "format data" in recovery before using ROMS
Upgrading from earlier version of crDroid:
The only difference between clean flash as above and upgrading is you just wipe system & cache, leaving data. Everything else is the same. ***Remember to always clean flash before reporting problems. Clean flashing is always the best method of ROM install.
KNOWN ISSUES
LIST-KNOWN-ISSUES-ON-YOUR-DEVICE-HERE
None
Don't expect any support if you:
- are not running the included kernel
- have installed any mods such as Xposed!
- have modified system files
Thanks to:
- ENTER-SPECIFIC-THANKS-HERE-IF-YOU-HAVE-THEM
- Google
- LineageOS
- SlimRoms
- AOSPA (Paranoid Android)
- OmniRom
- NamelessROM
- Many others... (if you're feeling upset being out of the thanks list just send a PM )
Device tree: https://github.com/Rondeau79/android...motorola_ocean
Vendor tree: https://github.com/Rondeau79/proprie...g/lineage-16.0
Download Link: https://androidfilehost.com/?w=files&flid=302315
AB copy partitions Download Link: https://androidfilehost.com/?fid=4349826312261636295
XDA:DevDB Information
CrDroid Pie, ROM for the Moto G7 Power
Contributors
Rondeau79
Source Code: https://github.com/crdroidandroid/android/tree/9.0
Kernel tree:https://github.com/Rondeau79/android_kernel_motorola_sdm632/tree/lineage-16.0
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Latest bootloader and TWRP recovery
Based On: Lineage OS
Version Information
Status: Stable
Current Stable Version: 5.11
Stable Release Date: 2019-11-25
Created 2019-11-27
Last Updated 2019-12-23

Reserved

Thank you Rom is really stable and beautiful plenty of customization baked in. Been running it for 4 days no problems at all OTA is also working great two updates already love it

Thanks! I run it as my daily driver. My first official ROM! I have built plenty in the past, but decided to make the jump. As soon as a few bugs get straighten out I will be moving it to Android 10!

Just installed the rom a couple of hours ago, and damn it's good! Only a small problem though, when you make a screenshot the little menu that appears where you can edit and take extended screenshots closes after a few seconds on its own. Is this intended or a bug? If so I hope you can fix it in the next update. Thanks a lot for the rom!

badapple420 said:
Thank you Rom is really stable and beautiful plenty of customization baked in. Been running it for 4 days no problems at all OTA is also working great two updates already love it
Click to expand...
Click to collapse
Gabe29 said:
Just installed the rom a couple of hours ago, and damn it's good! Only a small problem though, when you make a screenshot the little menu that appears where you can edit and take extended screenshots closes after a few seconds on its own. Is this intended or a bug? If so I hope you can fix it in the next update. Thanks a lot for the rom!
Click to expand...
Click to collapse
You can change the animation speeds in developer options to slow down that screenshot options. That will allow that edit page to stay on your screen longer.

Rondeau79 said:
You can change the animation speeds in developer options to slow down that screenshot options. That will allow that edit page to stay on your screen longer.
Click to expand...
Click to collapse
I see, I set the duration scale to 0.5x so no wonder it closed so fast. Anyways is there a way to make opengl skia the default gpu renderer? Because it switches back to default after a reboot.

Gabe29 said:
I see, I set the duration scale to 0.5x so no wonder it closed so fast. Anyways is there a way to make opengl skia the default gpu renderer? Because it switches back to default after a reboot.
Click to expand...
Click to collapse
Flash the attached zip in recovery. It will take care of that.

Rondeau79 said:
Flash the attached zip in recovery. It will take care of that.
Click to expand...
Click to collapse
Thank you, it worked.

As it is getting regular updates I though I would give this ROM a try on my new G7 Power. To be honest it works much better than I expected, not seeing any stability problems and it has some nice features. Still testing, but will probably start using this ROM + phone as my daily.
I did however have a heck of a time installing and getting both the ROM and TWRP to boot on the phone. That mostly had nothing to do with this ROM and more to do with the A/B partitions thingy Google has done on recent phones (which I have grown to hate). Also the ROM's install instructions are a bit vague in parts, so there was a bit of a learning curve (for me at least).
One the upside everything I have tested so far works. Storage encryption is enabled by default and working, wifi works (even with hidden SSIDs), dual SIMS works, camera app works, fingerprint works , call quality seems good. SELinux is disabled, which is not good but I can live with.
A big thanks for the all the done work on this!!

joefidler said:
As it is getting regular updates I though I would give this ROM a try on my new G7 Power. To be honest it works much better than I expected, not seeing any stability problems and it has some nice features. Still testing, but will probably start using this ROM + phone as my daily.
I did however have a heck of a time installing and getting both the ROM and TWRP to boot on the phone. That mostly had nothing to do with this ROM and more to do with the A/B partitions thingy Google has done on recent phones (which I have grown to hate). Also the ROM's install instructions are a bit vague in parts, so there was a bit of a learning curve (for me at least).
One the upside everything I have tested so far works. Storage encryption is enabled by default and working, wifi works (even with hidden SSIDs), dual SIMS works, camera app works, fingerprint works , call quality seems good. SELinux is disabled, which is not good but I can live with.
A big thanks for the all the done work on this!!
Click to expand...
Click to collapse
Download terminal emulator
Su
setenforce 1
SeLinux will be enforcing

Hey @Rondeau79, thank you for the rom, this was actually the only one I was able to flash. (But I think the problem is on my side of the table
Is there any way to get rid of the google-parts of the rom (searchbar etc.)? Thx in advance!

[email protected] said:
Hey @Rondeau79, thank you for the rom, this was actually the only one I was able to flash. (But I think the problem is on my side of the table
Is there any way to get rid of the google-parts of the rom (searchbar etc.)? Thx in advance!
Click to expand...
Click to collapse
The search bar is apart of the launcher, it is based off the Lawn chair launcher. You could always not flash Gapps and use Aptoide as store for apps..

Any suggestions on the best way to use MicroG with this ROM? It's listed here https://forum.xda-developers.com/showpost.php?p=71042083 as having signature spoofing but I could not find it. cheers.

joefidler said:
Any suggestions on the best way to use MicroG with this ROM? It's listed here https://forum.xda-developers.com/showpost.php?p=71042083 as having signature spoofing but I could not find it. cheers.
Click to expand...
Click to collapse
Some ROMs have an option button built in. Others the option is just baked in, it will work.

joefidler said:
Any suggestions on the best way to use MicroG with this ROM? It's listed here https://forum.xda-developers.com/showpost.php?p=71042083 as having signature spoofing but I could not find it. cheers.
Click to expand...
Click to collapse
Go with the Xposed method. As of late CrDroid Pie dose not support it. That would have to be a custom build.

Thanks @Rondeau79 will try Xposed. MicroG's spoofing check does not detect signature spoofing.
---------- Post added at 02:56 PM ---------- Previous post was at 02:56 PM ----------
Thanks @Rondeau79 will try Xposed. MicroG's spoofing check does not detect signature spoofing.

This will be the first ROM I flash to my phone. Can wait to get it set up!

joefidler said:
Any suggestions on the best way to use MicroG with this ROM? It's listed here https://forum.xda-developers.com/showpost.php?p=71042083 as having signature spoofing but I could not find it. cheers.
Click to expand...
Click to collapse
WoofahRayet said:
This will be the first ROM I flash to my phone. Can wait to get it set up!
Click to expand...
Click to collapse
Any questions feel free to pm me!

Thanks again for this port o.p
Ive tried all roms accept omni and this rom by far exceeds expectations. The Best Gaming Rom ive used.
I dont know what changes were made from the kernel between the 11/19 build and the 11/28 build. But I got better performance with the 11/19 kernel so i lm using the 11/19 build boot.img on the 11/28 rom update.
Battery drain is less noticeable on the latest build as the 11/19 build was draining very fast.
Once one roots this rom with a few tweaks, one will see a huge boost in performance.
Resurrection Remix was my daily driver prior because of the Led Notification light in which i love on this phone. 
 @Rondeau79 can the notification light get added to CRDroid like on RR and Aospex...?cOther than that no bugs to report.
You rock o.p..!!!

[ROM][UNOFFICIAL][10.0] AICP w GAPPS [MOTO G7 POWER]

{
"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
And all the other Developers, Testers, Donators and Users.
@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!!
If you wanna donate to me, @Electimon my paypal link is here: paypal.me/ciphermtm
Latest Stable Release Version 15.0
Download link: https://1pwn.tk/android/ocean/AicpQ/aicp-4172020.zip
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:
Included
You tell...
FAQ:
Before using the ROM:
Q. Can I have an ETA for the next build?
A. No
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!)
Preparation for A/B Roms:
01. Download TWRP.
02. Remove your google account under Settings > Accounts then factory reset your device as FRP is enforced.
03. Unlock your bootloader
04. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
05. While on Slot_A Flash copypartitions.zip (This step only needs to be completed Once only after updating from stock factory firmwares.)
06. While in TWRP choose Reboot > bootloader
07. Now you're ready for ROM Steps below
ROM - Installation:
01. Download the ROM.
02. Use terminal to boot latest twrp.img "fastboot boot twrp.img"
03. Wipe data, dalvik, system and internal storage, then format userdata.
04. Flash ROM.zip
05. Reboot > Recovery
06.Install Gapps + Magisk (if you choose)
07. Reboot > System
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!
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.
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/electimon/android_kernel_motorola_sdm632-1
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:
@Electimon
@SyberHexen
@Jleeblanch
@erfanoabdi
ROM OS Version: 10.0.x
Kernel: Linux 4.9.y
Version Information:
Status: When ever I want to release an update
Release Date: 4-15-2020
April 17 2020
- Fixed Daydream.
- Fixed Stereo Audio.
- Fixed Wifi Calling.
- Fixed Some radio issues.
- Replace stock clock app with google clock app.
- Fixed some battery issues.
- Fixed audio bugs.
You want to see a "normal" night at the "DEV office", click here!!

Anyone knows if this will work with Verizon sim with SMS working and data?

zfk110 said:
Anyone knows if this will work with Verizon sim with SMS working and data?
Click to expand...
Click to collapse
Why wouldn't it work? Or why would you have such issues. Have you swapped out your apn config file yet? You may have better luck typing Verizon's current apns in and can get data/sms working that way then just save your xml for a future swap in case you need it on another rom install on down the road. Unless im not aware of some new strange Verizon issue if you get your apns right then everything should work fine. And make sure your other settings in the roms settings/network's and internet/ are good and setup right..

Good stable rom here. Always like AICP.

Thanks for the ROM, I really like it, but I have a G7 Power with NFC, and the NFC doesn't work, do you know how to make it work? Thank you

Great Rom!?
Thanks for this hidden gem.
I was looking for a stable 10 rom for my power due to the Aosp extended rom had a few bugs later on after use.
1.Data stopped working
2.Unable to use swap.
But when I flashed this rom, I'm pleased to say this rom should be OFFICIAL!!
Only minor gripe., since gapps is pre-installed there was only 16mb of /system space.
I had to use root file browser to delete most of the Google apps in /system/product/app,,,and /system/product/priv-app.
That gave me 789mb of free space back.
Swap works, custom kernel very good, great battery life.
Thanks again O.P for this diamond in the rough!!

Saying thanks again for the ROMs for the g7power.
As of tomorrow I'll be the on the Moto G power thread.s.
Hope you guys get the new Moto g power as well and port some roms.
Love y'all stay safe guys..

I've installed AICP pie in my mido device! This is the best rom that I've got till date! But musicfx doesn't work more than half of the times! Though it does work sometimes. I'm using youtube music to stream music. Can somebody suggest me a solution for this?

Cant seem to pass safety net checks with this rom - specifically the ctsProfile is showing as False. SElinux is set to Permissive - should I try to change this? Anyone else have this issue?
PS - ROM itself is great! My favorite so far. If I can get safetynet to pass, I am keeping this one on here

timba123 said:
I used magisk module MagiskHide Props Config to edit fingerprint... it lists Motorola g7 power.
Click to expand...
Click to collapse
U use terminal emulator type su at prompt till I get # then I in su mode props hit enter then 1 enter then f enter then 15 enter then 15 wait till it's done then reboot

Thank you guys, got it working.
I am really impressed with this ROM! I have tried every single other rom for this device and none is on the same level as AICP (in my opinion). I'm really just shocked at how much smoother and clearly better it is over Stock especially. Thank you devs so much for this!!! Still testing but.....man, this is something else.

Seeing the responses from other users I really want to try out this ROM, my problem though are the Gapps..
- Do you think you would do a build without them?
- Is it possible or rather easy to remove them from the source and build it myself?
- Do you think it is enough to remove gapps installed in system- and priv-apps or are they going "deeper". I think I once read that also some apps are replaced on Gapps installation.
Thanks for your work!

I hope this is the right place for this, I couldn't find AICP for G7 power w/o GAPPS...
Thank you for a very, very well made rom. I have a Moto G7 Power xt-1955-5 and for months I tried several other roms, but either the sim card was not recognized, or everything worked except for the phone audio (I could make and receive calls but they couldn't hear me and I couldn't hear them).
When I flashed aicp_ocean_r-16.1-WEEKLY-20220604 I was really disappointed because I still had the phone call audio issue.
However, after the June 11 update, everything works!!!!!!!!
Did you do something specifically to fix it or is it just a happy coincidence?
Three more questions. How do I turn off the camera? Can I disable the camera swipe for selfie? If I load the Pixel camera (or whatever it's called) I assume it will send data to Google, correct?
Again, thanks for your work.

Can someone please explain to me the copypartitions.zip part of this procedure? I'm not exactly sure what I am supposed to flash or do there and I'm having a lot of trouble. I've got my phone rooted and whatnot I just have not been able to flash any custom roms because I'm confused about this part

Jake81345 said:
Can someone please explain to me the copypartitions.zip part of this procedure? I'm not exactly sure what I am supposed to flash or do there and I'm having a lot of trouble. I've got my phone rooted and whatnot I just have not been able to flash any custom roms because I'm confused about this part
Click to expand...
Click to collapse
I'm not expert, but AFAIK copypartitions makes sure that both partitions (A & B) have the same thing so that if something goes wrong when you flash A, there will be a backup on B.
Again, I'm no expert, but it worked for me.

[ROM][OFFICIAL][10.0] [WEEKLIES] Official AICP for Moto X Play

{
"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_msm8916
Device tree common source:
https://github.com/AICP/device_motorola_msm8916-common
Device tree source:
https://github.com/AICP/device_motorola_lux
Vendor source:
https://github.com/AICP/proprietary_vendor_motorola
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:
@jeferson1979 @althafvly @squid2 @thopiekar
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
Oficial AICP for Moto X Play, ROM for the Moto X Play
Contributors
jeferson1979, althafvly, thopiekar, squid2
Source Code: https://github.com/AICP
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Latest stock ROM
Based On: Aosp, Lineage
Version Information
Status: Stable
Current Stable Version: 15.0
Stable Release Date: 2020-08-21
Created 2020-08-21
Last Updated 2020-08-21

Reserved
- Which recovery i should use?
AICP was developed and tested using this: https://forum.xda-developers.com/moto-x-play/development/unofficial-twrp-3-2-3-lux-t3834795
- Which Gapps I can use on it?
The less size, more smooth. I would like you use pico or nano.
- Why so different code from Lineage at this source?
Because every source has it's own particularities

Reserved
Changelog: 08-28-20:
- Reworked Actions UI;
- Fixed ambien Display;
- Mediaserver and camera minnor updates.
Download from https://dwnld.aicp-rom.com/ or use the ota updater

@jeferson1979
Could you explain to me, why motorola knowing that the snapdragon 615 is 64-bit, why didn't it make a 64-bit kernel?
I feel cheated.

KUSANAGUI said:
@jeferson1979
Could you explain to me, why motorola knowing that the snapdragon 615 is 64-bit, why didn't it make a 64-bit kernel?
I feel cheated.
Click to expand...
Click to collapse
Costs reduction at the time, AFAIK

@jeferson1979
and, is there any way to make a 64 bit kernel? @squid2 said he was going to try it, but at the time he was very busy.
https://forum.xda-developers.com/moto-x-play/help/64bit-kernel-t3303672
Oh, and I'm already testing your rom, I'll send you the log and my analysis later, thanks for this rom, not even the moto x force has as much development as this device.

@jeferson1979
LOG: http://www.mediafire.com/file/1wfqpfugd3a760f/AICP-LUX-20200904.txt/file
First, thank you very much, what I have noticed is that Lineage17.1 is more fluid than aicp, I was using the simple system monitor app and I saw that there is a lot of use of gpu being on the home screen.
I don't know why the mxp rebooted by itself 3 times.
The focus error is still present.
-Record a call with the loudspeaker activated, and the recording turned out to be like this: The audio was heard in a noisy way, and the same voice was repeated, but in low volume, that is, there were 2 voices, 1 others, the first in loud volume and the second in low volume, but they were the same voice. This does not happen in LOS17.1
-I have the problem that when I open the ES file explorer app for the second time, I can no longer access it, only its information.
Lineage camera
-Panorama photo mode does not work
-I recorded a video and played it with the system gallery, and the app does not show the video well, only a static image is seen and only the audio is heard.
FOOTEJ CAMERA 2
-Hdr mode does not work.
MOTOCAMERA
-I HAVE TAKEN 2 VIDEOS, ONE WITH THE SELFIE CAMERA AND THE OTHER WITH THE MAIN CAMERA, BOTH VIDEOS ARE SEEN WITH A DIFFERENT ORIENTATION. IT IS AN ERROR OF THE APP, IT SEEMS TO ME.
-When I RECORDED THE VIDEO WITH THE FRONT CAMERA, I TAKEN 2 PICTURES IN DARK PLACES WHILE I RECORDED, I GOT THE SAME ERROR OF THE GREEN PICTURES.
In general, I have noticed more use of cpu and gpu, both becoming 100%, in low load situations, such as playing a recorded video and without having other applications running, since I use greenify, which generates a lot of heat. .
In lineageOS 17.1 I have seen little load on the gpu and cpu.
SUMMARY:
I think you should focus on LOS17.1, or a 64bit kernel (if possible), although you did a nice job.

Hi. I installed this ROM yesterday, and it works fine. I didn't try SIM card and GPS because Moto X Play is not my daily driver device anymore.
Thank you for developing.

Thank you so much for keeping this device updated! This ROM was all I could find to get my XT1563 working again, after dropping my OnePlus 3(sad times)!
I'm almost certain I just need to replace the battery, as my lux has sat in a drawer for several years now, but I was just wondering if anyone has noticed any issues with battery drain, or the battery not charging while the device is powered off. It seems to be draining much more slowly if it sits idle, but screen-on I'm losing 1-2% every couple minutes doing nothing significant. I also left it to charge last night while powered off, and it remained at 68% until I woke up and turned it on. Just thought I would ask while I wait for my new battery to arrive, and see if going back a few weeklies might help.
Thanks so much again to all involved, if it weren't for this ROM I'd be forced to get whatever I could afford from my carrier just in order to be able to get texts and calls at all!

Questions re smoothness
jeferson1979 said:
- Which Gapps I can use on it?
The less size, more smooth. I would like you use pico or nano.
Click to expand...
Click to collapse
I tried flashing with full package before I saw this post, and it definitely seems very laggy, so I was going to try again with nano. I used to flash full or micro years ago without issues, but that was like 1y or less after launch.
I saw in the thread for HavocOS someone saying to
"lower down your display resolution (from 1080 to 720)"
and was wondering if that might help for AICP as well. I couldn't find an option for resolution in settings and so was going to try using an old zip I have laying around from years ago that flashes DPI from TWRP, and try flashing a dpi of like 280 or so. Would you recommend this, or do you think nano gapps would be enough?
Thanks again man, this ROM really saved me!

hi, can you do something for the cam focus ??its a bit weird ??!! good rom by the way
and for the sd card, i mean for the photo cam, you can't saved the picture, into the sd card .

hello, i tried to install the last update, bootloop (clean flash) , I go back to the version
08/01/2021q-15.0WEEKLYaicp_lux_q-15.0-WEEKLY-20210108.zip
and everything is installed normally .

Nice, this ROMS rocks !

Hi, since last update (15.0 weekly 20210416), my SIM card is not detected ! This is a pblm

spart_tan said:
Hi, since last update (15.0 weekly 20210416), my SIM card is not detected ! This is a pblm
Click to expand...
Click to collapse
Clean cache in TWRP

Download link last version https://media.aicp-rom.com/vault/lux/

[ROM][UNOFFICIAL][matisse][millet] CypherOS 11

New Updates for CypherOS are online.
Changelog
-Security Patch October '21
-Synced with LOS-Source
-A lot of work under the Hood from @matteo0026

Wonderful rom sir. My first issue is that Im not able to sign into playstore when or get past "Getting tablet ready" it always says "Couldnt connect" Not sure if its the rom or the gapps but im using opengapps. Anyway, thank you so much for the hard work that you have done with this rom. Extremely impressed. Thank you so much and looking forward to see more of your work.

Dvalin21 said:
Wonderful rom sir. My first issue is that Im not able to sign into playstore when or get past "Getting tablet ready" it always says "Couldnt connect" Not sure if its the rom or the gapps but im using opengapps. Anyway, thank you so much for the hard work that you have done with this rom. Extremely impressed. Thank you so much and looking forward to see more of your work.
Click to expand...
Click to collapse
Are you sure Wifi is connected?
If yes, try a different package of Gapps or try to restore a older backup (/data only) from a different ROM, if you have. Also be aware, that our tablets cannot connect to Routers with WPA3.
This will be fixed in one of the next builds.

crazydrive22 said:
Are you sure Wifi is connected?
If yes, try a different package of Gapps or try to restore a older backup (/data only) from a different ROM, if you have. Also be aware, that our tablets cannot connect to Routers with WPA3.
This will be fixed in one of the next builds.
Click to expand...
Click to collapse
I tested mindthegapps from this link https://www.cyanogenmods.org/downloads/mindthegapps-11-0-download/ its letting me setup, so it just opengapps that is the issue. Will share more later

Dvalin21 said:
I tested mindthegapps from this link https://www.cyanogenmods.org/downloads/mindthegapps-11-0-download/ its letting me setup, so it just opengapps that is the issue. Will share more later
Click to expand...
Click to collapse
Aye. Sometimes the Setup Wizard is causing troubles.

logcat and kernel logs. Also, the button for the camera is so low on the screen its cut off. I tried to make a phone call earlier, but it would just end the call immediately. Im able to get on the internet with 4G though

Dvalin21 said:
logcat and kernel logs. Also, the button for the camera is so low on the screen its cut off. I tried to make a phone call earlier, but it would just end the call immediately. Im able to get on the internet with 4G though
Click to expand...
Click to collapse
Hi. I´ve tested the Issues you mentioned.
The Camera App seems to be broken or has a wrong resolution. That´s nothing i can fix but i´ll report it to the devs. As a workaround install Open Camera. This App is working normal.
I tested phonecalls (in and out) with 4G and Edge. Both are working for me.
Maybe there´s an issue with your local provider. If the problem persists, i would suggest to dl ROM and Gapps again (maybe a file is corrupted), delete your ROM in TWRP + format /data and do a clean install of both, ROM and Gapps. Often this will fix those errors.
Your logcat is looking not too bad except a crash of firebase, what definetly could cause the trouble. But we´ll see it, if you´ve done a clean and fresh installation.

Hi, I got the SM-T531 tablet and I'm going to download this ROM and see how it behaves I will do all the possible tests I can do, to contribute. There's no way the 3g works right, just connections right?

Utherbone said:
Hi, I got the SM-T531 tablet and I'm going to download this ROM and see how it behaves I will do all the possible tests I can do, to contribute. There's no way the 3g works right, just connections right?
Click to expand...
Click to collapse
Yes, unfortunately 3g isn't working at any ROM from 9 to 11.
Matteo is working on it but with no success so far.

New Files are up!
-synced with LOS-Source
-Security Patch November 2021
-all Devices are now able to use WPA3

Hi @crazydrive22 . I'll take the opportunity and ask you a question of mine. I'm having trouble flashing any SM-T531 compatible roms. I will list the steps I followed.
1 - Flasing twrp with heimdall. At first I tried here: https://twrp.me/samsung/samsunggalaxytab4101.html but ta off the link there.
I downloaded it here on the XDA forum: https://forum.xda-developers.com/t/recovery-3-5-2_9-unified-matisse-millet-twrp-recovery.4019831/ ;
2 - full wipe and format;
3 - Flashing this rom (with or without gapps) Resulting: Loop in Samsung logo or should I wait too long?
Thanks for working.

Utherbone said:
Hi @crazydrive22 . I'll take the opportunity and ask you a question of mine. I'm having trouble flashing any SM-T531 compatible roms. I will list the steps I followed.
1 - Flasing twrp with heimdall. At first I tried here: https://twrp.me/samsung/samsunggalaxytab4101.html but ta off the link there.
I downloaded it here on the XDA forum: https://forum.xda-developers.com/t/recovery-3-5-2_9-unified-matisse-millet-twrp-recovery.4019831/ ;
2 - full wipe and format;
3 - Flashing this rom (with or without gapps) Resulting: Loop in Samsung logo or should I wait too long?
Thanks for working.
Click to expand...
Click to collapse
Hi.
First boot can take a lot of time. If it's not booting i would suggest to flash Stock 5.0.2 and start again from scratch. It's nescessary to had 5.0.2 installed once to make sure, that the Bootloader is updated. The Bootloader from KitKat (4.x) is not working with LineageOS 9 or newer and it's forks like crDroid or Cypher. The TWRP from Matteo is good, it's the lastest one and working well. But i can't tell you anything about Heimdall. I'm using Odin only to flash Stock or TWRP.

crazydrive22 said:
Hi.
First boot can take a lot of time. If it's not booting i would suggest to flash Stock 5.0.2 and start again from scratch. It's nescessary to had 5.0.2 installed once to make sure, that the Bootloader is updated. The Bootloader from KitKat (4.x) is not working with LineageOS 9 or newer and it's forks like crDroid or Cypher. The TWRP from Matteo is good, it's the lastest one and working well. But i can't tell you anything about Heimdall. I'm using Odin only to flash Stock or TWRP.
Click to expand...
Click to collapse
Thanks for the answer, it must be the 4.4.x bootloader, I didn't even ask if I had the 5.x.x one, I'm flashing the 5.0.2 About haimdall. It's wonderful, a point that can be negative is that the process is more manual, you must select each file for its respective partition, the good thing is that with it you can capture the pit file, it is very rare for an error to occur except if there is a problem on the PC or cable. It works on Linux and Windows and Mac OS X. I will return with news.

This is working amazing on my SM-T530NU, far better than whatever Nook bloat that was running before.

Installed and tested in matisselte, very good rom, very fluid. Everything works perfectly,
I will continue using this rom, very happy with how it works.
I hope you continue with the updates. Great job

groulo said:
Installed and tested in matisselte, very good rom, very fluid. Everything works perfectly,
I will continue using this rom, very happy with how it works.
I hope you continue with the updates.
Click to expand...
Click to collapse
THX.
Updates every Month ca. 15th, maybe earlier.

Hello again @crazydrive22. I tested this rom, conclusions, this rom in my normal use, very usable with tricks in developer options "disable animations scale and enable acceleration 2d". Overall is good.
Sorry. I stay practice English, on this time don,t use translator

New Builds are up.
Changelog
-synced with LOS-Source
-Security Patch December 2021

I need help, I have a problem, I have gone to update and I have restarted in recovery mode, but the tablet does not start, it is in a loop restarting all the time. I have disconnected the battery and the problem continues.
What I can do?

Better Mobile App

welcome