Viewing and Editing Project Properties
Running Projects in the Emulator
Searching the WURFL Device Database
Finding Files in the Multiple User Environment
CLDC Emulation on a Windows Mobile Device
Installing CLDC Emulation on a Windows Mobile Emulator
Managing Device Addresses (device-address)
Running the Emulator From the Command Line
Building a Project from the Command Line
Packaging a MIDLet Suite (JAR and JAD)
Command Line Security Features
Changing the Emulator's Default Protection Domain
Signing MIDlet Suites (jadtool.exe)
Managing Certificates (MEKeyTool)
Running the Payment Console From the Command Line
Running the Java Heap Memory Observe Tool
JSR 82: Bluetooth and OBEX Support
JSR 135: Mobile Media API Support
JSR 177: Smart Card Security (SATSA)
JSRs 184, 226, and 239: Graphics Capabilities
JSR 205: Wireless Messaging API (WMA) Support
JSR 211: Content Handler API (CHAPI)
JSR 238: Mobile Internationalization API (MIA)
The Java Heap Memory Observe Tool (also known as the Heap Walker) records detailed information about the Java heap at a specific point in the virtual machine execution. It collects and displays:
global pointers
data for all objects (classes, sizes, addresses and references)
addresses for all roots
names of all classes
Please note the following:
The memory profiler uses the same connection technology as the debugger (see On-device Debugging Procedure). Because they use the same transport layer, the memory profiler and Java debugger cannot be used simultaneously.
Note - For the memory profiler, the Xrunjdwp -suspend option must be set to n.
The memory monitor slows down your application startup because every object created is recorded.
The memory usage you observe with the emulator is not exactly the same as memory usage on a real device. Remember, the emulator does not represent a real device, it is just one possible implementation of its supported APIs.