search

element-hq / element-x-android

Android Matrix messenger application using the Matrix Rust Sdk and Jetpack Compose
Apache License 2.0
885 stars 115 forks source link

Calls are stuck on "Loading" #3117

Open RyanGibb opened 1 week ago

RyanGibb commented 1 week ago

Steps to reproduce

  1. Open a room
  2. Click on the camera icon
  3. An "Element Call" window opens and remains on "Loading"

Outcome

What did you expect?

The call to go through like it does on the Element client.

What happened instead?

I was shown a loading screen that doesn't show any signs of terminating.

Screenshot_20240701-135244

Your phone model

Google Pixel 7a

Operating system version

Android 14

Application version and app store

Element X Version: 0.4.14 (40004140) GCOTEJCZIU, Google Play

Homeserver

Synapse 1.109.0

Will you send logs?

Yes

Are you willing to provide a PR?

Yes

RyanGibb commented 6 days ago

I'm not sure if this is intended behaviour or not, but calls from the old Element android client show a notification on Element X "Call in progress (unsupported)"

YamatoRyou commented 5 days ago

I'm not sure if this is intended behaviour or not, but calls from the old Element android client show a notification on Element X "Call in progress (unsupported)"

Element X does not support calls driven by the coTURN backend, so in the default configuration you need to make sure that the current device can access https://call.element.io Use a browser to access the above URL to verify. The long display of "Loading" in the app may also be caused by you not being able to access the above URL.

RyanGibb commented 5 days ago

It looks like I can access this URL in a browser on the device Screenshot_20240702-210602.png

YamatoRyou commented 5 days ago

It looks like I can access this URL in a browser on the device Screenshot_20240702-210602.png

Try updating to 0.4.15, then open "Settings", click the version number 7 times in a row, click "Developer Options", check if "Custom Element Call URL" is the link above, if not change it to the link above. If it still doesn't solve the problem, then @bmarty may have expected that this is a bug. Element X will point to call.element.io in the default configuration.

Note: The above is a relatively general solution. I am a self-hosted solution, and the above method will point to my own Element Call instance.

RyanGibb commented 5 days ago

Updating to 0.4.15 seems to have fixed this! The call is connected to an iOS Element X instance. Unfortunately no audio or video are getting through.

mazzz1y commented 3 days ago

Element X does not support calls driven by the coTURN backend, so in the default configuration you need to make sure that the current device can access https://call.element.io/

Does anyone know if this feature will be implemented someday, or is this solution deprecated?