eglswapbuffer on two threads

40
January 19, 2019, at 8:20 PM

I find an app with two threads submitting eglswapbuffer commands.
Thread1 does the heavy image processing job, and the original image is transferred from another thread, taken from the camera. After all the processing, it submits a eglswapbuffer.
Thread2 draws the UI part. I can also see the eglswapbuffer commands.
Since thread1 is limitted by camera frequency, which is 30Hz. And the UI part is 60Hz. I used to think eglswapbuffer is the line accross two frames. But I don't think I can assume this for this case. I remember a page says that eglswapbuffer is just a queuebuffer operation. So how does android work on this situation? What happends when a vsync comes? Combine the thread1 content and the thread2 content? Since thread1 has lower update frequency, so only update the thread2 content sometimes? What does drop frame means in this situation? How does CPU or GPU schedule the work? Because these two threads both take GPU time, if GPU keeps busy working on thread1 for a period, then update for thread2 will be delayed, vice versa?

READ ALSO
(Off-topic) Can I use Xmpp server quickblox for chat application which works locally?

(Off-topic) Can I use Xmpp server quickblox for chat application which works locally?

I have tried to make chat application which works by firebaseAnd everything works well but now I want to make chat application which works on local server

17
Forcing a DialogFragment to not recreate after orientation change

Forcing a DialogFragment to not recreate after orientation change

When I'm changing the orientation of my app with a visible DialogFragment opened from my Activity, the dialog will be recreatedHow can I forcefully dismiss it?

12
push notifications set large icon when sending from server

push notifications set large icon when sending from server

I'm sending push notifications from server with PHP like so:

45
Resources Android not found

Resources Android not found

These resources are not found now (maybe since the last SDK upgrade):

34