Atlast I got a way to turn on wifi calling on Moto E4 plus. I tried it on nicklaus, it also works on owens.
So to do it you need magisk root(>19v).
After magisk installation is done, go to this link and download the latest voenabler module:
https://github.com/edgd1er/voenabler/releases
This is a magisk module for enabling volte and vowifi created by edgd1er(thanks to him for creating this module).
So after downloading it, put it into your phone and open Magisk manager app and go to modules section->click +(add)->go to the directory where you saved voenabler module and select it and magisk will install it.
Then do a reboot
Now if you go to settings->more->you will see wifi calling. Toggle it on and select wifi preferred. And thats it...now wifi calling is on.
If you're facing stability issues (like no incoming calls on wifi calling), then you may have to change your stock kernel and install a custom kernel.
This technique works on all roms(stock, custom).
It worked perfectly for me. So feel free to ask any questions, if you stuck in any step.
SreyasXd said:
Atlast I got a way to turn on wifi calling on Moto E4 plus. I tried it on nicklaus, it also works on owens.
So to do it you need magisk root(>19v).
After magisk installation is done, go to this link and download the latest voenabler module:
https://github.com/edgd1er/voenabler/releases
This is a magisk module for enabling volte and vowifi created by edgd1er(thanks to him for creating this module).
So after downloading it, put it into your phone and open Magisk manager app and go to modules section->click +(add)->go to the directory where you saved voenabler module and select it and magisk will install it.
Then do a reboot
Now if you go to settings->more->you will see wifi calling. Toggle it on and select wifi preferred. And thats it...now wifi calling is on.
If you're facing stability issues (like no incoming calls on wifi calling), then you may have to change your stock kernel and install a custom kernel.
This technique works on all roms(stock, custom).
It worked perfectly for me. So feel free to ask any questions, if you stuck in any step.
Click to expand...
Click to collapse
Hi @SreyasXd, I have the exact same phone. I tried to install the Wifi Calling from the play store. The app It lets me enable that feature, but it doesn't stick. This is my main phone and I use it frequently, I can't risk stability issues with it. How has it been working for you since? Thank you.
zspeciman said:
Hi @SreyasXd, I have the exact same phone. I tried to install the Wifi Calling from the play store. The app It lets me enable that feature, but it doesn't stick. This is my main phone and I use it frequently, I can't risk stability issues with it. How has it been working for you since? Thank you.
Click to expand...
Click to collapse
It works well, there would be no stability issues whatsoever if you do the process right. Just follow this
as it is and get your phone rooted with magisk, then download and add the module provided above. You will have wifi calling working.
Important: Your carrier must support wifi calling
Related
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.
Hi guys,
I have a OnePlus 3T.
So I updated to beta 17 to look at Oreo but found cellular data wouldn't connect, internet connection. I have 2 sim cards on different networks and neither worked. After playing around with the APN settings, googling and trying a few things I came to the conclusion that the DNS settings were wrong and if I used an app called DNS Changer which runs as a VPN with Google DNS settings I would be able to access the Internet again. WiFi works perfectly without the need for the app.
Anyway, I didn't like that idea so I went back to the stable Oxygen OS 7.1.1 that's on the OnePlus website and I'm still having the same issues.
I know if I root my phone I can manually change the dns for cellular in a file on root but I don't want to root my phone because my NFC banking apps won't work. Is there another way to fix this? Have I installed the incorrect version on the ROM from OnePlus? Stupid me didn't back up.
I live in Australia and am connected with Virgin Mobile (RSP Optus) and second sim is Telstra.
Rooting with magisk is not a problem. You can access banking apps with magisk. Read the thread of magisk.
Moreover after rooting you can customize so many things, No need to explain...........
Hey,
If you don't want to root your device, you can do a clean flash of OB17. This may fix your DNS issue.
Have you tried using your SIM in another device?, to see if it's a carrier compatibility issue with your phone.
On a different subject, you should try Magisk, which roots your device systemlessly, that is installing root without affecting the /system partition.
Magisk 14.0 Stable : https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Magisk 14.3 Beta : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
Magisk does not work on the 3T Open Beta 17 as of yet, but the developer, topjohnwu, is working on it (https://twitter.com/topjohnwu/status/925732785821704192)
You can also use Modules which add more features, so try using Magisk for your banking apps. I can confirm that Android Pay works.
Cheers!
Thanks for your help guys... Yeah I did a clean install of both B17 and 7.1.1 and this is where I got the issues... I will try magisk tonight and let you know. I have rooted my phones in the past but I have been using NFC payments on my phone so much it's one thing I don't want to loose. I don't take a wallet out anymore
I've seen a few threads on the Blackberry Work app, but they all seemed have become idle at the end of 2017. Has anyone been able to run new versions of Blacberry Work with the new versions of Magisk?
I'm running an unrooted custom ROM, but the way new versions of the ROM are compiled (using Android Clang) are triggering the checker. Was hoping I could flash Magisk to hide root and custom rom detection from the app.
It depends on what the app is detecting, of course, but take a look under "Hiding root from apps" in the troubleshooting guide. The rest of the post might have some useful tips as well.
I ended up installing Magisk and hiding from the app. It works really well, so we can go ahead and close this thread. Thanks for the follow up.
napes22 said:
I ended up installing Magisk and hiding from the app. It works really well, so we can go ahead and close this thread. Thanks for the follow up.
Click to expand...
Click to collapse
Is BB Work still working for you with Magisk? Our company moved to BB Good (now Work) years ago. I stopped rooting back then since it was too much of a hassle to figure out and I need to have my work email. If this works, the only thing holding me back would be getting official updates from OnePlus. I have the 5T.
jvnat said:
Is BB Work still working for you with Magisk? Our company moved to BB Good (now Work) years ago. I stopped rooting back then since it was too much of a hassle to figure out and I need to have my work email. If this works, the only thing holding me back would be getting official updates from OnePlus. I have the 5T.
Click to expand...
Click to collapse
Yes I can confirm that magisk root does work with BB Work. You have to use the "hide" function in the Magisk Manager and select BB work.
FYI
I am using a stock rom with root.
Tip: don't use xposed framework if you want a working BB work app.
I flashed Magisk in my redmi note 3 kate and installed the magisk manager apk app, everything is working fine, but my question is: Should I install phhSuperUse, rather than this variant has SU because it was built to be installed with magisk ?
Excuse me, I'm not very familiar with the subject and I've been reading about this and I'm a little confused
---------- Post added at 10:22 PM ---------- Previous post was at 10:20 PM ----------
What is the difference when using the magisk modules?
always use xposed framework plus S.U. But since I can no longer download some apps in play store I have resorted to install magisk on my device.
Hello,
Is it still working ?
It work with Good for Enterprise , but i am not able to install UEM Client and BB Work ?
UEM Client seems fine and show device as unrooted but then setting up Blackberrry Dynamics failed due to that , any idea ?
Regards,
Darkwa said:
Yes I can confirm that magisk root does work with BB Work. You have to use the "hide" function in the Magisk Manager and select BB work.
FYI
I am using a stock rom with root.
Tip: don't use xposed framework if you want a working BB work app.
Click to expand...
Click to collapse
I have a message bb work data wiped. And installation fails at the last point. How can I solve it?
Greetings
Wysłane z mojego MI 6 przy użyciu Tapatalka
As of yesterday, blackberry is detecting my root for some reason. Nothing has changed so my guess is that it has something to do with my company's policy changing? At this point I'm very confused
napes22 said:
As of yesterday, blackberry is detecting my root for some reason. Nothing has changed so my guess is that it has something to do with my company's policy changing? At this point I'm very confused
Click to expand...
Click to collapse
I am in the same boat. I can no longer get Magisk 18.0 and BB Work (or any of the BB enterprise apps) to function. I immediately get the "jailbroken" message. I have no idea what changed. :crying:
I am going to try 18.1 and will report if things change.
DaCHeF36 said:
I am in the same boat. I can no longer get Magisk 18.0 and BB Work (or any of the BB enterprise apps) to function. I immediately get the "jailbroken" message. I have no idea what changed. :crying:
I am going to try 18.1 and will report if things change.
Click to expand...
Click to collapse
Magisk 18.1, Manager 7.0, and following this guide is what works:
https://www.didgeridoohan.com/magisk/MagiskHide
Make sure the "Basics" are taken care of, manually.
Hide Magisk Manager package under settings, MagiskHide "Work" only now (no "Work Profile" choice present in the new version). I removed all root-requiring apps. The combo here worked. I may go one by one to see if any of those apps made a difference. Regardless, it works following those instructions. Good luck. :good:
DaCHeF36 said:
Magisk 18.1, Manager 7.0, and following this guide is what works:
https://www.didgeridoohan.com/magisk/MagiskHide
Make sure the "Basics" are taken care of, manually.
Hide Magisk Manager package under settings, MagiskHide "Work" only now (no "Work Profile" choice present in the new version). I removed all root-requiring apps. The combo here worked. I may go one by one to see if any of those apps made a difference. Regardless, it works following those instructions. Good luck. :good:
Click to expand...
Click to collapse
Perfection, thanks so much. Running DU on taimen with Magisk 18.1 substratum TitaniumBackup Franco app. All good!
Sent from my Pixel 2 XL using Tapatalk
Blackberry Appstore
bigknowz said:
Perfection, thanks so much. Running DU on taimen with Magisk 18.1 substratum TitaniumBackup Franco app. All good!
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
@DaCHeF36 Spoke too soon, not able to load BB Access or Appstore, thoughts?
bigknowz said:
@DaCHeF36 Spoke too soon, not able to load BB Access or Appstore, thoughts?
Click to expand...
Click to collapse
I'm not sure about the Appstore, but I am stuck at an "Authenticating" screen for Access. If I make any progress I'll let you know.
Canary
DaCHeF36 said:
I'm not sure about the Appstore, but I am stuck at an "Authenticating" screen for Access. If I make any progress I'll let you know.
Click to expand...
Click to collapse
Everything works on Canary, running 18100.
bigknowz said:
Everything works on Canary, running 18100.
Click to expand...
Click to collapse
Magisk 19.0 and the new 7.1.1 Manager combination seem to work with all BB apps. Maybe it's just me, but the Work Profile option returned in Hide.
Are there any dependencies for BB apps we need to also hide from Magisk?
DaCHeF36 said:
Magisk 19.0 and the new 7.1.1 Manager combination seem to work with all BB apps. Maybe it's just me, but the Work Profile option returned in Hide.
Click to expand...
Click to collapse
I only need to use the BB work app, are you hiding any other app except BB Work ? Also,a) are you hiding the Magisk Manager, b)using Magisk Hide to hide BB Work or c)doing both?
TarunN5 said:
I only need to use the BB work app, are you hiding any other app except BB Work ? Also,a) are you hiding the Magisk Manager, b)using Magisk Hide to hide BB Work or c)doing both?
Click to expand...
Click to collapse
Work and Work profile setup are hidden. Work profile setup is definitely there again. I use Access, Tasks, and Connect too. I have them all hidden even though that may be overkill. I hide Magisk Manager using the built in package option too. I also followed the guide to ensure that all settings like debug, etc. were off. Gold. I excluded the BB apps from auto-updating. I don't plan to upgrade them unless the back-end requires it at some point.
DaCHeF36 said:
Work and Work profile setup are hidden. Work profile setup is definitely there again. I use Access, Tasks, and Connect too. I have them all hidden even though that may be overkill. I hide Magisk Manager using the built in package option too. I also followed the guide to ensure that all settings like debug, etc. were off. Gold. I excluded the BB apps from auto-updating. I don't plan to upgrade them unless the back-end requires it at some point.
Click to expand...
Click to collapse
Thanks, can you please tell me what exactly do you mean by "work profile" and "work profile setup". The app I see is i dont see a work profile app in the play store either. Can you also please send a screenshot of the BB apps that you have hidden in Magisk? This is the first time I'm using BB on my phone so pardon my noobness
On my phone xiaomi A1 rooted it works on the wife's phone xiaomi note 5 pro rooted it used to work fine but for some reason it has suddenly detected root and won't work now. I have checked all the settings to do with hiding are still selected as before, strange thing is it has worked briefly for a few seconds but then stopped again.
Please can people tell me if they have had this happen and how they fixed it please.
What checks is it doing to detect root does anyone know?
Thanks
hycraig said:
On my phone xiaomi A1 rooted it works on the wife's phone xiaomi note 5 pro rooted it used to work fine but for some reason it has suddenly detected root and won't work now. I have checked all the settings to do with hiding are still selected as before, strange thing is it has worked briefly for a few seconds but then stopped again.
Please can people tell me if they have had this happen and how they fixed it please.
What checks is it doing to detect root does anyone know?
Thanks
Click to expand...
Click to collapse
Try updating magisk.
Try to disable xposed modules.
Try to disable all modules.
See if it works now.
Then one by one reenable them.
Sent from my SM-G985F using Tapatalk
vash_h said:
Try updating magisk.
Try to disable xposed modules.
Try to disable all modules.
See if it works now.
Then one by one reenable them.
Sent from my SM-G985F using Tapatalk
Click to expand...
Click to collapse
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
hycraig said:
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
Click to expand...
Click to collapse
Credits Google
Now safetynet fails after March update
You need to change device props to pixel or lock bootloader
hycraig said:
Thanks for your reply magisk is up to date and I don't have any modules just magisk on its own. I do find it strange how it just stopped working after many months of being used regularly.
Click to expand...
Click to collapse
Biggest_Noob said:
Credits Google
Now safetynet fails after March update
You need to change device props to pixel or lock bootloader
Click to expand...
Click to collapse
My safteynet passes fine on both my devices
Thanks
somehow they manage to detect root even if magisk manager is running under custom package name and magisk hide is enabled.
Last version that is still running is 13.1.1 (apk available on apkmirror).
h4lli said:
somehow they manage to detect root even if magisk manager is running under custom package name and magisk hide is enabled.
Last version that is still running is 13.1.1 (apk available on apkmirror).
Click to expand...
Click to collapse
thanks @h4lli i couldn't see sky go version 13.1.1 for uk
so i got Sky Go UK 12.4.14 from apkmirror and can confirm is working fine
yeah still doesnt work, latest sky go app 20, latest magisk, still detects, anyone able to reverse the sky app to see what methods its using?
Fyi - any version other than the latest (20.6.1) at the moment forces an upgrade to 20.6.1, which then detects root.
Safety net is passing both basic and cts with Eval type basic. I'm on latest canary (20425).
I've tried :-
Uninstalling all apps that skygo could look for (titanium, openvpn etc.)
Using a work profile (shelter and island)
Disabling oem unlocking
Disabling usb/adb debugging
Disabling developer options
Deleting all files and folders that have magisk, twrp or titanium in them.
Basically everything here https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
So, I think it's basically no go for sky go at the moment. Happy to be corrected if someone has it working.
Beardy
beardymarrow said:
Fyi - any version other than the latest (20.6.1) at the moment forces an upgrade to 20.6.1, which then detects root.
Safety net is passing both basic and cts with Eval type basic. I'm on latest canary (20425).
I've tried :-
Uninstalling all apps that skygo could look for (titanium, openvpn etc.)
Using a work profile (shelter and island)
Disabling oem unlocking
Disabling usb/adb debugging
Disabling developer options
Deleting all files and folders that have magisk, twrp or titanium in them.
Basically everything here https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
So, I think it's basically no go for sky go at the moment. Happy to be corrected if someone has it working.
Beardy
Click to expand...
Click to collapse
Yeah still can't get it working. Damn it.
Hast everyone a sollution for running the sky Go App on rooted phones?
Skygo doesnt Work... hast anyone a sollution?
eula1977 said:
Skygo doesnt Work... hast anyone a sollution?
Click to expand...
Click to collapse
Have you tried this? It worked for me
SkyGo app detected root!
Hi everyone i have a problema using SkyGo app on my device because It detects the root. I renamed magisk , used magisk Hide , tried magiskhide props config , tried to delete cache and re-install SkyGo app but nothing worked...any solution...
forum.xda-developers.com
I switched from MIUI 12.0.4 to Pixel Experience (28 Dec 2020 build) running on Android 11. The hotspot worked fine initially. Then I installed Magisk, Viper and AML (audio modification library). Now whenever I turn hotspot on, it turns off and it's written "error" on the hotspot screen. I tried uninstalling, restarting, factory reset and changing timeout, but nothing worked. Hiding Magisk didn't seem to work either. Changing the hotspot names and settings didn't help either. Tethering seems to work fine. Please help.
Edit: So, after much investigation I found that Viper4Android is the culprit. Whenever I install it, hotspot doesn't work. Is there a way to fix this?
Hotspot and Wifi doesnt work if you flash V4A. You need to flash a custom kernel. All custom kernels support V4A. But I cant recommend one as I am using stock. You need to check with others about custom kernels.
Saswata Chakraborty said:
Hotspot and Wifi doesnt work if you flash V4A. You need to flash a custom kernel. All custom kernels support V4A. But I cant recommend one as I am using stock. You need to check with others about custom kernels.
Click to expand...
Click to collapse
Yeah. Immensity worked for me