4 ms·
Reasonably happy with GrapheneOS, but the number of bugs (maybe more ecosystem bugs) would make me hesitant to suggest other people rely on it as a communicatio
by mrkeen 3mo ago
Reasonably happy with GrapheneOS, but the number of bugs (maybe more ecosystem bugs) would make me hesitant to suggest other people rely on it as a communication device.
I have notifications turned ON for WhatsApp, Signal and Telegram. I never receive notifications from Telegram. I have to open that app to see if anyone said anything. WhatsApp and Signal notifications seem to vary between late or never? This is despite a constant notification reminder that Signal has Background connection enabled.
Also I can only send messages to some whatsapp contacts. My messages appear as pending for a while and eventually turn into 'could not send'.
- HybridStatAnim8 3mo agoThis is not an issue with GrapheneOS, this is an issue with your configuration, which is trivial to solve. All of those apps support using google services FCM for push notification delivery. I dont think Telegram has a fallback, and Signal and Whatsapp have power-intensive fallbacks. You may also need to reinstall these apps for them to detect google services (apps generally dont check for google services more than once on initial launch).
- classified 3mo agoThat's not how I understand the meaning of "trivial".
- lnfromx 3mo agoYou just have to reinstall you apps using Google Play Store and install Google Play Services
- yolo1897 3mo agoNo, whatsapp fallback to websockets is very power efficient unlike official signal app one, all you need is to set battery optimization to unrestricted for it.
- lnfromx 3mo agoI doubt that however an app solves this problem without FCM or Unified Push can be called power efficient.