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.

                                  Just an update , seems when I have owner plus one user profile open fingerprint login is not an option .

                                    Skyway Upstream bug that has been around for a while, though it seems more prominent with QPR3. It will have to be fixed upstream in all likelihood.

                                        Skyway This is a very annoying bug. I just switched to a user profile to use a payment app and now after switching back to the main profile, my fimgerprint is no longer working no matter how many times I relock and unlock the device. Now I need to restart the device in order to make the fingerprint work. So, if I need to switch profile 5 times a day, I need to restart my device 5 times in order to use fp. Not sure if alpha/beta testing guys even report any issues or if they just use alphe/beta because they want updates before everyone else.

                                            SoulKeeper multiple users test alpha / beta builds. Bugs or lack of them reported in #testing:grapheneos.org on Matrix, in addition to this forum.

                                              SoulKeeper As @DeletedUser115 said, people do test releases. What you may not necessarily realize is that the second to last update brought us Android 13's QPR3. This next release that you're commenting on right now (2023061402) is the second release that was made in the same day to address issues found during alpha/beta testing.

                                              The issue you're experiencing, like most other bugs come from upstream. GrapheneOS tries to but cannot fix every single upstream issue, and it's usually up to Google to get those issues sorted out.

                                              If it is something that only affects GrapheneOS, the team tries to address it ASAP.

                                                  matchboxbananasynergy
                                                  Very early testing but my p6p does not have this issue.
                                                  Two things
                                                  1 I have 5 apps installed across 2 profiles
                                                  2 this is the alpha release of 061402 not sure if this matters .
                                                  Could this be a ram issue as my p6 is my daily phone with lots of apps installed which is having the fingerprint issue ?

                                                    mv10201 After playing around, I've noticed that at boot up if I "Pause" the boot and then resume, the swipe from the lock screen works and I can enter my passcode ok. Everything works as normal. The next time the screen locks, I have to power cycle the phone and do the pause-resume to continue.

                                                        mv10201 I ended up doing a "Data Reset" and it seems to be working normally.

                                                          lots of new bugs in release. Fingerprint stops working randomly. Launcher crashes all the time so task switching does not work 90% of the time. I cannot have more than 1 app open at a time. How do we downgrade? I updated because liked the feature of pin not animating to prevent shoulder surfer but this is too many bugs.

                                                            • [deleted]

                                                            • Post #33

                                                            gosrox

                                                            Downgrade isn't possible for security reasons.

                                                              SoulKeeper I also have this issue but I noticed that unlocking an app protected with fingerprint unlock in the owner profile also re-enables fingerprint unlock for the owner profile. So that might be a temporary workaround that does not require a reboot.

                                                                matchboxbananasynergy this is the launcher crash that has been causing my headache since updating

                                                                java.lang.NullPointerException: Attempt to read from field 'com.android.internal.util.LatencyTracker com.android.systemui.shade.NotificationPanelViewController.mLatencyTracker' on a null object reference in method 'void com.android.systemui.recents.OverviewProxyService$1$$ExternalSyntheticLambda9.accept(java.lang.Object)'
	at android.os.Parcel.createExceptionOrNull(Parcel.java:3027)
	at android.os.Parcel.createException(Parcel.java:3005)
	at android.os.Parcel.readException(Parcel.java:2981)
	at android.os.Parcel.readException(Parcel.java:2923)
	at com.android.systemui.shared.recents.ISystemUiProxy$Stub$Proxy.onStatusBarMotionEvent(ISystemUiProxy.java:360)
	at com.android.quickstep.SystemUiProxy.onStatusBarMotionEvent(SystemUiProxy.java:287)
	at com.android.launcher3.uioverrides.touchcontrollers.StatusBarTouchController.dispatchTouchEvent(StatusBarTouchController.java:79)
	at com.android.launcher3.uioverrides.touchcontrollers.StatusBarTouchController.onControllerInterceptTouchEvent(StatusBarTouchController.java:109)
	at com.android.launcher3.views.BaseDragLayer.findControllerToHandleTouch(BaseDragLayer.java:183)
	at com.android.launcher3.views.BaseDragLayer.findActiveController(BaseDragLayer.java:193)
	at com.android.launcher3.views.BaseDragLayer.onInterceptTouchEvent(BaseDragLayer.java:163)
	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2653)
	at com.android.launcher3.views.BaseDragLayer.dispatchTouchEvent(BaseDragLayer.java:303)
	at com.android.launcher3.dragndrop.DragLayer.dispatchTouchEvent(DragLayer.java:225)
	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3121)
	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2802)
	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3121)
	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2802)
	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3121)
	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2802)
	at android.view.ViewGroup.dispatchTransformedTouchEvent(ViewGroup.java:3121)
	at android.view.ViewGroup.dispatchTouchEvent(ViewGroup.java:2802)
	at com.android.internal.policy.DecorView.superDispatchTouchEvent(DecorView.java:500)
	at com.android.internal.policy.PhoneWindow.superDispatchTouchEvent(PhoneWindow.java:1912)
	at android.app.Activity.dispatchTouchEvent(Activity.java:4307)
	at com.android.launcher3.Launcher.dispatchTouchEvent(Launcher.java:2111)
	at com.android.internal.policy.DecorView.dispatchTouchEvent(DecorView.java:458)
	at android.view.View.dispatchPointerEvent(View.java:15309)
	at android.view.ViewRootImpl$ViewPostImeInputStage.processPointerEvent(ViewRootImpl.java:6774)
	at android.view.ViewRootImpl$ViewPostImeInputStage.onProcess(ViewRootImpl.java:6574)
	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:6030)
	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:6087)
	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:6053)
	at android.view.ViewRootImpl$AsyncInputStage.forward(ViewRootImpl.java:6218)
	at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:6061)
	at android.view.ViewRootImpl$AsyncInputStage.apply(ViewRootImpl.java:6275)
	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:6034)
	at android.view.ViewRootImpl$InputStage.onDeliverToNext(ViewRootImpl.java:6087)
	at android.view.ViewRootImpl$InputStage.forward(ViewRootImpl.java:6053)
	at android.view.ViewRootImpl$InputStage.apply(ViewRootImpl.java:6061)
	at android.view.ViewRootImpl$InputStage.deliver(ViewRootImpl.java:6034)
	at android.view.ViewRootImpl.deliverInputEvent(ViewRootImpl.java:9202)
	at android.view.ViewRootImpl.doProcessInputEvents(ViewRootImpl.java:9153)
	at android.view.ViewRootImpl.enqueueInputEvent(ViewRootImpl.java:9122)
	at android.view.ViewRootImpl$WindowInputEventReceiver.onInputEvent(ViewRootImpl.java:9325)
	at android.view.InputEventReceiver.dispatchInputEvent(InputEventReceiver.java:267)
	at android.view.InputEventReceiver.nativeConsumeBatchedInputEvents(Native Method)
	at android.view.InputEventReceiver.consumeBatchedInputEvents(InputEventReceiver.java:247)
	at android.view.ViewRootImpl.doConsumeBatchedInput(ViewRootImpl.java:9282)
	at android.view.ViewRootImpl$ConsumeBatchedInputRunnable.run(ViewRootImpl.java:9416)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1231)
	at android.view.Choreographer$CallbackRecord.run(Choreographer.java:1239)
	at android.view.Choreographer.doCallbacks(Choreographer.java:899)
	at android.view.Choreographer.doFrame(Choreographer.java:824)
	at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:1214)
	at android.os.Handler.handleCallback(Handler.java:942)
	at android.os.Handler.dispatchMessage(Handler.java:99)
	at android.os.Looper.loopOnce(Looper.java:201)
	at android.os.Looper.loop(Looper.java:288)
	at android.app.ActivityThread.main(ActivityThread.java:7937)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
	at com.android.internal.os.ExecInit.main(ExecInit.java:49)
	at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
	at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:355)

                                                                    gosrox

                                                                    How did you capture this? I will do the same next time it happens to me.

                                                                    Most of the time, though, I do not get an alert that launcher crashed - I simply notice that I have no more recent apps listed.

                                                                        spiral the crash dialog box pops up after the 3 or 4th crash in a row then tap more details