Exit Print View

Java Platform Micro Edition Software Development Kit Version 3.0, Mac OS

Get PDF Book Print View

Document Information

Getting Started


Using Sample Projects

Creating and Editing Projects

Viewing and Editing Project Properties

Running Projects in the Emulator

Searching the WURFL Device Database

Finding Files in the Multiple User Environment

Profiling Applications

Saving Profiler Data

Loading Profiler Data

Saving Customized Snapshots and Images

Loading a Customized Snapshot

Network Monitoring

Lightweight UI Toolkit

Security and MIDlet Signing

CLDC Emulation on a Windows Mobile Device

Installing CLDC Emulation on a Windows Mobile Emulator (Windows Only)

On-device Debugging

Command Line Reference


JSR Support

JSR 75: PDA Optional Packages

JSR 82: Bluetooth and OBEX Support

JSR 135: Mobile Media API Support

JSR 172: Web Services Support

JSR 177: Smart Card Security (SATSA)

JSR 179: Location API Support

JSR 180: SIP Communications

JSR 184: Mobile 3D Graphics

JSR 205: Wireless Messaging API (WMA) Support

JSR 211: Content Handler API (CHAPI)

JSR 226: Scalable 2D Vector Graphics

JSR 229: Payment API Support

JSR 238: Mobile Internationalization API (MIA)

JSR 256: Mobile Sensor API Support


Saving Profiler Data

Follow these steps to enable data collection:

  1. Ensure that the heap size is at least 4MB. The profiler maintains a large amount of data, so profiled MIDLets place greater demands on the heap. To check the heap size, go to the Device Selector window, right-click on a device and choose Properties. If and provide a larger heap size. See Setting Device Properties.

  2. In the Device Selector window, right-click on a device and choose Properties.

  3. Check the Enable Profiler option, and note the location of the profiler output file.

    You can also edit the device.properties file to set profiler.enabled to true. The properties file is located in the device instance directory, as described in File Locations. The device number corresponds to a device in the device selector, as discussed in Device Names .

    Enabling the Profiler (Mac OS)

    Enabling the profiler

    Enabling the Profiler (Windows)

    Enabling the profiler

    Note - It’s helpful to display the output window. If it is not open, select Window > Output > Output.

  4. Start your application.

    Interact with your application as you normally would.

  5. Exit the application (the MIDlet suite) and return to the AMS.

    The profile data snapshot is saved and is loaded automatically and displayed in a tab labeled CPU:time, where time is the time the snapshot was saved. The SDK reports the location of the profile data in the Output window

See Loading Profiler Data.