Ok I guess this has been talked before but I can't find it, anyways I'm running the latest stock version of Android and ever since I rooted and unlocked my bootloader I haven't been able to get if to work.. Am I missing something or does it get disabled?
Cobra11Murderer said:
Ok I guess this has been talked before but I can't find it, anyways I'm running the latest stock version of Android and ever since I rooted and unlocked my bootloader I haven't been able to get if to work.. Am I missing something or does it get disabled?
Click to expand...
Click to collapse
did you enble it? check out the phone settings.
Yup I did, I should of mentioned that while ago, seems it tries then stops really quick I restarted the router thinking that could be it, but nothing
root must disable it I guess?
Cobra11Murderer said:
root must disable it I guess?
Click to expand...
Click to collapse
nope. im rooted, and tmobiles wifi calling works fine here.
Having the same issues here. Flashed the 'V' update and verified that wi-fi calling was working. Flashed root and TWRP through wugfresh's app and wifi-calling stopped working. I'm assuming that the new stock kernel was updated so that if the device was rooted it would break wi-fi calling.
---------- Post added at 01:35 PM ---------- Previous post was at 12:49 PM ----------
goinflyn said:
Having the same issues here. Flashed the 'V' update and verified that wi-fi calling was working. Flashed root and TWRP through wugfresh's app and wifi-calling stopped working. I'm assuming that the new stock kernel was updated so that if the device was rooted it would break wi-fi calling.
Click to expand...
Click to collapse
flashed back to the 'Q' version and again restored wifi calling. Flashed supersu 2.67 and twrp 3.0.0.0 and lost wifi calling. BTW this setup was working prior to me flashing the update previously. I'm going to try a different version of supersu and see what happens.
I'm on the V build, rooted, and T-Mo WiFi calling works fine.
When you say WiFi calling is not working, is the wifi calling verbiage not showing up in notification area? Or does it show WiFi calling, but calls are not going thru when on WiFi?
Related
I have the Verizon (locked bootloader) version of the Moto X, rooted on 4.4. Today, my tethering stopped working. I can enabled it on the phone with no issues, but no devices seems to be able to find it. I tried changing the SSID and password, but still no luck. Has anyone else had this issue and maybe could point me in a direction to fix it? Thanks.
alm1ghty said:
I have the Verizon (locked bootloader) version of the Moto X, rooted on 4.4. Today, my tethering stopped working. I can enabled it on the phone with no issues, but no devices seems to be able to find it. I tried changing the SSID and password, but still no luck. Has anyone else had this issue and maybe could point me in a direction to fix it? Thanks.
Click to expand...
Click to collapse
What method are you using?
I use this one: http://forum.xda-developers.com/showthread.php?t=2449534 and haven't had any problems.
GandalfTehGray said:
What method are you using?
I use this one: http://forum.xda-developers.com/showthread.php?t=2449534 and haven't had any problems.
Click to expand...
Click to collapse
I was using the Native Tether with Moto Tether for Xposed. It had been working fine up until yesterday. I tried your method, and it's working. I'm not sure why the native method just stopped working.
alm1ghty said:
I was using the Native Tether with Moto Tether for Xposed. It had been working fine up until yesterday. I tried your method, and it's working. I'm not sure why the native method just stopped working.
Click to expand...
Click to collapse
All I can tell you is I'm on a VZW Dev Ed with 4.4.2 and my Xposed tethering works fine. In fact I'm native tethered right now to the computer I'm typing this on.
So I did a factory reset and flashed the rooted H811 system image exactly as per instructions from the other thread and everything has been working flawlessly, except my HotSpot. When I try to turn on the Mobile Hotspot, I get a pop-up saying "Unfortunately, WiFi has stopped" and the ON/OFF toggle for the HotSpot stays off. Then, when I try to turn it on again, this time I get a toast notification saying "Activity is not exist this device." So it looks like it's looking for an application that's missing?
EDIT: SOLVED! Do not freeze the Upsell (com.lge.upsell) application, as that's what HotSpot uses to verify your tethering status with T-Mobile, as well as display the first time use tutorial.
It has nothing to do with recovery. It was my own mistake.
No issues for me so far with hotspot. I even have all the apps you listed frozen in TB.
Mine works fine also. Not sure what the problem could be.
now that we are rooted i am using wifi tether router by fabio and it works great. also bypasses tmobiles limit which i believe is 2 gbs or so of tethering. costs 2 bucks but imo its totally worth it
I just tried it on my G4 and didn't have any issues. I'm also on tmobile and rooted.
Sent from my LG-H811 using XDA Free mobile app
Okay, thanks for confirming, guys.
EDIT: I figured it out. Do not freeze the Upsell (com.lge.upsell) application, as that's what HotSpot uses to verify your tethering status with T-Mobile, as well as display the first time use tutorial. It has nothing to do with recovery. It was my own mistake.
siraltus said:
Okay, thanks for confirming, guys.
I figured out what was wrong. I tried flashing TWRP 2.8.7.0 using Flashify (as per instructions in the post!) and I think it flashed the recovery to the wrong partition, wiping its contents. I guess it was a hidden system partition that contained something that HotSpot needed.
I KDZ'd back to stock without wiping user data, then flashed the rooted image, and HotSpot works!
So... DO NOT USE FLASHIFY FOR NOW!
Click to expand...
Click to collapse
I used flasify for twrp and my hotspot still works.
Sent from my LG-H811 using Tapatalk
KJW979 said:
I used flasify for twrp and my hotspot still works.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
I figured it out. Do not freeze the Upsell (com.lge.upsell) application, as that's what HotSpot uses to verify your tethering status with T-Mobile, as well as display the first time use tutorial. It has nothing to do with recovery. Thank you everyone for confirming it was not the recovery. It was my own mistake.
KJW979 said:
I used flasify for twrp and my hotspot still works.
Sent from my LG-H811 using Tapatalk
Click to expand...
Click to collapse
Same here with no issues.
I can't seem to find the com.lge.upsell application, I'm getting this error after typing:
adb shell content insert --uri content://settings/global --bind name:s:tether_dun_required --bind value:i:0
I just want my unlimited tethering back ;__;
Flashed 10n update on my rooted H811, no problems with hotspot. If the other thread you're referencing is from here (http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-10n-stock-rooted-rom-t3188858), it has been updated with a hotspot fix on a separate file.
restoring com.lge.upsell, fixed it for me as well. Thanks,
I have the same problem! After rooting (with 20p debloated unlocked roam), the hotspot is not working with the message "Activity is not exist this device." (verbatim!). The interesting part is that when I installed FoxFi, it worked! Of course it stopped after 15 minutes as it was a freeware. When FoxFi was running, I could see that native Hotspot app showed my mac as a tethered device and everything seemed very natural (besides the blue FoxFi logo on top). On uninstalling FoxFi, native HotSpot app started giving the same error message. I could not find Upsell (com.lge.upsell) app or apk on my phone. Please advise - I would like to continue using the native HotSpot app with my T-Mobile connection. Many thanks!
---------- Post added at 06:16 PM ---------- Previous post was at 06:01 PM ----------
metropical said:
restoring com.lge.upsell, fixed it for me as well. Thanks,
Click to expand...
Click to collapse
Can you share this APK please?
UPDATE: Went to recovery mode using flashify, downloaded zips using Android File Transfer from my mac, Flashed Stock 20p, followed by Extreme 20p (both flashed at the same time) and voila! Tether is back to work and I am giving this update through my phone's tether connection
The speeds are not so great, but I am tempted to blame it on T-Mobile and not on ROM:
The whole research and finding the zip files for 20p took the majority of time. Otherwise, the download itself should take <20 minutes, transferring files <5 min, flashing another 10 minutes and restart of the phone another 5 minutes or so (it is a dirty flash - it only bothered to update some 5 apps!)
I think it is corrupted ROM (I positively remember there was a glitch for whatever reason and i lost all my data - probably the glitch deleted relevant tether files as well). But now it is much easier!!!
Links to the ZIP files that I used:
http://forum.xda-developers.com/tmo...om-lg-g4-h811-20p-stock-rooted-radio-t3477821
http://forum.xda-developers.com/tmobile-g4/development/rom-g4-h811-xtreme-rom-v1-0-7-28-15-t3167667
Many thanks y'all!!!
glad you found your way to it.
this was the issue I had. http://forum.xda-developers.com/showpost.php?p=62060665&postcount=8.
I had uninstalled com.lge.upsell as part of my own try to de-bloat and that was a step too far.
The 1st link you point to is the rom I used and the radio fix and hotpot/tether fix as well.
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.
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
After rooting the wifi just keeps getting disabled and it didn't work even after reverted back to stock,
Is there any solution?
Thanks in advance!
VishV_V said:
After rooting the wifi just keeps getting disabled and it didn't work even after reverted back to stock,
Is there any solution?
Thanks in advance!
Click to expand...
Click to collapse
Did you use the same root image of your version? What's your build number and what's the root file you have used?
also, are you using twrp? twrp breaks wifi with latest update...