All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=652596

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1Y60owkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgtezwoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1aWiuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1b2FpQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1YnaqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1dygrAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICglcOwtgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgteilugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1a6jswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg1du9vAoM


Bot(s) for this bug's original alert(s):

webrtc-android-tests-nexus5
webrtc-android-tests-nexus72
webrtc-android-tests-nexus9

Looks ok, but I don't know why the stats would change with that CL. It basically means we're ramping up to higher bitrates at the same time as before, but by sending less padding and more media.

Per, any clue why that would be?

Beats me. In is only Android it looks like.
https://chromeperf.appspot.com/report?sid=8a8ade726c9e016d80bc2dd720022c5a149ffd7691815c66b1a80e1d41f5d9b7

Closing since it have only happened on Android and is now closer to the performance on Win.