Installation

From TrekBuddy

General steps of installation and verification.

1. Download the application from the forum www.trekbuddy.net/ (or the link to the forum on the left side)
2. Install TrekBuddy application.
3. Create obligatory folders for waypoints, logs, sounds, graphical elements etc. Copy CMS profile files, check how it works. See CMS and [1] and [2]
4. Connect to GPS (internal or module), remember to restart TB to have provider shown in menu as Start YourGpsName.
5. Check Settings.

Additional steps of installation verification

1. Copy maps and choose default one.
2. Copy waypoints file and try navigate. Check if logs are recorded.
3. Try to comunicate position via SMS.
4. Record waypoint and take picture.

The midlet is signed by Thawte Code certificate. For signed midlets, users have more options for setting up permissions for the application.

Typically, in addition to Never Allowed and Ask Always, for signed applications Ask Once and Always Allowed are available.

Since TrekBuddy has been designed for offline maps, it is very useful to set Always Allowed value for file reading permission. Also it is a good idea to set Always Allowed value for file writing permission, for easy trackloging.

Contents 1 Nokia 1.1 S40 1.1.1 N6230i 1.2 S60 1.2.1 N95, E61i, ... 1.2.2 N6220 classic 2 SonyEricsson 2.1 W800i/W810i/W880i/K750i 2.2 Z520i (and other Bluetooth phones) using Mac OSX 2.3 K530i and HGE-100 2.4 M600i 3 Siemens 3.1 SXG75 3.2 S65 4 Motorola 4.1 Q9h 4.2 ROKR Z6 5 LG 5.1 KU 990 Viewty 6 Palm 6.1 Treo 650 6.2 How to get and install Java for Palm 7 Blackberry 8 Known Issues 8.1 Branded phones 8.1.1 List of affected Providers/Phones 8.1.2 Possible Solutions 8.2 "Operation failed" on Sony Ericsson phones 8.3 Nokia N95 (also 6290) 8.3.1 Solution

[edit] Nokia

[edit] S40

[edit] N6230i

Use Nokia PC Suite.

1. Connect your mobile as you regularly do (bluetooth, irda, serial, whatever)
2. Open the PC Suite
3. Click on "Install Application"
4. Select trekbuddy
5. Wait for the installation to complete

The program will end up in "Programs/Collection" as "Trekbuddy".

Once it is installed, you may want to setup the permissions:

1. Go to "Programs/Collection" and put cursor on "TrekBuddy".
2. Select Options->Application acces->Phone Access->Read user data->Always allowed
3. do the same for Write user data

[edit] S60

On some S60 devices, Thawte certificate is not allowed to be used for application signing. To enable it, do (eg. N95):

1. go to Tools (or Menu)->Settings->General->Security->Certificate management-> MIDP2 Thawte->Options->Trust Settings
2. set Application installation option to Yes

Exception (noticed with N6110 navigator): When getting an errormessage while installing: download the jar and the jad File to your phone via GPRS/UMTS/WiFi /USB-Cable(Datatransfer, not via the Nokia Application Installer) and manually start the installation process on your phone.

[edit] N95, E61i, ...

Use PC Suite, or:

1. Copy trekbuddy.jar and trekbuddy.jad to the phone
2. In the phone, use "File Manager" to browse to trekbuddy.jad
3. Select it to start Installer and install the midlet
4. Once installed, go to Tools->AppManager->open TrekBuddy, and set Always allowed for Read user data (and for Edit user data for tracklogs)
5. That's it!

[edit] N6220 classic

1. Copy trekbuddy.jar and trekbuddy.jad to the phone
2. In the phon, go to Menu -> Settings -> Data mgr -> File mgr
3. Find trekbuddy.jad and select it to start installation
4. Once installed, go to Menu -> Settings -> Data mgr -> App mgr -> Installed apps -> TrekBuddy and select Settings
5. Adjust permissions like set Always allowed for Read user data (and for Edit user data for tracklogs)

[edit] SonyEricsson

[edit] W800i/W810i/W880i/K750i

Installing TrekBuddy on a W800i/W810i/W880i/K750i is quite straightforward. The USB-cable provided with the phone is required. The following instructions should work with Linux and Windows.

• Connect your W800i/W810i/W880i/K750i to your computer using the USB-cable.
• A new drive should appear. It correspond to the memory stick of your phone.
• Copy both trekbuddy.jar and trekbuddy.jad to MSSEMC\Media files\other\. Do not rename the files.
• Disconnect your phone and go to Menu -> File manager -> Other.
• You need to install trekbuddy.jar and not trekbuddy.jad. In order to find the good one, select More -> Information. You should see File type: jad. This is important, because only then you can configure the Java-Permissions of Read/Write user data to Never ask!
• Select Install.
• Select the destination. You probably want to select Applications.
• Don't start application when phone offers this to you - you may want to set up application permissions first, to avoid confirmation prompts when accessing resources like files and/or bluetooth connection: go to Applications, find TrekBuddy, select More -> Permissions and set Read/Write user data to Never ask. Consider doing the same for Local connectivity.

[edit] Z520i (and other Bluetooth phones) using Mac OSX

Installing TrekBuddy on a z520i and surely on many other Bluetooth-enabled phones is quite easy.

• be sure Bluetooth is enabled and visible on both computer and phone.
• to transfer files, use the Bluetooth File Exchange application located into the Applications:Utilities folder (it is reachable also from the menu bar, on right, if you enabled the Bluetooth shortcut).
• select your phone from the list of Bluetooth devices (wait until it is recognised).
• if requested, do the pairing.
• just navigate into the phone file system, until you find the "Other" folder (or the memory stick for phones having also that). Put there both jar and jad files. You might also just transfer the jar file, but you will not be able to use the signed midlet feature.
• close the computer software, go to the phone, go to Menu -> File manager -> Other, and select the jad file.
• Select Install.
• Select the destination. You probably want to select Applications.

In the same way you will be able to transfer maps and other files.

[edit] K530i and HGE-100

• Installation is straightforward
• connect using the USB interface. In normal operation mode you will have to locate a folder in the selected language, using it in file transfer mode you will get the english default names.
• copy both files into a folder of your choice, possibly create a new one.
• On the phone locate the files, since their extensions are hidden you will see both having the same name. Select one and run the install command. The phone is smart enough to use tha jad file...
• choose target, presumably applications rather than games.
• once installed configure the communication to be serial; set the connection string to "comm:AT5;baudrate=9600". select HGE-100 location provider in Settings->Location
• important to save the settings rather than just apply. Otherwise your phone will vibrate when the application is started.

[edit] M600i

• Copy trekbuddy.jad and trekbuddy.jar to the device, eg. to Other directory on the memory card
• Select trekbuddy.jad (the one that has Details option in the context menu when you press select View) and then Install to install the application

You may want to remap some keys for easier use - see Customization

[edit] Siemens

On many Siemens/Benq phones Thawte certificate is not present and installation fails. Luckily, even for unsigned midlets, user can use Ask Once (or Allow for session) permission, so it is not a problem - either remove certificates and signature from the JAD file (see S65 installation bellow), or do not use it at all.

[edit] SXG75

A DCA-540 data cable is needed to install TrekBuddy from your PC on a Siemens SXG75.

The easy way of installing TrekBuddy is by using the JMI (Java Midlet Installer) After the phone is recognized by the JMI, select the Java Application radio button, find the trekbuddy.jar and trekbuddy.jad files on your system (you should put them in the same folder) and click Install. The JMI will ask you to reset the phone automatically but you can also do it yourself.

If you experience problems (TrekBuddy does not appear in the Apps folder after installation) you may need to edit the trekbuddy.jad file. Simply delete the last couple of lines containing the Midlet certifications. (Actually, it's enough to remove the 'MIDlet-Jar-RSA-SHA1:' line.)

The JMI may not work with every firmware version. Another method is using the Brew Mobile Commander. Create a trekbuddy.jad from the jar using JADgen. Right click trekbuddy.jar and choose install.

It is recommended to create a subdirectory tb in brew/shared (so a user independent directory (not efs-user) that is not stored on memory card (efs-mmc)) with subdirectories resources, sounds, tracks-gpx, ui-profiles and wpts. Set the data directory to file:///fs/tb/ in the Settings. The maps can be stored on the memory card. See in the TrekBuddy forum under Themes what to store in ui-profiles and resources. A sound when reaching a route point can be found here

Filesystem in SXG75 showing TrekBuddy data directory structure

[edit] S65

1. download generic version
2. open trekbuddy.jad in editor and remove all lines beginning with MIDlet-Certificate- and MIDlet-Jar-RSA-SHA1
3. copy jar and jad to phone (over Bluetooth or cable)
4. click on trekbuddy.jad, select when the application should be installed (Applications)
5. on first launch, when asked for permission to access some file, change permission scope to "for relation"

[edit] Motorola

For Motorola P2K phones (mostly 3G specific) see: Requirements

[edit] Q9h

See forum

[edit] ROKR Z6

See forum

For generating Certificates for File-Access see here: modmymoto.com

[edit] LG

[edit] KU 990 Viewty

My basic phone specs.

Phone: KU990 Firmware: Version 10a Operator: T-Mobile (UK) Memory: Micro sd 1GB GPS Device: Bluetooth enabled Keychain GPS 2000 by Freedom

Note: Before installing TrekBuddy, pair your GPS device with your phone first and grant all necessary permissions.

1. Download Trekbuddy.jar from this site. The phone will save the file to My Stuff, External Memory, Others

2. Navigate to TrekBuddy.jar file on your phone and double tap on the name to begin installation.

3. Grant all permissions requested by the application during installation.

4. Switch on your GPS device and start Bluetooth on your phone

5. Navigate to the installed TrekBuddy application which should now be found in My Stuff, My Games and apps and double tap the screen to start the app.

6. On the screen you should now see a map of the world and the word "Options" above the left "soft key" of the phones native navigation console/display. Tap "Start" and TrekBuddy will search for your GPS device. Once the name of your device appears tap on "Select" and wait for TrekBuddy and the GPS device to connect. Note: The next time you start TrekBuddy the name of your GPS device will have been added to the TrekBuddy menu so you can select it.

7. Tap Options to open the TrekBuddy menu and then tap "Settings". Scroll through to set your desired settings. (See Help, Manuals, How Tos elsewhere on this site)

Almost Done!

8. In order to use all the functions of TrekBuddy you'll need some maps, which you can obtain from elsewhere on this site. The important thing to do is to set up the following directories on the phone sd card for storing maps, waypoints and track logs.

Note: The easiest way I have found is to connect the phone to your computer (usb cable) and use the normal Windows file explorer to create directories on your sd card. When you download maps later you can save them directly to the card it's really simple. You can also do the same thing with phone file explorers such as Mobyexplorer

9. Connect phone and navigate to the sd card using windows file explorer then create then the directory /TrekBuddy.

10. In the /TrekBuddy directory create 3 further sub-directories, /tracks-gpx (gpx track logs will be saved here), /tracks-NMEA (NMEA track logs will be saved here, /wpts (waypoints will be saved here)

11. The final step is to tell TrekBuddy where these directories are. Start the TrekBuddy app and tap the left soft key to bring up the menu. Tap Settings, tap Basic, scroll down the menu and tap Data Dir, enter the following, file:///Card/TrekBuddy The other 3 sub-directories which we created above are used by TrekBuddy.

Done!

TrekBuddy works on my phone and it's brilliant. If you encounter any difficulties with the above it is more than likely your phone specs are not the same as mine or I've made a "mistake" in above description. Please let me know. (Ricster)

[edit] Palm

[edit] Treo 650

Ton install TB on Treo, please make sure, you have installed JAVA Runtime. Then it is quite easy:

1. download the jar file
2. translate jar to prc with jartoprc_w.exe from the java runtime kit
3. install the *.prc file
   • with the next hotsync,
   • or copy it to your SD card in the folder /palm/launcher/
4. follow the HOWTO from kruch http://www.trekbuddy.net/forum/viewtopic.php?t=22

[edit] How to get and install Java for Palm

Quoting www.palm.com "As of January 12, 2008, Palm no longer has rights to distribute the IBM WebSphere Micro Environment Java Virtual Machine (JVM - info) to our customers"

Note: you need to find WEME571.zip

For Palm OS Devices, one can download the enviroment from http://www.palm.com/us/support/jvm/ resp. http://www.palm.com/us/support/jvm/download.html. For some devices the environment is for free and support JSR-75 for file access.

Now extract the archive, and install all the needed prc files with the next hotsync to your TREO (not on SD card).

In the subfolder JVM\PalmOS JVM 5.7.2\Tools\bin you will find the program called jartoprc_w.exe for translation of jar or jad files to the palm specific *.prc format. Start it and give the path to the jar / jad file. [Image:http://www.trekbuddy.net/forum/files/jartoprc_153.png]

There is no need to convert it anymore, since trekbuddy.prc is provided by default, signed.

[edit] Blackberry

Use Blackberry Desktop Manager to install TrekBuddy to the device. Or use Over-The-Air installation.

Tip: "Also a bit of a tip to 8310 users, if you can't add the instalation with the BB desktop manager, connect the BB to the pc with usb and put the .jad instalation file somewhere with according 2 files and then unplug it, go to media and switch browse files ==> open the .jad file and instalation will begin. Also you might want to set permission level to allow." bgluvacevic

Another user installation experience here

[edit] Known Issues

[edit] Branded phones

Branding is evil. Some GSM providers modify the firmware of the phones they sell with their plans. In some cases (see below), Thawte root certificate is missing. This prevents TrekBuddy from being installed as a signed application. Constantly having to confirm file system access and similar security messages are the result.

[edit] List of affected Providers/Phones

• Vodafone Germany: SE K800i, K750i
• Vodafone Spain: Nokia 6234
• Movistar Spain: Samsung L760
• Orange Israel: Nokia 6288
• Proximus/Vodafone Belgium : SE K800i
• Telstra Australia - SE W810i
• Orange Slovakia: SE K800i
• Rogers Canada: SE W810i
• Extend me!

[edit] Possible Solutions

• Try to get a firmware update from your local retailer
• Get your phone "debranded" / "Unlocked", either in a local cellphone-store, or via the internet
• Try to fix the firmware yourself (may be dangerous)
• Do an unsigned installation and live with the nag-screens

The first two solutions are preferable, although are not entirely free. Some phones have internal firmware upgrade support, others include software and cables to install upgrades at home. Phone shops often bill a few euros for this service. Debranding services are a few dozen euros. Fixing the firmware yourself is a dangerous (may cause a inoperable phone), very model specific and, depending on local law, illegal procedure.

An unsigned installation can be made by erasing the .JAD-File and selecting the .JAR-File upon installation.

[edit] "Operation failed" on Sony Ericsson phones

Remove line starting with MIDlet-Certificate-1-3 from JAD file.

[edit] Nokia N95 (also 6290)

SecurityException is thrown whenever a file is to be read or GPS accessed, even though permissions are set up accordingly.

[edit] Solution

In the JAD file, Rename attribute MIDlet-Permissions-Opt to MIDlet-Permissions, and reinstall the application.

http://forum.nokia.com/document/Forum_Nokia_Technical_Library/contents/FNTL/Problems_in_requesting_optional_API_access_with_MIDlet-Permissions-Opt.htm

--more to come--