answering videocalls on callkit when the screen is locked often doesn't work

[ara4n]

if you hit the video button to try to turn on the camera, it sits there stuck in 'connecting' state after you unlock the screen

[SylvainMorisse]

I'd be ready to work on this if anyone could share information i'd be happy to share

[farialima]

Note that the issue happens also when the app is in the background, or hasn't been started yet - it's not directly related to locked screen.

I'm trying to investigate a little...

[farialima]

comparing the logs of when it works and when it doesn't, and grepping for "MXJingleCallStackCall", I shows this potentially interesting difference:

• when it works (app already in for foreground):

(...)
Riot[3642:355100] [MXJingleCallStackCall] didGenerateIceCandidate: RTCIceCandidate:
Riot[3642:355100] [MXJingleCallStackCall] didChangeIceGatheringState: 2
Riot[3642:355100] [MXJingleCallStackCall] didChangeIceConnectionState: 2
Riot[3642:355100] [MXJingleCallStackCall] didChangeIceConnectionState: 5
Riot[3642:355100] [MXJingleCallStackCall] didChangeIceConnectionState: 6
Riot[3642:355100] [MXJingleCallStackCall] didChangeSignalingState: 5

• when it doesn't work (app in background):

(...)
Riot[3642:355100] [MXJingleCallStackCall] didGenerateIceCandidate: RTCIceCandidate:
Riot[3642:355100] [MXJingleCallStackCall] didChangeIceConnectionState: 6
Riot[3642:355100] [MXJingleCallStackCall] didChangeIceGatheringState: 2
Riot[3642:355100] [MXJingleCallStackCall] didChangeSignalingState: 5

which causes then the MXCallState to go from MXCallStateConnecting to MXCallStateEnded (when failing, the log shows [MXCall] setState. old: 6. New: 8) instead of MXCallStateConnected (when working OK, the log show [MXCall] setState. old: 6. New: 7)

Will look at it more but if anyone has an idea...

[farialima]

Per discussion with @manuroe , most likely the first step toward a fix would be to upgrade the webRTC libraries that are very old. See #1483 (comment) and subsequent comments

[Tokodomo]

Per discussion with @manuroe , most likely the first step toward a fix would be to upgrade the webRTC libraries that are very old. See #1483 (comment) and subsequent comments

^ Sadly, upgrading to the latest version (v0.8.6) doesn't seem to solve the issue. This is really annoying and a show-stopper in every way.