you only have to lock the hd2 by using the lock- symbol on the run gps -screen. It will work with
the build 1920. During a run, you can take a look at on the rungps- screen by using on/off button, after 10 seconds the hd2 will lock again automatically.
Thanks for advise. I have installed version 235 build 1920 and tried it out (1 run). The measured distance is now very accurate. Instead of 15%, there is only 1,2% difference. My GPS settings are manual: COM4, baudrate 2400.
With my HD2, when I press the on/off button it shut off and recording stops. Maybe a registry setting?
02.03.2010 13:14:06 UTCgeändert am 02.03.2010 13:14:52 UTC
brotsje
Hello Brotsje,
I`ve got bad news for you. You are not running as fast at it seems. For correct Trackrecording with the HD 2 you have to use the Build- version 1920 wich is only here available :
http://www.gps-sport.net/forums/thread/1353-0/
In my opinion, best setting for running is to lock rungps by the lock-icon, and the setting when application is locked, lock screen and buttons also. So you can take a short look on the screen by pressing on/off button.
I have installed the programm on my HTC HD2, starting from version 2.3.4 and working now with it for 5 months. The only problem I have is that I can't prevent the phone to go to hybernate when I touch the on/off button (most right button). I tried several settings but that doesn't helps (blocking buttons, leaving light on). Now I just be carefull not to touch the button during running. I made one rim on the case, around the buttonposition to prevent that.
The issue has been identified and fixed in latest delivery of RunGPS 2.3.5
More details here: http://www.gps-sport.net/forums/thread/1364-0/Run.GPS-InvalidProgramException
I have retry with this release and it worked!
Thanks!
Please guys, improve your communication!
This tool is great!
Thanks for giving the error message, but it does not provide very much information.
InvalidProgramException
à cs.ad(Int32 A_0, Int32 A_1, ...
means that the error happens when the first Run.GPS screen is loaded and layouted. It probably occurs when the GUI DLL "Run.GPS.GuiUV.dll" is loaded. But still we don't know why this could happen.