Android Exchange Service Battery Drain and High CPU Usage: Difference between revisions

From Yggenyk
Jump to navigation Jump to search
No edit summary
No edit summary
Line 3: Line 3:
[[Category:Android]]
[[Category:Android]]
<google>ENGELSK</google>
<google>ENGELSK</google>
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"
* [ActiveSync warnings on exchange server caused by Droid users only http://androidforums.com/droid-support-troubleshooting/23248-activesync-warnings-exchange-server-caused-droid-users-only.html]
* [Issue 37437 in android: Exchange Service High CPU Usage, Battery Drain since Jelly Bean 4.1.1 Upgrade http://code.google.com/p/android/issues/detail?id=37437]
* [Issue 37437 in android: Exchange Service High CPU Usage, Battery Drain since Jelly Bean 4.1.1 Upgrade http://code.google.com/p/android/issues/detail?id=37437]
* [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 http://code.google.com/p/android/issues/detail?id=39728]
<google>ENGELSK</google>
<google>ENGELSK</google>

Revision as of 09:39, 23 December 2012

<google>ENGELSK</google>

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"


<google>ENGELSK</google>

id=siteTree