Troubleshooting - Motorola T720 Developer's Manual

Developing for the
Motorola T720 Handset

Troubleshooting

This section describes some common troubleshooting issues and their solutions.
Title
Problem
Solution
Title
Problem
Solution
Applications consume more space on the Motorola T720 than other
devices.
The application consumes much more size when downloaded to
Motorola T720 devices or use Motorola T720 emulator. The Motorola
i95cl (actual device as well as emulator) uses approx 340KB of heap.
Motorola's Motorola T720 emulator, the exact same MIDlet uses over
900KB of heap!
Image files take up twice as much space in the emulator as they
should. Image files will be substantially larger under the emulator since
they are stored as 24-bit true color images instead of the 12-bit images
that would be stored on the phone. We recommend increasing the
heap size of the emulator as a workaround. The heap size can be
changed in the Motorola T720.props file in the 7.5 emulator installation.
Although image files take up the correct amount on space on the "real"
phone, you will encounter other problems there. On the real Motorola
T720 phone an installed MIDlet requests twice as much memory as it
needs so you might run into more problems.
An application installed on the device takes permanent space for
existing on the device.
When an application is installed to a device, it consumes the device's
space. Does this application take that program space permanently in
order to exist on the handset, or just temporally in order to install on the
handset?
After the application has been installed on the phone, it exists there.
Normally, the installation of an application to the phone takes 3 steps:
1. Decompression if your JAR file is compressed;
2. Verificaton: the class files are verified to ensure that the class files
come from a trusted source;
3. Transformation: After the application has been verified, it is
transformed from the application class files into a device specific
internal representation. This allows the application to be launched and
executed faster than loading the raw class files. The transformed file
(and associated resources) is stored in the FLASH file system on the
device.
37