Android AppRTC - How to avoid 'No surface to draw on' ?

[ML]

Hello All,

I'm using Android AppRTC to make call with https://appr.tc. Once the app is not running in foreground (e.g. navigate back to home scree), a thousand of log is shown as follows:

01-06 18:41:58.861 9592-9631/org.appspot.apprtc I/SurfaceViewRenderer: SurfaceViewRenderer: remote_video_view: No surface to draw on

01-06 18:41:58.909 9592-9631/org.appspot.apprtc I/SurfaceViewRenderer: SurfaceViewRenderer: remote_video_view: No surface to draw on

01-06 18:41:58.962 9592-9631/org.appspot.apprtc I/SurfaceViewRenderer: SurfaceViewRenderer: remote_video_view: No surface to draw on

01-06 18:41:59.008 9592-9631/org.appspot.apprtc I/SurfaceViewRenderer: SurfaceViewRenderer: remote_video_view: No surface to draw on

01-06 18:41:59.058 9592-9631/org.appspot.apprtc I/SurfaceViewRenderer: SurfaceViewRenderer: remote_video_view: No surface to draw on

01-06 18:41:59.114 9592-9631/org.appspot.apprtc I/SurfaceViewRenderer: SurfaceViewRenderer: remote_video_view: No surface to draw on

01-06 18:41:59.159 9592-9631/org.appspot.apprtc I/SurfaceViewRenderer: SurfaceViewRenderer: remote_video_view: No surface to draw on 

I'm facing the exact same problem when developing my own application. 

I tried to call release() but it doesn't help, which shows another log telling me that "Dropping frame - SurfaceViewRenderer not initialized or already released."

What should I do so that I can get rid of these logs when the app is running in background?  

Thanks

[alireza pir]

Same Problem...

[Asrar Ul Haque]

Have you found a solution yet? I'm also facing the same problem and want to know whether this problem can be ignored.

[Ray Hunter]

I ran into this issue when the surface view was not visible before frames were received in the onFirstFrameRendered method. Once I had the view visible, then this error went away.

[vadym...@gmail.com]

Is there any option to not drop frames when surface view invisible or gone?

вторник, 19 мая 2020 г. в 09:50:11 UTC+3, Ray Hunter: