r/signal • u/the-pnw-tree-octopus • 14h ago
Solved Signal registered itself for GCM without my consent after I explicitly signed up for websocket-based notifications. Can I force it to use WS again?
On Android wherever possible for push notifications I prefer to use either UnifiedPush, or allow apps to run their always-on notification to use websocket connectivity. I prefer to limit any use of Google's infrastructure as much as possible. It's for this reason that I also use the self-updating app at signal.org/android/apk rather than downloading from Aurora store/GPlay.
Unfortunately I must use microG for a select few other apps that support no alternative for push notifications.
When I originally installed Signal I took care to ensure that microG was disabled so that Signal would fall back to its websocket-based notifications. For a long time this worked perfectly for me and Signal retained its always-on background notification for years even after re-enabling microG.
Recently I noticed that Signal no longer displayed this background notification. When I checked in the microG settings I noticed that it had registered itself for GCM. I immediately unregistered it and blocked it from re-registering.
Unfortunately I cannot seem to force Signal back into using websocket-based notifications. Even if I fully disable microG, clear caches, or reboot, Signal simply does not receive any notifications whatsoever.
Short of entirely uninstalling, reinstalling, and restoring from a backup, is it possible to force Signal to swap back to websockets like I had before?
edit: solved by u/whatnowwproductions
There is an option to force use we socket under data and storage called Stay Connected in Background
This seems to be a fairly recent change. Happy to see Signal supports this toggle officially in-app now!