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
During 1:1 calls the physical volume button change the volume of the "in-call" channel, but the app outputs the sound on the media channel.
Outcome
The result is the physical buttons won't control the volume of the call.
When earphones plugged, the buttons actually change the call's volume. Without earphones it does not.
Your phone model
Samsung A55, Pixel 9
Operating system version
Android 15
Application version and app store
Element X v25.04.3 (Github release)
Homeserver
matrix.org
Will you send logs?
Yes
Are you willing to provide a PR?
No
The text was updated successfully, but these errors were encountered:
I am running into the same issue on latest v25.04.3 Github release as well. I thought it was fixed with #4481 as in the release notes, but that doesn't appear to be the case. I'm on a Pixel 8 Pro device. Cc @jmartinesp for visibility
What I found was the volume buttons correctly identify the phone output (at the bottom of the volume bar). But the element-call works on the media output. So no control through the volume buttons.
With bluetooth (earphones) all output goes through that single channel anyway the buttons work.
So the option is to:
Change the volume control button to pick media output when the call is active or
Steps to reproduce
During 1:1 calls the physical volume button change the volume of the "in-call" channel, but the app outputs the sound on the media channel.
Outcome
The result is the physical buttons won't control the volume of the call.
When earphones plugged, the buttons actually change the call's volume. Without earphones it does not.
Your phone model
Samsung A55, Pixel 9
Operating system version
Android 15
Application version and app store
Element X v25.04.3 (Github release)
Homeserver
matrix.org
Will you send logs?
Yes
Are you willing to provide a PR?
No
The text was updated successfully, but these errors were encountered: