[Sprint Samsung Galaxy S III] stealthdave:
Wake lock issues

I've been getting some pretty severe wake lock issues on this ROM over multiple kernels (default kernel, Light Kernel 5.4, and KT747 4/11/13). I'm getting Kernel wake locks for wlan_rx_wake and PowerManagerService constantly, and my battery life is going down faster than the Titanic. Here's the BBS dump:

===================
General Information
===================
BetterBatteryStats version: 1.13.2.0
Creation Date: 2013-04-15 11:10:49
Statistic Type: Unplugged to Current
Since 46 m 57 s
VERSION.RELEASE: 4.2.2
BRAND: samsung
DEVICE: d2spr
MANUFACTURER: Samsung
MODEL: SPH-L710
OS.VERSION: 3.4.40-leanKernel-spr_aosp_43-5.4-+
BOOTLOADER: L710VPBMB1
HARDWARE: qcom
FINGERPRINT: samsung/d2spr/d2spr:4.0.4/IMM76D/L710VPALG2:user/release-keys
ID: JDQ39
TAGS: release-keys
USER: kejar31
PRODUCT: d2spr
RADIO: L710VPBMB1
Rooted: true
============
Battery Info
============
Level lost [%]: Bat.: -6% (75% to 69%) [7.7%/h]
Voltage lost [mV]: (3957-3926) [39.7%/h]
===========
Other Usage
===========
Deep Sleep (): 2 m 41 s (161 s) Ratio: 4.8%
Awake (): 44 m 17 s (2657 s) Ratio: 94.3%
Screen On (): 56 s (56 s) Ratio: 2.0%
Wifi On (): 46 m 58 s (2818 s) Ratio: 100.0%
Wifi Running (): 46 m 58 s (2818 s) Ratio: 100.0%
No Data Connection (): 46 m 55 s (2815 s) Ratio: 99.9%
No or Unknown Signal (): 46 m 55 s (2815 s) Ratio: 99.9%
Screen dark (): 56 s (56 s) Ratio: 2.0%
=========
Wakelocks
=========
Starting CM_VnoteService (com.coremobility.app.vnotes.Voicemail): 6 m 27 s (387 s) Count:50 13.7%
StartingAlertService (Calendar): 4 m 53 s (293 s) Count:71 10.4%
LocationManagerService (Android System): 2 m 10 s (130 s) Count:49 4.6%
GpsLocationProvider (Android System): 1 m 58 s (118 s) Count:81 4.2%
MAIL_SERVICE (com.qs.enhancedemail.Enhanced Email): 1 m 34 s (94 s) Count:98 3.3%
NetworkLocationLocator (Google Services): 47 s (47 s) Count:108 1.7%
AlarmManager (Android System): 43 s (43 s) Count:298 1.3%
AlarmManager (com.android.providers.calendar.Calendar Storage): 41 s (41 s) Count:17 1.5%
NetworkLocationLocator (com.google.android.apps.maps.Maps): 39 s (39 s) Count:17 1.4%
AlarmManager (Phone): 37 s (37 s) Count:55 1.1%
MediaScannerService (Media): 28 s (28 s) Count:0 1.0%
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 23 s (23 s) Count:70 0.7%
AlarmManager (com.google.android.apps.plus.Google+): 21 s (21 s) Count:57 0.7%
NetworkStats (Android System): 20 s (20 s) Count:47 0.6%
*sync*_com.android.calendar_Account {name=fa379ab42c4fd9fd67fa3c5d7b5e3df8, type=com.google} (Calendar): 18 s (18 s) Count:36 0.6%
RILJ (Phone): 18 s (18 s) Count:77 0.7%
AlarmManager (com.google.android.apps.maps.Maps): 17 s (17 s) Count:155 0.5%
SignalCollector.ScannerThread (com.google.android.apps.maps.Maps): 15 s (15 s) Count:74 0.5%
SignalCollector.Scanner (com.google.android.apps.maps.Maps): 14 s (14 s) Count:109 0.5%
AlarmManager (com.levelup.beautifulwidgets.BeautifulWidgets): 7 s (7 s) Count:52 0.2%
com.google.android.music.leanback.AutoCachingService (com.google.android.music.Google Play Music): 6 s (6 s) Count:44 0.2%
AudioOut_2 (1013): 6 s (6 s) Count:3 0.2%
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 5 s (5 s) Count:69 0.2%
AlarmManager (com.google.android.music.Google Play Music): 5 s (5 s) Count:47 0.2%
FbClientConnManager (com.facebook.katana.Facebook): 5 s (5 s) Count:60 0.2%
NetworkLocationCacheUpdater (com.google.android.apps.maps.Maps): 5 s (5 s) Count:85 0.2%
SyncLoopWakeLock (Android System): 4 s (4 s) Count:526 0.1%
*sync*_com.android.calendar_Account {name=dfde4bd3bbb0912d0b911695a065d8a9, type=com.qs.exchange} (com.qs.enhancedemail.Enhanced Email): 3 s (3 s) Count:36 0.1%
Camera Monitor (com.google.android.apps.plus.Google+): 3 s (3 s) Count:28 0.1%
ScheduleNextAlarmWakeLock (com.android.providers.calendar.Calendar Storage): 3 s (3 s) Count:47 0.1%
*sync*_gmail-ls_Account {name=fa379ab42c4fd9fd67fa3c5d7b5e3df8, type=com.google} (com.google.android.gm.Gmail): 2 s (2 s) Count:4 0.1%
CM Message wakeup (com.coremobility.app.vnotes.Voicemail): 2 s (2 s) Count:26 0.1%
SyncManagerHandleSyncAlarm (Android System): 2 s (2 s) Count:168 0.1%
Checkin Service (Google Services): 1 s (1 s) Count:95 0.1%
FacebookService (com.facebook.katana.Facebook): 1 s (1 s) Count:51 0.0%
*vibrator* (Android System): 1 s (1 s) Count:183 0.0%
*sync*_com.google.android.apps.plus.content.EsProvider_Account {name=fa379ab42c4fd9fd67fa3c5d7b5e3df8, type=com.google} (com.google.android.apps.plus.Google+): 1 s (1 s) Count:1 0.0%
Icing (Google Services): 1 s (1 s) Count:149 0.0%
================
Kernel Wakelocks
================
"wlan_rx_wake" (): 26 m 18 s (1578 s) Cnt:(c/wc/ec)2958/0/2958 56.0%
"PowerManagerService" (): 24 m 14 s (1454 s) Cnt:(c/wc/ec)173/0/0 51.6%
"wlan_wd_wake" (): 11 m 49 s (709 s) Cnt:(c/wc/ec)8963/0/0 25.2%
"suspend_backoff" (): 7 m 50 s (470 s) Cnt:(c/wc/ec)48/0/48 14.0%
"sec-battery-monitor" (): 4 m 8 s (248 s) Cnt:(c/wc/ec)486/0/0 8.8%
"wlan_wake" (): 3 m 35 s (215 s) Cnt:(c/wc/ec)26563/336/0 7.6%
"wlan_ctrl_wake" (): 1 m 47 s (107 s) Cnt:(c/wc/ec)208/0/208 3.8%
"mmc1_detect" (): 1 m 33 s (93 s) Cnt:(c/wc/ec)859/0/1 2.8%
"alarm_rtc" (): 1 m 7 s (67 s) Cnt:(c/wc/ec)94/0/26 2.0%
"radio-interface" (): 41 s (41 s) Cnt:(c/wc/ec)38/0/0 1.5%
"bam_dmux_wakelock" (): 27 s (27 s) Cnt:(c/wc/ec)14/0/0 1.0%
"sec-battery-measure" (): 10 s (10 s) Cnt:(c/wc/ec)492/0/0 0.4%
"alarm" (): 4 s (4 s) Cnt:(c/wc/ec)343/0/0 0.2%
"msm_ipc_read00000001:0000001a" (): 2 s (2 s) Cnt:(c/wc/ec)244/0/0 0.1%
"rmt_storage_1106325224" (): 2 s (2 s) Cnt:(c/wc/ec)10/0/0 0.1%
"power-supply" (): 2 s (2 s) Cnt:(c/wc/ec)486/0/0 0.1%
"rmt_storage_1106325400" (): 1 s (1 s) Cnt:(c/wc/ec)9/0/0 0.0%
"KeyEvents" (): 1 s (1 s) Cnt:(c/wc/ec)2421/0/0 0.0%
"qcril" (): (0 s) Cnt:(c/wc/ec)121/0/0 0.0%
"PowerManagerService.Broadcasts" (): (0 s) Cnt:(c/wc/ec)3/0/0 0.0%
"smdcntl0" (): (0 s) Cnt:(c/wc/ec)355/1/0 0.0%
"smdcntl1" (): (0 s) Cnt:(c/wc/ec)130/0/0 0.0%
"qmuxd_port_wl_0" (): (0 s) Cnt:(c/wc/ec)372/0/0 0.0%
"qmuxd_port_wl_1" (): (0 s) Cnt:(c/wc/ec)132/0/0 0.0%
"mmc0_detect" (): (0 s) Cnt:(c/wc/ec)859/0/1 0.0%
"ipc_rtr_smd_rpcrpy_cntl" (): (0 s) Cnt:(c/wc/ec)872/0/0 0.0%
"msm_ipc_read00000001:00000001" (): (0 s) Cnt:(c/wc/ec)24/0/0 0.0%
======================
Alarms (requires root)
======================
======================
Network (requires root)
======================
==========
CPU States
==========
384 MHz (): 31 m 13 s 66.5%
486 MHz (): 1 m 34 s 3.4%
594 MHz (): 56 s 2.0%
702 MHz (): 48 s 1.7%
810 MHz (): 9 m 25 s 20.1%
918 MHz (): 0.0%
1.03 GHz (): 0.0%
1.13 GHz (): 6 s 0.2%
1.24 GHz (): 0.0%
1.35 GHz (): 0.0%
1.46 GHz (): 0.0%
1.51 GHz (): 9 s 0.3%
Deep Sleep (): 2 m 41 s 4.8%
==================
Reference overview
==================
ref_boot: Reference ref_boot created 7 m 33 s (Wl: 18 elements; KWl: 6elements; NetS: null; Alrm: null; Proc: 4 elements; Oth: 8 elements; CPU: 12 elements)
ref_unplugged: Reference ref_unplugged created 9 m 10 s (Wl: 25 elements; KWl: 21elements; NetS: null; Alrm: null; Proc: 6 elements; Oth: 8 elements; CPU: 12 elements)
ref_current: Reference ref_current created 56 m 8 s (Wl: 46 elements; KWl: 30elements; NetS: null; Alrm: null; Proc: 28 elements; Oth: 9 elements; CPU: 13 elements)

I've been getting this on all the latest nightlies and 1.6.1. I've read about the work-around using a static IP to reduce DHCP calls, but that's not really an option for me between my corporate network, home network and municipal wifi that I use on a daily basis. Has anyone else seen this behavior? Better yet, does anyone have a solution?

- Dave

UPDATE: This is definitely wifi related. I turned off wifi and my battery drain immediately stopped. Using bluetooth or 3G/LTE works as expected with no unexplained battery drain.