Forums - Does the Adreno Profiler support the Nexus 4?

17 posts / 0 new
Last post
Does the Adreno Profiler support the Nexus 4?
programmerTim
Join Date: 14 Nov 11
Location: Cambridge, UK
Posts: 3
Posted: Wed, 2012-12-19 06:42

Does the Adreno Profiler support the Nexus 4?  I tried the latest version (2.9) but it didn't find my application.  I've previously been using the profiler successfully with my old HTD Desire.

 

  • Up0
  • Down0
Stephen
Join Date: 21 Oct 10
Posts: 2
Posted: Thu, 2013-01-31 15:34
Bump
  • Up0
  • Down0
VMX
Join Date: 28 Apr 11
Posts: 3
Posted: Sat, 2013-02-02 09:57
I have the same problem using the current version (3.1) on a Nexus 4 using JB 4.2.1 (JOP40D) or 4.2 (JOP40C) ... I don't know if it's a permission problem. Has anyone run successfully the Profiler on Nexus4?
  • Up0
  • Down0
Scott (not verified)
Posted: Fri, 2013-02-08 16:03
I'm curious about this as well.
  • Up0
  • Down0
Ernest
Join Date: 2 Jun 10
Posts: 3
Posted: Tue, 2013-02-19 06:54

Same problem here.Nexus 4, Android 4.2.2, Build number JDQ39.

  • Up0
  • Down0
Manjuladevi Kuttuva
Profile picture
Join Date: 26 Oct 12
Location: San Diego
Posts: 5
Posted: Thu, 2013-02-21 14:46

Thanks for reporting the issue. We are able to reproduce it and the fix will be in the May update.

  • Up0
  • Down0
VMX
Join Date: 28 Apr 11
Posts: 3
Posted: Mon, 2013-02-25 08:41

Thank you for the reply.

I am wondering if you can tell us if the Adreno Profiler problem with Nexus4 is related to the profiler support in the Nexus4 kernel, or if it has to do with the Adreno Profiler itself.

 

If you can't answer the above can you please tell us if there is a known APQ8064 codeaurora release known to work with Adreno Profiler?

 

Best regards.

 

 

 

  • Up0
  • Down0
seano
Join Date: 12 Apr 13
Posts: 4
Posted: Tue, 2013-05-14 13:28

I have not been able to get the latest Adreno Profiler to connect to my Nexus 4.   Has this problem been repaired?

I downloaded the latest profiler today (version 3.3) and pressing Connect.. gives me "WARNING! Could not find a device". I tried restarting adb, killing all other adb instances to no avail.

 

  • Up0
  • Down0
seano
Join Date: 12 Apr 13
Posts: 4
Posted: Wed, 2013-05-15 12:59

Any update?  Anyone get this profiler working on a nexus 4?

  • Up0
  • Down0
Dave Astle
Profile picture
Join Date: 19 Oct 12
Location: San Diego, CA
Posts: 99
Posted: Thu, 2013-05-16 11:11

There is supposed to be an update coming from Google this month that officially fixes it. You can also push the driver binaries from the downloads page here, and that should work as well.

  • Up0
  • Down0
seano
Join Date: 12 Apr 13
Posts: 4
Posted: Thu, 2013-05-16 14:07

@Dave

Manually updating the drivers worked!

FYI, the steps I took were:

  1. 1. Root the Nexus4. Create a temporary folder on the phone: mkdir /sdcard/temp
  2. 2. Download and then copy the drivers from 23 Apr 13 at https://developer.qualcomm.com/mobile-development/mobile-technologies/gaming-graphics-optimization-adreno/tools-and-resources to my sdcard using  adb push system /sdcard/temp
  3. 3. Make the /system volume on the Nexus4 writeable using adb shell, su,  mount -o remount,rw /system
  4. 4. Copy the updated drivers from /sdcard/temp to the system folder: cp -R /sdcard/temp/* /system
  5. 5. Reboot Nexus4 and enable profiler: adb shell, setprop debug.egl.profiler 1
  6. 6. Start my app, connect with the profiler (worked!)
  • Up0
  • Down0
Jack Hsieh
Join Date: 22 Apr 13
Posts: 3
Posted: Tue, 2013-06-04 20:02

Are you guys able to run the Scrubber CL in the Adreno Profiler? We have rooted the Nexus 4, put in the lastest driver, set the ADRENO_PROFILER_ENABLE_OPENCL property. We were able to connect the app, the Grapher worked just fine, but the big red button in Scrubber CL stayed gray. I tried deferring the call to clGetPlatformIDs untill after the app is connected, still no good. Any idea what I might have missed out? 

  • Up0
  • Down0
Dave Astle
Profile picture
Join Date: 19 Oct 12
Location: San Diego, CA
Posts: 99
Posted: Wed, 2013-06-05 09:43

APK profiling for OpenCL isn't supported in the current public driver release for Nexus 4. It should be available in the next update, though (not sure when that will be yet).

  • Up0
  • Down0
mattr_hb
Join Date: 12 Jun 13
Posts: 2
Posted: Wed, 2013-06-12 08:20

When I try to connect the profiler to my Nexus 4 I get a dialog that says:

"WARNING!  ADB found a device, but no Adreno Profiler enabled application can be found.  If your application is running please ensure that network privileges have been enabled in the APK manifest."

I do have network privileges in the manifest file, and I did the shell setprop to enable debugging.

One step in the instructions that is confusion is: "Finally, before profiling, and after rebooting your Android device..."

Why would I reboot my Android device?

BTW, I did try rebooting it, and I still get the above message.

Any suggestions?

  • Up0
  • Down0
mattr_hb
Join Date: 12 Jun 13
Posts: 2
Posted: Thu, 2013-06-13 05:58

As a follow up, I followed seano's directions and can now connect the Adreno Profiler to my app.

  • Up0
  • Down0
vladich
Join Date: 12 Nov 13
Posts: 1
Posted: Tue, 2013-11-12 17:28

Did anybody try to make it work with Nexus 5?

  • Up0
  • Down0
willgunx
Join Date: 20 Oct 13
Posts: 1
Posted: Sat, 2013-11-30 04:02

Dear Dave,

I tried to use Adreno Profiler 3.5 for Nexus 4, but got no luck. Profiler can connect to my app, but neither Grapher nor Scrubber can get any results.

After reading your post, I have several questions:

  1. 1. What does "apk profiling" mean? Are there any other kinds of OpenCL profiling supported on Nexus 4?
  2. 2. Since half a year has passed after you posted this info, has the Nexus 4 supporting status changed now?
  3. 3. Does Adreno Profiler get profiling info from hardware performance counters integrated in the GPU? If so, can i get these info manually without the help of Adreno Profiler?
  4.  

It would be highly appreciated if you can give any hints or suggestions. Any hardware/software setup can be provided if you need.

Thanks in advance.

  • Up0
  • Down0
or Register

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.