TrekBuddy

[petr.kvapil]

Hello Kruch,
1) please, what is MOB! ?
From the last version it is almost impossible to use it because when navigating to the waypoint then many times it is changed to the waypoint "MOB!" in form of new file and I have to then everytime open the right waypoint file again.
2) It crashes many times when I want to open a new waypoint so I have to do it in the way that I open the same file again (it was also the problem in older versions).
I think about "downgrading" to some older version.
Thank you for the answer and for the great program!!!
Petr

PS. I use Motorola Defy + Android 2.2.2. and Motorola Motoluxe XT615 + Android 2.3.7.

[shen]

this is the new man over board function ... But I'm also having problems with that by accidentally setting mob WPTs - I wish I could switch this feature off

Stefan

[kruch]

[shen]

This option would help a lot

For some reason I double hit fire now and then, possibly to put the screen on and then center the map to actual position ...

Gruß Stefan

[kruch]

Maybe it should be triggered by triple click...

[shen]

That would be ok for me, but perhaps not for the guys who asked for this feature.
But isn't it so that waiting for a 2nd or even 3rd click slows down the reaction time on a single click? So perhaps an other key would be the better solution as fire is often used. So a double or even long key 3 could also do the trick.

Gruß
Stefan

[kruch]

It should not, there is no wait for second click - single click synchronizes map&screen position with current location immediately.

[vincentiuzz]

thx kruch...
thats great for my samsung B2710..


i think it's more awesome if i can see how much locked sattellite,,

[mbailey]

I upgraded from 1.1.3 to 1.2.0 on my old Sony Ericsson K610i before heading off on the bike today and unfortunately wish I hadn't.

Trekbuddy was constantly coming up with Java error and the program crashing every 15 to 30 minutes. Some times it will continue to track, but other times crashed all together.

I wasn't sure if it was causing by the route I was trying to follow, so I ran it with out any route loaded and just the map loaded, but it still crashed.

I wasn't sure if it was a new map I had installed yesterday, so enabled an old map which I had used before, but again still crashing.

Now to put the older version back on the phone.

[mbailey]

Had a nightmare trying to get 1.1.3 back onto the phone as it kept saying "operation failed" when I tried to install the jad file. The jar file would install ok, but that doesn't work on my phone as the security doesn't get set up correctly unless you install via the jad file.

I ended up doing a master reset on the phone, formatting the memory card, but still couldn't get it 1.1.3 to install.

I managed to install 1.1.6 and thought I would test that.

Unfortunately still getting the error come up with 1.1.6:

"[7] : InvalidMapException [null]: Failed to load tile: java.long.OutofMemory"

[kruch]

@mbailey the other Java errors ("constantly coming up with Java error") were also OutOfMemory errors?

[mbailey]

[kruch]

Thanks for the version tip, I'll check 1.1.3-1.1.4 diffs.

[mbailey]

[JNT]

I have been out (on the ice), testing the MOB function a little. Double-tapping works great to create the MOB waypoint. Without stopping and starting the tracking, if I double-tap a second or third time, the MOB point is created at the new position each time. This is good, but looking at the list (of MOB! points) that was created, all the points in the list had the same coordinates (and name)...

I would like to request that if more than one MOB point is created, that they are all stored as a numbered list (MOB001, MOB002, MOB003... tec.) with their separate coordinates. (Otherwise the real one might be over-written by mistake.)