You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are making a small but significant change in Element Call. With this EC release, we will be using the multi-SFU approach for our video and voice calls.
The big advantage is that it mitigates any negotiation over which SFU users in a call connect to. Instead, everyone connects to the SFU associated with their homeserver. No negotiation required. If you want to subscribe to a stream from someone on a different homeserver, Element Call will connect to that SFU in subscribe-only mode. You still have the option to switch back to legacy mode (negotiate on one SFU) using the developer settings tab.
EC has been compatible with this mode for 6 months already, so the whole ecosystem should be updated by now and this should not lead to any incompatibilities.
Of course, this requires every call participant to have an SFU associated with their homeserver if they want to participate in a session. Since we already have checks in place so only users with an SFU can join a call, this should not make a difference for anyone already on the latest versions.
✨ Features
Default to compatibilty mode (multi sfu) - non breaking, as multi-sfu is compatible with all versions younger 6 month by @toger5 in #4066
🙌 Improvements
Move ringing status indicator to header on mobile by @robintown in #4046
Invert the colors of the speaker toggle button by @robintown in #4060
Show the subtitle of the app bar on small screens by @robintown in #4061
📱 Scan the QR code below to install the build (arm64 only) for this PR.
If you can't scan the QR code you can install the build via this link: https://i.diawi.com/WQ4Bvm
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.20.3→0.21.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
element-hq/element-call (io.element.android:element-call-embedded)
v0.21.0What's Changed
We are making a small but significant change in Element Call. With this EC release, we will be using the multi-SFU approach for our video and voice calls.
The big advantage is that it mitigates any negotiation over which SFU users in a call connect to. Instead, everyone connects to the SFU associated with their homeserver. No negotiation required. If you want to subscribe to a stream from someone on a different homeserver, Element Call will connect to that SFU in subscribe-only mode. You still have the option to switch back to legacy mode (negotiate on one SFU) using the developer settings tab.
EC has been compatible with this mode for 6 months already, so the whole ecosystem should be updated by now and this should not lead to any incompatibilities.
Of course, this requires every call participant to have an SFU associated with their homeserver if they want to participate in a session. Since we already have checks in place so only users with an SFU can join a call, this should not make a difference for anyone already on the latest versions.
✨ Features
🙌 Improvements
🐛 Bugfixes
💾 Developer Experience
👒 Dependencies
Full Changelog: element-hq/element-call@v0.20.3...v0.21.0
Docker full package
Element Call is available as a Docker image from the GitHub Container Registry.
The image provides a full build of Element Call that can be used both in standalone and as a widget (on a remote URL).
Embedded packages
This release includes the following embedded packages that allow Element Call to be used as an embedded widget
within another application.
NPM
Android AAR
SwiftPM
Docker full package
Element Call is available as a Docker image from the GitHub Container Registry.
The image provides a full build of Element Call that can be used both in standalone and as a widget (on a remote URL).
Embedded packages
This release includes the following embedded packages that allow Element Call to be used as an embedded widget
within another application.
NPM
Android AAR
SwiftPM
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.