Some notes on Windows Mobile
General information about Windows Mobile
The execution of Java midlets on devices running Windows Mobile will be taken over by a so-called midlet manager. There are a number of different midlet managers from different manufacturers available. Manufacturers of mobile devices and mobile operators decide upon which midlet manager to pre-install on their devices.
Even if the platform requirements for the use of the MobileSitter software are fulfilled on your device (see menu item "Technology"), it may be, however, that the installed midlet manager does not implement these requirements compliant to the standard.
On this page we have put together some information on the use of the MobileSitter software on devices with Windows Mobile. This information consists of problem descriptions, solutions and tips for using the software. The following topics are considered:
- Problems of the midlet manager accessing files (JSR75)
- Problems of the midlet manager with key codes
- Identification of the installed midlet manager
- Selection and installation of a new midlet manager
- Adjusting font size
- Install the signed version of the MobileSitter
- Adding a program shortcut to start the MobileSitter
- Additional Resources
1. Problems of the midlet manager accessing files (JSR75)
Some midlet managers do not handle file accesses according to the JSR75 standards. The MobileSitter software tests the JSR75 compatibility at the start. If the device is not standard compliant, an error message is shown. In some cases, this can lead to freezing the software (usually with the message "Please wait").
On the page Checking the JSR75 support of a midlet manager you will find information to determine whether your installed midlet manager supports JSR75 or not.
If your midlet manager does not support JSR75, the installation of an appropriate midlet manager can provide a solution. See section "Selection and installation of a new midlet manager" below.
2. Problems of the midlet manager with key codes
Midlet managers on some devices have problems with the processing of key codes. As a result, midlets cannot be properly controlled from the keyboard. This problem occurred in our tests on the devices HTC TyTN, O2 XDA II, Qtek 9600, T-Mobile MDA Vario II with preinstalled Tao Intent midlet manager versions. Please note that newer versions of TAO Intent midlet manager may handle key codes correctly.
The installation of an appropriate midlet manager usually solves this problem. See section "Selection and installation of a new midlet manager" below.
3. Identification of the installed midlet manager
In many cases, the starting point for troubleshooting is the identification of the installed midlet manager. On the page Identifying the installed Windows Mobile Midlet Manager we provide information about how to identify the installed midlet manager.
In addition, it is useful to know, whether your midlet manager fulfills the platform requirements, in particular JSR75 (see the section "Problems of the midlet manager accessing files (JSR75)" above).
4. Selection and installation of a new midlet manager
Often, the selection and installation of an appropriate midlet manager provides a solution for the previously mentioned problems or a precondition for desired properties such as the use of the signed MobileSitter version or font size adjustments.
On the page Selection of a new midlet manager we have put together information on selecting and installing a new midlet manager.
5. Adjusting font size
After successful installation of the MobileSitter software it is possible that the displayed font size in MobileSitter appears too small or too large. For a guide to the various possibilities of font size adjustments, see Adjusting font size.
6. Install the signed version of the MobileSitter
The MobileSitter software is available both as an unsigned as well as signed midlet. The signed version has some benefits with respect to usability, since all security-related questions of the midlet manager when accessing files are suppressed (e.g., at the start of the software or when exporting and importing).
Experienced users can use the instructions at Install the signed version of the MobileSitter software to install the signed version of the MobileSitter software.
7. Adding a program shortcut to start the MobileSitter
By default, midlets can be started only from the midlet manager. However, with a little trick it is possible to create a MobileSitter shortcut in the Programs menu, as well as assign a software key to start the MobileSitter. We provide a guide for experienced users on the page Creation of a MobileSitter Shortcut and Running the MobileSitter from a Soft Key.
8. Additional Resources
Problems with Windows Mobile midlet managers are discussed in many forums on the Internet, particularly in the context of widespread J2ME applications, such as, Opera Mini.
An overview of existing midlet managers (including their features and information where to download or buy them) provide, for example,
- the "Java Midlet Bible" by Modaco and
- the "MIDlet Bible chart" of Winmobiletech.
Please use a search engine to find the corresponding pages.
