[Windows Mobile Apps and Games] windtrader:
Big thanks!

Finally, after a long long time of waiting and searching, this program is the true treasure of true push mail utilities!!!!

Until now there was only MS Exchange as the true push email and contact sync solution for windows mobile. Lots of reading every single thread and post from the gmurray utility to here.

I had to go with a hosted Exchange service as it was the only way I could have integrated contact and true push integrated to the WinMo messaging client. Just finished trying Flexmail but I want something that stays integrated with winmo email. Email scheduler seems like the holy grail to true push for IMAP mail!

With great hope I can disconnect from the hosted service by using this utility and G Mobile Sync for keeping contacts and calendars together. The combination offer fully integrated email, calendaring, and contacts between Google and native winmo platform.

I installed the latest version last night and had zero problems. Only thing was trying to decipher the start end parms which many comments reflect similar confusion.

My two greatest critical needs are that it work reliably and very easy on the battery. It seems both are already met but I found only a couple posts that actually compared this utility vs the MS Exchange-Activesync Direct Push option. It was also GSM while my HTC 6800 is Sprint CDMA. From my reading it seems emailscheduler might even less energy than DirectPush under certain situations.

I thought I read DirectPush requires a data connection but the heartbeat function in the server manages the connection and it seems when using Exchange-DirectPush-AS the data connection EVDO icon is always on. Similarly, IMAP Idle seems to need a data connection all the time which begs the question is either more energy efficient or the difference is trivial.

Since the frequency and volume of email are major variables could someone offer an educated determination on battery use for a couple scenarios using both IMAP-Idle and DirectPush?

Scenario1: 1 small (25k) message arrives at 10 minute interval.

Scenario2: 1 small message arrives at 1 hour interval.

Again, thanks for the excellent piece of software!

*** UPDATE ***

Well I had more time to test the utility and its power usage pattern against AS-Direct Push. I noticed right away that the battery use was much higher with it running so I started measuring the device use using acbPowerMeter. It seems every minute or so there is a large power spike that corresponds to what the log records. It ramps up to about 400 ma for a brief time then drops down. I compared this with AS-DirectPush and it is the same peak usage but the main difference is the AS connection remains at nearly zero power use for long periods of time and only spikes up when an update is getting pushed down.

Depending on how often email drops into your IMAP inbox will have a dramatic impact on your battery drain. If you gets lots of emails, let's say one a minute, then you won't notice any difference in battery use. If you get email one every 15 minutes, then you will experience a big difference. AS does connect to the winmo device once in awhile even if there is nothing to push but it is quite infrequent. I am testing that now just for the record but it is maybe every 30 minutes. I think it depends on how the heartbeat is set in the Exchange server.

It is becoming clear that the only way to really have the optimal push PIM/email on winmo is Exchange/AS/Direct Push. I hate to have to say that but it really seems like reality. The push function really has to be driven from the server and the device is gonna be on the receiving end. Emailschedule gets really close but IMAP IDLE is still not as robust as AS-DirectPush.

Here is link to technet that describes the heartbeat better. The interval dynamically changes to optimize the frequency of checking.

http://technet.microsoft.com/en-us/library/cc182270.aspx

Keep up the great work and this is wonderful solution for many folks.