Hello,
I am trying to use the Adreno Profiler (v3.3) with a Samsung Galaxy S4. I have installed the following USB drivers : http://developer.samsung.com/android/tools-sdks/Samsung-Andorid-USB-Driver-for-Windows
But when my device is in USB debugging mode, the USB driver fails to recognize my device. Is there something I have missed ? Has anyone succeed using the Adreno Profiler with a Galaxy S4 ?
Thanks
Hi Eric,
Have you succeeded using the profiler with Galaxy S4?
Cheers
Karthik
Same problem here. I'm trying to use Adreno Profiler 3.4.4918.22992 with stock Samsung Galaxy S4 I9505.
Profiler detects the adb but doesn't find any apps to be profiled.
This is high priority for my company, because we try to investigate why our game freezes inside glSwapBuffers() on Adreno 320. The game works fine on other devices such as those based on Adreno 2xx, Tegra 2/3 and SGX 5xx. We are hoping the Profiler will give us some clues what happens and possible workaround.
Unfortunately, after investigation on our part, it looks like the SGS4 shipped with a build on which Adreno Profiler is broken. We've since provided a fix to Samsung, so it'll eventually make it out in an OTA update, but I don't know when that will be (and it probably depends on your carrier).
Thanks for the information!
What other Adreno 320 based devices are known to work with the Adreno Profiler 3.4?
Sony Experia Z? HTC One?
The Nexus 4 definitely works (although you may have to push updated driver binaries from our downloads page), and I've personally used it with an LG Optimus G. I'll see if I can get my hands on the phones you mentioned and verify personally, but I've not heard of any issues with them.
I tested with the HTC One, and Profiler works with it without issues.
Thanks!
I've got some more information. Here's a log from Galaxy S4 (Adreno 320, Android 4.2.2)
07-09 15:47:39.791: I/Adreno200-EGL(5130): <qeglDrvAPI_eglInitialize:265>: EGL 1.4 QUALCOMM build: (CL3544079)
07-09 15:47:39.791: I/Adreno200-EGL(5130): Build Date: 03/28/13 Thu
07-09 15:47:39.791: I/Adreno200-EGL(5130): Local Branch: adreno_20130328
07-09 15:47:39.791: I/Adreno200-EGL(5130): Remote Branch:
07-09 15:47:39.791: I/Adreno200-EGL(5130): Local Patches:
07-09 15:47:39.791: I/Adreno200-EGL(5130): Reconstruct Branch:
*** Here is where our game runs fine for about 100 frames. ***
07-09 15:48:01.973: W/Adreno200-GSL(5130): <gsl_ldd_control:357>: ioctl fd 58 code 0x400c0907 (IOCTL_KGSL_DEVICE_WAITTIMESTAMP_CTXTID) failed: errno 4 Interrupted system call
07-09 15:48:01.973: W/Adreno200-EGLSUB(5130): <updater_thread:444>: waitFunc failed
07-09 15:48:11.272: W/Adreno200-EGLSUB(5130): <updater_thread:449>: native buffer is NULL
07-09 15:48:38.278: W/Adreno200-EGLSUB(5130): <updater_thread:449>: native buffer is NULL
Let me say that our game runs fine on:
- iOS devices
- Android tablets based on Tegra 2&3
- Android devices based on PowerVR
gl functions don't return any errors. The game will freeze inside glSwapBuffers(). By this point I have been systematically removing parts of code but nothing helps. It always hangs inside glSwapBuffers().
I could provide APK if you guys could take a look?
APK: http://www.kulfun.com/cve.apk
When you start the game, it should show a welcome splash screen and a loading bar. It takes about 10 seconds to load. Once loading bar reaches the end, it should switch to a bunch of clouds starting to clear. At this point it usually freezes or terminates the app.
The errors from Adreno driver actually happen some time before the actual freeze/termination. So they might give a clue to what is happening. Sometime there is no error at all, but the game still freezes or terminates.
Here are some more errors:
Hi ,
I was trying to profile simple openCL application with Adreno Profiler on samsung phone, namely S5.
Following requirements were met:
1) APK manifest was modified for permission.
2) PATH variable modified accordingly.
3) Device connected to profiler -Success.
4) Insatnce of ScrubberCL launched.
Problem : CApture button for starting the process is inactive, can't be turned on.
Tried with both one-shot applications and Periodic Applications, but still capture button is inactive.
Has anyone faced the same problem, or know the solution?
Thanks
We haven't been able to duplicate your problem with the S5. What build is on your S5 device?