Delayed FCM/push on new Pixel8Pro

F0g

I bought a refurbished Pixel 8 Pro and installed GrapheneOS on it.
I have used Graphene on the Pixel 6a now for years and everything worked great.
I set up the new Pixel 8 Pro completely from scratch, no seedvault backup etc.

I installed the Sandboxed Google Play apps and some other Apps like Signal or Protonmail.

And now I'm experiencing extremely unreliable FCM push notifications on the whole phone.
If I start the apps that are using FCM, like Signal, the foreground process is pulling new messages, but nothing via the background process.
Lately I've been getting Signal messages with a delay of 1h.

I read the installation guide and also set the background use of the battery to unrestricted, but that doesn't affect the push notifications at all.

I never experienced such a thing on any Graphene device, I installed a lot of them.

Maybe someone have an idea what could be wrong here?

Thank you very much!

GrapheneOS

F0g There are other potential causes beyond not having Unrestricted battery for Play services such as having Data Saver enabled without an exception or Battery Saver. Turn off developer options if they're enabled.

soi44

I can confirm the same issue on the Pixel 9 Pro, which is fully updated. Signal push messages (FCM) are delayed from a couple of minutes to several hours if the screen is locked and the phone is untouched. The same goes for calls; they get missed.

GrapheneOS

soi44 Check the configurations mentioned above.

linux-dev

I noticed the same today. When I picked up the phone and unlocked it I received the notification for a message that was sent already 7 minutes ago. This is with element x and google push

This is the first time I have experienced it.

GrapheneOS

linux-dev That's likely a Matrix server issue, especially if you're not having any other problems. If you're using matrix.org, it's known to be very unreliable.

F0g

GrapheneOS

Thank you very much for the feedback!
Apparently data saver and battery saver are completely turned off.

Is there any other thing I can do?
Is there any point in the log of the FCM where I can search for potential exceptions?

Thanks!

soi44

GrapheneOS In my settings, Data Saver is off, Play Services has "Allow background usage" turned on, and battery usage is unrestricted. Developer options are disabled. All of these settings have remained untouched since I started using GrapheneOS (more than 9 months ago). I began experiencing these issues about a week after a recent update.

DeletedUser495

soi44 do all other push notifications work well? Does Signal come from Google Play or did you download it from another source before/after installing sandboxed Google Play?

soi44

DeletedUser495 I’m using Molly and Signal, and both have the same issue; both use FCM. Signal was installed from Google Play, while Molly was installed from F-Droid. I don’t have any other messaging apps, so I can’t definitively confirm that all notifications are affected.

F0g

DeletedUser495

All my apps, which have a dependency in FCM, are affected like Signal, Protonmail, banking apps, postal mail apps etc.

DeletedUser495

F0g I am using Molly with websocket and unrestricted battery and experience none of the sort. On occasion notifications may be delayed a few minutes but I guess this is related to websocket implementation.

I am sorry I can't be of better assistance but if this was happening to me, badly affecting my experience, I would back up all I can and do a factory reset and then reinstall everything starting with properly setting up Play services first and then looking at all possible toggles that may be relevant to apps I am using.

Shining1337

I recently got a Pixel 9 and GrafeneOS.
I installed Google Play Services and exempt "Google play Services" and "GsmCompactConfig" from battery optimisation.
Afterwards, i installed apps like Discord, which do not seem to get any push notifications what so ever. When Google Play Services and Discord asked for notification permissions, i allowed them.

Am i doing anything wrong or has anyone figured out what causes this yet?

Shining1337

Shining1337 EDIT: It was DNS! D: aaaaa
I have a DNS blocker (Pi-Hole) running and https://github.com/GrapheneOS/os-issue-tracker/issues/3354#issuecomment-2011000862 helped me find the right domains where i noticed that some were blocked.

de0u

Shining1337 Thanks for reporting back!