Hello,
I am sorry with bother this forum with my trouble. Before I posted this issue i really searched web for solution and made several attempts to fix this issue. Unfortunatelly I was not successful. I am developing application for Android using opengl. Last month several devices received Android 5 update and crash-log on google developer console starts filling with errors posted below. I am receiveing all these crashes only from Samsung Galaxy Note 4 with Android 5. I don't have to disposition this device, but one friend on the other side of world was very helpful and we were trying to fix this issue several hours. Without success.
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'Verizon/trltevzw/trltevzw:5.0.1/LRX22C/N910VVRU1BOAF:user/release-keys'
Revision: '12'
ABI: 'arm'
pid: 12798, tid: 13179, name: Thread-27549 >>> app.xyz <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0xbc
r0 00000000 r1 00000000 r2 ad3d1020 r3 ad3d1000
r4 af85d000 r5 aa1aad98 r6 00000000 r7 aa1c97d0
r8 9c89e054 r9 0000000c sl b6f52e7c fp afc3224c
ip aa1aadac sp 9caff9b8 lr aa016788 pc aa087ea6 cpsr 800f1830
backtrace:
#00 pc 00112ea6 /system/vendor/lib/egl/libGLESv2_adreno.so (EglContext::UnmakeCurrentEsx()+53)
#01 pc 00112f19 /system/vendor/lib/egl/libGLESv2_adreno.so (EglContext::UnmakeCurrent()+12)
#02 pc 0011a30f /system/vendor/lib/egl/libGLESv2_adreno.so (EglThreadState::UnmakeCurrent()+14)
#03 pc 0011366f /system/vendor/lib/egl/libGLESv2_adreno.so (EglThreadList::SearchCurrentDisplayAndUnmake(EglDisplay*)+62)
#04 pc 00114291 /system/vendor/lib/egl/libGLESv2_adreno.so (EglDisplay::Terminate()+56)
#05 pc 0011438d /system/vendor/lib/egl/libGLESv2_adreno.so (EglDisplay::Destroy()+4)
#06 pc 00114713 /system/vendor/lib/egl/libGLESv2_adreno.so (EglDisplayList::Destroy()+30)
#07 pc 00114773 /system/vendor/lib/egl/libGLESv2_adreno.so (EglDisplay::DestroyStaticListsAndStaticMutex()+26)
#08 pc 001693a9 /system/vendor/lib/egl/libGLESv2_adreno.so (EsxMemFreeManager::~EsxMemFreeManager()+72)
#09 pc 001693bd /system/vendor/lib/egl/libGLESv2_adreno.so (EsxMemFreeManager::Release()+16)
#10 pc 001693dd /system/vendor/lib/egl/libGLESv2_adreno.so (EsxMemFreeManagerDestructor::~EsxMemFreeManagerDestructor()+4)
#11 pc 00035a89 /system/lib/libc.so (__cxa_finalize+132)
#12 pc 0000f04f /system/lib/libc.so (exit+6)
#13 pc 000454f0 /data/app/app.xyz-1/lib/arm/libxyz.so (myfunction()+320)
#14 pc 000468b4 /data/app/app.xyz-1/lib/arm/libxyz.so (my_native_function+80)
#15 pc 00045e37 /data/dalvik-cache/arm/data@app@[email protected]@classes.dex
This issue happens always when application quits. Application starts and works fine, without issues and long time. When user hits quit button then everything goes fine. From output log I see that all exiting steps were processed. Seems like application quits fine, but after that appears "Unfortunately application has stopped" and user can send report (see above).
Looking into log I see that problem may be with releasing resources, so I made function in which I release all opengl textures and I added GLSurfaceView.onPause at the end. Nothing helped.
I will be very happy for any idea.
Thank you
Hi Anton,
Not sure if the issues are related, but our app also started encountering render problems in Note4 when users upgraded their OS from 4.4 to 5.*,
This is the thread with our issue described
https://developer.qualcomm.com/forum/qdn-forums/maximize-hardware/mobile...
Hello,
We can confirm this issue, at least in these devices (all running Android 5.0):
Galaxy S5 LTE-A (kccat6) Galaxy Note4 (trlteatt) Galaxy Note Edge (tblteatt) Galaxy Note Edge (tblte) Galaxy Note4 (trltecan) Galaxy Note4 (trltevzw) Galaxy Note4 (trltespr) Galaxy Note4 (trlte) Galaxy Note4 (trltetmo)A possible workaround is not using "exit()" in your NDK code (if it is really possible).
Regards.
It is possible that this issue is related to https://developer.qualcomm.com/forum/qdn-forums/maximize-hardware/mobile-gaming-graphics-adreno/28752
in which case the issue is likely fixed in our latest driver update that should be found in Android 5.1.1. However note a few caveats:
1. We have no control over when / if the OEM customers (in this case "Samsung") will pull this or any fix into the updates for their specific devices [Galaxy S5 LTE-A (kccat6) Galaxy Note4 (trlteatt) Galaxy Note Edge (tblteatt) Galaxy Note Edge (tblte) Galaxy Note4 (trltecan) Galaxy Note4 (trltevzw) Galaxy Note4 (trltespr) Galaxy Note4 (trlte) Galaxy Note4 (trltetmo)] and when / if they will push the update out to their devices. So it is entirely possible that even after an update of a device to 5.1.1 it might contain the issue still.
2. It is not possible to tell for certain whether this particular issue is due to the same problem as in issue #28752 without an APK to test internally. So to be certain it would be ideal if you could provide an APK to us that demonstrates this issue.
Thanks for the report.
Yes, I use "exit" in ndk to quit application. It is really necessary.
If someone from team write on my email I will provide apk immediatelly.
Hello Anton.
I was able to reproduce the issue using the "Magic DOSBox" from the Play Store running on an Android 5.1.1 Snapdragon device.
The issue appears unrelated to issue #28752.
We'll keep you informed of any progress regarding this issue.
Hello Anton.
I just verified that the issue appears fixed on our internal latest driver build from today (June 10 2015) for Magic DOS Box.
This means that whenever the fix makes it into the Samsung devices, either via OTA Google update or other means, the issue should be fixed for your app.
Thank you very much for good work guys. Have a nice day.
Hello,
I'm from CANADA.
My phone: Galaxy note 4 running 5.01. (Bell provider).
After upgrading from 4.4 (Kitkat) to 5.0 and 5.0.1 I keep receiving this annoying bug (error code
trltecan-user 5.0.1 LRX22C N910W8VLU1BOE2 release-keys
I can still use the phone normaly but this bug is so annoying (not knowing what's behind this problem).
I saw some informations that this could be related to the Qualcomm video driver (rendering problem) (that is suppose to be fix in 5.1). But this 5.1 upgrade is still not available....
Any idea.
Many thanks.
Serge
Montreal