talk-android
talk-android copied to clipboard
nextcloud
Microphone mute state not remembered across reconnects to same call (or in the same conversation)
Steps to reproduce
- Connect to a call
- Mute yourself
- Reconnect to the call
Expected behaviour
Your last used mute/unmute state is remembered and thus you are muted by default here.
Actual behaviour
You have to mute yourself again every time, something you are very likely to do when on mobile.
Device brand and model
Fairphone 5
Android version
14
Nextcloud Talk app version
21.0.1
Nextcloud server version
Latest of cloud.nc
Talk version
No response
Custom Signaling server configured
None
Custom TURN server configured
None
Custom STUN server configured
None
Android logs
No response
Server log
Additional information
No response
As the current situation is expected code wise i changed it to feature. But the scenario makes sense of course.
Is this implemented on iOS? @Ivansss @SystemKeeper ?
I think it depends a bit. How is "reconnect" done here? If it is an automatic reconnect because of a lost connection, the state should be remembered. Also when moving to another room, e.g. breakout room or the new extending 1:1. But if you leave and join again, we don't remember the state.
@SystemKeeper if you are asking about the expectation: It doesn’t matter how one reconnects. On web, device state is remembered even across days and system restarts.
