Bugzilla

### Beta/Release Uplift Approval Request
* **User impact if declined**: Video calls on Android are likely to freeze for remote peers at some point because we do not send frames for certain resolutions, which could be set by the site or by libwebrtc under the hood.
* **Is this code covered by automated tests?**: Yes
* **Has the fix been verified in Nightly?**: Yes
* **Needs manual test from QE?**: Yes
* **If yes, steps to reproduce**: see comment 6
* **List of other uplifts needed**: None
* **Risk to taking this patch**: Low
* **Why is the change risky/not risky? (and alternatives if risky)**: This bug adds a bit of plumbing and some logic to adjust the send resolution. gtest coverage of the resolution adjustment exists. mochitest coverage of both pieces exist. No lifetime/timing changes. Multiple threads access the relevant data but it is const so no real concern here.
* **String changes made/needed**: 
* **Is Android affected?**: Yes

### Beta/Release Uplift Approval Request
* **User impact if declined**: Video calls on Android (webrtc) are likely to freeze for remote peers at some point because we do not send frames for certain resolutions for the default codec on Android. The affected resolutions could be set by the site or by libwebrtc under the hood.
* **Is this code covered by automated tests?**: Yes
* **Has the fix been verified in Nightly?**: Yes
* **Needs manual test from QE?**: Yes
* **If yes, steps to reproduce**: see comment 6
* **List of other uplifts needed**: None
* **Risk to taking this patch**: Low
* **Why is the change risky/not risky? (and alternatives if risky)**: This bug adds a bit of plumbing and some logic to adjust the send resolution. gtest coverage of the resolution adjustment exists. mochitest coverage of both pieces exist. No lifetime/timing changes. Multiple threads access the relevant data but it is const so no real concern here.
* **String changes made/needed**: 
* **Is Android affected?**: Yes