Hey jkallar@,

Do you have the WebRTC text logs for this call?

Did the artifacts always look like the attached picture, or did you also get some "blocky" distortions?

philipel@:

I don't have the WebRTC logs but I will get them for next time the bug happens

Yes I also got "blocky" distortions;  I will try to make a video next time and attach (upload) that.

sorry  brandtr@, I meant to answer to you also.

I confirmed offline with jkallar@ that these are not the same distortions as the ones caused by https://bugs.chromium.org/p/webrtc/issues/detail?id=7475. He will try to get text logs for the next time this happens.

Both the smaller and the larger video "fields" are moving, so it looks like a renderer bug rather than a decoder bug.

Upgrading to P2, until we know how common this problem is.

Marking as 'assigned' to take it off the triage list (and it looks like we have an owner).

Firstly, I haven't seen this bug again in the last two weeks but anyway document what I've done.


Also an correction: the device stated in the bug description was 'Samsung Galaxy S7' and not 'Samsung Galaxy S7'



I reached an impasse since I couldn't' enable Chrome logging on the Samsung Galaxy S7 device.

Just to clear up: I can only get webrtc logs for Hangout calls, not apprtc calls (where I see the bug). 

Thus, looked at enabling Chrome logs. That is only possible by doing either one of the following two:

1. A device (Samsung Galaxy S7 in this case) has be configured correctly either by:

	1a) A userdebug/eng build (i.e compile your own Chrome mobile app)
	1b) Android itself (you need root access)

2. You need to set Chrome as the debug app in developer settings by doing on Samsung Galaxy S7 device
	 Settings App > Developer options > "Select debug app"


As I'm only a tester, option 1a is not possible and neither option 1b (since I can only root Google Pixel or Nexus devices, not Samsung devices)

Option 2 is also neither possible since the Chrome 'apk' I download and test is a release build and not debuggable. Doing: Settings App > Developer options > "Select debug app", gives 'No apps' on the Samsung Galaxy S7 device


However, one thing.  I have noticed that doing 'adb logcat -s chromium' gives some webrtc ouput (some libjingle info) but not enough if I compare the corresponding output for a Chrome desktop peer to peer call.

Just for your information, I tried to enable logs on the Samsung S7 device by writing chrome flags (--enable-logging --v=1) to the file  /data/local/tmp/chrome-command-line.  Example:

 ./adb_command_line.py -d 9885e65345354b5546 --device-path /data/local/tmp/chrome-command-line  --enable-logging --v=1  

and then restarting the Chrome app.   However, when I do in a new Chrome tab 'chrome://version" I don't see these flags being set.



That's as far I've gotten and I don't think there much else I can do. If anybody has suggestions please feel free to contribute

Ping for triaging.

Still an issue? If not we'll close.

A lot of things have changed since this was last reported, so let's close.