lightdot
commented
5 years ago I see this happen regularly in the past days, on several Android devices.
After a call is placed, it can be manually terminated by the calling party or left to time out, but the device being called continues to ring endlessly.
On one occasion, a phone actually vibrated for several hours before being discovered.
I trobleshoot briefly and it seems that a phone needs to be unlocked, then the ringing stops.
Some kind of a deep sleep issue? Perhaps the Riot.im client wakes up to start to ring but gets suspended again before being able to terminate the call?
Perhaps something in my environment contributes? In my case, two accounts are involved. The first one is used on an Android phone only. The second is simultaneously used on an Android phone and with a desktop linux client.
Both phones ring endlessly on occasions. Sometimes the call gets answered on a desktop client, but the phone with this same account continues to ring.
Devices and clients:
A) Samsung Note8, Android 9, stock Google Services enabled Riot.im 0.9.3 (G-f1d310d84) from Google Play
B1) LG G2, AOSP Extended (Android 9), OpenGApps Nano Riot.im 0.9.3 (G-f1d310d84) from Google Play via YALP Store B2) Riot.im Desktop 1.3.2-1 on Arch Linux
Using matrix.org server.
My wife placed a call to me at 25 minutes past the hour. Because I didn't answer, she hung up about a minute later.
I didn't answer because I left the phone in the kids' room, after they had fallen asleep.
I just noticed the phone ringing in the kids' room, 40 minutes past the hour. Presumably it had been ringing for 15 minutes, despite my wife having had hung up already.
I was able to accept the call, but obviously, there was no call anymore.
This sounds a bit like #841 and #1613, but these have been fixed. The issue I am reporting exists with Riot-Android from FDroid version 0.8.22 (F-59e927c79).