Our application (Unity 3D game) always crashes on Nexus 7(2nd Generation) in random places with the absolutely same reason after some minutes of normal work (see log):
W/Adreno200-GSL(19088): <gsl_ldd_control:397>: ioctl fd 36 code 0x400c0907 (IOCTL_KGSL_DEVICE_WAITTIMESTAMP_CTXTID) failed: errno 35 Resource deadlock would occur
W/Adreno200-GSL(19088): <log_gpu_snapshot:314>: panel.gpuSnapshotPath is not set.not generating user snapshot
W/Adreno200-EGLSUB(19088): <updater_thread:454>: waitFunc failed
W/Adreno200-GSL(19088): <gsl_ldd_control:397>: ioctl fd 36 code 0xc02c093d (unknown) failed: errno 35 Resource deadlock would occur
W/Adreno200-GSL(19088): <log_gpu_snapshot:314>: panel.gpuSnapshotPath is not set.not generating user snapshot
W/Adreno200-GSL(19088): <gsl_ldd_control:397>: ioctl fd 36 code 0xc02c093d (unknown) failed: errno 35 Resource deadlock would occur
W/Adreno200-GSL(19088): <log_gpu_snapshot:314>: panel.gpuSnapshotPath is not set.not generating user snapshot
W/Adreno200-GSL(19088): <gsl_ldd_control:397>: ioctl fd 36 code 0xc02c093d (unknown) failed: errno 35 Resource deadlock would occur
W/Adreno200-GSL(19088): <log_gpu_snapshot:314>: panel.gpuSnapshotPath is not set.not generating user snapshot
E/Adreno200-GSL(19088): <os_exit:1632>: Exiting the process com.**.****.********** from function qeglDrvAPI_eglSwapBuffers and line 3516
I/ActivityManager( 526): Process com.**.****.********** (pid 19088) has died.
Crash log is always the same, except the number after words "ioctl fd" (it may be 36, 39, 40, etc).
We thought that this might have something to do with the GPU (Adreno 320) in the 2nd gen Nexus 7, but other Adreno 320 (Galaxy S4, Nexus 4) appear to be working fine.
Can you provide any hint for us or at least explain this log? Which reason can be possible for this crash?
About tablet:
Android 4.3
Kernel version 3.4.0-g6537a16
Build number JSS15Q
Sorry to hear that you're experiencing a crash on the Nexus 7.
Would you be able to provide us with an apk that we can use to duplicate the problem here?
thanks..
any upfdate on this as many people want to be able to use coopers efforts in the future etc and all the other unresolved bug reports such as outlines here
https://dolphin-emu.org/blog/2013/09/26/dolphin-emulator-and-opengl-drivers-hall-fameshame/
https://dolphin-emu.org/m/user/blog/gl-bugs/20130917_223443.jpg
I'm not sure of the status of this particular issue, but the issues mentioned in the blog have all been fixed, and updated binary drivers for Nexus devices will be posted here within the next couple of weeks.
Is there any more information on this issue, we have a similar problem with our game closing (no program has stopped mesage - just boom and gone, sometimes it even hard resets the device). The main device we have tested on that cause the problem is a 2013 edition of the nexus 7. I have tracked through the code and it seems to be related to VAO usage, given how it dies im at a loss as to how to best track this issue.
Any advice would be great, we are ment to be shipping shortly, i can just disable the VAO but dont really want to have to do this
Adrian
Any information on the text that Dave said that development drivers will be coming to nexus devices? It has been much longer than a couple of weeks at this point.
The intention was to push out an update on December 18th, but there were performance regressions that manifested at the last minute that delayed the release. Due to the holidays, many key people have been out, so I'm not sure of the current status, but there IS someone currently dedicated to supporting development drivers now, so there will an update soon.
Can we have an eta for us Nexus users? we've had this problem 3 months now since 4.4, just clarify has this been fixed with the v66 drivers or will us Nexus users be getting something newer than Samsung's & Asus's last updates?
A developer release of our driver for Nexus devices was posted back on the 24th: https://developer.qualcomm.com/forum/qdevnet-forums/mobile-technologies/...
Nexus 5 only though? what about the Nexus 7 flo & deb?
The currently posted driver *might* support Nexus 7, but it hasn't been tested on it. There is an upcoming release (probably next week) that will be tested on Nexus 7, though.
The current Nexus 5 release unfortunately doesn't support Nexus 7, but the Nexus 7 release is scheduled to be out by the end of this month.
the same the Nexus 5 update? from all reports i've seen the rotation bug remains.
I tried installing UPDATE-adreno-drivers-razor.zip via K0T49H 4.4.2r1 stock system recovery and I get the following
Finding update package
Opening update package
E: footer is wrong
E:signature verfication failed
Installation aborted.
I shouldn't have to unlock the bootloader to install a custom recovery just to apply a driver update, Not when signed driver's are offered by google
https://dl.google.com/dl/android/aosp/qcom-flo-kot49h-f92d75b1.tgz
Unfortunately, we are not able to sign our driver updates with Google's platform key. That's why a recovery image that's willing to install unsigned update packages is required. Although these releases are for developers, they are meant to be installed without the need for an AOSP source tree.