Forums - Snapshot fails on Pixel 5

1 post / 0 new
or Register
Snapshot fails on Pixel 5
roland.kindermann
Join Date: 28 Sep 20
Posts: 1
Posted: Wed, 2020-11-18 00:07
Top

I am trying to capture a snapshot on my Pixel 5, but the profiler always gets stuck on "Retrieving Snapshot".

Capturing a trace works without issues. I have set the WRITE_EXTERNAL_STORAGE permission. The app am trying to capture is a Unity/OpenGL ES 3 app.

Looking at logcat, I think this is where the capture happens:

11-18 09:46:03.203  9099  9099 I SDP     : SDPCore: QGL_DP: Start snapshot capture
11-18 09:46:03.207  9098  9098 I SDP     : SDPCore: Metric 'OpenGL Snapshot' activated for PID 14284
11-18 09:46:03.283   868  9947 D qc_adm  : ns 1508005 > expected_ns 1000000 (skipped 1647)
11-18 09:46:03.285   868  9947 D qc_adm  : ns 1740609 > expected_ns 1000000 (skipped 1647)
11-18 09:46:03.289   868  9947 D qc_adm  : ns 1583890 > expected_ns 1000000 (skipped 1647)
11-18 09:46:03.300  9098  9098 I SDP     : SDPCore: GLES_DP: Sending QSTREAM Token 0x102000A
11-18 09:46:03.301  9098  9098 I SDP     : SDPCore: GLES_DP: Sending QSTREAM Token 0x102000A
11-18 09:46:03.301  9098  9098 I SDP     : SDPCore: GLES_DP: Sending QSTREAM Token 0x4020040
11-18 09:46:03.302  9098  9098 I SDP     : SDPCore: GLES_DP: Sending QSTREAM Token 0x4020003
11-18 09:46:03.302  9098  9098 I SDP     : SDPCore: GLES_DP: Sending QSTREAM Token 0x902000B
11-18 09:46:03.302  9098  9098 I SDP     : SDPCore: GLES_DP: Sending QSTREAM Token 0x1020006
11-18 09:46:03.302  9098  9098 I SDP     : SDPCore: GLES_DP: Sending QSTREAM Token 0x102000E
11-18 09:46:03.302 14284 14354 I AdrenoGLES-0: Unhandled QGC token: 0x102000e
11-18 09:46:03.302  9098  9098 I SDP     : SDPCore: Metric 'OpenGL Snapshot' deactivated for PID 14284
  • Up0
  • Down0

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.