Is your WiFi Calling staying connected after updating to 10n? Mine was working fine on 10h, but on 10n it disconnects after 5-10 minutes with a REG99: Unable to connect error and won't reconnect until I reboot the phone.
I did all the troubleshooting steps with T-Force: factory reset, got a new SIM card, got an update sent to the SIM card twice, factory reset again, and no dice.
Is anyone else experiencing this on 10n? I'm on stock rooted 10n (odex).
EDIT: It's XPosed. As long as the XPosed Framework is installed (even with no modules), WiFi Calling is completely broken.
I was getting the same error on 10N. I called and was transferred to Tech Support. They updated my E-911 info and was back up in running in less than 5 minutes
siraltus said:
Is your WiFi Calling staying connected after updating to 10n? Mine was working fine on 10h, but on 10n it disconnects after 5-10 minutes with a REG99: Unable to connect error and won't reconnect until I reboot the phone.
I did all the troubleshooting steps with T-Force: factory reset, got a new SIM card, got an update sent to the SIM card twice, factory reset again, and no dice.
Is anyone else experiencing this on 10n?
Click to expand...
Click to collapse
Are you using xposed? I am experiencing same while xposed is installed and it works perfect without...
jamesd1085 said:
Are you using xposed? I am experiencing same while xposed is installed and it works perfect without...
Click to expand...
Click to collapse
I'm using xposed and it works great (wi-fi calling).
gerald410 said:
I'm using xposed and it works great (wi-fi calling).
Click to expand...
Click to collapse
Not the case for me and others are trickling in with the same issue
So I rooted my phone a little more than a week ago and then flashed MicroMod777's rooted stock 10n ROM a few days later. Up until this point, WiFi calling was working. I then flashed the Xposed framework v72, downloaded some modules, and installed them. I realized that WiFi calling was no longer available and would give me the classic REG99 error, unable to connect. Another user on MicroMod777's 10n stock ROM thread (http://forum.xda-developers.com/tmo...m-g4-h811-10n-stock-rooted-rom-t3188858/page9) had the same problem, though another user responded that Wifi calling was working fine with the 10 ROM and Xposed v72.
I uninstalled Xposed and I could immediately access WiFi calling, so it seems that Xposed is conflicting with the 10n stock ROM's WiFi calling. Same results with v73. Users who are getting WiFi calling to work on Xposed, did you get the official 10n update OTA or flash a rooted ROM? And what version of Xposed are you running?
Synchronicities said:
So I rooted my phone a little more than a week ago and then flashed MicroMod777's rooted stock 10n ROM a few days later. Up until this point, WiFi calling was working. I then flashed the Xposed framework v72, downloaded some modules, and installed them. I realized that WiFi calling was no longer available and would give me the classic REG99 error, unable to connect. Another user on MicroMod777's 10n stock ROM thread (http://forum.xda-developers.com/tmo...m-g4-h811-10n-stock-rooted-rom-t3188858/page9) had the same problem, though another user responded that Wifi calling was working fine with the 10 ROM and Xposed v72.
I uninstalled Xposed and I could immediately access WiFi calling, so it seems that Xposed is conflicting with the 10n stock ROM's WiFi calling. Same results with v73. Users who are getting WiFi calling to work on Xposed, did you get the official 10n update OTA or flash a rooted ROM? And what version of Xposed are you running?
Click to expand...
Click to collapse
Stocked rooted rom and v72 I believe (how to confirm?).
gerald410 said:
Stocked rooted rom and v72 I believe (how to confirm?).
Click to expand...
Click to collapse
Open the XPosed Installer app and look in the Framework section.
jamesd1085 said:
Are you using xposed? I am experiencing same while xposed is installed and it works perfect without...
Click to expand...
Click to collapse
I was having the issue on a totally stock, factory-reset phone with nothing installed.
T-Force opened a ticket with network engineering, supposed to be resolved by tomorrow.
siraltus said:
Not XPosed's fault at all. I was having the issue on a totally stock, factory-reset phone with nothing installed.
Click to expand...
Click to collapse
Just asking as i have same issue but only with xposed...as are some others
jamesd1085 said:
Just asking as i have same issue but only with xposed...as are some others
Click to expand...
Click to collapse
Interesting.... I wonder why. I have Xposed installed on my Note 4 also and WiFi Calling works perfectly fine there. Might be a specific module causing it.
Come to think of it, when I factory-reset the phone, Xposed was still installed into the system partition, since it's not an app, but a modification to system files.
I will have to re-test after explicitly uninstalling Xposed. It would be a total bummer if Xposed is the problem. And if it is, I hope it's just a specific module that I can disable. I'd hate to lose YouTube AdAway and a few others.
siraltus said:
Interesting.... I wonder why. I have Xposed installed on my Note 4 also and WiFi Calling works perfectly fine there. Might be a specific module causing it.
Come to think of it, when I factory-reset the phone, Xposed was still installed into the system partition, since it's not an app, but a modification to system files.
I will have to re-test after explicitly uninstalling Xposed. It would be a total bummer if Xposed is the problem. And if it is, I hope it's just a specific module that I can disable. I'd hate to lose YouTube AdAway and a few others.
Click to expand...
Click to collapse
Mine is broken without even adding modules...fixes instantly after flashing xposed uninstaller
jamesd1085 said:
Mine is broken without even adding modules...fixes instantly after flashing xposed uninstaller
Click to expand...
Click to collapse
Well that just sucks. I just uninstalled Xposed and WiFi Calling is staying connected now. This is not good.
siraltus said:
Well that just sucks. I just uninstalled Xposed and WiFi Calling is staying connected now. This is not good.
Click to expand...
Click to collapse
Looks like we need to try and get some logs for rovo and hopefully he can easily fix it...
Scrap that! Download SELinux mode changer and change to permissive...instantly popped up and stayed connected! Great news
jamesd1085 said:
Looks like we need to try and get some logs for rovo and hopefully he can easily fix it...
Scrap that! Download SELinux mode changer and change to permissive...instantly popped up and stayed connected! Great news
Click to expand...
Click to collapse
O RLY... is that an Xposed module?
siraltus said:
O RLY... is that an Xposed module?
Click to expand...
Click to collapse
Try ticking disable resource hooks in exposed installer app...and You can google SELinux mode changer its an app it coonects after boot...takes longer than it used to but its working on my end
siraltus said:
Open the XPosed Installer app and look in the Framework section.
Click to expand...
Click to collapse
I'm running v71 thx.
jamesd1085 said:
Try ticking disable resource hooks in exposed installer app...and You can google SELinux mode changer its an app it coonects after boot...takes longer than it used to but its working on my end
Click to expand...
Click to collapse
Nope, neither works. WiFi Calling is still busted while Xposed is installed.
siraltus said:
Nope, neither works. WiFi Calling is still busted while Xposed is installed.
Click to expand...
Click to collapse
Try unticking disable hooks...it's working fine without that...try a couple reboots...mine has settled in and works fine...also did you opeen the app and grant root and press permissive?
jamesd1085 said:
Try unticking disable hooks...it's working fine without that...try a couple reboots...mine has settled in and works fine...also did you opeen the app and grant root and press permissive?
Click to expand...
Click to collapse
Of course I granted root and pressed Permissive, I know what SELinux is. I also unticked that checkbox and rebooted like 5 times. It either never connects or connects and disconnects after 2-3 minutes.
Related
I flashed the .230 kitkat update couple days ago, everything works pretty good so far until just now I am trying to use my xz to share wifi.
But it seems failed to start so I try using usb tethering, still didn't work out. Any ideas?
chunweng428 said:
I flashed the .230 kitkat update couple days ago, everything works pretty good so far until just now I am trying to use my xz to share wifi.
But it seems failed to start so I try using usb tethering, still didn't work out. Any ideas?
Click to expand...
Click to collapse
Did you flash any xposed module or any other "boosting" mod?If you do try to remove it and it should work.Stock .230 works just fine for Wi-Fi tethering.
zeroed said:
Did you flash any xposed module or any other "boosting" mod?If you do try to remove it and it should work.Stock .230 works just fine for Wi-Fi tethering.
Click to expand...
Click to collapse
In before yes, i did flash a xposed module but removed an hour later and xposed installer is still there, should i get rid of it?
Hi all!
I wonder if anyone managed to install Xposed & Xprivacy on Lollipop? I tried to install xposed, flashed it through the recovery, restarted the phone which was apparently working fine. I installed then the xposed module manager, it was saying that xposed was installed. I restarted the phone and this time I had a bootloop.
So my question is, has anyone succeeded?
Thanks
Bootlooping
difto said:
Hi all!
I wonder if anyone managed to install Xposed & Xprivacy on Lollipop? I tried to install xposed, flashed it through the recovery, restarted the phone which was apparently working fine. I installed then the xposed module manager, it was saying that xposed was installed. I restarted the phone and this time I had a bootloop.
So my question is, has anyone succeeded?
Thanks
Click to expand...
Click to collapse
No luck... even with unlocked BL, Root, and the new Xposed 3.0 alpha3 (xposed-sdk21-arm-20150426.zip)...
Exact same symptoms. Everything else works, but only xprivacy causes the loop...
Anyone else have luck?
Well the développer of xprivacy said that it triggers a bug in xposed and that it cannot do anything before xposed gets updated (which can take time as the xposed developer only works on it as a leisure)
difto said:
Well the développer of xprivacy said that it triggers a bug in xposed and that it cannot do anything before xposed gets updated (which can take time as the xposed developer only works on it as a leisure)
Click to expand...
Click to collapse
Hey thanks for the update. Anything we can do to help expedite the bugfix?
you can do this with App Ops , it's on google play.
briarbiz said:
Hey thanks for the update. Anything we can do to help expedite the bugfix?
Click to expand...
Click to collapse
I think he suspended the development until Xposed gets updated so no unfortunately.
difto said:
I think he suspended the development until Xposed gets updated so no unfortunately.
Click to expand...
Click to collapse
Yeah, I guess it's understandable...
Thanks for the info...
....!!!!PLEASE ONLY POST ABOUT XPOSED AND MODULES YOU ARE USING ON AT&T STOCK FIRMWARE NOT THE UNLOCKED U FIRMWARE AS THERE MAY BE DIFFERENCES IN EXPERIENCE AND USABILITY THAT MAY CAUSE PROBLEMS!!!!....
This thread is for anyone to posted what Xposed modules you use and if they are or are not working. It will also be a thread to let others see who are new to xposed or havent used it on their s7 edge yet what is and isn't working as well as identifying what modules should be avoided because they are causing problems with the phone ex. lag, freezing, bootloops, other. please comment what you are using along with your experience and any news related to xposed and or modules. i will (when i have time) edit this post with what i have installed what does and doesnt work as well as posting what others put here. of course there will be a working and not working section that will be updated when things break or become useable. hope this thread helps some people out and saves some time and trouble.
....AGAIN!!!!PLEASE ONLY POST ABOUT XPOSED AND THE MODULES YOU ARE USING ON STOCK AT&T FIRMWARE ONLY AS THERE CAN BE DIFFERENCES BETWEEN WHAT DOES AND DOESNT WORK ON STOCK FIRMWARE AND THE UNLOCKED U FIRMWARE!!!!....
....WORKING MODULES ARE IN POST #2....
....modules that work for me and or others....will be update as i use working modules or people post or pm working modules....i will not be including modules that do not work just to save time and space. At this point in time just assume it doesnt work unless someone can confirm it, dont want to kill your phone!!!!....
1. Greenify
2. Amplify
3. Xtouchwiz (turned some setting off that were on by default!!!! Fake system status i'm guessing is best turned off!!!!)
4. Neopower menu
rob219 said:
****ONLY ANPLIFY AND GREENIFY ARE WOTKING OUT OF THE ONES I HAVE INSTALLED IN THE PICS, ALL THE OTHER MODULES SHOWN ARE NOT WORKING AS OF NOW ON MY DEVICE****
Click to expand...
Click to collapse
Did you have any luck with RootCloak or XTouchWiz?
TehPirate_ said:
Did you have any luck with RootCloak or XTouchWiz?
Click to expand...
Click to collapse
rootcloak im unsure as i have uninstalled it (didnt need it) and xtouchwiz i hacent retried. something (maybe a setting in xtouchwiz) was giving me some sim card pop up that wouodnt go away on boot and wouod make me reboot to recovery to do something to ky sim that just failed and the pop up would be there upon boot. i had to odin to get rid of it. it happened 3 times and each time it happened i had rootcloak and xtouchwiz installed. since removing both i hacent had a problem. so no i didnt and i believe one of them caused the problem. if anyone is using both or one or the other let me know what you do and dont have enabled or disabled in each module.
rob219 said:
rootcloak im unsure as i have uninstalled it (didnt need it) and xtouchwiz i hacent retried. something (maybe a setting in xtouchwiz) was giving me some sim card pop up that wouodnt go away on boot and wouod make me reboot to recovery to do something to ky sim that just failed and the pop up would be there upon boot. i had to odin to get rid of it. it happened 3 times and each time it happened i had rootcloak and xtouchwiz installed. since removing both i hacent had a problem. so no i didnt and i believe one of them caused the problem. if anyone is using both or one or the other let me know what you do and dont have enabled or disabled in each module.
Click to expand...
Click to collapse
I appreciate your feedback. It would be inaccurate for me to reply with mine as I use the unlocked firmware. But in this case, the results were the same more or less.
TehPirate_ said:
I appreciate your feedback. It would be inaccurate for me to reply with mine as I use the unlocked firmware. But in this case, the results were the same more or less.
Click to expand...
Click to collapse
i have since installed xtouchwiz and have no problems i turned a few things off that were on by default. i turned off fake system status and the disable scaling feature that was on. it works. rootcloak i have also reinstalled but i don't think it works. im not sure, i know snapchat has problems logging in if your rooted and i am experiencing this problem with or without rootcloak so i believe it is not working but i could be wrong.
Hi, I am new to xda and Android as a whole. So I have rooted (SM-G935A) and I can't find any way to install xposed because TWRP doesnt support the snapdragon variants. Do you mind telling me how you did it?
RileyIssKing said:
Hi, I am new to xda and Android as a whole. So I have rooted (SM-G935A) and I can't find any way to install xposed because TWRP doesnt support the snapdragon variants. Do you mind telling me how you did it?
Click to expand...
Click to collapse
flashfire
i Am using motorola droid turbo android 6.0 reserrection remix rom.
Is there any way i can do wifi calling using custom rom?
bilalrajput said:
i Am using motorola droid turbo android 6.0 reserrection remix rom.
Is there any way i can do wifi calling using custom rom?
Click to expand...
Click to collapse
https://youtu.be/nF_lJTGKFP0
TheSt33v said:
https://youtu.be/nF_lJTGKFP0
Click to expand...
Click to collapse
I'm limited to 8 thanks per day. I'll come back later.
TheSt33v said:
https://youtu.be/nF_lJTGKFP0
Click to expand...
Click to collapse
The only thing that would have been better is this one...
https://www.youtube.com/watch?v=xoMgnJDXd3k
rnwalker7 said:
The only thing that would have been better is this one...
https://www.youtube.com/watch?v=xoMgnJDXd3k
Click to expand...
Click to collapse
I'm making it a personal goal to respond to as many questions with youtube videos as possible.
I use Google Hangouts and their add-on app for WiFi calls. Have to have Google voice number to do this.
Sent from my MetroPCS Turbo
Ok a simple question
I am on stock official 6.0.1
I can't find wifi calling option :/
Where to find it and how to make a wifi call?
Sparksys said:
Ok a simple question
I am on stock official 6.0.1
I can't find wifi calling option :/
Where to find it and how to make a wifi call?
Click to expand...
Click to collapse
Advanced calling menu
It's not there..no advanced calling menu anywhere
I'm on computer freeks mm.1.0.4 stock based ROM
It's under advanced calling as mentioned.
Not for me :/
Has anyone had any issues running wifi calling in airplane mode? I'm using stock marshmallow with unlocked bootloader, xposed, and twrp. Performed a factory reset and tried to make a wifi call in airplane mode and got the error that airplane mode needs to be turned off. Just wondering if anyone has seen this issue and how best to resolve it.
Hyperbomb64 said:
Has anyone had any issues running wifi calling in airplane mode? I'm using stock marshmallow with unlocked bootloader, xposed, and twrp. Performed a factory reset and tried to make a wifi call in airplane mode and got the error that airplane mode needs to be turned off. Just wondering if anyone has seen this issue and how best to resolve it.
Click to expand...
Click to collapse
I see the same behavior. I'm also unlocked, rooted with twrp. No exposed though.
Sent from my XT1254 using Tapatalk
Hyperbomb64 said:
Has anyone had any issues running wifi calling in airplane mode? I'm using stock marshmallow with unlocked bootloader, xposed, and twrp. Performed a factory reset and tried to make a wifi call in airplane mode and got the error that airplane mode needs to be turned off. Just wondering if anyone has seen this issue and how best to resolve it.
Click to expand...
Click to collapse
Have you tried turning Wi-Fi back on after Airplane mode turns it off?
Airplane mode turns OFF Wi-Fi.
https://www.howtogeek.com/194421/what-does-airplane-mode-do-and-is-it-really-necessary/
Enabling airplane mode always disables Wi-Fi. However, on most devices, you can enable Wi-Fi after enabling airplane mode. Cellular signals will still be blocked, but Wi-Fi will be working so you can connect to that in-flight Wi-Fi network. Some devices also allow you to enable Bluetooth when airplane mode is enabled.
Click to expand...
Click to collapse
Yeah tried that.
Would there be any way to turn off the radio other than using airplane mode? Also does this feature actually work using verizon wifi calling built into marshmallow?
Sent from my XT1254 using Tapatalk
So it seems that flashing SuperSU causes wifi calling to stop working. I flashed stock recovery and firmware, downloaded the new OTA, flashed TWRP and wifi calling continued to work. As soon as I flashed SuperSU it stopped. Anyone stock and rooted that has wifi calling working?
Hyperbomb64 said:
So it seems that flashing SuperSU causes wifi calling to stop working. I flashed stock recovery and firmware, downloaded the new OTA, flashed TWRP and wifi calling continued to work. As soon as I flashed SuperSU it stopped. Anyone stock and rooted that has wifi calling working?
Click to expand...
Click to collapse
What version of SuperSu did you use? And if it was the older beta 2.62, did you then update it to the latest version afterwards?
First way I tried was the bets 2.62 to see if it would work. When it didn't I restored my nandroid backup and then flashed beta 2.62 then 2.79 per TheSt33v's guide (select the beta zip then select add more zips and select the latest).
Hyperbomb64 said:
First way I tried was the bets 2.62 to see if it would work. When it didn't I restored my nandroid backup and then flashed beta 2.62 then 2.79 per @TheSt33v's guide (select the beta zip then select add more zips and select the latest).
Click to expand...
Click to collapse
Not to contradict him... but when you flash the beta SuperSu to do intitial root for this finicky version of Motorola Marshmallow firmware, you should then reboot to your desktop make sure it works -- that you actually have root -- then reboot back into recovery and flash the newer SuperSu.
In my opinion, that's the best way. Yes, there are many times I consecutively flash zipped files in TWRP, but flashing two vastly different versions of SuperSu is not one of them.
Hyperbomb64 said:
First way I tried was the bets 2.62 to see if it would work. When it didn't
Click to expand...
Click to collapse
Are you saying flashing that beta SuperSu WILL didn't root your phone or didn't allow Wi-Fi calling to work? That version of SuperSu WILL root your phone -- but you will just need to update to newest version afterward.
I've attached that beta SuperSu to this post.
ChazzMatt said:
Not to contradict him... but when you flash the beta SuperSu to do intitial root for this finicky version of Motorola Marshmallow firmware, you should then reboot to your desktop make sure it works -- that you actually have root -- then reboot back into recovery and flash the newer SuperSu.
In my opinion, that's the best way. Yes, there are many times I consecutively flash zipped files in TWRP, but flashing two vastly different versions of SuperSu is not one of them.
Are you saying flashing that beta SuperSu WILL didn't root your phone or didn't allow Wi-Fi calling to work? That version of SuperSu WILL root your phone -- but you will just need to update to newest version afterward.
I've attached that beta SuperSu to this post.
Click to expand...
Click to collapse
I have done both ways meaning flashed beta version of SuperSU, booted, confirmed that I have root, then update. Also I have flashed both and can confirm that I still have root.
So I'll run through it again and check, but I should be able to flash stock firmware, check if wifi calling is working, flash Beta SuperSU, confirm that phone is rooted, update to latest SuperSU, then check if wifi calling is working. Would those steps be correct?
Sent from my XT1254 using Tapatalk
Hello everyone. I have created this thread (hopefully in the right place) to start a discussion on methods/developing methods to get fortnite to work on a rooted device, with magisk installed. Im currently running Dr. Ketan's rom (android pie) on a samsung galaxy note 9 and for obvious reasons (the fortnite galaxy skin) would like to play a few games and have it work without any hiccups. Im not looking to hack the game or any nonsense like that, so if anyone has a currently functioning method that doesnt require me to reflash stock firmware (as i dont have a pc and had to use a friends to unlock bootloader and such) and play on the unrooted device then re-root and install custom rom
evan5935 said:
Hello everyone. I have created this thread (hopefully in the right place) to start a discussion on methods/developing methods to get fortnite to work on a rooted device, with magisk installed. Im currently running Dr. Ketan's rom (android pie) on a samsung galaxy note 9 and for obvious reasons (the fortnite galaxy skin) would like to play a few games and have it work without any hiccups. Im not looking to hack the game or any nonsense like that, so if anyone has a currently functioning method that doesnt require me to reflash stock firmware (as i dont have a pc and had to use a friends to unlock bootloader and such) and play on the unrooted device then re-root and install custom rom
Click to expand...
Click to collapse
Uhh. Its already working. Atleast for me. You just need to hide magisk manager , hide Fortnite app and installer on magisk hide tab, disable usb debugging, and make sure there isn't magisk named folder or files inside your internal storage. That should do it. I'm on the note 8 and it works just fine
white7561 said:
Uhh. Its already working. Atleast for me. You just need to hide magisk manager , hide Fortnite app and installer on magisk hide tab, disable usb debugging, and make sure there isn't magisk named folder or files inside your internal storage. That should do it. I'm on the note 8 and it works just fine
Click to expand...
Click to collapse
Dang, really? Thanks man!
evan5935 said:
Dang, really? Thanks man!
Click to expand...
Click to collapse
Yep!! Its working on mine ....
white7561 said:
Yep!! Its working on mine ....
Click to expand...
Click to collapse
Its not workin for me bro, i hide magisk manage, have no folders or files named makgisk, or even have magisk in the name, hide the root apps with magisk as well as the fortnite installer and app before i launch each of them. It just deosnt work for me :'(
Are you running in magisk core mode, with adb/root disabled as well?
And what about USB/ADB Debugging? Have you turned that off as well?
white7561 said:
Yep!! Its working on mine ....
Click to expand...
Click to collapse
Didgeridoohan said:
And what about USB/ADB Debugging? Have you turned that off as well?
Click to expand...
Click to collapse
Yes but developer options is still on, does that make a difference? Also, I have not tried with magisk core mode off and root disabled, so if you are doing that then that may also be my issue
Edit: i turned on magisk core mode and disabled root and still does not work. Would having lucky patcher installed be an issue?
evan5935 said:
Yes but developer options is still on, does that make a difference? Also, I have not tried with magisk core mode off and root disabled, so if you are doing that then that may also be my issue
Edit: i turned on magisk core mode and disabled root and still does not work. Would having lucky patcher installed be an issue?
Click to expand...
Click to collapse
Prob yeah ...
white7561 said:
Prob yeah ...
Click to expand...
Click to collapse
Definitely was the issue. Deleted lucly patcher and also the Xposed installer (even though exposed isnt on Pie yet) and that combined with everything else did the trick
evan5935 said:
Definitely was the issue. Deleted lucly patcher and also the Xposed installer (even though exposed isnt on Pie yet) and that combined with everything else did the trick
Click to expand...
Click to collapse
Yep. Also . No xposed . Since it fails the safety net [emoji4]. Well. Happy gaming!! [emoji4][emoji4][emoji4]
Working still Season 9 Magisk 19.1? Not I
Anybody still using this method? I get all the way to the drop then get kicked out "can't sync user profile"
Magisk is hidden in a random folder, installer and game both hidden. Tried with Developer settings off and also with them on. Rooted.
Even Google Pay works so I'm head scratching here if there is a system processes that is now needing hidden or what to play the newest Beta. All help appreciated.
I have the same problem. Google pay is working but fortnite not
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Chuck_C said:
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Click to expand...
Click to collapse
Curious what was your setup? To have it work?
Pvt WhoOkid said:
Curious what was your setup? To have it work?
Click to expand...
Click to collapse
Stock OnePlus 7 pro with magisk and TWRP. Epic launcher and Fortnite both hidden in magisk hide. USB debugging turned off. No modules installed. Just using it for root. Worked fine until last night. Gpay and all other safety net apps work fine. It's just Fortnite. Logged in on a friend's Xbox and a really laggy ipad and could play on both so it's not my account - it's definitely the rooted phone and magisk no longer hides itself from Fortnite.
I'm really irritated with the whole thing because I was so close to finishing the season pass and now I can't play at all.
Here's another fix. These last few updates they have added more things to the blacklist. So remember that they basically scans the internal sdcard etc for MagiskManager folder right? Well now they scan TWRP folder too!! So try renaming it to something else without TWRP in it. And see if it works!. Just tried mine and still working just fine!
white7561 said:
Here's another fix. These last few updates they have added more things to the blacklist. So remember that they basically scans the internal sdcard etc for MagiskManager folder right? Well now they scan TWRP folder too!! So try renaming it to something else without TWRP in it. And see if it works!. Just tried mine and still working just fine!
Click to expand...
Click to collapse
Thanks for posting that. I renamed the folder and now it works again.
Now I need to figure out if I can leave it that way or if I need to keep switching the folder name back and forth to be able to use TWRP correctly.
Chuck_C said:
I'm on a rooted OnePlus 7 Pro and mine just stopped working yesterday. Was fine for about an hour after the Star Wars event then logged on around 10pm and I get kicked out as soon as I exited the bus. Keeps happening over and over again. No other software changes so I'm guessing there needs to be some update to Magisk to get it working again.
Click to expand...
Click to collapse
I have pretty much the same setup as you. Do you happen to get lag here and there? During game play? I was able to get mine working again by renaming the folder for trwp as suggested.
Chuck_C said:
Thanks for posting that. I renamed the folder and now it works again.
Now I need to figure out if I can leave it that way or if I need to keep switching the folder name back and forth to be able to use TWRP correctly.
Click to expand...
Click to collapse
With Tasker or Automate, you can set a trigger to automatically rename folder on start of Fortnite and rename back, after the game is closed.