[MAGISK] Ambient EQ Tweak (Flame) - Google Pixel 4 XL Themes, Apps, and Mods

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.

Related

Xposed and Safety Net Pass -- How To!

XPOSED and Safety Net PASS -- Instructions How To
I've been using Xposed because it has functionality that I don't want to give up. But "regular" Xposed won't pass Safety Net.
Thanks to @drewcu, I now have found a way to use Xposed and PASS Safety Net.
This is important enough it deserves its own Guide thread. All credit goes to @drewcu -- and of course the edXposed devs! Go here and THANK this post. Full exchange is below, but please go thank @drewcu in that post.
_______
drewcu said:
Installed Magisk and edXposed and all is well.
Thanks!
Click to expand...
Click to collapse
ChazzMatt said:
First hearing about "edXposed". Quick Google search, sounds interesting, and some say it allows you to pass Safety Net, which regular Xposed (I use) doesn't. Is that true?
Which Magisk version are you installing with that?
Click to expand...
Click to collapse
drewcu said:
Latest Magisk 19.3.
YES, EdXposed absolutely passes Safetynet (both ctsProfile and basicIntegrity)! Install instructions here: https://github.com/ElderDrivers/EdXposed but see below for the specific EdXposed version I recommend using.
I personally use magisk-EdXposed-sandhook-v0.4.0.1_beta-SNAPSHOT-release.zip found https://www.lanzous.com/b642738. Newer Sandhook versions with resource hooking like v0.4.1.2_beta and v0.4.2.3_alpha (and the YAHFA versions too) found https://github.com/ElderDrivers/EdXposed/releases introduce some LAG for me that isn't present on 0.4.0.1. Haven't tried newer ALPHA versions like 0.4.3.7 but you are welcome to see if you experience the same lag. Would have to separately install both versions, start opening apps, clicking around, and counting time till the V30 responds to see the lag I am referring to. Is subtle but most noticeable in 0.4.1.2 and less so in 0.4.2.3.
The only Xposed module I use is GravityBox(O) and there is a version specifically for EdXposed -- 8.5.3.1-edxposed (https://github.com/GravityBox/GravityBox/releases/tag/v8.5.3.1-edxposed_o), although I updated to general version 8.5.4 (https://forum.xda-developers.com/xposed/modules/app-gravitybox-v8-0-0-beta-1-tweak-box-t3739929) and have no resource hooking problems with 0.4.0.1 like I thought there might be and had with general version 8.5.3. If you use any OTHER Xposed modules that require resource hooking, you will need to use an EdXposed version 0.4.1.2 or above which has resource hooking but also possibly some lag (perhaps none in the latest alpha I don't know).
So I stay on magisk-EdXposed-sandhook-v0.4.0.1_beta-SNAPSHOT-release because it works with the latest version of GravityBox no problem, has 0 lag unlike newer versions (I think an Oreo problem), and passes Safetynet just fine.
Not sure if some of the steps I took after reading a forum about Safetynet were necessary but I did them anyway -- namely:
1) EdXP Settings - Enable Black/White List
2) Black List Google Play Services and Google Play Store
3) Magisk Hide - ALL of Google Play Services
Enjoy!
Click to expand...
Click to collapse
TotallyAnxious said:
Thanks. I've been meaning to check out the new Xposed offshoots.
Click to expand...
Click to collapse
_________
@drewcu:
edXposed INSTRUCTIONS
Install instructions here: https://github.com/ElderDrivers/EdXposed but see below for the specific EdXposed version I recommend using.
I personally use magisk-EdXposed-sandhook-v0.4.0.1_beta-SNAPSHOT-release.zip found https://www.lanzous.com/b642738. Newer Sandhook versions with resource hooking like v0.4.1.2_beta and v0.4.2.3_alpha (and the YAHFA versions too) found https://github.com/ElderDrivers/EdXposed/releases introduce some LAG for me that isn't present on 0.4.0.1. Haven't tried newer ALPHA versions like 0.4.3.7 but you are welcome to see if you experience the same lag. Would have to separately install both versions, start opening apps, clicking around, and counting time till the V30 responds to see the lag I am referring to. Is subtle but most noticeable in 0.4.1.2 and less so in 0.4.2.3.
The only Xposed module I use is GravityBox(O) and there is a version specifically for EdXposed -- 8.5.3.1-edxposed (https://github.com/GravityBox/GravityBox/releases/tag/v8.5.3.1-edxposed_o), although I updated to general version 8.5.4 (https://forum.xda-developers.com/xposed/modules/app-gravitybox-v8-0-0-beta-1-tweak-box-t3739929) and have no resource hooking problems with 0.4.0.1 like I thought there might be and had with general version 8.5.3. If you use any OTHER Xposed modules that require resource hooking, you will need to use an EdXposed version 0.4.1.2 or above which has resource hooking but also possibly some lag (perhaps none in the latest alpha I don't know).
So I stay on magisk-EdXposed-sandhook-v0.4.0.1_beta-SNAPSHOT-release because it works with the latest version of GravityBox no problem, has 0 lag unlike newer versions (I think an Oreo problem), and passes Safetynet just fine.
Not sure if some of the steps I took after reading a forum about Safetynet were necessary but I did them anyway -- namely:
1) EdXP Settings - Enable Black/White List
2) Black List Google Play Services and Google Play Store
3) Magisk Hide - ALL of Google Play Services
Enjoy!
When I go to download the file, it's in, I assume, Chinese characters.
Any help.
Never mind, figured it out.
This is great. I'm so happy to have Gravity Box again.
I too had a problem with lag with newer versions of edxposed. I switched to the version recommend in the OP and all is well.
If you comfortable using "chinese" app. Taichi is simpler solution (personally), although not much modules currently supported. Both edxposed and taichi are available on magisk repo
Thanks @ChazzMatt, finally got around to installing Xposed again. Thank god for GravityBox!
edit: after playing around for a day, I'm disabling edx. I'm getting lag, force closes, unresponsive back button, and major battery drain. Sad to see the framework hasn't changed much in 1-2 years. It's not worth it for a single Xposed module.
Gravitybox system framework not respondinhlg.
On us996k
Guess I'm missing something?
qwas7899 said:
Gravitybox system framework not respondinhlg.
On us996k
Guess I'm missing something?
Click to expand...
Click to collapse
Edit; figured it out
qwas7899 said:
Edit; figured it out
Click to expand...
Click to collapse
share with the class.
Right. Didn't have riru-core module installed.
Thanks a lot for this guide . It's great to have xposed and safety net passing.
soo I tried to install edxposed sandhook (latest version), after a couple reboot, all went fine, but now I lost wifi and data connection (they cant be turned on), any ideas or fix? is it linked to that version of edxposed? I have a Lg ls998 converted to Us998h, thank you
LeTerrible said:
Just wanted to share my experience with NFC banking and FullHD working Netflix. Managed to delete everything google and installed Microg only (to get Gcam to work), my banking app, Netflix app, Canary EdXposed and it works flawlessly! Could never get FullHD and NFC banking to work previously with Xposed. Of note was the fact I am running Xprivacy, too. Just make sure you blacklist the apps in EdXposed and also hide them in Magisk and it all works
Hope this helps others as it really made my NoGapps/Rooted stock phone experiences significantly better.
Click to expand...
Click to collapse
Great.
I'm having trouble getting EdXposed to activate. I'm on a fresh clean install of the TWRP flashable version of US998 30b with Magisk 20.1 installed and working, and while i've got the Riru - Core module installed (v19.5), no matter which Riru - Ed Xposed module I use I get the following error message from EdXposed Manager 4.5.2 explaining why it's installed but not activated:
There seems to be a known issue("Wrong base directory: /mnt/expand/7f941a12-b7aa-4d2a-a664-f89a46b7d86c/user_de/0/org.meowcat.edxposed.manager") with your ROM.
Suggestions on where I go from here?
radwolf76 said:
I'm having trouble getting EdXposed to activate. I'm on a fresh clean install of the TWRP flashable version of US998 30b with Magisk 20.1 installed and working, and while i've got the Riru - Core module installed (v19.5), no matter which Riru - Ed Xposed module I use I get the following error message from EdXposed Manager 4.5.2 explaining why it's installed but not activated:
There seems to be a known issue("Wrong base directory: /mnt/expand/7f941a12-b7aa-4d2a-a664-f89a46b7d86c/user_de/0/org.meowcat.edxposed.manager") with your ROM.
Suggestions on where I go from here?
Click to expand...
Click to collapse
Solution Found. My EdXposed Manager had been installed to External Storage. It only works on Internal Storage.
Safety Net Fail w/ Gravitybox
It looks like as soon as I enable the Gravitybox module that you recommend, safetynet fails. Are you still passing with your setup (I'm wondering if there has been some update that this version of Gravitybox no longer passes)?
UPDATE: even though safetynet shows up as failing in Magisk, I am still able to use Google Pay, so maybe it is working? I'll update this post once I've tried using Google Pay to pay for something.
UPDATE again: after a couple of days, Google Pay showed a pop up message saying that it would no longer work. Uninstalling and reinstalling gets it working temporarily again it seems.
Dear @ChazzMatt
Should I install the old beta in the last page or the latest canary to avoid safety net and which versions is the best?
Note to everyone: installing xposed framework will trigger safetynet....and uninstalling it will do as well
And i don't know how to solve this except flashing a new rom

Magisk Module to Change QS Pulldown back to 9 Tiles

For stock only. This is built-into my clock mods and ADB bases.
Android 12
Uploaded 2-13-22
February update
9tiles.zip | by Tulsadiver for Pixel
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
------------------------------------------------------
Android 11
Uploaded 7-1-21
Stock
9tiles.zip | by Tulsadiver for Pixel
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Active Edge Sense
9tilesedge.zip | by Tulsadiver for Pixel
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
-------------------------------------------------
If I helped, hit the Thanks Button!
Feeling generous, send me a beer!
--------------------------------------------------
I don't understand which of those to use. Do they do more than just change to 9 quick-settings tiles?
How is it related to active-edge?
AndroidDeveloperLB said:
I don't understand which of those to use. Do they do more than just change to 9 quick-settings tiles?
How is it related to active-edge?
Click to expand...
Click to collapse
If you are using Active Edge module/app you will need to delete the Active Edge module and flash this in it's place. It's ported from the Active Edge SystemUI and has both mods. The op of Active Edge gave me permission to do this.
Edit: op has been updated to explain differences.
Will the active edge mod require an update after every monthly security update? Thanks
Sent from my Pixel 4 XL using Tapatalk
Hey is this the same mod you posted in the status bar icon notification max 7 mod with 9 tiles or is this another mod?
Nice, but also curious to see what it looks like in landscape with the music player being there. ?
Tulsadiver said:
If you are using Active Edge module/app you will need to delete the Active Edge module and flash this in it's place. It's ported from the Active Edge SystemUI and has both mods. The op of Active Edge gave me permission to do this.
Edit: op has been updated to explain differences.
Click to expand...
Click to collapse
Sadly Active Edge doesn't work for me even without this one...
If this is a module too, how about publishing it on the Magisk modules list?
Zilla0617 said:
Will the active edge mod require an update after every monthly security update? Thanks
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Not always, but i update them if he does.
Jiggs82 said:
Hey is this the same mod you posted in the status bar icon notification max 7 mod with 9 tiles or is this another mod?
Click to expand...
Click to collapse
This just has 9 tiles.
AndroidDeveloperLB said:
Sadly Active Edge doesn't work for me even without this one...
If this is a module too, how about publishing it on the Magisk modules list?
Click to expand...
Click to collapse
No need to. This is firmware specific.
Tulsadiver said:
No need to. This is firmware specific.
Click to expand...
Click to collapse
There are modules that are firmware specific...
According to what you wrote, this means that (suppose active edge module works) if I want to use active edge module , I actually have to remove it, and use yours instead, under "Stock Active Edge" , right?
How can I be up-to-date with it now?
Before, we had the active-edge module on Magisk, so it could get updated there.
AndroidDeveloperLB said:
There are modules that are firmware specific...
According to what you wrote, this means that (suppose active edge module works) if I want to use active edge module , I actually have to remove it, and use yours instead, under "Stock Active Edge" , right?
How can I be up-to-date with it now?
Before, we had the active-edge module on Magisk, so it could get updated there.
Click to expand...
Click to collapse
You'd have to come back here for updated modules.
Tulsadiver said:
You'd have to come back here for updated modules.
Click to expand...
Click to collapse
Too bad.
Seems that the module works, but only if the media control is hidden.
Appreciate your work, but why did you do a Magisk module? It would be much more better if you decided to do an Xposed module, because then people could use more another mods that modify this part of system without have to replace files. Xposed is much more efficient, because it doesn't replace system files, but calls.
Senliast said:
Appreciate your work, but why did you do a Magisk module? It would be much more better if you decided to do an Xposed module, because then people could use more another mods that modify this part of system without have to replace files. Xposed is much more efficient, because it doesn't replace system files, but calls.
Click to expand...
Click to collapse
This is a really strange thing to say to a guy who has Magisk modules all over this section and no Xposed modules at all anywhere. It simply appears that he makes Magisk modules and doesn't make Xposed modules. Obviously, Magisk has a huge number more users than Xposed, so the idea that Magisk would be better is definitely not true to anyone who is not an Xposed user. Efficiency is probably less important than accessibility, as a mod is useless to one who cannot use it with their setup.
Senliast said:
Appreciate your work, but why did you do a Magisk module? It would be much more better if you decided to do an Xposed module, because then people could use more another mods that modify this part of system without have to replace files. Xposed is much more efficient, because it doesn't replace system files, but calls.
Click to expand...
Click to collapse
The vast majority of devs on here specifically call out Xposed, kernels and scripts ( in that order) as voiding the right to ask for help troubleshooting issues. While the last two seem to get a pass from many folks, Xposed almost always is requested to be uninstalled before folks will dedicate any time to help with a problem. Maybe unfair but it's always explained up front. For this reason I for one and I'm sure many other users just don't get into using it. As mentioned above, magisk has a much larger use base.
@Tulsadiver Awesome mod. I installed it my 4a. I was really cautious and disabled the Magisk Props module and rebooted before installing 9tiles because I was afraid that if I didn't the install would download the SystemUIGoogle apk for the Pixel 3a which I had set in Props module Force Basic attestation to pass CTS. My question is, did I need to be this cautious? Does your 9tiles installer look only at device fingerprint to identify the model and monthly patch version, or would these spoofed props in the screenshot make your installer download the 3a system ui?
Thanks
buffal0b1ll said:
@Tulsadiver Awesome mod. I installed it my 4a. I was really cautious and disabled the Magisk Props module and rebooted before installing 9tiles because I was afraid that if I didn't the install would download the SystemUIGoogle apk for the Pixel 3a which I had set in Props module Force Basic attestation to pass CTS. My question is, did I need to be this cautious? Does your 9tiles installer look only at device fingerprint to identify the model and monthly patch version, or would these spoofed props in the screenshot make your installer download the 3a system ui?
Thanks
Click to expand...
Click to collapse
This mod just contains the files for the Pixel 4 XL though I understand your caution. I believe Active Edge's module pulls a file bases on the build prop. Mine is not so sophisticated.
Edit: I see now where you said you had the Pixel 4a. I ran a quick mod for you that is Pixel 4a specific.
Tulsadiver said:
This mod just contains the files for the Pixel 4 XL though I understand your caution. I believe Active Edge's module pulls a file bases on the build prop. Mine is not so sophisticated.
Edit: I see now where you said you had the Pixel 4a. I ran a quick mod for you that is Pixel 4a specific.
Click to expand...
Click to collapse
Thanks for the reply. So my 4a is running fine on a modded 4XL SystemUIGoogle.apk? Wow. I wonder if this is going to keep working moving forward on new monthly patches.
Tulsadiver said:
This mod just contains the files for the Pixel 4 XL though I understand your caution. I believe Active Edge's module pulls a file bases on the build prop. Mine is not so sophisticated.
Edit: I see now where you said you had the Pixel 4a. I ran a quick mod for you that is Pixel 4a specific.
Click to expand...
Click to collapse
Thanks for the 4a specific zip.
FYI this is where I found out about this mod and nowhere in the article does it even mention the 4xl. That's why I originally thought you were curling down device specific apks like Janny. https://android.gadgethacks.com/how-to/bring-back-9-tile-grid-android-11s-quick-settings-0340584/
Other Pixel 3 and 2 users might not be so lucky if they install as I was on 4a.

ROM ❯ PIXEL 2 XL ❯ OFFICIAL ❯ ProtonAOSP 11

ProtonAOSP
Android 11 ROM​
ProtonAOSP is a minimal Android fork (custom ROM) focused on UI/UX and performance, with a touch of privacy.
Screenshots
Screenshots of the latest version
Installation
This ROM is currently distributed as factory images, similar to stock. Flash it the same way you would flash stock factory images. Don't forget to wipe all data using "fastboot -w" before booting the ROM.
Firmware is included, so there is no specific requirement for which version of the stock ROM you are coming from.
You can also use the quick & easy web installer, which allows you to install and update the ROM from any computer or phone without using the command line. The installer works entirely within your web browser and completes in as little as 4 minutes, depending on the speed of your internet connection. Consider using the web installer instead of installing manually.
More detailed installation instructions and guides
Features
List of current features, with accompanying screenshots and explanations
Downloads
Downloads and changelogs for all versions
Builds with and without minimal Google services (gapps) included are provided for convenience.
Using the quick and easy web installer is recommended unless you have a specific reason to download and install the ROM manually.
Support
If you have questions or concerns, please read the Frequently Asked Questions before asking. It saves time for everyone involved, especially you, and allows us to provide higher-quality answers for all users.
Website with comprehensive documentation
Join the Telegram group for support and extras
Please consider donating to support development if you found this helpful: recurring donation to keep the project alive in the long term or buy me a coffee
Kernel source code
ROM source code
Looks so tempting, downloading as I type.
Quick check - for the updates in future, would we still need to wipe data before booting if already in the previous ProtonAOSP version .
Thank you for bringing love to our pixel series !
Love to know what you have changed to alter battery usage before i download it, every other 11 ROM drains like a bathtub, even at idle
According to the Pixel 5 thread this ROM passes safetynet w/o magisk. looks interesting. Downloading now!
componentchunk said:
According to the Pixel 5 thread this ROM passes safetynet w/o magisk. looks interesting. Downloading now!
Click to expand...
Click to collapse
It may be like the other new 11 based ROM that turned up on here yesterday, and have its device name set to Pixel 5/5a to pass SafetyNet out of the box
https://forum.xda-developers.com/showpost.php?p=83885115&postcount=12
Its not the way i would do it, but each to his own.
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
twiddles said:
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
Click to expand...
Click to collapse
fastboot flash boot boot.img (stock October). That booted it for me until he can update a fix. This ROM btw is phenomenal on battery life
twiddles said:
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
Click to expand...
Click to collapse
Same, I've tried flashing/sideloading from Lineage 17 and stock P/Q/R. Stuck on splash for 10+ mins before I force reboot into bootloader to retry each time
kdrag0n said:
ProtonAOSP • Pixel 2 XL
Click to expand...
Click to collapse
Hello. Proton is incredible. Very fast, smooth and tenacious. Tested it from the first version. Thank you very much. I want to clarify something else for myself: Do I need to flash in both slots if a stock is installed?
palimatix said:
Looks so tempting, downloading as I type.
Quick check - for the updates in future, would we still need to wipe data before booting if already in the previous ProtonAOSP version .
Thank you for bringing love to our pixel series !
Click to expand...
Click to collapse
No, you only need to wipe data if switching from another ROM.
73sydney said:
Love to know what you have changed to alter battery usage before i download it, every other 11 ROM drains like a bathtub, even at idle
Click to expand...
Click to collapse
I didn't do anything specific for battery; it's just that battery tends to be better on custom ROMs than it is on Pixel 2 stock, partially due to being less bloated.
73sydney said:
It may be like the other new 11 based ROM that turned up on here yesterday, and have its device name set to Pixel 5/5a to pass SafetyNet out of the box
https://forum.xda-developers.com/showpost.php?p=83885115&postcount=12
Its not the way i would do it, but each to his own.
Click to expand...
Click to collapse
My ROM reports a fake security patch level to SafetyNet so basic attestation will always pass. However, I've observed that Google has started to roll out hardware attestation for the Pixel 2, so I also modified the model name with an invisible character to revert it back to basic. The Pixel 5 name is not used.
twiddles said:
Not booting for me. Stuck on splash screen. Clean flash of proton-aosp_taimen_11.2.0-gapps.zip on twrp-3.4.0-1-taimen then wipe data before reboot.
Click to expand...
Click to collapse
componentchunk said:
Same, I've tried flashing/sideloading from Lineage 17 and stock P/Q/R. Stuck on splash for 10+ mins before I force reboot into bootloader to retry each time
Click to expand...
Click to collapse
Sorry for the inconvenience, the problem lies in a botched SafetyNet fix that was missed in testing due to not flashing all partitions. You can make it boot temporarily by flashing the stock boot image. A hotfix that boots out-of-the-box will be up shortly.
pablo9023 said:
Hello. Proton is incredible. Very fast, smooth and tenacious. Thank you very much. I want to clarify something else for myself: I tested it from the first version. Do I need to flash in both slots if a stock is installed?
Click to expand...
Click to collapse
No, ideally the latest stock ROM would be installed in both slots beforehand but that's only because this build is missing firmware. A hotfix will be up shortly with the latest firmware included.
Nice, got gpay working with magisk.
Unfortunately stuck on splash after installing edxposed. This is definitely an unreasonable request but if xposed edge features could be built natively into the rom I wouldn't need xposed
componentchunk said:
Nice, got gpay working with magisk.
Unfortunately stuck on splash after installing edxposed. This is definitely an unreasonable request but if xposed edge features could be built natively into the rom I wouldn't need xposed
Click to expand...
Click to collapse
Xposed will never be supported, you are on your own if it's broken. I wouldn't recommend using it because it can cause all sorts of weird bugs.
A hotfix update has just been released to fix issues with a botched SafetyNet fix that caused most apps using HTTP outside of a browser to break, including Google Translate, SMS/MMS, and many others. I've figured out a new way to fix SafetyNet that doesn't come with those pitfalls, so SafetyNet is still passing out-of-the-box and apps will no longer break. A bug with sensitivity in the Active Edge settings has also been fixed, and missing firmware has been re-added so there is no need to flash the latest stock ROM first.
Re-download v11.2.0 from GitHub for the fixes. I've decided to re-upload it rather than bumping the version because the previous SafetyNet fix was very broken and also caused boot failures if boot.img wasn't replaced.
kdrag0n said:
A hotfix update has just been released to fix issues with a botched SafetyNet fix that caused most apps using HTTP outside of a browser to break, including Google Translate, SMS/MMS, and many others. I've figured out a new way to fix SafetyNet that doesn't come with those pitfalls, so SafetyNet is still passing out-of-the-box and apps will no longer break. A bug with sensitivity in the Active Edge settings has also been fixed, and missing firmware has been re-added so there is no need to flash the latest stock ROM first.
Re-download v11.2.0 from GitHub for the fixes. I've decided to re-upload it rather than bumping the version because the previous SafetyNet fix was very broken and also caused boot failures if boot.img wasn't replaced.
Click to expand...
Click to collapse
Great work, and thank you for the fast updates. Really looking forward to using the ROM when I clean format next time. Waiting for Google to release the last Security patch in December before making the jump, don't want to clean install every month. I usually stick with a ROM for a few months at a time.
Just to clarify if anyone is confused: this is an Android 11 ROM, not Android 10. XDA DevDB has no option for 11 so I had to put 10. I've just edited the DevDB info out of the post now and added 11 to the header so there should be no more confusion.
I am testing proton, so far its fast, snappy, and stable, one word of caution for anyone who uses my recommendations. Do not patch the boot.img as I always recommended, this landed me in a bootloop. Once I wiped the device clean, and started over (installed ROM+GAPP), then setup the device, then once setup, reboot to BL/TWRP (ADB TWRP), and installed MAGISK zip version from within TWRP, it booted fine. It only has an issue if you patch the boot.img from within MAGISK itself then ADB the boot.img. Normally this is the only method I use, but it will not work properly with this ROM (which is perfectly fine as the zip works great and passes safetynet out of the box)!
This ROM doesnt have all the goodies I am used to, BUT its a VERY decent, and stable 11 ROM so I DO recommend users to at least try it if you are looking for a decent 11 ROM. Battery life for me is on par with 10 so I do not see any major show stoppers using this as a DD. I will run it for a few days and report anything found (if anything is found), otherwise, its great.
GROOVYJOSHCLARK said:
I am testing proton, so far its fast, snappy, and stable, one word of caution for anyone who uses my recommendations. Do not patch the boot.img as I always recommended, this landed me in a bootloop. Once I wiped the device clean, and started over (installed ROM+GAPP), then setup the device, then once setup, reboot to BL/TWRP (ADB TWRP), and installed MAGISK zip version from within TWRP, it booted fine. It only has an issue if you patch the boot.img from within MAGISK itself then ADB the boot.img. Normally this is the only method I use, but it will not work properly with this ROM (which is perfectly fine as the zip works great and passes safetynet out of the box)!
This ROM doesnt have all the goodies I am used to, BUT its a VERY decent, and stable 11 ROM so I DO recommend users to at least try it if you are looking for a decent 11 ROM. Battery life for me is on par with 10 so I do not see any major show stoppers using this as a DD. I will run it for a few days and report anything found (if anything is found), otherwise, its great.
Click to expand...
Click to collapse
thank you very much for your assessment! I also find this rom to be very stable, snappy and the slight changes to the stock rom are very well thought out - next to perfect! big thanks to the dev krag0n!
I'm coming from an Android 9 Custom ROM and I wanted to switch to this, the instructions states that it should just be a simple flash. Should I still start from a clean reinstall of stock Android 11 or does flashing this come with that already?
kdrag0n said:
I didn't do anything specific for battery; it's just that battery tends to be better on custom ROMs than it is on Pixel 2 stock, partially due to being less bloated.
Click to expand...
Click to collapse
Stock has battery issues, all other 11 based ROMS ive tested have hadthe same battery issues. So i was asking in case you managed to find and fix the issue, because Google so far hasnt
I'll give it a crack anyways and see what its like, cheers
kdrag0n said:
My ROM reports a fake security patch level to SafetyNet so basic attestation will always pass. However, I've observed that Google has started to roll out hardware attestation for the Pixel 2, so I also modified the model name with an invisible character to revert it back to basic. The Pixel 5 name is not used.
Click to expand...
Click to collapse
fwiw, there is no evidence that Google has or plans to force hardware attestation on Pixel 2/XL. i monitor reports of these things over in the magisk threads, and as part of my own magisk module, and theres no suggestion it will happen to Pixel 2/XL, more likely it will happen with 4+ than the old Pixel 2/XL....
Ill probably change the fingerprint back to Pixel 2/XL and Android 11, personally i dont see the point of spoofing another device when the Pixel 2/XL is still officially supported...just my opinion, no offence meant
73sydney said:
Stock has battery issues, all other 11 based ROMS ive tested have hadthe same battery issues. So i was asking in case you managed to find and fix the issue, because Google so far hasnt
I'll give it a crack anyways and see what its like, cheers
fwiw, there is no evidence that Google has or plans to force hardware attestation on Pixel 2/XL. i monitor reports of these things over in the magisk threads, and as part of my own magisk module, and theres no suggestion it will happen to Pixel 2/XL, more likely it will happen with 4+ than the old Pixel 2/XL....
Ill probably change the fingerprint back to Pixel 2/XL and Android 11, personally i dont see the point of spoofing another device when the Pixel 2/XL is still officially supported...just my opinion, no offence meant
Click to expand...
Click to collapse
My Pixel 2 XL has been getting hardware attestation in all of my tests recently if the model name is set to "Pixel 2 XL". It's possible that I'm being A/B tested and most users don't have this problem, but either way, I haven't been able to pass SafetyNet without changing the model name because of it.
Either way, I've added hacks into the system in my ROM to avoid spoofing the model name while still defying hardware attestation and passing SafetyNet despite being on a mismatching security patch level. I agree, I don't want to change the model name just to pass SafetyNet, so I've been coming up with other solutions to avoid doing that.

Question Netflix not working with root?

So I downloaded Netflix today on a rooter Poco F3 with Xiaomi.eu and it throws me a 5.2 error meaning that I can't watch any videos. I have tried a method with a magisk module called liboemencrypt disabler but it didn't help at all. Any help?
stavrosbin said:
So I downloaded Netflix today on a rooter Poco F3 with Xiaomi.eu and it throws me a 5.2 error meaning that I can't watch any videos. I have tried a method with a magisk module called liboemencrypt disabler but it didn't help at all. Any help?
Click to expand...
Click to collapse
ianmacd said:
Apps that use liboemcrypto.so to play content protected by DRM, such as Netflix and My5, will fail when playback is attempted on a rooted device.
The symptoms displayed by affected devices vary by brand and Android version. Some devices may display an obscure error message when you attempt playback. Others may just appear stuck loading the requested content.
This Magisk module fixes the problem by masking liboemcrypto.so with a zero byte replacement. Whilst the same effect could be achieved by simply deleting or renaming liboemcrypto.so with a root-enabled file manager, this has the disadvantage of altering your /system partition by writing to the file-system. The advantage of the Magisk method is that no actual changes are made to the device. The problematic file is merely concealed from the apps that attempt to use it.
To use the module, flash it in the Modules section of Magisk Manager and then reboot your device.
The module works when the library in question is located at either /system/lib/liboemcrypto.so or /system/vendor/lib/liboemcrypto.so. If your library is located elsewhere (or missing), this module will have no effect (but it's harmless to try it).
The module has been verified working on a Samsung Galaxy S9+ (SM-G965F/DS) running Magisk 16.x/17.x/18.x on a variery of ROMs, on a Samsung Tab S3 (SM-T820) running stock Android 8.0 and Magisk 16.x/17.x, and on a Samsung Tab S4 (SM-T830) running stock Android 8.1 and Magisk 17.x/18.x. It was created because a similar module on XDA did not work on my devices. It is being released by popular request, because a number of other users contacted me with the same complaint.
The module was integrated into the official Magisk module repository on 2018-06-27, and can therefore be directly downloaded from within the Magisk Manager app.
Please note that a consequence of using this module is that Widevine DRM will fall back to using L3 instead of L1. This means that Netflix will play all content in SD quality, regardless of your subscription type. Of course, without this module, you won't be able to play anything on a rooted device, so beggars can't be choosers.
Change log:
2020-12-20: v1.5
Updated for Magisk v21 template format.
2019-03-29: v1.4
Updated for Magisk v19 template format.
Issue a warning if installed on an S10e (G970F), S10 (G973F) or S10+ (G975F).
2018-12-06: v1.3
Added support for devices that have the library under either /system/lib64 or /system/vendor/lib64.
Added support for devices that have the library in multiple locations.
2018-07-22: v1.2
Added logic to install in only the appropriate library directory, rather than in both.
2018-05-29: v1.1
Added support for devices that have the library under /system/vendor/lib instead of /system/lib.
2018-04-23: v1.0
Initial release.
Click to expand...
Click to collapse
Here
Kenora_I said:
Here
Click to expand...
Click to collapse
cant you use magisk hide and then use netflix?
That dosent work lmao, because of widevine
Netflix dosent allow rooted devices to use it or smth with rooting messes up with the widevine drm so.
Kenora_I said:
Here
Click to expand...
Click to collapse
Oh so that means I am losing L1? Is there a way to dodge this somehow?
You lose L3 not L1 why this is an issue I'm not sure.
Im not well versed in DRM bypasses
stavrosbin said:
So I downloaded Netflix today on a rooter Poco F3 with Xiaomi.eu and it throws me a 5.2 error meaning that I can't watch any videos. I have tried a method with a magisk module called liboemencrypt disabler but it didn't help at all. Any help?
Click to expand...
Click to collapse
You messed EU rom with some doubtfully modification.
EU rom is full L1 level and NETFLIX compliant.
lolo9393 said:
You messed EU rom with some doubtfully modification.
EU rom is full L1 level and NETFLIX compliant.
Click to expand...
Click to collapse
Yeah I deleted Netflix and reinstalled it and everything works again.

[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

Categories

Resources