"mailservice" and "powermanagerservice" causing huge battery drain an no deep sleep on Xperia Z1

[jrinco11]

Hi there, I recently purchased an Xperia Z1 and am having awful problems with battery life which appear to point to two possible reasons, either the "MailService" or "PowerManagerService" which are causing the phone to be unable to go into deep sleep.  

The phone was unplugged this morning at 100% battery, and over the span of ~4 hours, the battery is already down to 60%.  According to BetterBatteryStats, "PowerManagerService" has been a Kernel Wakelock for 2hr 2m 20s (77.5%) and "MAIL_SERVICE" has been a Partial Wakelock for 2hr 4m 37s (78.7%).    I do have an exchange account setup and initially had it setup to PUSH email, but I've since had it try manually checking every 15 minutes instead, to try to help the battery, but that hasn't changed a thing.  

When I go to the built in android battery usage screen, "Echange Services" is the most at 39%, followed by Screen at 19% and Email at 13%.   

Clearly, to me, it looks like there is a problem with the Exchange email account causing the phone to kill the battery.  Furthermore, since the phone was unplugged, it has only been in Deep Sleep for 14 minutes (9%).  

Why is exchange cuasing this to happen?  I have used the same exchange account on my Galaxy Note 2, Nexus 4, Galaxy S2 and have had no such battery drain issue. 

Any suggestions?? 

update:  I just noticed that since I changed the exchange sync options to be every 15 minutes (instead of PUSH), my exchange account hasn't been updated in over 2 hours, yet the "MAILSERVICE" is still cuasing the partial wakelocks.   What's going on? 

[Rickard]

Is the server you have a Microsoft server or some other type of server? We have another thread where some users have reported that the phones standard client doesn't work well with non Microsoft servers.

If it is a Microsoft server, would it be possible for you to test if the same thing happens with another account on the server?

[jrinco11]

I'm not sure how to tell if it is indeed a microsoft server or not?  I just assumed that since it is a Microsoft Exchange setup that it is indeed a microsoft account?  Also, I'm unfortunately unable to try with another account as this is just through my work and I don't have access to any coworkers accounts (not allowed anyway). 

Any other suggestions?   (thanks for the reply thus far!)

EDIT:  I've just done a factory reset, installed no apps except better battey stats and re-added my exchange account.  The "MAIL SERVICE" is still cuasing a constant partial kernel wake lock.  

[Rickard]

The new software (14.1.G.2.257) that's currently rolling out contains improvements for Exchange ActiveSync. Could you see if the problem remains after updating to this version?

[jrinco11]

as soon as the update becomes available for my phone, I will definitely give it a go (any ETA on a UK OTA update?)  I assume I could alternatively force an update from the PC software? 

[SergioPL1]

---

@jrinco11 wrote:

I'm not sure how to tell if it is indeed a microsoft server or not?  I just assumed that since it is a Microsoft Exchange setup that it is indeed a microsoft account?  Also, I'm unfortunately unable to try with another account as this is just through my work and I don't have access to any coworkers accounts (not allowed anyway). 

Any other suggestions?   (thanks for the reply thus far!)

EDIT:  I've just done a factory reset, installed no apps except better battey stats and re-added my exchange account.  The "MAIL SERVICE" is still cuasing a constant partial kernel wake lock.  

---

Check if you have some appointments (like birthdays) in your calendar that have infinite end time. I had similar problem with Xperia P and 4.0.4 Android. It drained the battery within 3 - 4 hours after full charge.

After doing some debugging of e-mail I found that the calendar service is trying to update, then finds one appointment with inifinite end time (set by Nokia E51 or older few years ago) and then it crashes. After restart of itself it does update again and crashen in the infinite loop. 

You can find "Enable debug" procedure below:

http://code.google.com/p/android/issues/detail?id=35208