Arm Mobile Studio release history

Here, you can find details about new features and changes included with each new release of Arm Mobile Studio.

To download the latest version, go to Downloads.

Arm Mobile Studio

Version 2020.2

Released: September 03, 2020

What's new in 2020.2

This release of Arm Mobile Studio includes:

System Requirements

Arm Mobile Studio is officially supported on 64-bit versions of the following host platforms:

  • Windows 10
  • macOS 10.13 (High Sierra) or newer
  • Linux Ubuntu 16.04 (Xenial Xerus) or newer

Arm Mobile Studio is supported on 32-bit and 64-bit versions of the following target platforms:

  • Android 8.0 (Oreo) or newer

Not all Android devices provide complete performance data. Check our supported devices page to see which platforms we recommend.

Changes in this release

This release introduces the following changes and updates compared to Arm Mobile Studio 2020.1.

Streamline 7.4

  • Improved device connection user interface and workflow. When you launch Streamline, you now see a Start tab that lists any connected devices, and enables you to quickly start capturing data. Refer to Connect Streamline to your device for details.
  • You can now visualize Arm NN timeline trace data. This allows you see what your machine learning application, built with Arm NN, is doing, and how it is interacting with accelerator hardware such as the GPU.
Note: Streamline 7.4 can open capture files that were taken with previous versions, from version 6.9 onwards. Captures taken with Arm Development Studio can not be opened with an Arm Mobile Studio starter edition license. If you need to open captures taken with Arm Development Studio, you will need an Arm Mobile Studio professional edition license.

Performance Advisor 1.2

  • You can set per-frame performance budgets for a range of metrics, that are then shown on the charts in the Performance Advisor report.
    GPU cycles per frame chart with a cycles budget of 33 million cycles per frame
    Use the following command-line options when running the  pa command to specify budgets:
    --bandwidth-budget <value>
    --cpu-cycles-budget <value> 
    --draw-calls-budget <value> 
    --gpu-cycles-budget <value> 
    --overdraw-budget <value> 
    --pixels-budget <value>
    --primitives-budget <value> 
    --shader-cycles-budget <value> 
    --vertices-budget <value>
  • Specify command-line options to the pa command, using a file containing a list of options. Refer to Command-line options configuration file in the Performance Advisor user guide.
  • When using the --clip-start or --clip-end options to define a specific region of the Streamline capture to analyze with Performance Advisor, you can now specify the frame number, instead of the timestamp in milliseconds. For example, --clip-end=7000f ends the region at frame 7000.
  • Frame numbers are shown in the report.
  • Wildcard operator support when manually defining regions start and end with a regions file. Refer to Specify a CSV file containing the regions in the Performance Advisor user guide.
  • Improved region summary messaging in the report.
  • Pretty-printed JSON is now an option and not the default for JSON reports. This makes the default JSON format consumable by 3rd party database and visualization tools such as ELK stack. If you want to output more human-readable pretty-printed JSON, use the --pretty-print option to the pa command.
  • Vertex data has been renamed to 'non-fragment'. Refer to Non-fragment bound for advice.
  • Changes to command-line interface:
    • The default setting for --lwi-mode is now none. This means that Performance Advisor will perform the capture without attempting to capture images of slow frames, and you no longer need to specify the --lwi-out-dir option by default. If you want to see the frame capture images in the Performance Advisor report, you need to set --lwi-mode to capture, and define an output directory for the frame images with --lwi-out-dir
    • The default setting for --lwi is now on.
    • The default setting for --lwi-fps-threshold is now 30.
  • For Arm Mobile Studio Professional users, there’s a new tutorial and helper script, to help you set up automated performance analysis with Arm Mobile Studio as part of your continuous integration workflow.


Graphics Analyzer 5.6

  • Improved device connection support. You no longer need to use the script, to connect to your device; this functionality is now part of the Device Manager, which is launched when you start Graphics Analyzer. Refer to Capture a trace for details.
  • Updated API tracing support to include basic trace-only support for the latest Open GL ES extensions as well as for Vulkan 1.1, 1.2 and related extensions.
  • Removed support for:
    • Pre-Android 10 system-wide (rooted mode) tracing on Android targets.
    • OpenCL tracing on Android targets.
  • There's a new video to help you get up and running with Graphics Analyzer.


Mali Offline Compiler 7.2

  • Mali Offline Compiler can now be used to generate reports for devices with Mali-G57, Mali-G68, Mali-G77 and Mali-G78 GPUs, based on Arm’s latest Valhall architecture. For arithmetic-heavy shaders you can now see the instruction cycles split by the arithmetic pipeline they are using: CVT, FMA, and SFU.
  • Stack and register usage reporting for Mali Bifrost and Valhall GPUs has been improved:
    • The number of work registers in use is now accurate, previously, this number would only report whether the number was below 32 or between 32 and 64.
    • See whether any variables are spilled to stack memory, and how many bytes per thread are spilled.
    • See the percentage of arithmetic operations that are performed efficiently, at 16-bit precision or lower.
  • Shader properties are now reported to help you identify opportunities for optimization.
  • For vertex shaders, Mali Offline Compiler reports separate performance tables for position and varying shaders.
  • Information is listed for supported Vulkan SPIR-V feature level and extensions.
  • You can now export Mali Offline Compiler reports as machine-readable JSON files, so that you can build your own dashboard to monitor shader performance over time. To do this, run malioc with the --format json option.

Get started

For instructions on how to install and get started with Arm Mobile Studio, refer to the following topics on the Arm Developer website:

Further learning resources including user guides, tutorials and videos are available on the Arm Developer website.

Feedback and support

For Arm Mobile Studio starter edition you can raise queries and support issues relating to both the tools and general performance analysis on the Arm Community website.

With an Arm Mobile Studio professional edition license, you get access to world-class Arm support. To raise a request for help, go to the Arm support portal.

Known issues

The issues listed here are new in this release. Refer to our FAQ page for answers to common problems and workarounds.