[Bug] Incoming voice/video calls don't ring, but shows 'Missed video call' in red
- [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
For quite some time, intermittently voice or video calls will come in but not ring at all. This morning I made a date with someone to talk over Signal at a particular time. I waited and waited, but after 5min after our planned meeting time, I went to dial them. And that's when I saw the red 'Missed video call'. This happens fairly frequently.
Steps to reproduce
- I cannot reliably reproduce it, as it happens randomly (or perhaps only for certain callers). I have not been able to discern a pattern.
- If I ask my wife to call right after as a test, it will ring.
Actual result: No ring. Nothing in Android notification list. just a 'Missed video call' message in red in the relevant conversation Expected result: Phone should ring and present the ACCEPT/DECLINE pop-up prompt.
Screenshots
(See attached)
Device info
Device: Google Pixel 6a Android version: 14 (Build # AP2A.240605.024 Signal version: 7.9.6
Link to debug log
(See attached) signal-log-1720447511297.zip
Hi there, thanks for the report. I chatted with our calling team and the last call in your logs shows that you were slow to receive messages from the caller needed to establish the call connection between the two of you. Would you be able to get the logs from the caller?
This issue is very common and this happens to all the users mostly
This issue is very common and this happens to all the users mostly
Would you be able to provide debuglogs to help us figure out what's going wrong for you?
I have observed a similar issue for the last 2-3 months. What "helped to resolve" in my case - setting a custom ringtone for Signal calls, different from global (phone) call ringtone.
@cody-signal How do I capture debug logs? Do I need to use logcat? How long are these logs stored? The problem is, that this never occurs on my phone, but several of my family members told me that they have this issue, and I doubt they would be skilled enough to enable developer tools and use CLI tools like adb and logcat themselves.
I have the same issue on multiple pixels that run CalyxOS with MicroG. I'm mainly just adding myself to the notifications here, but can add logs if they will be of use. I presume it's safe just to add the logs generated in the help section of the app?
How do I capture debug logs? Do I need to use logcat? How long are these logs stored? The problem is, that this never occurs on my phone, but several of my family members told me that they have this issue, and I doubt they would be skilled enough to enable developer tools and use CLI tools like adb and logcat themselves.
I have the same issue on multiple pixels that run CalyxOS with MicroG. I'm mainly just adding myself to the notifications here, but can add logs if they will be of use. I presume it's safe just to add the logs generated in the help section of the app?
To get debug logs, within Signal, go to Settings > Help (scroll to the bottom) > Debug log and then press submit. Here's how we handle your logs and you can always reach out to Signal support via email too to submit them.
Oh, that's cool. I never noticed the built-in log feature. Do you have a PGP key for email submissions? @cody-signal
https://debuglogs.org/android/7.14.2/24bd9833978707e67fd8c39eb45e40e543d1887b192df75822be3431c39e2528
https://debuglogs.org/android/7.14.2/420cc6a5636ab95865689d2e93c73d6f1b0534a3dc203a0bec0c8de837a886a8
Probably a duplicate of https://github.com/signalapp/Signal-Android/issues/7733
We made a recent change to how incoming calls are handled and would appreciate anyone experiencing this issue to provide the following:
- Make sure you are running at least 7.14 or later
- Rough date and timestamp in your phone's timezone of when the missed call happened
- Debuglogs after it happened
Here's mine:
- Running Signal 7.16.4
- Log: https://debuglogs.org/android/7.16.4/8a5b84a565f5a0bf057680cdec5821b7fa68fb2717ffea63f8767677d5d2e226
- Missed calls occured multiple times (on both ends) at around 18:40 GMT+1 (16:40 UTC), +- 5 minutes
Appreciate you talking the time to look into it. On my end the issues started occuring after I was forced to migrate phones around a month ago. Reinstalling the app seems to have helped for one of my contacts, but evidently not all.
For a few weeks now, there has been no message tone for incoming chats and no ringtone for incoming voice calls. The message 'missed voice call' appears for voice calls. I missed a voice call at 4.58 p.m. and created a 'debug log' shortly afterwards.
https://debuglogs.org/android/7.17.5/e4cf9ee2c4c4d7f92ad820968a10956314e6e00dfb0a69e000ac047dce46f88b
@Cre8or looking through your logs, it seems like both directions had trouble establishing a connection for the call. It seems like you had good internet but something was preventing the communication from happening. I've let the call team know.
@timstrom Looks like you have slow message receiving problem OR the sender is slow sending. You received the message to start a call over a minute after it was sent. Thus why we don't ring and treat as a missed call. Do you often have late messages in general?
Thank you for checking the log file. I have understood that it is a local problem and not a malfunction of the app. I reset the wifi settings and it seems to be working again.
Here is one for me. Call was at around 15:42 GMT
https://debuglogs.org/android/7.20.2/11e2c96cfb2951c5e4d17e929d6fbb96ad133b2e8c2e2d539142dbc7b0d6ced3
Same issue here, calling the user doesn't ring and shows up as 'missed video call'. Started around a month ago I think, hasn't worked once ever since.
https://debuglogs.org/android/7.25.2/6d7eaf2ef023cdfaae6511a42ed1d6f0eb9091e5a7fb6dada18d55ce5a3dbd6a Time of call: 2024-11-23 - 22:48 GMT+1
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been closed due to inactivity.
I know this got marked as 'completed' but I'm wondering if this issue got resolved (or resolved itself) for the other people in this thread that had this issue?
I don't recall encountering it in the past few months. Hard to say when the last occurence was, but if desired I can update the thread if the issue arises on my end again.