I've had this issue on several Pixel devices - I most recently had this exact issue on my Pixel 6 Pro, but I think recent-ish Firefox updates resolved some of the issues.
In my case, Firefox would lockup, but I could easily switch to another app without an issue. I would have to kill the Firefox app to get it responsive again.
Getting Keycloak and Headscale working together.
But I did it after three weeks.
I captured my efforts in a set of interdependent Ansible roles so I never have to do it again.
If it wasn't better than that, no company would want arbitration cases.
I still have it on my Pixel 8 Pro. It requires a double tap to occur in less than 300 milliseconds.
This bug has been the bane of my existence for almost four years now: https://issuetracker.google.com/issues/204650736
The Android version of the app still has the zoom/cursor offset bug when using a software keyboard from when they sunset RDP 8. That has been a severe usability bug for over three years now.
The Android version of the app still has the zoom/cursor offset bug when using a software keyboard from when they sunset RDP 8. That has been a severe usability bug for over three years now.
CSV only exports data, not formulas. I don't really consider it a proper spreadsheet interchange format.
Right - I wasn't suggesting that it would fix the notification issue, just that it might give the previous commenter the Android environment they're looking for.
They're certainly losing interest in maintaining core Android, which is closer to what I meant. Everything you've described is within their Play Services environment.
Some of what you've said is incorrect as well - I have a third party gallery that works just fine on my stock Pixel 8 Pro. Its access is just managed by a separate permission.
With the Pixel phones, there's GrapheneOS. It might be my go-to one day.
It does!