Google is stepping up its game when it comes to UI customization. Google just dropped the Android 17 QPR2 Beta 3 update to eligible Pixel devices, and in...
I had never heard of this. It sounds like lift-to-silence is enabled but that’s not an option in the version of Google’s clock app I have here (version 9.0 (943154005)
com.google.android.deskclock).
It happens on multiple Pixel 10s running Android 16 when an alarm goes off and the screen is not locked.
If you slightly miss the “Stop” button on the alarm notification, that notification will sometimes disappear completely. There is then no way in the UI to stop the alarm and it just keeps getting louder - a real problem in public places. Probably killing the Clock app would do it but it’s easier to shut down the phone.
There is laundry list of other serious bugs that have been a problem on multiple Pixels. A couple weeks ago one phone randomly switched time zones, another (not carrier related) known bug. We use our phones as clocks and it caused a missed appointment.
I have an old Oneplus 6T running Android 11 and it is far more reliable.
Oof. Yeah, that’s ridiculous. With it being a Pixel, you probably have ROM options, but that’s a lot of messing around setting everything up again, for basic functionality that should work anyway.
I use cheap AF Motorolas with more storage than Pixels, call it the “Snapdragon for less” plan. Rip out everything unnecessary with Canta (Shizuku required) and now the battery lasts three days. I’m happy to be on Android 15, for now…
I really like Motorola phones but wanted to run Graphene. Unfortunately it’s a PITA to switch at this point. It will take a day or more to install Graphene and completely configure everything again. The other thing is Graphene is based off the original Android code and I expect most of the same bugs will exist there as well.
Because of the lousy, beta quality software they release I’ve long thought Google employees never use their own products. For example the current version of Maps on the Pixel regularly switches to night mode during the day and won’t switch back, something that should never have made it past their internal beta tests if they actually used their own stuff. Interestingly the few Google employees I’ve known all use Iphones so it seems they hold the same opinion of Android that I do.
You may have already tried playing with the now-very-granular notification permissions:
GrapheneOS is based on AOSP, not Google Android. So, for built-in apps like Clock, you would have “com.android.deskclock” instead of “com.google.android.deskclock”. Both forked from Cyanogenmod. 🤓
I do know it comes from AOSP, but my understanding is that everything first comes (in some fashion) from Google? Is there another path for the source code that does not include Google?
There’s nothing in notification settings or permissions that I’ve found that will fix the alarm problem.
My wife had a minor basic functionality bug when she had a Pixel 3. The phone app would turn the screen on to show an incoming call, then go dark, and she would have to put in her PIN to unlock in order to answer the call. 🤦 I had the same model and no problem, and also could not find any difference in settings or anything that would cause it.
I wish they’d fix some of the more severe bugs. Nothing like having an alarm go off and the notification disappear when I go to turn it off.
I had never heard of this. It sounds like lift-to-silence is enabled but that’s not an option in the version of Google’s clock app I have here (version 9.0 (943154005) com.google.android.deskclock).
It happens on multiple Pixel 10s running Android 16 when an alarm goes off and the screen is not locked.
If you slightly miss the “Stop” button on the alarm notification, that notification will sometimes disappear completely. There is then no way in the UI to stop the alarm and it just keeps getting louder - a real problem in public places. Probably killing the Clock app would do it but it’s easier to shut down the phone.
There is laundry list of other serious bugs that have been a problem on multiple Pixels. A couple weeks ago one phone randomly switched time zones, another (not carrier related) known bug. We use our phones as clocks and it caused a missed appointment.
I have an old Oneplus 6T running Android 11 and it is far more reliable.
Oof. Yeah, that’s ridiculous. With it being a Pixel, you probably have ROM options, but that’s a lot of messing around setting everything up again, for basic functionality that should work anyway.
I use cheap AF Motorolas with more storage than Pixels, call it the “Snapdragon for less” plan. Rip out everything unnecessary with Canta (Shizuku required) and now the battery lasts three days. I’m happy to be on Android 15, for now…
I really like Motorola phones but wanted to run Graphene. Unfortunately it’s a PITA to switch at this point. It will take a day or more to install Graphene and completely configure everything again. The other thing is Graphene is based off the original Android code and I expect most of the same bugs will exist there as well.
Because of the lousy, beta quality software they release I’ve long thought Google employees never use their own products. For example the current version of Maps on the Pixel regularly switches to night mode during the day and won’t switch back, something that should never have made it past their internal beta tests if they actually used their own stuff. Interestingly the few Google employees I’ve known all use Iphones so it seems they hold the same opinion of Android that I do.
You may have already tried playing with the now-very-granular notification permissions:
GrapheneOS is based on AOSP, not Google Android. So, for built-in apps like Clock, you would have “com.android.deskclock” instead of “com.google.android.deskclock”. Both forked from Cyanogenmod. 🤓
I do know it comes from AOSP, but my understanding is that everything first comes (in some fashion) from Google? Is there another path for the source code that does not include Google?
There’s nothing in notification settings or permissions that I’ve found that will fix the alarm problem.
I think that is a fairly recent change. 1.5 years ago?! I’m getting old.
https://www.androidauthority.com/google-android-development-aosp-3538503/
My wife had a minor basic functionality bug when she had a Pixel 3. The phone app would turn the screen on to show an incoming call, then go dark, and she would have to put in her PIN to unlock in order to answer the call. 🤦 I had the same model and no problem, and also could not find any difference in settings or anything that would cause it.