[mswlogo]

Ok here is the scoop guys.

For Grins I tried this poll interval change with iGuidance (via GPSGate).

No change what so ever.

Then I changed iGuidance to NOT use GPSGate (bad idea by the way) and use Windows Mobile Virtual GPS COM Port (i.e. that port you set in "External GPS").

Then iGuidance went nuts and I could only see the clock on the GPS Page to check out update rate and it's resolution was 1 second. But it was "updating" way faster than 2 seconds like it normally does. Just because it updates it does not mean it has new data.

So for folks that are seeing a difference by changing this, it means you have your GPS Setup wrong and you WILL see lag becuase the Windows Mobile Virtual GPS COM port (usually COM4 by default) has been broken for years and still is (it lags like crazy). Boosting the pollinterval may make a bad setup less worse.

What you are boosting is how often the WM Virtual GPS COM port driver calls the Windows Mobile GPS API.

The better solution is to use the Windows Mobile GPS API directly and get the broken Windows Mobile GPS Virtual COM port out of the loop.

You do this by following what I said in the "How to setup your GPS thread" see my signature for how to do this.

If you have your heart set on playing with this pollinterval then use the COM port you have set in "External GPS" (usually COM4 by default on these phones but that might not be the same on all ROMs). And if you want to try a sain PollInterval I would try 500ms. That way you are assured of not missing a change that happens on 1 sec intervals and not wasting too much CPU and Battery for stuff that CAN'T change 10 times a second.