Closed GoogleCodeExporter closed 9 years ago
Update: when I saved path data to a kml file, distance automaticaly shows up
correctly.
Original comment by blaszkow...@gmail.com
on 7 Jun 2010 at 10:15
Hi,
I have a similar issue (http://code.google.com/p/gccv2/issues/detail?id=53) but
it only happens when I set the "GPS activity" to something different than 1
sec. In your case it would be "always on; log ev. 10 sec".
How do you have your GPS activity set-up?
I also use km/kmh units but I didn't check if that is essential for reproducing
the problem. I must check.
Original comment by jakub.sa...@gmail.com
on 8 Jun 2010 at 1:52
So for me the units setting is irrelevant. The bug is the same in eigher case.
Original comment by jakub.sa...@gmail.com
on 8 Jun 2010 at 9:43
It's strange, I changed My "GPS activity" to "run every 20sec" and now distance
is OK.
My previous settings was "always on, log ev. 5 sec" (when I got wrong distance
calculations)
Original comment by blaszkow...@gmail.com
on 8 Jun 2010 at 1:00
OK, I tested it again, wrong distance calculation is when I set "always on;
log ev. xx sec" (xx value doesn't matter). When I switch to "run every xx sec"
distance calculation is OK.
Original comment by blaszkow...@gmail.com
on 8 Jun 2010 at 8:15
[deleted comment]
Well, in my case (MDA Compact V - HTC Touch Diamond 2, with internal GPS, WM
6.1) the Distance is incorrect in both cases
- "always on; log ev. X sec" (wrong value is always X times smaller than the
expected)
- "run every X sec" wrong value is Y times smaller (tested results: for X=60 is
Y=48.5, for X=20 is Y=10.7, for X=5 is Y=9.3)
After re-loading the track (after finished tracking) the distance (and also
avg. speed) is recalculated correctly.
You didn't mention your device type and OS version. What is it?
In case you encounter the error, does the re-loading of track help as in my
case?
Is the distance always 10 times smaller no matter what the xx in "always on;
log ev. xx sec" is?
And is here anybody who has none of these problems? If so, state the gcc
version, device type, OS version
Original comment by jakub.sa...@gmail.com
on 11 Jun 2010 at 11:06
I run gcc on Samsung Omnia (i900) with WM 6.1 with internal GPS. Re-loading of
track help as in your case, but I didn't checked if wrong calculations depends
on X sec value... I'll check it later.
Original comment by blaszkow...@gmail.com
on 11 Jun 2010 at 11:30
Sorry guys for this stupid bug. Please use the version 4.3beta2 posted in the
forum
http://forum.xda-developers.com/showthread.php?t=424423&page=121
or as workaround set gps "always on; log ev. 1sec"
Klaus
Original comment by kmb...@gmx.de
on 12 Jun 2010 at 6:41
Thanks for fix, but yesterday I found another problem - I don't know if it's
related. I often use gogole maps with gcc (one of them is in the background).
When gcc is in background it's stops calculating distance at all. When I switch
gcc to the foreground it displays the same distance as before the previous
foreground work. It's looks like in the background work points are saved
correctly (graphic path is OK) but it stops calculating the distance. When I
click "save path to klm file" distance is magically coreccted.
Original comment by blaszkow...@gmail.com
on 13 Jun 2010 at 10:43
Original issue reported on code.google.com by
blaszkow...@gmail.com
on 7 Jun 2010 at 7:25