asksven / betterwifionoff Goto Github PK

Possible rules:

• turn on when at location...
• turn off when leaving location...

See http://developer.android.com/reference/android/net/wifi/WifiManager.WifiLock.html

state machine controlled by prefs "wifi_on_when_previously_on" and "last_action"

Goal:
last action shows what was the last thing done by BetterWifiOnOff
if last_action was on
but wifi is off that means that the user turned it off -> don't turn on
if last action was off
but wifi is on that means that the user turned it on -> don't turn off

0.3

Just installed on my TF101 and was updating a load of apps from Google Play. The screen went off, and a few minutes later I unlocked the screen and the WiFi was off (and then reconnected as expected).

It would be nice if the WiFi wouldn't drop when the screen goes off if there is data transferring (over a given threshold I guess), to avoid aborting any downloads that are in progress.

TelephonyManager telephony = (TelephonyManager) mContext
.getSystemService(Context.TELEPHONY_SERVICE);
if (telephony.getCallState() == TelephonyManager.CALL_STATE_OFFHOOK
|| telephony.getCallState() == TelephonyManager.CALL_STATE_RINGING) {
Slog.w(TAG, "Phone is ringing or in a phone call, not enabling power saver");
return;
}

ceiverCallNotAllowedException: IntentReceiver components are not allowed to bind to services
E/AndroidRuntime(29242): at android.app.ActivityThread.handleReceiver(ActivityThread.java:2362)
E/AndroidRuntime(29242): at android.app.ActivityThread.access$1500(ActivityThread.java:142)
E/AndroidRuntime(29242): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1284)
E/AndroidRuntime(29242): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(29242): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime(29242): at android.app.ActivityThread.main(ActivityThread.java:4928)
E/AndroidRuntime(29242): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime(29242): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime(29242): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:791)
E/AndroidRuntime(29242): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:558)
E/AndroidRuntime(29242): at dalvik.system.NativeStart.main(Native Method)
E/AndroidRuntime(29242): Caused by: android.content.ReceiverCallNotAllowedException: IntentReceiver components are not allowed to bind to services
E/AndroidRuntime(29242): at android.app.ReceiverRestrictedContext.bindService(ContextImpl.java:142)
E/AndroidRuntime(29242): at com.asksven.betterwifionoff.services.EventWatcherServiceBinder.doBindService(EventWatcherServiceBinder.java:95)
E/AndroidRuntime(29242): at com.asksven.betterwifionoff.services.EventWatcherServiceBinder.getInstance(EventWatcherServiceBinder.java:46)
E/AndroidRuntime(29242): at com.asksven.betterwifionoff.handlers.BroadcastHandler.onReceive(BroadcastHandler.java:122)
E/AndroidRuntime(29242): at android.app.ActivityThread.handleReceiver(ActivityThread.java:2355)

e.g. "Disable all" and "On when plugged in" still turns on Wifi

It is keep going on even I close the WiFi manually.

If in call (I feel this pref could be removed completely and the behavior aleays be as "on")
If Wifi tethering (I feel this pref could be removed completely and the behavior aleays be as "on"

If in a call section should be leave wifi on if not of

Wifi tethering section should be leave on not of

for consistently purposes under the rules for leaving wifi on add the word in after if plugged to match your language with the other sections.

Together with wifi on while plugged a good way to have fast wifi as not every device stays awake while charging

Also, the "Connection timeout" and its description indicates that it only applies to the "Only if connected" rule but I think it applies to all "Rules for leaving wifi on"

In 0.2

A "simple" mode would be:
Service setting (all hidden)
Rules for turning Wifi on (all visible)

Rules for leaving Wifi on
Only if connected (on by default but hidden)
Check for cage (off by default but hidden)
If in call (I feel this pref could be removed completely and the behavior aleays be as "on")
If netwotk activity (off by default and hidden)
If wakelock is held (on by default but hidden)
If Wifi tethering (I feel this pref could be removed completely and the behavior aleays be as "on"

Rules whn plugged in
Wifilocks (off by default and hidden)

Rules for turining Wifi off (all on by default and hidden)

Own logfile: not really required as I will provide logcat with grep on BetterWifiOnOff

rationale: if the screen is off but bigger downloads (e.g. google play updates) is running we want to wavoid turning wifi off till it is finished. This may be doable by detecting if a partial wakelock is held.

See http://forum.xda-developers.com/showpost.php?p=29825839&postcount=68

For ref: http://forum.xda-developers.com/showpost.php?p=29827190&postcount=71

wrong section, will fix but not here but in BBS :-D

There's a kernel module responsible for creating KWLs on behalf of userland processes. It exposes 2 sysfs entries at /sys/power/wake_lock and wake_unlock.
Any regular process (running as radio or as system) can write to wake_lock to create and lock a KWL with the same name as the passed text. And to unlock it, write the same text to the wake_unlock file.

consider the impact of whitelisted SSIDs

1. screen off
2. screen on within 10 seconds
3. Wifi goes off because of the alarm scheduled in 1.

Solution
at 2. remove any pending Wifi off alarms