Intel® Frame Debugger Release Notes

Thank you for choosing the Intel® Frame Debugger for debugging your Android* game or application. These Release Notes provide information about the product new features, system requirements and installation instructions, as well as lists known issues and limitations.

Intel® Frame Debugger Overview

Intel® Frame Debugger enables you to find the root cause of rendering issues in your Android* application, such as unsupported OpenGL* ES extensions, misplaced objects, issues with shadowing, lighting, or color schemes. Using frame capture files, Intel Frame Debugger displays detailed information on all visual changes that occur inside the frame on each rendering stage, function by function. This enables you to locate the exact API call that causes a rendering issue.

For additional information and assistance in using the product, refer to the following online resources:

• Intel GPA Online Help for Windows* OS Analysis Platforms
• Intel GPA Home Page
• Intel GPA Support Forum
• Intel GPA FAQ

What's New

• OpenGL ES 2.0 states can now be edited.
• Dynamic textures are now supported.
• Uniforms can be edited.
• Limited support for ARM*-based devices is introduced.
• Alpha channel visualization for textures in Graphics Pipeline View can be switched on and off.
• Shaders and binary program replacement is now supported.
• Compatibility check for shader extensions is now supported.
• Multiple UI enhancements: dark UI color scheme, improved full screen mode, improved touch support, etc.
• Automatic checks for software updates.

System Requirements and Supported Platforms

Minimum requirements for client systems used to debug Android* workloads are: Intel® Core™ Processor with a minimum of 2GB of memory. At least 4GB of memory is highly recommended. To perform frame debugging, you need to run Intel Frame Debugger on a Windows* OS 64-bit system.

• Client Processor: Intel® Core™ Processor
• System Memory: 2GB RAM (4GB recommended)
• Video Memory: 512MB RAM
• Minimum resolution: 1280x1024
• Disk Space: 80MB for minimal product installation

The table below shows platforms and applications supported by Intel Frame Debugger.

Target Platform (the system where your game runs)	Client Platform (your analysis system)	Target Application (types of supported applications running on the target platform)
Google* Android* 4.0, 4.1, 4.2, 4.4 (Devices based on Intel® Architecture)	Windows* 7 SP1/8/8.1 OS	OpenGL* ES 1.0, 1.1, 2.0

(Beta) Support for ARM*-Based Devices

Intel Frame Debugger now includes beta-level support for the following ARM*-based device configurations:

 

Model	GPU	Android version
Samsung* Galaxy Nexus (GT-i9250)	Imagination Technologies* PowerVR SGX540	Android 4.3
Samsung* Galaxy S4 (GT-I9500ZNASER)	Imagination Technologies* PowerVR SGX544	Android 4.4
Samsung* Galaxy S III (GT-i9300)	ARM* Mali 400MP	Android 4.3
Nexus 4	Qualcomm* Adreno 320	Android 4.4
Nexus 5	Qualcomm* Adreno 330	Android 4.4
LG* G2 D802	Qualcomm* Adreno 330	Android 4.4
Amazon* Kindle Fire HD	Imagination Technologies* PowerVR SGX544	Amazon* Fire OS 3.0

Intel Frame Debugger may run with other ARM*-based devices, but they are not supported.

Windows* OS Client Specifics

Installing Intel Frame Debugger on Windows* OS Analysis Platforms

To install Intel Frame Debugger on Windows* OS, download the IntelFrameDebugger_x64.msi file from Intel GPA home page and run the installer.

Debugging Android* Frames

Using Intel Frame Debugger, you can debug Android* applications if the following conditions are met:

• Your application runs on an Android* device based on Intel® architecture, or on an ARM*-based device that appears in the table above.
• The latest version of Android* SDK is installed on the client system.
• Android* Debug Bridge (adb) USB connection is successfully established between the Android* device and the client system.

For information on how to set up the Android* Debug Bridge USB connection for the Intel-based mobile devices, refer to the online help.

Troubleshooting Android* OS Connection Problems

If the target device does not appear when the "adb devices" command is executed on the client system, do the following:

1. Disconnect the device
2. Execute "adb kill-server"
3. Reconnect the device
4. Run "adb devices"

If these steps do not help, restart the system and then run "adb devices" again.

Once your system is set up, you can start debugging Android* applications. For details, see the Debugging on Android* topic of online help.

Intel Frame Debugger Known Issues and Limitations

• Intel Frame Debugger does not support profiling browsers on Android*.
• Intel Frame Debugger runs best on systems with a minimum of 4GB of physical memory.
• Intel Frame Debugger may fail to replay frames which extensively use multi-context rendering.
• EGLImage sharing across OpenGL* ES contexts is not supported. Intel Frame Debugger may fail to render such frames properly.