we had this case already with one customer but it seemed that he had done something wrong and never said anything about the issue after the first discussion ...
So here's what we'll do: I'll provide you with a special version that bypasses the dilution parameter and we'll see what happens. I'll post the link tomorrow.
Yes -- The GPS does get coordinates and it appears to be updating the coordinates properly when I'm moving around. It just will not lock and Dilution stays at 50.0. I am using 2.0.6. build 701 which I downloaded three days ago.
I had also found and tried the GPS Activated code from modaco.com. Once the code was installed, I was able to use the GPS in both the Windows intermediate driver and COM4 settings in Live Search. However, Run.GPS was not able to use any of the COM ports and can only use the Windows Managed setting.
It seems the phone's integrated GPS and Run.GPS has a difference in opinion in the Dilution readings. Therefore preventing Run.GPS from allowing the lock and functioning. Is there a way to bypass Dilution as part of GPS locking in Run.GPS?
Well Run.GPS uses the Intermediate Driver too when in Windows Managed mode. Does your device display the GPS coordinates while the Dilution is 50.0? Did you try the latest Run.GPS release (2.0.6)?
I had Run.GPS working on my Samsung BlackJack I i-607 Smartphone and I liked it so much I went and upgraded to the new Samsung Blackjack II i-617 with theinternal GPS chip. I was able to get TeleNav and Live Search to work properly with the internal GPS but I'm not successful with Run.GPS.
I have the GPS configuration to connect via Windows Managed. The applicaiton is able to find 11-12 satellites but is always no fix. It also shows a Dilution of 50.0 the entire time -- No matter where I go.
At the same time, Live and TeleNav connects without issues. In Live, it is connected to the GPS via the GPS Intermediate Driver.
Tom - Any suggestions? Would love to get this back up and running on my new phone!