element-hq / element-hq/element-android
Call waiting / Incoming call from another user while first call is still ongoing/active: vibration doesn't end
- Dominant language
- Kotlin
- Stars
- 3.7k
- Forks
- 917
- PR merge metrics
- No merged PRs in 30d
Description
### Steps to reproduce
1. Put your device in vibrate mode.
2. Start a voice call with a user.
3. Have another user call you while the first call is ongoing.
4. The call banner shows up for the second call, and the device starts vibrating.
5. Rejecting the new call doesn't stop it. The device keeps vibrating.
6. The way to stop the vibration is to end the ongoing call, _in addition_ to rejecting the incoming call or having the other user cancel it.
Bonus: If you end the ongoing call instead of the other user, the proximity sensor stays active until the app is force-closed.
This is fully reproducible.
The app behaves normally if the device is set to silent mode or ringing mode. This bug only happens for vibrate mode.
### Outcome
#### What did you expect?
- Vibration should end when the new call is rejected.
- The proximity sensor bug should not occur.
#### What happened instead?
- The device keeps vibrating.
- The proximity sensor bug (which had been fixed earlier) shows up if you end the ongoing call, instead of the other user.
### Your phone model
_No response_
### Operating system version
_No response_
### Application version and app store
1.4.11 (F-Droid)
### Homeserver
_No response_
### Will you send logs?
No
Contributor guide
Assessment
This issue has not been assessed yet.