Android Exchange Service Battery Drain and High CPU Usage: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 22: | Line 22: | ||
* [http://code.google.com/p/android/issues/detail?id=39728 Issue 39728 in android: Android 4.2 drains Galaxy Nexus battery] | * [http://code.google.com/p/android/issues/detail?id=39728 Issue 39728 in android: Android 4.2 drains Galaxy Nexus battery] | ||
android "Connection Timeout" exchange battery drain | android "Connection Timeout" exchange battery drain<br> | ||
"tcp timeout" "activesync" | |||
<google>ENGELSK</google> | <google>ENGELSK</google> |
Revision as of 16:53, 23 December 2012
- Email app battery drain - FIXED
- Email.apk - Gingerbread src code w/o Exchange security
- HACK Samsung Email App - Exchange Wakelock Bug Fix
The average of the most recent heartbeat intervals [470] for request [Ping] used by clients is less than or equal to [540]. Make sure that your firewall configuration is set to work correctly with Exchange ActiveSync and direct push technology. Specifically, make sure that your firewall is configured so that requests to Exchange ActiveSync do not expire before they have the opportunity to be processed.
For more information about how to configure firewall settings when using Exchange ActiveSync, see Microsoft Knowledge Base article 905013, "Enterprise Firewall Configuration for Exchange ActiveSync Direct Push Technology"
- Issue 37437 in android: Exchange Service High CPU Usage, Battery Drain since Jelly Bean 4.1.1 Upgrade
- Issue 39728 in android: Android 4.2 drains Galaxy Nexus battery
android "Connection Timeout" exchange battery drain
"tcp timeout" "activesync"
<google>ENGELSK</google>