• General

  • Graphene OS intermittently fails to ring for incoming calls

Have the same issue, it happend back in december but stopped at some point when i got a new provider, then it started happening again withing the last 2-4 weeks. im at a point where 50% off calls don't come through and have to revert back from graphene until this issue is solved.

    applesbana Yea i noticed now i must have missed that reply. My bad. but kinda make it suck more since then i have no option until google fixes the issue.

        Empress

        I’ll admit, I keep my old iPhone as a backup for situations like this. Google hardware has been finicky for me over the years from battery life, sim issues, and fingerprint readers

            Seeing GOS release notes about CarrierConfig2 app, but I can't find it in the GOS "Apps" application. Has anyone tried using CarrierConfig2 instead of the Google CarrierConfig? Would that potentially fix the issue?

            applesbana applesbana It's not a Pixel or GrapheneOS issue but rather a carrier or app issue. It could mean the carrier lacks reliable VoLTE support when it's being used. For apps, it's generally caused by having a broken configuration without push fully working. For example, Signal or Molly without Play services with unrestricted battery usage not granted to them. Unrestricted battery usage is more hidden away than before since Android 14 QPR2. You need to press the text next to the toggle for background battery usage to access the menu for enabling unrestricted usage.

            applesbana It's not a Pixel or GrapheneOS issue. An iPhone won't fix issues with your carrier, unless the issue is that they don't follow standards in a way that only impacts certain devices.

                    Having VoLTE or Wi-Fi calling enabled when it doesn't work with your carrier will cause problems. Enabling LTE-only mode if you don't have working VoLTE will break cellular-based calls. Your carrier may have flaky LTE / VoLTE where it sometimes works but doesn't work in other cases. These are carrier issues.

                      GrapheneOS

                      I appreciate the detailed response.

                      Someone previously posted this which could lead one to believe it’s related to the pixel specifically (not graphene):
                      https://support.google.com/pixelphone/thread/264865035/pixel-7-pro-not-receiving-calls-after-march-2024-update

                      My specific location has no issue with missed calls when using an iPhone, so my anecdotal experience tells me it isn’t a carrier issue unless the carrier is misconfigured on my graphene pixel but correctly configured on my iPhone

                        I'm having this issue too. Lost many incoming calls, most of them actually.

                        GrapheneOS

                        Hi!
                        Non-native speaker here, please excuse my language. Not trying to be rude, just summing up stuff from what I've seen this past month.

                        The new issue that has been bugging everyone since March - it IS a Pixel issue.
                        I and many others are having this issue as well.
                        Before March 14, I could use WiFi Calling and VoLTE just fine with my phone/sim. My carrier supports it. Been using GOS on my P7 from day 1 without any issues. This new call drop issue started happening the day I updated my phone with March 14 update.

                        I have another device(non-pixel) using the same sim card, calls(VoLTE and WiFi calling both) and text messages work fine without any issues. So yes, currently using an iPhone/any other backup device will help!
                        I also opened a service request with my ISP, went to their office and spent a few hours, but they couldn't troubleshoot anything and concluded that it's a device issue (albeit it felt like a generic - "we've checked everything, and it's not an issue from our side, so must be your phone" response)

                        Other threads for this issue:
                        https://discuss.grapheneos.org/d/11866-pixel-8-dual-sim-physical-sim-no-calls/12
                        https://discuss.grapheneos.org/d/11890-cell-service-drops/9
                        https://discuss.grapheneos.org/d/11990-grapheneos-version-2024040900-released/15

                        External:
                        https://www.reddit.com/r/GooglePixel/comments/1c0bmp1/performance_after_marchapril_updates/
                        https://www.reddit.com/r/GooglePixel/comments/1beh3gl/pixel_7_unable_to_receive_calls_after_march_update/
                        https://support.google.com/pixelphone/thread/264865035/pixel-7-pro-not-receiving-calls-after-march-2024-update
                        https://www.androidpolice.com/pixel-network-issues-missed-calls-texts/

                        From what I've seen it is affecting phones from P6a to P8P. It is very random though, since not everyone is seeing the issue.
                        I have a friend using P7 who is unaffected, a friend using P8 who is affected by the issue. Both using Stock OS, and they have the same carrier as mine.

                        Again, to be clear - we are not saying this particular thing is a Graphene issue. Since a lot of people using Stock OS are also reporting this issue. But since the latest release notes mentioned something about carrier config, we got our hopes up that the update could potentially fix the upstream issue

                        There has been no official response from Google yet. I keep opening these links every day, only to find more affected people but no fixes :(

                        Edit:
                        I'm happy to work with a dev to help debug this issue if needed.

                        Edit 2:
                        For those affected, this is a temporary fix that works for me - https://discuss.grapheneos.org/d/11866-pixel-8-dual-sim-physical-sim-no-calls/11
                        Doesn't work for everyone though, so fingers crossed!

                            jagorom515

                            I appreciate the work you did in summarizing the issue and helping pinpoint it to being device specific.

                            Not sure why @GrapheneOS seemed to believe it’s not possible for this to be a pixel specific issue but would love if they could close the loop and acknowledge it’s possible/likely this isn’t carrier specific as they claimed. This isn’t an attack on graphene os in any way, but rather about the hardware that graphene of course does not produce.

                              Pixel 6a with Graphene OS user here.
                              The first time I encountered this issue was actually already back in December last year. Suddenly a notification of a missed call, although the phone didn't ring and the call should have gone through. Since I rarely get any calls and didn't notice anything unusual I didn't think much about it. It once happened again in February.

                              Just now after reading a few fix suggestions, I disabled "4G Calling" (I assume that's what my carrier calls VoLTE). Wi-Fi calling wasn't enabled in the first place. And then I could no longer receive test-calls nor make outgoing calls. But I've been using LTE-only mode and had "Allow 2G" disabled. Only after changing both (I tried changing only either), test-calls worked again normally. I guess this might be expected, but I hadn't given it any thought before.

                              I've re-enabled "4G Calling" and hope that without LTE-only mode and with "Allow 2G" enabled this issue won't reappear.

                              I was unable to make calls without VoLTE turned on so decided to re-enable that and WiFi calling. No issues in 2 days.

                              This happened to me again today. It is frustrating because I don´t receive many calls. The ones I do receive are generally very important and 50% they fail to reach me as I only either get a notification that I missed a call or simply receive an sms telling me that I missed it. The phone was in front of me on my desk the whole day...

                              5 days later