GPS-Sport ForenRun.GPS HardwareSamsung Galaxy 2
Bitte einloggen, um neue Kommentare zu erstellen Foren durchsuchen
Erste Seite<Seite1von1>Letzte Seite
wak 22.07.2011 19:26:25 UTC geändert am 22.07.2011 19:29:44 UTC

gps problem solved!!!

Build 2.3.9j obviously solves the high DOP values with android 2.3.4. Thx Tom for your efforts!!
Gave it a try today while driving the car: http://www.gps-sport.net/trainings/driving_635344.
DOP was ok all the time. High DOP only while driving through tunnels.
kalle74 22.07.2011 16:36:50 UTC geändert am 22.07.2011 16:37:08 UTC

Probably solved

In my case, it's obviously the track, not a fault of RunGPS. Yesterday I did a different track and everything worked pretty fine (although it was cloudy and rainy http://www.gps-sport.net/trainings/running_634835). I also notice that the mentioned DOP-freakouts occur at pretty much exactly the same part of the track. I am a bit puzzled about what could cause this, but consider this issue solved for me.

Sorry for having dragged this thread into offtopic...
kalle74 20.07.2011 23:14:49 UTC geändert am 20.07.2011 23:39:51 UTC

Likewise problems

RunGPS worked *quite* okay for me so far, at least good enough. However, since about a week the results are quite a bit disappointing...

This is a typical result when it works well: http://www.gps-sport.net/trainings/running_629373
Same track a day later, losing fix in the middle of the track (sky was clear) and regaining it after about 1 kilometer: http://www.gps-sport.net/trainings/running_630245 (beside that, the rest of the track looks like I drank a bottle of vodka before starting [which I did not!]).
Two days later I couldn't even use RunGPS because it couldn't find a fix after 45 minutes (weather was fair as well).
And today it had the same behaviour as shown in the second example: http://www.gps-sport.net/trainings/running_633966

Being a beginner, that is *really* frustrating.

I use a HTC TRIN 100 with Win Mobile (which suggests that it might not be a problem of the used hardware / system). I will set the max. accepted DOP from 15 to 20 and check again in two days.

wak 20.07.2011 16:42:11 UTC

today training again not plausible.

@Harald: lucky you
@Hard-Rider: what is the ke7 rom and where did you get it?
downloaded gps status from the market. showed a dop of 2-3 while run-gps at the same time had 17
HaraldS 19.07.2011 23:20:10 UTC



I have no problem with my GS2. Works better than Galaxy S
:-)
Hard_Rider 19.07.2011 16:53:50 UTC



Yes, your DOP values seem high. Here are you can see mine http://www.gps-sport.net/trainingReports/Hard_Rider/trainings201107/110719_075017_058217/training.html. They are much lower and average around 12 which is still a little high IMO but I don't seem to have had any drop outs or weird values.

Galaxy S2 with stock KE7 rom and latest trial version of RunGPS.
wak 19.07.2011 15:13:58 UTC

high dop with SG2

I have the same issue, which drives me nuts, because all the training records are considered not to be plausible
e.g. : http://www.gps-sport.net/trainingReports/wak/trainings201107/110719_141023_077423/training.html

:-((, rather enoying.hope we will get a fix soon...
Hard_Rider 19.07.2011 13:14:57 UTC



Has this now been fixed? I just tried the latest trial version on my GS2 and the distance and speed measured seemed to match that of my cycle computer but I don't know if that was a fluke or not. I'm going to try a few more rides and see how it performs.

My max accepted DOP value is set to 20.

What I didn't seem to get working was using an external bluetooth GPS receiver. The receiver is paired ok but Run.GPS just wasn't seeing it and it always said no-fix when the receiver was clearly showing a fix. I'll need to do a little more checking on that. The receiver is a Holux GPSlim 236.
admin 19.05.2011 10:29:49 UTC



We have the problem of excessive DOP values on a number of new devices.

Please try setting the "max accepted DOP" value in Configuration >> GPS Settings to a very high value.

gjoess 18.05.2011 21:30:21 UTC

GPS lock issue

Hello there

Just got my brand spanking Galaxy 2. When I start it it asks me to use Pico or Samsung TTL. I tried both with no difference.
The issue is that the GPS never give me better than a "weak" status... most of the time it is "no fix".
This is even when I have 10 satelittes green !. When I look at the map track it looks pretty accurate but the distance/ speed is way off. It recorded 8 km on a 5 km run which is a disaster for me.

Any thoughts, suggestions ? I also check the optional "Use sensor aiding" on/ off with no difference.

Erste Seite<Seite1von1>Letzte Seite
© 2024 | Impressum | Allgemeine Geschäftsbedingungen | Nutzungsbedigungen | Datenschutzerklärung | Widerruf und Rücksendung | Batterieentsorgung