I couldn't find an acceptable workaround. It seemed to be a threading issue
fighting with OpenGL
On Apr 8, 2014 6:15 AM, "Voinea Adrian" wrote:
> I have the exact same question.
> Did you manage to find any workaround for this?
> On Thursday, March 6, 2014 12:54:53 AM UTC+2, David Seabolt wrote:
>> When I try to lock the window I get an error -22, and then I receive
>> output: E/BufferQueue( 180): [SurfaceView] connect: already connected
>> (cur=1, req=2)
>> I'm attempting to lock the surface of a subclassed GLSurfaceView, and
>> attempting to draw to that surface without going through EGL, in the
>> that I can just blit a loading screen texture while the EGL thread is
>> loading textures.
>> Is such a thing even possible?
> You received this message because you are subscribed to a topic in the
> Google Groups "android-ndk" group.
> To unsubscribe from this topic, visit
> To unsubscribe from this group and all its topics, send an email to
> [email protected]
> To post to this group, send email to [email protected]
> Visit this group at http://groups.google.com/group/android-ndk.
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected]
To post to this group, send email to [email protected]
Visit this group at http://groups.google.com/group/android-ndk.
For more options, visit https://groups.google.com/d/optout.