[Galaxy S II General] qkster:
OP - are you still around to comment? Thanks

Original post in Infuse Forum. Screen captures also on original post.

I spent a good portion of yesterday reading up on this thread. It has shed some light on the issue.

Here are some tools that may be helpful:

Terminal Emulator (will be TE)

To capture dmesg and /proc/wakelocks in TE:

su

dmesg > /sdcard/dmesg.txt

cat /proc/wakelocks > /sdcard/wakelocks.txt

reference:

http://xdaforums.com/showpost.php?p=18495038&postcount=232

Find these *.txt in your /sdcard/

After reading up on this thread, it appears to suggest that rogue Apps is the key to the high Android OS as battery consumption.

By rogue apps, it is not necessarily some games or apps from market. It may also mean system apps. Some examples were: Skype, Talk (google), Maps, Email (stock), Gmail, Google+, Latitude, Calendar Storage. Any such apps that take in a data and require data sync will potentially do this.

In our Settings/account and Sync, background data may play a role in stopping apps from pulling data. Some Google Apps will obey this toggle and stop pulling data when it is off. MAPS will not. The sync will apply only to gmail, contacts, calendar and pics. There are other Email (Hotmail was named), K9, Trillion etc or other apps like FB Twitter that may not obey the background data toggle.

Allowing Google location services will potentially cause a data request loop that can suck your battery dry in the form of Android OS as well.

However, I feel that there is a problem here. Whether it is due to a rogue apps or system settings or power control, the constant request of data or error loops prevent the phone from deep sleep and also causes the CPU to race during these events. There should be better power management either by Google or Samsung or ATT - by providing proper firmware or by apps that will allow users to manually sync data or stop data requests or recognize that the drain has started and stop the process.

I have not used Juice Defender or other battery saving apps but it has been suggested the apps that will allow you to control scheduling, when and where the data sync takes place will also limit the "bug" from appearing.

It also has been suggested that under the wifi advance menu, clicking on the "Never when plugged in" has also reduced this from happening.

Where is all of this leading? I have noted that my drain usually starts from coming off the wall charger and running at 100%. Wifi and/or cell data is/are on and starts somewhere from during a transition point. Home to work, work to home or places in between.

A couple of days ago, I started with 100% battery. I have Maps, Email, Gmail, Google Play Store and Gtalk with video from HERE. I usually don't use Email and Maps but I re-installed these to see if I can get "capture" the culprit. (On previous Andoid OS drain, I did not have Maps installed.)

I left Wifi and Cell Data (data) off. I had background and sync off. I turned on wifi or data only when I need it for quick Gmail sync, Gtalk, or XDA. The battery phone went for 2 days and 16hr with 40% left.

As I also have picked up from reading other threads that having Market (Play Store) update, auto update or notification can also be a drain - so these have been turned off as well.

I finished reading the thread last night. I charged the phone to 100%. Then I turned on Wifi. Left background and sync off. I went to a local car dealer ship for free coffee and donuts. Connected to their free wifi.

And, BAMM! There it is!

Screen shots, dmesg and wakelocks included.

After 2hrs, MAPS started the process of data pull. The phone stayed awake when the screen was off. As soon as I noted it, and went along with looking it up, it continued the drain. I had also went from the car dealership to home. The same wifi source that did not cause any issue before, the same drain continued.

I know the fix. I uninstalled Maps. Booted into cwm. wipe cache and dalvik. Rebooted. After an hour, the phone with wifi on, behaved normally again. Battery usage graph leveled off.

In this scenario, it was Maps. In the past, when Maps was not installed, Android OS was the top hog. I'm thinking that it could might as well be Gtalk Video, Gmail, Calendar Storage and Email or as other have noted, FB, Skype etc. In my case, I suspect my Gtalk Video. I have seen the drain with Email not installed as well.

I'm thinking: One of these Effing Apps from Google is the trigger, F'n Wifi driver is the bullet, #$%^ Samsung/ATT is the gun and my poor battery is the victim. :D

I'm going to continue with a few other scenario testings to see if any other apps takes the bait.

Interpretation of wakelocks and dmesg are welcome.

Edit: Firmware: dman's uclb3 2.3.6 deodexed and rooted. Modem: UCLB3. Kernel: Entropy's DD device: SGH-i997 Infuse 4g