Confirmed users
158
edits
B2G/Wifi Display: Difference between revisions
Jump to navigation
Jump to search
→Approach 2 (Layer-based)
| Line 69: | Line 69: | ||
[[File:Miracast pipeline.png|1000px]] | [[File:Miracast pipeline.png|1000px]] | ||
[[File:VirtualDisplayRender.png|1000px]] | |||
We tested on flame v188 and nexus 4 KK. Statistics showed the fps can still reach 60 on nexus 4 but less than 20 on flame. After profiling each stage of the frame processing, we found that eglSwapBuffer took too much time in the virtual display run. This might be due to the poor codec power on flame. Take Frame 2' as the example. Even if Frame 2' is complete before the next scheduled Render() task, we might still need to wait for the encoder to consume the frame and cause the compositor thread blocked. | We tested on flame v188 and nexus 4 KK. Statistics showed the fps can still reach 60 on nexus 4 but less than 20 on flame. After profiling each stage of the frame processing, we found that eglSwapBuffer took too much time in the virtual display run. This might be due to the poor codec power on flame. Take Frame 2' as the example. Even if Frame 2' is complete before the next scheduled Render() task, we might still need to wait for the encoder to consume the frame and cause the compositor thread blocked. | ||