We're pleased to announce that Snapdragon Profiler 1.4 is now available. You can download the Mac, Windows and Linux installers here.
Snapdragon Profiler 1.4 Release Notes
- Added Vulkan API performance profiling to Trace captures, including API traces and Render stages
- Added support for Snapdragon 820
- Reduced impact of Snapdragon Profiler on the device when executing System traces
- Improved performance of Trace captures
- Renamed Trace View to Data Explorer
- Data Explorer now shows data correlated from Trace captures
- Added progress notification to Trace captures
- Added support for App Tune-up Kit to Tools menu (this app is available in Google Play)
- Fixed realtime graphs stop showing data after 5 minutes
- Fixed Shader Analyzer not showing selected program
- Fixed texture thumbnail not matching actual texture
- Fixed "Active Only" resources not always accurate for buffers
- Fixed duplicate Resource categories displayed in Resources view
- Fixed Metrics showing multiple times in Data Sources view
- Fixed Snapshot not working for apps using certain GLES features
- Fixed possible crashes when connecting to the device
- Fixed Blocking not enabled when Enable Blocking is set as true in OpenCL settings
- Fixed OpenGL ES Snapshot first drawcall has incorrect metric value
- Fixed issues exporting realtime data to CSV
- Fixed out-of-memory condition when browsing Trace captures
- Fixed performance issues with Logcat view
Please share any comments you have about this update below.
- Rick
Suggestion, add menu to let user set the adb folder path,
default value should auto detect from system PATH, keep NULL if no found.
when it is NULL, and user click "Connect to a device", you should prompt user to set it or provide a link to go to Android SDK Setup file download website.
Agree - the out of box experience is difficult.
Let me know if you have any suggestions how we can improve our usability. Thanks.
- Rick
Hi,
This item has been in our backlog for a while. We'll review its priority for the next release (1.5).
Kevin
A really simple improvement is to at least fix the start-up script for the Profiler. Most systems with android sdk installed have setup the ANDROID_SDK environment variable that any shell script should see. Or it could check the default location at ~/Library/Android/sdk. Also the shell should be /bin/bash by default not /bin/sh
bugs found one 1.4:
1 Windows reaktime FPS data will lost if user switch EGL app to a non EGL app, then if user come back, the FPS still not resume it;
Only way is close snapdragon profiler and restart again after 1 minutes
2. Disconnect and reconnect by Connect/Disconnect button will never works, it will bring snapdragon profilers stop abnormally.
3 After your exit Snapdragon Profilers byWindows close button, the exe is closed, your you try to start it by the Windows Icon, your will be prompt, "Snapdragon Profiler is already running.Only one instance of Snapdragon Profiler may run at a time." wait some time such as 1 minute, you can go.
Thank you for reporting this issue and the work-around.
- Rick
"Write total (MB/s)" section in Snapdragon Profiler v1.4 always shows "zero" values on Snapdragon 800 & 820 devices. I think this bug should be fixed as soon as possible because users cannot measure actual memory traffic on GPUs.
P.S. Maybe I already wrote a post about the bug, but I found the post was not successfully uploaded in this forum and this is why I am writing this post. If both posts are uploaded, please delete one of them.
I am using 820, and all the OpenCL metrics are always zero. I only get Queued, Submitted and Execution Durations. This is what i did to get the trace:
setprop ADRENO_PROFILER_ENABLE_OPENCL 1
setprop ADRENO_PROFILER_ENABLE_BLOCKING 1
And then when i run my application i get,
Pending qxprofiler connection and capture signal...
Then open "New Trace Capture", select my app and OpenCL Metrics and Start Capture.
Am i missing anything?. I am getting the same results 810 too.
Hi Shanthan,
The steps you are doing look correct (although just so you know, they don't need to be done manually anymore and can be toggled within the Snapdragon Profiler UI under the 'Options' view).
We will try to reproduce internally as metrics values shouldn't be all 0.
Just to confirm though, you are enabling OpenCL metrics and the "OpenCL trace" metric right?
Hi jaeho.nah
Thank you for your comment I will follow up internally about your issue with "Write total (MB/s)" and we will get to it as soon as possible.
Hi Carlos,
Yes, i am enabling both OpenCL metrics and OpenCL trace.
Hi Carlos,
Were you able to reproduce the issue?
Also, profiler is not stable. It crashes a lot. And looks like Mono is the causing the crash
Crash Report:
We're seeing a very persistent crash when attempting an OpenCL Trace across all platforms (OS X 10.11, Windows 10 and Linux Ubuntu 15.10)
I grabbed this from the terminal on Linux. Hopefully this is useful to someone on the Snapdragon Profiler team at Qualcomm.
Hi jfamiglietti,
I followed up internally on your issue and while it is not fixed on 1.4.1 it will be fixed for 1.5.
Thanks,
Carlos
Hi Shanthan,
We can't reproduce this issue in house. Would you mind sharing the info of your system build and the test application? Also have you tried updating your system build?
Thanks
Juan Li
QualComm Tools Team