Mine works but with tmobile sim. Try disabling your wireless signal to force wifi:

WiFi Calling -> Calling Preferences -> Call Over WiFi

    Lucas
    I can confirm Number 2 on Pixel 7 Pro with Play Store and F-Droid. Also had to grant permissions to install apps multiple times in the last weeks.

    joshndroid
    At least with Play Store this option is deactivated per default and can't be activated. For F-Droid I deactivated it right after installation.

    Seems like a bug indeed.

      joshndroid

      Thank you very much for a reply.
      Unfortunately, this cannot be the reason, because I use the apps permanently, and by non-use I mean weeks or even months, but definitely not hours or days.

      kruton
      I'm glad to hear that I'm not the only one with the problem.
      Now I'm wondering, are there any developers reading along here, how do we get this resolved, do we need to create a thread on GitHub?
      I have never done something like this before.

        joshndroid

        kruton

        Since you also own a Pixel7Pro, would it be possible for you to test problem #3 briefly? You just have to go to the developer options, check the box and you will immediately see the current frame rate in the upper left corner, which also has an impact on the battery performance.

        For me, it switches exclusively between 60hz and 120hz, but it should go down to 10hz to save battery, but maybe that is only activated in special situations, in which case I don't understand what that should particularly bring.

        Of course, you can deactivate the developer option again or just observe a bit...

          Google will probably release the next AOSP update for the Pixel smartphones today. Maybe we are lucky and they have already fixed some of the problems in the changelog.
          This should generally be the first bugfix update from Google for the 7Pro.

          Lucas
          Activated frame rate in developer options, can confirm it only switches between 60 and 120 on .y Pixel 7 Pro as well (pretty often and quick interestingly)

            Lucas
            Probably best to wait and see if the AOSP update fixes these issues, if not then to open an issue on GitHub.

              kruton
              Thank you for checking.
              Very interesting and obviously two bugs could be confirmed now already.

              There are three changelogs that can be accessed:

              1) Android Security Bulletin-November
              https://source.android.com/docs/security/bulletin/2022-11-01?hl=en

              2) Pixel Update Bulletin-November
              https://source.android.com/docs/security/bulletin/pixel/2022-11-01?hl=en

              3) Google Pixel Update-November
              https://support.google.com/pixelphone/thread/187593653/google-pixel-update-november-2022?hl=en

              I wonder though, where are the bug fixes actually released that are generally released for AOSP?
              I've always wanted to know that.

              The first two points include only security updates, the third point refers only to the Pixel smartphones, but Google should actually still publish bug fixes for all Android manufacturers, is there no changelog available for this or does this not even happen monthly, with the exception of the security update?

              I've also been having issues with Wi-Fi calling on Pixel 7. Wifi calling worked perfectly on my Pixel 6. Upgraded to a Pixel 7 and it would not work. After many calls with support with my carrier (Telstra in Australia), trying a new sim card and eventually re-flashing GrapheneOS once the Pixel 7 came out of experimental, I still had no luck getting Wifi calling to work. I just flashed back to stock android and wifi calling worked straight away! And then re-flashed to Graphene, and no love. So it seems like it is an issue with GrapheneOS on the Pixel 7. I have raised an issue on GitHub but the account that I created to do so got flagged for some reason so it's not publicly viewable, I hope that means the devs can see it still. In some ways it's a relief to hear you are having the same issue as I have pretty much ruled out everything outside of it being an issue specifically with grapheneOS now.

                free23
                I'm very happy to hear your confirmation of the problem.

                I'm also pretty sure it must be an issue with GrapheneOS, as well as the new Pixel7 generation, at least for certain vendors....

                Since I too had no problems at all with the Pixel6 and the same mobile plan, I rule out other causes on principle.

                Now three mentioned problems have already been confirmed by others.

                I hope some GrapheneOS developer reads along here and becomes aware of this, I'm afraid I have no idea about GitHub as I have no idea about software development.

                I have the same problem on my 7 Pro too. Never goes lower than 60 FPS. Is this a GrapheneOS bug ? I think that's why the screen is still consuming too much energy.

                  free23
                  Thank you for this preliminary work, I have already registered there and will write a comment below the days.

                  Zoltan
                  Very interesting, the more users write here, the more likely it will be solved, but so far it seems that no developer has come up with it yet.