Guys, I'm new to this. My phone (7 Pro) is still on 2023060700 and says the device is up-to-date when I ask to update. Is this ok? Are 2023061400 and 2023061402 not stable versions?

    Hb1hf

    Releases are first pushed to alpha, then announced, then goes through beta before stable. It stops at either alpha or beta if it turns out a new release is needed before it can be considered stable.

    It takes too long to finalize system update compared to stock Pixel update. Is it normal? I have a 100 mbps wifi connection.

      SoulKeeper Only downloading the update uses your internet connection. Verifying, installing, validating and finalizing does not. Finalizing takes significantly longer than the stock Pixel OS if you have a lot of apps since we use full ahead-of-time compilation instead JIT compilation with only very sparse use of ahead-of-time compilation based on JIT-generated profiles. This is also why installing/updating apps takes longer on GrapheneOS. It saves battery life and improves performance of the Java/Kotlin code at runtime compared to the stock OS approach, but that's not why we do it. It's an important security feature. Also, not having profiles of which parts of apps you use could be useful in some situations, but isn't why we do this.

      GrapheneOS installed the update at around noon today (Pixel 4) and on firstpower up it was difficult to get the passcode screen up. once up, logged in as usual. The next time the screen locked I couldn't swipe up to get the passcode screen. After a few attempts, the phone restarted and now that's the loop it's in.

        After installing/rebooting into the update, I got a notification from system updater saying:

        Failed to check for updates
        An error occurred checking for the latest update. The update system will try again soon.
        Binding socket to network 100 failed: EPERM (Operation not permitted)

        I then checked for updates manually and the message did not recur.

        I have noticed a visual glitch after the latest update. When I enter PIN/password and unlock the device (P7a), the lock screen wallpaper flashes for a millisecond before going into home screen wallpaper. This doesn't happen when I unlock through fp scanner. Turning ON/OFF enhanced PIN privacy makes no difference.

          Everything fine for me. Big thanks to the team !

          For me as well, everything worked with my mobile Pixel 6a and the restart after the update was ready in a few minutes. But I also only installed 16 additional apps.

          Thanks a lot for to the whole development Team and the fast update and quick reaction and trouble shooting.

          Pixel 6a issues:

          • screenshots crashing with apps running on work profile "System UI has stopped working"
            • screenshots are fine with apps running on main profile
          • recent apps list gets cleared every time app switcher is opened
            • just moving back to home clears the apps list too

          I have two issues after the recent update as well
          1 getting the pin login screen to stay open is had some times . similar to mv10201

          2 fingerprint login isn't always an option .

          spiral I'm not sure if this is a device specific bug but here you can follow these steps to check.
          Press the power button to wake up the device > You will see the lockscreen wallpaper > Swipe up to open lock screen keypad > Now you will not see any wallpaper; only the keypad is visible > Enter the PIN and click on the arrow beside that to confirm > You will see the lock screen wallpaper appears for micro second before going into the homescreen. Previously, it used to go into the home screen directly after confirming the PIN.

            SoulKeeper

            Thanks for the detailed steps. I'm able to confirm what you've reported using these steps but only IF there is a separate wallpaper for both the lock and home screens.

            I'm able to confirm this on both a Pixel 6a and Pixel 7. Both are running TQ3A.230605.012.2023061402

              SoulKeeper I had set up the same wallpaper for the lock screen and home screen. With different images I can confirm the behavior. The black screen when entering the password I had interpreted as a strange feature instead of a bug. Basically nothing really serious, but now I see it also rather as a bug.

              spiral Are you saying you have also observed this bug if there are different wallpapers on lock screen and home screen? Sorry English is not my first language.

                SoulKeeper
                Your English is great!

                Yes, it seems to be that the behavior you're reporting can only be observed if there are different wallpapers for home and lock screens.

                I have never noticed this myself because I have never had a wallpaper on my GOS Pixels (only black screen), so to be honest, I'm not sure how this behaved before the latest update. I only wanted to confirm that the behavior you observed exists on my devices IF there are two different wallpapers active.