[ROM][UNOFFICIAL][9.0.0_r56] [F500,LS991,H81x,US991,VS986] AOSiP 9.0 Final

[ROM][UNOFFICIAL][9.0.0_r56] [F500,LS991,H81x,US991,VS986] AOSiP 9.0 Final - G4 Android Development

Pie-related bugs
https://github.com/Suicide-Squirrel/issues_pie/issues
TWRP for Pie
https://forum.xda-developers.com/g4/development/recovery-twrp-3-touch-recovery-t3442424
LG G4 Users Group on Telegram
A Telegram group for us to hang out and discuss and share logs relating to the LG G4
https://t.me/joinchat/EwLibA3rnTMbuY4KHC2R8Q
This ROM is compatible with UsU
[F500,LS991,H81x,US991,VS986]

Frequently Asked Questions (FAQ)
Note, I have shamelessly kanged this from the LOS16 thread by @steadfasterX
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!
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:
logcat GUIDE
If you encountered a kernel panic follow FAQ #6 in this post instead.
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: It looks like the CPU cores 5 and 6 are disabled - how can I fix that?
TLDR;
There is no fix required! it is fully ok when those are idle. they get hot plugged whenever needed.
Details:
we have 2 clusters of CPU cores resulting in a Hexa-core CPU set: (4x1.4 GHz Cortex-A53 & 2x1.8 GHz Cortex-A57)
the big one (2 CPU cores - higher performance = more battery drain, more heat which potentially causing the: bootloop issue) and the little (4 CPU cores - less battery drain but a bit slower) are handled dynamically based on the load of your device.
the big cluster will run ONLY when it is NEEDED - i.e. high load.
so when you look closer: those are not DISABLED they are IDLE which is a big difference.
Q #04: I get a kernel panic or green/purple/blue screen how to grab logs for this?
You need a ROM with pstore fully enabled and working (pstore = debug kernel panics/oops happened in a ROM)!
All builds starting from 2019-08-15 on support pstore due to: commit#1, commit#2, commit#3
This is a 2-site change if you want to make use of it in TWRP you must install the latest TWRP "PREVIEW" release as well (TWRP is only able to show pstore logs when the ROM is able to write them so I needed to fix pstore in the ROM first (see above commits #1 + #2 )).
Besides those 2 patches these kernel configs were set: PSTORE
You can check if a ROM does support writing pstore logs by:
as soon as possible on a fresh boot:
Code:
adb shell
dmesg | grep "ramoops|pstore"
Code:
[ 0.000000] cma: Found [email protected], memory base 0x000000001fe00000, size 2 MiB, limit 0xffffffffffffffff
[ 0.000000] cma: CMA: reserved 2 MiB at 0x000000001fe00000 for ramoops_mem
[ 0.200846] cma: Assigned CMA region at 0 to ramoops.78 device
[B][ 3.957553] console [pstore-1] enabled[/B]
[B][ 3.957939] ramoops: attached [email protected], ecc: 16/0[/B]
[ 3.958079] drv probe : 200 ramoops 3744
[ 6.262463] SELinux: initialized (dev pstore, type pstore), uses genfs_contexts
or (if you are not fast enough) this ensures mostly the same check:
Code:
adb shell
ls -la /dev/pmsg0
Code:
crw-rw-rw- 1 camera camera 254, 0 2015-01-05 04:54 /dev/pmsg0
If you get no output your ROM does not support pstore logs.
From now on when you encounter a kernel panic and you are able to reboot without taking out the battery (taking out the battery will erase RAM):
1) reboot (without taking out the battery!) to either TWRP or (if you have root access) to your ROM
2) grab everything need from here: /sys/fs/pstore/ (e.g. adb pull /sys/fs/pstore/)
If you don't have a pc near you can do it directly from the device as well:
Enable the terminal app in developer options or download any
Open the terminal app.
su
cd /sdcard/Download
tar czf pstore.tgz /sys/fs/pstore
Attach pstore.tgz to your post.
It is crucial important that you do this only after the reboot happened . It's not important "when" though - as long as the device stays powered on.
Developers note:
convert PMSG log
Code:
tr -cd '\11\12\15\40-\176' < pmsg-ramoops-0 > readable-pmsg.txt

Here are some useful apps:
GCam with night sight
Velis Auto Brightness

DT2W is back
Hello all,
New h811/h815 builds uploaded today with Double Tap to Wake reimplemented.
I have rebased on SFXs trees, so now the device should be even more stable..
Enjoy!!

aoleary said:
Hello all,
New h811/h815 builds uploaded today with Double Tap to Wake reimplemented.
I have rebased on SFXs trees, so now the device should be even more stable..
Enjoy!!
Click to expand...
Click to collapse
Very happy to see that DT2W is back! This is 1 of the 3 features I can't stand without!
The other 2 are:
- Power button-long presso to turn on torch
- Metadata working for bluetooth car device
Are these features workin? If yes I will test this ROM immediately!

gioyann said:
Very happy to see that DT2W is back! This is 1 of the 3 features I can't stand without!
The other 2 are:
- Power button-long presso to turn on torch
- Metadata working for bluetooth car device
Are these features workin? If yes I will test this ROM immediately!
Click to expand...
Click to collapse
Long press should be there. Its a pretty standard feature for custom ROMs.. I'm on Havoc-OS at the moment..
What do you mean by metadata for Bluetooth phone call?

Please can you add full automatic internal call recording feature to any of pie based rom ?

aoleary said:
What do you mean by metadata for Bluetooth phone call?
Click to expand...
Click to collapse
When you play MP3 on the car stereo (for ex.), those info talking about name of the artist, title of the song and name of album!

Linux version
What does linux 4.x stand for? What's the difference with linux 3.10?

gioyann said:
When you play MP3 on the car stereo (for ex.), those info talking about name of the artist, title of the song and name of album!
Click to expand...
Click to collapse
It works on Havoc-OS which has the same device trees. I'll have to load AOSiP again, but it would surprise me that it doesn't work..

Biber_Golge said:
What does linux 4.x stand for? What's the difference with linux 3.10?
Click to expand...
Click to collapse
I used the thread for a different device as a base. I forgot to edit that, because as the G4 is a 3.10 kernel and a 4.x kernel would never be compatible

mkrts said:
Please can you add full automatic internal call recording feature to any of pie based rom ?
Click to expand...
Click to collapse
If the ROM doesn't already have it, I probably won't add it..

I got black screen while calling so hang up is imposible. Someone else?
Edit: it was a proximity sensor failure. Nothing to do with the rom, my excuses.

i have just tried to install this rom but it gives an error that says 'This package is for device g4, p1, 811; this device is h815'.
I have H815TR. How can i fix this issue ?

Please add jio India volt file
aoleary said:
I used the thread for a different device as a base. I forgot to edit that, because as the G4 is a 3.10 kernel and a 4.x kernel would never be compatible
Click to expand...
Click to collapse

ogun281 said:
i have just tried to install this rom but it gives an error that says 'This package is for device g4, p1, 811; this device is h815'.
I have H815TR. How can i fix this issue ?
Click to expand...
Click to collapse
The H815TR is not able to be officially bootloader unlocked, I suspect. In order to install this custom rom, you need to unlock your bootloader first, before you can do anything.
If you have not already unlocked your bootloader unofficially with the process referred to in this thread, [UNLOCK] [UNOFFICIAL] [G4] Unlock ** ANY ** LG G4 device with UsU refer to it now and read everything very carefully and make sure you understand it fully.
When you have unoffocially unlocked your bootloader, you can install TWRP for the Pie preview version and proceed to flash the H815 rom (not the H811) that is referred to in the Downloads section at the beginning of this thread.

sdembiske said:
The H815TR is not able to be officially bootloader unlocked, I suspect. In order to install this custom rom, you need to unlock your bootloader first, before you can do anything.
If you have not already unlocked your bootloader unofficially with the process referred to in this thread, [UNLOCK] [UNOFFICIAL] [G4] Unlock ** ANY ** LG G4 device with UsU refer to it now and read everything very carefully and make sure you understand it fully.
When you have unoffocially unlocked your bootloader, you can install TWRP for the Pie preview version and proceed to flash the H815 rom (not the H811) that is referred to in the Downloads section at the beginning of this thread.
Click to expand...
Click to collapse
I have already unofficialy unlocked my bootloader with all nececity stuff. I can install the other custom roms such as lineage rom AOSCP etc. But this rom gives the error i said.

ogun281 said:
I have already unofficialy unlocked my bootloader with all nececity stuff. I can install the other custom roms such as lineage rom AOSCP etc. But this rom gives the error i said.
Click to expand...
Click to collapse
FAQ #13 in the UsU thread.
Sent from my OnePlus 6T using XDA Labs

Hi guys,
Uploading new builds of AOSiP with the DT2W fixes, much improved HDR processing speeds in Google Cam and some other small stuff.

Related

[G4][14.0][TITAN] ~ AICP ~ [H815][H811][UNOFFICIAL]

{
"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
->@kessaras
->@steadfasterX
->@ThePiGuy
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: http://leech.binbash.it:8008/aicp/oreo/
Latest Stable Release Version 14.0
Download link: https://mega.nz/#F!N1ACjAxC!JOfB69vtX2P_Hr7Qz23URw
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.
2018-07-05:
Initial build
Google Apps:
Choose arm64 | 8.1 |
- Distorted Bluetooth Audio in a call
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:
Titan Kernel for LG-G4
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!!!)
Kernel source:
https://github.com/Suicide-Squirrel/Titan-Kernel-LG-G4
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
Contributors:
@kessaras, @steadfasterX, @ThePiGuy
ROM OS Version: 8.1.x Oreo
Kernel: Linux 3.10.y
Version Information:
Status: STABLE
Release Date: 05-07-2018
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
[G4][14.0][TITAN] ~ AICP ~ [H815][H811][UNOFFICIAL], ROM for the LG G4
Contributors
kessaras, steadfasterX, ThePiGuy
Source Code: https://github.com/Suicide-Squirrel/Titan-Kernel-LG-G4
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.10.x
ROM Firmware Required: v29a
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 14.0
Stable Release Date: 2018-07-05
Created 2018-07-05
Last Updated 2019-06-24

Reserved
Video teaser of the first boot.
Because I was bored to grab screenshots.
https://photos.app.goo.gl/WbzNEVoUQJwKeN8e7

kessaras said:
Video teaser of the first boot.
Because I was bored to grab screenshots.
https://photos.app.goo.gl/WbzNEVoUQJwKeN8e7
Click to expand...
Click to collapse
How it's the ROM going kessaras? What about performance and battery life in conjunction with the titan kernel?

rabinorojo said:
How it's the ROM going kessaras? What about performance and battery life in conjunction with the titan kernel?
Click to expand...
Click to collapse
Not answering such questions. For me ,
since the development repos are the same, cypher - los - or any other rom are the same.
What changes is slightly the UI and the mods of each rom.
Select and use any rom that fits better to your needs.

rom works very well, battery life is excellent ...

Big cores are permanently disabled and i can't turn them on in this rom

my core works like a watch ........

??? hehehe.. This is awesome! I love it. The screen saturation feature really improves the display! Good work team. Donations will arive shortly .

rotoko said:
my core works like a watch ........
Click to expand...
Click to collapse
Did you flash any custom kernel?

I apologize, not my core, but the built-in Titanium ...

Congrats on bringing another ROM to our G4! I'll be loading this baby on in the near future
IoIam said:
Big cores are permanently disabled and i can't turn them on in this rom
Click to expand...
Click to collapse
I'm going to go out on a limb and say that since this is also the Titan Kernel, you should be able to use the method described here:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102/post76862286#post76862286

Phanty said:
Congrats on bringing another ROM to our G4! I'll be loading this baby on in the near future
I'm going to go out on a limb and say that since this is also the Titan Kernel, you should be able to use the method described here:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102/post76862286#post76862286
Click to expand...
Click to collapse
I see, however i have no idea how to change the value. Should i use a file explorer or a terminal?

IoIam said:
I see, however i have no idea how to change the value. Should i use a file explorer or a terminal?
Click to expand...
Click to collapse
I used FX File Explorer on AOSCP. I imagine everything should work the same here. What you use is up to you

@steadfasterX; @kessaras; @ThePiGuy
Just a quick question re: the boot.image file size of 24,856 kb in the latest H811 upload vs ~10615 kb for the AOSCP 6.0 and ~10627 kb for the LineageOS 15.1
Is it solely accounted for by the difference between the Linux kernel bulkiness vs the Titan kernel? I'm presuming this rom does not contain the full bootloader stack given the contributors involved but would like to confirm this before proceeding to test it as I am on a UsU'd device and do not want the risk of a hard brick.
Thanks,
S.

Phanty said:
I used FX File Explorer on AOSCP. I imagine everything should work the same here. What you use is up to you
Click to expand...
Click to collapse
@LoLAm Guys pls can you help explain plainly how to fix the big core issue. I'm clueless on your explanations. Thanks.

Phanty said:
Congrats on bringing another ROM to our G4! I'll be loading this baby on in the near future
I'm going to go out on a limb and say that since this is also the Titan Kernel, you should be able to use the method described here:
https://forum.xda-developers.com/g4/development/g4-cypheros-t3680102/post76862286#post76862286
Click to expand...
Click to collapse
what are you talking about ? why disable the core control ? for the thermal to not offline the cores ?
And my g4 here is on the second day of use and doesn't have a big battery drain. I think it was Google app notifications I disabled...
Google app really hit our battery hard , I don't know why.

@kessaras pls be aware that the 2 big cores tend to be offline almost everytime, I don't know if this is by design but if it isn't is there anyway to fix this... There's no lag whatsoever anyway, I'm just curious.
PS. Sometimes one or both appear as online ie the switch indicates it's on, however there's no reading indicating it's actually running when I observed using kernel audiotor. Thanks.

fi5z.x9 said:
@kessaras pls be aware that the 2 big cores tend to be offline almost everytime, I don't know if this is by design but if it isn't is there anyway to fix this... There's no lag whatsoever anyway, I'm just curious.
PS. Sometimes one or both appear as online ie the switch indicates it's on, however there's no reading indicating it's actually running when I observed using kernel audiotor. Thanks.
Click to expand...
Click to collapse
I use the CPU Info quick setting tile to show my CPUs. Quite often CPU 4 and 5 show 0 (off) but they do come back on at other times. This is with a default setup, I have not messed around with any governor settings. The tile says CPU 0,1,2,3 are on blu_active and CPU 4,5 I conservative. In Kernel Adiutor on its Overall page it shows that big and little cores never used deep sleep.
I haven't noticed lag as such either. Perhaps they are just very good battery saver settings (but why no deep sleep then?)
Darren
Sent from my LG-H815 using Tapatalk

sdembiske said:
Just a quick question re: the boot.image file size of 24,856 kb in the latest H811 upload vs ~10615 kb for the AOSCP 6.0 and ~10627 kb for the LineageOS 15.1
Is it solely accounted for by the difference between the Linux kernel bulkiness vs the Titan kernel? I'm presuming this rom does not contain the full bootloader stack given the contributors involved but would like to confirm this before proceeding to test it as I am on a UsU'd device and do not want the risk of a hard brick.
Thanks,
S.
Click to expand...
Click to collapse
You can just verify it by yourself. Open the zip and if you see a modem image or even worse sbl1 or aboot it's not safe.
If you can't find those it's safe.
The boot image sizes (a boot image contains not just the kernel but also the ramdisk) differs from ROM to ROM because a kernel can be compressed or not (~10MB diff) and what they add within the ramdisk.
Sent from my LG-H815 using XDA Labs

@fi5z.x9 the big cores ONLY work when the small can't handle the load. That's how snapdragon 808 works. I've said this many times.
Just stress test the CPU to see that the cores work fine.
Yes it's just like @DarrenNewsgroup said. This is an art. It's made by me in kernel level and it's the best battery life without performance loss. Ofc I could improve the speed , overclock , downclock , I could do a lot more. But no need.
Maybe , I've never experimented this , I could change how snapdragon 808 works and use all six cores ignoring the load on the small. But thats something that will keep the big cores running and your battery go down way too fast.

[ROM][PIE][UNOFFICIAL][TITAN][9.0_r21] AICP P 14.0 | Pie 9.0 | Unofficial Builds

{
"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 Pie for Titan
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 we are now based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
If there are any bugs, either we will sort them out or the GZOSP team, if it concerns their code base. This ROM isn't GZOSP 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
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 Unofficial Release Version 14.0
Download link: Unofficial Builds
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/
Google Apps(Choose ARM/Pico/9.0): OpenGapps
What's working :
--Boots
--RIL (Calls, SMS, Data)
--Wi-Fi
--Wi-Fi Hotspot
--Bluetooth
--Camera
--Camcorder
--Audio
--Flash
--Night Mode
--Enforcing Build
What's not working :
--Power off/Reboot to recovery has issues, use hardware buttons combinations to boot into recovery/turn off
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 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. 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" 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 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 Pie. 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 for the first time:
(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. 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 might 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!
The root solution should be flashed together with every OTA update (= ROM Update)
Currently supported Root Solution:
Magisk stable
Magisk versions higher than 17.2 doesn't usually require to be flashed on every dirty flash. Depending on the device, you may need to flash it every time. Unless your maintainer says otherwise it should be fine.
PREREQUISITE FOR OTA ("Over-The-Air" Updates):
To be able to flash using the built-in OTA app, TWRP recovery is needed.
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!!!)
Kernel source:
Source Code
ROM & Additional links:
AICP Gerrit Code Review
AICP on Github
AICP G+ community
Contributors:
thedeadfish59
Device Source Code: Device Tree
Credits for titan:
@LuK1337 : for trees, our codes and works mostly depends on his code
@RenanQueiroz : For his trees, cant thank him enough, all pie builds are based on his fixed trees
@jhenrique09
@AdrianDC
@luca020400
Motorola : For providing the Kernel Source Code
CM/LOS Team
ROM OS Version: 9.0.x Pie
Kernel: Linux 3.4.x
Based On: GZOSP
Version Information:
Status: TESTING-Unofficial
Release Date: 11-26-2018
You want to see a "normal" night at the "DEV office", click here!!

Screenies
These arent enough? Flash to see more!

Changelog
Code:
[U]First Build(11-26-2018)[/U]
--Initial Release With OpenGL force enabled
[U]Build(11-30-2018)[/U]
--Mobile Data fixed
--Performance Improvements
[U]Build(12-11-2018)[/U]
--Reverted to SkiaGL instead of OpenGL
--SElinux is set to Enforcing
--Fixed boot issue (Reboot to recovery/Stuck in boot)
--Updated with AICP source
--December Security Patch Update (Android 9.0.0_r21)
--Added FMRadio
--Added the ability to download Motorola apps from the Play Store
--ZRAM re-enabled and set to 256 MB
--Fixed bluetooth app force close when connecting to an AV receiver that supports AAC
--Performance fixes
--Fixed Instagram/WhatsApp video playback
[U]Build(12-17-2018)[/U]
--Fixes offline charging
--AICP updates (fixes clock AM/PM and many feature updates)
--Some more SElinux Enforcing fixes
[U]Build(03-08-2019)[/U]
--Fixed hotspot
--Fixed Sim Settings Crashes
--AICP updates
--Stable enforcing build
--Built in Equalizer (JamesDSP)
--Some more SElinux Enforcing fixes
[U]Update(29-03-19)[/U]
--Fixed Boot issue (Neither turns off nor goes to recovery)
--CPU fixes
--Some minor changes
Common Ques:
Q: Is there any common Pie discussion thread available?
A: Sure here it is! https://forum.xda-developers.com/moto-g-2014/general/discussion-pie-rom-discussion-thread-t3834902
Q: Are you going to update it daily?
A: Only if I get time...
Q: Can you make overclock kernel for this rom?
A: Nope (If I do, that would be a separate project)
Q: Suitable for Daily driver?
A: Check issues section, rest are fine in ROM
Q: Are you going to fix bleh?
A: Whenever I will feel to fix, whenever it will be possible
Q: Screenshots?
A: Check #2
Q: Will this rom become official?
A: I am lazy, maybe in future
Q: When will you release the next build?
A: Asking for ETA is a sin
Q: Want to report bugs! Device is dancing like a maniac
A: There is an old meme I like bout this
Q: I want to donate LineageOS developers, and whoever maintaining ROMs, they worked so hard for titan
A: Here you can do that
RenanQueiroz: http://forum.xda-developers.com/donatetome.php?u=7344859
LuK1337: http://forum.xda-developers.com/donatetome.php?u=5075128
luca020400: http://forum.xda-developers.com/donatetome.php?u=5778309
thedeadfish59: https://forum.xda-developers.com/donatetome.php?u=5284910

Great!! Dowloading , tanks.

You're a machine! You keep delivering ROMs! Thank you very much @thedeadfish59
Btw it would be amazing if this would go official.....

Mobile data is not working and sim settings are crashing,I'm using the dual SIM variant

DanGLES3 said:
Mobile data is not working and sim settings are crashing
Click to expand...
Click to collapse
I will check the logcat asap, this rom is still under development, thanks for providing logcat

thedeadfish59 said:
I will check the logcat asap
Click to expand...
Click to collapse
That was quick, outside of mobile data everything else is great,it seems with every new pie ROM the titan seems to always get a little faster and smoother. ,Thx for the quick response BTW
---------- Post added at 07:26 AM ---------- Previous post was at 06:38 AM ----------
I found out,It seems you are missing the libcnefeatureconfig.so and libstlport.so libraries,i added them manually and fixed the mobile data issue,but sim settings menu still crashes @thedeadfish59, guess i just saved you a few minutes/hours of debugging and testing on the mobile data issue :laugh:

New Build Is Up
Update(30/11/2018)
--Mobile Data Fixed
--Performance improvements
--Updated with AICP sources
Download: From Here
Note: AICP Pie is at Development stage, so bugs may appear definitely, in such case, attach a logcat while reporting bug, thanks

DanGLES3 said:
That was quick, outside of mobile data everything else is great,it seems with every new pie ROM the titan seems to always get a little faster and smoother. ,Thx for the quick response BTW
---------- Post added at 07:26 AM ---------- Previous post was at 06:38 AM ----------
I found out,It seems you are missing the libcnefeatureconfig.so and libstlport.so libraries,i added them manually and fixed the mobile data issue,but sim settings menu still crashes @thedeadfish59, guess i just saved you a few minutes/hours of debugging and testing on the mobile data issue :laugh:
Click to expand...
Click to collapse
AICP source has some repos missing, I fixed mobile data now, thanks for the logcat, soon simsettings will be fixed hopefully, have patience

thedeadfish59 said:
AICP source has some repos missing, I fixed mobile data now, thanks for the logcat, soon simsettings will be fixed hopefully, have patience
Click to expand...
Click to collapse
Thx,glad I could help

thedeadfish59 said:
Update(30/11/2018)
--Mobile Data Fixed
--Performance improvements
--Updated with AICP sources
Download: From Here
Note: AICP Pie is at Development stage, so bugs may appear definitely, in such case, attach a logcat while reporting bug, thanks
Click to expand...
Click to collapse
I don't know what you did in this last build the the graphical slowdown that I had in all pie ROMs so far has been almost fully fixed in this build,it's amazingly smooth now

Is night mode really working?
bluetooth?

hab12345 said:
Is night mode really working?
bluetooth?
Click to expand...
Click to collapse
Both night mode and Bluetooth are working just fine here

@thedeadfish59,is it possible to fix the blank screenshot notification,weird bright corners around notifications and icons on the home screen sometimes disappearing when being dragged while using OpenGL?,these issues don't exist if I use skiagl but skiagl has performance issues

DanGLES3 said:
@thedeadfish59,is it possible to fix the blank screenshot notification,weird bright corners around notifications and icons on the home screen sometimes disappearing when being dragged while using OpenGL?,these issues don't exist if I use skiagl but skiagl has performance issues
Click to expand...
Click to collapse
Keeping in mind, performance does matter and this is why I dont prefer using skiagl for now

thedeadfish59 said:
Keeping in mind, performance does matter and this is why I dont prefer using skiagl for now
Click to expand...
Click to collapse
Yeah I know,do you know if either skiagl is going to be improved or OpenGL is going to get fixed?, regardless,thanks for the awesome ROM,I'll stick with OpenGL for now

DanGLES3 said:
Yeah I know,do you know if either skiagl is going to be improved or OpenGL is going to get fixed?, regardless,thanks for the awesome ROM,I'll stick with OpenGL for now
Click to expand...
Click to collapse
I dont think skiagl is going to be better, it will be as the way it is, titan is oldAF now, its a legacy device

thedeadfish59 said:
I dont think skiagl is going to be better, it will be as the way it is, titan is oldAF now, its a legacy device
Click to expand...
Click to collapse
Yeah,hope the OpenGL bugs can be ironed out in the future,or skiagl improves (unlikely but who knows), strangely a lot of devices with pie custom ROMs are having issues with skiagl, including newer and more powerful devices like the LG G2 and Lenovo Vibe K5,it seems it's a issue with the graphics drivers or something

Everything is working fine but the hotspot is not working, and the QS tiles is not aligned perfectly other than that the ROM is perfectly fine. Sorry I forgot to take screenshots and flashed other ROM

[ROM][10.0.0][Himawl] Android Ice Cold Project 15.0 [Unofficial]

{
"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 we was based on the "Ground Zero Open Source Project" (GZOSP) for Android Pie.
For Android 10 we are now full AOSP-based.
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
SlimRoms team
Resurrection Remix team
Community
...
@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@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!!
Download-Links:
ROM: https://mirror.codebucket.de/claymore1297/AICP/15.0/hima
TWRP (SAR): https://github.com/CaptainThrowback/android_device_htc_hima/releases/tag/3.3.1-0_CPTB-20200116-02
GAPPS: https://sourceforge.net/projects/opengapps/files/arm64/beta/
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.
What's working
-wifi
-mobile data
-camera
-bluetooth
-NFC
-audio
-DT2W
-AICP Themes
-GPS
-mobile data signal strength
What's not working
- encryption
-DT2S
FAQ:
Before using the ROM:
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. Xposed is not yet released for Pie, however you can try to use edxposed .
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, 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" 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. (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 Pie. 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).
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 canary
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_htc_msm8994
Device tree source:
https://github.com/AICP/device_htc_hima
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[/B]
Contributors:
@Claymore1297
@k4y0z
@eyosen
The following information is ONLY needed if you are not opening up a devdb thread on XDA!
ROM OS Version: 10.0 Android 10
Kernel: Linux 3.10.108
Requirements
HTC Firmware: 4.x
TWRP: 3.3.1
Version Information:
Status: BETA
Release Date: 14-09-2019
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
AICP 15.0, ROM for the HTC One (M9)
Contributors
Claymore1297, eyosen, k4y0z
ROM OS Version: Android 10
ROM Kernel: Linux 3.x
ROM Firmware Required: 4.x
Based On: AOSP
Version Information
Status: Beta
Created 2019-09-14
Last Updated 2019-09-14
XDA:DevDB Information
AICP 15.0, ROM for the Verizon HTC One (M9)
Contributors
Claymore1297, eyosen, k4y0z
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
ROM Firmware Required: 4.x
Based On: AOSP
Version Information
Status: Beta
Created 2019-09-14
Last Updated 2020-01-16

We are introducing in Android 10 a vendor partitionon hima. So please follow the OP and install the linked TWRP, til @Captain_Throwback will release a official version.
So hima is not treble, but has a smell of treble
Also please note, that android Q introduces System-As-Root (SAR), so flashing GAPPS will only work properly with the linked TWRP.
There is also a GAPPS linked that will work with Q until official GAPPS are released.

Reserved #1

#### New build is up!! ####
the build is containing mainly the following:
-GPS
-Mobile signal strength indication
-minor fixes
Enjoy!

Great booting! Thank you, devs.

#### New build is up!! ####
the build is containing mainly the following:
-video playback issue fixed
-Jelly browser-app included
-minor fixes
Enjoy!

Happy to create a dev ticket or whatever is required but wanted to see if anyone else is seeing a big lag time between unlocking and having the home screen show up? I tried both swipe lock screen and pattern lock and both are doing the same thing.

nogoldformarfa said:
Happy to create a dev ticket or whatever is required but wanted to see if anyone else is seeing a big lag time between unlocking and having the home screen show up? I tried both swipe lock screen and pattern lock and both are doing the same thing.
Click to expand...
Click to collapse
Not here. Maybe a log would be helpful.

awesome, thank you to the dev team! boots fine and seems to run. although i got stuck in a boot loop after flashing magisk v19.3. is there a different way to install magisk or different version to use? or should i use a different method to root?

Xzanthurus Gorthamus said:
awesome, thank you to the dev team! boots fine and seems to run. although i got stuck in a boot loop after flashing magisk v19.3. is there a different way to install magisk or different version to use? or should i use a different method to root?
Click to expand...
Click to collapse
well now i am using a magisk canary build and it seems to be working.
---------- Post added at 08:57 PM ---------- Previous post was at 08:30 PM ----------
the Aicp Extras screens are blank for me

#### New build is up!! ####
the build is containing mainly the following:
-alarm clock issue fixed
-warn-message on boot fixed
-CTS failure fixed
-minor fixes
AICP features added:
-cpuinfo widget
-added various tiles
-improved dialer settings
-batterybar (but colorized feature is missing right now)
-some notification customizations
-extended chargeinfo on lockscreen
-unlock pin scramble
Enjoy!

Joined the XDA forums just to say Thanks! Thank you guys very much for your hard work, I've flashed this rom and finally after dealing with me being lazy about my firmware, have it running. I'm not quite sure if I'm rooted correctly or not however. I do get some options in the Aicp Extras app but nothing under system. I don't have any extra apps after flashing.
But thanks very much and will be happy to report anything that goes wrong I'll be using this daily.

RazzRaccoon said:
Joined the XDA forums just to say Thanks! Thank you guys very much for your hard work, I've flashed this rom and finally after dealing with me being lazy about my firmware, have it running. I'm not quite sure if I'm rooted correctly or not however. I do get some options in the Aicp Extras app but nothing under system. I don't have any extra apps after flashing.
But thanks very much and will be happy to report anything that goes wrong I'll be using this daily.
Click to expand...
Click to collapse
settings-app is more or less pure AOSP - AICP-Extras will be filled in the next months

Just an update for myself using this rom. I have experienced gps issues as I use google maps. I did attempt to navigate with maps and my location stayed static even after several attempts. It does also take a bit for it to lock on if its unable to use wifi to assist it. When i was out walking it would bounce me all over the city block.
So not sure if this is just me or what. But if there is something data wise i can provide i can do so.
Addition: So listening to audio through the headphone jack I am experiencing definit audio issues. Any audio that plays has millisecond drops in audio. It does not matter the app. I feel like its the cpu maxing out. Bluetooth is just fine.

#### New build is up!! ####
the build is containing mainly the following:
-JamesDSP
-minor fixes
AICP features added:
-DT2S
-DT2S on lockscreen
-Screenrecord fixed
Note: you have still to reflash GAPPS and regrant permissions. As soon as this issue is fixed, we will provide unofficial OTA's
Enjoy!

Claymore1297 said:
#### New build is up!! ####
the build is containing mainly the following:
-JamesDSP
-minor fixes
AICP features added:
-DT2S
-DT2S on lockscreen
-Screenrecord fixed
Note: you have still to reflash GAPPS and regrant permissions. As soon as this issue is fixed, we will provide unofficial OTA's
Enjoy!
Click to expand...
Click to collapse
Dirty flash stuck at this screen ,going to roll back to previous rom

Logcat
DaveedDB said:
Dirty flash stuck at this screen ,going to roll back to previous rom
Click to expand...
Click to collapse
I fetch one logcat here.

imknown said:
I fetch one logcat here.
Click to expand...
Click to collapse
uploaded a fixed build. Try this one

Claymore1297 said:
uploaded a fixed build. Try this one
Click to expand...
Click to collapse
Booted, great. :highfive:

#### New build is up!! ####
the build is containing mainly the following:
-JamesDSP Icon fixed
-Camera fixed
-minor fixes
AICP features added:
-Changelog
-addon.d/backuptool support
Note: This means starting with this build you don't need to reflash gapps, magisk etc.
Enjoy!

[ROM][OFFICIAL][gts4lvwifi][10] LineageOS 17.1

-- bit more friendly stock -> lineage instructions --
1. Unlock the bootloader
- Connect to WiFi network
- Enable OEM Unlock in developer options
- Turn off the tablet
- Boot to download mode manually by plugging in USB and holding all the buttons for few seconds
- Follow instructions on the screen
2. Connect to WiFi network and make sure OEM Unlock in developer options is still checked
3. Flash custom VBMeta image ( https://dl.twrp.me/gts4lvwifi/vbmeta.tar.html ) in Odin ( use AP slot )
4. After flashing VBMeta, boot to stock. It'll likely ask you to wipe data, if so do that
5. Connect to WiFi network and make sure OEM Unlock in developer options is still checked
6. Now you can flash TWRP ( https://dl.twrp.me/gts4lvwifi ) in Odin ( use AP slot once again ), for convenience you can hold volume up while flashing it so that you boot to recovery right after it's flashed
7. Install Lineage × whatever else you need ( gapps, addon-su, ... )
8. Format data
9. Reboot ( make sure to not install TWRP app when TWRP asks you to )
---
Also Odin download for those who can't find it on their own https://build.nethunter.com/samsung-tools/Odin_3.13.1.zip
( sha1sum 1057496afa34bfdf7e77caf0b99207dca77fcb2d )

Builds 20200824+ depend on Android 10 firmware, and thus from now on the recovery will abort the installation if you're still on Android 9 one.
You can update the firmware by flashing following Odin package: https://github.com/luk1337/gts4lv-fw/releases/tag/T720XXS2CUA3.
After the firmware update you should be able to flash newer builds.

Well.. that was faster than expected. Thank you very much for your dedication.
Which gapps are you currently using or recommending? Opengapps doesn't seem to have gapps for 10 yet.
Also any special instructions for flashing when coming from your previous los16 rom?

LuK1337 said:
LineageOS is a free, community built, aftermarket firmware distribution of Android 10, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
Download the latest build and gapps
Reboot to recovery
Flash the latest build and gapps
Reboot
Downloads :
Builds :
https://www.androidfilehost.com/?w=files&flid=299579
http://downloads.codefi.re/jdcteam/luk/lineage-17_0/gts4lvwifi
https://sourceforge.net/projects/luk-lineageos/files/gts4lvwifi/lineage-17.0
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
XDA:DevDB Information
[ROM][UNOFFICIAL][gts4lvwifi][10] LineageOS 17.0, ROM for the Samsung Galaxy Tab S5e
Contributors
LuK1337
Source Code: https://github.com/LineageOS
ROM OS Version: Windows 8 Mobile
Version Information
Status: Testing
Created 2019-09-24
Last Updated 2019-09-24
Click to expand...
Click to collapse
Wow!!!! Thanks op!

andre0005 said:
Well.. that was faster than expected. Thank you very much for your dedication.
Which gapps are you currently using or recommending? Opengapps doesn't seem to have gapps for 10 yet.
Also any special instructions for flashing when coming from your previous los16 rom?
Click to expand...
Click to collapse
Apparently https://sourceforge.net/projects/opengapps/files/arm64/beta/ works.

I had the opportunity to test the image yesterday as kind of a preview. After killing the setup wizzard, it worked really great. The switch from LOS 16 to 17 was easy.
Rooting had to be done with magisk (current stable was fine) as Luk told me that superSU probably won't work.
I eventually reverted to LOS 16 mainly because of personal discomfort. No Trebuchet, some settings dialogues not (yet) ported and Titanium Backup did not work (there were no buttons displayed - could not even press the problems? button as it was not there ). I personally decided to wait a bit until I will return to LOS 17 on that device.

That was fast. You got me

inka$$o said:
I had the opportunity to test the image yesterday as kind of a preview. After killing the setup wizzard, it worked really great. The switch from LOS 16 to 17 was easy.
Rooting had to be done with magisk (current stable was fine) as Luk told me that superSU probably won't work.
I eventually reverted to LOS 16 mainly because of personal discomfort. No Trebuchet, some settings dialogues not (yet) ported and Titanium Backup did not work (there were no buttons displayed - could not even press the problems? button as it was not there ). I personally decided to wait a bit until I will return to LOS 17 on that device.
Click to expand...
Click to collapse
Did you perform a full wipe before flashing?
Also how did you 'kill' the setup wizard?

There is an issue with twrp decrypting storage on Los 17. Is this more than likely a twrp issue?
I also can't install apps, probably because no access to SD card.

suzook said:
There is an issue with twrp decrypting storage on Los 17. Is this more than likely a twrp issue?
Click to expand...
Click to collapse
TWRP issue.

LuK1337 said:
TWRP issue.
Click to expand...
Click to collapse
Apps won't install from play store also
Unfortunately I can't download anything, since SD card is encrypted. Guess I will go back to Los 16. Thanks anyway op.

suzook said:
Apps won't install from play store also
Unfortunately I can't download anything, since SD card is encrypted. Guess I will go back to Los 16. Thanks anyway op.
Click to expand...
Click to collapse
>Apps won't install from play store also
Format data; reboot and they should install fine now.

LuK1337 said:
>Apps won't install from play store also
Format data; reboot and they should install fine now.
Click to expand...
Click to collapse
Will give it a shot.

andre0005 said:
Did you perform a full wipe before flashing?
Also how did you 'kill' the setup wizard?
Click to expand...
Click to collapse
I started with my device running LOS16 already. If you're coming from stock, you should stick to the instructions for the LOS16 installation in the other thread - just use instead of LOS16 image the LOS17 image.
If you have already LOS16 on the device:
-> Boot to Recovery
-> install LOS 17 image
-> if desired stable Magisk for rooting
-> if desired these openGAPPS (was told to use them - they worked fine)
-> FORMAT data (wipe doesn't do the trick, as it doesn't do it when installing LOS 16)
After facing the problem with the setup wizzard I was told to simply delete it.
Boot to Recovery, mount system partition and open the terminal.
The command is:
rm -rf /system/priv-app/SetupWizard
After that, the wizard is gone and you can boot to system. You'll have to manually go through the settings to set up everything though.

Are there any launchers other than the included that work with the new gesture navigation?

andre0005 said:
Are there any launchers other than the included that work with the new gesture navigation?
Click to expand...
Click to collapse
No.

OK, got it set up properly with the format data. Just a couple things. Black theme doesn't work, and immersive mode force crashes settings app when trying to access it. Not complaining, just letting you know.

suzook said:
OK, got it set up properly with the format data. Just a couple things. Black theme doesn't work, and immersive mode force crashes settings app when trying to access it. Not complaining, just letting you know.
Click to expand...
Click to collapse
Use a standalone dark theme toggle, not 'Style' one.

@LuK1337 Thanks a lot for the build. Time to buy the Tablet.
One Question:
 @LuK1337 or anyone, are the corners rounded like that of the stock ROM or are the corners sharp?

[ROM][testing] AICP 15.0 - q10.0 - apollo (Sony XZ2 Compact)

{
"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
SlimRoms 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/
Note: No official builds for now.
Test builds: https://androidfilehost.com/?w=files&flid=309318
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)
- 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.
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.
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. However, please make sure to backup your device regularly in case something goes wrong.
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!)
0. Install the latest stock ROM, ideally to both slots or use the LineageOS copy-partitions.zip
1. Boot a current TWRP
2. Factory reset
3. Flash the ROM zip
4. Optional: Reboot to recovery, then flash add-ons like GApps, Magisk etc.
How to upgrade from an older AICP build to a newer test build:
1. Make sure you have advanced reboot enabled: Settings/AICP Extras/Auxiliary buttons/Power menu/Advanced Reboot
2. Press the power button, select "Advanced" and "Recovery" to enter the inbuilt TWRP recovery
3. Flash the ROM zip
4. Optional: Reboot to recovery, then flash add-ons like GApps, Magisk etc.
Old instructions:
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)
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.
1. Flash latest stock ROM (52.1.A.0.672)
-> either with sony flashtool ("emma") or xperifirm + newflasher
2. Unpack the ROM tar
Code:
> tar -xzvf the_file_you_downloaded.tar.gz
2. Flash the ROM
Code:
> fastboot flash boot boot.img
> fastboot flash dtbo dtbo.img
> fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
> fastboot flash system system.img
> fastboot flash vendor vendor.img
> fastboot flash userdata userdata.img
Skip flashing userdata if you are comming from an older AICP 15.0 build and want to upgrade without losing your data!
3. Reboot to the ROM
Code:
> fastboot reboot
First boot might take a few minutes.
4. Optional: flash GApps and/or Magisk
- Enable Advanced Reboot in Settings / AICP Extras / Hardware buttons / Power menu
- Press power button, select Advanced > Recovery
- Use the inbuilt TWRP recovery to flash zips
Currently supported Root Solution:
Magisk stable
Magisk versions >= 20.3 don't usually need to be flashed on every dirty flash.
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.
Note: no official builds for now.
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_sony_sdm845/tree/q10.0
Device tree source:
https://github.com/AICP/device_sony_apollo/tree/q10.0
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:
- Olivier
- Sjll
- MartinX3 - thanks to him for allowing me to include his TWRP
- The sony open devices team and contributors
- LineageOS team
You want to see a "normal" night at the "DEV office", click here!!
XDA:DevDB Information
Android Ice Cold Project (AICP) 15.0 (q10.0) apollo (Sony XZ2 Compact), ROM for the Sony Xperia XZ2 Compact
Contributors
SpiritCroc
Source Code: https://github.com/AICP
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: Unlocked bootloader
Version Information
Status: Testing
Created 2020-04-26
Last Updated 2020-10-18

Nice job!
SpiritCroc said:
Offline charging is broken, your device will boot when you connect a charger to a switched off
Click to expand...
Click to collapse
You may want to cherry-pick this kernel patch - it will fix offmode charging.

Olivier said:
Nice job!
You may want to cherry-pick this kernel patch - it will fix offmode charging.
Click to expand...
Click to collapse
Great, thank you!

Nice work!
(Damn! Not the first who comment!)
[emoji2957][emoji12]

don't need to flash sony oem? ( https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-tama/ )

nikkdib said:
don't need to flash sony oem? ( https://developer.sony.com/file/download/software-binaries-for-aosp-android-10-0-kernel-4-14-tama/ )
Click to expand...
Click to collapse
No
It's a stock based ROM

MartinX3 said:
No
It's a stock based ROM
Click to expand...
Click to collapse
so in this rom will never be a gcam?

nikkdib said:
so in this rom will never be a gcam?
Click to expand...
Click to collapse
Yes, on the other side SODP and stock doesn't share the same bugs

nikkdib said:
so in this rom will never be a gcam?
Click to expand...
Click to collapse
In case the sony open devices program at any point in the future catches up with stock-based solutions concerning performance and functionality, I might switch to it as well.
For now, I experience the best results with a stock-based approach.

Would flashing this ROM fix the quiet microphone issue?

pakman5391 said:
Would flashing this ROM fix the quiet microphone issue?
Click to expand...
Click to collapse
The microphone is loud enough for me, but I don't know your issue personally, so your best bet is to try it out I guess

I uploaded a new build.
I have not tested a dirty flash this time, so I recommend to do a full backup to external storage in case something goes wrong if you try to upgrade from the previous AICP build (otherwise, you need a clean flash either way).
This time, it's a flashable zip (instead of images for fastboot), I have updated the install instructions accordingly.
This update features enforcing sepolicy (thanks to @Olivier and @Sjll for their work on the offcial lineage trees).
It might be ready for official AICP builds, but I don't know if it's worth it since I have not received any user feedback yet and don't know if there is actually demand... so if you use AICP, would be great if you could provide some feedback

I will definitely flash this when i'm in vacation. Needed a working phone to manage things because of a car accident.
Things are done now and it's time to say goodbye to pie.

Bug report: Proximity sensor not working
Edit: it seems that are other sensors too...

shamllakh said:
Bug report: Proximity sensor not working
Edit: it seems that are other sensors too...
Click to expand...
Click to collapse
These are working for me. Have you flashed the latest stock ROM (52.1.A.3.49) to both slots before flashing latest AICP?

SpiritCroc said:
These are working for me. Have you flashed the latest stock ROM (52.1.A.3.49) to both slots before flashing latest AICP?
Click to expand...
Click to collapse
I flashed the 52.1.A.3.49 using xperiafirmware flasher.
Then, i used the old method (fastboot method) to flash the AICP rom...
Did i miss anything?

shamllakh said:
I flashed the 52.1.A.3.49 using xperiafirmware flasher.
Then, i used the old method (fastboot method) to flash the AICP rom...
Did i miss anything?
Click to expand...
Click to collapse
So you flashed the old build (20200425_1435)? That one might need older firmware (around 52.1.A.0.672).
For the newest AICP build (20200731_1348), you need the new firmware (52.1.A.3.49) and the new instructions.

SpiritCroc said:
So you flashed the old build (20200425_1435)? That one might need older firmware (around 52.1.A.0.672).
For the newest AICP build (20200731_1348), you need the new firmware (52.1.A.3.49) and the new instructions.
Click to expand...
Click to collapse
Thanks a lot for the hint
I re-flashed the 25.1.A.3.49 via newflasher33, then flashed the AICP ROM via fastboot.
Now it works fine.
:fingers-crossed:

I finally found the time to flash my xz2c with this great rom and first i want to thank @Olivier for the official LOS base and second @SpiritCroc making this possible on this device!
As i use Aicp since years as my main Rom on my HTC One M8 i know what i'm getting with this.
However i had problems with installation: no matter what i did, i could not get the "zip" flashing to boot.
I first used Newflasher to update to the latest stock Rom, then i booted it twice to finish the carrier installation.
then i booted up twrp and flashed the zip file. Once, for the unused slot, then on the other slot. Spent a whole evening without succes...don't know what was wrong. Unfortunately i'm not used to this A/B flashing.
I then used this guide/files to extract the img files and flashed them with fastboot. That worked like a charm!
All in all this Rom has almost no problems and is faster than stock to me. Some things i noticed so far:
- biggest (and only real) problem (and as far as i heard it is the same on the LOS base) the ringtone/notification sound is is quieter than stock. I hope this can be solved, because stock was not really loud already
- flashlight brightness is not really bright, same like stock rom i think. I used some modded lib files from an Android 9 mod to make it brighter.
- i miss the option to change the visual appearance of the navbar button which was available until Android 9 in Aicp
- screen colors seems to be much more brighter, it looks much more better than stock to me
I will continue testing and see what i'll find.
All in all this Rom with it's many features is definitely worth flashing it!!!

!!! KUDOS !!!
AICP-q10.0_apollo_20200731_1348 is the first the most customizable and fully working ROM for Xperia XZ2C, if not the only one at all. I have not tested all the goods yet, but the most important features are here:
* fully working TWRP v3.4.0.0 - no issues with touch every time! until now the only TWRP working for me was the one booted with fastboot, all the flashed TWRPs had either touch issues or SD card issues
* SafetyNet basicIntegrity passed! - ctsProfile can be easily fixed with MagiskHide Props Config and therefor we have a full SafetyNet passed along with Magisk, allowing the banking and all the other sensitive apps to work
* WIFI
* Bluetooth (audio and calling)
* GPS
* fingerprint
* camera (but not the Sony one )
* encryption with TWRP decryption working
* SD card with exFAT
* notification LED
A few installations points from me
The ROM Installation was very easy and quick, but I was doing a total clean install. Here is what I did
1. Install Sony's stock ROM 52.1.A.3.49 with newflasher
2. Boot TWRP v3.4.0.0 stock version with fastboot
3. Flash AICP-q10.0_apollo_20200731_1348.zip (please note the messages, it should flash to "inactive slot B")
4. In TWRP select Reboot => Slot B => Recovery... to reboot the phone into recovery in Slot B
5. Flash Gapps
6. Format data (just in case, many times without format with other ROMs I got bootloop)
If you need fully working Magisk with full SafetyNet pass (steps are not logical and obvious but it works, tried it w few times):
1. Flash Magisk v20.1 or v20.3.... later versions breaks the basicIntegrity! If you have flashed later Magisk version simply use Magisk Unistaller zip in TWRP and flash v20.1 or v20.3
2. Boot the phone and update Magisk Manager to the latest version 8.0.2 (307) with an option inside the Magisk Manager
3. Go back to the TWRP and now you can flash Magisk v20.4 or v21.0 - this time flashing does not break the basicIntegrity and those versions are required to fix the ctsProfile
4. Install MagiskHide Props Config module in Magisk Manager
5. Install Terminal Emulator
6. Run terminal and enter the commands su followed by props
7. Change fingerprint to XZ2C with the following options: 1 => f => 27 => 20 => reboot
Ok, so what are the drawbacks? Well not much and more personal preferences I think:
1. Missing Sony's stock camera app. I tried to flash those zips below but I get "unknown error" when I try to launch the app. Do you think it would be possible to make the Sony camera work with your ROM?
https://androidfilehost.com/?w=search&s=semccamera
2. Missing custom navigation bar buttons. On the RR ROMs I used to work the most it was possible to add extra navigation buttons and assign customized actions for tap, long press, etc.
3. Slow auto brightness reaction (I can live with that)
4. Veeery low flashlight level (there was a solution for XZ1C to fix that, I have to dig a little bit to see if it can be done here as well)
5. Ambient Display - to show notifications on blocked screen
Please don't give up the project. There is not much going with the XZ2C custom development, the last and only "normal size" Android phone.
Do you think you can take a look at some of my "drawbacks" and try to fix them?
Do you think you will make some other ROMs for XZ2C in the future, like ResurrectionRemix, EvolutionX, HavocOS?

Develop Bugs

welcome