[REF] Known identified battery drainers

Search This thread

JustinW3

Senior Member
Feb 20, 2012
173
45
You claim now to have used BBS and CPUSpy - but there isn't a single shred of evidence in your existing posts prior to this that indicate you have used it. No wakelock lists, no indication of what your deepsleep percentages were, nothing useful. All you've done is post some stats from the stock Android battery statistics screen which are basically useless.

Fine, I will post info from BBS next time I experience the drain, I disabled Facebook notifications and disabled the automatic refresh of the status updates for the widget to see if that was causing wakelocks. I have previously posted stats from CPUSpy but didn't in this case because they weren't any good. I had forgotten to reset the timers so there were like 3 days of data in there.

So far since I made the mentioned changes, the idle seems to be extremely improved. The AOS says it's been on the battery for 4+ hrs. CPUSpy is accounting for 3h 12 min and showing 96% of that in deep sleep. About phone says battery is still at 99%.
 
Last edited:

akaleshnikov

Senior Member
Dec 18, 2011
107
15
Xiaomi Poco F3
Entropy, attached are my wakelocks.txt and dmesg.txt

I would've analyzed in excel myself but I've never done formulaic work with it, and couldn't figure out how to do it.

Total wake time: 1hr 13m
Battery Drain: 4%

CPU Spy information:
80% deep sleep 59:16
9% 200mhz 06:43
6% 800mhz
2% 1000mhz
1% 500mhz

Firmware: CheckROM RevoHD V6
Kernel: Siyah 2.6.13 (noop I/O scheduler, smartassV2 governor, underclocked 1000mhz and undervolted)
Radio: KH3

I'll try and get a longer reading by doing it overnight, but I use Sleep as An Android to wake me up in the morning and that'd skew the data heavily
 
Last edited:

Spo0f

Senior Member
Jan 23, 2012
365
57
Hi guys,

while i'm reading through the thread, here is some wireshark from me. I see a little of the mentioned bug, few APR request, 2-3 IPv6 requests and huge amount of things that i cannot identify. Expect Yahoo ofc, but it does not seems to be that huge battery drain.

The problem is that at workside i get HUGE battery drain on WiFi - like 50% for 8 hours.

Can someone help me with this? Usually i have huge locks from wlan_wake and deleted_wake_lokcs.

This is with LA4/LA6.

I've identify that the biggest packages are send and received to Google and something like "CDNetworks".

Thank you in advance.
 

Attachments

  • shark_dump_1331710987.zip
    9.7 KB · Views: 3
Last edited:

duowing

Senior Member
Dec 14, 2010
537
106
Cleveland, OH
I've been following this thread and thanks to it have pretty much solved any issues with my phone constantly waking on 3G. With 3G on I pretty much have great battery life. With Wi-fi on my phone never goes to sleep. I've used wireshark over say a 10 minute period to try and analyze things. I see stuff, but I'm not exactly sure what it is. The biggest thing is that it appears my router/modem is continuously sending out ARP requests. It goes through what appears every single address and just continues to do it over and over and over. I don't know if this is the reason I'm not sleeping on wi-fi? I got up in the morning unplugged my phone rebooted it, reset cpu spy, and after a little over an hour of time on. Didn't touch the phone at all, I had 7 minutes of deep sleep. The rest remained at 200Mhz. I know this is the SII forum and I'm using the Galaxy Note, but hopefully you guys can give me some info. Is this just my phone or is it something going ridiculous with my wireless?

I just did a quick couple minute poll on my Galaxy Nexus on Wi-Fi and it looks like it's seeing these same ARP requests, but it looks like my Nexus at least goes into deep sleep. I added the dump from the Nexus as well. These are at different days/different times so unfortunately network activity may be different between the two. Hopefully someone can compare these and see if they have any recommendations.

Thanks!
 

Attachments

  • shark_dump_1331615913.zip
    17.1 KB · Views: 0
  • shark_dump_nexus.zip
    11.1 KB · Views: 1

alacrify

Senior Member
Jan 12, 2009
3,437
1,903
I've been following this thread and thanks to it have pretty much solved any issues with my phone constantly waking on 3G. With 3G on I pretty much have great battery life. With Wi-fi on my phone never goes to sleep. I've used wireshark over say a 10 minute period to try and analyze things. I see stuff, but I'm not exactly sure what it is. The biggest thing is that it appears my router/modem is continuously sending out ARP requests. It goes through what appears every single address and just continues to do it over and over and over. I don't know if this is the reason I'm not sleeping on wi-fi? I got up in the morning unplugged my phone rebooted it, reset cpu spy, and after a little over an hour of time on. Didn't touch the phone at all, I had 7 minutes of deep sleep. The rest remained at 200Mhz. I know this is the SII forum and I'm using the Galaxy Note, but hopefully you guys can give me some info. Is this just my phone or is it something going ridiculous with my wireless?

I just did a quick couple minute poll on my Galaxy Nexus on Wi-Fi and it looks like it's seeing these same ARP requests, but it looks like my Nexus at least goes into deep sleep. I added the dump from the Nexus as well. These are at different days/different times so unfortunately network activity may be different between the two. Hopefully someone can compare these and see if they have any recommendations.

Thanks!

I didn't look at the shark dump (don't have the resources at work), but sounds like the Note has the same sucky problem the GSII does with UCKK6 - it doesn't filter out the ARP requests like it should. I fixed this by killing the services on my Win 7 network that were doing the continual broadcasts. You can find that here: http://xdaforums.com/showpost.php?p=23337687&postcount=514

If that doesn't do it, maybe someone else here will chime in, but you're probably better off in the Note forums building off each others knowledge.
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
I've been following this thread and thanks to it have pretty much solved any issues with my phone constantly waking on 3G. With 3G on I pretty much have great battery life. With Wi-fi on my phone never goes to sleep. I've used wireshark over say a 10 minute period to try and analyze things. I see stuff, but I'm not exactly sure what it is. The biggest thing is that it appears my router/modem is continuously sending out ARP requests. It goes through what appears every single address and just continues to do it over and over and over. I don't know if this is the reason I'm not sleeping on wi-fi? I got up in the morning unplugged my phone rebooted it, reset cpu spy, and after a little over an hour of time on. Didn't touch the phone at all, I had 7 minutes of deep sleep. The rest remained at 200Mhz. I know this is the SII forum and I'm using the Galaxy Note, but hopefully you guys can give me some info. Is this just my phone or is it something going ridiculous with my wireless?

I just did a quick couple minute poll on my Galaxy Nexus on Wi-Fi and it looks like it's seeing these same ARP requests, but it looks like my Nexus at least goes into deep sleep. I added the dump from the Nexus as well. These are at different days/different times so unfortunately network activity may be different between the two. Hopefully someone can compare these and see if they have any recommendations.

Thanks!

I'll need to look at the dumps when I get time (I've been busy lately) - but which firmware are you on?

Some bases (XXKI3, UCKK6, probably XWKK5) block the ARP filters from working right, on other bases (XWKL1, XWLA4) the ARP filters seem to work well.
 

duowing

Senior Member
Dec 14, 2010
537
106
Cleveland, OH
I'm on the LB1 Rom for the note, I'm now running a custom Rom and I just flashed the LA4 Baseband as someone said it seems to work better with data connections. So I'm giving that a try. I saw there was a new LC1 Rom/Kernel with LB2 baseband just released for the Note. Supposedly this will be the last GB rom before ICS so I'm going to give that a try. As for 3G I checked after about an hour and a half in CPU spy and my deep sleep was I believe 96%. So I'm good as far as programs running in the background goes. At least over mobile data. Thanks for the help guys. I was looking around in the Note section and couldn't find any real topics on this.
 

jsolares

Senior Member
Feb 20, 2011
83
15
Latitude was eating through my battery, now i wonder if the drain i had on the ICS roms wasn't also due to Latitude, i signed out of latitude and disabled wifi for location.
 

simplicityy

Senior Member
Oct 12, 2011
120
9
I keep wanting to install Skype to make use of my phone's front camera, but I know it's a wreck of an app. Better app? Or do you think since Microsoft bought out Skype recently that they will fix it?
 

JustinW3

Senior Member
Feb 20, 2012
173
45
I keep wanting to install Skype to make use of my phone's front camera, but I know it's a wreck of an app. Better app? Or do you think since Microsoft bought out Skype recently that they will fix it?

I wouldn't hold my breath for MS fixing Skype. Why not keep Skype and just freeze it on TiBu when you're not using it. Then if you want to use it, thaw it.

Will this work? I'm not 100% on it, can somebody else comment on this idea?
 

sirhc81

Senior Member
May 10, 2008
110
2
Bergen County, NJ
my results

hello entropy, just wanted to post my results and say thank you for all of your fine work, i'm currently running unnamed 1.3.2 w/standard kernel. if i can improve the battery life any further just let me know :)
 

chamonix

Recognized Contributor
Nov 7, 2008
5,048
19,623
Berlin
Google Pixel 6 Pro
hello entropy, just wanted to post my results and say thank you for all of your fine work, i'm currently running unnamed 1.3.2 w/standard kernel. if i can improve the battery life any further just let me know :)

You main problem is network traffic. Looking at the alarms and the fact that wifi is on I believe that google maps is besides facebook the reason for the overhead. You could try to disable wifi when not using it to see if part of the awake time goes down (as google maps caching options distinguish between Wifi and Cell)
 
  • Like
Reactions: sirhc81

dandrumheller

Senior Member
Jul 10, 2010
3,625
1,137
Southern Maine / Seacoast NH
multipdp kernel wakelock

wondering if anyone can help me track down a kernel wakelock that I am seeing on ICS that I wasn't on GB?

I'm currently on ShoStock2 RC3, and I'm seeing this "multipdp" kernel wakelock in BBS. It is by far the highest time wakelock on the device. As I write this it is at 42m of kernel wakelock in 8h6m of uptime, with 435 counts, so it's firing pretty close to once a minute. I don't ever recall seeing it on GB. I'm currently monitoring it while on the mobile data network, and will check to see if it behaves similarly on WiFi.

Google results showed a couple mentions of it in the BBS thread and the i9100 forum here on XDA, and it was also mentioned in a poor battery life thread for i9100 on AndroidForums. But in all these cases, the post was never followed up by an answer that addressed it (or at least I didn't see it - read about 100 posts past it's mention in i9100 forum here...)

Could this be caused by an app misbehaving because it's not built properly for ICS? I'm running the same apps I had on GB ROMs, and not noticing any "out of the ordinary" data use by installed apps.

In addition to this (perhaps related) is an apparent discrepancy between reported awake time in BBS and the details of the android OS item in the built in battery monitoring in ICS. Android OS seems to report significantly higher awake time than BBS. Right now, Android OS reports 3h18m of awake time, while BBS reports 2h37m.

Hope someone can point me in a direction to try to troubleshoot this...

Thanks,

dd
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
wondering if anyone can help me track down a kernel wakelock that I am seeing on ICS that I wasn't on GB?

I'm currently on ShoStock2 RC3, and I'm seeing this "multipdp" kernel wakelock in BBS. It is by far the highest time wakelock on the device. As I write this it is at 42m of kernel wakelock in 8h6m of uptime, with 435 counts, so it's firing pretty close to once a minute. I don't ever recall seeing it on GB. I'm currently monitoring it while on the mobile data network, and will check to see if it behaves similarly on WiFi.

Google results showed a couple mentions of it in the BBS thread and the i9100 forum here on XDA, and it was also mentioned in a poor battery life thread for i9100 on AndroidForums. But in all these cases, the post was never followed up by an answer that addressed it (or at least I didn't see it - read about 100 posts past it's mention in i9100 forum here...)

Could this be caused by an app misbehaving because it's not built properly for ICS? I'm running the same apps I had on GB ROMs, and not noticing any "out of the ordinary" data use by installed apps.

In addition to this (perhaps related) is an apparent discrepancy between reported awake time in BBS and the details of the android OS item in the built in battery monitoring in ICS. Android OS seems to report significantly higher awake time than BBS. Right now, Android OS reports 3h18m of awake time, while BBS reports 2h37m.

Hope someone can point me in a direction to try to troubleshoot this...

Thanks,

dd

I'll need some time to do research, but based on the name, multipdp may be the new name for svnet-dormancy.

As to Android OS reporting high awake time - that's because Android 4.0.3 and below have a display bug that adds screen-on time to that statistic instead of subtracting it.
 
  • Like
Reactions: shoman94

dandrumheller

Senior Member
Jul 10, 2010
3,625
1,137
Southern Maine / Seacoast NH
I'll need some time to do research, but based on the name, multipdp may be the new name for svnet-dormancy.

As to Android OS reporting high awake time - that's because Android 4.0.3 and below have a display bug that adds screen-on time to that statistic instead of subtracting it.

Thank you for getting back to me on this Entropy. Sorry I missed the simple math on the conflicting awake times. Since that's the case, then AOS should be reporting (BBS awake + (2*screen on))? Or (1*screen on) if BBS is also reporting screen on as awake?

Further observation of the multipdp wakelock indicates that it is only present when on mobile data - does not appear to increase significantly when on WiFi. If I understand correctly what svnet-dormancy is, that would be consistent with multipdp being a renamed svnet-dormancy, would it not?
 

Entropy512

Senior Recognized Developer
Aug 31, 2007
14,088
25,086
Owego, NY
Thank you for getting back to me on this Entropy. Sorry I missed the simple math on the conflicting awake times. Since that's the case, then AOS should be reporting (BBS awake + (2*screen on))? Or (1*screen on) if BBS is also reporting screen on as awake?

Further observation of the multipdp wakelock indicates that it is only present when on mobile data - does not appear to increase significantly when on WiFi. If I understand correctly what svnet-dormancy is, that would be consistent with multipdp being a renamed svnet-dormancy, would it not?

Yes, that is correct.

One of the things new in Android 4 is lumping all wakelocks not accounted for by apps under Android OS. (This should include kernel wakelocks.) Screen time was supposed to be removed from this number, but a math error caused it to be added instead.

I think the math might still have some issues that could lead to some things being double-counted but I'm not sure.
 

dandrumheller

Senior Member
Jul 10, 2010
3,625
1,137
Southern Maine / Seacoast NH
Yes, that is correct.

One of the things new in Android 4 is lumping all wakelocks not accounted for by apps under Android OS. (This should include kernel wakelocks.) Screen time was supposed to be removed from this number, but a math error caused it to be added instead.

I think the math might still have some issues that could lead to some things being double-counted but I'm not sure.

Understood. I think you are right about other wakelocks getting double counted - when I have been paying closer attention to wakelock times, quick adding up of wakelocks do seem to indicate a higher total than the total awake time being reported by BBS - but I haven't been on ICS ROMs long enough to have spent the time to do careful math on them. I'll keep an eye on this. Are there any particular areas for me to look at where info would be useful to you?
 

test9876543

Senior Member
Jun 13, 2009
53
14
I'll need some time to do research, but based on the name, multipdp may be the new name for svnet-dormancy.

As to Android OS reporting high awake time - that's because Android 4.0.3 and below have a display bug that adds screen-on time to that statistic instead of subtracting it.

I've got wakelock issue with multipdp as well and with secril_fd-interface.

I've been on CM9 nightlies for a few months and am currently on the CODEWORKX 2012-03-31 release with his 3.0.26 Kernel, but the same kernel wakelocks have been there on the Samsung kernels before as well. I've got two google accounts setup and one twitter account. I tried googling for any details but only found the sources for multipdp and don't understand enough to figure out what that driver actually does and why it would keep my phone awake all the time without doing anything.
The stats below are taken after charging all night in airplane mode, then unplugging and going back to regular mobile data. Have not received any mails/texts/tweets in the past 1.5 hours, still these two keep my phone awake for some reason. Any help would be much appreciated. If you need more details, let me know. Thanks.

Statistic Type: (0) Since Charged
Since 1 h 28 m 8 s

Awake (): 53 m 13 s (3193 s) Ratio: 60.4%
Screen On (): 11 m 53 s (713 s) Ratio: 13.5%

================
Kernel Wakelocks
================
"multipdp" (): 37 m 13 s (2233 s) Cnt:(c/wc/ec)62/0/62 42.1%
"secril_fd-interface" (): 34 m 53 s (2093 s) Cnt:(c/wc/ec)157/0/0 39.5%
 

Attachments

  • BetterBatteryStats-2012-04-01_124942797.txt
    4.1 KB · Views: 5

mzaur

Senior Member
Nov 13, 2011
575
58
NJ
I'm running UnNamed Rom 2.2.1 which is based on UCKK6 and battery life is sucking. With 6 hours of uptime, I have 33minutes of kernel wakelocks from [P]_NetworkLocationLocator, 15min from svnet, 13min from wlan_rx_wake.

Weird thing is that I set wifi sleep policy to turn off when screen turns off, but the picture below shows that it seems to stay on.. and my phone keeps intermittently coming on for some reason.

Is the only fix to flash to an other ROM?
 

Attachments

  • SC20120401-141109.jpg
    SC20120401-141109.jpg
    17.7 KB · Views: 275

Top Liked Posts

  • There are no posts matching your filters.
  • 73
    In many cases, people who have battery drain issues have a tendency to end up being found to be using a known battery draining app or configuration. To help these people, I'm going to try to start a list here. I will, in the case of known rogue apps, include the reporting date so people can try updates to see if drain is fixed. (For example, Facebook is rarely a culprit any more, but it was the #1 most common battery eater in 2010.) The primary focus here will be things that shouldn't drain your battery but do.

    Firmware bugs:
    1. The UCKK6 OTA update contains a number of issues with wifi and bluetooth. Among these is that an oddball feature of our Wifi/Bluetooth chipset goes nuts and wakes up the phone once per second intermittently. Rebooting temporarily fixes it, turning off wifi temporarily fixes it, only permanent fix is to ditch UCKK6. http://xdaforums.com/showthread.php?t=1409513 for more details - Appears as a variant of the Android OS "bug" - this is the only one that is actually 100% a firmware bug. International XWKK5 is also affected.

    LAN Environment (WiFi):
    • Broadcast LAN traffic can wake your wifi chip often. This also manifests as the Android OS "bug", but it's a small problem with the firmware base (XXKI3 and UCKK6 are known to be affected) and mostly a network problem. Examples I've seen so far include:
      • Windows Client Backup
      • UPnP (DLNA) SSDP
      • Dropbox Lan Sync Discovery Protocol
      • Buggy piece-of-**** routers that spam lots of ARP requests continuously - The 2Wire routers that are required for UVerse access apparently fit in this category.
    You are more likely to have the above issue on some firmware bases than others. For example, XXKI3 disables all of the chip's packet filters, making it vulnerable to this sort of thing. UCKH7 and XWKL1 don't, leading to significantly improved life on "dirty" networks. UCKK6 almost surely also has the same problem.

    Configuration issues:
    1. Hotmail calendar sync
    2. Misconfigured Microsoft Exchange servers - 1) is a special case of this. At least one person has reported that calendar sync to a non-Hotmail account was problematic for them, but email sync was OK
    3. A bad Exchange configuration - the client apparently goes nuts if it can't contact the server
    4. BLN - On Galaxy S II devices, there is no stable BLN implementation that does not hold a wakelock when a notification is active. This means that an active BLN notification will drain about 4-5%/hour. I say this in bold letters in my kernel thread, but somehow people still don't realize it...

    Rogue apps:
    1. Words with Friends (October 2011)
    2. Skype (October 2011) - Particularly insidious, as it does not directly hold a wakelock. However, it causes lots of background network activity, and this activity keeps your phone awake. Since most of the time is spent wakelocked in the network stack, Skype drain shows as Android OS.
    3. Any IM app that works similarly to Skype is likely to have the same issues.
    4. AP Mobile Widget on stock AT&T ROMs - this one also blows through your data allotment quickly if you don't have unlimited data
    5. AT&T Smart WiFi can sometimes hold excessive wakelocks - this is why AT&T bloat is bad for you.

    The Obvious:
    1. 3D or animation/action-intensive games

    The Rare:
    Apps that occasionally go nuts, but not frequently
    1. Facebook - I've had it wakelock me once, and also, Facebook chat may have triggered my first obvious "AOS bug" episode once - so far, it's been responsible for drain once this month
    2. StartingAlertService - some sort of Calendar notification related bug

    The False Blame:
    1. GPS Status and Toolbox - may appear to be high-drain but is actually not draining - this is an Android battery reporting bug - see http://xdaforums.com/showpost.php?p=23106668&postcount=491 for more details. Thank you for the info and the great app rhornig.

    If you're having battery drain issues, I suggest the following:
    1. Install BetterBatteryStats. The XDA edition from the author's thread on these forums is free. (Market version is paid.)
    2. Also, having CPUSpy to see deep sleep percentages is VERY useful
    3. BBS now shows kernel wakelocks - make sure to check these. If you have an older version that doesn't show kernel wakelocks, use the instructions below.

    Get ADB up and running (Google it, and if you're on Windows, Googling Droid Explorer may help)
    Using ADB, do the following:
    Code:
    adb shell cat /proc/wakelocks > wakelocks.txt
    adb shell dmesg > dmesg.txt
    Zip em' up and post em' here for analysis.

    Edit: Specifically, to get a good baseline measurement of idle drain - make sure to have CPUSpy installed for this procedure:
    Charge phone to full
    Reboot
    Reset timers in CPUSpy, otherwise the percentages and bars will be wacky
    Let the phone sit for a while - Overnight is best. Then provide data:

    Deep sleep percentage
    Time the phone was sitting
    Percentage battery drained
    I don't need screenshots of the above, just the numbers. Screenshots use up massive amounts of thread space
    Grab /proc/wakelocks as mentioned above and post it, OR use BetterBatteryStats 1.4 or above to pull kernel wakelocks.

    Note: If you're at or below 1%/hour idle drain, not much point of posting your wakelocks.

    If you have high wlan_wake, wlan_rx_wake, or svnet-dormancy wakelock times, then you have an app eating data or one of the wifi wakeup bugs described above. Install Shark for Root - https://market.android.com/details?id=lv.n3o.shark

    Start it, and change parameters from:
    Code:
    -vv -s 0
    to
    Code:
    -vv -s 68
    This tells it to only capture the first 68 bytes of each packet, which is all we need for this purpose. This provides two benefits: A smaller capture, and privacy for you. (It captures packet headers but not contents)
    Then start a capture and let it sit for a bit.

    Note that your drain will be higher during the capture than normal - we're collecting data here, not directly nuking the drain.

    After a while where you are positive you are encountering drain, stop Shark and then pull the .pcap file - load it in Wireshark on your PC or post it here. If you post it here, MAKE SURE you have a truncated capture as instructed above!
    10
    I just confirmed - multipdp is the new name for svnet-dormancy - same 6000ms wakelock timer.
    6
    GPS Status and Toolbox - battery usage

    Hi all,

    I'm the author of GPS Status and Toolbox mentioned also on the first post.

    I'm receiving several complaints about the battery issue and investigated the reports, because GPS Status was designed explicitly NOT to run in background. It does not have services, alarms, does not start at boot. In fact once you close it, it cannot be activated without user interaction.

    Also it was strange people were reporting excessive use when they have not used the app at all. Here are my findings:

    It seems that the battery measurement routines are buggy in android (ICS still has this bug). The battery measurement service registers when an app starts using a sensor, but sometimes forgets to unregister this when the app releases it. (even if you kill the app's process). When the battery use is displayed the battery screen calculates the battery use by adding up the different ways a program can consume the battery (CPU, GPS, network radio use, and sensor use). The sensor use is basically calculated by subtracting the last sensor start value from the current time and the difference is multiplied by the sensors power requirement (per second). Because the system does not de-registers the sensor use correctly some programs are treated as using the sensors while in fact they are not even existing as a running process. As time passes this 'phantom' battery use grows even relative to the rest of the system's power use.

    In short this means that when the device is in sleep mode and consumes almost no battery, the calculation assumes that the sensors are still running. This results in increasing battery use reports for apps that use sensors.

    This does not happen always, but I was able to reproduce it with practically any app that uses several sensors. The effect is most visible on Samsung phones because I guess samsung assigns higher power requirement values for the ensors than other vendors.

    Long story short, DO NOT trust the battery usage display. It may give you an indication, but it is just a guess. (however seeing the code, the CPU usage statistics seems to come from the kernel so they are much more reliable).

    As a rule of thumb, higher battery use should come with higher CPU use. If you see high battery use for a task that hast consumed only low amount of CPU then chances are that the battery use is not correctly displayed.

    Hope this helps
    6
    I'm one of those people that really encourages people to search and try to help themselves. I'm probably even more sarcastic about it than most (though not in a mean way... just in a sarcastic way ;))

    However, the link you just posted was WORSE than useless. Unless a person is familiar with both the linux kernel AND the modifications android makes to the kernel, a link to a source file from the kernel does what? It will only create more questions.

    Even someone that is familiar with the kernel and android, and even an expert in C, would get questions from that link...

    Here's what I got from that source file: There's a symbol exported from the kernel (available to modules, etc) that allows both kernel and non-kernel code to call "destroy_wake_lock()" and if that happens, the stats on the destroyed wake lock are added in to some global "deleted_wake_locks" structure.

    This doesn't make clear if the kernel deleted_wake_locks structure is the same thing as displayed in BBS. It also, perhaps misleadingly, implies that every single wakelock in the system is eventually destroyed and all the time for those old wakelocks is added to the deleted_wake_locks. That would, in turn, lead logically to the question of "so if GPS is causing a wakelock, then I turn off the GPS, does the time for that wakelock show up as a GPS wakelock, in deleted wakelocks, both or neither?" We might even get people assuming that BBS wakelock stats are useless, as all the wakelocks have to eventually get destroyed, and if they do, their stats will just get dumped into this huge meaningless "deleted" pool.

    (Of course, I have the ability to dig deeper into this and find the answers - but most people don't. Even most of the people who develop for android are NOT proficient in C and kernel issues.)

    So... was that link supposed to be some kind of answer, or something to encourage more questions?

    :)

    Gary
    4
    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..
    Doesn't look like low service - you were on wifi, so data was going over wifi.

    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