java.lang.NoClassDefFoundError during application
startup. What can I do?The installation procedure differs from handset type to handset type. For some there is an installation program for applications (e.g. Nokia PC Suite, Java Midlet Installer for BenQ-Siemens SXG75). With other types it is sufficient to copy the unzipped files onto the mobile phone. If necessary please refer to the manual of your mobile phone! Helpful references you can also find here: Installations-Hilfe (FAQ). If applications are downloaded by WAP, the installation takes place automatically.
During file access all files are read from or written to a
folder Data inbox. This folder already exists in
the most Siemens devices. Possibly it is named differently, e.g.
Misc (Siemens S*75, except SXG75). Usually this is the
default folder into which files are stored which are transferred to
the mobile phone. On devices of other manufacturers the folder will
be created automatically during the first access if it was not
created manually before. In Wayviewer the full path is displayed in
option "Folder" in the menu "Options". In LocViewer Pro the
path can be seen in Option "NMEA log file".
On Siemens mobile phones one must select the application in the folder view (menu "My phone", folder "Applications"), push the key "Options" and select the menu item "Security". The Bluetooth and data cable inquiries can be disabled completely with "Always permit". The file system inquiries cannot be disabled completely, but reduced to a minimum with "At start".
In Java™ ME applications are classified in trusted and untrusted. Untrusted applications evoke additional safety inquiries by the firmware of the mobile phone or certain actions are in principle blocked. Extreme examples are some Motorola mobile phones, e.g. the MOTORAZR V3i, which prevent any file access.
In order to convert an untrusted into a trusted application, the application must be signed with a certificate of a trusted Certificate Authority (CA). These certificates are however temporally limited and expensive. In addition it is not guaranteed that such a certificate is accepted by all mobile phones. This lies exclusively in the discretion of the manufacturer of the mobile phone or the network provider. There is only one obligatory exception, the certificate of the Java Verified™ Program. This is however too expensive, since applications must go through complex test procedures at an external test provider for each new version and for each approved handset type. This procedure may increase security and software quality, but leads however also to a restriction of the product range, in particular from smaller suppliers. To sign the applications of this web site is therefore not an option.
java.lang.NoClassDefFoundError during application
startup. What can I do?There is a Java class missing in the firmware of the mobile phone. You could try to install an alternative Java runtime environment, e.g. IBM WebSphere Everyplace Micro Environment MIDP 2.0 Java Emulator.
The files google_earth_Blitzer.kml from the
NaviFriends are declared to be UTF-8. In fact they are ISO-8859-1
coded. Depending on the firmware version this can cause problems
during the import of files which contain non ASCII characters.
There are the following options to solve the problem:
According to the NMEA 0183 standard in element 9 of the GGA sentence the altitude above see level has to be sent. Unfortunately not all GPS receivers accomplish this standard and send instead of that the altitude above the WGS-84 ellipsoid. The altitude difference in Germany is about 48 m. This altitude difference has to be sent in element 11. If the GPS receiver sends this value, an automatic altitude correction is possible. The real altitude is the difference of the values of elements 9 and 11.
GPSViewer and LocViewer have a built-in altitude correction. If the displayed altitude is correct, no altitude correction is required. If it is not, the automatic altitude correction should be tried. If this does not work too, switch to manual correction. The correction value is preset to 48.0 m and can be modified. This value will be subtracted from the received altitude value.
If you have a Siemens SXG75 you to live with it since the altitude values delivered by the device are completely wrong (see also Re: SXG75 - GPS).
Newer Nokia devices with integrated GPS receiver seem to have a problem with sound output if Bluetooth is switched on. Please switch off Bluetooth in this case.
For the voice output AMR files are used. Most mobile phones can play these. If the phone does not support this format or if the sound output doesn't work due to a firmware bug, the option "Voice output" should be switched off. Then a tone sequence is being played.
With Siemens mobile phones the voice output is quiet over the internal speaker at the beginning and becomes then louder. That was implemented specially in such a way by Siemens, in order to avoid hearing damage. This behavior unfortunately cannot be affected by application software. Also for this reason the use of a hands-free speaking system or a headset is recommended. Then the problem does not arise.
Yes, simply select the large font size in "Options". The symbols are increased four times in size. However the transparent symbol background is lost for technical reasons.
LocViewer downloads exactly the map sections (bitmaps) from the Internet which are required for display. That saves data transfer volume. Since it is hard to know in advance, where one will be later on and which zoom level will be required, it is nearly impossible to download the required map sections in advance. Therefore only direct download to the mobile phone is supported.
Not necessarily, GPSViewer, Wayviewer, and LocViewer work with almost any factory setting. Nevertheless it is reasonable to let the GPS receiver send exactly the data which are also processed afterwards, in order to not waste the reduced computing power of the mobile phones.
GPSViewer, Wayviewer, and LocViewer are able to process the NMEA 0183 sentences GGA, VTG, and RMC. For GPSViewer and LocViewer it is optimal to send one GGA and one VTG sentence per second (in this order). For Wayviewer it is sufficient to send one RMC sentence per second. Wayviewer also works with GGA sentences only. In this case however the step up of the driving instructions is not speed-dependent.
Universal GPS receivers with cable connection usually have a RS-232 interface (nine-pole DB-9 female connector) for the data and a PS/2 connector for voltage supply.
Adaptor cables to connect GPS receivers and mobile phones directly are usually not available. Therefore it makes sense to connect the data cable of the mobile phone with the connection cable of the GPS receiver.
If the data cable of the mobile phone has also a RS-232 interface with a nine-pole DB-9 connector, one can connect both cables with a so-called null-modem adapter (DB-9 male connector on both sides).
Unfortunately also such adapters are not commercial. One can make such an adapter however, by:
The connection scheme can be found for example at Nullmodem.com or Kabel-FAQ and the two D-SUB connectors and the do-it-yourself enclosure at Reichelt Elektronik (Article No. D-SUB ST 09 and COM 942).
For voltage supply cigarette lighter cables 5V / PS/2 may be used. They are available for example at Landolt-Computer.
The NMEA default Baud rate is 4800 Bit/s. Some GPS receivers deviate however from it. The SC-GPS-1 JENTRO runs e.g. with 115200 Bit/s. Please set the appropriate Baud rate in the menu "Options" in GPSViewer, Wayviewer, and LocViewer.
That means that the GPS receiver could successfully be connected, but that no useful data come in. That can be due to a wrong Baud rate setting or because wrong NMEA sentences are sent. Then the GPS receiver must be configured suitably (see above). In addition the GPS receiver must be synchronized with the satellites. That can possibly take some minutes.
Please check first whether other Bluetooth devices are in range.
If this is the case, try device search again at another place. If
this does not help, you can enter the address of the receiver in
"Options" in the field "URL". The format is
btspp://<address>:1.
<address> is the Bluetooth address of the
receiver consisting of 12 alphanumeric digits.
In several discussion boards it is reported that there are occasionally problems with Bluetooth stability in different mobile phone models.
GPSViewer, Wayviewer and LocViewer are designed in such a way that they try to work around or handle flexible such problems. If problems arise nevertheless, it is advisable,
The SXG75 has problems to read umlauts from an UTF-8 stream. Please replace all umlauts by US-ASCII characters!
If several positioning methods are supported, disable others but "Integrated GPS", in particular "Bluetooth GPS".
With Wayviewer 3.0.5 the licensing mechanism for Nokia phones was modified. Please request a new license key for free using the Feedback form. Please provide the Bluetooth device address.
Due to the big number of available mobile phone models, on which our software runs in principle, it is not possible for us to test the applications on all suitable models. Therefore it can occur despite largest care that a software bug occurs. Often also the firmware of the mobile phones is not bug free, in particular in the Bluetooth area. Please let us know such problems using the Feedback form. So you help yourself and others since we try to fix them as soon as possible.