[Galaxy S II General] Capp5050:
Global Warming is REAL - and so is the AOS bug...

Sorry, I didn't bother getting into an explanation of the specifics of my situation, because I'm beyond questioning whether there is an issue. But since you asked (and to dissuade others from throwing the 'maybe you're imagining this' posts), I'll add that I've been using almost all of the battery and CPU utilities referenced within this post, and have observed similar results

- average battery life of 8-10 hours under VERY limited use (30-40 mins of phone, limited to zero web surfing, occasional reference to task lists, calendars, etc.)

- ZERO Deep Sleep, whether wi-fi is on or off

- Rapid battery drains in 'screen-off' scenarios, whether wi-fi is set to turn off when display closes or not, and even when wi-fi is forced off

- Drain in airplane mode of 3-7% per hour

- suspend and events/0 as leading processes

- Similar results whether Autosync is on or off, 4G on or off (btw, I don't use Exchange Sync, only gmail, yahoo, and facebook)

- I live in a city, where 3G data is almost always accessible, and 4G most of the time. I have replicated this issue here, as well as 3 other distinct geographies where I've recently spent time. I thus rule out 'local signal' issues and wi-fi

I consider myself astute at deductive reasoning, and though I am not as technically proficient in these technologies as the OP, his observations and related conclusions are the most sound I've heard thus far.

What seems to be creating a lot of noise is the fact that some people are happy with 10-12 hrs of battery b/c it's an improvement over previous, and other people are attempting 'tweaks', sometimes with results that appear to work, but only because:

a) they never had the bug in the first place, perhaps a different issue, and so their tweak may have directly or indirectly fixed their particular issue.

FOR EXAMPLE: I noticed a ton of processing going on w/my SD card, and like another poster who claimed to have solved the AOS problem, I removed and reformatted my card. This liminated the CPU use associated with THAT issue, and did return

some

battery life as a result; it even lowered 'Android OS' from about 80% down to closer to 50%, but did not address the core issue.
​

b) they somehow managed to defer or mask the bug, but not remove it.

FOR EXAMPLE: In my testing (with wi-fi off and screen off most of the time), I saw ZERO deep sleep (I'll post a screen shot from 30 mins of observation, but I did test it for 4 hours at one point). NOW, when I re-activated JuiceDefender Pro, I started seeing actual Deep Sleep for the first time, and - of course - battery life improvement. Again, some have claimed that JD 'fixed' their problem. Well it didn't. It just helped, because it forced the device into deep sleep when it otherwise would not have. It's like putting a bandage on a wound. Bleeding stops, but the wound is still there.​

In summary (and I really didn't want to have to write a long email): If you are NOT experiencing this issue; if you ARE getting 20-40 hours of battery life - please don't assume that the rest of us are idiots; we're not getting 10% drain per hour because our wi-fi is turned on or our local signal is weak, or we play too many games on our phones. Understand that there is a problem, and try to keep this forum focused on sharing observations, updates, and potential solutions.

One final note and question for the group (on the topic of observations):

- When I use OS Monitor and System Tuner Pro, and drill into the 'Android System' process (which is almost always chewing CPU time), the error logs show one consistent error, appearing at least every second, sometimes multiple x per second:

[ERROR] AlarmManagerService

android_server_AlarmManagerService_set to type=3, 41459.732000000

The number after 'type=' sometimes changes. (see screenshot)

The reason I'm throwing this out there, is because when using BetterBatteryStats, and filtering for 'Partial Wakelocks',

AlarmManager showed over 11,000 instances in less than 5 hours

.

So my question to the pros: Is it possible that this service (and the related errors) are keeping, or contributing to keeping the phone 'awake'?

Secondly: Why is this process/command running? I've eliminated every add-on application, soft-booted, disabled any app that I thought might trigger an alarm, and yet it is still being called by Android System. So even if this has nothing to do with the AOS bug, I'd love an opinion or two, even a suggestion on how to stop it so I can test the impact (can PM me if off topic).

Thanks,

Andy Capp