Strange, I had more problems with calls with the stocks OS that I ever did with Graphene. Most of the issue I have now seems linked to weather events, like high winds.

And some weird pattern that I want to look deeper into. I have seen a few hard to define anomalies that seems related to some data being received by IMS prior to said anomaly. Might just be a misconfigured tower or the nature of 4G/5G network itself. There are likely more efficient ways to do this but you might want to have a look at the system logs, I used "ims" as filter. The output is not that overwhelming on desktop.

I would call the carrier, from my experience they tend to play dumb and still change a few settings in the background regardless.

I reinstalled my Salto Homelok (because I need to be able to lock my door), and the problem reemerged. So at least we know it has nothing to do with Whatsapp.

Got a tag for locking the door now and will try to live without the Salto app for a while to see if the app really is the issue. Most probable is that it's the Salto app that does something with Android, and nothing really Graphene related.

    luddevig Thanks for the update! This still seems a bit mysterious.

      I thought that if the mic is turned off, no one can use it. What's the solution for this?

      And does is it the same issue for the camera and location as well?

      Having issues as well.

      I have a physical sim and an E-sim active, and I can't receive calls on either. When someone calls me, they hear "this number does not exist" on the physical sim, and they hear "this number is not available at this moment" on the E-sim. I can call others normally, however.

      Using a Pixel 7a with a Vodafone e-sim.

        MichaelJohn
        Hi Michael,
        is your physical SIM from a reseller aka discounter, I mean a provider without its own cell network?
        Maybe a new one on the market? Then sometimes it is possible, that your phone number isn't reachable from every other network, as long as not all providers have updated their databases.

        Or it's much easier: this physical SIM card is a little bit older or you have touched the SIM's chip contacts while you had the SIM card in the drawer. This can result in a static discharge, which damages the chip. Although this is rare, it cannot be completely ruled out.

        First mentioned case can also be the reason for the error message from your eSIM.
        Have you already checked the call forwarding settings in your Pixel phone?
        You can find them in the phone app. These can also change after inserting a new SIM card or activating a new eSIM profile!
        So even if you've already checked them before, it's better to check them now again.

        Good luck!

            MichaelJohn Same issue here also with Vodafone Germany and physical Sim. But if I call immediately again (my partner who has also Vodafone Germany) it works normaly

                Eagle_Owl thank you for the effort post. I tried to access the call forwarding settings on both SIMs, and on both, after some time loading, it ultimately gives me a "SIM access error".

                You're right about one of the SIMs being brand new in the market (in this case, Digi), that's the physical Sim, and I'm not so concerned about that one.

                The one that concerns me is Vodafone, because it's well established in my country and worse, it's my main number. It's an eSIM, so it's extra inconvenient that it's giving me issues. It's the phone number I have for all my banks also.

                  MichaelJohn
                  Since we are not seeing widespread reports of this and there are a lot of GrapheneOS users in Germany I wonder what is different about your circumstances.
                  Have you removed permissions from or disabled any system apps? Have you made any changes to your phone via adb? Any other unusual/invasive changes you have made, like changing dev options, rooting ?

                      luddevig I reinstalled my Salto Homelok (because I need to be able to lock my door), and the problem reemerged.

                      This is unexpected. Had a quick look at that app and the only thing that appeared possibly relevant is its Bluetooth capabilities. Did you have these problems when at a different location to your locks? Maybe some weird bug where the locks could be acting as the mic when you are on a call?

                      Can see the app has very few reviews on Play Store and looking at them looks to have had problems.

                        Carlos-Anso no to all of the above. I'm at a loss myself because it just started happening. I'm currently abroad and perhaps there are some problems with the connection, so I'll report back when I'm back in my country of residence.

                            MichaelJohn to me it happened also abroad (Portugal). I landed today in Germany and so far (2 calls) the issue didn't reoccur. Just out of curiosity:

                            • are you directly with Vodafone (I use Wetell and theyre on Vodafone)?

                            • And was VoLTE in the country you have been supported by Vodafone (in Portugal my calls were on 2G)?

                                I had the same exact problem on and off for over a year now. I switched my main phone for receiving SIM based calls to my iPhone and literally 0 problems. It was something to do with either the google pixel hardware or the graphene software, because the exact same SIM in the exact same location in an iPhone had no issue.

                                Seems like google needs to get their crap together. Between my fingerprint reader working about 25% of the time and not being able to use my phone for :: PHONE CALLS :: is ridiculous for a >$700 handset

                                ZoraIsHere you may have discovered powder, since I am Also in Portugal and I'm having the problem here.

                                What is hilarious is that the SIM card that is giving me issues is Vodafone Portugal... I went to Vodafone and they couldn't identify any problems on their end, so I assumed the issue was related to GrapheneOS.

                                Now I'm at stake zero again.

                                    hi eagle_owl. just joined dont have a sim yet. with australian carriers as you say not providing privacy & the likes of tangerine leaking info on the dark web do you have any advice for esim or sim. i dont have a problem with anyone phone tampering physically but there are reasons to want as much privacy & unhackability as possible. any advice in any area of privacy is appreciated.

                                    12 days later

                                    MichaelJohn Do you still have the issue? I was in back in Germany for 2w and now I'm back in Portugal and so far had no issues with Vodafone in Roaming regarding call drops etc. I only have huge problems with call quality which I already posted here but from what I understood your issues are not regarding quality, they are regarding the call drops or it doesn't even ring.