I am trying to understand the requirements to get the Snapdragon profiler to recognize a running application. From other posts in this forum, I have gleaned that I need to be using an Adreno GPU from series 400 or higher: I am using a Snapdragon 820, which uses the Adreno 530.
I have also gleaned that I need to create an Open GL context, and I need to have internet permissions enabled. I have done these things. I have created a small native app with the following entry in AndroidManifest.xml:
<uses-permission android:name="android.permission.INTERNET" />
My current test application does nothing but establish an EGL context over GLES 3.2, poll and dispatch from the ALooper message pump, create a surface for rendering when the window becomes available, and render a green background with a blue quad on top of it repeatedly from then on.
When I launch this application with the SnapDragon profiler running, I see the following message shortly after creating the render surface, which I believe to be an error that might be preventing the profiler from recognizing my application:
06-16 11:26:17.186 19057-19096/com.example.timmcquaig.androiddemo I/Adreno: Could not create Profiler listener thread
I am currently using the latest Snapdragon Profiler I could find (v 1.7.0.5152017), though I have encountered the same issue with 1.6.1.2242017. I am unclear how to proceed; I cannot find any mention of where this error is coming from, nor how to address it (nor am I 100% sure it's my problem/my only problem).
Any assistance would be greatly appreciated!
Hi Tim,
Sorry you are having problems! Normally the "Could not create Profiler listener thread" means the apk does not have the needed internet permission enabled. Since you've added that to your manifest, I'm wondering if you need to perhaps uninstall your apk first and do a clean install for the apk to actually get updated on your device?
To help verify that the apk contains the permission, you can try extracting the apk from the device, unzipping it, and check the manifest for the permission (the manifest is mostly unreadable when doing this, but usually the permissions can still be noticed).
Let me know if any of this helps, and we can try more ideas if things are still failing.
-Ben
I could not figure out what was going on, so I decided to go with the nuclear option - I blew the demo away and rebuilt it from scratch. When I was done, it worked. I do not know what I did wrong, but it no longer matters :).
Thanks!
Glad to hear you got things working....although I do remain curious as to what was causing the issue. Let us know if it starts happening again, and we can continue troubleshooting.
Cheers,
Ben