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

Multiple seconds of delay before audio works when answering voice or video call #11354

Open
4 tasks done
spagy opened this issue Jun 1, 2021 · 8 comments
Open
4 tasks done

Comments

@spagy
Copy link

spagy commented Jun 1, 2021


Bug description

Video call

When I receive a call, I press the green button to start the call.
The screen remains unchanged, still displaying the buttons to answer the call.
After multiple seconds I will hear a noise that indicates the start of a call.
The screen shown during the call then appears and video becomes visible.
At the point when the video becomes visible, the call duration is usually already about 12 seconds.

Voice call

When I receive a call, I press the green button to start the call.
The screen changes to the normal in-call screen, I can see the duration of the call at the top of the screen, the seconds start to count.
However, I cannot hear the other person and I don't think they can hear me.
After multiple seconds I will hear a noise that seems to indicate the start of a call.

Steps to reproduce

  • Have someone call you, video or voice, from Android or iOS (desktop untested)
  • Answer the call

Actual result: The call will start, but there is no audio or video for multiple seconds. This causes confusion and results in lots of calls starting with "can you hear me"s.
Expected result: The call starts audio and video work almost instantaneously (within less than a second at least).

Device info

Device: Motorola Moto G6
Android version: 11
Signal version: 5.11.5

Link to debug log

https://debuglogs.org/65d25d427534c953fe6c607bb4348d1f7f698c9bd6b06eadbdc028f973a58780
To my untrained eye it looks like the call is answered at 2021-06-01 18:29:00 and video becomes visible at 2021-06-01 18:29:12

@stale
Copy link

stale bot commented Jan 26, 2022

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the wontfix label Jan 26, 2022
@stale stale bot closed this as completed Feb 2, 2022
@spagy
Copy link
Author

spagy commented Apr 24, 2022

this is still an issue. i'm using version 5.35.3

i can submit more logs if that would be helpful.

if there's anything useful i could do to help track this down, i'd be happy to help.

@jim-signal jim-signal reopened this Apr 25, 2022
@stale stale bot removed the wontfix label Apr 25, 2022
@jim-signal
Copy link
Contributor

Hi @spagy, yes some updated logs would definitely help to find a cause for the issue.

@spagy
Copy link
Author

spagy commented Apr 25, 2022

thanks for re-opening the issue.

i'll provide some updates on the issue as well as a few debug logs.

updates

  • this affects both calls that i make and that i recieve. (it's possible this isn't a change and that i just only tested answering calls not making calls when i raised this issue.)
  • the video now starts as soon as the green answer button is pressed. you can see the other person for about 10-12 seconds before the a 'ping' noise indicates that audio is connected and you can start your call.

this affects almost every call. although, today i answered a call and unexpectedly the audio was connected straight away (or at least it wasn't the normal 10-12 second delay). i have a debug log from just after this call. i cannot remember any other recent video call, regardless of who started it, that didn't start with a delay.

debug logs

@cody-signal
Copy link
Contributor

Could provide timestamps of when the delayed calls were made/received? The logs have multiple calls in them so it's hard to know exactly which ones are experiencing the problem.

@spagy
Copy link
Author

spagy commented Apr 26, 2022

yep, will do. the last call in each log should be the relevant one. i've edited my comment above to include the timestamp (provided in the app UI) of the call next each debug log link.

i think debug log links used to point to plain text files but now point to encrypted or compressed logs that i don't know how to view. are the logs only available to signal contributors or is there still some way for me to view them?

@cody-signal
Copy link
Contributor

Thanks!

They are compressed gz files now to save data/space. You can extract them by downloading the file, adding .gz to the end and then using gzip to decompress them into raw text.

@spagy
Copy link
Author

spagy commented Apr 26, 2022

fab, thanks! i got as far as running gunzip (without adding .gz) and promptly gave up when it didn't work :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants