TrekBuddy

kruch · Site Admin Joined: 02 Jul 2006 Posts: 5654

Changelog

- fixed "sliding" image handling in CMS
1.32 download page

This version only fixes image handling defect introduced in previous version, where rotating image support was implemented in Android version (see this topic) and backward compatibility with existing CMS was broken.

boowoo · Joined: 12 Jun 2013 Posts: 486 Location: France

Hello,
Version 1.32 works nice on android but display version: 1.31 in "Informations" . Wink

kruch · Site Admin Joined: 02 Jul 2006 Posts: 5654

You were too fast Smile

Updated version uploaded a few minutes later.

Uffepuffe · Joined: 10 Mar 2010 Posts: 2

Hello Kruch,

I have a Meizu MX5 and the route track dont work. The maps and all other things works but wpt and route dont.

Ranger · Joined: 12 Dec 2006 Posts: 6001

What it exactly means "doesn't work" ? No list available ?
Maybe you just have a problem with FlymeOS interface ?
http://www.trekbuddy.net/forum/viewtopic.php?t=7939&start=7

Uffepuffe · Joined: 10 Mar 2010 Posts: 2

I dont know if it is Flyme OS or somthing else, but if i want to load a route it dont display on the map. I tried every possible settings and nothing helps...

guest · Joined: 08 Oct 2006 Posts: 4649

(only) With a Samsung Galaxy S3 we experience problems with the tracklog:

Some time the tracklog plotted is quite correct, then - problably because of a gps-signal loss the cross stops at a point. After getting new gps fixes trekbuddy doesn't log any new positions. It draws a straight line from the fix before the loss to the actual fix. Everything from that position of first gps-loss on is lost in the gpx and onscreen replaced by a straight line.

The setting log-only-valid didn't affect this behaviour.

Is there any known work-around (i.e. it is not a new problem), manually restarting Logging and doing editor-work with the gpx-file is quite tedious...

Ranger · Joined: 12 Dec 2006 Posts: 6001

Easy solution is to turn on nmea logs to be saved by TB. They shows detailed gps data received by app, so you can analyze then.
Do you have such logs ?
No position from receiver situations can't be repaired by app itself, just no valid data are available.
Turning receiver on/off, in place where signal conditions are wrong for one used, changes nothing mostly.

guest · Joined: 08 Oct 2006 Posts: 4649

thanks for the first feedback...

It's quite clear that during loss of gps tb can't log anything, but after a few minutes tb again shows the correct position. From then on the positions imho could/should be logged&drawn, but they aren't!

currently we don't have nmea logs, but we could activate them next time for debugging purposes.

Ranger · Joined: 12 Dec 2006 Posts: 6001

It is not true logs are the same, nmea log is recorded regular way in time, even if gps position isn't available.
So it covers case you described. On my last trip I had similar situation, position was not available for 50 secs, but log was continued as usual next.
It is why I recommend to use nmea log, you can use it in app similator mode to check case in detail many times.
Case isn't hard to reproduce, just fix receiver outside, go inside building to have position lost, go outside, check log content etc. Smile

guest · Joined: 08 Oct 2006 Posts: 4649

sorry, what is "app similator"-mode?

guest · Joined: 08 Oct 2006 Posts: 4649

as said: the problem was seen only on the galaxy s3 when losing gps, which I don't have with me now - so, sorry it will take some time to provide nmea log..

Ranger · Joined: 12 Dec 2006 Posts: 6001

Simulator mode, like name says, is special app mode allowing to use nmea logs to simulate gps providers Smile

Sorry for my typing mistake Embarassed

Just look in TB at Location, Provider settings.
Also described in wiki:
http://www.trekbuddy.net/wiki/index.php?title=Configuration#Location
Yep, problem can be model/firmware specific. Unfortunately I don't have S3 now too Smile

erdos · Joined: 30 Jul 2014 Posts: 18

thank you!

I Installed on my nokia E71 symbian phone, installation is ok.

but where i run the program, i received following error:
'Failed to create E:/TrekBuddy/: javax microedition.io.file
IllegualModeException: Illegal mode for this operation call'

kruch · Site Admin Joined: 02 Jul 2006 Posts: 5654

@erdos

You are not upgrading from previous version? I was able to reproduce it when I did fresh installation and TrekBuddy folder did not exist on card or internal memory. I will investigate it. Meanwhile, workaround is to create TrekBuddy folder in memory card (or internal memory) manually and start TB again.

EDIT: Or, you can try this build where it should be fixed: http://www.trekbuddy.net/dev/2016-04-29
I tested it on N808, seem ok.