phillip Odd. How about: Settings, System, Reset options, Reset mobile network settings?

    Thanks very much for the reply @de0u ! I tried this per your suggestion but it didn't seem to have any effect 😕

    Pixel 8
    Google Fi

    I have also experienced this issue
    Also unable to send/receive sms via default Messenger app while on non-owner Profile

      Same problem here too.
      Google Fi
      Pixel 8
      Tried disabling private DNS. No luck.

        This morning I dialed in to a zoom call since mobile data isn't working. I was getting disconnected from the call consistently after about 2-3 minutes

        I am delighted to report I found a fix for this!

        Settings -> users -> [select user] -> install available apps -> toggle the radio selector for Google Fi

        This is it! Note that for me, I didn't need to sign in to the app on the guest account, only have it installed. Hope it helps others 👍

          5 days later

          de0u
          I tried to toggle Google Fi for the second profile and had no luck. Tried a few times and did few reboots. Will keep looking for a solution...

              squart

              What does this mean "tried to toggle Google Fi for the second profile and had no luck". Can you give us more details on exactly what you tried, and what was the result?

                  7 days later

                  phillip

                  Second profile: uninstalled Google Fi, then reinstalled it.

                  There have been some OS updates since this issue started and I am not receiving SMS on second profile intermittently but still have to switch to main/admin profile in order to send sms or make calls.

                    5 days later

                    +1, also experiencing this. Pixel 9 Pro, Google Fi, Release 2025032500. I started experiencing this after Release 2025030900.

                    I tried the suggested solution above from phillip to install Google Fi in other non-owner user accounts, and that seems to have fixed the issue for now. This seems like an odd fix, and it definitely had different behavior prior to this. I see that there is an issue on Github tracking the same problem: https://github.com/GrapheneOS/os-issue-tracker/issues/5059