No notifications after update

clappingChive

I recently updated my OS to latest version on stable release channel. After that I don't get any notifications. Only the sounds play but no notifications pop up. Whenever an alarm rings, there is no way to snooze or dismiss it there is nothing on screen just the alarm tone. I have to go to clock app and turn off the alarm.

Android Version 13
Build number: TP1A.220624.014.2022082400

lberrymage

clappingChive Does this happen with any app besides the default clock app?

GrapheneOS

clappingChive It's unlikely that any of this was caused by an OS update. Perhaps you used lockdown mode which hides notifications on the lockscreen or disabled notifications another way.

DevilsDueRebellion

A bug when using lockdown mode. Not fixed.

greffer

DevilsDueRebellion

This is just to confirm that indeed, there seems to be something going on with notifications not showing:

user (non-admin) profile
using 'Podcast Addict' to listen to podcasts (obviously … ;), notifications in the 'draw-down-drawer' seem to work fine, like progress bar when updating podcasts, 'new episodes available', currently playing episode, etc
before putting Pixel into pocket, I lock the screen; then just listen to the podcasts
after unlocking (PIN), it seems that absolutely no more notifications are displayed when drawing down from top of display … :(
the only thing that seems to rectify this is a restart; 'End Session' and logging in again is not good enough …
just noticed this a short while ago; I need to watch this a little time longer …

I must say that I have never used 'stock' Android 13 before; so I'm not familiar with how things SHOULD work.

GrapheneOS

greffer

Please make a new thread instead of using this one. It's not related to the original topic.

Android's standard Lockdown mode is not a normal way of locking the screen. It also disables secondary unlock and disables notifications on the lockscreen. It's known that there are currently bugs with notifications not being re-enabled after unlocking with this feature. It's not a GrapheneOS specific issue. Locking the screen normally is done with the power button, since the default configuration is for that to lock immediately rather than waiting for the screen timeout. You can control how this works.

greffer

GrapheneOS
Thanks very much for replying … :D

I'll do some further experimenting with the tips you've given.

Not that the issue is that much of a problem to begin with; if I know that notifications are not displayed, I'll simply look for stuff myself …

greffer

GrapheneOS

Locking the screen normally is done with the power button, …

Short explanation: That's what I'm trying hard to AVOID; these mechanical buttons are the greatest points of failure on a phone. I've got an old device that WOULD work perfectly fine—if it wasn't for ALL buttons being defective …

GrapheneOS

@DevilsDueRebellion appears to have figured out their issue was tied to Lockdown mode. Removed the older posts because it would be very confusing and misleading for anyone else who searches for this and comes across this thread.

mythodical

greffer I might just be lucky but in the more than twenty-four years that I've used cell phones, not a single phone has experienced a failed button. Your phone is very likely to age-out of firmware support long before the buttons fail.

greffer

mythodical
Thanks, good to hear … and yes, maybe the Pixel is a bit sturdier than one of my previous devices ;)

Yet: why take a risk when there's nothing to gain? I found an 'assistive touch' app that seems trustworthy; I can now lock the screen and adjust volume without touching those mechanical buttons … ;)