on the 16th October release, Pixel 8 Pro:
when i take a screenshot and immediately press the Edit icon on the screenshot notification at the bottom of the screen, it says it's not possible. I have Google Photos installed.
I can edit the screenshot when I then go into Google Photos myself and open the screenshot myself.
Link for where it’s confirmed, current experimental p8/p8p don’t have the hardened kernels
After buying my original iPhone back in 2007 and many more in the years that followed, i just flashed my first android phone (Pixel 8 Pro) and I can't believe how easy it was!
The only thing I can't get working is the Pixel Watch 2 that came with my phone. It worked with stock android but after installing GrapheneOS the Watch app crashes in the last setup step with the text "Additional Legal Teams and Disclosures". I click accept and the app crashesh. When I reopen the app I see that the watch is connected but there is a message stating something went wrong and opting to reset the watch to factory.
I see more posts of "prompting to reset the watch to factory" even on stock android so I don't know if it is something GrapheneOS related.
But great work!
applesbana Thx for that... will read...
Whats the next phase? Beta -> Stable?
rover87 Have you activated the Pixel Watch service on a device running something other than GrapheneOS? You need to do that first. There is some unpublished dependency that GrapheneOS is missing in order to activate cell service in addition to needing the Play Store, Google Services Framework and/or Google Play Services.
See this thread for more information: https://discuss.grapheneos.org/d/1236-pixel-watch-and-grapheneos
[deleted] I don't think that's required.
rover87 The only thing I can't get working is the Pixel Watch 2 that came with my phone. It worked with stock android but after installing GrapheneOS the Watch app crashes in the last setup step with the text "Additional Legal Teams and Disclosures". I click accept and the app crashesh. When I reopen the app I see that the watch is connected but there is a message stating something went wrong and opting to reset the watch to factory.
Make sure play services has the nearby devices permission, and install the "Google" app (the app is literally called Google). Then, go through the setup again and let us know if it doesn't work.
matchboxbananasynergy I don't think that's required.
You don't think what's required?
Is there any update if face unlock is secure enough for GrapheneOS?
I dont think they have had time to evaluate that yet. For now, there is no face unlock in gos. But hopefully we will see that later.
DeletedUser124
The Pixel 8 is Class 3 biometric security (could be used for banking applications), so I really hope too that it will be supported at some point
Confirming as an Australian on the Telstra network that the current release is working quite well on my Pixel 8 Pro. Only had a few little issues, like the pull down and app navigation gestures not working, and mobile data refusing to autoconnect. Been a good 6 hours since they've resolved though, and the phone is otherwise perfectly fine, including banking apps. Great job, guys.
EDIT: I don't use biometric security features, so cannot comment on face or fingerprint unlocking. PIN and password are working fine though, as you'd expect.
Hello, first of all thank you for the great operating system - I am a first time user (Pixel8Pro) and really excited! The version runs very stable and I can rarely find errors. Great job!
What I noticed:
NFC switch does not respond - if I press it for a long time and get into the submenu, I can then turn NFC on and off without problems.
Other buttons (Internet, flight mode) react - but sometimes a bit sluggish.
I noticed some silent notifications that shouldn't be possible to dismiss by swiping (e.g. Disconnected from always-on VPN) can actually be dismissed. Is this a bug?
matchboxbananasynergy The Google App did it! Thanks!
ope_ape_a For the NFC quick toggle, check whether it actually doesn't respond, or if the toggle just doesn't change.
To test this, try disabling it or enabling it through the quick tile, and then check if the toggle worked through the setting.
If it has changed, but the quick tile's state hasn't changed, I believe this is due to an upstream AOSP bug and is not specific to 8th gen Pixels.
MrSmith
Ok I confirm this is a bug as according to the docs foreground services notifications shouldn't be dismissable, but currently are: https://developer.android.com/develop/ui/views/notifications#foreground-service
It can be reproduced by using Signal (downloaded from the website) without Play Services installed. The "Background connection enabled" notification can be dismissed.
I'm still unsure about the "Disconnected from always-on VPN" notification, as according to the same doc there was a change for some notification that can now be dismissed where it was impossible before: https://developer.android.com/develop/ui/views/notifications#android_140_api_level_34
But it seems weird to me that such important notification could be inadvertently cleared, so it may be a bug in this instance too.
matchboxbananasynergy
thanks for the quick answer - it's your 2nd guess: only the quick tile's state hasn't changed.
