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

Network Failed! happening several times when calling between our Samsung S8s #10281

Closed
4 tasks done
gab81 opened this issue Dec 12, 2020 · 15 comments
Closed
4 tasks done
Assignees
Labels

Comments

@gab81
Copy link

gab81 commented Dec 12, 2020


Bug description

Network Failed! happening several times in last 2 months when calling between our Samsung S8s

Steps to reproduce

  • Do an audio or video call
  • Phone that makes the call rings for a bit (maybe 5 seconds) so you think it works OK, then you get network failed!
  • Random, 2 times it works fine, 2 times it drops and you have to call twice every time. more often audio only drops

Expected result: Call to connect first time properly, like Telegram or Whatsapp, etc

Device info

Device: Samsung S8
Android version: 9.0
Signal version: 4.79.3

Debug Log: https://debuglogs.org/9c10750e9a950dca5dfdee99f64597357725d0c583a4b07597ca7365eb13ac02

@gab81
Copy link
Author

gab81 commented Dec 13, 2020

again, this was happening today - i had low signal in a shop, and "signal" couldn't get a phone or audio call no matter what! not even messages. I managed to have a choppy video call on WhatsApp and an OK normal voice call. Why is Signal so struggling to connect when the signal is not PERFECT? when the video calls work they are beautiful but it seems that if everything isn't perfect signal wise (can't get any other word sorry), then it will not even bother connecting and not even delivering messages.

Can you please address these issues? i want to use Signal more and more but this makes it unusable :(

@gab81
Copy link
Author

gab81 commented Dec 14, 2020

have to report it again, today, called my contact that uses Signal, call, ring ring ring ring for 30 40 seconds, call just went off on my end, then called again, and other end ringed and picked up, when i asked "hey did you hear it ring, other end said no", so this consistently happens.

My phone was on 4G LTE on KPN (NL) 4G+ full signal and other end was on strong wireless indoors.

@xmrv
Copy link

xmrv commented Dec 15, 2020

have to report it again, today, called my contact that uses Signal, call, ring ring ring ring for 30 40 seconds, call just went off on my end, then called again, and other end ringed and picked up, when i asked "hey did you hear it ring, other end said no", so this consistently happens.

My phone was on 4G LTE on KPN (NL) 4G+ full signal and other end was on strong wireless indoors.

The exact opposite happens to me since a couple of weeks ago. I can make calls successfully but when I get a call, phone doesn't ring at all only displays a network error and a missed call afterwards. Tested on both good cellular and wifi networks, same.

@gab81
Copy link
Author

gab81 commented Dec 16, 2020

ok this only confirms that something's going on and they should fix it.

@n0sign4l-official
Copy link

n0sign4l-official commented Dec 17, 2020

I can confirm this issue too, if developers need more logs I can provide them since it is quite reproducible. I'm using pixel 3, and for my expirience is something that does happen only amoung android phone

@xmrv
Copy link

xmrv commented Dec 26, 2020

I've tried to reproduce this issue today with 2 phones running Signal 5.0.8(7592).

Device 1: xiaomi mi9t, rooted, no gapps (microg only), resurrection remix 8.6.3 a10 aosp rom.

Device 2: samsung a31 (SM-A315F/DS), no root, full gapps, oem a10 rom.

Issue: Device 1 can successfully call device 2 without any problems whatsoever. However when device 2 tries to call device 1, following happens in device 1:

  • Incoming call notification comes in but neither call ui comes up nor phone rings.
  • If Signal is in foreground it gets closed gracefully and incoming call notification disappears.
  • No indication of a call reappears at all even if Signal gets opened by user afterwards.
  • Missed call notification comes in after device 2 eventually hangs up after timeout.

Here is my debug log:

https://debuglogs.org/bac438fc44e64f78df8ea21581a95d2eaa31e93a4356d55b13b01837bf030619

@gab81
Copy link
Author

gab81 commented Dec 26, 2020

thanks for sharing @Blacktail92 - i really hope they pick this one up as it's not just one or two people...

@gab81
Copy link
Author

gab81 commented Dec 26, 2020

and by the way, it should always ring when you "don't know" somebody is calling you, obviously otherwise it defeats the purpose.

@gab81
Copy link
Author

gab81 commented Dec 28, 2020

did anyone have any luck from support with this? happened again today, called my wife, ring ring ring ring, then failed, then called her again, asked her hey did it ring? No. disappointing. how can you even know if it rings

@n0sign4l-official
Copy link

n0sign4l-official commented Dec 28, 2020 via email

@gab81
Copy link
Author

gab81 commented Jan 3, 2021

sorry but i have to share this one again

again network failed. i turned on the option in sms mms for wifi calling compatibility mode with voice over LTE. going better couple of days now again called my wife ring ring ring, she picked up and i got network failed! had to call twice again. She is at home on wifi voice over wifi, me out on mobile network over voLTE.

i cannot imagine journalists or who really really needs encryption being frustrated with dropping calls and not answering so you never know of the other end answers or is just the connection that sucks.

one last thing, even if bad signal whatsapp always connects even crappy video but usually goes through. why cant signal too?

thank you

@JsBergbau
Copy link

Just want to mention a very similiar issue. I'm on Wifi, 4 meters from AP away, no obstacles inbetween, so best signal. Try calling another phone, immediately "Network failed". Tried again, no calling worked. Had this several times today when testing call function.

@cody-signal
Copy link
Contributor

Hey Folks, thanks for sticking with us. We recently pushed some fixes and hopeful changes to calling in the latest 5.6 beta.

I'm hopeful it'll fix some issues for some of you but I believe gremlins are still lurking in calling. So, after updating to the beta, if you are still encountering the issues above please provide updated debug logs and anything interesting about your calling situation. Examples of things that are interesting: phone has non-standard hardware (like no camera), using bluetooth, in a region that has internet restrictions, using a VPN, etc.

@cody-signal cody-signal self-assigned this Apr 2, 2021
@xmrv
Copy link

xmrv commented Apr 5, 2021

I can confirm that if installed to both phones, v5.6.2 (80702) solves the issue I previously submitted . Thank you devs!

@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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

5 participants