Skip to content

[pull] master from jitsi:master - #834

Merged
pull[bot] merged 1 commit into
code:masterfrom
jitsi:master
Aug 18, 2026
Merged

[pull] master from jitsi:master#834
pull[bot] merged 1 commit into
code:masterfrom
jitsi:master

Conversation

@pull

@pull pull Bot commented Aug 18, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

…open (#17724)

WebRTC's NetworkMonitorAutoDetect already calls
ConnectivityManager#requestNetwork for TRANSPORT_CELLULAR on its own, to keep
the mobile data interface up even while wifi is the active network. That call
needs CHANGE_NETWORK_STATE, and jitsi-meet never declared it, so the call has
been throwing SecurityException, caught and logged by WebRTC, ever since.

Without a cellular interface up, WebRTC gathers only one ICE candidate for a
JVB session (whichever transport wifi/cellular happens to be active), so only
one candidate pair ever forms. A bridge running keep-alive-strategy =
all_succeeded has nothing to fail over to, and losing wifi means recovering
from a torn-down session rather than switching to an already-established
path.

CHANGE_NETWORK_STATE is protection level normal, so it is granted at install
time with no runtime prompt and no user-facing change.

Measured on a Pixel against a single bridge, wifi disabled mid-call:

  before   17.35 s of no media, recovered by a full session restart
  after     ~1.2 s of no media, recovered by WebRTC's own pair switch

Reconnecting to wifi measured no gap above 0.3 s.
@pull pull Bot locked and limited conversation to collaborators Aug 18, 2026
@pull pull Bot added the ⤵️ pull label Aug 18, 2026
@pull
pull Bot merged commit aa449eb into code:master Aug 18, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant