Graphene OS intermittently fails to ring for incoming calls

https://9to5google.com/2024/04/22/google-pixel-april-update/

It seems to be a upstream bug.

The new update fixed it for me.

Pixel 7 Pro, on 2024042100 which includes the AP1A.240405.002.B1 update from upstream Android.

Still experiencing calls straight to voicemail, but only sometimes. I haven't identified a pattern of which callers work, or don't work.

Things I've tried:

A power-off, remove SIM, wait 2 minutes, reinsert SIM, power-on cycle suggested by my carrier (Telus).

Turning off 5G by setting the option to LTE.
Reset Mobile Networking option.

studog

Ok. My problem seems to have been I had turned on "Do Not Disturb" mode in the phone app.

Coming from an LG G7 Thinq, where DND is an OS-level item that affects all notifications, I had been unable to find the same OS-level DND on my Pixel 7 Pro, and ended up enabling the DND in the phone app when I found it. I thought it would turn off automatically I think, like the OS-level version.

This explains why things sometimes worked and sometimes didn't; certain contacts are starred and certain aren't.

jagorom515 It doesn't change that these are carrier bugs. New releases of AOSP / stock OS can work around more of them but they are carrier bugs.

GrapheneOS
A Google software update caused the issue
A Google software update fixed the issue

My phone was working fine until March 13
My phone was broken after March 14
My phone was working fine again after April 22

I'm not sure where a carrier bug fits in here sir/mam. It feels like it was more of a modem bug introduced by an UPDATE (March 14) and not a change in my carrier. The Apr 20 update, which had the vendor update to AP1A.240405.002.B1, seems to have fixed that modem bug.

I'm not very tech literate, so please forgive me if we are both talking about the same thing and I am being too dense about it, but it felt like you were denying that the March Google Update was not responsible for the issue.

Again to be clear, I am not saying it was a Graphene issue or anything. It clearly was an upstream problem given the amount of non-GOS users facing this issue.
I'm a big fan of all the work you folks do and I love using the OS. Thank you!

jagorom515

You know what they say.

Walks like a duck, quacks like a duck, it’s a carrier issue.

Just today my 6a experienced the "call straight to voicemail" problem and also could not make or receive any calls. I have ONLY one profile and am updated to the latest OS version. This is the first time I have ever seen this. I just Reset Mobile Network Settings ( Settings/System/Reset Options/Reset Mobile Network Settings) then rebooted the 6a and everything worked properly.

I experienced this 3 times this week. I reset the network settings and didn't touch it since. But today I got 2 calls from same guy. 3 minutes apart. 2nd one was not received. I'm on newest gos version. Pixel 8

Same issue for me, clean install pixel 8 pro. I can make calls but when trying to call the phone, no ringing, no notification, nothing, just goes directly to voicemail.

So after trying to get the phone working every which way I knew I ended up returning to stock Google build, tested phone and it worked immediately, flashed lineage, worked immediately and has continued to. Is there an actual known issue that I can keep an eye on the change logs to know if/ when it's fixed?

I've had intermittent issues with incoming calls this month.
Not sure if might be something to do with adding more user profiles or my carrier who recently sent me a new SIM.

New build was released I see, noting in the change logs about phone not working but was wondering if anyone has tried it? My issue was incoming calls wouldn't work at all which is a piety basic requirement for me. If the new build solved the issue I'd love to hear that.

Ducter I don't know for sure, but I'd suspect the issue people are reporting here is an upstream one. It's possible QPR3 has fixed the issue, but I don't know if it has. Only way to find out is to try, but keep in mind alpha/beta releases might have other issues.

I have the same issue. No wifi calls enabled, signals strength very good. Call goes straight to voicebox even when the phone is unlocked. I get a message from the carrier about a missed call half an hour later. This occurs very rarely so it's hard to track.

Ducter lineage

It's my understanding that they're behind on updates and their patch level isn't exactly 100% accurate, so it's possible that a new bug was introduced at some point by upstream AOSP that just isn't in LineageOS. The reason I think it's unlikely to be because of a change GrapheneOS made is because GrapheneOS, to my knowledge, hasn't changed any code that would affect this sort of thing.

I am sure people want this fixed, but it's not really possible for the developers to troubleshoot and fix a problem when they don't know how to reproduce it. I'd help if I could, but I seem to always get notified of all incoming calls, even if I actually end up ignoring all of them.

other8026 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. The priority should be how severe the problem is and this one is rather high. I use my phone for business so if a call does not go through I may loose a client.

In cases like this one it's sometimes needed to improve diagnosing. I.e. we would be interested on any carrier message about missed calls where at the time of the call the signal strength was good.

I can also see in the list of carrier messages that I had the first occurence of the problem on January 26th. It occurred four times since. That's not a lot but still cumbersome.