Calls always income as missed ones without ringing and Signal doesn't report the call failed

szotsaki commented 6 years ago

Please, report issues only from version 5.6 upwards!

General complaints forum and user help-out on this issue: https://community.signalusers.org/t/make-signal-calls-reliably-ring-on-the-receiver-side/18510

[X] I have searched open and closed issues for duplicates
[X] I am submitting a bug report for existing functionality that does not work as intended
[X] I have read https://github.com/signalapp/Signal-Android/wiki/Submitting-useful-bug-reports
[X] This isn't a feature request or a discussion topic

Bug description

Users are welcome to re-submit bug reports

When Signal is opened in front of me on my phone and via Hangouts PC I hear the other party while his Signal is actually ringing me. My Signal shows no sign that I'm being called. At the end of ringing, when the network automatically disconnects, I immediately receive a "You have a missed call" notification in the chat.

Reproduced on three different WiFi networks with the same person.

The time difference between the two phones is approximately 5 seconds. Both phones are set to synch to carrier time.

Steps to reproduce

Make phone A call phone B in Signal
Observe that phone B gets no notification about the incoming call just the missed one.

Actual result: Call arrives as missed one. Expected result: Phone B rings.

Screenshots

Device info

Device: Sony F5121 Android version: 7.1.1 Signal version: 4.14.10

Link to debug log

Callee debug log: https://gist.github.com/anonymous/9984ab543d85a181b06b02954564c060 Caller debug log: https://gist.github.com/anonymous/5eae662fee114e5e07a72dbd02c0e92d

Original report: #7314

@moxie0:

According to the logs in the issue, the devices are not able to find a valid ICE candidate.

Please, unambiguously tell the user there is an error happening during the call and the call has never been initiated.

References: #7603

Since this bug report is specifically about the non time-sync issue, there's another one for the time-sync problem. Please, don't clog this report with NTP-timing issues anymore but you're more than welcome to add your comments in and subscribe to #9633. Thank you.

pietervw commented 5 years ago

We are still experiencing this bug most of the time.

Here are the logs off our 2 phones: https://debuglogs.org/1803944df359aeee66995314c94b117e076e81a95cb41f8046fec6ce287b5e74

https://debuglogs.org/daeffb3b881de0d753dee94975b57d1f4faa8d9ae9dc3bf261d0d8642c4f72d1

Any assistance would be appreciated

ozgurakyazi commented 5 years ago

@mattimac @five-c-d I could not login to the https://community.signalUsers.org with my github credentials but I created the new topic.

Here it goes: https://community.signalusers.org/t/issue-7733-call-always-miss-new-debug-logs/6493

five-c-d commented 5 years ago

@pietervw , almost certainly you are onto something, though it might not solve all the problems (ozgurakyazi is experiencing failures on wifi-to-wifi calls ... as is the case in my intermittent MissedCall situation).

But at least in one situation, cryptocalls worked fine on wifi, worked fine on wifiWithVpn, worked fined on dataplanWithVpn, and mysteriously failed with dataplanSansVpn. The problem was that one of the devices was an S9 with android v9, and the enduser had enabled 1.1.1.1 as their DNS-provider. We suspect (but do not know for sure) that there was IPv6-related something something going on under the hood, which using the VPN-on-dataplan masked successfully. https://community.signalusers.org/t/calls-not-connecting-possible-issue-with-dns-over-tls-and-or-ipv6/6286/31 Can you see what your DNS-lookup settings are like, in your android network-settings? Do you have an app installed which allows you to perform ping&traceroute type of tests from your android, such as Termux perhaps?

ozgurakyazi commented 5 years ago

Hello All, With the helps of @five-c-d , the problem is resolved (at least for 4 different phones I have access to) now. :+1: :clap: :smile: The source was the time. All 4 phones were seemingly in the same time(was varying at most 1 minutes.). But when I check the time configurations, 3 of them were in the different(wrong) time zones. I changed all time zones to the correct ones and enabled automatic time. Now all the calls work for all directions :fireworks:

I hope this is the problem for all and the issue is fixed.

Thank you all :)

five-c-d commented 5 years ago

@pietervw , please see https://community.signalusers.org/t/spurious-missed-call-on-dataplan-android-7733/6504 ... it looks like you are having some process-problems (both people dialing each other simultaneously -- which is understandable since this is a frustrating bug). See the comment about 'Receiver not registered' which is possibly related to #8402 on the +xxx79 enduser's handset.

But even when you are not having mid-air-collisions happen, there are a lot of strange exceptions in your debuglogs you posted == https://github.com/signalapp/Signal-Android/issues/7733#issuecomment-468351112 In particular, this cannot be correct:

2019-02-28 17:36:05.398 SAST W SignalServiceMessageSender: java.io.IOException: No connection!

The same exact device just received a bunch of packets over the same exact dataplan-connection. There are a lot of TimeoutException and a lot of DuplicateMessageException errors (especially on the one 'successful' call-attempt at 17:44 excerpted here). There are some recent hits in github for DupeMsgE, but they might not be directly related. Why is signal4android under the impression that it has "No connection" when clearly it has one?

davidar commented 5 years ago

Whitelisting Signal in the power optimisation settings seems to have resolved this for me.

DemiMarie commented 5 years ago

I can think of two problems:

Does Signal use the proper Android VOIP APIs?
Does Signal use real-time FCM notifications?

yaomtc commented 5 years ago

While I've also experienced missed Signal calls (I have it set to vibrate but I haven't felt it), I feel that this Gadgetbridge bug report is relevant:

https://github.com/Freeyourgadget/Gadgetbridge/issues/786

I use Gadgetbridge to get most of my notifications, but Gadgetbridge ignores "ongoing" notifications, which Signal uses for calls. Maybe it would help if there were an option to send one regular notification when the call is coming in, and then start the "ongoing" notification while the call is going, if necessary.

kravietz commented 5 years ago

I have identified one more thing that is causing this symptom: Signal seems to rely on Google Play Services and I couldn't get Signal calls to work on a custom ROM (LineageOS) with the services app replaced by MicroG for privacy. The emulation of Google Services in MicroG was however disabled and apparently Signal wasn't getting some kind of notification - when I re-enabled them, it all started to work.

Champion0081 commented 5 years ago

does ipv6 configuration somehow blocks the connection just one way?

@ozgurakyazi -- Yes, this seems to be the case, at least with some configurations. One person that was receiving no calls on dataplan, but got them to work on wifi or by using the VPN with their dataplan (which typically ADDS latency and HURTS cryptocalling but in this situation helped), traced the difficulty to enabling a non-default DNS-lookup service. https://community.signalusers.org/t/calls-not-connecting-possible-issue-with-dns-over-tls-and-or-ipv6/6286/31 This was different from the usual 7733 type of bug, but methinks related to some flavours thereof. The workaround was to return to using the normal DNS-lookup service of the carrier... does anybody who is experience 7733 buggy behavior, have cloudflare or dns.google 1.1.1.1 or 8.8.4.4 or 8.8.8.8 enabled, perhaps?

I use DNS over https (avaiilable natively on samsung S9 android 9) please remember to test with and without it this may be important factor.

harmonicus commented 5 years ago

Hey there, hew guy here, missed call problem,

i have both phones on desk, they have automatic (same) timezones, ipv4, wifi connection Android 8.0 and Android 5.1

I found out that Orbot blocks calling/recieving - TOR + VPN (both in Orbot) Orbot version 16.0.5-RC-2-tor-0.3.4.9

when both phones have Orbot disabled - all ok; all works
Android 8.0 is calling, Android 5.1 receiving A. Android 8.0 TOR off, VPN off; Android 5.1 Orbot on, VPN on all ok; calling works, sound works B. Android 8.0 TOR on, VPN on; Android 5.1 Orbot on, VPN on missed call problem, C. Android 8.0 TOR on, VPN off; Android 5.1 Orbot on, VPN on all ok; calling works, sound works
Android 5.1 is calling, Android 8.0 receiving
A. Android 5.1 TOR off, VPN off; Android 8.0 Orbot on, VPN on reciever do not hear ringing sound, on main screen there are no changes, but you can see icon of calling one the top line. Anyways when the call is answered there is no connection established B. Android 5.1 TOR on, VPN on; Android 8.0 Orbot on, VPN on missed call problem, C. Android 5.1 TOR on, VPN off; Android 8.0 Orbot on, VPN on same as in 3.A. D. Android 5.1 TOR off, VPN off; Android 8.0 Orbot on, VPN off i can see on main screen incoming call and answer it and establish connection, BUT i can not hear the calling sound (vibrations are there). When connection is established, i hear no voice on the other side (bad) E. Android 5.1 TOR off, VPN off; Android 8.0 Orbot off, VPN off same as 3.D. - no calling sound, no hearing sound

Android 8.0 https://debuglogs.org/b3363c1eaedd655ade75de1edb683356de0fb759021b0042e0e249edc16a14d6 Android 5.1 https://debuglogs.org/c86aa192c1b5c8c169e5594da181375ae1d38a3c0abe01fe3cc85330935c92a3

Time stamps 2A, 1219 2B 1220 2C 1221 3A 1221 3B 1223 3C 1223 3D 1225 3E 1226

Ok, so that my piece of the cake

EDIT: small changes, on android 8.0 sometimes there is a calling voice (sometimes not), and after connection is properly established sometimes there is voice on the other side (sometimes not), sometimes just one microphone works, sometimes non - and that on both devices with Orbot completly off

And yes VoiceNotes works perfect

Champion0081 commented 5 years ago

@harmonicus please save as much debug log assigned to each of the cases i bet that will be helpful for the devs to look into it. Here is short manual if needed https://support.signal.org/hc/en-us/articles/360007318591-Debug-Logs-and-Crash-Reports

five-c-d commented 5 years ago

i would have to make the whole process again

No, the debuglogs are not erased ... just capture the debuglog on your android 8.x device, now, then submit it, longpress to copy the URL#1.

Then do the same on your android 5.x device, submit and copy URL#2.

Paste both URLs here, and give us some idea of what timestamp is associated with each test#1 / 2A / 2B / 2C / 3A / 3B / 3C / 3D.

I can say though that because of the high jitter&latency, cryptocalling through Orbot is pretty much guaranteed to be awful (possibly even non-functional). You can usually make voiceNotes work, which is like a kinda-sorta semi-realtime conversation... to a moonbase.

harmonicus commented 5 years ago

moonbase :)

I've edited main post above - logs, time stamps, small edit

Ben-Russell commented 5 years ago

https://debuglogs.org/b6218683e2430f809079a9d12d62a4f87d26cf5e49ff55478e52c15903f99f02

Of the last 4 phone calls, 3 went directly to missed and the last one is the only one that actually rang my phone. How can I stop this from happening?

Ben-Russell commented 5 years ago

I have no vpn or anything similar installed on my phone.

ozgurakyazi commented 5 years ago

Without checking the debug log, can you check the time settings of all the phones?

It would be easier to have them automatically set with correct timezones. Let us know what happens after putting them all auto. Best Regards,

Özgür Akyazı

---- On Tue, 02 Jul 2019 03:14:18 +0200 notifications@github.com wrote ----

https://debuglogs.org/b6218683e2430f809079a9d12d62a4f87d26cf5e49ff55478e52c15903f99f02

Of the last 4 phone calls, 3 went directly to missed and the last one is the only one that actually rang my phone. How can I stop this from happening?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

Sensor66 commented 4 years ago

I have this problem too, on a MotoG5, Android 8.1.0. No VPN. I connect via a WiFi with ipv6.

Whitelisting of power optimization does not help.

Just now a test: when I put the phone on 4G (WiFi off), then the problem is solved immediately: calls get through normally.

Champion0081 commented 4 years ago

I have this problem too, on a MotoG5, Android 8.1.0. No VPN. I connect via a WiFi with ipv6.

Whitelisting of power optimization does not help.

Just now a test: when I put the phone on 4G (WiFi off), then the problem is solved immediately: calls get through normally.

Is that ipv6 only wifi? If not are you able to use ipv4 only and narrow down the issue to ipv6 networking?

ghost commented 4 years ago

Is there a thread for iOS too? Both me and my partner can't call each other, same issue. Rings and rings but nothing, then the second you hang up you get the missed call notification.

Champion0081 commented 4 years ago

Is there a thread for iOS too? Both me and my partner can't call each other, same issue. Rings and rings but nothing, then the second you hang up you get the missed call notification.

can you attach debug logs from both sides? can you test more on LTE/cellular data and wifi? can you tell in any of those cases: wifi/cellular data if you get ipv4 or ipv6 address to test if ipv4 or ipv6 makes any difference?

Sensor66 commented 4 years ago

@ mattimac

I have this problem too, on a MotoG5, Android 8.1.0. No VPN. I connect via a WiFi with ipv6. Whitelisting of power optimization does not help. Just now a test: when I put the phone on 4G (WiFi off), then the problem is solved immediately: calls get through normally.

Is that ipv6 only wifi? If not are you able to use ipv4 only and narrow down the issue to ipv6 networking?

I have a TP-Link Access Point TL-WA801ND, and I think that is IPV4 only, but I am not sure and could not find it.

Champion0081 commented 4 years ago

@greyson-signal @moxie-signal OK guys i believe i was able to isolate the problem and it seems in that scenario chaning the APN from ipv6/dual stack to ipv4 fixes the issue. Here are debug logs. Please note Orange claims they do not shape the traffic in any way.

Phone A (dials the call) - Samung galaxy A70 SM-a705FN PPR1.180610.011.A705FNXXU3ASG6 SIM: Poland Operator: Play Phone B (wait for the call) Samsung galaxy S9+ SM-G965F PPR1.180610.011.G965FXXS6CSH5 SIM: Poland Operator: Orange Phone B configured APN profiles:

"Orange INTERNET" (default) Name: Orange INTERNET APN: internetipv6 Proxy: not set Port: not set Username: internet Password: internet Server: not set MMSC: not set Proxy MMS: not set MCC 260 MNC 3 Authentication type: no auth APN tyoe: default,supl APN protocol: ipv6 APN roaming protocol: ipv4 Connection: undefined Virtual cellular network operator type: SPN Virtual cellular network operator value: Orange

On this profile phone gets two IP addresses: 2a:00:f41:1870:xxxx:xxxx:xxxx:xxxx:xxxx ipv6 address 192.0.0.4 ipv4 address

"ipv4" (custom) Name: ipv4 APN: internet Proxy: not set Port: not set Username: internet Password: internet Server: not set MMSC: not set Proxy MMS: not set MCC 260 MNC 3 Authentication type: no auth APN tyoe: default,supl APN protocol: ipv4 APN roaming protocol: ipv4 Connection: undefined Virtual cellular network operator type: SPN Virtual cellular network operator value: Orange

On this profile phone gets 10.71.xxx.xx IP address only

Phone A set up on test wifi network 192.168.7.0/24 vlan, dont worry bout connection quality - dediacted cable connection from UPC 600/60 for those tests

In scenario where both phone A and B are on wifi everything works great.

In scenario where phone A is on wifi and phone B is on LTE (customized APN with ipv4) phone B does receive the call properly phone A call log https://debuglogs.org/25ab0b41bb878995228f0c9e0a7b6519aaa20cb51adbf6197a58c66d91c3d3e4 phone B call log https://debuglogs.org/dbe73db4ae7fec032d79ed49a7b8f429bd204731c12ae50c931a90cca94e2494

In scenario where phone A is on wifi and phone B is on LTE (default APN with ipv6) phone B does NOT receive the call properly around 23:00 phone A call log https://debuglogs.org/4c3a676bd862504d840e9193d42107924e830711f3caeac668bf6b537fbf343b phone B call log (what is interesting there is incoming call icon on notification bar at the toip and in notification drawer there is constantly "connecting" https://debuglogs.org/650e826933b3624faeeb66be37b872972021cf44be8e163422f5cb37b2b60356

Interesting part, notification with no vibration and sound? this what we see on notification bar (screenshot below)

2019-09-18 23:02:16.373 CEST I MessageNotifier: Posted notification. Notification(channel=messages_1 pri=0 contentView=null vibrate=null sound=null tick defaults=0x0 flags=0x1 color=0xff2090ea category=msg actions=2 vis=PRIVATE semFlags=0x0 semPriority=0 semMissedCount=0) 2019-09-18 23:02:16.380 CEST D LockManager: Entered Lock State: PARTIAL 2019-09-18 23:02:16.381 CEST D AccelerometerListener: enable(false) 2019-09-18 23:02:16.397 CEST I IncomingRinger: Cancelling vibrator

Phone B screenshot while phone A tries to ring phone B and on phone B side no ringing but "connecting" (only the icon on notification bar and notification with "connecting" information") signal-attachment-2019-09-18-230330

Logs sent just after each scenario

MrWolf-to commented 4 years ago

Hi, I had the same issue with my Samsung Galaxy S7 edge with Oreo. If I tried to call from another phone of mine, calling would't work and I received the message of missed call. Oddly enough, viceversa worked, so I thought it was a phone problem.

Searching for this problem on Google, I found a solution on Reddit that seems to work, at least for me: just set "Date and time" on automatic.

Champion0081 commented 4 years ago

@greyson-signal is there anything we can do as we already have test report, debug logs and some proofs that may be connected to ipv6 only? Can i do anything on my setup to provide more useful information?

szazer commented 4 years ago

I have the same problem on four smartphones, operator Orange Poland (2xAndroid 8, 1xAndroid 7.1.1, and one of them is 9.0 Pie). I announced that is not problem of GSM operator (APN). That's no matter LTE or HSPA or GSM technology. The big problem is Google DNS. I installed Cloudfare 1.1.1.1 aplication from Google Play, turned on this app, DNS was switched to 1.1.1.1 and Signal began work PERFECTLY. And there is one problem: when DNS are changed to 1.1.1.1 Google Play shop doesn't work at all, many Google service doesn't work too... Generally i have deleted Signal from my smartphones because this issue is not accepted for me, there is not professional application for home / bussines using. Bye Bye funny Signal. I use Wire today, its work perfectly ! :-) Full encrypt and works on WIFI, LTE, HSPA, GSM and any ADSL or VDSL broadband connections. See you on Wire :)

szotsaki commented 4 years ago

Just to have all the information in one place:

Originally posted by @usergoodvery in https://github.com/signalapp/Signal-Android/issues/8302#issuecomment-509656511

Signal folks this issue and #7733 are most likely related to some logical bug in how you set IceTransportsType.RELAY for PeerConnection configuration as in https://github.com/signalapp/Signal-Android/blob/e603162ee767d56fa16f56701cd29010f22ed22d/src/org/thoughtcrime/securesms/webrtc/PeerConnectionWrapper.java#L72

Since you are automatically forcing non system contacts on the TURN path as per https://github.com/signalapp/Signal-Android/blob/84fd1a9140e15a3f02bec6a2803d26223acc44a3/src/org/thoughtcrime/securesms/service/WebRtcCallService.java#L389 (suspect very few users turn this option on by default) your TURN servers are probably overloaded and users are getting random success rate with their webrtc connections, because system-contact vs non-system-contact is random and highly localised to each user.

The remote peer won't be trickling ICE candidates back, and onIceConnectionChange won't evolve out of the CHECKING state forcing a timeout and users seeing missed call note.

@alan-signal, @greyson-signal, @moxie-signal: does it give the necessary input for you to start investigating this issue further?

DemiMarie commented 4 years ago

Also, some users are behind nasty NATs that force them to the TURN path.

Champion0081 commented 4 years ago

Can someone with more in-depth knowledge about ipv6 analyze this? I found description of how Orange introduced Ipv6 to its network. I remind that there are issues with calls on IPv6 only, on IPv4 LTE on Orange the problem does not exist. http://www.data.proidea.org.pl/plnog/12edycja/day2/track4/01_ipv6_implementation.pdf

lcortier commented 4 years ago

I have that bug with only one person, which is very annoying because it's my significant other :( We both are using the same mobile data provider. No VPN on either phone. I'm the only contact she has with Signal. We verified each other's signal contact last time we were physically together. No change. Up to a few weeks ago, she could not call me but I could. Now it's not working in both directions. Back to WhatsApp for the moment :(

Champion0081 commented 4 years ago

@lcortier Check APNs on both phones and let us know if they are ipv6 or ipv4 or dual. If dual or ipv6 change to ipv4 and let us know if that fixes the issue. provide debug logs if not.

lcortier commented 4 years ago

APN on my phone (OnePlus 6T) is ipv4, on my partner's phone (Samsung Galaxy S7), it's all greyed out. I tried to explain how to set a new APN for her but it didn't work... Will try again tomorrow. Thanks for the quick answer !

Champion0081 commented 4 years ago

APN on my phone (OnePlus 6T) is ipv4, on my partner's phone (Samsung Galaxy S7), it's all greyed out. I tried to explain how to set a new APN for her but it didn't work... Will try again tomorrow. Thanks for the quick answer !

its grayed out because you cant edit this one but that is still applied let me know what info is there. you can create new one with setting the same or similar.

lcortier commented 4 years ago

its grayed out because you cant edit this one but that is still applied let me know what info is there. you can create new one with setting the same or similar.

Ok, the greyed out and the new one we created are both in IPv4.

attila-lendvai commented 4 years ago

i have experienced this with one contact (Samsung phone with standard OS). my calls immediately went to missed call on her side, on my side it was "dialing". she could call me for a while.

then it stopped working both ways.

then it started to work again for both directions.

we didn't deliberately change anything in our environment, at most Signal app updates.

here are two logs that may help:

https://debuglogs.org/df39172a406a0797c8500a73e77b6de710b309f9605567870939689807d7099e

https://debuglogs.org/8d479835a25e70f185aa63c471322e114be06c2e94fad0ce17654b11f11a9152

lcortier commented 4 years ago

Yessss ! Issue solved. Her clock was set to manual and was 10 minutes late. I just set it to automatic and everything started to work immediately in both directions now. Wouhouuu, after 4 months of research and getting mad about "such a stupid bug", I understand how it was just a "feature". :) Why her clock was set to manual, I'll never know (it's a second hand phone, so she didn't do it) and even why Google allows phones to be set in manual (at least for the general public) when many apps may start to bug if not synchronized is beyond me.

erik55 commented 4 years ago

Just wanted to comment, that I have the same issues. And the non automatic time (manual time) and time shift seems to be the problem. (Here on Canary Islands I have to set it on manual, as otherwise the timezone changes several times a day, as we have providers that send the mainland Spain time zone, others the Canary Islands time zone.)

Conclusion: Is there a possibility for Signal to circumvent this non-working phone calls? At least show a hint: Maybe your or your callees time isn’t set correct or differ?

Champion0081 commented 4 years ago

Just wanted to comment, that I have the same issues. And the non automatic time (manual time) and time shift seems to be the problem. (Here on Canary Islands I have to set it on manual, as otherwise the timezone changes several times a day, as we have providers that send the mainland Spain time zone, others the Canary Islands time zone.)

Conclusion: Is there a possibility for Signal to circumvent this non-working phone calls? At least show a hint: Maybe your or your callees time isn’t set correct or differ?

Please look for this issue and then if not already reported start separate one including debug logs and all data required. This is not in scope of issue #7733 i believe as issue seems to be at least ipv6 related (at the same time on both ends same time and timezone).

strugee commented 4 years ago

@lcortier it's not a feature and it is, in fact, a bug, because there is no such thing as time.

szakib commented 4 years ago

I have seen this issue on two (receiving) phones now, a CAT S41 and a Sony Xperia Z2. Source does not seem to matter. Please solve this. I convinced my family a year ago to switch to Signal, but if calls don't work reliably, I cannot keep the non-technical members on this platform.

erik55 commented 4 years ago

@lcortier it's not a feature and it is, in fact, a bug, because there is no such thing as time.

Haka, very funny. Point 6 says “Protocol ideas that require synchronized clocks are doomed to failure.”

Well, we are all doomed, as the developers don't stick to their own rules.

I have reproduced it just now. If my time is set wrong only 3 or 4 minutes I can't call my daughter (Samsung S7), neither can she call me.

Surprisingly I can call my wife (also Samsung S7).

Maybe that is the only bug for all users? Workaround: synchronize your clocks! Tsss.

strugee commented 4 years ago

@erik55 you're missing my point, I think. I'm not disputing that it can be reproduced! I was addressing the comment that said "I didn't realize this was a feature and not a bug" because that implies that it doesn't need to be fixed, when really it does.

lcortier commented 4 years ago

What I mean is, as an ex-developper, I perfectly understand why time synchronisation is needed for a communication application. My issue being solved just by synchronizing time, I tip my hat to you guys. Good luck :)

kirkawolff commented 4 years ago

A fix should be simpler than synchronizing clocks. It seems to me the problem is the ring-timeout is comparing the local clock with the sender's initiation time stamp. This should be easily resolved by starting a ring timeout upon receipt of the request in the receiver's end rather than depending on both end's clocks to be synchronized. The alternative is to use a separate clock in the app that's synchronized with a server so both phones can be working from the same reference. Asking users to turn on clock synchronization on their phone isn't reasonable for several reasons such as the fact that cell towers are often the source of time in this case and they often are way off. Also, cell phones are some of the worst devices at keeping time without synchronization, they commonly drift 30 minutes per year.

ioogithub commented 4 years ago

I have this issue as well. I have two contacts that I used to communicate with during signal.

I am using LineageOS version 17 on a Motorola G7 Contact 1 was using an iPhone 7 but has upgraded to iPhone 11 Contact 2 is using a Samsung A8

None of us can use signal. The calls go right to missed call on all of our phones. I just tested for 30 minutes with both contacts, having them call me and me calling them. Not a single call actually worked, it just goes to Missed call immediately.

We all had to abandoned Signal because of this issue, it just doesn't work an any platform on any phone. There is no way to contact each other.

I have been trying to get family members to use Signal but we are back to regular cell service. What is going on with Signal that it is so broken?

Edit: None of our clocks are set to manual time and none of us are using a VPN or private DNS.

quantizzed commented 4 years ago

Same with me. I tried to move my family to using Signal, but failed due to the problems with missed calls (and messages, too, by the way, as described in issues #8604 and #9533 ).

ioogithub commented 4 years ago

It is very frustrating. I can't recommend anyone using Signal at this time, too many problems, it is obviously not ready for prime time.

It is a struggle trying to get users onto the platform. The answer I get is "why can't you use Facebook messenger like everyone else"

What am I supposed to say when Signal doesn't even work, here try this platform that is more secure but is unreliable and don't actually work?

Signal seems like more of a proof of concept.

donfn commented 4 years ago

@ioogithub E x a c t l y. I've brought ~10 people on signal and they are slowly drifting away to facebook again, because signal simply does not work.

kravietz commented 4 years ago

@ioogithub @donfn You could try https://matrix.org/ as it offers comparable levels of security and privacy while being fully open-source and federated.

szakib commented 4 years ago

Dear Signal developers,

Maybe it would be time to fix this fundamental bug reported two years ago, before all your users leave.

@ioogithub @donfn You could try https://matrix.org/ as it offers comparable levels of security and privacy while being fully open-source and federated.

signalapp / Signal-Android