Hi ,
Is that possible via Snapdragon profiler profile on Android native c++ (callstack, function tree calls, bottleneck ..)?
If yes what configuration steps required to do that .
Thanks.
native c++
Posted: Thu, 2018-03-15 02:07
Forums - native c++
Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.
Hi,
I have the same problem. Have you solved it yet?
I tried to do it, but it didn't work out，Maybe we can talk about it
Looking forward to your reply.
thanks.
I haven't found a way to do exactly this, but you can get an approximation by recording a trace and then pressing the Analytics button (Erlenmeyer flask icon) next to the zoom buttons above the trace report. Once you have the analytics window, go to Thread Level Data -> Thread Time Per Core and you can see CPU% usage per core associated with all running threads. This doesn't give much info on its own, but it can point to definitive troublemakers when paired with data from Android Studio's Profiler C++ function tracing, which gives a breakdown of Wall Clock time taken up by various threads and their callers/callees; the SDP readout tells us the actual CPU usage per thread and the AS Profiler tells us a bit about the actual call flows associated with various threads. Good luck!
Edit: while the above can help, a more direct solution seems to be Sampling Capture, which is detailed in the User Guide -- it shows up as grayed out under Capture -> New Sampling by default and requires Android SDK and NDK locations to be set and SDP to be restarted thereafter before sampling capture becomes available.