Question "Ok google" not working on custom roms

Question "Ok google" not working on custom roms - Xiaomi Mi 11 Lite 4G

As posted in other thread, i'm on latest crDroid (7.9) with Flamegapps full.
Pretty much everything working, except voice match "hey/ok google", whose activation is grayed out in google settings ("the function is not available on your device").
Searching the web, it seems that's a common problem for Android 11 custom roms, related to some file (hotword blobs) missing in the rom, device specific.
See this thread for example:
New Hotword blobs on Android 11 · Issue #19 · ShivamKumarJha/android_tools
Hotword functionality requires the following files on Android 11 system_ext/etc/permissions/com.android.hotwordenrollment.common.util.xml system_ext/framework/com.android.hotwordenrollment.common.u...
github.com
I'm no dev, so i don't really understand this stuff...but many people have my same problem here and on Telegram (the others simply doesn't use voice match, i guess), so i think it is good thing to report out this thing to developers, if this is the problem
thank you

I'm leaving this reply in case someone needs it in the future.
The solution is making Google a system app, you can use a magisk module called systemize.
This is the most recent version I found: https://github.com/xeddmc/terminal_systemizer

Cryn_058 said:
I'm leaving this reply in case someone needs it in the future.
The solution is making Google a system app, you can use a magisk module called systemize.
This is the most recent version I found: https://github.com/xeddmc/terminal_systemizer
Click to expand...
Click to collapse
Thank you very much for your replay.
That was the issue, and yours is a good solution.
For me, the issue has been solved with the next Flamegapps release, some time later.

i confirm on android 13 crdroid rom app 2023, nikgapps, Google must be installed as system app to google assistant working ( "and not be grayed out in google settings)

strachan said:
i confirm on android 13 crdroid rom app 2023, nikgapps, Google must be installed as system app to google assistant working ( "and not be grayed out in google settings)
Click to expand...
Click to collapse
System/app or system/priv-app??

Related

[GUIDE] GSI ROMs installation tutorial. In pursuit of the best ROM that is not MIUI

Disclaimer: I am not a developer (I don't code), but I have been flashing ROMs for many devices over the years. This is more of a practical guide from an end-user perspective in pursuit of finding the best ROM for this magnificent hardware. This is more of a compilation of all the relevant information I found. I'm very open to suggestions/corrections that could improve this.
Disclaimer: Only tested with RR, PixelExperience, and ArrowOS GSI.
I haven't seen a proper guide to flash GSI ROMs for Mi Mix 3, thus I decided to share what I know that works. I put a brief explanation for each step below.
1. Unlock Bootloader - If you haven't done so yet, I recommend following the instructions in https://www.reddit.com/r/Xiaomi/wiki/bootloader
2. Install TWRP
a) I recommend to use the official TWRP from this link https://twrp.me/xiaomi/xiaomimix3.html or refer to the forum https://forum.xda-developers.com/mi-mix-3/development/recovery-unofficial-twrp-recovery-t3901261.
b) To install TWRP, I recommend to follow the instructions from Xiaomi.eu. For those not familiar, the "twrp.img" in the code should be the full path of the file. Something like "D:\folder\twrp.img"
c) If you have an older version of TWRP, I suggest to update it to the official.
3. Install Xiaomi.eu - Start from this step in case of bootloops or issues (especially caused by Magisk modules by my experience)
a) This is what I do instead of the 'flash vendor.img from Chinese Dev' prerequisite mentioned in other threads. This is an easier step (just one flash in TWRP) and a better fallback (a working ROM) in case things go wrong. I have had no issues (fingerprint, calls, etc..) with this and I've done this thrice.
b) Download the latest MIUIv10.2 Stable for MIMix3 from the link https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/.
c) Wipe > Format Data (prevents problems, and removes encryption if you had it). Also do Factory Reset (idk, just to be sure).
d) Copy xiaomi.eu ROM to internal storage, then Install > Flash. No need to boot/restart, proceed to the next step.
4. Install GSI ROM - wth is GSI? https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
a) We can actually install any GSI in https://forum.xda-developers.com/project-treble/trebleenabled-device-development but there is an issue in installing Google Apps (Open GApps) as many people mentioned in https://forum.xda-developers.com/mi-mix-3/development/9-0-resurrection-remix-v7-0-t3891975 and as confirmed by the official TWRP thread https://forum.xda-developers.com/mi...p-recovery-t3901261/post79035909#post79035909
b) Given the above, the only feasible options are GSI ROMs with built-in GApps and the only 2 I found are PixelExperience GSI and ArrowOS GSI. As GApps is integrated in the system.img, no need to flash Open GApps thus no issues. Having tried both, I personally recommend ArrowOS due to the performance and additional customization options.
c) Download the arm64 AB version (ArrowOS as an example) https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
d) Copy the resulting system.img to internal storage (extract if its a .zip), in TWRP click Install > Install Images > select system.img of ArrowOS > select System partition. You can now boot, or follow next step to root with Magisk.
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-mix-3/how-to/root-magisk-18-2-mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Final Thoughts
ArrowOS GSI seems to be stable enough and I'm using it as my daily driver now. I am so much happier compared to when using MIUI Global ROM. I really like the performance (very fluid), battery life (a lot better than MIUI Global), customizations (like traffic indicator, status bar stuff), unli Google Photos, and everything that makes AOSP/stock android awesome. No more bloatware, annoying non-dismissable notifications, and horrible auto brightness from MIUI.
The only real issue I encountered so far is the bluetooth audio/music issue, but this seems to be a common problem in GSI ROMs. Bluetooth calls work though. There is no app to handle the slider (but I don't care. lol). Lastly, the AI button becomes useless, but see below for the fix.
Optional stuff that makes things better:
1. Remapping AI button - When using GSI ROMs, AI button becomes useless. But to map it back to Google Assistant (or anything actually), follow the instructions from this thread (needs some knowledge about Tasker). https://forum.xda-developers.com/showpost.php?p=78523778&postcount=38 For the Tasker Task, I selected Input > Voice Command. This now assigns the button to open Google Assistant. Does not work well when screen is off though, but its just easy to unlock.
2. Google Camera - The main reason why I bought this phone. Google Camera brings out the best in the awesome camera - Use this version https://forum.xda-developers.com/mi-mix-3/themes/gcam-6-manual-focus-long-exposure-t3885610
3. Stereo Speaker Mod - https://forum.xda-developers.com/mi-mix-3/themes/magisk-stereo-speaker-mod-mix-3-t3900580 Makes the phone earpiece into a speaker, increasing overall volume. I personally use version 3 and I'm very happy.
4. Fluid NG - App in Google Play Store to have the same recents/home/back gestures from MIUI 10.

reasonablebasis said:
Disclaimer: I am not a developer (I don't code), but I have been flashing ROMs for many devices over the years. This is more of a practical guide from an end-user perspective in pursuit of finding the best ROM for this magnificent hardware. This is more of a compilation of all the relevant information I found. I'm very open to suggestions/corrections that could improve this
I haven't seen a proper guide to flash GSI ROMs for Mi Mix 3, thus I decided to share what I know that works. I put a brief explanation for each step below.
1. Unlock Bootloader - If you haven't done so yet, I recommend following the instructions in https://www.reddit.com/r/Xiaomi/wiki/bootloader
2. Install TWRP
a) I recommend to use the official TWRP from this link https://twrp.me/xiaomi/xiaomimix3.html or refer to the forum https://forum.xda-developers.com/mi-mix-3/development/recovery-unofficial-twrp-recovery-t3901261.
b) To install TWRP, I recommend to follow the instructions from Xiaomi.eu. For those not familiar, the "twrp.img" in the code should be the full path of the file. Something like "D:\folder\twrp.img"
c) If you have an older version of TWRP, I suggest to update it to the official.
3. Install Xiaomi.eu - Start from this step in case of bootloops or issues (especially caused by Magisk modules by my experience)
a) This is what I do instead of the 'flash vendor.img from Chinese Dev' prerequisite mentioned in other threads. This is an easier step (just one flash in TWRP) and a better fallback (a working ROM) in case things go wrong. I have had no issues (fingerprint, calls, etc..) with this and I've done this thrice.
b) Download the latest MIUIv10.2 Stable for MIMix3 from the link https://xiaomi.eu/community/threads/miui-10-0-10-1-10-2-stable-release.47170/.
c) Wipe > Format Data (prevents problems, and removes encryption if you had it). Also do Factory Reset (idk, just to be sure).
d) Copy xiaomi.eu ROM to internal storage, then Install > Flash. No need to boot/restart, proceed to the next step.
4. Install GSI ROM - wth is GSI? https://github.com/phhusson/treble_experimentations/wiki/Frequently-asked-questions-(FAQ)
a) We can actually install any GSI in https://forum.xda-developers.com/project-treble/trebleenabled-device-development but there is an issue in installing Google Apps (Open GApps) as many people mentioned in https://forum.xda-developers.com/mi-mix-3/development/9-0-resurrection-remix-v7-0-t3891975 and as confirmed by the official TWRP thread https://forum.xda-developers.com/mi...p-recovery-t3901261/post79035909#post79035909
b) Given the above, the only feasible options are GSI ROMs with built-in GApps and the only 2 I found are PixelExperience GSI and ArrowOS GSI. As GApps is integrated in the system.img, no need to flash Open GApps thus no issues. Having tried both, I personally recommend ArrowOS due to the performance and additional customization options.
c) Download the arm64 AB version (ArrowOS as an example) https://forum.xda-developers.com/pr...abled-device-development/gsi-arrowos-t3835111
d) Copy the resulting system.img to internal storage (extract if its a .zip), in TWRP click Install > Install Images > select system.img of ArrowOS > select System partition. You can now boot, or follow next step to root with Magisk.
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-mix-3/how-to/root-magisk-18-2-mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Final Thoughts
ArrowOS GSI seems to be stable enough and I'm using it as my daily driver now. I am so much happier compared to when using MIUI Global ROM. I really like the performance (very fluid), battery life (a lot better than MIUI Global), customizations (like traffic indicator, status bar stuff), unli Google Photos, and everything that makes AOSP/stock android awesome. No more bloatware, annoying non-dismissable notifications, and horrible auto brightness from MIUI.
The only real issue I encountered so far is the bluetooth audio/music issue, but this seems to be a common problem in GSI ROMs. Bluetooth calls work though. There is no app to handle the slider (but I don't care. lol). Lastly, the AI button becomes useless, but see below for the fix.
Optional stuff that makes things better:
1. Remapping AI button - When using GSI ROMs, AI button becomes useless. But to map it back to Google Assistant (or anything actually), follow the instructions from this thread (needs some knowledge about Tasker). https://forum.xda-developers.com/showpost.php?p=78523778&postcount=38 For the Tasker Task, I selected Input > Voice Command. This now assigns the button to open Google Assistant. Does not work well when screen is off though, but its just easy to unlock.
2. Google Camera - The main reason why I bought this phone. Google Camera brings out the best in the awesome camera - Use this version https://forum.xda-developers.com/mi-mix-3/themes/gcam-6-manual-focus-long-exposure-t3885610
3. Stereo Speaker Mod - https://forum.xda-developers.com/mi-mix-3/themes/magisk-stereo-speaker-mod-mix-3-t3900580 Makes the phone earpiece into a speaker, increasing overall volume. I personally use version 3 and I'm very happy.
Click to expand...
Click to collapse
Not all GSI work ontop of Xiaomi Eu
Flashing magisk and safety net patch also doesn't guarantee safety net passing on a few of the GSI as well. CTS will fail for obvious reasons

Mackay53 said:
Not all GSI work ontop of Xiaomi Eu
Flashing magisk and safety net patch also doesn't guarantee safety net passing on a few of the GSI as well.
Click to expand...
Click to collapse
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?

reasonablebasis said:
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
Click to expand...
Click to collapse
Can't remember as it was a while ago, possibly OctoOS and descendant and 1 other, omni ROM maybe.
For the ones that come with SU you need to navigate to the xbin folder in the system and remove the SU file.
Then cause Xiaomi EU uses the wrong fingerprint props you need to use the magisk props config module and manually type in the mix 3 fingerprint (unless the module has been updated to include mix 3).
If you installed the Chinese dev vendor then the props will be there ready to be used so the magisk module can make them active without manually typing it. This will sort out both safety net fails.

If this was sometime ago, the features in China Dev would have already been integrated in the latest China Stable, which is the basis of Xiaomi.EU.
Maybe you can test it now to see if Xiaomi.EU really works. I tried it with RR, PixelExperience, and ArrowOS and I'm facing no issues. So flashing China Dev vendor.img seems to be an outdated instruction.

reasonablebasis said:
Noted. Which GSI have you tried that do not work on top of Xiaomi.EU? I tried RR, PixelExperience, and ArrowOS and all work well. I can put this as a disclaimer.
Any solution for the Magisk safetynet, or is this really the best solution available so far?
Click to expand...
Click to collapse
Pixel dust gsi too....

reasonablebasis said:
If this was sometime ago, the features in China Dev would have already been integrated in the latest China Stable, which is the basis of Xiaomi.EU.
Maybe you can test it now to see if Xiaomi.EU really works. I tried it with RR, PixelExperience, and ArrowOS and I'm facing no issues. So flashing China Dev vendor.img seems to be an outdated instruction.
Click to expand...
Click to collapse
The 3 GSI you mention is a very small sample of the GSI available so you can't say it's an outdated instruction. Have you tested them all like I have? No you haven't.
Xiaomi EU does not use the correct mix3 vendor.img, that's what causes the issue.

Mackay53 said:
The 3 GSI you mention is a very small sample of the GSI available so you can't say it's an outdated instruction. Have you tested them all like I have? No you haven't.
Xiaomi EU does not use the correct mix3 vendor.img, that's what causes the issue.
Click to expand...
Click to collapse
Ok, I'll put a disclaimer that this only works on RR, PixelExperience, and ArrowOS. Anyway, I'm sure that the latest stable Xiaomi.EU vendor works without any issues with ArrowOS, else why would I be using it as my daily driver.

[deleted, duplicate post]

Someone know if there is a GSI with gapps and that don't have issue with bluetooth?

SafetyPatch module
reasonablebasis said:
5. Install Magisk
a) The Magisk version that passes SafetyNet is the builds from ianmacd https://github.com/ianmacd/MagiskBuilds look for v18.2 (newer versions might work but I haven't tried them yet). You can still use the official Magisk Manager and the ianmacd version will be recognized. Just change the update channel in Magisk to https://goo.gl/yZpnrf. Credits to this thread https://forum.xda-developers.com/mi-...mix-3-t3905754
b) After flashing Magisk, boot, install Magisk Manager, then download and install the module "SafetyPatch". SafetyNet check will now be success.
c) Even though SafetyNet is passed, some banking apps still are not working. Hopefully someone can share a solution (probably MagiskHide Props Config, or canary builds?) to make banking apps work.
Click to expand...
Click to collapse
Mate, I can't find this module via Magisk Manager... Please help!

jonny908 said:
Mate, I can't find this module via Magisk Manager... Please help!
Click to expand...
Click to collapse
You sure? Try searching for "SafetyPatch"

reasonablebasis said:
You sure? Try searching for "SafetyPatch"
Click to expand...
Click to collapse
Strange....

reasonablebasis said:
You sure? Try searching for "SafetyPatch"
Click to expand...
Click to collapse
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....

jonny908 said:
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
Click to expand...
Click to collapse
On Arrow ?

Wahoux said:
On Arrow ?
Click to expand...
Click to collapse
Yep! Not sure how to prove that though xD

Android Q GSI !
https://www.xda-developers.com/android-q-gsi-project-treble/

Wahoux said:
Android Q GSI !
https://www.xda-developers.com/android-q-gsi-project-treble/
Click to expand...
Click to collapse
Dare to try? xD

jonny908 said:
Dare to try? xD
Click to expand...
Click to collapse
ahah no xD
Right now i'm about to flash Arrow, I hope I won't have bluetooth issue . On the non-GSI Pixel Experience, some reported issue with bluetooth whereas it was working fine for me... so let's see :fingers-crossed:

jonny908 said:
Mate, I can't find this module via Magisk Manager... Please help!
Click to expand...
Click to collapse
jonny908 said:
Issue resolved. I had to use Magisk Manager 7.x.x, I was trying using 6.0.
Installed, MagiskHide working as it should now.
---------- Post added at 18:23 ---------- Previous post was at 18:15 ----------
@reasonablebasis
Sorry for third post in a row., but.... I have no issues with bluetooth audio/music that everyone is talking about. Listening to Spotify on my QCY bluetooth earphones now.....
Click to expand...
Click to collapse
Wow good for you. You flashed xiaomi.eu prior to GSI right? enumerate the steps you did, so that we we hopefully can replicate your success. Hehe

[MAGISK] Ambient EQ Tweak (Flame)

Hey all,
Just wanted to share a simple Magisk Module that tweaks the Ambient EQ on our phones to behave more like Apple's True Tone feature. This idea and module was originally created by @MishaalRahman and published here. As you can see the article was published in November 2019, and the structure of Magisk Modules has since changed. So, the module that you can download from that article no longer works. I've simply updated the module to be compatible with the new Magisk Module file structure and function correctly on our phones.
Instructions and Notes:
Note: This module was originally created for the Pixel 4 (Flame). Due to the Pixel 4 XL (Coral) using a different panel, this module may have unintended effects on screen color and gamma that I have not been able to test. Give it a shot if you'd like, but YMMV.
Install via Magisk Manager or flash the .zip using your favorite Kernel Manager and reboot.
The module has been submitted to the Magisk Module Repo, where it will be able to be downloaded directly from the Magisk Manager app, but it is awaiting approval.
Download (Local)
Thanks to @digitalcircuit for zip-aligning the APK, which fixes earlier reports of App update failures and other weird behavior.
Confirmed working on Android 12.1!
Original Author: @MishaalRahman
Original Module and Associated Documentation: https://www.xda-developers.com/google-pixel-4-ambient-eq-tweak/
Source: https://github.com/Alcolawl/AmbientEQTweak

AFAIK, this module could really mess with the performance on my Pixel 4 XL. Don't know how's the outcome here but thanks for the module template update!

Queentus said:
AFAIK, this module could really mess with the performance on my Pixel 4 XL. Don't know how's the outcome here but thanks for the module template update!
Click to expand...
Click to collapse
Are you saying that this module caused a drop in performance on your Pixel 4 XL? I can't say I've had the same experience on my end.
Looking through the comments on the article for the original module, others have complained about a performance drop as well. Certainly interesting and worth investigating.

Alcolawl said:
Are you saying that this module caused a drop in performance on your Pixel 4 XL? I can't say I've had the same experience on my end.
Looking through the comments on the article for the original module, others have complained about a performance drop as well. Certainly interesting and worth investigating.
Click to expand...
Click to collapse
Yes. Check out those comments blow @MishaalRahman's original article, I'm pretty sure I'm not the only one who had performance drop after using @MishaalRahman's module.

Installed and don't seem to have any issues with battery consumption. Thank you for the updated Magisk module.

Edit 2020-10-7: I've managed to fix this by decompiling the APK, recompiling it using the modern Android SDK, and ensuring I both signed and zipaligned the APK. If anyone wants this, I can upload it somewhere.
This appears to break on Android 11. Workaround: disable or remove the Ambient EQ Tweak Magisk module.
Rambling details in the hopes that others facing this issue can find it via Internet searching:
Some Google apps (Google Play Services, Google Camera, Files by Google, Google Photos, Device Personalization Services, Google TV/Play Movies, Google Play Games) and one F-Droid app (BirthDay Droid) would fail to install/update with a vexing error code:
Code:
Targeting R+ (version 30 and above) requires the resources.arsc of installed APKs to be stored uncompressed and aligned on a 4-byte boundary
However, various other targetSdk 30 apps would install/update just fine (e.g. Firefox, Firefox Nightly).
Uninstalling updates for Google Play Services almost fully broke the functionality of Play Services. If the Ambient EQ module is enabled, Android 11 updates will also lead to bootloops unless Android 11 is first fully booted once with the stock image. Given nobody else seemed to mention this online, it confounded me. After tinkering, I realized that booting stock (without Magisk) worked, I narrowed it down to modules (not MagiskHide/etc), and down to this module. I suspect the overlay APK itself needs updated for wherever the color temperature ramp resources are stored in Android 11.
I think simply disabling/removing the module and rebooting should be sufficient to fully recover. If one's concerned about inconsistent Play Services state, it's possible to clear data there, but that was not necessary for me.

digitalcircuit said:
Edit 2020-10-7: I've managed to fix this by decompiling the APK, recompiling it using the modern Android SDK, and ensuring I both signed and zipaligned the APK. If anyone wants this, I can upload it somewhere.
This appears to break on Android 11. Workaround: disable or remove the Ambient EQ Tweak Magisk module.
Rambling details in the hopes that others facing this issue can find it via Internet searching:
Some Google apps (Google Play Services, Google Camera, Files by Google, Google Photos, Device Personalization Services, Google TV/Play Movies, Google Play Games) and one F-Droid app (BirthDay Droid) would fail to install/update with a vexing error code:
Code:
Targeting R+ (version 30 and above) requires the resources.arsc of installed APKs to be stored uncompressed and aligned on a 4-byte boundary
However, various other targetSdk 30 apps would install/update just fine (e.g. Firefox, Firefox Nightly).
Uninstalling updates for Google Play Services almost fully broke the functionality of Play Services. If the Ambient EQ module is enabled, Android 11 updates will also lead to bootloops unless Android 11 is first fully booted once with the stock image. Given nobody else seemed to mention this online, it confounded me. After tinkering, I realized that booting stock (without Magisk) worked, I narrowed it down to modules (not MagiskHide/etc), and down to this module. I suspect the overlay APK itself needs updated for wherever the color temperature ramp resources are stored in Android 11.
I think simply disabling/removing the module and rebooting should be sufficient to fully recover. If one's concerned about inconsistent Play Services state, it's possible to clear data there, but that was not necessary for me.
Click to expand...
Click to collapse
Yep, I can confirm this.

I've had a request in the comments of the XDA blog post to share my modified Magisk module, so I've attached it to this post. Only change is decompiling the APK, zipaligning, then re-signing it; credit to Mishaal Rahman for the original module. No warranty provided.
You should be able to flash this in Magisk on top of the existing module, or from scratch if you've removed or never installed the previous module.
In case there's issues with the XDA forum download, I've also hosted this on my web server as AmbientEqTweakAligned-v1.2.zip:
SHA256 hash for both is e8fa5f9283acd0bcc8518e0acc5dd905c62c348cf0a4534b4bed072a5ebb0d7d.

digitalcircuit said:
I've had a request in the comments of the XDA blog post to share my modified Magisk module, so I've attached it to this post. Only change is decompiling the APK, zipaligning, then re-signing it; credit to Mishaal Rahman for the original module. No warranty provided.
You should be able to flash this in Magisk on top of the existing module, or from scratch if you've removed or never installed the previous module.
In case there's issues with the XDA forum download, I've also hosted this on my web server as AmbientEqTweakAligned-v1.2.zip:
SHA256 hash for both is e8fa5f9283acd0bcc8518e0acc5dd905c62c348cf0a4534b4bed072a5ebb0d7d.
Click to expand...
Click to collapse
Thanks

digitalcircuit said:
I've had a request in the comments of the XDA blog post to share my modified Magisk module, so I've attached it to this post. Only change is decompiling the APK, zipaligning, then re-signing it; credit to Mishaal Rahman for the original module. No warranty provided.
You should be able to flash this in Magisk on top of the existing module, or from scratch if you've removed or never installed the previous module.
In case there's issues with the XDA forum download, I've also hosted this on my web server as AmbientEqTweakAligned-v1.2.zip:
SHA256 hash for both is e8fa5f9283acd0bcc8518e0acc5dd905c62c348cf0a4534b4bed072a5ebb0d7d.
Click to expand...
Click to collapse
Just to confirm, will this work on Android 11, latest Magisk?
Thanks in advance!

Rodimus8402 said:
Just to confirm, will this work on Android 11, latest Magisk?
Thanks in advance!
Click to expand...
Click to collapse
As of 2021-1-5, I'm successfully using this Ambient Eq tweak module on Android 11 with the December 2020 security patch using Magisk 21.2 (beta channel) with Magisk Manager 8.0.4.
I haven't checked the ADB logcat to make sure it's actually applying the color temperature changes, but it seems to work and I haven't had any issues.

No performence issue on Jan 2021 update.

Can this be used on the pixel 4xl running android 12.1 April 2022 security patch ?

shahez said:
Can this be used on the pixel 4xl running android 12.1 April 2022 security patch ?
Click to expand...
Click to collapse
It works on Android 12.1 just fine. I've confirmed the AmbientEQ changes with adb commands (adb shell dumpsys color_display). I can't comment on any performance issues just yet but the module itself does work properly.
EDIT: Just make sure to download the fixed .zip supplied by DigitalCircuit. I've also changed the download link in the original post to make sure people don't download the old .zip that broke the OS.

[q] Gpay on lineage 19.1

Hey guys, has anyone gotten Gpay to work on lineage 19.1? I have done the following and have had very odd results. Firstly, I am passing safteynet and my device is registered as play certified in Google play store. I'm seeing where sometimes gpay won't open at all and when it does it says it is unable to load my payment methods.
Specs:
OS - linageOS 19.1 (latest build as of this post)
GAPPS - Mindthegapps (latest build as of this post)
Steps taken:
Installed magisk, enabled zygisk and rebooted
Installed magisk hide props module then rebooted
Installed shamiko module then rebooted
Installed universal safteynet fix (zygisk) then rebooted
Configured denylist in magisk checking GPS (all), and Gpay (all) rebooted
Changed device fingerprint with magisk hide props module to a certified one then rebooted
Additional steps taken:
I cleared data from GPS, play store and Gpay and rebooted
I tried a different device fingerprint and rebooted (clearing data like above afterwards and rebooting again)
I have done a complete fresh install of my OS and tried again from scratch.
I also tried seeing is renaming magisk would help at all, it didn't
It appears I'm getting nowhere with this. If anyone has gotten it to work and has some insight it's be greatly appreciated!

Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.

deathblade said:
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
Click to expand...
Click to collapse
Hey deathblade!
Thanks for helping me out on the other thread.
Just wanted to check in, did you use the official build or the unofficial one with the Pixel Goodies? I'm intending/hoping to have full functionalities of Google Pay using the unofficial build, but from your post it seems that I can't have the Pixel experience if I want the ROM to work with Google Pay?

HW898 said:
Hey deathblade!
Thanks for helping me out on the other thread.
Just wanted to check in, did you use the official build or the unofficial one with the Pixel Goodies? I'm intending/hoping to have full functionalities of Google Pay using the unofficial build, but from your post it seems that I can't have the Pixel experience if I want the ROM to work with Google Pay?
Click to expand...
Click to collapse
I'm using the official build. I think the unofficial has everything needed to use Gpay and have some pixel things baked in. So might be worth a look in your case

deathblade said:
I'm using the official build. I think the unofficial has everything needed to use Gpay and have some pixel things baked in. So might be worth a look in your case
Click to expand...
Click to collapse
Aite, I will try out the unofficial one and see if GPay works there too. Thanks for the headsup!

HW898 said:
Aite, I will try out the unofficial one and see if GPay works there too. Thanks for the headsup!
Click to expand...
Click to collapse
I just remembered, the unofficial is setup to pass safteynet out the box, but more maybe needed for Gpay to work. Once you flash it try it out, if you run into issues I can provide what I did to get Gpay working

deathblade said:
Nevermind, looks like it was an issue from having the pixelify module installed as well. After I removed it it started working just fine.
Click to expand...
Click to collapse
Hi there, trying out the official build after experiencing some problems on the unofficial one. Any alternatives to pixiel-ing the ROM?

HW898 said:
Hi there, trying out the official build after experiencing some problems on the unofficial one. Any alternatives to pixiel-ing the ROM?
Click to expand...
Click to collapse
Not that I've found, however I did notice if you install the pixelify module then uninstall it, it does seem to leave some stuff behind. Like I still have the option to use Hold for me and direct my call. So it might work out where you can install it to get the things you want then remove it to get Gpay working

deathblade said:
Not that I've found, however I did notice if you install the pixelify module then uninstall it, it does seem to leave some stuff behind. Like I still have the option to use Hold for me and direct my call. So it might work out where you can install it to get the things you want then remove it to get Gpay working
Click to expand...
Click to collapse
I see... So these also means stuff like Now playing etc. will be gone too right?
Also, did you experience the problems I've faced in the unofficial build? sounds cannot change etc. as posted in main thread

HW898 said:
I see... So these also means stuff like Now playing etc. will be gone too right?
Also, did you experience the problems I've faced in the unofficial build? sounds cannot change etc. as posted in main thread
Click to expand...
Click to collapse
Nope now playing is still there. I really only used it the module to force call screening to show up. But I have pretty much everything I remember from stock plus a few phone related goodies. I never tried the unofficial build but on the official I do not have that issue

deathblade said:
Nope now playing is still there. I really only used it the module to force call screening to show up. But I have pretty much everything I remember from stock plus a few phone related goodies. I never tried the unofficial build but on the official I do not have that issue
Click to expand...
Click to collapse
I see... I will try installing the official one without magisk as I won't want to meddle with rooting stuff for now, will get back with results asap!

deathblade said:
Hey guys, has anyone gotten Gpay to work on lineage 19.1? I have done the following and have had very odd results. Firstly, I am passing safteynet and my device is registered as play certified in Google play store. I'm seeing where sometimes gpay won't open at all and when it does it says it is unable to load my payment methods.
Specs:
OS - linageOS 19.1 (latest build as of this post)
GAPPS - Mindthegapps (latest build as of this post)
Steps taken:
Installed magisk, enabled zygisk and rebooted
Installed magisk hide props module then rebooted
Installed shamiko module then rebooted
Installed universal safteynet fix (zygisk) then rebooted
Configured denylist in magisk checking GPS (all), and Gpay (all) rebooted
Changed device fingerprint with magisk hide props module to a certified one then rebooted
Additional steps taken:
I cleared data from GPS, play store and Gpay and rebooted
I tried a different device fingerprint and rebooted (clearing data like above afterwards and rebooting again)
I have done a complete fresh install of my OS and tried again from scratch.
I also tried seeing is renaming magisk would help at all, it didn't
It appears I'm getting nowhere with this. If anyone has gotten it to work and has some insight it's be greatly appreciated!
Click to expand...
Click to collapse
Just also wanted to clarify in the case I decide to install magisk, which module do you install exactly? All of them? Zygisk/hide props module/shamiko/universal safetynet fix?

HW898 said:
Just also wanted to clarify in the case I decide to install magisk, which module do you install exactly? All of them? Zygisk/hide props module/shamiko/universal safetynet fix?
Click to expand...
Click to collapse
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them

deathblade said:
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
Click to expand...
Click to collapse
Aite thanks for the help mate! just installed but apparently, i couldn't find gapps despite sideloading it.. might have to reinstall again

Hmm safetynet fix seems to fail, can't pass cts profile.. any step by step guides by any chance?
deathblade said:
Ok so here is the breakdown:
Zygisk is not a module, but an implementation method used by modules. Magiskhide props is used to change the device fingerprint to a valid one that registers as protected by google play. Shamiko is for hiding root from Google play services, and Gpay (and whatever other apps may need it). Universal safteynet fix is used to help pass google safteynet checks (security). Not listed is the pixelify module used to add pixel exclusive features but of course with it install it cause havoc on Gpay and other apps so once installed it should be uninstalled.
TLDR
Yes all of them
Click to expand...
Click to collapse

HW898 said:
Hmm safetynet fix seems to fail, can't pass cts profile.. any step by step guides by any chance?
Click to expand...
Click to collapse
That's where magisk hide props comes in. I don't have a full guide that I know of but I could do a quick wtite up tomorrow for you

deathblade said:
That's where magisk hide props comes in. I don't have a full guide that I know of but I could do a quick wtite up tomorrow for you
Click to expand...
Click to collapse
I got it working after following a guide~
Unfortunately features like now playing isn't working. the rest is pretty much okay tho

HW898 said:
I got it working after following a guide~
Unfortunately features like now playing isn't working. the rest is pretty much okay tho
Click to expand...
Click to collapse
You install the pixelify module? Also can you explain how it's not working?

deathblade said:
You install the pixelify module? Also can you explain how it's not working?
Click to expand...
Click to collapse
Nope, I didn't. Other than the modules to hide from banking apps as mentioned above, I installed a pixel launch module here to make it for pixel-like: https://forum.xda-developers.com/t/app-mod-pixel-launcher.4442077/
Other than that nothing else.
It doesn't;t work in the sense that it does not pick up music, even popular ones. The settings are there though, I can see them. It just doesn't identify any songs

HW898 said:
Nope, I didn't. Other than the modules to hide from banking apps as mentioned above, I installed a pixel launch module here to make it for pixel-like: https://forum.xda-developers.com/t/app-mod-pixel-launcher.4442077/
Other than that nothing else.
It doesn't;t work in the sense that it does not pick up music, even popular ones. The settings are there though, I can see them. It just doesn't identify any songs
Click to expand...
Click to collapse
This is the pixelify module I installed then removed, you can give it a try.
GitHub - Kingsman44/Pixelify: Magisk module to enables pixel exclusive features and ui
Magisk module to enables pixel exclusive features and ui - GitHub - Kingsman44/Pixelify: Magisk module to enables pixel exclusive features and ui
github.com

Question [Issue] Google pay (Wallet) does not work with oxygen 13 (LE2121 Model)

Hello guys,
I just upgraded from oxygen 12 to 13 last week.
Since than, google pay does not work for me. It used to work perfectly with oxygen 12.
As i have mentioned at title, my one plus 9 pro model is LE2121, im quite sure its related to this.
I've looked for a solution for this here and also in other forums, but i cannot find one at the moment.
Hard reset is my last option .
Does anyone facing this issue and managed to solve it?
Many thanks.

I'm using GPay and all banking apps on rooted LE2121. This is what I did.
Installed Safetynet Fix and Shamiko modules
Configured Zygisk & Denylist
Turned OFF "enforce denylist" (according to Shamiko instructions)
Renamed Magisk to something else (look in Magisk settings)
See if that works for you.

tathagatab said:
I'm using GPay and all banking apps on rooted LE2121. This is what I did.
Installed Safetynet Fix and Shamiko modules
Configured Zygisk & Denylist
Turned OFF "enforce denylist" (according to Shamiko instructions)
Renamed Magisk to something else (look in Magisk settings)
See if that works for you.
Click to expand...
Click to collapse
This was working for A12.
For A13 it's a different story and a solution is to remove the Work profile or any cloned apps.

RASTAVIPER said:
This was working for A12.
For A13 it's a different story and a solution is to remove the Work profile or any cloned apps.
Click to expand...
Click to collapse
It works for me on OOS 13. Maybe because I have only one profile and zero cloned apps.

More information here:
OnePlus Community
Introducing our new OnePlus Community experience, with a completely revamped structure, built from the ground-up.
community.oneplus.com

Had this one. Via ADB I had to delete second profile which was created when I cloned WhatsApp.

Google Wallet/payments doesnt work with cloned apps enabled. its many times reported bug and still is here in stable. same problem was in upgrade from 11 to 12.

In FAQ OnePlus stated they fixed it. But still in Stable the issue persists.

l_mike said:
In FAQ OnePlus stated they fixed it. But still in Stable the issue persists.
Click to expand...
Click to collapse
yes, because promises of new 1+ are trash. is not fixed on stable F.16.

l_mike said:
Had this one. Via ADB I had to delete second profile which was created when I cloned WhatsApp.
Click to expand...
Click to collapse
There is no way I delete my second whatsapp profile just to get this upgrade.
First they need to solve such important bug.

Hello all,
thanks for all the replies.
What fixed the issue for me was to make hard reset.
Luckly, its very easy on one plus with the google cloud backup and restore method.
So i made it, and everything works fine. (Had also few bugs that where fixed also.. on the way..).
Also, Gpay works in my galaxy wacth 4!! with oxygen 12 i couldn't use it!
After all, happy ending!

davidz85 said:
Hello all,
thanks for all the replies.
What fixed the issue for me was to make hard reset.
Luckly, its very easy on one plus with the google cloud backup and restore method.
So i made it, and everything works fine. (Had also few bugs that where fixed also.. on the way..).
Also, Gpay works in my galaxy wacth 4!! with oxygen 12 i couldn't use it!
After all, happy ending!
Click to expand...
Click to collapse
nice, but for other people who use xy apps hard reset isnt easy. for me is "5 days settuping.." its main bug with cloned apps. you just delete 999 user with hard reset.

How To Guide A Complete Guide to Unlocking and Flashing for the A52s 5G.

Disclaimer
Your warranty will be void
Some carriers' Terms of Service prohibit device modifications
Modifying will trip Samsung Knox and SafetyNet, so be aware that some apps will cease to work
I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FAILED ATTEMPTS AND OTHER CAUSES OF IMPROPER USAGE OF THIS GUIDE!Now that we got that out of the way, we can continue.
Unlocking the BootloaderUNLOCKING THE BOOTLOADER WILL ERASE ALL OF YOUR DATA!
Go into Settings > About Phone > Software Information
Find Build Number and quickly tap it 7 times. This will enable Developer Options
Find OEM Unlocking and USB Debugging options and enable them
Turn off the phone
Hold Volume Up and Volume Down while connecting your phone to a PC to boot into Download Mode
Read the Warning carefully to understand it and then if you want to continue press Volume Up
On the Unlock Bootloader screen, press and hold the Volume Up button one more time (This is the step that erases all of your data, if you don't want to do it, now is the time to turn back!)
After the automatic reboot, repeat steps 1. - 3. and make sure that OEM Unlocking is greyed out and enabled
Congratulations! You bootloader is now unlocked.
Flashing a Custom RecoveryCredit to @BlackMesa123 for this guide.
Rooting your Phone
Download the latest version of Magisk on your Computer
Follow the Official Installation Guide from Magisk developers
Flashing a GSI (Generic System Image)
Choose a GSI from this List
Power Off your phone and connect it to your Computer
Hold Volume Up and Power buttons, after the logo appears, release only the Power button, this will boot you into TWRP
Do a Wipe and transfer the GSI file from you Computer to your Phone
Click Install >Image Flashing, find your transferred GSI file and tap on it.
Toggle the System Image option and flash the file.
After flashing Format Data to be able to boot into your new System.
I know your Camera doesn't work, don't worry check out this Post to get it to work again.
Useful Resources
A52s bootloader/modem collection repository
OrangeFox Recovery
SafetyNet Fix for Magisk (Zygisk)
Custom ROMs: RayOS (One UI 4.1), NcX (One UI 5.0)
Mesa's Custom Kernel
Credit to @BlackMesa123 @Ryzen5950XT @ShaDisNX255 for the additional resources.
That's it! Thank you for following the guide and enjoy your unlocked Samsung.

This is very helpful thanks

Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.

BlackMesa123 said:
Thank you for the guide. Here's some additional resources/changes that can be added in the post:
- A52s bootloader/modem collection repository
- OrangeFox Custom Recovery, same as TWRP but with a different UI
- SafetyNet and (some) Knox features can still work with the correct adjustments. See the SafetyNet fix for Magisk (Zygisk) or custom ROM's such as RayOS (One UI 4.1), NcX (One UI 5.0)
- Mesa's Custom Kernel, greatly improves device's performance
Hoping to see the list enhanced soon.
Click to expand...
Click to collapse
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?

kzyx said:
Thank you for the links, thread is now updated.
Quick question, with MCK, should I wipe everything before/after flashing and will it work with PE+ GSI?
Click to expand...
Click to collapse
You shouldn’t wipe anything when flashing the kernel. If the stock kernel works fine, I don’t see why mine shouldn’t

Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.

Mian-786 said:
Everything is working perfectly, thanks for the guide. I installed the PixelExperience GSI but for some reason Fingerprint sensor is not working. The process is stuck on "Touch the sensor" and the sensor is not lighting up. Yes, I set the color of fingerprint sensor to White (and even tried all other colors).
I even have the following options checked
- Enable Extra Sensor
- Enable workaround for broken fingerprint sensor
- Enable workaround for white-ish screen
Any help will be appreciated, thanks.
Click to expand...
Click to collapse
I don't know what could be the issue, maybe try to google or try disabling and enabling the fingerprint lock again.

I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.

Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.

kzyx said:
Thanks for the feedback, have you tried any ROMs instead of GSIs?
You have links for them in this thread.
Click to expand...
Click to collapse
Nope, I tried to find a good custom rom for A52s but couldn't find any.

What about volte and hotspot on GSI pixel experience 13?

Mian-786 said:
I have tried few GSI Roms. Here is my summary:
Android 13
- AOSP, Android 13, No image with GAPPs pre-installed and cannot seem to install it. Tried NikGAPPs, and LiteGAPPs, both didn't work
- Google GSI, Android 13, same issue
- Pixel Experience, Android 13, GAPPs pre-installed but Fingerprint sensor won't get detected.
Android 12
- AOSP, Android 12, GAPPs pre-installed, Fingerprint sensor detected (changing color to white). Will stick to it unless there is an issue detected.
Click to expand...
Click to collapse
Thanks for your summary,
Is there any experience with MicroG on this device with AOSP 13?

7slaper said:
Thanks for your summary,
I'm on AOSP 13 now, but perhabs it's better to go back to 12. I'm very interested in the AOSP with the GAPPs pre-installed. Could you share a link to the file?
Click to expand...
Click to collapse
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.

Zhazhael said:
What about volte and hotspot on GSI pixel experience 13?
Click to expand...
Click to collapse
I think VoLTE was available as an option in one of the ROM I tested but I don't remember exactly. Currently AOSP 12 doesn't support it. Hotspot worked on every ROM just fine.

Mian-786 said:
I got the image from AOSP under the official Android 12/12L section. You can find release here. The exact image I got is the system-squeak-arm64-ab-vndklite-gapps-secure.img.xz one since the standard gapps one came with an app called "superuser" which I couldn't seem to uninstall (I tried the scripts to remove supersu). This caused my banking apps to not run. That is why I installed the "secure" one and then installed Magisk and added my banking apps to the defylist.
Click to expand...
Click to collapse
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.

7slaper said:
Hi Mian,
Thanks for your response. When I typed my question I realized that in the end I want to have and de-googled phone. So I changed my question in the direction of MicroG. I didn't expect you to be so quick with answering.
Click to expand...
Click to collapse
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.

Thx, all worked.

Mian-786 said:
I haven't tried MicroG in any of the ROM. I just to have as little Google apps as possible but if you do find a good guide, let me know, I will try to use a de-googled phone.
Click to expand...
Click to collapse
I've installed MicroG. But it seems AOSP doen't allaw support system spoofs signature. Play services (GmsCore) is installed but without the spoofed signature it can't do much I guess...

I have been using AOSP Android 12 for the past week or so. Most of the things just plain works but somethings don't. Here is the list of things that are not working so you can decide if the hassle of installing GSI is worth it or not.
- Proximity Sensor is worse than it was in OneUI. Yes, it is a virtual sensor but on OneUI, it worked better. Now, it is worse. More often than not, it turns on the screen during the call. It would have been better if it simply didn't work.
- The viewport of default camera App in the AOSP displays picture in 4:3 but the camera hardware is giving out 16:9, so the viewport was squeezed. After installing GCam everything is good.
- Fingerprint Sensor simply doesn't work in-app like those in banking apps. It works on the lock screen but nowhere else.
- USB Audio Devices don't work. I have a USB-C to A OTG where I used to insert my headphones. On OneUI they used to work but here they don't. Storage devices work.
- 120 Hz felt smoother on OneUI.

Hello everyone
I managed to install LineageOS with working GApps and camera using this guide, so a big thanks to everyone who worked on flashing this phone
If anyone wants to install it, you need to:
Chose a bgN package (I installed this one : https://sourceforge.net/projects/an...UNOFFICIAL-arm64_bgN-vndklite.img.xz/download). It includes the GApps. You won't be able to install GApps after installing a vanilla (bvS / bvN) package. For some reasons, the /system partition is too small.
For unlocking camera and install magisk, just flash this kernel : https://forum.xda-developers.com/t/kernel-12-13-a528b-n-mesas-custom-kernel-r4.4490653/
I also installed magiskhide prop conf module, but I'm not sure it changed anything and the camera fix was probably already in the MCK. You can find it here anyway : https://forum.xda-developers.com/t/...safetynet-prop-edits-and-more-v6-1-2.3789228/

Develop Bugs

welcome