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?
After upgrading to ICS from CheckROM V6 (ginger bread) I seem to have lost the rSAP or SIM access profile. Has this been removed from ICS, can anyone confirm which profiles are supported in ICS?
I could go back to GB to test that it's not my car that is at fault as it stopped working after I got my car back from the dealership.
Thanks for your help.
Well it's not my car, I downloaded the rSAP application from the market and installed it. This now gives me the rSAP profile and I can connect to my car in rSAP mode or HFP mode.
So it seems it's missing from ICS, that might make the SIII a no go depending on how good this little app is in the real world.
Apps from the market
Remote SIM access installation
Remote SIM access trial
Which ICS ROM did you upgrade to? I would expect Stock based ROMS to have rSAP and AOSP/AOKP ones to not have this support...
If you look on the google android code site, you will find it is a common problem so it seems to be stock roms that it refers to.
At work, my S4 unable to sign on to the wifi network when I use any touchwiz rom. Every other device I have ever used connects just fine, and my S4 connects to all other wifi networks without issue. It doesn't matter if I use beans, stock, eclipse, synergy, or hyperdrive. I enter the password for the wifi network, it will say connecting for a short period, and then will just go back to saying the network is"Saved, Secured". I delete the network and enter the password again and still the same result.
Now, I also have used the CM aosp and google experience roms, and the wifi connects without issue. Is there a way to pull the wifi radio from these? Honestly I am a novice - I don't develop or modify apks, I do have some beginner experience with adb.
My usual fix is to flash an aosp rom at work, as I do prefer aosp roms. But I always find myself flashing back for the TW camera sharpness and its burst pictures.
Any help you have is appreciated.
All,
I'm running the beta cm11 on my YPG70 (US) so far this has been fantastic.
I have one feature not working that it seems has also been an issue for others.... Bluetooth tethering does not work.
I am able to get the device to connect to my main phone (a Moto X) with bluetooth tethering enabled on both AND it seems like the devices are able to change data across bluetooth, however, now Internet or WAN traffic gets to the YPG70.
I know there was a bug fix in an older version of Cyanogenmod to some networking routing table config files (I belive) so maybe this is related to that cropping up again.
I also found a post to check for /system/bin/pand which DOES NOT exist on this build from Jan 13.
Any ideas?
[email protected] said:
All,
I'm running the beta cm11 on my YPG70 (US) so far this has been fantastic.
I have one feature not working that it seems has also been an issue for others.... Bluetooth tethering does not work.
I am able to get the device to connect to my main phone (a Moto X) with bluetooth tethering enabled on both AND it seems like the devices are able to change data across bluetooth, however, now Internet or WAN traffic gets to the YPG70.
I know there was a bug fix in an older version of Cyanogenmod to some networking routing table config files (I belive) so maybe this is related to that cropping up again.
I also found a post to check for /system/bin/pand which DOES NOT exist on this build from Jan 13.
Any ideas?
Click to expand...
Click to collapse
Afaik, bluetooth tethering is not enabled in CM11 for YP-G70...
Just thought I would throw out a question. As a KitKat user with a custom ROM I enjoyed pretty seamless WiFi Calling capabilities on my Note 3. I recently loaded the AOKP Oreo ROM and happened to go to a place that didn't have signal (I must admit that isn't very hard to do in my area) and although I loaded Google Voice and could use that number on the local WiFi in the building to make and receive text and calls, I was curious if there was a way to load the native WiFi calling Sprint offers which lets me use my Sprint phone number. I tried downloading the Sprint WiFi APK v. 1 and v.2 but they didn't seem to work.
Anyone else have any thoughts? I am using Magisk now and even tried an old app that supposedly provides a direct way to activate the WiFi calling abilities but no luck there either.
I have my KK system backed up on TB and tried restoring the WiFi Calling app from there but it didnt seem to want to load either. Perhaps I am missing a companion app that needs to run as well?
All suggestions will be entertained!
Dave