[Windows Mobile Apps and Games] dingolino:
For my HD2 I have at the moment the following settings which are working for me on Duttys WWE ML V1.5 rom

GPSModDriver (System Menue)

Sleep Time 1000

ComTimeOut 100

Keep Alive 15000

Internal GPS Device (System Menue)

** ATTENTION: changing this settings needs a soft reset to be effective **

sleep time 500

poll time 500

Input Buffer 1024

Output Buffer 1024

But maybe I will go back to the default settings:

sleep time 1000

poll time 1000

will see how further testing is working

I am using the Walking profile with the default settings from Mach2003 with 1 exeption:

"Speed Fix" is On and coresponding "Prefer GPS" is ON

because this is neccessary that TomTom is working nicely.

If I am setting "Prefer GPS" Off I am getting a "jumpy" GPS signal in TomTom (going from zero to full freaquently) and strange speed values (higher and lower speed than real)

All the rest is the default setting from Mach2003

My discussion with Mach2003 about the settings for the "Internal GPS Device" in System Menue

(for me this was quite helpful to understand the settings and that not all numbers are making sense - in fact only a few - if the assumptions are ok)

dingolino:

What do you think:

Sleep time: 500

Poll rate: 600

Mach2003:

The following is all speculation, I don't actually know how HTC_GPSID.DLL uses these numbers, and different versions of the DLL could use them in different ways. These values COULD even be passed down to the GpsOne driver.

Since the raw data is going to be formed about every 1 second, poll rate would be best as a divisor of 1000. If set to 600 then the first poll at 600 would return nothing, the second poll at 1200 would return data from 1000, the third poll at 1800 would return nothing, fourth poll at 2400 would return data from 2000. Think of the case where the raw data is formed a few milliseconds late (at t+1025 or t+1100, instead of t+1000). Except that your sleep of 500 would pick up 1000 (600 + 500), 1200 + 500 would still miss, 1800 + 500 would hit 2000...

Example of t+1025, 100/50 will read it at t+1000 (100,200,300...1000+50). t+1100 would be read at 1100. If poll was 500, t+1100 would be read at 1500 (400 ms late).

If poll rate and Sleep Time are the same, then data would be returned as soon as possible. With sleep half of poll rate, then the possible waste is equal to sleep time. I can live with 50 ms of tardiness, it does not adversely affect position, and it covers off the case where the driver might use poll AFTER sleep (100+50, +100 +50, +100 +50 = 450 instead of 300).

dingolino:

From the above I learn that a poll rate which is not a divisor of 1000 is not good.

>With sleep half of poll rate, then the possible waste is equal to sleep time. I can live with 50 ms of tardiness,

From this info I am assuming that a sleep time of 100 and a poll time of 200 will result in a waste of 100ms and that would be too much.

Therefore all numbers with a higher poll time than 100 should have the same sleep time.

Option 1 for Internal GPS Device (= the optimum for Mach2003 on his Diamond)

sleep time 50

poll time 100

Option 2 for Internal GPS Device

sleep time 100

poll time 100

Option 3 for Internal GPS Device

sleep time 200

poll time 200

1000/200 = 5 = ok

Option 4 for Internal GPS Device (= what I am using now on my HD2)

sleep time 500

poll time 500

Option 5 for Internal GPS Device (Standard MS/HTC setting)

sleep time 1000

poll time 1000

Best regards

&

Thank you very much Mach2003 for the patient to

go through all the log files, settings and for all the

detailed explanations!

dingolino