So far everything works perfectly for me. P6P.
GrapheneOS version 2023061402 released
@SoulKeeper @greenmonster This sounds like a potential visual bug/glitch introduced upstream with QPR3. Unfortunately, a lot of upstream bugs are introduced this way, and it's something that they would have to fix on their end.
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.
- Edited
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
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.
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.
SoulKeeper Don't apologise for your english : they don't apologise for not speaking your languuage !
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.
matchboxbananasynergy
I know I made a post about first login after switching profiles . but this is after first login.
Thank you .
- Edited
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.
- Edited
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.