[BetterBatteryStats] shinew:
Thanks for taking the time to look into it! Here are more details:

screen was off, unplugged, no phone calls, wifi on and set to never sleep,cell radio & background sync were all on

I think it only occurs when the screen is off, because as soon as I turn on the screen sand start using the phone, the % for "sec-battery-adc" decreases

there is no "sec-battery-adc" count when the phone is plugged into an outlet

I downloaded the new 1.6rc1 yesterday and logged it last night before I went to bed and slept for about 5hr45min. Here is the dump:

===================
General Information
===================
BetterBatteryStats version: 1.6.0.0RC1
Creation Date: 2012-02-06 09:40:33
Statistic Type: (4)
Since
VERSION.RELEASE: 2.3.6
BRAND: samsung
DEVICE: SGH-T989
MANUFACTURER: samsung
MODEL: SGH-T989
===========
Other Usage
===========
=========
Wakelocks
=========
================
Kernel Wakelocks
================
"sec-battery-adc" (): 2 h 2 m 50 s (7370 s) Cnt:(c/wc/ec)2468/0/0 34.9%
"wlan_rx_wake" (): 24 m 3 s (1443 s) Cnt:(c/wc/ec)2216/0/2216 6.8%
"alarm_rtc" (): 19 m 19 s (1159 s) Cnt:(c/wc/ec)2497/1768/161 5.5%
"wlan_wake" (): 4 m 30 s (270 s) Cnt:(c/wc/ec)5797/665/0 1.3%
"sec-battery-monitor" (): 2 m 57 s (177 s) Cnt:(c/wc/ec)4925/0/0 0.8%
"[P]_AlarmManager" (): 1 m 28 s (88 s) Cnt:(c/wc/ec)2757/0/0 0.4%
"[P]_Tasker.UserAbsentWakelock" (): 1 m 11 s (71 s) Cnt:(c/wc/ec)35/0/0 0.3%
"alarm" (): 58 s (58 s) Cnt:(c/wc/ec)2777/0/0 0.3%
"[P]_*sync*" (): 34 s (34 s) Cnt:(c/wc/ec)5/0/0 0.1%
"sdio_al" (): 8 s (8 s) Cnt:(c/wc/ec)88/0/0 0.0%
"[P]_GmailProviderProviderChangedBroadcastWakeLock" (): 8 s (8 s) Cnt:(c/wc/ec)4/0/0 0.0%
"[P]_NetworkLocationPassiveCollector" (): 4 s (4 s) Cnt:(c/wc/ec)1/0/0 0.0%
"power-supply" (): 4 s (4 s) Cnt:(c/wc/ec)4925/0/0 0.0%
"rmt_storage" (): 3 s (3 s) Cnt:(c/wc/ec)14/0/0 0.0%
"sec-battery-measure" (): 3 s (3 s) Cnt:(c/wc/ec)2467/0/0 0.0%
"[P]_AlarmReceiver" (): 3 s (3 s) Cnt:(c/wc/ec)4/0/0 0.0%
"mmc4" (): 2 s (2 s) Cnt:(c/wc/ec)710/5/710 0.0%
"mmc_delayed_work" (): 1 s (1 s) Cnt:(c/wc/ec)8713/0/0 0.0%
"[P]_GTALK_CONN" (): 1 s (1 s) Cnt:(c/wc/ec)71/0/0 0.0%
"[P]_RILJ" (): 1 s (1 s) Cnt:(c/wc/ec)161/0/0 0.0%
"radio-interface" (): 1 s (1 s) Cnt:(c/wc/ec)41/0/0 0.0%
"[P]_M" (): 1 s (1 s) Cnt:(c/wc/ec)59/0/0 0.0%
"[P]_WifiService" (): (0 s) Cnt:(c/wc/ec)1852/0/0 0.0%
"[P]_backupdb" (): (0 s) Cnt:(c/wc/ec)1/0/0 0.0%
"[P]_BWL" (): (0 s) Cnt:(c/wc/ec)1/0/0 0.0%
"event3-307" (): (0 s) Cnt:(c/wc/ec)9/1/0 0.0%
"[P]_E" (): (0 s) Cnt:(c/wc/ec)18/0/0 0.0%
"[P]_SyncManagerHandleSyncAlarm" (): (0 s) Cnt:(c/wc/ec)10/0/0 0.0%
"[P]_GOOGLE_C2DM" (): (0 s) Cnt:(c/wc/ec)8/0/0 0.0%
"[P]_ServiceStateTracker" (): (0 s) Cnt:(c/wc/ec)3/0/0 0.0%
"[P]_NetworkLocationCallbackRunner" (): (0 s) Cnt:(c/wc/ec)12/0/0 0.0%
"KeyEvents" (): (0 s) Cnt:(c/wc/ec)258/0/0 0.0%
"[P]_keyguardWakeAndHandOff" (): (0 s) Cnt:(c/wc/ec)2/0/0 0.0%
"rpcrotuer_sdio_xprt" (): (0 s) Cnt:(c/wc/ec)196/0/0 0.0%
"rpc_sdio_xprt_read" (): (0 s) Cnt:(c/wc/ec)196/0/0 0.0%
"rpc_reply" (): (0 s) Cnt:(c/wc/ec)22/0/0 0.0%
"rpc_read" (): (0 s) Cnt:(c/wc/ec)47/0/0 0.0%
=========
Processes
=========
======================
Alarms (requires root)
======================
com.morrison.applock (): Wakeups: 2115
ccc71.bmw.pro (): Wakeups: 353
com.google.android.gsf (): Wakeups: 34
net.dinglisch.android.tasker (): Wakeups: 35
android (): Wakeups: 22
com.google.android.apps.maps (): Wakeups: 15
com.levelup.beautifulwidgets (): Wakeups: 1
com.whatsapp (): Wakeups: 1
========
Services
========
Active since: The time when the service was first made active, either by someone starting or binding to it.
Last activity: The time when there was last activity in the service (either explicit requests to start it or clients binding to it)
See http://developer.android.com/reference/android/app/ActivityManager.RunningServiceInfo.html
net.dinglisch.android.tasker (net.dinglisch.android.tasker.MyAccessibilityService)
Active since: 2 m 2 s
Last activity: 2 m 2 s
Crash count:0
com.morrison.applock (com.morrison.applock.service.AppLockService)
Active since: 2 m 28 s
Last activity: 3 h 6 m 40 s
Crash count:0
ccc71.bmw.pro (ccc71.bmw.lib.bmw_service)
Active since: 2 m 36 s
Last activity: 19 m 36 s
Crash count:0
com.google.android.apps.googlevoice (com.google.android.apps.googlevoice.UpdateService)
Active since: 2 m 7 s
Last activity: 25 m 34 s
Crash count:0
com.sec.android.app.factorytest (com.sec.android.app.rilsupport.RilSupportService)
Active since: 2 m 23 s
Last activity: 33 m 3 s
Crash count:0
system (com.android.server.DrmEventService)
Active since: 2 m 20 s
Last activity: 2 m 20 s
Crash count:0
com.google.android.apps.googlevoice (com.google.android.apps.googlevoice.widget.WidgetService)
Active since: 2 m 15 s
Last activity: 25 m 38 s
Crash count:0
com.google.process.gapps (com.google.android.location.NetworkLocationService)
Active since: 1 m 59 s
Last activity: 1 m 59 s
Crash count:0
system (com.android.internal.service.wallpaper.ImageWallpaper)
Active since: 1 m 57 s
Last activity: 1 m 57 s
Crash count:0
net.dinglisch.android.tasker (net.dinglisch.android.tasker.MonitorService)
Active since: 2 m 35 s
Last activity: 3 h 5 m 22 s
Crash count:0
com.android.systemui (com.android.systemui.statusbar.StatusBarService)
Active since: 1 m 56 s
Last activity: 1 m 56 s
Crash count:0
com.google.android.apps.googlevoice (com.google.android.apps.googlevoice.CallLogService)
Active since: 2 m 36 s
Last activity: 2 m 36 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.PushMessagingRegistrar)
Active since: 2 m 28 s
Last activity: 2 m 28 s
Crash count:0
com.whatsapp (com.whatsapp.messaging.MessageService)
Active since: 2 m 30 s
Last activity: 2 m 30 s
Crash count:0
com.asksven.betterbatterystats_xdaedition (com.asksven.betterbatterystats.BetterBatteryStatsService)
Active since: 2 m 25 s
Last activity: 2 m 25 s
Crash count:0
com.google.process.gapps (com.google.android.location.internal.server.NetworkLocationService)
Active since: 2 m 2 s
Last activity: 2 m 3 s
Crash count:0
com.android.phone (com.samsung.sec.android.application.csc.CscUpdateService)
Active since: 2 m 25 s
Last activity: 2 m 25 s
Crash count:0
com.noshufou.android.su (com.noshufou.android.su.service.ResultService)
Active since: 6 h 42 m 38 s
Last activity: 3 h 6 m 45 s
Crash count:0
com.skvalex.callrecorder (com.skvalex.callrecorder.service.CallRecorderService)
Active since: 2 m 15 s
Last activity: 2 m 15 s
Crash count:0
com.android.phone (com.android.stk.StkAppService)
Active since: 2 m 21 s
Last activity: 2 m 21 s
Crash count:0
system (com.google.android.backup.BackupTransportService)
Active since: 1 m 55 s
Last activity: 1 m 55 s
Crash count:0
com.google.android.apps.maps:NetworkLocationService (com.google.android.location.internal.server.NetworkLocationService)
Active since: 2 m 28 s
Last activity: 32 m 35 s
Crash count:0
com.whatsapp (com.whatsapp.ExternalMediaManager)
Active since: 2 m 43 s
Last activity: 2 m 44 s
Crash count:0
com.android.phone (com.android.phone.BluetoothHeadsetService)
Active since: 1 m 55 s
Last activity: 1 m 59 s
Crash count:0
com.wssyncmldm (com.wssyncmldm.DMService)
Active since: 2 m 20 s
Last activity: 32 m 28 s
Crash count:0
com.google.process.gapps (com.google.android.gsf.gtalkservice.service.GTalkService)
Active since: 2 m 3 s
Last activity: 2 m 56 s
Crash count:0
com.baidu.input (com.baidu.input.ImeService)
Active since: 1 m 57 s
Last activity: 1 m 58 s
Crash count:0

I also used CPU Spy to log the processor deep sleep & active time, here is the screen shot:

I might be completely off here but here is my theory. Even though "sec-battery-adc" was logged as responsible for holding the wakelock, could it be that it doesn't really hold the wakelock?? I know it sounds contradictory but I assume any Wakelock prevents Deep Sleep, with 5:50(Total State Time in CPU Spy) - 3:18(Deep Sleep), there should be max of 2:40min of wakelock time. I've roughly calculated the total "Kernel Wakelock" time(Partial Wakelock is missing from 1.6rc1), amd the recorded wakelock time alone is more than 3hrs+. According to your explanation of the Wakelock Count, this estimated time could only be higher but not lower. So the numbers don't really add up...

----------------------------------------------

Unrelated to the issue above, i think there are couple of bugs in the 1.6RC1, one of them is partial wakelock not being recorded, the other is that the graph for "Screen On" is wrong. Below are the graphs from Battery Monitor Widget Pro vs BBS, BMWP is correct here as most of the time I was asleep with no phone calls, but BBS is showing lots of Screen On time.

thank you!