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] Devices

Supported 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 irritate you 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

On Motorola P2K phones there are several problems, which needs to 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 - copy on rapidshare: [1]. (russian page seems that the file no longer exists) This can be done e.g. by using P2kCommander.

2) Second problem can be resolved by removing MIDlet-Jar-RSA-SHA1 attribute from trekbuddy.jad.


On Motorola A780 the above problems were solved with the following procedure:

1) Copy trekbuddy.jar and trekbuddy.jad (generic version) to MyPrograms on the phone.
2) Install using trekbuddy.jar (not .jad). It will install as an untrusted application.
3) Find a trusted application, for mine it was ExtremeSnowboarding, a game preloaded with the firmware update. Look up the application's java folder, for example .system/java/SystemApps/MIDlet00500/. Copy the file permfile.txt to trekbuddy's java folder, for example .system/java/DownloadApps/MIDlet005xx/.
4) Copy trekbuddy.jad to .system/java/DownloadApps/MIDlet005xx/Files/. Edit the file and downgrade the MIDP from 2.0 to 1.1: "MicroEdition-Profile: MIDP-1.1". You can leave the MIDlet-Jar-RSA-SHA1 line in there.
5) Look at the trusted app's registry.txt and modify trekbuddy's registry.txt accordingly (.system/java/DownloadApps/MIDlet05xx/registry.txt). Here are the lines I changed:

Jad-Path: /diska/.system/java/DownloadApps/MIDlet005xx/Files/trekbuddy.jad
DRM-Mode: Forbidden
Is-Trusted: 1
Jar-URL: trekbuddy.jar
Domain:

This procedure solved GPS access permissions and file system read permissions. File system write seems to be denied still.

[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 supported.

Retrieved from "http://wiki.trekbuddy.net/index.php/Requirements"
Personal tools
others