TrekBuddy

[guest]

Hi,

I stumbled accros this excellent software while prepairing my phone for a BT GPS reciever which is on the way.

I have a Nokia 6630 and a Nokia E61, obviously I would want to use the E61 due to better screen size and battery life.

Now some buttons do not work on the E61, I just managed to load a single map and am surprised that there is no zoom in and zoom out, so I will definitely prepare an atlas with different layers for that.

I can not load waypoints because the "1" numeric key does not launch the waypoints menu, can these features be made part of the main menu to avoid this problem. Or are any workarounds for this? Also I have 1300 or so waypoints for my city do I need to remove some from my gpx file or can TB handle this number of waypoints??

[tazzix]

If the first post was too complicated, in short:

keys do not work on Nokia E61.

I am a J2ME developer myself and have access to several mobiles, would be glad to help in this regard.

[kruch]

Are "Waypoints" (key 1) the only trouble on devices like E61? Can you scroll etc? I'll add "Waypoints" command to the main menu, no problem.

As for many wpts - didn't tried yet (I have ~85 max in one gpx file); I guess it is only matter of free memory....

[tazzix]

Thanks for you reply, here is a summary of "what happens" for keys:

1: Scroll North
2: nothing changes apparently
3: backlight 50% 100% 0%
4: same as 2
5: scroll East
6: Scroll West
7: Scroll South
8: same as 2
9: Map selection (from Atlas?)
0: Scroll South
*: Scroll North
#: same as 2 (should switch CMS/HPS??)
Direction joystick: scrolls in appropriate directions.

If I keep pressing any thing which scrolls East then the app starts scrolling West in a very fast pace.

I loaded an Atlas with one file having a bad parameter in the .MAP file, I fixed it now but TB is stuck with the old version does it use RMS for cache? Can I reset or force reading the new version?

Thanks a lot.

[kruch]

- keycodes

Searched Nokia forums a bit, and found two interesting notes

1) "The keycode issue is corrected in the next public firmware release. 2.0618.06.05 if I am not mistaken."

2) keycode as seen by an application seems to be different when "the blue key in the bottom left" is pressed... eg. "When pressing #, 106 is returned (unless you press the blue key in the bottom left at the same time, in which case 35 is returned" - 35 is what TB recognizes as screen-switch action

- TB does not cache anything in RMS, it's used only to store configuration there..

[tazzix]

I'll probably wait for your next release before trying Nokia Update (I bricked a 6630 already), actually I am used to my old Garmin eTrex Venture and miss the track trace to the extent that I am uncomfortable. I am evaluating nhGPS on my SonyEricsson P910i but that thing has a calibration bug which surprises me as it is a commercial product. Hats off to you guys because TB is pixel perfect and the atlas feature compensates zoom in/out better because I can still read the street names, etc.. And I have binary polygon data for my city so I can generate any zoom level as I please. Moreover, I have generated maps with my POIs drawn on it so I can live with the fact that TB does not show waypoints on the map.

[kruch]

OK, but can you check whether that "the blue key in the bottom left" affects keycodes for TB?

[tazzix]

No it does not. In the firmware that I am using I can use number keys in all apps without using the blue key that is why I want to stick to this, so I can press e.g. menu - 9 - 4 to launch the clock app and set an alarm while holding a book in my other hand. If I upgrade the firmware, I will have to use both hands for simple tasks like these

[Momme]

Hi,

i got my E61 today, after a softwareupdate trekbuddy works now.

regards

Momme