I'm on Verizon and don't pay for tether. Before I upgraded to Oreo I could tether, since it was rooted. I've re-rooted and the bootloader is still unlocked. But the native wifi tether no longer works. I've searched and can't seem to find out how to enable it again. Can anyone point me in the direction of how to get tethering working again, please?
Turns out I needed to add the no provisioning line to build.prop:
https://android.gadgethacks.com/how-to/enable-free-wifi-tethering-android-marshmallow-0167832/
Now it's working
Related
I have tried it on 4.0.4 and the most recent version of software for the T-Mobile
I like the features of wifi tether for root users but every time the screen goes out tether stops working
I have the plan thru t-mobile and using their app works but I would like to use WTRU instead.
Any ideas on how to fix that?
Tried a program to lock wake and that didn't work.
Hi all,
I have been unable to tether since upgrading to lollipop. Web pages simply will not load on connected devices.
I have always been able to tether on kitkat, and upon restoring an old backup running kitkat, I am still able to tether, so the problem is definitely lollipop. I've tried adding net.tethering.noprovisiong=true to build.prop, and editing settings.db to no avail.
Has anyone else had this problem? I'm considering switching back to kitkat since tethering is pretty important for me.
Many thanks,
Jack
I haven't had any trouble tethering (T-Mobile, rooted stock 5.0.1).
I recently had my Sprint Note 5 Unlocked. Now I am looking for my hotspot button and its not here. I can manually search for the hotspot and find it in settings. When I turn it on it says its on. But I get no icon on my status bar. I see it in other devices but it will not connect.
Anyone else have this problem or any solutions?
TroyS0326 said:
I recently had my Sprint Note 5 Unlocked. Now I am looking for my hotspot button and its not here. I can manually search for the hotspot and find it in settings. When I turn it on it says its on. But I get no icon on my status bar. I see it in other devices but it will not connect.
Anyone else have this problem or any solutions?
Click to expand...
Click to collapse
Know what you might need to do? Install foxfi, the free version- and then run the hotspot from that app. After that, the config that app sets up might fix your issue.
If that does not work, try to sideload the foxfi key app. Now that is a paid app, so if you want to go through other means to get it that is up to you. Then, use the main foxfi app again. It should work.
I noticed that foxfi has some type of certificate a few years ago, that fixes issues that can come from using root to enable native tethering. It worked then, and it worked for me now on an SM-N920P.
Let me know if it works.
I researched and tried everything I could but running GSM on our CDMA phone simply would never let me increase number of connections above 1. You can change it up to 10 IF you don't care about GSM phone calls and switch the radio to the regular Cdma/lte/auto. I just did that since I did not want or need calls while I was using it as my homes wifi source.
Hello,
I have a carrier unlocked Pixel 2 walleye that is rooted (magisk, no custom recovery) and on Verizon
android version 8.1.0
build #OPM1.171019.021
when I try to activate wifi calling, i get the spinning circle for a long time, and then it finally says "unable to activate wi-fi calling. please try again later"
I have HD voice activated on my verizon wireless account.
I tried the VoEnabler module in Magisk
Wifi calling is turned on in the phone info screen (*#*#4636#*#*)
The only thing i guess i haven't tried is installing a Verizon ROM instead of the stock Google ROM.
Before I went that route, I wanted to check here and see if anyone else was able to get it to work for them.
Thanks in advance.
ok so i had this issue twice on the same phone and i am rooted as well. i think the only way to get it to work is to disable root, activate wifi calling, then reactivate root.
I have enabled this feature while rooted on 2 different PIxel 2's.
This sounds silly but turn off wifi and try to activate it. I've been unable to input my address during the activation process multiple times unless I am on cellular.
thanks for the suggestions everyone. with wifi turned off, it still won't work. I'll try the unroot path next time there is a new system update. It's not a critical need at the moment, but it is rather annoying that i can't activate it.
Schedonnardus said:
thanks for the suggestions everyone. with wifi turned off, it still won't work. I'll try the unroot path next time there is a new system update. It's not a critical need at the moment, but it is rather annoying that i can't activate it.
Click to expand...
Click to collapse
I don't think your problem is related to root unless it's a Magisk module of some kind that's the problem. I'm on Verizon, rooted with Magisk. I haven't had wireless calling turned on but after seeing your post I thought I'd check and see if it works on mine. It connected without any problems for me.
Did you ever figure this out?
Schedonnardus said:
thanks for the suggestions everyone. with wifi turned off, it still won't work. I'll try the unroot path next time there is a new system update. It's not a critical need at the moment, but it is rather annoying that i can't activate it.
Click to expand...
Click to collapse
I'm having a similar issue, except that I can enable wifi calling but always get the "Turn off airplane mode or connect to a wireless network" message when attempting to place a wifi call. Everything with regard to wifi calling is set up correctly. I thought I had this narrowed down to Oreo version and patch level, but I honestly can't come up with a repeatable scenario that breaks it. About all I can say for sure is it seems like when I flash back to bone stock, OPM1.171019.021, wifi calling works as expected. However, it seems to break after a while, even without applying any updates. My gut says it's related to root, but I've also seen it work with root. I also have a suspicion it has something to do with the type of authentication on the wifi network, as the first time I ever saw wifi calling work was when I connected to an open SSID. The problem is, right after that, it worked fine on a WPA2 network on which it never worked before. This is on Verizon with a Pixel 2 from the Google Store. I have a hard time believing it's a Verizon issue, though. It's more like the phone does a check for wifi connectivity and returns "false" for some reason.
*** I should add all my testing has been done by turning on airplane mode (thus disabling LTE/3G) and then enabling wifi. My office at work has horrendous cell coverage, but I haven't gotten it down to zero bars without airplane mode to see if it works then.
I use CWM Tether for usb and Secure Tether for wireless. Both have worked well for me. I have an XA2 bootloader unlocked running Oreo and apps work as they should. I have an XZ2 compact running Pie, bootloader still locked, apps running fine. I have an XZ Premium, bootloader unlocked running Pie and both apps will run but the CWM app will not download ANY data but shows outgoing data. Secure Tether will run but will not pass through data to connected devices, and windows 10 will not see the wifi signal at all, but other phones do. I have tried other firmware from different regions but unless I revert to Oreo and want to deal green pics, nothing seems to help. Even tried the tethering enable module for Magisk....no help. Now, if I want to use the native tether and hotspot apps THEY WORK, but, I'm capped on high speed tether/hotspot data. The two mentioned apps I use don't show up as such. So...any ideas?