Update: NFC payments has been fixed in Los 17.1 (and probably in all other ROMs) so this module is no longer required.
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24
Click to expand...
Click to collapse
Havoc OS added it in the latest build (20202602) too I think in the future all ROMs will include the fix from NOS sources.
Thanks to NOS devs and to you guys! :good:
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24
Click to expand...
Click to collapse
Great! But... Where is the module?
mvalda01 said:
Great! But... Where is the module?
Click to expand...
Click to collapse
Lol!
I accidentally created a duplicate thread and the attachment was in the other thread.
I've now added to the OP.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24[/QUOTE
Hai bill,
I have problem with NFC. Now iam using Havoc OS 10 v3.3 QQ2A.200305.003.
So i just flash this patch via twrp for problem solving?
I use redwolf recovery, is it possible to flash this module? And do I have to install the magisk before or can I install this module without the magisk?
Click to expand...
Click to collapse
uutucherenz said:
BillGoss said:
As far as I know out of all the Android 10 roms only NOS and now (based on NOS) the two PE roms support NFC tap and pay using Google Pay.
I've created a Magisk module that adds the NFC files from these working roms which should make tap and pay work on other roms (I'm using it on Los 17.1).
The nice thing about Magisk modules is that they don't touch the system partition, they survive dirty flashing, and can easily be removed either with Magisk Manager or by deleting the relevant folder under /data/adb/modules
I've attached the module (flash it in TWRP; don't try to install it using Magisk Manager).
Note: requires Magisk 20.2 or later.
Thanks to @xyyx, @PlayFriik, and @Gaurav24[/QUOTE
Hai bill,
I have problem with NFC. Now iam using Havoc OS 10 v3.3 QQ2A.200305.003.
So i just flash this patch via twrp for problem solving?
I use redwolf recovery, is it possible to flash this module? And do I have to install the magisk before or can I install this module without the magisk?
Click to expand...
Click to collapse
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
BillGoss said:
uutucherenz said:
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Click to expand...
Click to collapse
Can you recommend a forum to discuss lineage on oneplus3 / 3T? And the link to download ROM Lineage OS?
Click to expand...
Click to collapse
uutucherenz said:
Can you recommend a forum to discuss lineage on oneplus3 / 3T? And the link to download ROM Lineage OS?
Click to expand...
Click to collapse
Check out the threads in https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development and make sure you read the first post (OP - original post) in the thread your interested in.
Sent from my OnePlus 3T using XDA Labs
BillGoss said:
uutucherenz said:
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Click to expand...
Click to collapse
Hai bill,
What are the steps to install this NFC patch fix? I tried to install it directly via redwolf recovery but failed, "error: 1" ...
Click to expand...
Click to collapse
uutucherenz said:
BillGoss said:
Hai bill,
What are the steps to install this NFC patch fix? I tried to install it directly via redwolf recovery but failed, "error: 1" ...
Click to expand...
Click to collapse
I've always flashed it using the TWRP mentioned in the OP of the Los 17.1 thread (aka SAR TWRP) https://forum.xda-developers.com/on...ageos-17-0-oneplus-3-3t-t3990061/post80652281
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
BillGoss said:
uutucherenz said:
Yes, you have to have Magisk installed and then flash this module.
Fyi, ROMs that are based on Los should no longer need this module because NFC is now fixed in Los.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
FWIW, definitely don't flash this on top of an LOS ROM; caused a bootloop for me that I couldn't get out of, had to clean wipe and start over. My own darn fault for not reading everything through the first time or making a backup first, just a warning for others :silly:
Click to expand...
Click to collapse
Joshmccullough said:
BillGoss said:
FWIW, definitely don't flash this on top of an LOS ROM; caused a bootloop for me that I couldn't get out of, had to clean wipe and start over. My own darn fault for not reading everything through the first time or making a backup first, just a warning for others :silly:
Click to expand...
Click to collapse
I've updated the OP to say that the module is no longer needed.
Sent from my OnePlus 3T using XDA Labs
Click to expand...
Click to collapse
Related
OnePlus seems to have enabled aptX codecs in the new OB5/14 for the OnePlus 3/T.
For those of you who don't want to wait until the stable release and also would rather not flash the open beta, @Chaosgod27 has extracted the related files for use in the stable release. These files can be placed within OOS 4.1.X to enable aptX mode. These files are different from the old aptX-enabling files that were broken in OOS since updating to 7.1.1.
Edit: It seems there's some issues with the stacks. Playback does use aptX, but music is playing at a slightly higher pitch and faster than it should be.
I've dug around through the files in the new open beta and found the files myself. It seems there were a few missing before. The issue with the raised pitch and fast playback should be gone now.
Flashable Zip (through custom recovery, does not require Magisk): View attachment 4121507
Magisk Module (same thing, just systemless): View attachment 4121508
There was an issue before with some missing files that caused playback to run too fast and with a higher pitch. That has been fixed now. If anyone flashed the old Magisk module, I would advise you to download the new one in the OP and flash over it. I've also included a flashable zip for those of you who aren't using Magisk.
Anova's Origin said:
There was an issue before with some missing files that caused playback to run too fast and with a higher pitch. That has been fixed now. If anyone flashed the old Magisk module, I would advise you to download the new one in the OP and flash over it. I've also included a flashable zip for those of you who aren't using Magisk.
Click to expand...
Click to collapse
Thanks a million
Thank you, I have installed it but it seems to have a lot more problems (noise/cracking as in packets lost or something) than the previous version that I was using and which I got from here:
https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228
Is there any way to uninstall this version and return to "old default" (from where I can get back to the aptx version from above)?
xclub_101 said:
Thank you, I have installed it but it seems to have a lot more problems (noise/cracking as in packets lost or something) than the previous version that I was using and which I got from here:
https://forum.xda-developers.com/oneplus-3/themes/mod-aptx-codec-t3521228
Is there any way to uninstall this version and return to "old default" (from where I can get back to the aptx version from above)?
Click to expand...
Click to collapse
If you used the Magisk module, simply delete the module and reboot.
If you flashed the regular zip, you'll have to dirty flash your ROM to restore to default.
Hi @Anova's Origin, how do i know if this mod is working or not?
Vixiebalistic said:
Hi @Anova's Origin, how do i know if this mod is working or not?
Click to expand...
Click to collapse
Use a logcat app (Catlog / Matlog) and search for an aptx entry in the recorded logs after you connected your aptx capable device via Bluetooth to your aptx enabled phone...
You should be able to find something if it's working, otherwise it wouldn't show any aptx entry
Sent from my OnePlus3T using XDA Labs
Edit 2: Nevermind, it's working now. Idk what the problem was.
Didn't work for me on OOS 4.1.6 on Oneplus 3T I can't turn on Bluetooth. Anyone else having this problem? Also, have the drivers been updated in a newer OB?
Edit: I am using magisk v13.3
vini2710 said:
Didn't work for me on OOS 4.1.6 on Oneplus 3T I can't turn on Bluetooth. Anyone else having this problem? Also, have the drivers been updated in a newer OB?
Click to expand...
Click to collapse
Nope... Working fine here with op3t 4.1.6. Did u make back up before flashing?
Vixiebalistic said:
Nope... Working fine here with op3t 4.1.6. Did u make back up before flashing?
Click to expand...
Click to collapse
I used magisk so no worries (v13.3)
Edit: It's working. Yay! Thank you for the good work with this module!
how about op3T 4.1.7? Is it work?
qwealan said:
how about op3T 4.1.7? Is it work?
Click to expand...
Click to collapse
It works flawlessly for me on OOS 4.1.7 on my op3t
Sent from my ONEPLUS A3003 using Tapatalk
Anyone, test Magisk module with lineageOS Rom ?
vinicentus said:
It works flawlessly for me on OOS 4.1.7 on my op3t
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
I use Magisk Module on OOS4.1.7 but i cant use aptX (use catlog search "aptx" ). are you use zip flash or use Magisk too?
qwealan said:
I use Magisk Module on OOS4.1.7 but i cant use aptX (use catlog search "aptx" ). are you use zip flash or use Magisk too?
Click to expand...
Click to collapse
I am using magisk (v14)
Working on OP3T with OOS 4.5.1 + Magisk 14.0. Those libs where updated to show battery for devices in OB15, update needed.
Thanks very much! Looking for this about a week long and finally solved
My device is OP3T, with H2OS V3.5 stable, no magisk
can I share this to oneplusbbs.com?
I have long sought a way to pass the safetynet. Finally I found a solution. I found a project made for Xiaomi Mi5 and i have ported it on Leeco Le Pro3.
Original Project by @coronafire : https://forum.xda-developers.com/mi-5/how-to/mi-5-passing-safetynet-unlocked-t3557845
Actually i have made the mod only for Le Max 2 and Le Pro 3. I have tested only on Le Max 2, because i have no Leeco device in this moment and I someone have test it on Le Pro 3 with succes ( ZIP4). This mod will not work if you have xposed on your phone.
I have built a github project and if you want you can add more Leeco device.
Github Project: https://github.com/mauronofrio/magisk-leeco-safetynet-props/tree/master
What this mod do?
- This mod set some props and enable magisk hide (If you don't enable magisk hide your phone can't pass Safetynet check). This mod will survive future updates and in general it will survive if you don't make a wipe data.
How to install:
You need to have already installed magisk on your phone. You can find it on official thread: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk direct link: http://tiny.cc/latestmagisk
Just download the zip and flash it in TWRP
DOWNLOAD
Safetynet Pass for Le Pro 3 (Zip 4) MEGA
Safetynet Pass for Le Pro 3 (Zip 4) AFH
If you test it please comment and/or give me a feedback
Sorry for a dumb question, but I assume you need to install magisk first?
Sent from my LEX727 using XDA Labs
llblwskydrgn said:
Sorry for a dumb question, but I assume you need to install magisk first?
Sent from my LEX727 using XDA Labs
Click to expand...
Click to collapse
Yes, i forget to write it
I'm on AICP, which have default Magisk. Downloaded lastest version from Play Store. On settings of Magisk I have "Magisk Hide", which make "SafetyNet Correct".
marik1 said:
I'm on AICP, which have default Magisk. Downloaded lastest version from Play Store. On settings of Magisk I have "Magisk Hide", which make "SafetyNet Correct".
Click to expand...
Click to collapse
Yes but on rom stock based you need of this zip to pass safetynet check
Does this also work on Lineage OS?
Moritz Bayerl said:
Does this also work on Lineage OS?
Click to expand...
Click to collapse
Yes
First of all thank you very much. I'll try that in a second.
---------- Post added at 10:50 AM ---------- Previous post was at 10:44 AM ----------
Alright so I just installed it but still the cts profile check fails.
I guess I'll need another kernel.
mauronofrio said:
Yes
Click to expand...
Click to collapse
Does it mean I can use Android Pay with LineageOS?
sweetboy02125 said:
Does it mean I can use Android Pay with LineageOS?
Click to expand...
Click to collapse
Yes
Sadly it just don't work for me. Any ideas?
Moritz Bayerl said:
Sadly it just don't work for me. Any ideas?
Click to expand...
Click to collapse
What rom do you have? Do you have magisk installed? Do you have xposed installed?
Magisk installed on lineage os 7.1.2 and no xposed
Moritz Bayerl said:
Magisk installed on lineage os 7.1.1 and no xposed
Click to expand...
Click to collapse
I don't know why.
It says that cts profile would not match
Moritz Bayerl said:
It says that cts profile would not match
Click to expand...
Click to collapse
MMM but you have only magisk on your phone or you also have superuser? If you have both is normale that you have cts mismatch
mauronofrio said:
Yes
Click to expand...
Click to collapse
Do you think it will stay if I update LineageOS weekly or I have to flash this every times LineageOS update?
sweetboy02125 said:
Do you think it will stay if I update LineageOS weekly or I have to flash this every times LineageOS update?
Click to expand...
Click to collapse
This is a permanent fix. You will lose it only if you make a wipe data or unistall magisk
sweetboy02125 said:
Do you think it will stay if I update LineageOS weekly or I have to flash this every times LineageOS update?
Click to expand...
Click to collapse
Tell me if you try this mod and if it works
Moritz Bayerl said:
It says that cts profile would not match
Click to expand...
Click to collapse
I have made another zip, try this: https://mega.nz/#!cA1TUBQb!5vDJKFjPq3lTVqFZxopHGc-YWWoJzW4KhSZjPiIsnFg
Hey, I installed magisk on stock miui 8.2.10.0 but it failed to pass the safetynet after that.I tried xiaomi.eu both developer and stable and they also failed safetynet with magisk. Without magisk they worked fine. Is there a way to pass safetynet on miui. On LOS it used to pass easily but not on miui
rxlord said:
Hey, I installed magisk on stock miui 8.2.10.0 but it failed to pass the safetynet after that.I tried xiaomi.eu both developer and stable and they also failed safetynet with magisk. Without magisk they worked fine. Is there a way to pass safetynet on miui. On LOS it used to pass easily but not on miui
Click to expand...
Click to collapse
install the latest magisk and use this module
https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431/page98
asusm930 said:
install the latest magisk
Click to expand...
Click to collapse
Using magisk 13.3
rxlord said:
Using magisk 13.3
Click to expand...
Click to collapse
updated my reply
use this module https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431/page98
and use the TEST BUILD
Thank you magisk 13.3 with the module provided above works
using this test build :-
https://forum.xda-developers.com/showpost.php?p=73185618&postcount=978
safetynet passes
rxlord said:
Thank you magisk 13.3 with the module provided above works
using this test build :-
https://forum.xda-developers.com/showpost.php?p=73185618&postcount=978
safetynet passes
Click to expand...
Click to collapse
I don't have telegram....
Can you post another link, please?
Thanks
I'm Using Magisk 12.0 it shows device properly rooted but safetynet check failed.
Rom : miui 8 stable 8.2.5
And failed to flash magisk v13.3 it says restore boot image or something like that.
meibourne said:
I don't have telegram....
Can you post another link, please?
Thanks
Click to expand...
Click to collapse
Install telegram
Trust me its worth because it works
Mitu1998 said:
I'm Using Magisk 12.0 it shows device properly rooted but safetynet check failed.
Rom : miui 8 stable 8.2.5
And failed to flash magisk v13.3 it says restore boot image or something like that.
Click to expand...
Click to collapse
Finally solved
rxlord said:
Hey, I installed magisk on stock miui 8.2.10.0 but it failed to pass the safetynet after that.I tried xiaomi.eu both developer and stable and they also failed safetynet with magisk. Without magisk they worked fine. Is there a way to pass safetynet on miui. On LOS it used to pass easily but not on miui
Click to expand...
Click to collapse
Hey man I'm on 8.1.10 Redmond note 4 snapdragon,whenever I flash magisk the icon doesn't appear on phone and I have to install magisk manager apk,its installed and then it fails safety net,it works fine miui 9 but I love the battery backup of miui 8!?
Any help will be appreciated!
Sent from my mido using XDA Labs
saransh arya said:
Hey man I'm on 8.1.10 Redmond note 4 snapdragon,whenever I flash magisk the icon doesn't appear on phone and I have to install magisk manager apk,its installed and then it fails safety net,it works fine miui 9 but I love the battery backup of miui 8!
Any help will be appreciated!
Sent from my mido using XDA Labs
Click to expand...
Click to collapse
go to this thread:- https://forum.xda-developers.com/apps/magisk/xiaomi-safetynet-fix-t3600431
join their telegram group and download the latest universal safetynet fix and install it using magisk
Well there is no need to describe what this fix does.
Note there is already a multi-touch magisk module out there which is originally for pixel but this one is modified by me only for POCO F1.
*Note this works only in Custom ROMs. Yes It's not fixed in Custom ROMs by default.
Installation:
Flash the Magisk module via twrp and reboot.
Uninstalling:
Flash the uninmod Magisk zip in twrp.
Go to advanced->terminal and type "uninmod"
Select _// Multi touch fix for Poco
Reboot.
Status (flash and tell me)
Reserved for updates.
Does it work with miui.eu? Would love to try now. Thanks
Sent from my POCOPHONE F1 using XDA-Developers Legacy app
joseph168 said:
Does it work with miui.eu? Would love to try now. Thanks
Sent from my POCOPHONE F1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
there is app called touch screen test by siriuth , see if it works
$hivaM Manav said:
Well there is no need to describe what this fix does.
Note there is already a multi-touch magisk module out there which is originally for pixel but this one is modified by me only for POCO F1.
*Note this works only in Custom ROMs. Yes It's not fixed in Custom ROMs by default.
Installation:
Flash the Magisk module via twrp and reboot.
Uninstalling:
Flash the uninmod Magisk zip in twrp.
Go to advanced->terminal and type "uninmod"
Select _// Multi touch fix for Poco
Reboot.
Status (flash and tell me)
Click to expand...
Click to collapse
This is a great initiative for the community.
Unfortunately can't test it cos still on beta 8.9.20.
And even after shifting to custom ROM won't know what to test it for as don't realise my touch screen has a problem.
i get bootloop with aospextended
joseph168 said:
Does it work with miui.eu? Would love to try now. Thanks
Sent from my POCOPHONE F1 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Doesn't work on any MIUI based roms.
sanjay0501 said:
This is a great initiative for the community.
Unfortunately can't test it cos still on beta 8.9.20.
And even after shifting to custom ROM won't know what to test it for as don't realise my touch screen has a problem.
Click to expand...
Click to collapse
This problem exists in all phones and xiomi claims it's fixed when it isn't easiest way to check this is using multi touch applications.
$hivaM Manav said:
This problem exists in all phones
Click to expand...
Click to collapse
LOL No!
$hivaM Manav said:
Well there is no need to describe what this fix does.
Note there is already a multi-touch magisk module out there which is originally for pixel but this one is modified by me only for POCO F1.
*Note this works only in Custom ROMs. Yes It's not fixed in Custom ROMs by default.
Installation:
Flash the Magisk module via twrp and reboot.
Uninstalling:
Flash the uninmod Magisk zip in twrp.
Go to advanced->terminal and type "uninmod"
Select _// Multi touch fix for Poco
Reboot.
Status (flash and tell me)
Click to expand...
Click to collapse
How do I check if it's properly installed?
A fix for a problem no one knows they have?
Reserved for updates
Another fix is to use a custom patched kernel (Franco Kernel for example).
U wot m8
Here, you can share your favourite magisk OR Xposed modules
preferably, Compatible with android 10
add a "one line" description about the module for extra bonus points!
Cheers
Android 10 is compatible with EdXposed?
I flashed it and got a bootloop...
Sent from my Redmi K20 using XDA Labs
welder73 said:
Android 10 is compatible with EdXposed?
I flashed it and got a bootloop...
Sent from my Redmi K20 using XDA Labs
Click to expand...
Click to collapse
it is.
try different versions between yahfa and sandhook
if nothing works, taichi is always an option
welder73 said:
Android 10 is compatible with EdXposed?
I flashed it and got a bootloop...
Click to expand...
Click to collapse
You have to use the latest beta (0.4.6.0). You have to download it from github and not from Magisk Manager.
_Frostplexx_ said:
You have to use the latest beta (0.4.6.0). You have to download it from github and not from Magisk Manager.
Click to expand...
Click to collapse
I've found beta versions of Sandhook and Yahfa and both working...but the Customiuizer doesn't...
I read that I should update Magisk from some custom channel but I can't do that because I'm using MiuMix rom with Magisk preinstalled and they say we shouldn't update it...
Sent from my Redmi K20 using XDA Labs
C
welder73 said:
I've found beta versions of Sandhook and Yahfa and both working...but the Customiuizer doesn't...
I read that I should update Magisk from some custom channel bit I can't do that because I'm using MiuMix rom with Magisk preinstalled and they say we shouldn't update it...
Click to expand...
Click to collapse
I am sorry but i can't help you with that because customiuizer (and other mofules)also didn't work for me and now I am on the Pixel Experience Rom without Xposed. You could try switching to a rom like xiaomi.eu but you will probably lose your data.
welder73 said:
I've found beta versions of Sandhook and Yahfa and both working...but the Customiuizer doesn't...
I read that I should update Magisk from some custom channel bit I can't do that because I'm using MiuMix rom with Magisk preinstalled and they say we shouldn't update it...
Sent from my Redmi K20 using XDA Labs
Click to expand...
Click to collapse
On Android Q, you should use Yahfa. With Sandhook, you will have some fc on miuimizer.
Go on and flash custom magisk. You shouldn't, but you CAN .
Make a backup of boot partition into twrp, if you go into bootlop just restore it or reflash the rom.
sauliiin said:
On Android Q, you should use Yahfa. With Sandhook, you will have some fc on miuimizer.
Go on and flash custom magisk. You shouldn't, but you CAN .
Make a backup of boot partition into twrp, if you go into bootlop just restore it or reflash the rom.
Click to expand...
Click to collapse
Tnx man, it worked :good:
Sent from my Redmi K20 using XDA Labs
welder73 said:
Tnx man, it worked :good:
Sent from my Redmi K20 using XDA Labs
Click to expand...
Click to collapse
Nice!
Trying to get Edxposed on PixelUI but it won't go paste the google boot screen no mater which version I try YAHFA/Sandhook.
I'm using the Riru module on Magisk (v20.3) and EdXposed from Magisk, anything I should try to get it to work?
CustoMIUIser is the greatest module ever, honestly. Love being able to have my charge current on my lockscreen etc