[BetterBatteryStats] Karpfenhai:
Okay, lets have a closer look, bur it does not seem too bad.. imho..

What do we have:

Deep Sleep (): 16 h 49 m 59 s (60599 s) Ratio: 80.4% :good:

Awake (): 4 h 6 m 25 s (14785 s) Ratio: 19.6%

-

Screen On (): 3 h 30 m 36 s (12636 s) Ratio: 16.8%

-

Phone On (): 11 m 35 s (695 s) Ratio: 0.9%

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

= 25 Minutes Overhead, thats not much..

So lets try to find what caused these 25 mins, which is really hard to tell.. ;(

=========

Wakelocks

=========

ActivityManager-Launch (Android System): 9 m 20 s (560 s) Count:1837 0.7%

RILJ (Phone): 4 m 32 s (272 s) Count:1427 0.4% <-- looks to much to me, i know its not easy to mach Ril @ modem on cm10 but maybe another modem can improve the situation.

ConnectivityService (Android System): 3 m 32 s (212 s) Count:2511 0.3% <-- seems to be a lot but could also be okay due to playstore traffic

AlarmManager (Android System): 1 m 5 s (65 s) Count:2501 0.1%

NetworkStats (Android System): 14 s (14 s) Count:511 0.0% <-- Normal for this period

WifiStateMachine (Android System): 10 s (10 s) Count:1850 0.0% <-- This looks too much for me too

AlarmManager (Google Services): 7 s (7 s) Count:734 0.0% <-- did you disable autostarts from GSF ?

GTALK_CONN (Google Services): 7 s (7 s) Count:446 0.0% <-- guess its normal due to your huge amount of data transfer from playstore.

Checkin Service (Google Services): 6 s (6 s) Count:578 0.0% <-- did you disable autostarts from GSF ?

ActivityManager-Sleep (Android System): 4 s (4 s) Count:2651 0.0% <-- No clue about that..

keyguardWakeAndHandOff (Android System): 2 s (2 s) Count:1991 0.0% <-- did you disable autostarts from GSF ?

SyncLoopWakeLock (Android System): 1 s (1 s) Count:2565 0.0% <-- did you disable autostarts from GSF ?

================

Kernel Wakelocks

================

"PowerManagerService" (): 20 m 3 s (1203 s) Cnt:(c/wc/ec)823/0/0 1.6%

"l2_hsic" (): 4 m 50 s (290 s) Cnt:(c/wc/ec)3905/31/3905 0.4% <-- related to mobile data traffic

"umts_ipc0" (): 3 m 27 s (207 s) Cnt:(c/wc/ec)2158/0/2158 0.3% <-- self explaining ;)

"deleted_wake_locks" (): 2 m 22 s (142 s) Cnt:(c/wc/ec)76685/61/652 0.2% <--- Wifi ...

"wlan_rx_wake" (): 1 m 26 s (86 s) Cnt:(c/wc/ec)847/0/847 0.1%

"tx_hsic" (): 7 s (7 s) Cnt:(c/wc/ec)15945/0/0 0.0% <-- mobil data send direction

"secril_fmt-interface" (): (0 s) Cnt:(c/wc/ec)7101/0/0 0.0%

"wlan_wake" (): (0 s) Cnt:(c/wc/ec)24184/44/0 0.0%

======================

Alarms (requires root)

======================

com.google.android.gsf (): Wakeups: 156 ----- not a big deal for 16 hours

======================

Network (requires root)

======================

10060 (Wifi) (com.android.vending.Google Play Store): 152.0 MBytes 80.3%

10060 (Mobile) (com.android.vending.Google Play Store): 19.0 MBytes 10.1%

10070 (Wifi) (com.quoord.tapatalkpro.activity.Tapatalk): 5.0 MBytes 3.2%

10083 (Mobile) (com.jv.falcon.pro.Falcon Pro): 3.0 MBytes 1.7%

To be honest i dont see a real problem here...

So im not really sure what to advice, sorry.. im currently on the latest cm10 nightly and my deep sleep is even worse than yours, but my drain is less, so i assume the kernel & modem combination you are using is causing your problem.

2 Last question, how crowded is your wifi? could you try wifi analyzer from market and switch to a less crowded wifi channel? It may bring a measurable difference.

How is your signal receptiion in your area? The syncloop makes me think the mobile network could be unstable.

Good Luck mate!