I created a Magisk module based off the FMRaido PIE fix, this Magisk module will allow you to use the FM Raido under pie roms that don't support it, it should work with other Xiaomi devices too but I can only test on my RN3P.
I'm not sure who created the original flashable recovery zip / modules (FMRadioFixPiE.zip), I just converted it to Magisk so we don't need to modify the system or vendor partitions.
Edit
No longer needed for Havoc OS since it comes with the radio app on latest updates.
Enjoy.
Use at own risk...etc..etc.
Needs
Magisk 17.0+
Android 9 (PIE)
Not working with Havoc pie.
No playback.. Radio found channels correctly.
anurag86 said:
Not working with Havoc pie.
No playback.. Radio found channels correctly.
Click to expand...
Click to collapse
It's work well for me. It's a module for Magisk.
Magisk 18.0
Havoc pie.
Redmi Note 3 using Tapatalk
I am trying to install this on Citrus-CAF but even though I can see the app under the system/app directory for some weird reason the app is not installed. It might have to do with enforcing selinux since it was working great on Havoc OS.
It works great
otyg said:
I created a Magisk module based off the FMRaido PIE fix, this Magisk module will allow you to use the FM Raido under pie roms that don't support it, it should work with other Xiaomi devices too but I can only test on my RN3P.
I'm not sure who created the original flashable recovery zip / modules (FMRadioFixPiE.zip), I just converted it to Magisk so we don't need to modify the system or vendor partitions.
Edit
No longer needed for Havoc OS since it comes with the radio app on latest updates.
Enjoy.
Use at own risk...etc..etc.
Needs
Magisk 17.0+
Android 9 (PIE)
Click to expand...
Click to collapse
It works great on nitrogen os pie 9 and redmi notes 3. Thanks
ronkanor said:
It's work well for me. It's a module for Magisk.
Magisk 18.0
Havoc pie.
Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
Got FM radio in updated Havoc Build. :good:
Nos 9 work great
I instal this module for j7 pro j730GM rom PrometheusOneUI_V1.0_jxy17lte. But phone stuck in samsung logo so i restore backup. Plz update your module for work PrometheusOneUI_V1.0_jxy17lte. Rom.
Xxxnano said:
I instal this module for j7 pro j730GM rom PrometheusOneUI_V1.0_jxy17lte. But phone stuck in samsung logo so i restore backup. Plz update your module for work PrometheusOneUI_V1.0_jxy17lte. Rom.
Click to expand...
Click to collapse
Unfortunately I don't own that device, this module is only for Xiaomi devices.
fm for nitrogen os pie [2019-03-09]
Installed the module on nos for redmi note 3 kenzo
app opens but audio playback is missing and can't tune it.
Any pointers...
rahulh0785 said:
Installed the module on nos for redmi note 3 kenzo
app opens but audio playback is missing and can't tune it.
Any pointers...
Click to expand...
Click to collapse
same problem here.... im using Nos9Pie but it opens and nothings happens
someone can help me?
Related
This is a collection of small changes to fix things on my Moto G4 XT1626 that others may find useful.
ElementalX 1.02 with DTV driver:
This is the great and stable ElementalX Kernel from flar2, without any code changes, but with the ISDBT TV kernel driver that he didn't include in the official version, useful for XT1626 owners that want root but need the DTV receiver working.
Disable esdfs:
This is a magisk module (can also be flashed if you don't use magisk) to disable ESDFS and use FUSE instead, so apps like apps2sd work properly on the moto G4 or G4 Plus.
MotoG4 incall record enabler:
This is a magisk module (can also be flashed) that changes the mixer controls mapping to allow incall recording using any playstore app(even without root). Tested with ACR, works fine. This was made for Stock Nougat, untested on other roms.
I will add more quirks and mods I develop in the future to this thread.
Working Fine ?
_wyrm said:
This is a collection of small changes to fix things on my Moto G4 XT1626 that others may find useful.
ElementalX 1.02 with DTV driver:
This is the great and stable ElementalX Kernel from flar2, without any code changes, but with the ISDBT TV kernel driver that he didn't include in the official version, useful for XT1626 owners that want root but need the DTV receiver working.
Disable esdfs:
This is a magisk module (can also be flashed if you don't use magisk) to disable ESDFS and use FUSE instead, so apps like apps2sd work properly on the moto G4 or G4 Plus.
MotoG4 incall record enabler:
This is a magisk module (can also be flashed) that changes the mixer controls mapping to allow incall recording using any playstore app(even without root). Tested with ACR, works fine. This was made for Stock Nougat, untested on other roms.
I will add more quirks and mods I develop in the future to this thread.
Click to expand...
Click to collapse
Anyone tried the call recording on custom room?
Waycloud said:
Working Fine ?
Click to expand...
Click to collapse
On stock ROM?
How can I get the DTV driver or the last ElementalX with DTV driver?
brunopio said:
How can I get the DTV driver or the last ElementalX with DTV driver?
Click to expand...
Click to collapse
I want to know too. My model is XT1626
Doesn't the last ElementalX has the DTV driver included already? I believe flar2 started including the DTV driver a couple weeks after I created this thread.
_wyrm said:
MotoG4 incall record enabler:.
Click to expand...
Click to collapse
Thank you very much, in particular for the call recording. Although the recording app I had been using (CallRec) did not detect the new VOICE_COMMUNICATION stream, as you mention in the OPs it works fine with ACR. I'm running it in recent LOS 14.1 Athene builds on an XT1625.
One (somewhat off topic) question: I switched from LOS SU to Magisk in order to install this module. Except for a few other apps that seem to prefer LOS SU I'm happy with Magisk managing SU but in case I want to switch back to LOS SU ...is there a way to get this installed while using LOS SU. Perhaps this is a question for the Magisk thread but I've found no answers by searching so I'm starting here. Thanks again!
---------- Post added at 05:56 PM ---------- Previous post was at 05:48 PM ----------
optionalmgrr.la said:
Anyone tried the call recording on custom room?
Click to expand...
Click to collapse
Lineage OS as described in previous post section.
IronTechmonkey said:
One (somewhat off topic) question: I switched from LOS SU to Magisk in order to install this module. Except for a few other apps that seem to prefer LOS SU I'm happy with Magisk managing SU but in case I want to switch back to LOS SU ...is there a way to get this installed while using LOS SU. Perhaps this is a question for the Magisk thread but I've found no answers by searching so I'm starting here. Thanks again!
Click to expand...
Click to collapse
All this modules does is replace/bind (mount -bind), /system/etc/mixer_paths.xml with a custom version. You can do the same with a shell script, luckypatcher, or any other root app that alows you to selectively replace files in the system. You can also simply replace the file directly in LOS's /system/ if you want to make it permanent and don't care about keeping /system untampered.
Hope we can have call recording on LOS
hello plz help me in to enable call recordings in moto g5 plus
please friend
_wyrm said:
This is a collection of small changes to fix things on my Moto G4 XT1626 that others may find useful.
ElementalX 1.02 with DTV driver:
This is the great and stable ElementalX Kernel from flar2, without any code changes, but with the ISDBT TV kernel driver that he didn't include in the official version, useful for XT1626 owners that want root but need the DTV receiver working.
Disable esdfs:
This is a magisk module (can also be flashed if you don't use magisk) to disable ESDFS and use FUSE instead, so apps like apps2sd work properly on the moto G4 or G4 Plus.
MotoG4 incall record enabler:
This is a magisk module (can also be flashed) that changes the mixer controls mapping to allow incall recording using any playstore app(even without root). Tested with ACR, works fine. This was made for Stock Nougat, untested on other roms.
I will add more quirks and mods I develop in the future to this thread.
Click to expand...
Click to collapse
Please friend, you could include the DTV XT1626 driver in this kernel Vegito:
mega.nz/#!1R8XSRCD!L1pQiukRxflWfdPfiKmO13rIRdUn1RLaXUhFeGsIsuU
This kernel works best with the XT1626
yeah would be great
I can use DTV drivers on xt1625?
Sent from my [device_name] using XDA-Developers Legacy app
hope these modules get update to magisk 16, because here when i tried to flash over magisk manager or twrp, shows an error saying that magisk is not installed on system
nodio said:
hope these modules get update to magisk 16, because here when i tried to flash over magisk manager or twrp, shows an error saying that magisk is not installed on system
Click to expand...
Click to collapse
I desperately needed call recording feature on my Moto G4 Plus so I updated it myself to work with the latest version of Magisk (17.1). Here the file if you need it : drive.google.com/file/d/1fcO6FqFVXCUtwrFVTEijUG3LDaOWRmBP/view?usp=sharing
mithleshjs said:
I desperately needed call recording feature on my Moto G4 Plus so I updated it myself to work with the latest version of Magisk (17.1). Here the file if you need it : drive.google.com/file/d/1fcO6FqFVXCUtwrFVTEijUG3LDaOWRmBP/view?usp=sharing
Click to expand...
Click to collapse
I gave your version a try because I'm also running Magisk 17.1 and it trashed my system, wasn't expecting that much fun to happen.
After I installed module and rebooted the phone it just went to recovery mode, was forced to do a full reset.
Others be warned, try at your own risk...
lin_ux said:
I gave your version a try because I'm also running Magisk 17.1 and it trashed my system, wasn't expecting that much fun to happen.
After I installed module and rebooted the phone it just went to recovery mode, was forced to do a full reset.
Others be warned, try at your own risk...
Click to expand...
Click to collapse
FWIW I once used this on a Moto G4 Athene XT1625 running LOS 14.1 and Magisk 16x with no problems. Don’t know about Magisk 17 as I use LOS SU except when specifically testing something else but it's a simple mod which really "should" not cause that much trouble. In any event once you get your device back in shape you could try to enable call recording manually: https://forum.xda-developers.com/showpost.php?p=73603492&postcount=9.
[EDIT] Added details about device on which I had tested this in Magisk.
IronTechmonkey said:
FWIW I once used this on a Moto G4 Athene XT1625 running LOS 14.1 and Magisk 16x with no problems. Don’t know about Magisk 17 as I use LOS SU except when specifically testing something else but it's a simple mod which really "should" not cause that much trouble. In any event once you get your device back in shape you could try to enable call recording manually: https://forum.xda-developers.com/showpost.php?p=73603492&postcount=9.
[EDIT] Added details about device on which I had tested this in Magisk.
Click to expand...
Click to collapse
Thanks for your reply!
I agree that the mod should not have caused so much trouble, which is why I was a little shell shocked when it refused to boot to anything other than recovery. I'd just got the device set up nice and hadn't done a TWRP backup yet, so getting it back up and running again was a little painful, but perhaps good in a way as I'd learnt what didn't work well first time round, so this time it's lean and mean...
I've taken a look at the files enclosed in the mod (I know, I should have done that before installing it ... doh! ) and discovered that the location of mixer_paths.xml is different on my system, it's in /vendor/etc/ so I went ahead and swapped the modded file (I have root access) with my one and rebooted, phone came up with no sound output at all, so it looks like my newer system (and device, it's a Moto E5 XT1944-6) are not compatible with the modded mixer_paths.xml file.
I'd like to know which elements of the modded mixer_paths.xml file were change to make it work on the G4, I could then try to add/edit those particular ones in my mixer_paths.xml file to see if it works.
I have a backup of my original file so no pain in trying new settings....
For reference I'm running this ROM on my phone,
[GSI][8.1.0][OFFICIAL] Resurrection Remix O v.6.1.0 [08/18][ARM/ARM64]
it's quite impressive...
https://forum.xda-developers.com/pr...si-resurrection-remix-o-6-1-0-t3811299/page11
lin_ux said:
I gave your version a try because I'm also running Magisk 17.1 and it trashed my system, wasn't expecting that much fun to happen.
After I installed module and rebooted the phone it just went to recovery mode, was forced to do a full reset.
Others be warned, try at your own risk...
Click to expand...
Click to collapse
It shouldn't have caused so much trouble. It worked successfully on each of my friends Moto G4 Plus running stock ROM.
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?
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
i can't install xposed to my phone
it always go into bootloop
i have magisk and it works normally
i tried all versions of xposed at magisk modules store
(incl. sdk 27)
what is the right way to install it
Xiaomi Redmi 5 rosy
miui pro 10 9.1.24
Android 8.1.0
no one can help?!
anyone installed xposed on Redmi 5?
I'm using EdXopsed (beta) as magisk module in sdk 28. It's work fine.
Maybe work this Xposed
[emoji3504] https://forum.xda-developers.com/re...ment/modified-xposed-miui10-oreo-8-1-t3913160
I not tested yet, because haven't more time for this procedure [emoji6]
Sent from my Redmi 5
royalsixteex said:
I'm using EdXopsed (beta) as magisk module in sdk 28. It's work fine.
Click to expand...
Click to collapse
I tried it but it supports few modules of xposed ?
poky14 said:
Maybe work this Xposed
[emoji3504] https://forum.xda-developers.com/re...ment/modified-xposed-miui10-oreo-8-1-t3913160
I not tested yet, because haven't more time for this procedure [emoji6]
Sent from my Redmi 5
Click to expand...
Click to collapse
it works for few xposed modules my friends
its not a perfect solution
mido4ever2000 said:
I tried it but it supports few modules of xposed ?
Click to expand...
Click to collapse
Force request here to release official. ??
https://forum.xda-developers.com/essential-phone/help/xposed-sdk-28-android-9-pie-t3828168
Has anyone managed to find a working solution?
...
Maybe this?
https://taichi.cool/
I try it in Android Ten and works ,maybe it helps
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