Quote:
Originally Posted by Purple Lady
Creating a profile to turn wifi on when it turned itself off would have used a ton of battery for me. I would want it on to sync reading positions so that would be most of the time. It would have been nice to have it stay on when I was in the Google play store too.
|
After reading your reply, I realized the last line in my previous post was confusing, so I've edited it. In system settings, without using Tasker, if you turn Airplane mode on and wifi on, you will enable ONLY the wifi radio, and the system should quit trying to do cellular background sync of any sort. On the NST, some of us found that disabling or removing system .apks caused various problems, so this was a safer way to achieve the same effect.
With regards to using Tasker, I was suggesting you might create a profile to turn/force wifi on
when certain apps are loaded or launched, and otherwise let the system determine when it should be on. So IF your app of concern is open on-screen and IF wifi is shut off, turn it back on. You can get very granular, so you could have it do this only at certain times or on certain days. It provides a middle ground between Android's "always on" and "on while screen on" settings, as well as real-time monitoring of the state to make sure it stays where you want it.
Tasker also has the ability to set up profiles to do things like turn wifi on, wait for a connection to be established, then enable background sync/launch an app to sync (depending on how well your chosen app plays with Android's sync). In Financial War's situation, he could have Tasker launch a timed task to force wifi on, wait for a connection to be established, then launch a Folder Sync task.
Some capabilities (e.g. controlling GPS) do require root, but most do not. If your aggravation is a setting being turned off when you don't want it off, Tasker might be the perfect fix.