Hello,
I have old smartphone(Milestone 1) and would like to use it only for a wifi tethering. I have already installed CM7 and disabled everything i could(sync, animations, lowered max CPU) to reduce battery usage. I'm using currently the build-in wifi tether option, but want to know if there is an tethering app that:
disables 3G data when no client is connected in the last 5 minutes? I think it should provide a very better battery life, am I right?
If you have any other advices I'd be grateful for them.
Related
so I know theres already a dead thread on this....but it got no where.
So here goes, my x10(both on 1.6 and 2.1) seems to ALWAYS maintain a data connection whether it be wifi or hsdpa. This occurs with every running app/service disabled background data off etc etc. The only solution ive found is to switch off both wifi and toggle the apn/data connections off. I'd rather not have to do this as realistically I'll end up forgetting to toggle them off.
Shouldn't android simply connect on demand rather than maintaining the connection constantly?
and before anyone says it, it's not the data consumption im frustrated with...it's the unnecessary battery drain.
Bump....
Sent from my U20i using XDA App
Android keeps an active connection for things like:
1) syncing contacts & email
2) the ability to use Gtalk
Have you actually checked how little the active connection uses (not much)
constantly maintaining a data connection does indeed drain the battery in comparison to not keeping one. I assume the 'how little' it drains is based on that half assed percentage indicator android gives us?
If you actually read the first post you'd see that I'm specifically interested in having the connection on demand. If I'm not syncing my email or contacts at the time why on earth should it be maintaining a connection.
i had a hd2 it also had a constant connection.but on wm there is an app which turns off the connection and turns it on When needed.
isnt there an apps like that on android.
just use the APN On/Off widget and put it on your home screen, quick and easy and turns on/off with one press
This has frustrated me to no end. Does anybody know if there is an app that will switch from HSPDA to 2g? Preferably one I can set to a schedule? The WiFi calling app is the only one that seems to do this flawlessly, however it requires a WiFi connection.
When I am at work I do not use my phone for anything except phone calls and my calendar, so I do not have any need for 4 or even 3g coverage... And my phone just drains battery trying to establish these connections.
I've tried using APNdroid but it just force closes my phone process.
Any help on this matter would be greatly appreciated. I'm running elite sense 2.6 if that matters at all.
Sent from my HTC Glacier using XDA App
+1
It would be great if there is some app to schedule 2g/3g.
Sent from my GT-I9000 using XDA App
Why not just do it manually? If not then maybe Locale? It's $10 but it may do what you are looking for.
Switchpro or extended controls has the option idk about a schedule though.
I use a Juicedefender/tasker combo to Control the 3g. I had to ROOT and flash CM to get it do it, but its made my life easier since I never remembered to turn 3g off when I went to work.
*EDIT: though it should be noted that the AOSP Helper that Juicedefender uses to toggle 3g doesn't seem to work on Cm7.03
Hi williecat316,
I just have installed Tasker and I would like to do the same kind of combo as you did with Juice Defender and Tasker. E.g. when I unlock the phone, stay in 2g, but use Juice Defender to start 3g if I am away from any known wifi spot AND if I launch lets say the browser or any connected app. Could you give more details about the way you configured Tasker on your phone?
Thanks
P.S. the 3G/2g swithing through Juice Defender works perfectly on my phone (via AOSP Helper of course) but I'd like to fine tune the way it switches between 2g and 3g thanks to Tasker.
I have problems with 2g... All incoming calls go to voice mail....
Somebody can help me?
macmalon said:
Hi williecat316,
I just have installed Tasker and I would like to do the same kind of combo as you did with Juice Defender and Tasker. E.g. when I unlock the phone, stay in 2g, but use Juice Defender to start 3g if I am away from any known wifi spot AND if I launch lets say the browser or any connected app. Could you give more details about the way you configured Tasker on your phone?
Thanks
P.S. the 3G/2g swithing through Juice Defender works perfectly on my phone (via AOSP Helper of course) but I'd like to fine tune the way it switches between 2g and 3g thanks to Tasker.
Click to expand...
Click to collapse
Seriously, did you read the date on the last post.
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?
I'm running Scott's CleanRom 4.3, using Wireless Tether for Root Users to provide a hotspot for my laptop. Works great using Wifi Tether 3.1 b11 and up...for those wondering, here's how to set it up:
Device profile: Generic ICS works beautifully, so does Samsung Galaxy Nexus LTE. I think there's a little less latency using Generic ICS.
Setup Method: netd (master)
Wifi driver reload: Check ON.
Routing fix: check ON.
Should work on both LTE and 3G.
Now for the problem...
Open up your favorite browser and put your connection to good use (if you can spare the data, or have an unlimited plan...I am not responsible for carrier surcharges). Watch a ton of YouTube. Download stuff. Look at porn. Whatever...just put a good heavy load on your connection. Try to make it fairly continuous.
If you run into the same problem I have, then after some time, regardless of the amount of traffic passed, the connection will stop responding. Sometimes restarting Tether works. Sometimes though, it seems that all data is frozen...can't use the phone's browser, can't use any apps that rely on data...nothing gets through except possibly pings.
I would like to see who else runs into this issue, on what ROMs, and whether there is anything we can do to fix it.
My Wi-Fi is scanning constantly when already contacted to my home network successfully.
It is killing my battery. Visible difference with Wi-Fi on vs off in the battery graph
I have many things hibernated.
So I'm reading about this interval, wondering what the longest possible interval is as I turn off and on Wi-Fi manually, and I'd like to save my battery juice. Even idle but on Wi-Fi there's a big difference!
I'm on a rooted Samsung Galaxy s5 neo
And yes I've got it set to off already for it scanning even when Wi-Fi is set to off for Google networks.
Help?
Sent from my SM-G903W using XDA-Developers mobile app
Anyone?
Sent from my SM-G903W using XDA-Developers mobile app
Does WiFi not kill anyone else's battery? Orrr... ?
Sent from my SM-G903W using XDA-Developers mobile app
For being the third Google result when searching for "wifi supplicant scan interval", this thread's lack of feedback is remarkable. I was wondering the same. I've now set it it to 600 because I'm really not that dependant on WiFi since I have a 4GB data plan. I don't mind if it takes a while to connect when I get home and with this setting it'll only check for a connection 50 to 60 times a day (during the 9 hours I'm away from home) but still enough when connected, I don't need updates to be more frequent than 10 minutes. We'll see how that goes.
Did you eventually end up altering it, @Pawprints1986 (look at that, we're from the same year!)? If so, what were your experiences?
I actually haven't altered anything. I don't have the supplicant line already in my build prop and I'm not sure where to put it or which value to use, or if it would work.
I tried adding a line into my s2 build prop but it didn't seem to actually respond to it, so I must have done something wrong, still searches every 2 seconds.
Sent from my SM-G903W using XDA-Developers Legacy app
I tried 720 Supplicant WiFi Interval and I have low issues. The signal to find new WiFi is still easy to get, albeit some waiting a little bit but saved a tremendous amount of battery.
I also disabled WiFi Scan completely and not know how I did it until just recently by using AppOpsXposed and disabling Location on settings. That stops WiFi Scan completely and only allows you to connect to your WiFi routers that you already connected to.
How would you force Android to scan for new wifi network manually? With that, we could have the best of the two world - long battery and fast switching when you need it.