Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sometimes call stuck with no buttons or a way to hang up #4144

Closed
532910 opened this issue Oct 2, 2021 · 6 comments
Closed

Sometimes call stuck with no buttons or a way to hang up #4144

532910 opened this issue Oct 2, 2021 · 6 comments
Assignees
Labels
A-VoIP O-Occasional Affects or can be seen by some users regularly or most users rarely S-Critical Prevents work, causes data loss and/or has no workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems

Comments

@532910
Copy link
Contributor

532910 commented Oct 2, 2021

Steps to reproduce

I'm not sure this is always-reproducible.

  1. Start a voice call (to ios, but not sure)
  2. Answer a call on ios
  3. Hangup a call on ios -- android will show the call is ended
  4. Start a new call:
    image
    image

What happened?

What did you expect?

What happened?

Your phone model

No response

Operating system version

Android 11

Application version and app store

The latest beta from GPlay

Homeserver

No response

Have you submitted a rageshake?

Yes

@532910 532910 added the T-Defect Something isn't working: bugs, crashes, hangs and other reported problems label Oct 2, 2021
@532910
Copy link
Contributor Author

532910 commented Oct 2, 2021

This is a very annoying issue, as it's not trivial how to kill this activity, and phone reboot is the only way for most people.

@bmarty bmarty added the A-VoIP label Oct 4, 2021
@kittykat
Copy link
Contributor

@532910 which version of Element are you using?

@kittykat kittykat added O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Critical Prevents work, causes data loss and/or has no workaround X-Needs-Info labels Nov 17, 2021
@532910
Copy link
Contributor Author

532910 commented Nov 17, 2021

Sorry for forgetting to specify it, I'm on GPlay Beta channel, thus it was the latest at the time the issue was opened.
I'll try to reproduce it as soon as v1.3.8 becomes available.

@kittykat
Copy link
Contributor

kittykat commented Nov 24, 2021

There are no reliable reproduction steps, it just happens sometimes.

I got it on 1.3.8:
143217876-40ae4658-3cd0-4440-b93f-b748c9fae7a9

@kittykat kittykat added O-Occasional Affects or can be seen by some users regularly or most users rarely and removed O-Uncommon Most users are unlikely to come across this or unexpected workflow X-Needs-Info labels Nov 24, 2021
@ouchadam ouchadam self-assigned this Nov 25, 2021
@ouchadam
Copy link
Contributor

ouchadam commented Nov 25, 2021

I'm not entirely sure why this happens yet but the screenshots are showing the call stuck in the Idle state. Element isn't actually ringing at this point.

I can add UI to hang up but will investigate a little more to try and understand why we're getting stuck

EDIT:

from the logs in the rageshake it looks like the internal jitsi media player hits a native error which causes the VOIP connection to shutdown, this is something the jitsi/webrtc sdk would need to fix (might have been fixed with #4504 1.3.9)

org.webrtc.Logging: PeerConnectionFactory: onWorkerThreadReady
org.webrtc.Logging: PeerConnectionFactory: onSignalingThreadReady
org.webrtc.Logging: PeerConnectionFactory: onNetworkThreadReady
MediaPlayerNative: trying to set audio attributes called in state 8
org.webrtc.Logging: EglRenderer: fullscreenRendererQuitting render thread.

Working logs - the renderer starts processing instead of quitting

org.webrtc.Logging: PeerConnectionFactory: onSignalingThreadReady
org.webrtc.Logging: PeerConnectionFactory: onNetworkThreadReady
org.webrtc.Logging: PeerConnectionFactory: onWorkerThreadReady
org.webrtc.Logging: SurfaceViewRenderer: fullscreenRenderer: onMeasure(). New size: 1080x2246

there might be a playback OnError handler we're missing somewhere~

@ouchadam
Copy link
Contributor

(symptoms) fixed in 1.3.9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-VoIP O-Occasional Affects or can be seen by some users regularly or most users rarely S-Critical Prevents work, causes data loss and/or has no workaround T-Defect Something isn't working: bugs, crashes, hangs and other reported problems
Projects
None yet
Development

No branches or pull requests

4 participants