Requirements

From TrekBuddy

Jump to: navigation, search

Contents

[edit] Java

The minimum requirements are

  • CLDC 1.1, MIDP 2.0

In order to get position info, the phone should either

  • have internal GPS and support Location API (JSR-179), or
  • have bluetooth and support Bluetooth API (JSR-82), or
  • have serial/USB/IrDa port and support CommConnection

In order to use custom maps, it is very important that the phone supports FileConnection API (JSR-75/FileConnection). Although a map can be embedded in the application jar, there often is a size limit imposed by many devices.

[edit] Device List

Devices

[edit] Notes

[edit] Branded phones (Vodafone, Orange, ...)

Branding is evil. Network operators sometimes sell phones with customized firmware which may lack Thawte root certificate in its trustore. In such devices, TrekBuddy cannot be installed as a signed application, and therefore very probably cannot be set Always allowed/Do not ask permission for reading user data, like map tiles from memory card. Having to confirm loading of every map tile is very very very uncomfortable and may piss you off to death.

[edit] Sony Ericsson

Even if you have branded phone (like V600i), you may already have the Thawte root certificate and get the error described above. Most people will tell you that you don't need the jad file on SE phone. In order to use the certificate you will have to use the jad file. If you get an error each time you send the jad to the phone, you will have to install the application this way: Point your phones web-browser (use the default browser, not something you installed) to the download page for Trekbuddy and download the jad file. Your phone will ask to download the jar file as well, so do it. Now you can set the permissions.

[edit] Motorola

Motorola phones are very problematic for TrekBuddy. but it can run on MOTO e6 correctly.

On Motorola phones there are several problems, which should be resolved to run TrekBuddy:

  • Main problem is file system inaccessibility.
  • Second problem is refusal of certificates presented in TrekBuddy application.

First problem can be resolved on Motorola 3G phones like E1000 series, V3X, V3xx, V6maxx, Razr2 by following procedure:
1) Use special V3X certificates, which allow file system access. Need to copy additional certificates to /a/mobile/certs/root/ from following archive certs V3x factory.rar (thanks to Motofan.ru). This can be done e.g. by using P2kCommander.

Second problem can be resolved by following way:
2) Remove all certificates (MIDlet-Certificate-1-1, MIDlet-Certificate-1-2, MIDlet-Certificate-1-3 and MIDlet-Jar-RSA-SHA1) from trekbuddy.jad.

After installing TrekBuddy application and starting it need to:
3) Change data directory in the Settings from file:///E:/Trekbuddy/ to one of the following value:

  • file:///b/trekbuddy - in case if memory card used
  • file:///a/trekbuddy - otherwise

[edit] Windows Mobile Devices

TrekBuddy can run on WM2003/WM5/WM6. It has been successfully tested with

[edit] Blackberry

Blackberry version (both for OS 4.2 and 4.1) is available.

[edit] Palm Devices

Works with the java runtime. The runtime is free for some devices. As no jsr-82 support is integrated, use the normal serial port with setting: comm:rfcm;baud=9600. Now the palm will ask you for a bluetooth device. How to get java: see Installation

[edit] Sony Ericsson HGE-100

This GPS enabler is accessible :

  • in trek buddy 0.9.73 via serial port with the connection URL setting comm:AT5;baudrate=9600
  • HGE-100 provider
Retrieved from "http://wiki.trekbuddy.net/index.php/Requirements"
Personal tools
others