Graphene OS intermittently fails to ring for incoming calls

schweizer I agree that it is difficult to fix right now. But I hope you agree that we should not prioritize issues on how easy they are to fix.

Sorry, but I'm not sure what I said that made you think this. I said that there's no way to troubleshoot something when the issue can't be reproduced, not that it's hard to do. GrapheneOS does lots of impressive things, many of them hard. They've fixed a lot of upstream bugs as well, one example is the upstream Bluetooth bug introduced with QPR2. They bought a Samsung watch and everything to reproduce the bug and fix it.

Considering the fact GrapheneOS hasn't (to my knowledge) touched any of the code that would cause this issue, the issue would almost certainly be an upstream one, and can also be a carrier issue. I can't remember the exact details, but there were issues with certain carriers not long ago and AOSP pushed out fixes for those carriers. For all I know, this issue is fixed in QPR3.

schweizer Can someone remove the solved tag please?

done

other8026 unless it's just that random it's easily reproduced. Call the phone. My circumstance are pixel 8 pro, phone doesn't acknowledge an inbound call. I was hoping someone that's still using gos would chime in if it's still happening.

Ducter it's easily reproduced. Call the phone.

I get all of my phone calls, so it's not that easily reproduced. You'd think if it was a widespread issue, many people would be reporting it, but it just isn't that widespread. Could be caused by any number of things, like:

• owner or secondary user profile?
• default phone app or another one?
• phone settings
• carrier
• signal strength
• phone is up to date or not (latest stable release is 2024061400)
• maybe something else I didn't think of

The latest build (2024061400) suffers from the issue as well. Tried a clean install this morning. Immediately after booting I called the phone and nothing. T-Mobile is my carrier, Wi-Fi calling on or off mates no difference, phone just will not ring.

Ducter T-Mobile is my carrier [...]

I think T-Mobile operates in multiple countries, and their network may not work precisely the same way everywhere inside a single country.

Ducter Wi-Fi calling on or off [makes] no difference [...]

SIM or eSIM? Preferred network type? Battery saver? "Do not disturb"?

I think it is important to understand that, while some users are experiencing this problem, many many many many users are not. Thus the difference between experiencing it and not experiencing it is likely to depend on details, potentially the alignment of multiple details. It seems unlikely to be affecting all T-Mobile users throughout the countries served by T-Mobile. Obviously it is up to each person to decide what to disclose, but a report limited to "T-Mobile, independent of Wi-Fi calling" may not shed much light on the situation.

de0u fair enough.
Pixel 8 pro
T-Mobile US
Traditional SIM card
Preferred network, tried them all.
Battery saver off
Do not disturb off
Wi-Fi and Wi-Fi calling on and off
Default phone app.
My son has the same phone, carrier etc he's been on graphene since basically phone release as graphene came out pretty quickly and does not have the issue. When you install graphene what, if any part of the original os remains? Curious if something changed with Google's updates and android versions that remains, causes the underlying issue.

Ducter My son has the same phone, carrier etc he's been on graphene since basically phone release as graphene came out pretty quickly and does not have the issue.

This information is potentially quite useful!

Is his SIM card maybe newer than yours? This is one of the many things that should not matter but sometimes does.

de0u mine is newer, I had to get a new one last year, went from esim back to traditional. He is using traditional as well.

de0u that's av idea. When I get enough time to reflash graphene on my phone I'll give that a go. It takes me a good couple hours to flash Google stock, flash graphene then flash Google stock again to finally flash lineage and get it set up again which is what I've been using in place of graphene.

Ducter It takes me a good couple hours to flash Google stock, flash graphene then flash Google stock again to finally flash lineage and get it set up again which is what I've been using in place of graphene.

Would it be possible to just swap the SIM cards for a few minutes?

de0u yeah, I could try my SIM in his known working phone, at least that would help in determining if its SIM related.

Ducter I could try my SIM in his known working phone, at least that would help in determining if its SIM related.

I would swap both, and try calls from a third phone.

Hello,
I'm on the current build 2024061400.
Pixel 8
Proximus (Belgian network)
Traditional SIM card
4G and 5G
VoLTE on
Battery saver off
Do not disturb off
Wi-Fi on
Wi-Fi calling on (mobile network prefered)
Default phone app.

It happened before the update 2024060500 and after, with or without the original phone app.

I have the log around the time it recieved the call and no ringing nor vibrating. Is it usefull to someone, or should I just wait for an update from GOS or Google ?

Thank you

de0u my phone is currently running lineage, everything works as expected as it does with stock Google. Swapping my SIM into his phone running graphene would help illuminate the SIM being an issue or would point more towards it being an issue. Swapping his into mine I don't know what that would tell us as I'd assume it to work fine. If I'm mistaken, please enlighten me. The issue is with graphene only in my testing but if its build related, an unaddressed upstream change or somehow incompatibility issues with certain SIM cards across various providers I do not know.

Ducter my SIM in my sons phone running graphene works fine in a brief testing period. Put my SIM in and called the phone from several different phones on different carriers and the phone rang every time. I now believe the issue to be graphene itself as my phone running stock Google, lineage and calyx works as it should, only fails on graphene.

I know this is a question that likely won't get an answer because likely not readily known but how many graphene devs are testing coming from the latest Google firmware? I've seen mention several times of blame being put on upstream changes, wouldn't that directly impact the other said operating systems? I know at least lineage and stock are up to date on versions and patches, if they changed whatever code to fix the issue should graphene not do the same? Lineage stopped releases for several weeks to rebase and get things sorted, clearly they knew, found, fixed issues.

other8026
What makes you think it is impossible to troubleshoot? I think the case is rather simple: As soon as you get the missed call SMS you have two informations:

1. timestamp of the SMS. This is the time when the phone is back online again. Which event caused the phone to come back online exactly at this time?
2. time of the call. What happened internally in the phone at the time of calling? In which state was the radio module at the time of the call?

I am no specialist so not able to read the internal logs. But I am sure this can be narrowed down. Maybe it is necessary to increase the verbose level if the default is not detailed enough.
In my case I see three calls to voicebox:

1. Time of call: 26th Jan. 18:25, time of SMS 18:40
2. Time of call: 26th Jan. 18:37 time of SMS 18:40
3. Time of call: 12th June 19:52, time of SMS 20:04

Same issue
Country: Norway
Carrier: Telia MVNO
Pixel 7a
Physical SIM
Wifi calling off
Network selection doesn’t matter
Stock dialer and Google dialer, doesn’t matter.

Started sometime this spring. I’ve given up and switched to an iPhone for now, I cannot use the phone if I’m not getting calls.

This might be unrelated, but I’ve also noticed several times when starting a call that the recipient cannot hear me at all, as if I have muted on my end.