Dragon Board 410C - Chromium update for WebRTC

Hello,

The Version of the chromium browser package that is installed on Linaro Debian 16.04 is 47.0.2526.16.

I found that chronium is downgraded from V49 to V47.(http://www.96boards.org/forums/topic/debian-chrome-browser/)

But WebRTC is not working on that chronium version 47.
Is there any solution to upgrade to latest version of chronium?

Hi,

I’ll spin a chromium v50 build later this week. However, the last I tried, webrtc doesn’t work with newer builds either.

Hello, thank you for your reply.

I’ve tested the chromium version 49.0.2623, but remote stream is not working. (Camera interface is available but just black screen)
Does chromium v50 what you tested has same issue?

Is there any plan to support this issue?

Best regards, Thank you.

Is there any problem with using SRTP for WebRTC?
I’ve installed latest srtp packges. (Debian -- Error)
But has same issue with below chromium logs.

[51:62:0504/071416:ERROR:srtpfilter.cc(721)] Failed to init SRTP, err=5
[51:62:0504/071416:ERROR:srtpfilter.cc(721)] Failed to init SRTP, err=2
[51:62:0504/071416:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071417:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071418:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071419:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071419:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071420:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071421:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071422:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071423:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071423:ERROR:stunport.cc(90)] Binding request timed out from 192.168.43.13:44834 (wlan0)
[51:62:0504/071424:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071425:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071426:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071426:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071427:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071427:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071428:ERROR:channel.cc(579)] Can’t send outgoing RTCP packet when SRTP is inactive and crypto is required
[51:62:0504/071433:ERROR:stunport.cc(90)] Binding request timed out from 192.168.43.13:44834 (wlan0)
[51:62:0504/071442:ERROR:stunport.cc(90)] Binding request timed out from 192.168.43.13:44834 (wlan0)

If you use ‘chromium --no-sandbox’, remote streaming is temporarily working.

and here is a bug-fix for it.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=770659
https://bugzilla.mozilla.org/attachment.cgi?id=822066&action=diff

Could you include a above patch for updating of chronium v50 in linaro-debian?