• [deleted]

Try Settings > System > Developer options > Suspend execution for cached apps, set to Disabled. It will ask you to reboot. You will find more apps run for longer which may help with notification but may be heavier on the battery. Revert if you don't see improvement.

    [deleted] my setup was working just fine 2 updates ago, I don't believe switching this will help, plus, I have this issue in Pixel 5 and 7

    gonzalo

    Yes, the last two updates boost the problem with Signal and whatsapp. I need to open the app or switch on/off airplane mode.

    Tutanota uses its own daemon (they refused to use push because privacy concerns), i'm having problems with notifications more than 1 year ago, some friends with new pixel phones using tutanota have the same issue.

    [deleted]

    Thanks, i will try. At the end of the day my battery shows about 60-70% so i'm not worried about.

    treequell

    Sorry, i'm not sure about the meaning of FCM. I have enabled Play Store. I know tutanota and whatsapp are using its own daemons, signal is using push (Google play version) I think apk uses its own daemon.

    In Device Notifications and apps, Launcher is enabled and Google Play Services are disabled.

      Any idea on this? It's getting really annoying

        gonzalo

        You have to be patient, the developers do a selfless job that we all appreciate. I know it is sometimes frustrating when it comes to a major failure. The last days whatsapp and signal notifications arrived sharp (very rare), but with signal I have always had a problem, you call a person and you get a tone but the other person's phone doesn't ring, it also happens with WhatsApp, but that already happened to me with stock android.

        Regarding tutanota, you can't blame graphene, as I told you many friends use their service, we all have problems with notifications from time to time, this failure occurs with both google stock and graphene, so we can't blame graphene . The thing about tutanota is worrying because if you don't enter it manually, you can have emails that arrived days ago and they use their own daemon to avoid push, little by little they are improving it but it still has quite a few bugs or deficiencies. In this case you can get angry because many users are subscription users and failures take a long time.

          Icecube Sorry, i'm not sure about the meaning of FCM. I have enabled Play Store. I know tutanota and whatsapp are using its own daemons, signal is using push (Google play version) I think apk uses its own daemon.

          FCM means Firebase Cloud Messaging, and it is the connectivity provided by Google Play Services app for delivering push notifications.

          Have you installed Google Play Services, Google Play Store and Google Services Framework and given them all the network permission?

          If you have Google Play Services installed, I believe WhatsApp and Tutanota will use Google Play Services for push notifications. They will only fall back to their own implementation of push notifications if you uninstall Google Play Services.

            treequell any of the last updates changed any of this? Because I didn't

            Icecube I understand the patience, I wanted some update on the issue and don't let the thread died because clearly something changed since 3 weeks ago all this worked sharp and well.

            treequell FCM means Firebase Cloud Messaging, and it is the connectivity provided by Google Play Services app for delivering push notifications.

            Thx, now i understand.

            treequell Have you installed Google Play Services, Google Play Store and Google Services Framework and given them all the network permission?

            Yes, i have just done it. All of the were installed.
            About permissions:
            Google Play Services -> Contacts, Network and SMS (Notifications disabled)
            Google Play Store -> Network, Notifications and sensors (Notifications enabled)
            Google Services Framework -> Contacts and network (Notifications disabled)

            treequell I believe WhatsApp and Tutanota will use Google Play Services for push notifications. They will only fall back to their own implementation of push notifications if you uninstall Google Play Services.

            Tutanota is one of the few services that does not use Google Push

            I think Tutanota deployed FCM because google can read the subject and so on, but i'm not sure if f-droid apk has its own notifications daemon and Google play version uses FCM.

            May read the last comment of the article:

            bad-at
            2/2/2020

            Will the app from google play store continue to use google push?
            Tutanota
            2/2/2020

            No, it does not use Google Push, it's exactly the same app that you can get form F-Droid.

            Signal and Whatsapp are using push notifications. So the issue it still there :(

            Icecube gonzalo For apps using FCM, you need Unrestricted battery mode for Play services. For apps using their own background push service, you need Unrestricted battery mode for the app. Many apps like Signal use FCM when available and their own push when it's not available. Apps doing their own push need to run a foreground service which must create a non-hidden persistent notification which the user can disable without breaking it. It will show up in active apps when the service is running, so you can see when it's running the push service.

            Google Play services does not create the notifications for apps. FCM is not a push notification service but rather a push messaging service. It delivers messages to the apps and they handle the messages.

            Icecube There's no indication of any GrapheneOS issue for any of this. It's almost certainly a configuration issue with your device. You haven't said anything about your battery optimization configuration for Play services or apps doing their own push. All the apps you listed likely using FCM via Play services for push when it's available, and some of them will do their own push when it's not available. Their decision about using their own push may be done statically on first launch after install or app data reset rather than dynamically at each app launch. It depends on how the app chose to do it.

              GrapheneOS For apps using FCM, you need Unrestricted battery mode for Play services

              I just checked "Play Services" (Unrestricted Battery) . I think is the default configuration.

              GrapheneOS For apps using their own background push service, you need Unrestricted battery mode for the app

              Yes, for example Tutanota uses its own push system, so after installing it the Unrestricted battery mode was selected as recommended by the application developer.

              GrapheneOS Apps doing their own push need to run a foreground service which must create a non-hidden persistent notification which the user can disable without breaking it. It will show up in active apps when the service is running, so you can see when it's running the push service.

              Yes, I remember seeing it before in a messaging application called conversations, a chain icon is showed in top bar.

              GrapheneOS There's no indication of any GrapheneOS issue for any of this. It's almost certainly a configuration issue with your device. You haven't said anything about your battery optimization configuration for Play services or apps doing their own push. All the apps you listed likely using FCM via Play services for push when it's available, and some of them will do their own push when it's not available. Their decision about using their own push may be done statically on first launch after install or app data reset rather than dynamically at each app launch. It depends on how the app chose to do it.

              As I said in the previous paragraph, Play Services battery optimization is properly set (Unrestricted Battery) and Tutanota too. Of course Signal is using FCM so i keept (Optimization battery).

              Tutanota -> Run notification service in foreground (random fails with unrestricted battery
              Signal -> Runs FCM (random fails)
              Whatsapp -> Runs FCM (random fails)

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

              Agree, if only two people have that error, it is the most logical thing.
              Thx

                Icecube

                I just checked "Play Services" (Unrestricted Battery) . I think is the default configuration.

                It's not the default, but our compatibility layer makes a notification requesting it and you must have accepted them as intended.

                Agree, if only two people have that error, it is the most logical thing.

                Do you have battery saver or Do Not Disturb enabled in any way?

                  GrapheneOS Do you have battery saver or Do Not Disturb enabled in any way?

                  I checked Battery saver, it was disabled.
                  Do Not Disturb, Yes, i enable it manually at night before going to sleep and I disable it again when I wake up.
                  I have observed that it causes problems in applications like tutanota (notification service in foreground)

                  GrapheneOS Also, the Play Store is enabled, right? Play services depends on the Play Store.

                  Of course, it's enabled. I install and update the applications through the play store.

                  Want to report similar delay on notifications happen to my Pixel 7 as well.

                  Build Number is TQ3A.230901.001.2023100300. Gms, GSF, Google Play Store, and Google Play services all installed. Unrestricted battery usage permission given to Play services. Signal on the latest version. Also is given unrestricted battery usage permission.

                  Someone was calling me on Signal, and my Mac showed the call notification but my Pixel didn't. I had to open Signal on Pixel to see that there was a call coming. There were also multiple times where I had to open Signal to see I missed messages that were sent 30 minutes ago.