Develop Bugs

LineageOS 16.0 (build 20190425) - Microg, sig spoofing with full SafetyNet

UPDATE 06 OCT 2019: I will be returning to the project next week...
Apologies for my long silence over the past few months. After the initial release of this ROM I started focusing on getting the fingerprint sensor to work, which after some struggle I got it working. I then began spending time on removing non-FLOSS apps, services and providers that comes with lineageOS and replacing them with even better FLOSS alternatives. I made some good progress on this and created an automated build script for this. I also wanted to make the installation of the ROM easier, so I even created a script that automates the entire flashing procedure for you....yip...it's pretty cool On the security side I also made some good progress: I've applied several recommended hardening patches to the base system, and also patched the flawed mac-address randomization implementation that still exists in android today.
As I got close to preparing for release, google decided to stop support for maps-api V1 which is used by migrog. This completely broke all map views in apps and even started crashing the mobile browser. Because of the complexity of the android build workflow and tool-chain, I initially thought I screwed something up, but it was only after a couple of days of pulling my hair out people started reporting it on github. I had to wait for the mapbox implementation of microg to be released, and it eventually came a few weeks later.
It was shortly after the release that my personal priorities changed. I've been occupied (visa related) with that ever since but I'm happy to report that I should be able to return back to the project next week. Obviously some time has passed, so I will have to get up to speed with the latest releases of all of the repos and get that merged with my local changes, but that should only take a day. Hopefully there won't be many breaking changes, and if that is the case then I should be in a position to release V2 in about two weeks!
Cheers,
fanix (git-repo here: https://github.com/FaN11X?tab=repositories). Once you see commits you'll know I've started.
New build is available apparently.... don't know if it's the same dev..
UPDATE 08 MAY 2019: I'm in the process of adding support for the in-display fingerprint sensor. Stay tuned.
This is a lineageos 16.0 build from source on 25 April using latest source. The ROM is has been prepatched for system lavel signature spoofing based on the MicroG Android Pie patch (url removed, sigh). I did however change the protection level from "Dangerous" to "Signature|Restricted". This is a more secure way of enable signature patching as it requires the app using signature spoofing to be privaliaged, in other words, it needs to be installed to /system/priv-app in order for it to be granted this permission. This means that you wont be at risk of downloading and installing apps that might abuse signature spoofing.
The ROM also passes FULL SafetyNet with microg installed. It uses a custom build from Nanadroid which contains all the latest code changes which you wont find in there official releases as its not yet been packaged as a release. This solved many issues for me, like safetyNet now passing which allows me to install and run banking applications (like Barclay's Mobile Banking) and also uber seems to work just fine using the UnifiedNLP backend providers.
This custom ROM has NO google related apps or code, and you have the ability to switch on google released integration services through the microg services menu.
WORKING
So far... everything I've tested. (except fingerprint)
NOT WORKING
On-display fingerprint.
Installation steps:
1. Restore to stock firmware. I recommend the following Fastboot ROM as thats the one I used. *url removed* (download file search google "equuleus global images V10.2.2.0.PECMIXM")
2. Put device in fastboot mode (adb reboot bootloader or Power Button + Vol Down)
3. Flash using MiFlash (Find it on google and be sure to select the "FLASH ALL.bat" option at the bottom and NOT the LOCK on, otherwise you will relock your device)
4. After flashing the stock ROM, let it boot up, then enable developer options and USB debugging.
5. Flash TWRP
* adb reboot bootloader
* fastboot erase recovery
* fastboot flash TWRP_equuleus_1102.img
* fastboot boot TWRP_equuleus_1102.img
6. Once in TWRP, goto WIPE and select DATA. Enter the word "yes" and once it is complete, go back to main menu, RESTART=>RECOVERY to reboot and automatically boot back into recovery.
7. Goto WIPE again, but this time WIPE DalvicCache, SYSTEM & Cache by selecting all 3 and wiping them (NO NOT RESTART AFTER THIS STEP
8. Once wipe is complete, push the content from the download folder provided below to the sdcard folder of the phone.
* adb push download_folder_containing_all_the_files /sdcard/
example: adb push /home/fanix/Downloads/lineageosrom /sdcard/
9. Once complete, you are now ready to flash lineage ROM. Select the lineageos zip file and flash it. (filename => lineage-16.0-20190425-UNOFFICIAL-equuleus.zip)
10. Once complete, you can then reboot to system to load lineage. After going through the lineage setup, you can then install microg (if you want)
Optional - Installing microg (from latest nanodroid) FULL SAFETYNET SUPPORTED
* Boot into TWRP (adb reboot recovery)
* Goto INSTALL, and select the following file: (NanoDroid-microG-20.7.92.20190424.zip).
* NOTE: This will install microg, including MsfProxy and UnifiedNLP with 4 backend providers. It will also install Aurora Store & Fake store.
* When install is complete, reboot and once in lineage, you can configure microg. You can log into google store using Aurora, either with your own account or their anonymised account. This allows you to download anything form the google app store, including apps that require verification, like mobile banking apps.
* If you want, you can test your SafetyNET using Magisk. You can find the magisk manager in the download folder. Install that and test SafetyNET. You do NOT need to root your phone to test this, you can simply install the manager. If you want to root your phone, simply boot back into TWRP and select the magisk 19.0 zip file and that will then also root your device.
Enjoy!
DOWNLOAD LINK:
https://drive.google.com/open?id=1aJ...bkaHPw86sgHYMj

I've contacted one of the mods and asked if thye could post the link. Hope they do, otherwise if someone has the ability to post links then message me and i'll PM you the download link which you can then share to the thread.
Cheers
fanix

Hi fanix-uk,
Thank you very much! Is 3D face recognition working or just the 2d with the front camera?

mateHD said:
Hi fanix-uk,
Thank you very much! Is 3D face recognition working or just the 2d with the front camera?
Click to expand...
Click to collapse
Not sure, I haven't tried it. To be honest I've never used that feature on this phone before.

fanix-uk said:
Not sure, I haven't tried it. To be honest I've never used that feature on this phone before.
Click to expand...
Click to collapse
I tried it. Face unlock works with google smartlock. It use IR sensor, not the front camera, but it isn't 3D. So it works without light, but less secure than the stock rom version.
Btw. the rom works perfectly. Thanks again.

Is possible to have the miui camera with this rom?

mateHD said:
I tried it. Face unlock works with google smartlock. It use IR sensor, not the front camera, but it isn't 3D. So it works without light, but less secure than the stock rom version.
Btw. the rom works perfectly. Thanks again.
Click to expand...
Click to collapse
You are most welcome! Thanks for testing it... I'm working on a new release with some really cool features, including
Updated, hardened kernel.
Wireguard kernel module built into kernel.
Removal of non-FOSS apps/providers/services and replace with FOSS alternatives
Weather provider integration with openweathermap.
In-display fingerprint

perillo95 said:
Is possible to have the miui camera with this rom?
Click to expand...
Click to collapse
I can try and grab the camera app and drivers from stock and package it for you, but won't be including proprietary software in this build. I'll keep you posted.

fanix-uk said:
You are most welcome! Thanks for testing it... I'm working on a new release with some really cool features, including
Updated, hardened kernel.
Wireguard kernel module built into kernel.
Removal of non-FOSS apps/providers/services and replace with FOSS alternatives
Weather provider integration with openweathermap.
In-display fingerprint
Click to expand...
Click to collapse
Looking forward to it. I will probably try the current version as soon as I'm allowed to unlock my bootloader.

fanix-uk said:
I can try and grab the camera app and drivers from stock and package it for you, but won't be including proprietary software in this build. I'll keep you posted.
Click to expand...
Click to collapse
With miui camera and the in-display fingerprint would be a perfect ROM, Great work

thanks a lot for LOS!
Q: do i need to install gapps after ROM?

eerastov said:
thanks a lot for LOS!
Q: do i need to install gapps after ROM?
Click to expand...
Click to collapse
Yes.
Whats up with the new version? Can i help somehow?

Thanks
Hi Fanix
I really appreciate what you have done for Mi8 Pro. If you did not share your work here, I think I nearly sell my phone, as the MIUI is pretty trash.
Also, thanks for your progress on adding in-display finger sensor, after you done it I feel you can create one link for donation. I really hope you can keep develop on this phone and make LOS Andorid Q available in the future.
Kind regards
One of Mi8 Pro users
---------- Post added at 07:51 AM ---------- Previous post was at 07:47 AM ----------
I flashed this rom on my phone, it works really well. And I flashed a Gapps on my phone, work well as well. I did not flash the Nanadroid on my phone, is it necessary? I just worry about it becasue you said something related to SafetyNet, ahaha. I do not know if I do not have it, is my phone still safe?
Thanks a lot again.

fanix-uk said:
UPDATE 08 MAY 2019: I'm in the process of adding support for the in-display fingerprint sensor. Stay tuned.
This is a lineageos 16.0 build from source on 25 April using latest source. The ROM is has been prepatched for system lavel signature spoofing based on the MicroG Android Pie patch (url removed, sigh). I did however change the protection level from "Dangerous" to "Signature|Restricted". This is a more secure way of enable signature patching as it requires the app using signature spoofing to be privaliaged, in other words, it needs to be installed to /system/priv-app in order for it to be granted this permission. This means that you wont be at risk of downloading and installing apps that might abuse signature spoofing.
The ROM also passes FULL SafetyNet with microg installed. It uses a custom build from Nanadroid which contains all the latest code changes which you wont find in there official releases as its not yet been packaged as a release. This solved many issues for me, like safetyNet now passing which allows me to install and run banking applications (like Barclay's Mobile Banking) and also uber seems to work just fine using the UnifiedNLP backend providers.
This custom ROM has NO google related apps or code, and you have the ability to switch on google released integration services through the microg services menu.
WORKING
So far... everything I've tested. (except fingerprint)
NOT WORKING
On-display fingerprint.
Installation steps:
1. Restore to stock firmware. I recommend the following Fastboot ROM as thats the one I used. *url removed* (download file search google "equuleus global images V10.2.2.0.PECMIXM")
2. Put device in fastboot mode (adb reboot bootloader or Power Button + Vol Down)
3. Flash using MiFlash (Find it on google and be sure to select the "FLASH ALL.bat" option at the bottom and NOT the LOCK on, otherwise you will relock your device)
4. After flashing the stock ROM, let it boot up, then enable developer options and USB debugging.
5. Flash TWRP
* adb reboot bootloader
* fastboot erase recovery
* fastboot flash TWRP_equuleus_1102.img
* fastboot boot TWRP_equuleus_1102.img
6. Once in TWRP, goto WIPE and select DATA. Enter the word "yes" and once it is complete, go back to main menu, RESTART=>RECOVERY to reboot and automatically boot back into recovery.
7. Goto WIPE again, but this time WIPE DalvicCache, SYSTEM & Cache by selecting all 3 and wiping them (NO NOT RESTART AFTER THIS STEP
8. Once wipe is complete, push the content from the download folder provided below to the sdcard folder of the phone.
* adb push download_folder_containing_all_the_files /sdcard/
example: adb push /home/fanix/Downloads/lineageosrom /sdcard/
9. Once complete, you are now ready to flash lineage ROM. Select the lineageos zip file and flash it. (filename => lineage-16.0-20190425-UNOFFICIAL-equuleus.zip)
10. Once complete, you can then reboot to system to load lineage. After going through the lineage setup, you can then install microg (if you want)
Optional - Installing microg (from latest nanodroid) FULL SAFETYNET SUPPORTED
* Boot into TWRP (adb reboot recovery)
* Goto INSTALL, and select the following file: (NanoDroid-microG-20.7.92.20190424.zip).
* NOTE: This will install microg, including MsfProxy and UnifiedNLP with 4 backend providers. It will also install Aurora Store & Fake store.
* When install is complete, reboot and once in lineage, you can configure microg. You can log into google store using Aurora, either with your own account or their anonymised account. This allows you to download anything form the google app store, including apps that require verification, like mobile banking apps.
* If you want, you can test your SafetyNET using Magisk. You can find the magisk manager in the download folder. Install that and test SafetyNET. You do NOT need to root your phone to test this, you can simply install the manager. If you want to root your phone, simply boot back into TWRP and select the magisk 19.0 zip file and that will then also root your device.
Enjoy!
DOWNLOAD LINK:
https://drive.google.com/open?id=1aJ...bkaHPw86sgHYMj
Click to expand...
Click to collapse
hello I have tried treble version but i got MusicFX Force Close i hope you can fix this
and maybe you can port Miui Camera on this ROM thanks for your work

I found a bug :
NFC is not found in Settings and NFC Icon on status bar is error
Edit :
sometimes when opening the camera, freeze and got pop-up cannot be connected to the camera
And for musicFX is working...

Thanks
fanix-uk said:
UPDATE 08 MAY 2019: I'm in the process of adding support for the in-display fingerprint sensor. Stay tuned.
This is a lineageos 16.0 build from source on 25 April using latest source. The ROM is has been prepatched for system lavel signature spoofing based on the MicroG Android Pie patch (url removed, sigh). I did however change the protection level from "Dangerous" to "Signature|Restricted". This is a more secure way of enable signature patching as it requires the app using signature spoofing to be privaliaged, in other words, it needs to be installed to /system/priv-app in order for it to be granted this permission. This means that you wont be at risk of downloading and installing apps that might abuse signature spoofing.
The ROM also passes FULL SafetyNet with microg installed. It uses a custom build from Nanadroid which contains all the latest code changes which you wont find in there official releases as its not yet been packaged as a release. This solved many issues for me, like safetyNet now passing which allows me to install and run banking applications (like Barclay's Mobile Banking) and also uber seems to work just fine using the UnifiedNLP backend providers.
This custom ROM has NO google related apps or code, and you have the ability to switch on google released integration services through the microg services menu.
WORKING
So far... everything I've tested. (except fingerprint)
NOT WORKING
On-display fingerprint.
Installation steps:
1. Restore to stock firmware. I recommend the following Fastboot ROM as thats the one I used. *url removed* (download file search google "equuleus global images V10.2.2.0.PECMIXM")
2. Put device in fastboot mode (adb reboot bootloader or Power Button + Vol Down)
3. Flash using MiFlash (Find it on google and be sure to select the "FLASH ALL.bat" option at the bottom and NOT the LOCK on, otherwise you will relock your device)
4. After flashing the stock ROM, let it boot up, then enable developer options and USB debugging.
5. Flash TWRP
* adb reboot bootloader
* fastboot erase recovery
* fastboot flash TWRP_equuleus_1102.img
* fastboot boot TWRP_equuleus_1102.img
6. Once in TWRP, goto WIPE and select DATA. Enter the word "yes" and once it is complete, go back to main menu, RESTART=>RECOVERY to reboot and automatically boot back into recovery.
7. Goto WIPE again, but this time WIPE DalvicCache, SYSTEM & Cache by selecting all 3 and wiping them (NO NOT RESTART AFTER THIS STEP
8. Once wipe is complete, push the content from the download folder provided below to the sdcard folder of the phone.
* adb push download_folder_containing_all_the_files /sdcard/
example: adb push /home/fanix/Downloads/lineageosrom /sdcard/
9. Once complete, you are now ready to flash lineage ROM. Select the lineageos zip file and flash it. (filename => lineage-16.0-20190425-UNOFFICIAL-equuleus.zip)
10. Once complete, you can then reboot to system to load lineage. After going through the lineage setup, you can then install microg (if you want)
Optional - Installing microg (from latest nanodroid) FULL SAFETYNET SUPPORTED
* Boot into TWRP (adb reboot recovery)
* Goto INSTALL, and select the following file: (NanoDroid-microG-20.7.92.20190424.zip).
* NOTE: This will install microg, including MsfProxy and UnifiedNLP with 4 backend providers. It will also install Aurora Store & Fake store.
* When install is complete, reboot and once in lineage, you can configure microg. You can log into google store using Aurora, either with your own account or their anonymised account. This allows you to download anything form the google app store, including apps that require verification, like mobile banking apps.
* If you want, you can test your SafetyNET using Magisk. You can find the magisk manager in the download folder. Install that and test SafetyNET. You do NOT need to root your phone to test this, you can simply install the manager. If you want to root your phone, simply boot back into TWRP and select the magisk 19.0 zip file and that will then also root your device.
Enjoy!
DOWNLOAD LINK:
https://drive.google.com/open?id=1aJ...bkaHPw86sgHYMj
Click to expand...
Click to collapse
Current anything is good ！
thanks a lot again

Any news plss

Any news?
Still others are maintaining this rom, looking forward to updating

I was willing to bring up the rest of the hardware and make this device official, but I don't have the device. Is there any interest in donating a device for such purpose?

bgcngm said:
I was willing to bring up the rest of the hardware and make this device official, but I don't have the device. Is there any interest in donating a device for such purpose?
Click to expand...
Click to collapse
Would love to be in a position to do that. However, I have just had my OnePlus 6T stolen, and now need my Mi 8 Pro as a daily driver. Would be happy to donate to get the fingerprint reader working on AOSP / GSI-Treble ROMs for the MI 8 Pro.

Guide: Remove all google apps and bloat in any android rom (de_goggling lg v30)

PART 1 of 3
Had trouble posting this in XDA, got flagged by the system so the guide is broken into 3 parts.
Attachments are in part 3.
This guide is as detailed as possible so that you won't make the same mistakes I did and won't face the same problems.
Thanks to @xd4d3v and @conbak49 for your help buddies.
[TEXT IN BLUE ARE SPECIFIC TO LG V30]
THIS IS A MUCH SAFER AND EASIER WAY TO DE-GOOGLE / DE-BLOAT ANY ANDROID ROM AND IS WRITTEN SPECIALLY FOR THE LG V30, MIGHT WORK FOR ALL PHONES
AS OF POSTING THIS, I AM ON H930DS OREO ROM BUT THIS PROCESS MIGHT BE APPLICABLE FOR ANY ANDROID ROM, ANY VERSION
YOU NEED TWRP FOR THIS TO WORK. FOR ROOTING AND TWRP PLUS MAGISK RELATED PROCESS, REFER TO OTHER GUIDES ON THE V30/SPECIFIC PHONE XDA THREAD
Preparation
CHECK THAT YOU HAVE DOWNLOADED THE FOLLOWING APPS IN A FOLDER IN YOUR PC/LAPTOP)
(side note : the folder is in your pc because sometimes the phone's internal storage is encrypted and it is best to wipe all user data. We will copy this folder to internal storage after a clean install/factory reset)
A. TITANIUM BACKUP (download v8.3.3 or above from apkmirror.com)
B. Magisk 19+zip
(NOTE: if you followed @TxanMoe and @ChazzMatt 's WTF bootloader exploit for rooting the lg v30, be aware that the magisk.zip in that post is v18, you need magisk v19 for this process, but it is okay as long as you download magisk v19 from from "https://magisk.download/" website AND put it in the folder.
[ FOR THE V30, YOU NEED THESE EXTRA FILES IN THE FOLDER:
C. Encryption Disabler(Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip OR no-verity-opt-encrypt - 6.0_1_.zip(OREO) )
D. LG ROOT CHECKER Disabler(AK3_RCTD_REMOVER.zip OR lg-rctd-disabler-1.0._1.zip(OREO) )
I am on oreo so I have the ones with red OREO, the first .zips are the latest and are probably for pie and oreo both ]
DISCLAIMER:
Although we are completely removing google apps pre-bundled in the stock rom; at the end of this process, you will have a fully functioning Aurora Store . It is the same Play Store side by side without any google trackers, and is from the open source MicroG project, so relax, you will be able to download all apps(Anonymously) including paid apps(with your login) just like you downloaded apps from the play store.
BEFORE WE BEGIN
TWRP will sometimes give a error message in red saying 'unable to mount storage/system'... This often happens if you were previously working on a different storage(OTG/SD card) and TWRP fails to switch storage. If it happens :
Go to MOUNT>STORAGE>SELECT STORAGE MEDIA>INTERNAL MEMORY and try again...it will get fixed.
WARNING:
NEVER EVER START REMOVING SYSTEM APPS WITHOUT BOOTING THE ROM/SYSTEM FOR THE FIRST TIME. SYSTEM WILL CRASH AND A BOOTLOOP WILL BE JUST AROUND THE CORNER.
STEP 1: VERY VERY VERY IMPORTANT
REMOVE YOUR GOOGLE ACCOUNT AND PHONE'S SCREEN LOCK PASSWORDS FROM SETTINGS>ACCOUNTS
DOUBLE CHECK that any google account is removed from settings.
DOUBLE CHECK that ALL FINGERPRINTS/PIN/PASSWORD LOCK METHODS HAVE BEEN REMOVED OR CANCELLED
IF YOU DON'T REMOVE YOUR GOOGLE ACCOUNT, SETUP WON'T COMPLETE WITHOUT GOOGLE APPS. YOU WILL GET ENCRYPTION ERROR AND MANY OTHER PROBLEMS (I learned it the hard way)
REBOOT [IMPORTANT]
STEP 2: IF POSSIBLE HAVE A TWRP FLASHABLE ZIP OF YOUR ROM READY IN THE PC FOLDER
if you don't have a twrp flashable zip for your system, it's ok. It's just a fail-safe method.
(Note: FOR the lgV30 you can download flashable rom zip from https://forum.xda-developers.com/showpost.php?p=76584629&postcount=193 (at the very last of that post under UPDATE H930, US998, H930DS with latest stock firmware TWRP-flashable "ROMs" )
2.1 IF YOU HAVE A USB OTG/SD CARD
COPY THE FOLDER FROM PC TO USB OTG/SD CARD
STEP 3: back up your files from internal storage
It's getting WIPED/FORMATTED. Back up.

PART 2
STEP 4: TWRP AND FULL SYSTEM FORMAT
Disclaimer
We are going to format/factory reset your phone and delete all your data.
4.1 FROM TWRP
(Note: if you have magisk installed, to boot into TWRP simply go to 'Modules' in left plane of Magisk and in right pane inside 'Modules' there is option to 'reboot into recovery')
[ FOR THE LG V30, another method to boot into TWRP via volume down+power button is here: https://www.youtube.com/watch?v=VJF8oTGqohg
HARDWARE KEYS TO BOOT INTO TWRP:
> continue holding volume down and power button (10 sec)
>continue holding for the bootloader warning too
>as soon as LGV30 white logo appears on black background immediately unpress and repress the power button and
>continue holding both buttons
>a screen comes saying all your files will be deleted, press volume down button to YES, then press power button
>the same screen reappears again, press volume down button twice to YES, then press power button
>wait, phone reboots
>the same screen giving warning comes again
>Don't press any buttons
>After a while TWRP starts
4.1.A. PERFORM A FULL FACTORY RESET
In TWRP,
go to WIPE
SELECT ADVANCED WIPE
SELECT: DALVIK / ART CACHE
DATA
INTERNAL STORAGE
CACHE
(NOTE: don't wipe SYSTEM if you don't have flashable rom zip, there won't be any system to boot into)
(NOTE: after factory reset, Magsik must be re-flashed from TWRP, there will be Magisk icon in a firmware with previously Magisk installed, but it won't work)
(NOTE: many android roms now require a encryption disabler, make sure you have that in a flashble zip file for your rom)
SWIPE TO PERFORM ADVANCED WIPE, DON'T REBOOT.
THERE IS NOTHING IN INTERNAL MEMORY NOW
4.1.B FROM SD CARD/OTG
FLASH MAGISK 19+ ZIP
FLASH ENCRYPTION DISABLER ZIP
FLASH LG ROOT CHECK DISABLER ZIP
4.1.C IF YOU DONT HAVE SD CARD/USB OTG
follow STEP 5(not 5.1), after system starts connect phone to PC. copy the folder from PC to phone's internal memory.
COMPLETE STEP 4.1.B
While still in TWRP, go to WIPE and perform the default TWRP wipe then follow step 5 and 5.1 .
Remember this time you are not wiping your internal storage so 4.1.C users need not follow step 6. The copied folder is still there.
STEP 5: LET THE SYSTEM BOOT NORMALLY, DON'T CONNECT TO INTERNET
5.1 After booting up your system, configure settings to your like, manage display size, change your wallpapers etc.. to your liking.
THIS IS THE BASE SYSTEM WHICH WE WILL TAKE A BACKUP OF and which YOU WILL BE CONSTANTLY RESTORING VIA TWRP SHOULD ANYTHING GO WRONG.
5.2 ONLY FOR LG PHONES
LG Apps like HIFI Recorder and Smartdoctor have a Terms of use Screen before using that app for the first time. Removing google apps makes the terms of use app crash and consequently app like HIFI Recorder refuse to start. This is possible to bypass by the following method:
After step 5, open all Lg apps that you want to use like Hifi Recorder, Lg health etc and accept the terms and conditions. Once that is done; you can even remove those EULA app, Terms and conditions app...
I believe this is due to the lack of webview which gets removed along with 'Android System Webview'.
However, by the end of this post we will have a fully working, trackers and AD free Bromite webview.
STEP 6: MAKE SURE EVERYTHING IS FINE, COPY THE FOLDER FROM PC TO INTERNAL MEMORY/SD CARD/USB OTG AND REBOOT PHONE
STEP 7: BACKING UP YOUR SYSTEM IMAGE IN TWRP
After rebooting, reboot into TWRP via Magisk.
WHEN YOU START DELETING SYSTEM APPS, SYSTEM MIGHT NOT BOOT, GET STUCK IN A BOOT LOOP, HANG INFINITELY ETC. , IT TOOK ME 15+ SYSTEM RE-INSTALLS TO GET A WORKING LIST OF REMOVABLE APPS WITHOUT GETTING CAUGHT IN A BOOT LOOP.
RE-INSTALLING SYSTEM FROM A FLASHABLE ZIP IF ANYTHING GOES WRONG IS A LENGTHY, TEDIOUS PROCESS AND YOU WILL HAVE TO REPEAT EVERYTHING DONE TILL NOW.
TO MAKE RE-INSTALLING SYSTEM EASIER FOR YOU, YOU ARE GOING TO TAKE A COMPLETE SYSTEM IMAGE FROM A CLEAN INSTALL, THIS PROCESS IS IMPORTANT
In TWRP , go into BACKUP
Excluding 'SYSTEM IMAGE' back up everything to internal storage/SD, it only takes up a few minutes.
YOU NOW HAVE A COMPLETE MIRROR IMAGE OF YOUR SYSTEM. IF ANYTHING GOES WRONG AFTER REMOVING ANY APP, IT LITERALLY TAKES ONLY 2 MINUTES TO GET YOUR SYSTEM UP AND RUNNING FROM THE BACKUP.
STEP 8: REBOOT
STEP 9: INSTALL TITANIUM BACKUP,ALLOW ROOT ACCESS
STEP 10: FIND A LIST OF UN-INSTALLABLE GOOGLE APPS.
Personally, I think the easiest way is to download a FULLgapps package from 'opengapps.org' for your android version, extract it and find a file titled ' remove-gapps.txt ' . This gives you a basic idea of which packages are from google and which are not.
As a rule of thumb, packages with name like com.google.NSA_spyware are from google and packages with brand/vendor names like (here LG ELECTRONICS/lge) com.lge.hippityhoppityLGproperty are from your phone brand. Packages with name like com.android.teagoodcoffebad are core shared android apps, don't delete these.
Code:
UPDATE: DON'T USE THIS \ CAUSES BOOTLOOP thanks @cascabel for checking
HOWEVER, YOU CAN USE THIS FOR FINDING OUT GOOGLE PACAKGES YOU ARE UNSURE OF
[COLOR="Sienna"]There is this zip file specially made for removing gapps:
' [url]https://github.com/CHEF-KOCH/Remove-Gapps/releases[/url] '
but I didn't use that and it doesn't remove 'Android System Webview'
so it's upto you to find a list of removeable apps from your system.[/COLOR]
NOTE: nanoDroid/microG is a collection of open source softwares that combine the functionality of google services in a open source package. It is said that the nanoDroid installer automatically removes google packages during install. We will be installing nanoDroid later.
However, nanoDroid installer didn't remove google apps from the LG V30 OREO.
IF YOU SIMPLY WANT TO REMOVE SYSTEM AND GOOGLE APPS ON A HIT AND TRIAL BASIS, IT'S OK TOO AND THAT'S WHAT I DID BECAUSE WE HAVE A FULL SYSTEM BACKUP AND WE CAN RESTORE EVERYTHING EASILY IN 2 MINUTES.
STEP 10: IN TITANIUM BACKUP:
-----------------------------------------------
THIS PROCESS IS FOR BATCH REMOVING APPS THAT YOU ARE SURE ARE BLOATWARE\GOOGLE APPS like DRIVE,DUO,GMAIL etc
At the top right corner there are three icons: a search icon, a file with tick mark, and menu: Select the middle one.
This opens the 'Batch actions -ALL'
Swipe down to 'Un-install'
In Un-install, the last option is : 'Un-install all all user & system apps'
Select that, don't worry it just opens a page with all your apps.
Note the green tick mark at the top right corner.
Deselect all and select only the ones that you want to remove.
-----------------------------------------------
NOTE: YOU WILL FIND A LOT OF APPS WITH NAME ENDING IN OVERLAY like com.android.phone.overlay corresponding to an app com.android.phone.
They are very very small sized files and not full apps. I don't know if it is okay to leave them but by far there has been no problems leaving them alone.
Also if you remove the main app then TITANIUM BACKUP will show an error while trying to remove the overlay. JUST LEAVE OVERLAYS ALONE or REMOVE OVERLAYS BEFORE REMOVING THE MAIN CORRESPONDING APP.
-----------------------------------------------
DELETING APPS ONE-BY-ONE
ALSO: HOW TO KNOW A PACKAGE NAME IN ANDROID:
To know a package name like com.google.calculatorprebuilt from an app titled calculator so that you can be sure where the package is coming from (google/vendor/AOSP android), open TITANIUM BACKUP and in the first screen there is overview BACKUP/RESTORE Schedules; SELECT BACKUP/RESTORE and click any app. On the new window, select the button with YELLOW TEXT and find Package name.
If you are sure to remove this app, on this new window there is a option in RED titled UN-INSTALL!. Hit OK twice and uninstall the app.
Update: IN THE LG V30 removing 'Android Services Library 1' and 'Android Shared Library 1' causes bootloop and their name start with com.google.package....
-----------------------------------------------
STEP 12: AFTER REMOVING A FEW APPS RESTART YOUR SYSTEM
NOTE THE PACKAGES YOU HAVE REMOVED.
Often times, many apps inter-rely on each other and removing one app may cause other to crash.
IF THE SYSTEM BOOTS UP, FINE. CONTINUE REMOVING SYSTEM APPS.
STEP 13: BOOTLOOP AFTER REMOVING SYSTEM APPS/
SYSTEM REFUSES TO BOOT AFTER REMOVING GOOGLE APPS/
SYSTEM STUCK ON LG LOGO
This usually happens when you remove a core system app and the system fails to boot.
FOR A CONDITION LIKE THIS IS WHY WE TOOK A WHOLE SYSTEM BACKUP IN TWRP BEFORE (also called nAndroid Backup)
NO PROBLEM, FOLLOW STEP 14
STEP 14: RESTORING SYSTEM FROM A BOOTLOOP
1. BOOT INTO TWRP
2. GO TO RESTORE
3. RESTORE SYSTEM
4. DONE

PART 3/FINAL PART
STEP 15: TRY REMOVING APPS AGAIN FOLLOWING THE SAME PREVIOUS STEPS BUT CAREFULLY
STEP 16: INSTALLING microG services via NanoDroid
1. Download two zips from https://downloads.nanolx.org/NanoDroid/Stable/
First download NanoDroid-patcher-.zip
Secondly download NanoDroid-microG-.zip
2. COPY zips TO PHONE
3. IN TWRP, first flash the patcher then microG zip.
Note that the patcher takes a very long time.
4. In advanced wipe clear cache only in TWRP.
REBOOT
YOU NOW HAVE A PLAY STORE EQUIVALENT AURORA STORE AND OTHER CORE GOOGLE SERVICES IN OPEN SOURCE APPS.
PLEASE NOTE:
MOST OF YOUR APPS HAVE LOST THEIR PERMISSIONS NOW SO OPEN ALL APPS FROM LAUNCHER AND GIVE THEM PERMISSIONS. IT'S EASY. EVEN FILE MANAGER WILL ASK FOR PERMISSIONS. THIS IS DUE TO THE PATCHER PATCHING SOME SYSTEM FILES
STEP 17: INSTALLING WEBVIEW
Once Everything is done you will notice that some apps dependent on AndroidSystemWebview.apk will crash or not display properly. An example of this is the popular 'English' dictionary that can be downloaded from the play store. Instead of proprietary Webview we will now install open source webview.
IN MAGISK (Needs Internet)
1. Install Bromite Systemless Webview module(module itself needs internet and takes some time)
2. Install Xposed Framework [ UPDATE: THIS MODULE IS BROKEN AS OF NOW, DOWNLOAD XPOSED APK FROM ELSEWHERE]
IN XPOSED FRAMEWORK
1.INSTALL AnyWebView module
REBOOT
GO TO SYSTEM>Developer options
Under webview implementation option select Bromite Webview
STEP 17: AFTER REMOVING ALL APPS THAT YOU DON'T WANT, TAKE A BACKUP OF THIS BLOATWARE FREE SYSTEM IN TWRP AGAIN.
THAT WAY YOU DON'T HAVE TO GO THROUGH THESE SAME STEPS AGAIN IF YOU NEED TO FACTORY RESET YOUR DEVICE AGAIN
STEP 18: A LIST OF SAFE TO REMOVE APPS IN THE LG V30 OREO ROM
By now I am too tired to type all the apps so I just took a screenshot of all the apps I now have after installing nanoDroid and Bromite.
So you can safely remove all other apps that ARE NOT in these screenshots.
SCREENSHOTS IN ATTACHED ZIP.
Launcher: Nova Launcher
Icon Pack : Pixel Pie Icon Pack
Any Queries WELCOME.
Suggestions on other removable apps from the list HIGHLY WELCOME.

Been looking for a thread like this. Awesome!
Just a quick Q or two...
1. I might just use the zip and remove webview manually. Would that be okay? And should i uninstall libs too (g-killer has that option)?
2. I see you used nano microg - would it be fine to use the full nanodroid installer? There are some apps there that are handy afterr you have de-googled.
Again, thanks for the thread. Been trying to go microg on stock for a while now withoutuch luck (full of fc's).
Will try this asap.

cascabel said:
1. I might just use the zip and remove webview manually. Would that be okay? And should i uninstall libs too (g-killer has that option)?
2. I see you used nano microg - would it be fine to use the full nanodroid installer? There are some apps there that are handy afterr you have de-googled.
Again, thanks for the thread. Been trying to go microg on stock for a while now withoutuch luck (full of fc's).
Will try this asap.
Click to expand...
Click to collapse
Which zip are you referring to in the first point? If you mean bromite zip and if it is available, I think it would be okay to flash it. You (might) see two webviews in developer settings. I really have no idea regarding libs, I really don't have much idea of core android system but afaik the zip file from PART 2 under
There is this zip file specially made for removing gapps: ' https://github.com/CHEF-KOCH/Remove-Gapps/releases ' but I didn't use that and it doesn't remove 'Android System Webview' so it's upto you to find a list of removeable apps from your system.
Click to expand...
Click to collapse
lists many libs if you extract it and find a file delete.sh in zip>system>system.sh (shell/sh is essentially a .text file). You can try deleting those.
I might even try that zip file and see if it works or you can and update us, remember backing your system! after a fresh install.
I used the full nanoDroid package before and it came with a plethora of apps that scared me. You can download each of those apps from f-droid one by one if you just want a specific app. thanks for asking. good day!

B
tamakooo said:
Which zip are you referring to in the first point? If you mean bromite zip and if it is available, I think it would be okay to flash it. You (might) see two webviews in developer settings. I really have no idea regarding libs, I really don't have much idea of core android system but afaik the zip file from PART 2 under
lists many libs if you extract it and find a file delete.sh in zip>system>system.sh (shell/sh is essentially a .text file). You can try deleting those.
I might even try that zip file and see if it works or you can and update us, remember backing your system! after a fresh install. I think that's he zip you mentioned in your post. Not sure, though (at work and don't have time to check).
I used the full nanoDroid package before and it came with a plethora of apps that scared me. You can download each of those apps from f-droid one by one if you just want a specific app. thanks for asking. good day!
Click to expand...
Click to collapse
Oh. Sorry. My post was unclear.
I meant using g-killer to remove system apps instead of doing it manually (i don't have the time nor patience lol). I was wondering if i should delete libs using g-killer or just let them be and just remove apps. I think that's the gapps remover you linked (not sure. At work and don't have muh time besides checking here every once in a while )
About nanodroid, yeah it dies have a lot of apps. I do use the setup zip so i select which i use. Downloading on f-droid works, too.
Sorry for the questions. I'll try this tonight (maybe in 5-6 hours) and let you know what happens. :good:

Attempt 1: using the gapps uninstaller on you link gave me a bootloop. Gonna try gapps killer this tike without removing any libs.
Attempt 2: gapps killer without deleteing libs gives bootloop, too. Lol. Gonna try again but won't uninstall framework.
Attempt 3: same thing. Will try without deleting ps, play services, and framework.
Attempt 4: ok. So that worked. Still have PS and the others, though. Gonna try patching now and see if the last remnants of Google will disappear.
Ok. So i got it to work without having to clean flash. Gonna try a clean flash now and repeat. Not sure if i got all google apps deleted. Gonna try the zip again (gapps remover). If it works, I'll restore my old twrp backup and do it there. If not, I'll restore my backup and try again tomorrow. Patching takes a while...
Seems using g-apps killer zip or the gapps uninstaller zip you provided causes bootloops.
I'll try again tomorrow...

cascabel said:
Attempt 1: using the gapps uninstaller on you link gave me a bootloop. Gonna try gapps killer this tike without removing any libs.
Attempt 2: gapps killer without deleteing libs gives bootloop, too. Lol. Gonna try again but won't uninstall framework.
Attempt 3: same thing. Will try without deleting ps, play services, and framework.
Attempt 4: ok. So that worked. Still have PS and the others, though. Gonna try patching now and see if the last remnants of Google will disappear.
Ok. So i got it to work without having to clean flash. Gonna try a clean flash now and repeat. Not sure if i got all google apps deleted. Gonna try the zip again (gapps remover). If it works, I'll restore my old twrp backup and do it there. If not, I'll restore my backup and try again tomorrow. Patching takes a while...
Seems using g-apps killer zip or the gapps uninstaller zip you provided causes bootloops.
I'll try again tomorrow...
Click to expand...
Click to collapse
thanks for checking, I updated the post. Also had some other minor updates in the post.

Hey OP, thanks for writing this guide. I'm running Android 12 stock ROM + Magisk root on Zenfone 9 but I've had trouble deleting stuff in /system due to it being read-only. I am able to "freeze" goolag apps in Titanium Backup but can't seem to uninstall them with either TB or in TWRP recovery mode file browser. Seems that everything system related is mounted as read-only. Do you have any ideas on how to proceed with de-googling in such conditions? Regards

[GUIDE][AOSP][A10] Phh treble Q GSI non-root with Safetynet as a daily driver

This post is for specific ROM focusing on encrypted un-rooted setup https://github.com/phhusson/treble_experimentations/releases v217+
Usual lecture from your local system administrator: your warranty will be void, all you do is your own risk
Known issues:
- bluetooth in-call echo (patch needs to be applied)
- AVC mediacodec on Pie vendor issue (patch needs to be applied)
- VoLTE not tested, other things please report in this thread if discovered
Prerequisites:
- unlocked bootloader
- global stock Pie/Q rom already flashed (may also work for In/Cn variants - needs to be tested)
- A/B PHH GSI with Gapps unpacked (system-quack-arm64-ab-gapps.img is inside downloadable system-quack-arm64-ab-gapps.img.xz)
- stock fastboot rom unpacked (we need vbmeta.img)
- data and localstorage should be backed up, the process requires factory reset
Fastboot flash method:
- `fastboot flash system system-quack-arm64-ab-gapps.img`
- `fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img`
- reboot to system, do not put effort into setup, just get to settings
- if you do not have/not willing to flash twrp, patches need to be applied at this point with some root file explorer (see below)
- apply settings->phh->securize, the device should reboot and be stuck on android logo
- press and hold vol-up + power buttons, get to recovery
- for TWRP, format data partition (not just wipe, but format is needed, like mke2fs via adb/terminal); for stock recovery - wipe data
- reboot to system and setup
To apply patches via TWRP, just flash one of attached zips (Pie/Quack)
To apply patches without twrp, replace files in vendor filesystem with ones in vendor folder of the patch archive
To dirty flash new version, see post #2

Updating to new version without encryption issues
Prerequisite: TWRP
1. Flash new system image, like system-quack-arm64-ab-gapps.img, do not reboot
2. Mount system read-write
3. In terminal (adb) execute:
Code:
touch /system_root/system/phh/secure
rm /system_root/system/xbin/su
rm /system_root/system/bin/phh-su
rm /system_root/system/etc/init/su.rc
rm /system_root/system/bin/phh-securize.sh
rm -Rf /system_root/system/app/me.phh.superuser/
rm -Rf /data/su || true
Note: /system_root path prefix is for LR TWRP, if your recovery puts system to different folder when mounted, then adjust accordingly
Reboot. Done.

On v216 with EEA rom, deep sleep and AVC seem to be working for me without any patches. Also, if AVC doesn't work on a rom, the rest of the codecs might not work either - I've noticed this on LOS with VP9.
Can't test if VoLTE works, as I've dirty flashed it and phone services sqlite db is newer than this rom supports (and if I plug in a SIM, the phone services just crash).
I've used phh for the past week and I concur that it is stable enough for a daily driver.

Do you have root?
To resurrect telephony provider after installing older one (like aosp over los) I usually clean provider data in data/data and/or /data/user_de/0

Hello may I know how to fix the status bar to make it away from the rounded area? Thank you.

Developer options - display cutout - hide

btvbtv said:
Do you have root?
To resurrect telephony provider after installing older one (like aosp over los) I usually clean provider data in data/data and/or /data/user_de/0
Click to expand...
Click to collapse
Wait, do you know where the precise location of the sqlite db? The package name didn't show up in data and cleaning storage+cache within settings didn't seem to work (probably since it was a persistent service).
Otherwise, I'll probably clean flash phh sometime later anyway (I'm using the camera for scanning my exam papers these weeks, and I don't feel like setting up my accounts again so soon).

Hi i tried both phh asop v216 and Havoc-3.5 gsi based on v216 with lastest android 9 vendor.
On Asop RIL works well but not on Havoc i don't know why as they have same basis.

Got a couple of questions in PM lately.
I believe the forum is just for that - to ask the community.
If I do not answer each and every question - that's probably due to that fact that I do not know all the answers.
Still, the question in the thread has a chance of being answered by someone else, as opposed to pm.

Can someone please test and confirm if VOLTE works and is this daily driver capable? Thanks

I would argue that in my country no carrier has volte even with lte. Would be awesome to have a volunteer to test.

Updated to new version securized - all good
https://forum.xda-developers.com/showpost.php?p=82631277&postcount=2

seems to run pretty smooth.
I just realized that the security patch is dated on 1st december 2019 whilst v216 was may 2020.
Is there a possibility to use gestures like in PixelExperience while being securized?

Securize fakes security patch date from vendor. BTW, new a10 vendor has May security patch.
No idea for native gestures. Many apps for that in market. Accessibility service they use might add a small lag though.

Easily best AOSP rom on the phone

[ROM][All Quark][Android 11] LineageOS 18.1

ROM dedicated for All Quark (Moto MAXX/Turbo and Droid Turbo - XT1225, XT1250 and XT1254)
This ROM is the LineageOS from https://lineageos.org/ with specific changes to improve the experience for Quark that is why the ROM has the MOD type, all modification are in the changelog
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Gapps:
Open Gapps
Choose Platform: ARM, Android: 11.0, and a Variant the one that have all you need, I recommend the Nano pack, but it may not have all you need so check before download, if any problem with a diferent version try the Nano before reporting issues.
TWRP For Quark:
TWRP Use laste Mod version from xda
Installation:
Make sure you are running latest MOD TWRP from xda TWRP thread
Download the latest ROM and GApps**.
Reboot to recovery (recommended make a backup)
Coming from different ROM? Then Always wipe Data (without media aka without internal memory)
Wipe System*
Flash the latest build and GApps **
Reboot and enjoy!
* Wipe of Dalvik Cache and Cache not demanding but may help with some random minor bug that show after a update
** Gapps not demanding the ROM works perfect without it but if you plan to use gapps you need to flash it on a clean install with the ROM, In a ROM updates a "dirty flash" if you already have gapps always flash gapps again with the ROM update
Changelogs:
LineageOS - 18.1 source and Quark Changelog (Click Here)
What's working :
Everything minus VoLTE support for XT1254 (1225 doesn't have this featuring).
Known Android 11 issues :
Not PRE-ROOTED, ROOT solution is available read this thread second post
Old issue maybe resolved on latest TWPR update but... TWRP may not be able to backup or decrypt data encrypted on Oreo or Up: no know workaround, one day TWRP will support it.
General bug help/fix in second post or some were in the thread, use XDA building "Search Thread" option to find general help for this thread project...
Source:
LineageOS Source
Device Tree
Kernel tree
Vendor tree
Mod Kernel Adiutor tree
XDA:DevDB Information
[ROM][All Quark][Android 11] LineageOS 18.1 for Quark
Contributors
Felipe Leon (fgl27) is the main contributor (as I'm the one making it).
But the XDA community, quark user base plus the open source community from XDA, github and the LineageOS team is what make this project so good, thank you all :good:.
ROM OS Version: 10.x
ROM Kernel: Linux 3.10.x
Based On: LineageOS 18.x
Version Information
Status: Stable
Created 2021-30-05
Last Updated Check Changelog click here

Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Random Power off or reboots?
To identify if the device random reboot or simply power it self off there is two ways.
1) If after the device goes black you can't power it up again without plunging the charger, then is because the battery is dead, even if yours battery had good % left before it shutdown yours battery is probably damage doesn't matter if the device/battery is new a battery can go bad simply by charging the device wrong, a wrong way to do it is let the device constantly go bellow 20% as low you let it get worse yours battery will be with time.
2) Check the boot reason prop "ro.boot.bootreason" :
Using the app BHB27 Kernel Audiutor > logs section > search in a log > mark getprop > search keyword "reason".
If the result is power_key_press the device didn't reboot it power off.
Code:
[ro.boot.bootreason]: [power_key_press]
On this case, is recommended to set the battery "Automatic power saver" from default 15% to a higher value then the one yours device is power it self off.
-----------------------------
If the result is reboot the device reboot it self
Code:
[ro.boot.bootreason]: [reboot]
On this case, is recommended to just share a log, do as is recommended on next post.
Bootloop to TWRP after a Factory Reset (Settings/System/Reset option/Factory reset):
This is a Nougat and up problem, it only happens if you are using a TWRP from the official site (with is not update to properly support Nougat and Up Android versions) or a old version of TWRP, to fix it just flash latest MOD TWRP version from the TWRP xda.
TWRP xda thread Click Here
Pictures access, view, sharing or related:
One thing that I notice regarding permission is if you have a app that access a folder that was created in older OS this app may be able to access this folder but not fully access the files like the below example.
You take a picture or a screenshot and can't see or share it with some apps, the simple fix is just erased/delete the folder with that problem for example the DCIM (camera folder) and or Pictures (Screenshot) folder under Main storage (or any folder were you face a picture or file access related problem), of course you can backup the files to another folders first using a file explorer that can see the files (maybe necessary one with ROOT access), then let the OS service recreate the folder, it will automatic recreates after you take a new picture or screenshot (or manually make the new folder if is a custom folder mane by you), test to see if the problematic app can see after.
USB OTG player:
On latest android version Nougat and above, to play anything from a USB OTG device is needed proper permission, that is not simple to give as the app must request it to be given, so to play anything from a USB driver find a app like this one
VVM XT1254 only
VVM app (VVM may only be accessible via play with the link, click here and chose open with play), VVM may not work correctly google has it on version is free and seems to work 100% Google voice, the in the phone app of b this ROM also has a dedicated option for voice calls

Bug report are welcome, make with in the most accurate description possible, do not spare words, screens and logs, a bug that I can't understand or reproduced I can't fix.
Always post a bug with @fgl27 and a log .zip generated by the app
BHB27 Kernel Adiutor > Logs > One click all Logs to a ZIP (ROOT is needed for this)...
Even after a random reboot share a log
If is a Reboot/Power off related bug make the log as soon the device finishes boot up

Everything was working great, until this weekend. I was in an old hotel that gets terrible signal, so i used WIFI the whole time. When i left to head in to work this morning, i noticed that my data never came back. I can make calls, send texts, get on WIFI, use bluetooth... but the 4g LTE icon is not on my top bar, and im getting "No internet connection" errors. --- I verified that Data is turned on, i have something along the lines of "LTE/CDMA/EvDo" selected, ive restarted the phone, and ive tried popping out my SIM card and reinstalling it. -- Any suggestions?

imcensored1 said:
Everything was working great, until this weekend. I was in an old hotel that gets terrible signal, so i used WIFI the whole time. When i left to head in to work this morning, i noticed that my data never came back. I can make calls, send texts, get on WIFI, use bluetooth... but the 4g LTE icon is not on my top bar, and im getting "No internet connection" errors. --- I verified that Data is turned on, i have something along the lines of "LTE/CDMA/EvDo" selected, ive restarted the phone, and ive tried popping out my SIM card and reinstalling it. -- Any suggestions?
Click to expand...
Click to collapse
I figured it out. I started playing with all the network settings, and i found one that allowed me to set the "access point". I found the access point somehow was set to "Xfinity", once i changed it to "Verizon" my data came back. I am not sure how it changed or why it changed, as it was working before I entered the no coverage zone.

I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 18.1 source and Quark Changelog

I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 18.1 source and Quark Changelog

fgl27 said:
Below are some of the helps and or workarounds for the most occurring issues.
ROOT Use Magiks
GPS / Radio:
Changing/Updating the ROM may cause GPS lock problem, there is two separated help
option 1) Install "GPS Status & Toolbox" , open the app, slide the left option and open "Manage A-GPS state" click in Reset, after repete the process and now click in Download, close the app after receive the OK, wait a few seconds and try a gps lock using the same app, if that doesn't help try again after a reboot, if that doesn't help go to option 2 below
option 2) If the above doesn't help you can try to erase all the radio status
Erase the radio status also applies to the case you have No SIM Card or no Cell Signal level in status bar.
To erase the radio status is very simple just flash this zip "Clean_modem_status.zip" via TWRP no wipe is need, is also recommended to try option 1 after this if you flashed because of a GPS problem.
If after flashing the cleaner you find any problem related to lost of signal, re-try the flash of "Clean_modem_status.zip", if the problem persist, flash latest radio.img version via fastboot (aka "via bootloader")
Code:
mfastboot flash radio radio.img
find the radio.img inside the stock ROM xml.zip, some xml.zip and fastboot for windows can be found here (click here)
Click to expand...
Click to collapse
I tried these fixes for the GPS a few times but no luck. Do you have any other ideas?
Thank you.

It's been awhile since I've had to deal with this issue. I forget exactly what I went through to get it resolved. Have you tried an absolute cold raw reinstall? Wipe everything in the phone except internal memory, from TWRP.

SecretPotatoChip said:
I tried these fixes for the GPS a few times but no luck. Do you have any other ideas?
Thank you.
Click to expand...
Click to collapse
Sorry I was busy didn't check xda for a while.
If those don't help the best option is to try Einsteindks from above post
On Android was added a update to the GPS libs that fixed most of the issue, that is way most don't have any issue anymore, but if you have one is probably something very odd that need a full clean to resolve.

Active display is not working. How do I turn it on?

DobrRk said:
Active display is not working. How do I turn it on?
Click to expand...
Click to collapse
Active display is a Motorola name.
Use Ambient display, enable it on settings -> system -> actions

fgl27 said:
Active display is a Motorola name.
Use Ambient display, enable it on settings -> system -> actions
Click to expand...
Click to collapse
Thank you very much. It is a pity that it does not work as on the old motorola, with a separate processor under this option. I really liked the firmware.

Power Functions was an awesome option on Motorolas, at one point. Shame they didn't carry over. At least other options exist. Neat idea, though. Good to see the display stuff be standard, albeit under different names.

Verizon just sent me this text. (Advanced Calling /HD Voice). I feel like I enabled this years ago. I went to search to turn it on and I see it's not an option. Is this something that was coded out of Lineage?
I know you have to activate it on your phone and then Verizon has to activate it on their end.

imcensored1 said:
Verizon just sent me this text. (Advanced Calling /HD Voice). I feel like I enabled this years ago. I went to search to turn it on and I see it's not an option. Is this something that was coded out of Lineage?
I know you have to activate it on your phone and then Verizon has to activate it on their end.
Click to expand...
Click to collapse
I believed HD voice needs VoLTE something that doesn't work in custom ROM

opengapps release they version for Android 11, I updated OP with the link.
Sometimes after not using my device from a few hours it became very slow the first few minutes I try to use it, some apps freeze giving me that warning "app is freeze kill it" or something like that, I notice that a lot of service don't run as they did on old version of android regularly on background, but they sometimes run all together when you wake the device up.
Most are service from google apps and frameworks, to improve this I'm using this new battery option that show on each app info, that allows you to enable "Background restriction" see attached.
You have to manually set to restrict each individually app that you wanna to be restricted, after I did to almost all available apps, notifications are working as expected and I don't have slows down at least not from service on the background.
If anyone has some issue related try to use those options to improve.

I push a update.
Download:
ROM:
Main:
Main google Drive link
Secondary:
sourceforge (This is the server used by the Updates app in Setting>System>Updater)
Changelogs:
LineageOS - 18.1 source and Quark Changelog

Einsteindks said:
It's been awhile since I've had to deal with this issue. I forget exactly what I went through to get it resolved. Have you tried an absolute cold raw reinstall? Wipe everything in the phone except internal memory, from TWRP.
Click to expand...
Click to collapse
I went into TWRP, and wiped everything except internal storage and usb otg. My gps still does not work.

SecretPotatoChip said:
I went into TWRP, and wiped everything except internal storage and usb otg. My gps still does not work.
Click to expand...
Click to collapse
Next step would be to save internal on an OTG, along with ROM & Gapps, Titanium Backup, etc, eject/remove OTG. Get into TWRP, wipe ALL, plug in OTG, reboot into TWRP, install ROM, Gapps & modem reset zips after selecting OTG as source. Double check yourself along the way, trust me! It's easy to forget a step and have to re copy files onto the OTG from computer backup.

[ROM][12.1][Official]crDroid Android[v8.14][March 2023 ASB]

NOTICE: crDroid 8.x (Android 12) is moving into maintenance-only release mode, and no new feature changes should be expected.
I'll be merging monthly Android Security Bulletins from upstream as they're available, and pushing releases, but they'll be blind builds going forward.
Please consider updating to crDroid 9.x (Android 13):
crDroid 9.x XDA thread - OP 6/6T
{
"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"
}
*** Disclaimer ***​I am not responsible for any damage you cause to your device.
I hope you like reading.
You have been warned.
crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for your device, while also attempting to bring you many of the best features in existence today.
​Features:​General:​See our current feature list at our GitHub!
Device-specific:​
OnePlus Camera & Gallery fully working (using APKs directly from OOS 11.1.2.2 or apkmirror.com with verifiable signatures; currently shipping OnePlus Camera v3.14.40 and OnePlus Gallery v4.0.297); including 60fps video recording in 1080p & 4K, watermark, depth effect, smart content detection, actually-working HDR, et al.
DeviceExtras for OnePlus-feature-specific customizations including alert slider modes, DC dimming, High Brightness Mode including customizable Auto-HBM threshold, customizable rendered FPS overlay, digital earpiece/mic gain controls, built-in UI jitter test, turn off when not using because it conflicts with DASH charging), and 3-category vibration strength control (thanks to AnierinBliss for all his work on this implementation).
OnePlus-style color modes available through LiveDisplay (6 & 6T have slightly different implementations and you may not notice a difference, but think of "Natural" and "Wide Gamut" like uncalibrated versions of "sRGB" and "DCI-P3").
Ongoing kernel tuning (trying to get the best of both worlds tuning existing QTI perfd & scheduler & lmk, rather than cutting over to Google libperfmgr/powerhints/userspace lmk, definite improvements over vanilla LOS, mostly importing/adapting work by EdwinMoq and mcdachpappe).
Everything you never wanted to know about slots & A/B devices (but have been forced to find out):​
Spoiler: Show/Hide
"Clean flash": Removing device protection & clearing user settings before installing a bootable system install zip by formatting data.
"Dirty flash": Flashing a ROM zip (usually upgrading to new version, sometimes just re-flashing the existing one) without wiping data or anything first.
"Wipe data": This used to be synonymous with "factory reset" in TWRP, without formatting the data partition and losing the contents of internal storage. Now, with TWRP being deprecated and using built-in LineageOS-based recovery, "wipe data" and "factory reset" mean the same thing as "format data" (which means, everything in internal storage gets erased).
"Format data": Formats the data partition itself, resets all file-based encryption keys, loses all contents of internal storage, and in fact deletes all "user 0" directories (this has some implications for internal storage before & after first boot).
"User 0" directories are a series of directories that store userdata for the primary user, "Owner", and get created in various places throughout the filesystem on first system boot if they don't exist already. Anything you copy to "internal storage" while booted in recovery after "formatting data" will actually be copied to /data/media/ instead of /data/media/0/, and will become invisible to regular file browsing after first boot once the system has created /data/media/0, since the system will prefer to use that path for internal storage from then on (so you'll need a root file browser to delete things from /data/media, or just ADB sideload things instead of copying after formatting but before booting).
"OTA package": Originally an abbreviation for "over the air", referring to how a software update could be delivered (as opposed to having to take your phone to a carrier's store for a firmware update via serial/USB connection). The common usage in Android circles is any installation zip file that actually includes a bootable system. Is always installed to the currently "inactive slot", and will trigger a slot switch upon the next reboot.
Some partitions are duplicated (system, vendor, boot, and a couple others, but not data) and have a "slot A" & "slot B" copy.
"Slot A" and "slot B" are absolute designations, but most installer zip scripts use the relative designations: "active" and "inactive". Whichever slot you're booted from currently is "active", and the other one is "inactive".
Installing a zip file that's flagged as being an OTA package will 1) install the contents to the "inactive" slot, and then 2) flag the bootloader to switch which slot is considered "active" and "inactive" upon next reboot; causing it to attempt to boot from the formerly-inactive slot's boot partition.
The OxygenOS full OTA zip files and all custom ROM installer zip files are considered "OTA packages" and will trigger a slot switch on next boot after installation.
You can install multiple OTA zip packages one after the other without rebooting in both the stock recovery and TWRP; they will all get installed into the correct partitions in the "inactive" slot, one on top of the other, and then it will swap active & inactive upon reboot.
We don't use what are called "delta" updates, which can patch existing partitions by block or by file; we use full filesystem images. So for us, OTA zip packages are really just a bunch of partition filesystem image files all wrapped up into a "payload.bin" with some extra instructions & metadata/checksums, so when you flash a ROM, it overwrites entire partitions at a time instead of individual files or filesystem blocks within that partition. So if you've changed something in a partition like system that gets written as part of flashing an OTA zip, all your changes are gone. The only thing in the system partition afterward will be what was in the system.img that was included in the ROM zip payload.
The partitions that crDroid, LineageOS, and most custom ROMs for OnePlus 6 & 6T install to when flashing are boot (contains recovery & kernel), dtbo, system, vbmeta, and now vendor as of Android 12. If you are planning on going back to an Android 11 ROM that does not build the vendor partition from source (so everything except SyberiaOS, essentially), you'll need to flash the OOS stock vendor partition to both slots from fastboot before installing the OTA zip.
"Prebuilt vendor" vs. "source-built" vendor partitions: when first trying to get a custom ROM working on a new device now that we have separate system & vendor partitions & Google's "Project Treble" is a thing, you'll often just leave the contents of the vendor partition alone, because that's where all the proprietary or device-specific stuff lives (manufacturer specific hardware drivers & interfaces, any DRM libraries, custom frameworks & selinux policies for talking to them), and you make a compatibility map of what framework versions you're compiling against in system and what vendor version they're compatible with or supersede or you overlay updated things that should replace stuff in the vendor partition and keep it in system_ext instead. But you're also limited in that if there are some things in vendor, you CAN'T work around it from the ROM side (like, OnePlus Camera working correctly). So often, once the basics are functioning, the goal is to move to building the contents of the vendor partition from source, because you then have the freedom to fix problems with sepolicy, library/framework mismatches, etc. and make things work with the custom ROM instead of only working with the OEM's flavor of Android, and you can still copy individual pre-compiled files from the stock vendor filesystem image if needed (like if there's no open-source equivalent for some driver). We finally got a source-built vendor bringup for OnePlus SDM845 (enchilada & fajita) as part of the Android 12 (lineage-19.1) bringup, so some things work better, and some things work worse, but at least it's possible to fix things and keep moving forward to newer Android versions. However, since we're still dependent upon at least SOME binary blobs copied over from OxygenOS 11.1.2.2, the vendor patch level will remain at the release date for the last release of OOS 11, because we can't know for sure that some component isn't vulnerable, no matter how new all of the source-built components are.
"Updating firmware" simply means we're flashing updated contents from the manufacturer into all the OTHER partitions besides the ones that the ROM OTA zip touches. There are another dozen or more of those, besides system & boot, that the full OxygenOS OTA zip would normally write to when you install it. The contents of the system & vendor partitions in custom ROMs for our device are generally built against a particular version of OxygenOS; in this case OOS 11.1.2.2 was the final release by OnePlus before they announced the end of support & updates for the OnePlus 6 series. Some people are still on older firmware that is now dramatically different than what the current custom ROM was intended to deal with (that is, all the stuff from OxygenOS is still based on Android 10, while the ROM is expecting compatibility with Android 11), and while I tend to agree that OxygenOS 10 was better than 11, that doesn't matter when you're talking about installing this custom ROM over it. So please; update to OOS 11.1.2.2 firmware (see instructions below).
Notes on stock recovery & TWRP:​
Spoiler: Show/Hide
TWRP is deprecated & unsupported, for purposes of bug reporting & getting help with crDroid. I liked it personally, and I agree with all the reasons for wanting to try and keep using it; but the source has been described as a hot mess, the official releases for enchilada & fajita have not had good compatibility with Android 12 or newer (trouble with decrypting file-based encryption for userdata), and there are too many variations & unofficial TWRP-based recoveries for me to keep track of.
Meanwhile, the stock crDroid recovery (based on LineageOS) intentionally cannot decrypt userdata, and doesn't correctly process addon.d OTA survival scripts on A/B devices; so after using it to flash any OTA zips, you'll need to reboot to recovery and manually flash things like Magisk or GApps installers. But for all those shortcomings, it has working fastbootd (aka "Userspace fastboot", which is what happens when you go to "Advanced", then choose "Enter fastboot") that lets you flash one image to both slots at once with a single command, and unlocks critical partitions... while the OnePlus OEM bootloader (where it says "Fastboot Mode" in a square, then goes to the big green "START" text over white & dark red terminal font type text) can't be used to flash every partition to update firmware. Personally, I still think of it as wannabe-class and not a "proper" custom recovery until the Lineage team 1) implements userdata decryption so you can manage files in /data and install updates from internal storage, 2) allows for a factory reset the way we've always all understood it ("wipe data") WITHOUT nuking the contents of internal storage for no good reason ("formatting data"), and 3) gets the updater to call backuptool correctly & process addon.d OTA survival scripts on A/B devices. But they're not going to, and since crDroid is LineageOS-based; it's what we've got, and fastbootd is the best way to update firmware.
The takeaway: If you want to try different custom recoveries (new builds of TWRP, OrangeFox, PBRP, whatever), feel free; and let us know how it works! But you're on you're own doing that; it's an unsupported configuration.
For purposes of doing updates, plan on doing your initial installation from bootloader & recovery then applying subsequent system OTA updates using the built-in Updater tool (Settings > System > Updater), both with new OTA releases and when choosing a file from "Local Installation". It executes OTA survival scripts correctly from /system/addon.d/ as well. I've personally tested and it correctly preserved Magisk canary for several versions, and MindTheGapps & NikGapps on my tester fajita and MinMicroG "system" install package on my daily driver enchilada.
The built-in recovery DOES support use of a USB thumb drive and will mount it in OTG mode, so any place in the instructions you see "adb sideload", you can instead copy all your things to a FAT32- or exFAT-formatted USB stick and then apply the update from there instead.
Flashing Instructions:​Pre-installation prerequisites:​
Spoiler: Show/Hide
Make sure your bootloader is unlocked (and don't plan on relocking it ffs).
Make sure you have a reasonably-current, working installation of android platform tools (adb & fastboot command line binaries & necessary drivers) on your computer, USB drivers, and a known-good USB cable (see links in post #2).
Make sure you've downloaded the most recent full OxygenOS OTA installer zip (11.1.2.2), crDroid zip, matching crDroid boot.img, and whatever Magisk/GApps/microG installation packages you want to use to your computer (see links in post #2).
Make sure you've backed up whatever data you want to keep to somewhere that's not on your phone; for a new install, we're going to format the data partition and you're going to lose everything from internal storage.
If you don't KNOW you already have OOS 11.1.2.2 flashed to BOTH slots, follow the "Updating Firmware" instructions below. You may also want a utility like 7-zip in order to extract .tgz files under Windows.
Updating Firmware:​
Spoiler: Show/Hide
Reboot phone to bootloader (no USB cable connected until you've entered OEM bootloader).
If you're not already using the stock crDroid recovery, you'll need to 'fastboot flash boot path/to/boot.img' on the computer, substituting in the path & filename for the current crDroid boot.img that you downloaded as part of the prerequisites listed above.
Reboot to bootloader again (actually loads new bootloader contents that you just flashed).
Use Vol +/- buttons to select "Recovery mode" and press Pwr button to boot stock recovery.
Tap "Advanced", then tap "Enter fastboot" (the already-selected first option).
Follow the instructions for extracting the partition images from the official OxygenOS Updater full OTA zip you already downloaded using the "payload-dumper-go" utility, and flashing them one at a time, from https://wiki.lineageos.org/devices/enchilada/fw_update or https://wiki.lineageos.org/devices/fajita/fw_update, except for the very last command ('fastboot reboot').
If you're only updating firmware and were already on crDroid, you can just 'fastboot reboot' which will go back to booting the system normally. If this is part of coming to crDroid 9.x from another ROM, continue with the first-time installation instructions below.
First-time installation:​(when coming from any other ROM or stock OOS or crDroid 7.x or earlier)
Spoiler: Show/Hide
*Back up anything you want to keep from three phone's internal storage to your computer/cloud storage, because we're going to format the userdata partition in this process.*
Download boot.img & rom zip to computer.
Reboot phone to bootloader.
Flash boot image to both slots ('fastboot flash boot_a boot.img' then 'fastboot flash boot_b boot.img').
Reboot phone to bootloader.
Use vol +/- keys to select recovery mode & press power button to enter recovery.
On phone, choose "Apply update" > "ADB sideload" & then from computer, 'adb sideload path/to/rom.zip' (substituting the actual path to the actual filename) to sideload the installation zip; the orange recovery header graphic will disappear until the process has completed ("error" messages like "no error", or finishing at 47% on the computer are normal).
On phone, choose "Factory reset / Wipe data", and confirm (note: this will erase everything from the phone's internal storage; make sure that you have backed up anything you want to keep first!).
On phone, choose "Advanced" > "Reboot recovery" to reboot into recovery on the newly-flashed slot.
Use adb sideload to flash any magisk or GApps or microG installer zips (some installers might require you to choose "Advanced" > "Mount/unmount system" first).
Reboot into system.
???
Profit!
Update installation:​
Spoiler: Show/Hide
Use the built-in Updater ("Settings > System > Updater") to apply OTA updates as they become available, or to manually flash a ROM zip by going to the three-dot menu in the upper right and choosing "Local update". Seriously, that's it; it processes addon.d survival scripts correctly, including Magisk, MindTheGapps, NikGapps, MinMicroG, and presumably others.
If you must flash from recovery, then be aware that the stock crDroid recovery does NOT process addon.d OTA survival scripts correctly on our A/B system-as-root device, so you'll need to do the following:
Reboot phone to recovery.
Choose "Apply update > Apply from ADB" on the phone, and 'adb sideload path/to/installation.zip' from a terminal on the computer (or use a USB drive with appropraite files copied to it and choose OTG as the update source instead).
After installation has completed and the menus have reappeared on the phone, go back, then choose "Advanced > Reboot to recovery" on the phone.
Choose "Apply update > Apply from ADB" on the phone, and 'adb sideload path/to/installation.zip' for each addon like Magisk or GApps installation zip you need in order to match what was initially installed on the phone.
Reboot system.
Please see post #2 for current boot.img files, information about Google apps & microG, release notes, installation notes, known issues, and lots of helpful links.
Please see post #3 for information about bug reporting & troubleshooting.
Sources:​ROM:​https://github.com/crdroidandroid
Device trees:​https://github.com/crdroidandroid/android_device_oneplus_enchilada
https://github.com/crdroidandroid/android_device_oneplus_fajita
https://github.com/crdroidandroid/android_device_oneplus_sdm845-common
https://github.com/crdroidandroid/android_hardware_oneplus/tree/12.1-op6
Kernel:​https://github.com/crdroidandroid/android_kernel_oneplus_sdm845
Vendor-specific:​https://gitlab.com/crdroidandroid/proprietary_vendor_oneplus_enchilada
https://gitlab.com/crdroidandroid/proprietary_vendor_oneplus_fajita
https://gitlab.com/crdroidandroid/proprietary_vendor_oneplus_sdm845-common
https://gitlab.com/crdroidandroid/android_vendor_oneplus_apps
https://github.com/Terminator-J/vendor_ih8sn
Download:​ROM:​https://crdroid.net/enchilada/8
https://crdroid.net/fajita/8
Changelog:​https://crdroid.net/enchilada/8#changelog
https://crdroid.net/fajita/8#changelog
Links:​Visit the official website at crDroid.net
crDroid OnePlus 6/6T Telegram Group
crDroid Community Telegram Group
crDroid Updates Telegram Channel
Donate to help our team pay server costs (PayPal or Patreon)
Donate to support me in maintaining this device (PayPal or Patreon)

General Notes:​
Maintainer is only actively working on crDroid 9.x (Android 13) primarily and running that as daily driver. We'll be relying on community members in the Telegram group to verify any regressions/new issues in Android 12.1 builds, but will continue to release as new monthly security patches are merged in crDroid sources.
Yes this ROM supports package signature spoofing permission for microG compatibility out of the box (but will work without ANY GApps/microG implementation installed as well).
Requires OOS 11.1.2.2 firmware (last official release). You should consider using an Android 10 ROM if you want to continue using Android 10 firmware.
Tested against latest Magisk canary, works well.
No there won't be official builds with inline GApps; please don't ask. The dev team's policy is vanilla-only whenever possible (and it's very possible with our devices).
​Google Apps:​Maintainer doesn't often use Google Apps personally as daily driver, but here are some notes gathered from peoples' testing:
TL;DR: Use MindTheGapps.
Otherwise, in general, try to go with the lightest weight package you can and don't replace the stock dialer/messaging apps (just download them from Play Store and set defaults).
Since we are LineageOS-based, here are the Lineage team's recommendations & reasoning:
https://wiki.lineageos.org/gapps.html
MindTheGapps are recommended and considered the default supported configuration for either Android 11 or 12 (per the LineageOS wiki, linked above). Assistant works great out of the box.
Note on Google Keyboard: If installed as a system app, GBoard will actually do on-device speech recognition when it doesn't have a network connection, so you might want to try adding the Nik Addon for Gboard on top of MTG, just to get on-device speech recognition as an input method (someone please test this out & report back?), but not required for regular usage and GBoard works perfectly well installed from the Play Store as a user app after first boot as well.
MindTheGapps survives built-in System Updater OTA updates, works fine after doing manual update with built-in recovery, and passes SafetyNet.
http://downloads.codefi.re/jdcteam/javelinanddart/gapps
NikGapps also seems to work in Android 12.1, although it has had some issues with clobbering overlays leading to system apps triggering the privacy indicators that shouldn't be doing that. Recommend using Core plus addons, rather than going heavier from the beginning (we don't have much space left in the system partition).
You'll need Googlesearch (the actual "Google" app) and Velvet (Assistant pacakges), plus GBoard (gets offline speech recognition if installed to system) and either SetupWizard or PixelSetupWizard for the best voice-recognition & assistant experience.
Not the recommended GApps package, but give it a shot if you like the customization options. Survives built-in System Updater OTA updates, might have issues with re-flashing during manual updates from built-in recovery (needs testing by some brave soul), passes SafetyNet afaik.
https://nikgapps.com/downloads#downloads
Flame Gapps also seems to work well in Android 11 (haven't heard reports about Android 12.1 yet), although the "basic" package is a little heavier than Nik Core, at least it doesn't start replacing stock dialer & messages. Also survives OTA & passes SafetyNet, not sure about manual updates with built-in recovery.
https://flamegapps.github.io/download.html
OpenGApps are not recommended, for reasons outlined in the LineageOS wiki link above.
BitGApps ... exist. No idea how that's going.
Please report what worked for you, whether or not it survives updates when using the System Updater, whether or not it survives manual "dirty" update flashing via built-in recovery, and whether it passed SafetyNet, so I can keep this list updated.
crDroid 8.14 - March 2023 ASB release notes/changelog: ​Changelog since v8.13 hotfix 1 release:
Merged February and March 2023 Android Security Bulletins & any changes from upstream LineageOS device/kernel/vendor trees (lineage-19.1 branch).
Whatever the ROM dev teams changed upstream in LineageOS and crDroid sources (not much? they're busy with Android 13).
Other misc fixes ... probably.
Installation notes:​
In case of bootloop (boot animation stuck for longer than about 2 minutes and never gets to lock screen), reboot to recovery and manually flash the ROM zip either via ADB sideload from computer, or from a FAT32-formatted USB thumb drive via OTG, then reboot to recovery again, and re-flash your same Google Apps/microG/Magisk/whatever install zips (again via ADB sideload or USB OTG), and reboot system. This *should* take care of any lingering errors with old things getting stuck in your /system/addon.d/ directory that might be trying to preserve old privileged system apps without privileged permissions (which is what causes those boot loops in the first place).
The built-in OTA updater in Settings > System > Updater goes a lot faster if you go into Updater preferences and toggle on "prioritize updater process", and make sure the screen stays on by using the Caffeine QS tile, or "never sleep while charging" toggle in Developer Options, or changing your Display timeout to 30 minutes.
If you experience issues with OnePlusCamera & OnePlusGallery after updating from an old version, first get App Info and clear storage & cache for both. You might have luck with "update" installing the same apk version in-place (it will ask if you want to update the app, even though it's the same version). I used OP Camera v3.14.40, which is available from here: https://www.apkmirror.com/apk/onepl.../oneplus-camera-3-14-40-android-apk-download/ and OP Gallery v4.0.297, available from here: https://www.apkmirror.com/apk/onepl...eplus-gallery-4-0-297-2-android-apk-download/. Reports are that it usually works just fine updating from official 8.7, but here are some troubleshooting steps for just-in-case.
​Known issues:​
The usual LineageOS Android 12 things (mostly that big ugly blank spot at the top after reboot before unlocking).
(fajita-only) The "Pocket detection" toggle in crDroid Settings > Miscellaneous will interfere with "Screen off UDFPS" (crDroid Settings > Lock screen > UDFPS customization) and "Prevent accidental wakeup" (Display settings). If you use it, turn off the others, or you might run into the screen-won't-turn-on issue. Personally, I was just dealing with having to press the power button a few extra times, because disabling "Pocket detection" ended up with me almost calling emergency services several times a day.
Thankfully this seems to be fixed in crDroid 9 (Android 13), so I definitely recommend upgrading once that's released.
Maintainer is busy af in real life and takes forever to get releases out.
Helpful links:​
Download ROM: enchilada / fajita
Download current boot.img files: enchilada / fajita (also attached below)
Android platform tools (adb & fastboot)
OxygenOS 11.1.2.2 Full OTA: enchilada / fajita
Firmware update instructions (LineageOS Wiki): enchilada / fajita
MSMTool (oh now you're in trouble - use latest unless you have a good reason to intentionally downgrade): enchilada / fajita
Magisk (recommend latest canary version)

LOGS OR IT DIDN'T HAPPEN​How to make bug reports (and how not to):​i appreciate bug reports, but I also need details. If an app is crashing ("FCing", meaning "force closing") then at a bare minimum, copy the crash log URL and share that with your report.
That probably won't be enough, though, which is why there are two main logs that I'll ask for:
1. logcat​You can either use the built-in MatLog tool to acquire this, or get it via USB debugging and adb on the computer (which was in the prerequisites section of the XDA first post, so you installed platform-tools and have adb & fastboot on your PATH, riiiight? )
Using MatLog
MatLog is shipped built-in, and it works great. It's built for an older API though, so you'll need to manually grant it permission to access all files (it doesn't know enough to ask since it's a system app and assumes itself to be privileged). If you don't, then you can only use the "Sharing" interface to save logs, rather than saving them to internal storage.
To use, open the MatLog app, and go into settings and tick the box for "omit sensitive info" so that you don't end up sharing your IMEI or email addresses with the world. Probably still best if you PM me the logs instead of share to the group.
Ideally if it's a reproducible problem, reboot, open MatLog, do the thing that causes the buggy behavior, switch back to MatLog, tap on the menu and choose "Save Zip", then send me the resulting file (they're saved to /sdcard/matlog/saved_logs/). Otherwise, try to open it as soon after the issue as possible and Save Zip.
Using ADB (Android debug bridge)
Since we're currently building as "userdebug", you can always grab a logcat even without being rooted. I'm assuming you've got adb and fastboot installed & can run them from a terminal.
Enable Developer Options if you haven't already by going to "Settings" > "About Phone" > scroll down to the bottom and tap on the "Build number" field 7 times to enable, then back up to System and choose the new "Developer options" menu, and toggle on "Enable USB debugging".
Connect the phone to computer via USB, then on the computer open a terminal type adb devices to start the server & verify you can see the phone. At this point you might get a prompt on the phone asking if you want to trust the computer with some ID for debugging; tell it yes (probably always yes, in case you need to do troubleshooting later due to a boot loop). You should see your phone's serial number listed under the output of adb devices in the terminal window. If not, you probably need to install OnePlus USB drivers.
Run adb logcat from the terminal and get ready for a wall of text. Ctrl-C to stop the firehose after about 10 seconds. Save the output to a file. Note: this is the stupid way assuming you just opened a command window or built-in PowerHhell in Windows. Any linux shell or current version of PowerShell should instead be able to just run adb logcat > logcat.txt to dump the output directly to a text file in the current working directory without the wall of text; just give it about 10-15 seconds and Ctrl-C to stop the capture.
That's it! PM me the file, with any other details about what's happening and your setup (device, how you flashed, GApps, and so on).
2. dmesg​Requires root, probably USB debugging, platform-tools added to your PATH, and knowledge of what the below instructions mean
Open a root shell on the phone (via local terminal or adb shell via USB).
Run dmesg and save the output to a text file.
PM me the dmesg.txt file, along with a logcat capture as well, and a detailed description of what the problem is, what the behavior is you noticed, how to reproduce, details of your setup (which device, what GApps, what Magisk modules, any custom kernels, how you installed, and so on).
Protip: If you're not rooted, since this is a "userdebug" build, you can go into Settings > System > Developer options, turn on the toggle for "Rooted debugging", and then on your computer, do adb root to restart the adb server process. The next adb shell you run from the computer will get superuser privilege instead and you can run dmesg or do other things without having to root with Magisk.
If you are rooted, I highly recommend installing & using SysLog (by Tortel), available on the Play Store and on F-Droid; it's a GUI app that lets you easily capture both logcat & dmesg & can generate zip archives to send to your favorite maintainer, while allowing for scrubbing potentially sensitive data, and has some other advanced filtering options.
3. A detailed description of the actual problem & how to reproduce​Maintainer is not a mind-reader
Describe what the actual problematic behavior is, compared to what the expected behavior is. Don't just throw a logcat at me and expect me to figure out what you think was actually wrong. Explain how to reproduce the bug, and what you were doing at the time. Give me details about your configuration: are you actually on the most current version, did you clean install, did you use the recommended MindTheGapps package, are you rooted & if so what add ons/modules/root-required utilities are you using regularly, etc.
A picture is worth a thousand words. Moving pictures even moreso. If you can use screenshots, or better yet a screen recording, to show me how something is failing, that helps a TON.
Realize that a number of things are beyond my control. I'm not a software developer, I'm not on the ROM dev team, and some things might never get resolved. It's *still* better than OnePlus though, hey?
Feature requests are not bug reports. If you don't have a stack of tested commits that you can submit as a pull request for the dev team to merge, it's not likely to happen. But you can always ask politely!
Other Notes:​It's your device to use the way you want of course, but don't expect support for your bug reports if you:​
didn't update firmware in both slots.
didn't do a clean flash.
installed with TWRP/any other custom recovery (or, worse yet, installed that custom recovery after).
aren't using the built-in kernel.
are using extensive root-required modifications & Magisk modules like Project Themer, Xposed/Riru, Dolby Atmos, Viper4A, modified Adreno GPU drivers, etc.
immediately start flashing stuff like "finalize.zip" or migrate restore zips instead of following the actual instructions.
are running decrypted (ugh, just don't).
re-locked your bootloader for some reason... you're on a custom ROM; don't do that.
followed some other installation method different than the steps in the first post.
"Supported" status - Updating from crDroid 7.x:​To be considered a "supported configuration", I need for folks to do a clean installation when jumping from Android 11 to 12, rather than trying to migrate from crDroid 7.x (Android 11, prebuilt vendor partition) to 8.x (Android 12.1, source-built vendor partition). So do your backups accordingly, because internal storage on the phone is gonna get wiped.
It generally works to do a dirty upgrade from recovery, as long as you reboot to recovery & flash a newer version of the EXACT SAME GOOGLE APPS PACKAGE AS YOU HAD BEFORE, but there's going to be odd things broken and you're really better off doing a clean install for a new major Android version number change.
Connectivity issues:​If you are having problems with mobile data under Android 12, try some of the following (and please let us know if one/all actually fixed things for you):
Go into Settings > Network & internet, scroll down to "Adaptive Connectivity" and turn it off
Go into Settings > Network & internet > Calls & SMS, and make sure your primary SIM is actually selected for calls, messages, and mobile data, then back up one menu level, go into SIMs, select your SIM if needed, and make sure "Mobile data" is toggled on
Go into Settings > Network & internet > SIMs, select your SIM, and change the radio mode to one of the ones that *doesn't* start with "NR", like "LTE/TDSCDMA/CDMA/EvDO/GSM/WCDMA" (or the one without the CDMA/EvDO stuff if you know you're not on a CDMA carrier)
Go into Settings > Network & internet > SIMS, select your SIM, go into Access Point Names, and make sure you've got the correct APN selected
Go into Phone (whatever you have for the default dialer), keypad, type in *#*#4636#*#* to open the "Testing" activity, choose "Phone information", then in the three-dot menu in the upper-right, choose "Select Radio Band" and choose the correct region instead of leaving it on "Automatic"

thank you boss, thx for this hard work

crDroidAndroid-12.1-20220709-enchilada-v8.6.zip
is it Beta version..?

Yay we're finally official! Come 'n' get it kids!

syamkumar.tpl said:
crDroidAndroid-12.1-20220709-enchilada-v8.6.zip
is it Beta version..?
Click to expand...
Click to collapse
Nope, I just PR'd last night to go official and it was accepted.
crDroid 8.x has stricter requirements for device maintainers with Android 12 releases, so until now I've only been able to classify the 8.x builds I've been working on for the last several months as betas, and honestly I haven't had the time until now to set up all of the XDA pages, so they've just been linked in the Telegram chat group.

(also, please don't link to the sourceforge files directly -- having people go through the crdroid.net website and have ads displayed helps fund the ROM dev team's server costs. Unless you don't WANT the ROM to keep getting developed, of course...)

Terminator.J said:
If you're feeling super-adventurous, you *might* be able to update to the latest release of 7.x (I'm finally getting around to making official 7.19 builds now), then reboot to bootloader, flash the boot.img to current slot, reboot bootloader, start recovery, flash the 8.x ROM zip from recovery, reboot recovery AGAIN, flash an Android 12.1-compatible version of the same Google apps or microG package you were using, plus Magisk if you're using that, and boot into system... but... I have no idea how well that will work, or not.
I can't afford to consider that an officially-supported configuration, because I have no idea what will be broken or not; but I'm interested to know if it works for you.
Click to expand...
Click to collapse
Thank you for your work!
I just updated on my OnePlus 6 crDroid from version 7.19 to 8.6. For a quick check what I checked is working fine, all data is preserved.
Thanks!

tomasz-c said:
Thank you for your work!
I just updated on my OnePlus 6 crDroid from version 7.19 to 8.6. For a quick check what I checked is working fine, all data is preserved.
Thanks!
Click to expand...
Click to collapse
Oh holy crap, it worked?! That's... kind of amazing. I didn't expect it to work, ngl. Thanks for the report, and enjoy!
___
If you don't mind me asking; what GApps (if any) did you have before & which package did you flash as part of the update, what recovery or with built-in updater in Settings > System > Updater, etc etc.?

Terminator.J said:
Oh holy crap, it worked?! That's... kind of amazing. I didn't expect it to work, ngl. Thanks for the report, and enjoy!
Click to expand...
Click to collapse
Yes, it worked And could you explain why it surprised you? Looks like it was more risky than I thought but I made copies beforehand, of course.
All the apps I checked work without any problem. Contacts, SMS, call history, photos and other data on storage and data of other apps are preserved.
I didn't remove the encryption before the update and my pin (sign) works fine.
In the previous post I forgot to add an important piece of information: I don't use GApps so I didn't test it.
At first I uploaded boot.img to both slots (because I forgot that in the description for the update it said to upload to one) but I guess it doesn't matter. I uploaded crDroidAndroid-12.1-20220709-enchilada-v8.6.zip to slot B, rebooted it booted after a long while (probably updating something) Android 12.1, when I saw that it worked I rebooted to recovery and uploaded it to slot A as well.

Terminator.J said:
If you don't mind me asking; what GApps (if any) did you have before & which package did you flash as part of the update, what recovery or with built-in updater in Settings > System > Updater, etc etc.?
Click to expand...
Click to collapse
I only now saw the questions in the second part of your post.
Basically, I did it as you stated in the instructions: "First time installation:" only without the "Factory reset / Wipe data" step and without installing GApps, because I don't use them.
To begin with, I updated to the latest version of crDroid 7.x (7.19)
Reboot phone to bootloader
fastboot flash boot_a crDroidAndroid-12.1-20220709-enchilada-v8.6_boot.img
fastboot flash boot_b crDroidAndroid-12.1-20220709-enchilada-v8.6_boot.img
Reboot phone to bootloader.
Use vol +/- keys to select recovery mode & press power button to enter recovery.
On phone, in red menu recovery choose "Apply update" > "Apply from ADB" > "ADB sideload" & then from computer,
adb sideload crDroidAndroid-12.1-20220709-enchilada-v8.6.zip
Reboot to system
When I saw that everything worked I rebooted to recovery and uploaded the zip image to the second slot via ADB Sideload.
I didn't have GApps before and didn't install them afterwards because I don't use them.

I noticed that on the keyboard AOSP in Polish:
- swiping does not work,
- spell check does not work,
- word prompting does not work,
All these things worked on crDroid 7.19. Now they also work but in other popular languages, such as German or English.
I've tried deleting all AOSP keyboard app data and reconfiguring it from scratch, but that doesn't help.
Could I ask someone who has a clean installation to check this? Because without confirming it, it's unlikely to report the error.

8.7 testing releases available in the OP 6/6T TG channel if anyone is feeling adventurous!

Thanks for your hard work.
ROM runs pretty well, although there are some minor yet annoying issues (don't know if they have been mentioned in the Telegram group but I'll list them here anyway).
Sometimes the notification shade noticeably lags.
Text selection menu (cut, copy, etc) doesn't appear after selecting, I have to long tap the selection again for it to appear. It happens for both input fields and usual text (e.g. on a web page)
Gboard doesn't always save the buffer content into the clipboard manager. Same applies for the paste suggestions. Maybe I should install it as a system app? (I'm pretty sure I used it as a user app on crDroid 7 though)
Apps seem to unload from RAM more aggressively than on crDroid 7.
I guess they were removed in crDroid 8, but there used to be settings for weather on lock screen and smart charging (auto-disabling charging at XX%).
In quick settings, when I tap mobile data, it takes very long for the animation to switch on/off while Wi-Fi is on (only the animation). Sometimes it will get stuck at on or off until I reopen the notification shade. Also if you quickly reopen the shade, the animation will change instantly without any lag. (All this is true regardless of the Mobile data always active developer setting)

runtosafety said:
Thanks for your hard work.
ROM runs pretty well, although there are some minor yet annoying issues (don't know if they have been mentioned in the Telegram group but I'll list them here anyway).
Sometimes the notification shade noticeably lags.
Text selection menu (cut, copy, etc) doesn't appear after selecting, I have to long tap the selection again for it to appear. It happens for both input fields and usual text (e.g. on a web page)
Gboard doesn't always save the buffer content into the clipboard manager. Same applies for the paste suggestions. Maybe I should install it as a system app? (I'm pretty sure I used it as a user app on crDroid 7 though)
Apps seem to unload from RAM more aggressively than on crDroid 7.
I guess they were removed in crDroid 8, but there used to be settings for weather on lock screen and smart charging (auto-disabling charging at XX%).
In quick settings, when I tap mobile data, it takes very long for the animation to switch on/off while Wi-Fi is on (only the animation). Sometimes it will get stuck at on or off until I reopen the notification shade. Also if you quickly reopen the shade, the animation will change instantly without any lag. (All this is true regardless of the Mobile data always active developer setting)
Click to expand...
Click to collapse
So, dirty little not-so-secret: I'm not really sure what I'm doing most of the time. There are a lot of things that seem to be regressions in Android 12, and I believe I've set up overlays correctly to configure crDroid-specific features. But... There are plenty of things where I don't know where to begin, and just assume that it's something that one of the actual core ROM dev team for crDroid (I am a device maintainer, not part of the core dev team) will eventually deal with, or it's just an issue with our specific device, or ... Whatever. Occasionally it's a thing that maybe I can dig up bug reports and logs and reproduce and figure out what's up and fix it.
Most of the things you mention are entirely beyond my control.
1. I believe you. Dunno what to do there; this will probably be an upstream ROM thing that needs to get fixed, but possibly relies on an overlay I need to fix. Usually things like this, I try and try to get to the bottom of it and pull my hair out and waste hours & hours and then it's something that was in the frameworks anyway and I don't know enough Java or Kotlin or C/C++ to have possibly been able to fix it, and then someone else fixes it and I could've just waited and it would've been fine in a month or two.
2. Yeah, I've had that too; seems to depend on app. Can you send me a log after it happens?
3. I'm using GBoard as a user app myself, although that's with MinMicroG, and haven't had problems with it. But I believe you. What GApps are you using?
4. Yeah, I noticed that too. There's work to do tuning things, but I'm not sure where to begin. I'm in a little over my head trying to keep the best of both worlds between just running with the Qualcomm QTI perfd kernel driver, and cutting over to using Google's libperfmgr with power hinting, and their corresponding low memory killer drivers (the "EdwinMoq" commits you may have heard mention of). It feels like I'm getting better performance/battery life right now, with trying to just use some of the "clean up and do some tuning without dropping QTI perfd" commits as an approach, but it might be overkill. If I remove all those things, then we basically end up functioning just like vanilla LineageOS on stock kernel for battery life/performance/smoothness. I'm open to suggestions there.
5. Yes, they were removed. Lock screen was reworked a lot in Android 12, as well as background services, and running the OmniJAWS service (which was intended for older Android versions anyway) apparently broke. Smart charging functionality can be brought back by using the Advanced Charging Control (acc) Magisk module. Best results seem to be by installing the last release of AccA (the graphical front-end), and then manually setting it to use acc module v2022.2.22.1 (newer "android 12 compatible" ones actually kinda fail to work), and then check for a charging switch that supports "battery idle mode" (and toggle on "prioritize battery idle mode").
6. Quick Settings and data handling in Android 12 is... man I don't even know. See point #1. It's not just our device though, from what I've seen scroll by in the crDroid maintainer chat.

Status update (11 August):
There's a lot of stuff I'd like to work on fine-tuning, because I might not be a pro AOSP dev, but I like having things feel polished.
LineageOS has been working on merging the August ASB, maybe they're done by now; and I know Neobuddy89 has been working on merging that into crDroid sources (it wasn't ready to build/test as of a few days ago, but probably fine now).
We finally hit summer weather here and it's been too hot for me to work in the back room where my build computer (and monitor setup) lives, and my wife took the summer off teaching and I've been busy working... And working on real life household projects, cleaning, repairs, dealing with the aftermath of my cousin-in-law passing away, taking care of the kids since school is out; lots of things.
I want to fine-tune things of course, but I'll have to save that for the August security patch or later.
I'll just throw 7.20 (whatever test version) and 8.7 test 2 out to OTA for now as the official releases, because "real artists ship"... And I can't sync crDroid sources now to keep working on July ASB releases because it would probably end up pulling in August changes anyway.
Definitely seems like they've been good enough to release for weeks, I've been daily driving and haven't run into regressions, and I can't let "it's not perfect yet!" prevent people from getting updates.

Terminator.J said:
So, dirty little not-so-secret: I'm not really sure what I'm doing most of the time. There are a lot of things that seem to be regressions in Android 12, and I believe I've set up overlays correctly to configure crDroid-specific features. But... There are plenty of things where I don't know where to begin, and just assume that it's something that one of the actual core ROM dev team for crDroid (I am a device maintainer, not part of the core dev team) will eventually deal with, or it's just an issue with our specific device, or ... Whatever. Occasionally it's a thing that maybe I can dig up bug reports and logs and reproduce and figure out what's up and fix it.
Most of the things you mention are entirely beyond my control.
1. I believe you. Dunno what to do there; this will probably be an upstream ROM thing that needs to get fixed, but possibly relies on an overlay I need to fix. Usually things like this, I try and try to get to the bottom of it and pull my hair out and waste hours & hours and then it's something that was in the frameworks anyway and I don't know enough Java or Kotlin or C/C++ to have possibly been able to fix it, and then someone else fixes it and I could've just waited and it would've been fine in a month or two.
2. Yeah, I've had that too; seems to depend on app. Can you send me a log after it happens?
3. I'm using GBoard as a user app myself, although that's with MinMicroG, and haven't had problems with it. But I believe you. What GApps are you using?
4. Yeah, I noticed that too. There's work to do tuning things, but I'm not sure where to begin. I'm in a little over my head trying to keep the best of both worlds between just running with the Qualcomm QTI perfd kernel driver, and cutting over to using Google's libperfmgr with power hinting, and their corresponding low memory killer drivers (the "EdwinMoq" commits you may have heard mention of). It feels like I'm getting better performance/battery life right now, with trying to just use some of the "clean up and do some tuning without dropping QTI perfd" commits as an approach, but it might be overkill. If I remove all those things, then we basically end up functioning just like vanilla LineageOS on stock kernel for battery life/performance/smoothness. I'm open to suggestions there.
5. Yes, they were removed. Lock screen was reworked a lot in Android 12, as well as background services, and running the OmniJAWS service (which was intended for older Android versions anyway) apparently broke. Smart charging functionality can be brought back by using the Advanced Charging Control (acc) Magisk module. Best results seem to be by installing the last release of AccA (the graphical front-end), and then manually setting it to use acc module v2022.2.22.1 (newer "android 12 compatible" ones actually kinda fail to work), and then check for a charging switch that supports "battery idle mode" (and toggle on "prioritize battery idle mode").
6. Quick Settings and data handling in Android 12 is... man I don't even know. See point #1. It's not just our device though, from what I've seen scroll by in the crDroid maintainer chat.
Click to expand...
Click to collapse
Just updated, I'll see if 8.7 has fixed that.
See the spoiler below for logs.
NikGApps Basic. Yeah, I only noticed it's not a recommended option after installing (although that's what I used on crDroid 7 where I didn't have that issue).
Spoiler: Text selection log
Code:
08-16 22:44:05.021 2387 2387 D BatteryInfoBroadcast: onReceive: android.intent.action.BATTERY_CHANGED isPowerSaveMode: false
08-16 22:44:05.022 2387 2387 D BatteryDefenderNotification: isPlugged: true | isOverheated: false | defenderEnabled: false | isCharged: false
08-16 22:44:07.564 1035 1035 D vendor.qti.vibrator: Vibrator on for timeoutMs: 10
08-16 22:44:07.566 1035 4878 D vendor.qti.vibrator: Starting on on another thread
08-16 22:44:07.576 1035 4878 D vendor.qti.vibrator: Notifying on complete
08-16 22:44:07.577 1035 1035 D vendor.qti.vibrator: QTI Vibrator off
08-16 22:44:07.583 12805 12805 I cr_CompositorSurfaceMgr: Transitioning to surface with format: -1
08-16 22:44:07.592 12805 12805 D androidtc: Initializing SystemTextClassifier, type = System
08-16 22:44:07.593 12805 12805 W androidtc: TextClassifier called on main thread
08-16 22:44:07.595 3597 3597 I AiAiTextClassifier: onCreateTextClassificationSession = TextClassificationSessionId {8321aa96-9441-474e-9836-c6170d716612}
08-16 22:44:07.596 3597 3597 I AiAiTextClassifier: AiaiTextClassifierServiceConnector.onSuggestSelection
08-16 22:44:07.600 12805 12805 I cr_CompositorSurfaceMgr: surfaceCreated format: 0
08-16 22:44:07.667 12805 12805 I cr_CompositorSurfaceMgr: SurfaceState : detach from parent : -3
08-16 22:44:07.668 12805 12805 E cr_CompositorSurfaceMgr: surfaceDestroyed format : -3
08-16 22:44:09.149 1347 4506 D WindowManager: perform drag: [email protected] surface=Surface(name=drag surface)/@0x3a9d179 flags=100 data=ClipData { text/plain {T(8)} }
08-16 22:44:09.149 1347 4506 D WindowManager: registering drag input channel
08-16 22:44:09.171 1347 4506 D WindowManager: broadcasting DRAG_STARTED at (366.0, 1025.0)
08-16 22:44:09.171 1347 1731 W WindowManager: Unexpected ACTION_DOWN in drag layer
08-16 22:44:09.179 1035 1035 D vendor.qti.vibrator: Vibrator on for timeoutMs: 10
08-16 22:44:09.180 1035 4884 D vendor.qti.vibrator: Starting on on another thread
08-16 22:44:09.191 1035 4884 D vendor.qti.vibrator: Notifying on complete
08-16 22:44:09.192 1035 1035 D vendor.qti.vibrator: QTI Vibrator off
08-16 22:44:09.534 1347 1731 D WindowManager: Got UP on move channel; dropping at 366.0,1025.0
08-16 22:44:09.537 1347 1731 D WindowManager: sending DROP to Window{e1f7993 u0 com.vivaldi.browser.snapshot/com.google.android.apps.chrome.Main}
08-16 22:44:09.542 12805 12805 I ViewRootImpl[Main]: Reporting drop result: true
08-16 22:44:09.542 1347 8568 D WindowManager: Drag into new candidate view @ [email protected]
08-16 22:44:09.542 1347 8568 D WindowManager: Drop result=true reported by [email protected]
08-16 22:44:09.542 1347 8568 D WindowManager: unregistering drag input channel
08-16 22:44:09.542 1347 8568 D WindowManager: broadcasting DRAG_ENDED
08-16 22:44:09.542 1347 1731 D WindowManager: Drag ending; tearing down input channel
08-16 22:44:09.545 1347 1731 W InputManager-JNI: Input channel object 'drag (client)' was disposed without first being removed with the input manager!
08-16 22:44:10.880 3014 3086 I PhenotypeProcessReaper: Memory state is: 125
08-16 22:44:11.370 2387 2387 D PowerNotificationWarningsGoogleImpl: onReceive: android.intent.action.BATTERY_CHANGED
08-16 22:44:11.376 2387 2387 D BatteryInfoBroadcast: onReceive: android.intent.action.BATTERY_CHANGED isPowerSaveMode: false
08-16 22:44:11.376 2387 2387 D BatteryDefenderNotification: isPlugged: true | isOverheated: false | defenderEnabled: false | isCharged: false
08-16 22:44:11.768 4405 4485 E QMI_FW : qmi_cci_get_ref: ref count increased 2
08-16 22:44:11.772 4405 4415 E QMI_FW : qmi_cci_get_ref: ref count increased 2
08-16 22:44:11.792 3840 10026 I ConnectivityReport: signalStrength of #1 updated to 2
08-16 22:44:12.054 2387 2387 D PowerNotificationWarningsGoogleImpl: onReceive: android.intent.action.BATTERY_CHANGED
08-16 22:44:12.059 2387 2387 D BatteryInfoBroadcast: onReceive: android.intent.action.BATTERY_CHANGED isPowerSaveMode: false
08-16 22:44:12.059 2387 2387 D BatteryDefenderNotification: isPlugged: true | isOverheated: false | defenderEnabled: false | isCharged: false

Everything blew up this summer in real life.
I finally pushed the 8.7 test 2 that I've been using as a daily driver personally and everyone in Telegram seems to have been more than happy with to OTA as the official July 2022 ASB release, sorry it's like a month late.
The July patch took a long time to merge, and August even longer, but it'll take me a while to release August unless I just skip working on my backlog of bugfix notes entirely.

Okay, I took a mental health day to work on Android stuff.
First test builds of 8.8 will be going up tonight in the Telegram group if anyone wants to join & try them out!
Had to drop Camera2 (the basic AOSP camera) since that little 5MB makes the difference between MindTheGapps 12.1 arm64 & Magisk both being able to install and updater able to correctly process addon.d scripts when installing the zip, and a bootloop because it couldn't quiiiiite finish copying over the privapp permission XMLs to system/product/. Stupid tiny system partition...
No device-specific bugfixes yet in my trees, just testing with the most recent lineage changes & crDroid 8.8 sources.