When I enabled App Permissions under security, Outlook started to prompt me in an infinite loop to allow it to access contacts and whenever I gave the permission it asked again, so it looks, that if contacts sync is enabled Outlook keeps spamming the contact
list with sync. I disabled the contact sync on my outlook account and it seems that cpu usage is now lower, and also some guy from another forum said that this fixed his battery draining issue. I hope this will fix it, otherwise I'll stop using it as well.
Shame on you Microsoft -.-
Stopped the contact sync in Outlook and problem resolved. Thanks for the solution.
But it says that it will delete all contacts from the phone - Did it?
So I was having the same battery drain issues as everyone else and turning Contact Sync "OFF" immediately solved the problem. I can do that as I'm using the desktop app Contacts Sync Pro to sync all my contacts from my Windows desktop Outlook client to my
Google Contacts which then makes them available on my Android phones.
Having Sync Contacts on in the Outlook Android client was just adding duplicate versions of those contacts to my phone's contact database, so I didn't need it anyway. Turning it off did remove those contact records that Outlook for Android added but it
didn't remove any of my contacts that were synced via Contacts Sync Pro (or any other contacts I had added to my Google account Contacts).
Besides the battery drain this was causing major performance issues on my Blackberry KeyONE which I use for my work email and use the Outlook for Android app on. Once I turned off the Contact Sync option the phone's responsiveness returned. I had tried deleting
the Outlook app and reinstalling it but after about 10 minutes the performance and battery drain issues returned.
I think the Outlook Contact Sync process is doing something screwy to Google Play Services, it's battery usage was extreme in tandem with Outlook's, and was forcing Google Play Services to be running 100% CPU time (meaning when you look at it's CPU Total
time in app usage details, it's CPU time was exactly equal to the amount of time the phone had been on battery/not charging - that's crazy when you consider the Android System app only has used a quarter of that CPU time).