Tagged: EGL_BAD_SURFACE libEGL
Viewing 17 posts - 1 through 17 (of 17 total)
April 9, 2018 at 6:28 am
Is there any idea about the reasons of these EGL_BAD_SURFACE errors and possible solutions ? The errors are randomly observed. I can observe them in the reference Android app too.
1- flironeexampleapplication E/libEGL: eglQuerySurface:714 error 300d (EGL_BAD_SURFACE)
2- flironeexampleapplication E/libEGL: eglMakeCurrent:945 error 300d (EGL_BAD_SURFACE)
April 9, 2018 at 10:52 am
Hello Infrared Developer,
Would you please tell us what phone and FLIR One you are using?
April 10, 2018 at 8:17 am
I observe the problem with Samsung SM-T810 Tablet PC, Android 5.0.2, API 21 device. Error rate is high with FLIR ONE GEN2 and relatively lower with FLIR ONE GEN3. (I read about similar problems in big screen resolution but I am not sure)
- This reply was modified 1 year, 7 months ago by Devrim.
April 10, 2018 at 9:12 am
Hi Infrared Developer,
Thank you for providing that information. that particular device isn’t currently on the list of Android devices we’ve tested and confirmed to be compatible with the FLIR ONE. We are in the process of testing additional devices, and in the meantime we recommend that you use one of those currently on the compatibility list:
It is very likely that there is a tablet GPU incompatibility with the FLIR One.
Do you have any of the devices listed above?
Please let us know if you have any other questions.
April 10, 2018 at 9:26 am
Thank you Dominique. I can especially go on development with Samsung Galaxy S6 edge+ SM-G928I specs – SamMobile. The rate is very low with Gen 3.
Anyway, could you tell me the reasoning of the EGL_BAD_SURFACE type errors ? Could it be a workaround ?
April 13, 2018 at 2:32 pm
Unfortunately we do not currently have a workaround.
We are continuing to work on adding to our compatibility list
April 17, 2018 at 10:59 pm
Dominique, thank you for your comments.
Anohter point is that the official FLIR ONE application is running very robust on Samsung SM-T810 Tablet PC device. I think, the official app already has a workaround in it. Could you comment on this ?
April 18, 2018 at 4:31 amParticipant
I’ve got the same problem on CATS60. The same problem is FlirOne example application. GLSurfaceView instance lost EGL context. There is interesting if GLSurfaceView OnPause is not used in app. lifcycle, GLSurfaceView works correctly after re-enter screen off via power button.
April 19, 2018 at 10:29 am
Hi Peter and Devrim,
We are continuing to look into this. We will keep you posted on the progress.
June 21, 2018 at 2:03 am
Could be that the EGL context isn’t set up right. Are you missing a makeCurrent() somewhere? If you’re running this in the UI thread you may need to make the EGL context current more often, as the UI thread may be using GLES for its own rendering.
- This reply was modified 1 year, 5 months ago by Allison.
June 22, 2018 at 8:54 am
Could you make your comment more clear please ?
December 18, 2018 at 9:44 pmParticipant
I have the same problem when my app goes to background and then resumed. Dominique you speak about compatibilily but the official Flir ONE app, from the playstore, works perfectly in the two devices that i tested, that these devices are not in the compatibilty list that you share, and the sample application that comes with the SDK fails too when apply the previous process. I you are able to share the source code of that app i think that will be better.
Samsung Galaxy S6: SM-G920P OS: Android 7.0
KYOCERA: E6820TM OS: 6.0.1
Flir One Gen 3 for android devices.
December 28, 2018 at 12:40 pmModerator
Unfortunately, we cannot share the source code for the app. Additionally, we generally see GLSurface issues like EGL_BAD_SRFACE because of how some phone’s GPU’s handle the GLSurface. I can suggest looking into these solutions https://developer.flir.com/forums/topic/recover-the-device-connection/
If the issue persist past those solutions, I can escalate the issue and see if we can find a different solution for you.
December 29, 2018 at 12:33 amParticipant
I understand the thing with the source code, the thing that i dont understand is why the app that comes with the SDK didn’t work and the one in the play store works fine, i think that the sample app sould be fixed. Don’t you think so?
January 4, 2019 at 1:48 amParticipant
What are the solutions for this issue?
January 16, 2019 at 6:07 amParticipant
Have there been any improvements in this issue?
September 4, 2019 at 6:07 amParticipant
The problem persists. Any solution for that?
Viewing 17 posts - 1 through 17 (of 17 total)
You must be logged in to reply to this topic.