Tips for wifi management? - Galaxy S III Q&A, Help & Troubleshooting

I'm suffering from poor battery life on my S3 - worse than my S2 with the same set of user-installed apps. I suspect that it's because I tend to leave wifi switched on. Could someone provide guidance on a power-efficient way of managing wifi?
I want to receive notifications of incoming emails, and would like this to be done via wifi wherever possible. I have wifi both at home and at work. If I'm away from home and work ideally I don't want the phone to hunt for wifi signals.
Can anyone recommend the best way of achieving the above in the most power-efficient way?

---

You can try tasker or llama to manage a lot ou things in various conditions... Like Wifi off when Screen off... Etc....
Envoyé depuis mon GT-I9300 avec Tapatalk

---

Wifi doesn't drain a lot of battery, at least not for me.
Do you have a very faint signal or regular drops?
Please report what BetterBatteryStats (free APK here in XDA) shows after several hours (ideally a full battery cycle) of usage.

---

Past SG models WiFi has been found to drain battery when searching for networks .
If i turn my router off then SGS is searching for networks .
jje

---

That's true.
However it's the same for all wiieless data connectionsz sensing across frequencies costs more battery than keeping a connection alive.
I'd recommend JuiceDefender Beta since it can manage all data connections and additronally automatically toggle 3g/2g upon requirement.
The app's cost of a few bucks is in no relation to the worth of a longer-living battery on your 600USD phone
Sent from my GT-I9300 using xda premium

---

d4fseeker said:
Wifi doesn't drain a lot of battery, at least not for me.
Do you have a very faint signal or regular drops?
Please report what BetterBatteryStats (free APK here in XDA) shows after several hours (ideally a full battery cycle) of usage.
Click to expand...
Click to collapse
Here's the output from BetterBatteryStats, for a period of about 3 hours after unplugging the phone. During this time it was turned on very briefly a couple of times to check notifications, and was within 10 feet of the wifi router.
===================
General Information
===================
BetterBatteryStats version: 1.8.1.0
Creation Date: 2012-07-06 12:43:46
Statistic Type: (3) Since Unplugged
Since 3 h 19 m 46 s
VERSION.RELEASE: 4.0.4
BRAND: samsung
DEVICE: m0
MANUFACTURER: samsung
MODEL: GT-I9300
BOOTLOADER: I9300XXALE8
FINGERPRINT: samsung/m0xx/m0:4.0.4/IMM76D/I9300XXALE8:user/release-keys
HARDWARE: smdk4x12
ID: IMM76D
TAGS: release-keys
USER: se.infra
PRODUCT: m0xx
RADIO: I9300NELE4
Rooted: true
===========
Other Usage
===========
Wifi On (): 3 h 19 m 46 s (11986 s) Ratio: 100.0%
Poor Signal (): 3 h 4 m 31 s (11071 s) Ratio: 92.4%
Deep Sleep (): 2 h 54 m 59 s (10499 s) Ratio: 87.6%
Awake (): 24 m 47 s (1487 s) Ratio: 12.4%
Wifi Running (): 16 m 8 s (968 s) Ratio: 8.1%
No Data Connection (): 15 m 14 s (914 s) Ratio: 7.6%
No or Unknown Signal (): 15 m 14 s (914 s) Ratio: 7.6%
Screen On (): 15 s (15 s) Ratio: 0.1%
=========
Wakelocks
=========
*sync*_gmail-ls_Account {name=EM, type=com.google} (com.google.android.gm.Gmail): 4 m 48 s (288 s) Count:47 2.4%
GmailProviderProviderChangedBroadcastWakeLock (com.google.android.gm.Gmail): 53 s (53 s) Count:79 0.4%
SyncLoopWakeLock (Android System): 52 s (52 s) Count:485 0.4%
*backup* (Android System): 27 s (27 s) Count:84 0.2%
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 26 s (26 s) Count:10 0.2%
com.bellshare.util.WakefulIntentService (com.bellshare.beweather.BeWeather Pro): 23 s (23 s) Count:3 0.2%
FacebookService (com.facebook.katana.Facebook): 23 s (23 s) Count:6 0.2%
AlarmManager (Android System): 17 s (17 s) Count:291 0.1%
sleep_broadcast (Android System): 8 s (8 s) Count:80 0.1%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 8 s (8 s) Count:9 0.1%
*sync*_com.android.contacts_Account {name=EM, type=com.google} (Google Services): 7 s (7 s) Count:62 0.1%
GTALK_CONN (Google Services): 6 s (6 s) Count:221 0.1%
DHCP (Android System): 5 s (5 s) Count:81 0.0%
DownloadManager (Media): 4 s (4 s) Count:2 0.0%
GOOGLE_C2DM (Google Services): 4 s (4 s) Count:49 0.0%
NetworkLocationBurstCollector (com.google.android.apps.maps.Maps): 4 s (4 s) Count:11 0.0%
My Tag (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 4 s (4 s) Count:49 0.0%
RILS (com.sec.phone.SecPhone): 4 s (4 s) Count:1 0.0%
EM/android_talk14c111ed2ffe (Google Services): 3 s (3 s) Count:1 0.0%
Push Thread:6866 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 3 s (3 s) Count:45 0.0%
Push Thread:6793 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 3 s (3 s) Count:55 0.0%
Push Thread:6831 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 3 s (3 s) Count:44 0.0%
AudioOut_1 (1013): 2 s (2 s) Count:1 0.0%
GTALK_ASYNC_CONN_com.google.android.gsf.gtalkservice.AndroidEndpoint (Google Services): 1 s (1 s) Count:229 0.0%
NetworkStats (Android System): 1 s (1 s) Count:23 0.0%
Push Thread:6865 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 1 s (1 s) Count:50 0.0%
Push Service:1 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 1 s (1 s) Count:18 0.0%
Push Thread:6669 (com.nitrodesk.droid20.nitroid.TouchDown for SmartPhones): 1 s (1 s) Count:1 0.0%
WifiStateMachine (Android System): 1 s (1 s) Count:94 0.0%
GpsLocationProvider (Android System): 1 s (1 s) Count:76 0.0%
================
Kernel Wakelocks
================
"multipdp" (): 18 m 3 s (1083 s) Cntc/wc/ec)97/0/96 9.0%
"secril_fd-interface" (): 9 m 32 s (572 s) Cntc/wc/ec)153/0/0 4.8%
"PowerManagerService" (): 8 m 37 s (517 s) Cntc/wc/ec)370/0/0 4.3%
"l2_hsic" (): 5 m 13 s (313 s) Cntc/wc/ec)830/75/829 2.6%
"battery-monitor" (): 3 m 7 s (187 s) Cntc/wc/ec)186/0/187 1.6%
"alarm_rtc" (): 1 m 42 s (102 s) Cntc/wc/ec)178/0/65 0.9%
"wlan_rx_wake" (): 1 m 3 s (63 s) Cntc/wc/ec)50/0/49 0.5%
"alarm" (): 46 s (46 s) Cntc/wc/ec)213/0/0 0.4%
"rpm_hsic" (): 46 s (46 s) Cntc/wc/ec)638/0/0 0.4%
"GPS" (): 43 s (43 s) Cntc/wc/ec)1/0/0 0.4%
"wlan_wake" (): 16 s (16 s) Cntc/wc/ec)149802/110/0 0.1%
"tx_hsic" (): 11 s (11 s) Cntc/wc/ec)1021/0/0 0.1%
"umts_rfs0" (): 8 s (8 s) Cntc/wc/ec)3/0/3 0.1%
"AudioOutLock" (): 4 s (4 s) Cntc/wc/ec)1/0/0 0.0%
"umts_ipc0" (): 3 s (3 s) Cntc/wc/ec)10/0/10 0.0%
"vib_present" (): 3 s (3 s) Cntc/wc/ec)2/0/0 0.0%
"radio-interface" (): 2 s (2 s) Cntc/wc/ec)4/0/0 0.0%
"event1-2108" (): 1 s (1 s) Cntc/wc/ec)2/0/0 0.0%
"efsd-interface" (): (0 s) Cntc/wc/ec)6/0/0 0.0%
"event10-2108" (): (0 s) Cntc/wc/ec)1848/0/0 0.0%
"event4-2108" (): (0 s) Cntc/wc/ec)865/0/0 0.0%
"secril_rfs-interface" (): (0 s) Cntc/wc/ec)3/0/0 0.0%
"event5-2108" (): (0 s) Cntc/wc/ec)604/0/0 0.0%
"sync_system" (): (0 s) Cntc/wc/ec)2/0/0 0.0%
"power-supply" (): (0 s) Cntc/wc/ec)216/0/0 0.0%
"secril_fmt-interface" (): (0 s) Cntc/wc/ec)22/0/0 0.0%
"KeyEvents" (): (0 s) Cntc/wc/ec)239/0/0 0.0%
"mmc1_detect" (): (0 s) Cntc/wc/ec)198/0/0 0.0%
"mmc0_detect" (): (0 s) Cntc/wc/ec)198/0/0 0.0%

---

Please use the code tags when copy-pasting content, since it will format the content in easier-to-read format and prevent the forum from inserting smilies.
Your issue seems to be:
Code:
Poor Signal (): 3 h 4 m 31 s (11071 s) Ratio: 92.4%
That will, of course, drain the battery pretty fast since the Amplifier needs to run at maximum capacity to reach the antenna. If you have better signal on the S2 and use a case on the S3 try removing it (temporarely)

---

d4fseeker said:
Please use the code tags when copy-pasting content, since it will format the content in easier-to-read format and prevent the forum from inserting smilies.
Your issue seems to be:
Code:
Poor Signal (): 3 h 4 m 31 s (11071 s) Ratio: 92.4%
That will, of course, drain the battery pretty fast since the Amplifier needs to run at maximum capacity to reach the antenna. If you have better signal on the S2 and use a case on the S3 try removing it (temporarely)
Click to expand...
Click to collapse
Presumably it's the wifi signal that's weak, not the GSM signal?
I don't use a case with the S3, and it was sat on my desk all morning 10 feet from the wifi router, so I don't understand why the signal would have been weak :0(