[Sprint Samsung Galaxy S III] tdunham:
I think people misunderstand how wakelocks and battery life monitoring in general work so if you already know this, bear with me... ;)

The key to getting good battery life it to achieve a state of zen with the phone where it sleeps as deeply as possible with as little battery depletion as possible. The juggling act that is used with kernels, tweaks and other scripts to get the best balance with performance and awake time is fine but if the phone does not sleep well, it's not going to do you any good.

That being said, the ONLY WAY to monitor wakelocks and battery performance accurately is to allow the phone to achieve a deep sleep state for at least several hours. It makes sense; monitoring wakelocks and battery drain while you're using your phone is like driving your car 100 mph on the highway and you wonder why you use more gas. :rolleyes:

As for the log, the only obvious thing I see is a null pointer fatal errors regarding wallpaper service. I suspect (and this is a stab in the dark kinda thing) this may be due to your using a wallpaper that resides on external SD maybe and the phone has intermittent issues reading it?

02-02 23:58:14.712 409 711 E AndroidRuntime: !@*** FATAL EXCEPTION IN SYSTEM PROCESS: PackageMonitor
02-02 23:58:14.712 409 711 E AndroidRuntime: java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.PACKAGE_CHANGED dat=package:com.android.systemui flg=0x8000010 (has extras) } in com.android.server.WallpaperManagerService$MyPackageMonitor@428ce398
02-02 23:58:14.712 409 711 E AndroidRuntime:	at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java)
02-02 23:58:14.712 409 711 E AndroidRuntime:	at android.os.Handler.handleCallback(Handler.java)
02-02 23:58:14.712 409 711 E AndroidRuntime:	at android.os.Handler.dispatchMessage(Handler.java)
02-02 23:58:14.712 409 711 E AndroidRuntime:	at android.os.Looper.loop(Looper.java)
02-02 23:58:14.712 409 711 E AndroidRuntime:	at android.os.HandlerThread.run(HandlerThread.java)
02-02 23:58:14.712 409 711 E AndroidRuntime: Caused by: java.lang.NullPointerException
02-02 23:58:14.712 409 711 E AndroidRuntime:	at com.android.server.WallpaperManagerService.bindWallpaperComponentLocked(WallpaperManagerService.java)
02-02 23:58:14.712 409 711 E AndroidRuntime:	at com.android.server.WallpaperManagerService.clearWallpaperLocked(WallpaperManagerService.java)
02-02 23:58:14.712 409 711 E AndroidRuntime:	at com.android.server.WallpaperManagerService$MyPackageMonitor.doPackagesChangedLocked(WallpaperManagerService.java)
02-02 23:58:14.712 409 711 E AndroidRuntime:	at com.android.server.WallpaperManagerService$MyPackageMonitor.onPackageModified(WallpaperManagerService.java)
02-02 23:58:14.712 409 711 E AndroidRuntime:	at com.android.internal.content.PackageMonitor.onReceive(PackageMonitor.java)
02-02 23:58:14.712 409 711 E AndroidRuntime:	... 5 more

Edit: For the sake of it, switch back to a stock internal wallpaper for homescreen and lockscreen for a while to see if the reboot issue goes away. A null pointer exception error is almost always related to a missing resource. Not always an actual file but in your case, maybe it can't find your wallpaper file.