Hello,

Ever since I purchased my Pixel 7 Pro in March of last year and immediately as a first-time user loaded GrapheneOS onto it upon receipt, I've been plagued with a totally ridiculous issue of family and friends being temporarily unable to call me at certain unpredictable times...

This has created some massive inconveniences for me and even worsened some emergency-level situations in the past...

I've been a user of the Google Fi phone service since it was first rolled-out with the release of the 1st generation Pixel. I've had on and off issues with the service over the years but have never experienced something like this, only once I started using Graphene on the Pixel 7.

The issue shows itself as people making an inbound call to my Fi-serviced phone number, and immediately getting my voicemail. They can leave a voicemail too, but my call log will never show that I received a call. Afterwards I'll have these callers send me a screenshot of their call log proving they have multiple call attempts to me. This corroborated by their voicemail and my empty call log clearly identify a major issue in my phone and/or service's ability to receive calls...

I just posted about this on the Fi Reddit page. My attempts to get support from Google Support on this go nowhere, of course. But, I don't want them to know I use GrapheneOS and the AOSP Phone app just in-case those aren't actually the issue and the issue is actually on the service-side instead. So this post is my attempt to figure this issue out on the other end of the fence here...

I have plenty of screenshot evidence to prove the issue as I described above. My questions:

  1. Why does this happen? How could this even be possible?? If an inbound call comes in from the service provider, why would that ever not prompt ringing/notifying/registering in call log, etc.?
  2. Has anyone else experienced this?
  3. Can someone show me the source code link to the default Phone app (presumably AOSP) that GrapheneOS uses?
  4. What other apps could be responsible for this phenomena that I could investigate and what are the links to their source repos?

Any assistance whatsoever is hugely appreciated... Thanks very much!!

  • de0u replied to this.

    Zosh I am not a Fi user, but my understanding is that Fi depends on the Fi app being on the phone and (I assume) having elevated battery privileges. Can you describe your setup along those lines?

    • Zosh replied to this.

        It's 100% either a Google Fi issue or a hardware issue with your phone.

        Turn off 5G (i.e., use LTE-Only mode) and turn off Wifi Calling.

        • Zosh replied to this.

          de0u Yes I've had the Fi app installed since the day I installed Graphene. It's basically just an account management/billing app though. Nonetheless I've had it installed, and it's been allowed background battery usage, if that's what you were referring to.

            spiral I've also had 5G off since day 1 of install, turning off 5G was actually one of the big motivators for switching to Graphene. I just today turned off WiFi Calls from the Fi app, so we'll see if the issue persists with WiFi Calling disabled.

                Zosh you should also turn off wifi calling in the sim settings on your phone.

                A quick DDG search shows that lots of Stock Pixel users have this problem with Google Fi and Wifi Calling.

                  Zosh

                  You might also want to check the APN settings on your phone and make sure they're correct for Google Fi. In most cases, when a sim is installed, the correct APN settings are put in place automatically but it wouldn't hurt to check.