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 9: Line 9:
* [http://nicktangblog.wordpress.com/2010/05/19/enterprise-firewall-configuration-for-exchange-activesync-direct-push-technology/ Enterprise firewall configuration for Exchange ActiveSync Direct Push Technology]
* [http://nicktangblog.wordpress.com/2010/05/19/enterprise-firewall-configuration-for-exchange-activesync-direct-push-technology/ Enterprise firewall configuration for Exchange ActiveSync Direct Push Technology]


* [http://www.dd-wrt.com/wiki/index.php/Router_Slowdown DD-WRT Router Slowdown
* [http://www.dd-wrt.com/wiki/index.php/Router_Slowdown DD-WRT Router Slowdown]


The average of the most recent heartbeat intervals [470] for request [Ping] used by clients is less than or equal to [540].
The average of the most recent heartbeat intervals [470] for request [Ping] used by clients is less than or equal to [540].

Revision as of 16:43, 23 December 2012


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"


android "Connection Timeout" exchange battery drain

<google>ENGELSK</google>

id=siteTree