[BetterBatteryStats] Karpfenhai:
I had already but i afraid you will not like my suggestions..;)

Unfortunately, Tasker is not my line of country since i dont use it.

Wakelocks
=========
Sidekick_CalendarIntentService (com.google.android.googlequicksearchbox.Google Search): 22 m 37 s (1357 s) Count:42 3.7% --> See below (Alarms)
com.keramidas.TitaniumBackup.service.WorkerService (com.keramidas.TitaniumBackup.Titanium Backup): 16 m 18 s (978 s) Count:1 2.7% --> Why do you backup to the cloud?

NetworkLocationLocator (Google Services): 8 m 27 s (507 s) Count:124 1.4% --> See below (Alarms)
NetworkLocationLocator (com.google.android.apps.maps.Maps): 7 m 17 s (437 s) Count:107 1.2% --> See below (Alarms)
NetworkLocationCallbackRunner (Google Services): 2 m 22 s (142 s) Count:348 0.4% --> See below (Alarms)
NetworkLocationCallbackRunner (com.google.android.apps.maps.Maps): 1 m 22 s (82 s) Count:306 0.2% --> See below (Alarms)
NetworkLocationPassiveCollector (com.google.android.apps.maps.Maps): 28 s (28 s) Count:325 0.1% --> See below (Alarms)
NetworkLocationActiveCollector (com.google.android.apps.maps.Maps): 7 s (7 s) Count:432 0.0%
NetworkStats (Android System): 7 s (7 s) Count:97 0.0%
GpsLocationProvider (Android System): 5 s (5 s) Count:303 0.0%

EntriesRefresh_wakelock (com.google.android.googlequicksearchbox.Google Search): 45 s (45 s) Count:81 0.1%
Sidekick_TrafficIntentService_onHandleIntent (com.google.android.googlequicksearchbox.Google Search): 34 s (34 s) Count:121 0.1%

GOOGLE_C2DM (Google Services): 4 s (4 s) Count:350 0.0% --> Google Cloud Backup, get rid of it .. you use titanium, why 2 kinds of backup?
ConnectivityService (Android System): 4 s (4 s) Count:1366 0.0%

NLP PendingIntent client in com.google.android.googlequicksearchbox (com.google.android.apps.maps.Maps): 1 s (1 s) Count:431 0.0% --> See below

Kernel Wakelocks
================
"PowerManagerService" (): 35 m 30 s (2130 s) Cnt:(c/wc/ec)1164/0/0 5.8% <-- Collector, does only count all other alerts together

"dhd_wake_lock" (): 22 m 56 s (1376 s) Cnt:(c/wc/ec)1959/111/1959 3.8%
"dhd_dpc_thread" (): 2 m 51 s (171 s) Cnt:(c/wc/ec)[b]72151[/b]/0/0 0.5%
"dhd_watchdog_thread" (): 6 s (6 s) Cnt:(c/wc/ec)[b]37066[/b]/0/0 0.0%

^^ it turns out, this problem is specific to motorola only ;( Some users reported a factory reset could heal this, could you take out your battery for a short while (vodoo) sometoimes this works too, i wouldrecommend a full backup (nandroid) before performing a factory reset!

Try to change the Kernel, this is definitely related to a kernel module or the modem driver --> /drivers/staging/brcm80211/brcmfmac/dhd_linux.c b/drivers/staging/brcm80211/brcmfmac/dhd_linux.c

""mmc_delayed_work" (): 1 s (1 s) Cnt:(c/wc/ec)1049/364/0 0.0% --> Your SD Card

Alarms (requires root)
======================
com.google.android.location (): Wakeups: 224 <-- disable all location based services
com.google.android.apps.maps (): Wakeups: 200 <--Check post 3 for a possible solution
com.google.android.googlequicksearchbox (): Wakeups: 120 <-- Disable calendar sync and maybe freeze google search, i have never used or missed it..;)

Network (requires root)
======================
10069 (eth0) (com.keramidas.TitaniumBackup.Titanium Backup): 72.0 MBytes 96.8% <-- In my opinion your main reason for the battery drop. (due to network traffic)

There is a lot to do, good luck!

---------- Post added at 05:58 PM ---------- Previous post was at 05:53 PM ----------

This dump looks better but something is still wrong, 40 mins on call vs. 30 mins total awake...

And you are still not on the latest version :D

before 1.11 there were counting probs, just install the latest from post 2, thx ;)