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.

            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.