I download the apk file from Whatsapp website to install in GrapheneOS, and I’ve noticed that notifications for messages are very delayed from 15 minutes to no notifications at all until I turn on phone screen and then all of the messages come through. Is there other Whatsapp users with similar issues with functionality?
Signal functions good but there have been times of small delays with messages coming through to get a notification.
Have you installed google services on your phone? they are available through the grapheneOS official “App Store” app. This should be installed before whatsapp is installed (at least that is the instruction for general apps depending on google services).
Perhaps you have done so already, but just a general advice: when using google services and invasive apps like WhatsApp, it can be a good idea to install in their dedicated profile and allow the notifications to pipe through to your main profile instead of installing both in your main profile. If you need help configuring it, let me know.
I know Services is available in a sandbox, I didn’t think of that, presumably because I view it either with disdan or treat is not an option. There’s also MicroG which I’ve never been interested in trying.
That’s the problem. WhatsApp will use GCM for push notifications. No GSF, no GCM.
I have WhatsApp from Aurora store on grapheneOS and occasionally get what you’re describing, but it’s not constant.
I did wonder if Aurora version might function better. I downloaded the standalone apk file in hopes that there would be a removal from such heavy dependancies compared to the Play Store version.
Check here Personally wouldn’t piss on it if it was on fire, but needs must when the devil drives.
For talking with people outside of North America where people still pay to send a text message, getting rid of Whatsapp means cutting off all communication.
Thought it was something like that, hence needs must when the devil drives
A lot of android apps rely on GCM (google’s notification servers), I assume Whatsapp is one. Signal does too, but I think it can use its own websockets when gcm is not available, same for telegram. Whatsapp probably not.
Some ROMs with no google services restore the gcm funciinality via microg. Graphene os, as far as i know, does not have microg.
Hmm not exactly. WhatsApp is closed source, we don’t know exactly how it works, but since it is based on XMPP, chances are high it uses xmpps own push service. Either there would be a notification about missing GCM or firebase.
Btw. Websockets on signal and telegram needs the apps running in background which eats up the battery. That’s why a lot of degoogled-users install unifiedpush via ntfy-app. Some third party alternatives support unifiedpush, signal = molly + unifiedpush and telegram = mercurygram or nagram.
WhatsApp uses Google push notification service which is not available on GrapheneOS. Try to disable all battery restrictions for the app so it can check for notifications by itself but idk if it’ll work still.
Are push notifications even coming to Graphene? I was under the impression they’re inherently insecure and are the modern way the NSA watches all our text activity…
Pretty sure it’s in google services which you can turn on, personally think that waters down the point of Graphene if you leave that on, to the point of pointlessness, but some countries seem to live on whatsapp, more’s the pity.
I think we’re moving to a world where you need a secure device you own and a sucker device a megacorp sees all on to get by, which sucks
Google push notifications are available on GrapheneOS - just have to install Google Play Services. Their sandboxed version of google’s junk is nice because you can fully restrict permissions to it unlike stock Android.
The problem is that restricting permissions won’t change anything in that case. Google push notifications are not encrypted and can be read. If you use them, Google can read them.
Not if the app is coded properly to not include message content in the push notification. Signal uses google notifications only as a wakeup event to poll the (not google) server for the new message.
The apps that are coded properly usually have a fallback option and don’t require the Google’s implementation in the first place.
Like signal?
Yes.
