Exchange Services chewing up Battery - Seriously?

[pnd4pnd]

Hi all,

Just got my S3 yesterday and pretty much in shock this bug is out there. I've searched high and low and can't find a solution to this. How can samsung put out a phone where Exchange email doesn't work (well works but kills the battery) ? I otherwise love the phone, but this is a dealbreaker for me. Here is more detail: Issue 31246 - android - 'com.android.email' Alarm count high connecting to Exchange Server (shows as 'AndroidOS' in Battery Stats) - Android - An Open Handset Alliance Project - Google Project Hosting

Does CM10 fix this issue? Any pointers to fixes or workarounds would be greatly appreciated.

Eric

 

[Jerry Hildenbrand]

As mentioned in the issue tracker, this bug has been fixed (March 2012), but Samsung is not using the patch. You'll need to contact them for more information about an official fix here:
https://contactus.samsung.com/customer/contactus/formmail/mail/MailQuestionProduct.jsp?SITE_ID=31

It looks like it's fixed in any AOSP based firmware, so CM10 should take care of it.

 

[meyerweb#CB]

I sometimes get as many as 150 exchange emails in a day, and have no battery issues. On a "light day," maybe 50 emails, I can easily go 12 - 15 hours on a charge. On a heavy day, I'll probably give the phone 30-60 minutes on the charger sometime during the day. Those emails are in addition to other, normal use of the phone, including gmail, some web browsing, a few calls, and maybe some Words with Friends.

I've got dozens of calendar events each week, with alarms, too, and about 400 contacts stored in exchange (in addition to the corporate GAL)

Perhaps this is not an issue with JB?

 

[Jerry Hildenbrand]

It's a legit bug the OP is seeing, but it also depends on the configuration of the Exchange server.

The good news is that Google has fixed it, CM has fixed it, so Samsung should get it fixed in 2015 or so

 

[pnd4pnd]

Are you sure CM fixed it? I'm reading its fixed in CM9 but not 10.

 

[Jerry Hildenbrand]

CM9 was the current version when the issue was reported. CM10 and 10.1 are built off of the patches for 9 and will include the fix.