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...
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.
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.