I think I found the key for Direct Push heartbeat increment duration
I searched and got no matches for this so i will post it in case nobody has found it yet.
I am bummed about decreased battery time since the upgrade and i know it has to due with the push mail. I use autd but it still enables push in comm manager and it is killing my battery.
There are two keys.. One is heartbeat increment (300) and the other is initial increment (480). I am hoping that when I make these numbers larger it will increase the duration between heartbeats and increase battery life. Since I use autd the duration of the heartbeat can be as long as possible. I am going to change these values and continue to watch my battery usage app. I will report back on my findings.
The key is in HKCU\software\microsoft\activesync
Edit: I just saw another key called maximum heartbeat. It was set at 1680 so that is what I set both of the above intervals to. I was getting the heartbeat spike about every five or six minutes before. If logic applies this interval should be 5 to 6 times longer. I will report back in about an hour.
__________________
Always waiting for the next best thing!! And right now that's the Blackjack!
I made the same changes and so far im up to 20 min without a heart beat sync.. I changed all my times to 30 min because thats what I already had it set to just no push.
Are you using exchange activesync or true sp2 push mail?
i am using exchange activesync and have not yet noticed a change in the duration of my heartbeats. It still seems like they happen every five or six minutes. I dont understand why it still tries to send a heartbeat when it is using sms trigger, makes no sense.
__________________
Always waiting for the next best thing!! And right now that's the Blackjack!
by slowing the 'heartbeat' arnt you eliminating the function of direct push? If the phone is only going to check for messages every 2 hours why dont you use scheduled activesync and turn off direct push completely? Then you could turn it back on when prompt email delivery was more importent than battery life.
by slowing the 'heartbeat' arnt you eliminating the function of direct push?
The heartbeat simply keeps the connection from timing out. The server still pushes a packet over the 'net from exchange to your phone. The heartbeat has no effect on the speed in which you receive mail. However, if you set the heartbeat too long the connection will timeout and the server will be unable to send your phone the notification. I'm not sure how each side knows when the connection has timed out but it somehow knows as it does auto adjust.
1. Can you tell what effect this had on battery life yet?
2. I'm assuming your firewall timeout connections are set at 30 minutes, and that by using 1680 as the hearbeat interval you are pinging once every 28 minutes.
A. Have you noticed any loss of connection between pings at all?
B. Have you noticed any delay in receiving email because of a connection drop followed by a long heartbeat interval until the connection is reestablished?
1. From the one day that I had it setup I still can't tell fully on battery usage. I only use push at night and on the weekends. Sunday alone after a full day I still had 50% battery left with no charging throughout the day. I think this is normal to my everyday usage during work hours.
2. I did not change my firewall settings at my office.
A. I did not notice any loss of connection between pings
B. I did not notice any delay in receiving email but I only used this for one full day.
Before I made this change active sync would auto sync every 5 to 8 min and now it sync's every hour and a half to 2 hours. I'm sure the phone still sends a small heart beat to the Exchange server every 30 min? I'm unaware of how it works really but so far I like it.
Quote:
Originally Posted by finster869
Mdecker-
1. Can you tell what effect this had on battery life yet?
2. I'm assuming your firewall timeout connections are set at 30 minutes, and that by using 1680 as the hearbeat interval you are pinging once every 28 minutes.
A. Have you noticed any loss of connection between pings at all?
B. Have you noticed any delay in receiving email because of a connection drop followed by a long heartbeat interval until the connection is reestablished?
I made the same changes and so far im up to 20 min without a heart beat sync.. I changed all my times to 30 min because thats what I already had it set to just no push.
mdecker79,
Can you post the reg keys and values that you've changed to? I'm looking to increase battery life. As much as I like Push mail, the battery consumption is killing me. I'm willing to try anything that would slightly help this. TIA!
Being that I just started using DirectPush email with an Exchange server a few days ago, I found this thread encouraging as I've found DirectPush to be a buzzsaw to my battery life. I haven't fiddled with any registry settings (yet), but made these observations during some testing. All testing was done while the device was sitting stationary in my house, with a reasonably good EVDO signal:
I plugged my 6700 into AC power so I could keep the screen on and continuously monitor the EVDO connection arrows, and record how often they are turning white (active connection) while the device just sits there. I've found that when I have DirectPush enabled, the device is pinging (or getting pinged) once every minute. It's like clockwork, every 60 seconds the arrows turn white for a short while, then back to gray again. During this time I'm not actually receiving any emails, nor is any other application "using" the data connection for anything - it's simply unnecessary connections.
After turning DirectPush off, I stared at the screen for over 8 minutes and the arrows remained gray the entire time. This was no surprise, but I just wanted a control case in my test to prove that Vision itself wasn't responsible for the pings.
So I'm not surprised that the DirectPush functionality occasionally pings the device to keep the connection alive, but I was absolutely astounded to see that it does it once per minute. This is totally unnecessary, and just plain wreckless in my opinion. This is without question the reason people's batteries are draining like mad - what was MS thinking????
I plan to now try modifying the "heartbeat" registry settings that jhat3k1 discovered, but I'm a little confused at what the values really mean. The defaults seem to be 300 and 480. Are these supposed to be seconds? If so, why am I seeing it ping every 60 seconds??
I also noticed that the device would initiate an ActiveSync every 15 - 20 minutes or so. Since it really shouldn't do a sync until I receive an email, why the heck does it keep doing this??
Well, here's a disappointing update: I just changed the 4 heartbeat-related registry settings to the same increased values that mdecker79 is using, and I'm still getting data-pings every 60 seconds. So the registry changes appear to have made absolutey no difference at all.
Now I'm wondering if there's something that can be or should be adjusted on the server side to decrease all of this unnecessary pinging.
Can anyone else confirm what I'm seeing? (60 second pings) Particularly those of you who are using mail2web?? Thanks, if we can somehow figure this out then we should see a nice bump in battery life.
I never checked the 60 second data-pings but before I made this change the device would auto ActiveSynce every 5 to 8 min.. After I made my changes my device auto ActiveSynces once every hour or so.
I just sat and watched my device with push on.. It looks like my device did some type of data connection every 5 min or so.
thanks for the information.
Login
Panel
