ICS Battery Issue

[ThrillJunkieUK]

Hello,

Last week I upgraded my Samsung Galaxy S2 to ICS and ever since the upgrade I've been having major battery issues. My battery used to last at least 1 day before but now I'm lucky to get half a day out of it!
When I've looked into what is causing this issue I have found the "Android OS" process is consuming between 22% - 75% of my battery constantly!

To try to rectify this issue I have factory reset my phone and for a few hours this did the trick but then the same "Android OS" process shot up once again.

I have recalibrated by battery (Ran the device down, Turn Off, Recharge to 100%, remove battery for 2mins, turned back on) but still no joy.

Can anybody else tell me why this process is running so high and what I can do to get my phone back to normal?

I am using the original (Orange) ROM with the standard stock battery. I'm a Moderate/High usage user.

Any help appreciated

Thanks
ThrillJunkieUK

[greenman]

Join the queue with this problem.
You're going to have to try and manage the battery use, or revert back to Gingerbread.
This post may help: http://samsunggalaxysforums.com/show...-Apps-and-Tips

[chatter]

Could it be that anybody suffering issues had previously downloaded apps and used them on GB.
It's only and idea and it looks like were grasping at straws with these issues so any ideas could be relevant.
I get at least 24 hours and as a new owner I regard myself as quite a heavy user,Ebay,paypal,games,etc.
It might be good to hear from other "new" users;I personally downloaded ICS before I added any Apps.
Could someone completely"wipe" their phone then upgrade to ICS,then add their apps?

[RichH]

Could someone completely"wipe" their phone then upgrade to ICS,then add their apps?

This is the recommended route for major firmware upgrades. Happy with my battery life on ICS. You need to understand what is draining the battery in order to remedy the issue. "Better Battery Stats" off play for example....

[Tufftoad]

The Android OS percentage being above 10% is a firmware bug and was also present in Gingerbread. The only solution I have heard of would be to flash new firmware.

It's highly likely that you could flash the same firmware and the problem will dissappear but it is defnitely firmware related.