GrapheneOS It's almost certainly a configuration issue with your device.

Perhaps, but I don't think so. Same as OP, I've been experiencing this lately. Maybe it's always been like that and I'm the one who didn't notice before, but one thing is sure: I've haven't touched the system configs in months.

And it's not just online push notifications for me, but also local stuff such as BatteryBot alerts. I was actually prompted to come back to this post after just having received a "seedvault backup failed" notification from 43 minutes ago, from when I tried to perform a manual backup.

Yesterday i upgraded to Alpha channel, right now using Android 14, same behavior as above as far as this problem is concerned.
In the morning I disabled do not disturb mode, signal spent 10 minutes trying to retrieve messages, the weather widget spent more than 20 minutes with the wheel spinning trying to retrieve the latest information. Apps seem to be having trouble regaining connectivity after exiting do not disturb mode.

Display options for hidden notifications > Custom >

  • Don't turn on the screen enabled
  • Rest of options disabled (yesterday i performed some changes, i had enabled an option that prevented the applications from receiving notifications or so I seemed to understand, I think that in Android 14 they have renamed some of these options)

Same problem since updating to Android 14. It's affecting all apps that use FCM push messages. Play services is and has always been unrestricted. It's definitely an issue with either the update, or some coincidental google services update.

5 days later

Is there any way to receive push notifications with sound across profiles/users?

Profile 1: No Google Play Services
Profile 2: Google P. S. installed with network and notifications allowed.
Both with "Send notifications to current user" enabled and both user active.

Profile 1 get push notifications from profile 2 but I need to lift/unlock the phone to see them. No sound or vibration.

I've been using gOS only a couple of days and still getting familiar with it so maybe I overlooked some settings.

My notifications are coming through but when I get a large number in a group like from X for example they stop showing the alerts. Is there some kind of limits on Android?

Also when I swipe down the notifications menu I can only read 8 messages in a group even though there are 40+ in the the X notifications group.

What's the consensus (or default) for battery usage for all of the Google apps included in GOS? Should they all be set to unrestricted?

Also, I had a problem recently with Molly showing extremely delayed notifications.

    router99 Unrestricted for Google Play Services, optimized for the others. I have Molly set to unrestricted on my phone as well. I believe I get all notifications on time.

    I knew I will find this thread.

    I can confirm I am facing the same issue on P7 Pro with the latest update.

    Molly (using its own notification method), Simple Calendar Pro (afaik it uses its own method too), Whatsapp, Messenger Lite - either no notifications at all or VERY delayed and only when I open these apps manually. When I reboot the device, it shows all the missed notifications and then doesn't display new ones or displays with huge delays.

    Battery is Unrestricted on all these apps/Google services.

    This is certainly an update / Android 14 issue as all this was working perfectly fine prior to Android 14 update.

      Volen

      Same for me, but for Signal using GCM. Messages are, when phone is idle for x minutes, delayed by 10 min. Seems to be related to sleep/doze configs, because I got ca. 10% more battery life with Android14 compared to 13.

      router99 Molly needs Unrestricted battery mode to do push. It requests that and you need to grant it for that to work properly.

      This doesn't appear to be GrapheneOS specific:

      https://www.reddit.com/r/signal/comments/170rxvo/android_14_pixel_7_pro_delayed_notifications/
      https://www.reddit.com/r/GooglePixel/comments/170zxv6/android_14_delayed_notifications/

      Not clear if it's an issue with these apps, Play services, FCM service or Android 14 but other users have the issue on the stock OS. It only appears to impact a small number of users with specific configurations, otherwise there would be more complaints.

      3 months later

      As of today, somehow my notifications are back to normal as far as I can tell. I don't know what triggered it, but happy to see it 😎

      5 days later

      I have a security (trail cam) using Ucon app to alert me when someone starts up my driveway. Running on both Pixel 5 and Pixel 6 with all notifications set correctly for app, battery settings correct, etc. and Display->Lock Screen->Wake for notifications set.

      I get correct notifications if screen is on and for maybe 5 minutes after screen is off. After that, notifications are there but never wake the screen from sleep. As soon as I tap to wake the notifications are there. I even went into Developer Options and turned off Wi-Fi scan throttling and didn't help.

      Notifications are instant (icon shows on status bar) when I wake from sleep, so the app is sending the notifications correctly.

      Guess I spoke too soon. After phones sitting overnight, when the cam sent a push notification this morning it didn't wake up and notification sat waiting until I woke phone from sleep. SMS message notifications always show up. Tried running Wi-Fi on P6 and Cellular Data on P5.

      Consistent notifications is pretty fundamental stuff. Really frustrating to not have these wake up the phone, even set to show on Lock Screen and wake lock screen.

      • de0u replied to this.

        The Ucon app uses several notification channels but the three main ones are Push, Misc, and System. Through testing by setting each to Urgent to get a popup toast it appears that the app is using Miscellaneous. Most of the time notifications arrive within 10 seconds after the camera trips from motion. Occasionally notifications are delayed 1-5 minutes (unacceptable for using the cam as security as someone tripping it at the bottom of my driveway would already be at the front door by the time I receive the alert.

        The issue is notifications are NOT waking the P6 from sleep after the screen has been locked for a period of time. I have tried the following settings and apps that specifically wake on notification:

        GrapheneOS - Display->Lock Screen: Wake screen for notifications
        Automate app - using 'Wakeup on notification' Flow
        aodNotify for Pixel app - (very cool notification LED simulation and AOD preview options) Wake Screen setting ON
        Glimpse Notifications app - set Lockscreen display time and Persistent notification set ON
        Wake Up Screen app - simple wake on notification

        In every single case, these all will wake from sleep and show notifications (depending on how they're configured) IF the P6 screen was locked within the last 5 to 10 minutes. Any longer than that, it never wakes up on notifications. When I tap to wake the notification icon is in the status bar waiting and I immediately get a notification sound and if set to Urgent, a popup toast. Adaptive Battery is off, uConn and these notification apps are not restricted by battery optimization. But something is happening after a certain sleep time to keep notifications from waking. Very frustrating, been at this for two whole days testing and trying all combination of options and settings still no joy.

        de0u People reviewing the camera (Sehmua H-10 and using the Ucon app) don't seen to be having notification issues and are happy with the results (using stock Android).

        Forgot to mention that sometimes notifications show up 10 minutes late. Not sure if it's the notification just arriving or the phone finally wakes up from a pending notification that's been sitting there.

        Running the Automate 'Get all current notifications' flow, I pulled up the detail for a Ucon notification and it's using FCM. Perhaps the connection to FCM is getting closed in sleep? Throwing everything at the wall to see what sticks...

        • de0u replied to this.