Doesn't look like low service - you were on wifi, so data was going over wifi.ok, so I did try this to an extent, i would disable 4 apps at a time for the most part, only apps, none of the red items like wifi manager and stuff like that (even though i did try that at a different date)
I had no success.. I went back to stock, uninstalled all bloatware, at&t live TV, my account, bar scanner, all that bs, right now I have BBS, Cpu Spy and titanium, only apps that are not stock and are in the list of installed apps. I am still getting this issue!! could it be that I have poor service (though this never affected the iphone this badly) I lose 40% overnight though and it seems odd to me that would be because of low service..
Top three wakelocks were wlan_rx_wake, svnet, and mmc_delayed_work
wlan_rx_wake is a dead ringer for network traffic. This wakelock happens when your phone receives a network packet addressed to it and it's asleep. So incoming network traffic is waking your phone often.
svnet is unusually high - usually this is fairly low, as it's basic radio management stuff (Edit: low service MIGHT have driven this one up)
svnet-dormancy is almost nonexistent - this is what you will usually see when an app is driving network traffic via cell data
mmc_delayed_work is new to me, but I'm 90% certain that it is due to some app reading/writing to storage
Nailing your culprit might need a network capture - I'm going to work on a tutorial for using Shark for Root ( https://market.android.com/details?id=lv.n3o.shark ) in a day or two.
BTW, to analyze the /proc/wakelocks dumps:
Open in Excel or OpenOffice/LibreOffice Calc
Import as tab-delimited text
Add a new column called sleep_time_minutes
Set this column to equal sleep_time divided by 60e9 - this converts nanoseconds to minutes
Sort by sleep_time_minutes
Last edited: