Does anyone else have the issue of signal’s push notifications coming through dozens of minutes late?
I’m running grapheneos with no sand boxed google services and I find my Signal notifications will come in up to hours after the message was sent. Am I doing something wrong? I think I’ve given signal free reign to use battery in the background but are there any settings I should check?
I had a Signal message come in 20 minutes delayed on GOS with Sandboxed GP.
Afaik, it only happened once.
If it was an ongoing issue, I would split tunnel Signal to see if my VPN was slowing down the traffic.
So I understand correctly that was with sandboxed GPS? Currently I have it not installed but also not running a VPN on mobile. Could the lack of GPS be my issue?
Could be. Without Sandboxed GPS, Signal will have to run all the time to notify you of messages. Have you given Signal unrestricted battery permission?
I use Molly, the Signal fork downloaded from the Accrescent store, which in turn you can get from the GrapheneOS app store. The websockets notifications appear instantaneously so maybe you’ll have better luck with it. You can link your Signal app to Molly in the same profile and then disable Signal when you’re done (don’t un-install it as it acts as the “main” Signal client).
Yea, it’s on the list of unrestricted apps in the battery manager. I thought maybe it’s because signal is in a secondary profile but it shouldn’t. It could be an issue within GOS because I’m also having issues with SMS messages sometimes notifying but being delayed until I force close messages and open it again. I assumed that was because the SMS has to land in the primary and get passed through the profiles but I don’t know the mechanics of it all.
I’ll give that a shot, any other suggestions?
I’m also using GOS with no google play services and my messages work just fine on Signal. Are all messages coming in late or is it just one person? I know when one particular person sends me a message on Signal while they’re at work I’ll receive the message but the time stamp will be different cause it will state the time they sent the message but I just didn’t get it til later cause they have poor reception at their job. Example would be they send me a message at 9:20 but there phone doesn’t send it til 9:40 when it gets a signal. I’ll receive the message at 9:40 but the time stamp will say 9:20 making it appear the message was delayed.
I am not using GrapheneOS and I also have this problem, so it might not be a GOS issue. I send messages from my Android to other peoples phones, both iPhone and Android, and they get notifications for my messages very late (if at all). I’ve made sure it has unrestricted battery permissions and such on all devices involved.
So I only have a hand full of people I’ve been able to convince to join signal just to talk to me (privacy means nothing to so many) so I have a main group chat and individual chats with the same people so my dataset is small but appears to affect everyone equally.
Okay team I have some bad news. I realized I committed the cardinal sin of not searching before posting. After my not google research I’ve found a few reddit posts as far back as 2 years echoing this issue and found a signal troubleshooting guide with fairly pedestrian steps. Unfortunately the best thing I saw was update your signal app and if it persists log an issue with Signal. I appreciate all the recommendations and support, I’ll do better research next time.
https://support.signal.org/hc/en-us/articles/360007318711-Troubleshooting-Notifications
So the solution goes to jellyblurt
use Molly, the Signal fork downloaded from the Accrescent store, which in turn you can get from the GrapheneOS app store. The websockets notifications appear instantaneously