As of BlackBerry® 10 OS version 10.2 (which brings the Adobe® AIR® 3.5 runtime), AIR developers have the ability to profile their applications using Adobe Scout. Scout gives AIR developers insight into the behavior of their applications frame by frame. It works with standard DisplayList apps as well as with Stage3D and provides insight into how applications are using cpu, memory, and how content is being rendered.
To enable Scout to collect information on BlackBerry 10 you must add a file that’s called telemetry.cfg to the root of a projects src folder. In Adobe® Flash Builder® it looks like this:
The telemetry.cfg file has your debug IP address as well as some boolean variables that define what data you would like Scout to collect. Here is what it looks like:
The default IP address when testing using a USB cable is 169.254.0.1. The default debug IP is 169.254.0.2. The default port is 7934 and defined in Scout’s settings.
Enable detailed telemetry
To collect detailed telemetry data Scout relies on the telemetry feature that was introduced in AIR 3.4. In Flash Builder 4.7 you can enable this feature in the project properties ActionScript Compiler section.
If you don’t have Flash Builder 4.7 you can enable advanced telemetry data on your compiled swf’s using python or by using TelemetryEASY which is a drag and drop Windows® AIR application.
It should be noted that you will still be able to collect basic information from Scout even if you don’t have the detailed telemetry feature enabled on your swf. You must be publishing using Adobe® Flash® Player 11.4 or AIR 3.4. For more information on Scout you can visit the official getting started guide from Adobe.