Graphene OS intermittently fails to ring for incoming calls

Same issue 2 days ago call right to voicemail I thought this was fixed now have to check phone every 1/2 hour or so, I was doing this in March and April because was happening a bunch of times. No Wi-Fi calling just the straight up dialer that comes with OS. This is the most basic function of a "cell phone". It happens sometimes but once is to much and when u think it's fixed starts again. Can't be carrier cause were all on different ones in different countries. I don't get many calls at all so for me having it happen; must be brutal if u get a volume of phone calls coming in on a regular basis. This needs to get fixed.

I'm not sure if being on graphene and then getting an update maybe makes the missed calls random or what but for me, clean install and it happened every time. Couldn't get the phone to ring at all. If it was random, happening seldomly maybe I wouldn't have noticed right away but as a small business owner every call is important.

I know a few weeks ago lineage had to do a hard pause for several weeks while rebasing so perhaps it is an upstream issue that they fixed or something... Idk. Hopefully the graphene team can figure it out.

Happens here too, Pixel 7. Never bothered to report it as I just call back but today happened twice.
Wifi calling disabled.

Can someone remove the solved tag please?

Can anyone advise if either of the last 2 stable releases addressed the issue?

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

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.

Ducter What happens if the two of you swap SIM cards temporarily?

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.