Follow these steps to enable data collection:
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.
In the Device Selector window, right-click on a device and choose Properties.
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 (Windows)
Note - It’s helpful to display the output window. If it is not open, select Window > Output > Output.
Start your application.
Interact with your application as you normally would.
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