TrekBuddy

[velman]

I don't know whether this is a problem i my phone or in tb, but when I'm logging (approx) Dt=8 and Ds=20 the application freezes and makes the phone very slow.

It often occurs when i'm in a enviroment where there could be problems with the gps signals, eg in buildings. It also adds trackpoints with coordinates 0.0.

As I said, I don't know if this is a problem with my phone or TB. I just want to know how to make the program as stable as possible and still have as many tracking points as possible.

Can there be problems with the program if I get a text message or a phone call? I use a SE W810i.

- - - - -

<trkpt lat="57.699803333" lon="11.952585000">
<ele>20.7</ele>
<time>2007-10-18T16:27:16Z</time>
<fix>3d</fix>
<sat>5</sat>
<extensions>
<rmc:course>22.9</rmc:course>
<rmc:speed>0.3</rmc:speed>
</extensions>
</trkpt>
<trkpt lat="0.0" lon="0.0">
<ele>20.7</ele>
<time>2007-10-18T16:27:25Z</time>
<fix>6</fix>
<sat>3</sat>
<extensions>
<rmc:course>5.8</rmc:course>
<rmc:speed>0.4</rmc:speed>
</extensions>
</trkpt>
<trkpt lat="57.699835000" lon="11.952683333">
<ele>20.6</ele>
<time>2007-10-18T16:27:34Z</time>
<fix>3d</fix>
<sat>3</sat>
<extensions>
<rmc:course>73.9</rmc:course>
<rmc:speed>0.1</rmc:speed>
</extensions>
</trkpt>

- - - - -

/Staffan

[Ranger]

Hi Staffan,
You have coords 0,0 because your module lost fix for some points, ie. number of sats is 3 in your sample, correct fix should be 3d.

[kruch]

I'll check if dt=8 together with ds=20 does not result in too much processing.

Unless you check "log only valid", you may get a pt with lat/lon 0.0 (the attributes are mandatory) because of period (8 secs) criteria on.

Interesting record! Fix quality 6 = "estimated (dead reckoning) (2.3 feature)". Have never seen that before... Well, for fix quality values that do not match GPX fix types, I just use the numeric value. I just checked GPX specification, where it is said: "To signify the fix info is unknown, leave out fixType entirely".... hmmm, not sure what to do...