P
pachulo

  • 14 days ago
  • Joined Aug 16, 2022
  • In When are updates to Android auto pushed to Apps repository?

    Hi! I was guessing: which policy applies to push latest versions of Android auto into Apps repository?
    I'm asking because, right now, the latest version there is 11.0.635054-release but in Google Play I can see that 11.1.640234-release, released on the 25 of January, is available.
    Thanks!

    • de0u replied to this.
    • In VoLTE & VoWiFi not working or configurable after CarrierConfig2 introduction

      OK, everything is more clear now; thanks for all the explanations!

      I guess I will have to look at the https://github.com/kyujin-cho/pixel-volte-patch approach while a proper solution to override carrier settings is implemented in GrapheneOS, because it seems that waiting for Jazztel to homologate the newer pixels will take longer.

    • In VoLTE & VoWiFi not working or configurable after CarrierConfig2 introduction

      muhomorr

      Because the connection was not downgrading to HSPA when making/receiving phone calls. Besides, VoiceHD was always active.
      Regarding VoWiFi, as soon as I connected to a WiFi, the mobile network identificator changed to JAZZTEL WIFI, or something like that.

      I've looked into this issue. VoLTE & VoWiFi weren't supposed to be available for Jazztel, they aren't available on stock OS.

      Totally; that's why I asked on my 1st message if there's a way to overwrite the carrier settings now, as this was possible before the introduction of the CarrierConfig2 app.

      You have reported previously that they weren't working properly before:

      That was a problem where VoLTE was only working properly after setting airplane mode on and off after being connected to a WiFi network. I think this was related to an AOSP bug, because it was solved after 2 months or so.

      Thanks for looking at this!

        • In VoLTE & VoWiFi not working or configurable after CarrierConfig2 introduction

          Sure:

          jazztel_es-44000000059
MCC: 214 MNC: 03
MVNO: spn: JAZZTEL
2023-05-11

          Thanks again!

        • In VoLTE & VoWiFi not working or configurable after CarrierConfig2 introduction

          Hi all! I have an Pixel 6a and VoLTE & VoWiFi were both working fine before the latest update. Now they don't work and I can't configure anything related to them.

          I suspect it's related to this change:

          replace our changes to AOSP APN and CarrierConfig configurations with a GrapheneOS CarrierConfig2 app for easier maintenance, improved MVNO support and support for recently added configuration options

          I couldn't find any new application with that name, so my question would be: is there any way to overwrite the network operator provisioned values for VoLTE & VoWiFi support?

          Thanks!

          • In Lift To Wake and Touch To Wake erratic behaviour

            Some good news: after installing the latest update, with tag TQ3A.230605.012.2023061402, the problems seem way less apparent!
            Now Lift to Wake and Touch To Wake both work fine most of the time; they're still not perfect, but way better than before in my case.

          • In Feature Request: VoCrossSIM aka "Backup calling"

            OK, I don't see the option, so I guess it's something the network operator has to support, am I right?

            • In Feature Request: VoCrossSIM aka "Backup calling"

              I've read here that Android 13 supports something called VoCrossSIM, so the phone basically does wifi calling over data from another SIM.
              For it to work, there should be a "Backup calling" toogle in Settings, but I cannot find it in GrapheneOS.
              Are there any plans to activate it?
              Thanks!

            • In GrapheneOS version 2023032600 released

              OK, there seems to be a problem with VoLTE & VoWiFi on my network carrier with latest versions of GraphenOS when they are all activated, meaning that I loose VoLTE after disconnecting from a WiFi connection if VoWiFi is activated.
              At least, VoLTE works fine again after turning on and off airplane mode, so no big deal.

            • In GrapheneOS version 2023032600 released

              Thanks a lot for this! I'm using a Google Pixel 6a and my mobile network carrier is Jazztel (Spain). VoLTE was working fine till some weeks ago but it suddenly stopped working. VoWiFi kept on working fine, by the way.

              With this new version a toggle is there to activate VoLTE and it works...but only for outgoing calls in my case; as soon as somebody calls me, the phone goes back to 3G.

              Is this something that can be solved by GrapheneOS? Or is it related to my network carrier?

              Thanks again!

            • In Widget on secondary profile disappears after closing the session

              Hi! I've configured a secondary profile on GrapheneOS but I have a problem with it.
              When I add the monthly visualisation Google Calendar widget on the launcher, it's not there when I close the session on the secondary profile and open it again...is this a know problem?
              Thanks!

              • In Lift To Wake and Touch To Wake erratic behaviour

                OK, so I'm not alone. Does anybody knows how to debug those kind of issues?

              • In Lift To Wake and Touch To Wake erratic behaviour

                Hi! I've been using GrapheneOS on a Pixel 6a for the last 2 months and it's been a great experience so far, except for some issues with the gestures features.
                I have configured both the Lift to Wake & Tap to Wake gestures, but the problem is that they randomly stop working or behave quite oddly:

                • Sometimes they just work fine, but sometimes it gets really tricky to wake up the phone by lifting it, even when touching the screen multiple times, but in the end the phone wakes.

                • Some other times I just give up and use the power button, after having spent maybe 5 seconds holding the phone on my hand and touching the screen, as nothing seems to make the screen turn on...

                By the way, I don't use screen protector.

                Another thing that bugs me is that I don't really now if they're upstream Android or GrapheneOS issues, as I didn't really use the stock OS when I bought the phone.
                I also wonder if it could be a hardware issue...

                So, my doubts are:

                1. Am I the only one with those issues?
                2. How can I debug issues with the gestures?

                Thanks for any help!