You may have noticed, especially if you've got the new Free Wifi Calling feature from T-Mobile, that WiFi Calling is a BATTERY HOG. Worse, it hogs battery even when disabled. You can verify it's Hogginess even when disabled by noting it will almost always be the top APP in history using SystemPanel. It's incredibly badly coded, and if you've got a Rom with Wifi Calling on it, and you've had bad battery life, now you know WHY.
But, really, with the new Free Wifi Calling feature, we shouldn't have to kill it entirely.
You can freeze it with Titanium Backup, but that's a hassle. Likewise using Bloater to uninstall/reinstall it all the time. Wouldn't it be nice just to have a desktop widget to do it for you? Or be able to hook it into your "Home Wifi" profile, so it's always enabled at home, and then have it turned off as soon as you're no longer near your home wifi?
Thanks to user AntonX in this thread , I came across a method to simply kill the app at the system level until needed. Still not convenient. So, I whipped up some Tasker scripts which will help the situation.
This assumes you have Tasker, as well as a basic knowledge of how to use it. Here are your the TASKS to create (Don't create any profiles unless you want to)
You also need to have the Locale Execute plugin, which is free.
NOTE: For this to work correctly, leave the slider set to ENABLE in the wifi calling app, and disable the feature using the Tasker widget and not inside the app!
Create a Task "Disable Wifi Calling"
1. Variable Set %WIFIWASON to YES If %WIFI ~ on
2. Wifi Set Off
3. Wait 5 Seconds If %WIFIWASON ~ YES
4. Execute @!pm disable com.android.kineto
5. Wifi Set On If %WIFIWASON ~YES
6. Variable Clear %WIFIWASON
7. Variable Clear %WIFICALLING
Create a Task: "Enable Wifi Calling"
1. WiFi Set On
2. Plugin:Execute @!pm enable com.android.kineto
3. Wait 5 Seconds
4. Load App Wifi Calling
5. Variable Set %WIFICALLING to YES
Create a Task "Toggle Wifi Calling"
1. Perform Task Disable WIFI Calling If %WIFICALLING ~ YES
2. Perform Task Enable WIFI Calling If %WIFICALLING |~ YES
TO USE:
Add a Tasker Widget to your homescreen for the "Toggle Wifi Calling" task.
What is going on:
Disable script will check if wifi is on at the time it is executed. It has to turn Wifi OFF so we get a clean disconnect from the network and the taskbar Icon goes away before killing the Wifi Calling app. If Wifi was on beforehand, it turns it back on.
Enable script will make sure wifi is enabled, and give it time to connect, and then load the application since sometimes it won't activate on its own without loading manually.
These tasks are intended to be linked to Tasker widgets on your homescreen, but you can call them from location based profiles or whatever.
Now, when Wifi Calling is OFF, it is REALLY off, and not just sitting around, unused, sucking up your battery. With a little more work, this could probably be turned into a single "Toggle" task, but that's an exercise for someone who has slept and doesn't have work in 5 hours. Comments/Improvements welcome.
Update 1:
Added instructions for creating a Toggle widget at the same time.
Streamlined Tasks.
Planned Features:
1. Automatically disable WIFI calling app once WIFI has been disconnected to save battery. Seems to need a block to prevent the state from triggering during processing of the disable/enable tasks, as it breaks functionality. I'm sure it is trivial but I have a limited attention span.
2. Automatically enable WIFI calling app if currently connected to WIFI *and* cell has no signal for longer than a set time. (%CELLSIG)
3. [not possible?] - Audible warning that WIFI signal is getting low and you are currently on a call. Is there any way to read current WIFI signal strength with Tasker?
Very good guide and a great idea.. if only we could get a better coded wifi calling app... or one for cm7
Sent from a cell tower to the XDA server to you.
I love the idea, but I can't quite seem to get it working. When I run the "disable" task, it eventually turns WiFi back on and WiFi calling gets re-enabled.
Then, a while later I get an "app not responding" warning from the Android system for the execute locale plugin (I can select Force Close or Wait).
Also, what is the best way to grant SU permissions to the plugin in the SU application? I have never been prompted to allow it. To test it out, I just temporarily granted access to everything...
Thanks!
lotherius,
I follow on the G2X forums. And you know how the G2x & MIUI Roms can't seem to get Wifi Calling to work consistently. I noticed that if I can get the Wifi Calling app to stay turned OFF it allowed my Sim card to not get the "Invalid Sim" error and then I was able to get wifi calling to work again even after reboots. Do you think by any chance that this script could help cure our Wifi Calling issue with MIUI Roms??? And is there a way to make a flashable zip of this for us Noobs? Thanks Again.
GFam4 said:
lotherius,
I follow on the G2X forums. And you know how the G2x & MIUI Roms can't seem to get Wifi Calling to work consistently. I noticed that if I can get the Wifi Calling app to stay turned OFF it allowed my Sim card to not get the "Invalid Sim" error and then I was able to get wifi calling to work again even after reboots. Do you think by any chance that this script could help cure our Wifi Calling issue with MIUI Roms??? And is there a way to make a flashable zip of this for us Noobs? Thanks Again.
Click to expand...
Click to collapse
Nope, this script wouldn't help with that. The problem on MIUI roms on the G2X is due to the operator (T-Mobile for most) not sending the phone # directly to the SIM card when it is activated. Some SIM cards have it, typically older ones, so it works. Those without, however, find that it doesn't work.
Supposedly you can manually program the SIM by using a phone that supports doing so, but I haven't checked to see if that would fix the problem.
Also I no longer bother with this on the G2X as it appears that while wifi calling still uses *some* battery when not active, it's not the battery hog it was back on the Vibrant.
Lotherius,
I had an HD2 running MIUI with Wifi Calling working before the G2X. The is the hack/mod that this guy TyTung did to get wifi calling to work for the HD2. http://forum.xda-developers.com/showthread.php?t=1038784 You think something like this can be used for the G2X to get wifi calling working?
GFam4 said:
Lotherius,
I had an HD2 running MIUI with Wifi Calling working before the G2X. The is the hack/mod that this guy TyTung did to get wifi calling to work for the HD2. http://forum.xda-developers.com/showthread.php?t=1038784 You think something like this can be used for the G2X to get wifi calling working?
Click to expand...
Click to collapse
WiFi Calling is really picky about the network information being accurate. I'm surprised that they got it working on the HD2...
The best fix for it on MIUI on the G2X would depend on fixing MIUI itself, since the RIL is correct -- the G2X doesn't allow you to change the RIL so it isn't affected. In the case of MIUI, older SIM cards typically work better than new ones.
The issue comes down to the ability to read the network information from the SIM card. If that data has been programmed to your SIM card, then it might work. If it has not been programmed to your SIM card, then it won't work.
So basically... not saying it's impossible to get it working on G2X/MIUI, but it is more likely to require a fix to MIUI rather than to Wifi Calling.
lotherius said:
WiFi Calling is really picky about the network information being accurate. I'm surprised that they got it working on the HD2...
The best fix for it on MIUI on the G2X would depend on fixing MIUI itself, since the RIL is correct -- the G2X doesn't allow you to change the RIL so it isn't affected. In the case of MIUI, older SIM cards typically work better than new ones.
The issue comes down to the ability to read the network information from the SIM card. If that data has been programmed to your SIM card, then it might work. If it has not been programmed to your SIM card, then it won't work.
So basically... not saying it's impossible to get it working on G2X/MIUI, but it is more likely to require a fix to MIUI rather than to Wifi Calling.
Click to expand...
Click to collapse
I wish i knew what Lib's and RIL's that I can swap from a CM7 Rom (Weapon G2X, Eaglesblood, or TSUGI) and push it via Root Explorer. I did this on my Hd2 and had wifi calling working. Can't this method work to get wifi calling working on G2X. Sorry I know this is off topic. But I even had Wifi Calling on your TSUGI ROM. You wouldn't happen to know what Lib's & Ril's on your TSUGI Rom are responsible for Wifi Calling to be enabled?
Is battery life really bad with wifi calling for you guys? I use it nearly 24/7 on my phone, and get fantastic battery life. Like way better than I did without it.
Of course, I'm on the clearly superior HTC G2, but still
I've been toying with this, but anytime I force Wifi calling to disable (by killing the app or disabling kineto), restarting Wifi calling says I'm not registered with the T-Mobile network (sure) and won't connect (even after clicking Register) until I reboot the phone.
Any tips?
This is my first post here, so I made sure I checked the forum for previous issues that may relate to my problem, to no avail (nothing that matches exactly).
Basically, I can't tether anymore, it was working fine last week, but now my other devices will connect, but with "Limited or no Connectivity" (Laptop and iPod Touch). I have a data plan and tethering access through my provider (Rogers in Canada)
Here's is what I have:
Samsung Galaxy S4
Rooted (TWRP installed)
Custom ASOP 4.2.2 ROM installed (DEODEX)
(http://forum.xda-developers.com/showthread.php?t=2341376)
Custom ASOP Kernel
(http://forum.xda-developers.com/showthread.php?t=2342298)
As of this morning, tethering has ceased to function, as stated above, I can enable and my devices can see the network, but they will never acquire internet access after connection, even though I have full signal and the phone itself has internet access
Please note, tethering was working on this ROM (but not the kernel) last week.
I would post this in the ROM thread, but I’m unable to do so as I cannot post in the developer board until I have 10+ posts under my belt
Bump (Update)
Anyone else out there encountering this issue?
I have been trying to figure out the root of the issue ever since my original post, but still not too much further. Seems that as soon as I revert to my touchwiz ROM, all works as it should, but any custom ROM I try (and I've tried many), tethering does not work. I have verified the APN settings are the same on the touchwiz version (stock ROM) and the custom ROMs that I've tried todate, very frustrating and I can't seems to find anyone with the same problem. I even call Rogers and had them remove and readd the tethering flag on my account, to no avail.
Howdy,
Found the solution to my tethering issues, simply go to the Play Store and search for this app:
ISWAT Tether Unlocker Free
There will be a rather obnoxiously loud app that will play before it performs the operation to unlock your tethering, but afterwards, it works as it does with the stock ROM. You're free to uninstall the app afterwards and you'll retain your tethering abilities
I have a sgh-t399n (samsung galaxy light) running stock rooted/busybox/xposed
I also have a couple lg motions (all are rooted/busybox/xposed) some on stock 4.0.4 and some have cm11
Im a metro pcs user and all are native metro. Phones.
I want to tether. I don't have internet where I am outside of my phone so I wanna activate a phone on the 60dollar unlimited plan and use it as my personal wifi hotspot
I hear its possible to get around the metro restriction at a system level. Something about decompling and recompiling the system framework res apk or something like that and editing a string or two of code.
Anyone know anything about that?
Alternatively....I noticed that even though both of my motions aren't active on a network the metro stock rom motion still prompts me to sign up for the service (to tether) at metro I noticed my motion running cm11 doesn't prompt me to sign up for tethering. It simply connects but obviously it has no data to share since its not active on any networks.
If I activate the motion should it allow me to tether since it didnt give problems when I tried before activating it? Im referring to the one running cm11 not stock
And if not then help bypassing at a system level on would be greatly appreciated.
I figure this is the best place for this.
I'll try and make this simple because I sucke at explaining myself lol
EVERY ROM I try I have major issues, to simplify
If the rom has working native tether and it's normal speed (30+mbs) I have NO sms, I can send all day but not receive.
If a ROM has perfect working SMS like stock B1 or what ever one I just odined back on then tether won't work. Even with WiFi tether router app...it works the first time then never again.
I was just using CM12.1 KLTE from their site and all was perfect until today ZERO ability to receive texts/sms I can't win.....I just want basic functions and tether at normal speeds...my network speed with CM12.1 I was averaging 40+mbs all day...I'm within a mile of 3 LTE towers
When tether does not work I average 0.12mbs....yes dile up is faster....
Any Rom out there that has both...I've even tried variety like Galaxy Project...I can't find the perfect rom.
I don't need millions of tweaks and customized features....
GPS
Tether
Basic phone fetures calling texting browsing
That's it
Any advice is appreciated...I'm not dumb I've rooted and installed hundreds of roms over the years but this is beyond me...maybe S5 is pos lol
Hey I just reverted back to stock from Cherish OS, kept having way too many issues with the ROM rebooting or just freezing. I managed to get hotspot working on Cherish by editing the build prop to include:
net.tethering.noprovisioning=true
then pushing adb shell: settings put global tether_dun_required 0
Was working fine minus the crashes.
Now going back to stock I havnt had any unexpected crashes but I cannot seem to get the tethering to work anymore using magiskhide prop config. Does anyone know what else needs to be done to get wifi tethering working again? It looks like the DUN APN setting on my custom APN does not stick around after saving it, I dont know if it was enabled on Cherish OS somehow or what the difference between the two set ups would realistically be.
Edit:
Solution Provided by lentm:
"If you're rooted, try using VPN Hotspot: https://github.com/Mygod/VPNHotspot/releases"
Just enabled wlan0.
Still looking for a solution, If someone can point me to where I might need to start to resolve this I would appreciate it.
Ex; does it need a custom keneral? or Radio?
What is the limiting factor, that doesnt allow the connected device to get internet?
If you're rooted, try using VPN Hotspot: https://github.com/Mygod/VPNHotspot/releases
I can confirm the linked app works and replicates the built in Wifi Hotspot feature. I have it running on a T Mobile, bootloader unlocked, rooted, stock firmware, and on Android 11. Worked with my desktop, other phone, and Smart TV. I do not have it as a part of my plan. No VPN, port, or other nonsense to setup on the client to get it working. Just put in the WiFi spot password and off you go!.
Thanks for the link! I was never able to find a way to get the built in one working with out an app of some kind. I have no idea what would be needed to patch the factory hotspot to get it working without an app.
xVoidx said:
I can confirm the linked app works and replicates the built in Wifi Hotspot feature. I have it running on a T Mobile, bootloader unlocked, rooted, stock firmware, and on Android 11. Worked with my desktop, other phone, and Smart TV. I do not have it as a part of my plan. No VPN, port, or other nonsense to setup on the client to get it working. Just put in the WiFi spot password and off you go!.
Thanks for the link! I was never able to find a way to get the built in one working with out an app of some kind. I have no idea what would be needed to patch the factory hotspot to get it working without an app.
Click to expand...
Click to collapse
Great. BTW, I think the reason why it's recommended to use with the VPN (such as AdGuard) is to hide the tether usage.
I was a bit skeptical, but after I enabled the wlan0 toggle it worked! thank you soo much I have been struggling with this for a while.
lentm said:
Great. BTW, I think the reason why it's recommended to use with the VPN (such as AdGuard) is to hide the tether usage.
Click to expand...
Click to collapse
Something to note here I wasn't using Adguard and had no issues with the hotspot vpn app. I wasn't using the "Temporary Hotspot" toggle in the app either. Using the wlan0 option gave me Internet on any device I tried while on T Mobile service / Towers. I went out of town and I'm now roaming on US Cellular indicated on my notification bar. This hotspot method stopped working for me. I could connect to the hotspot but no internet. After some research I found using Adguard does resolves this as you mentioned. In the VPN hotspot app you must choose "tun0" as the upstream interface.