Websocket battery drain workaround.

[deleted]

I currently use an app with a websocket implementation for notifications which drains a lot of battery (I have it set to restricted battery usage). If i install the the version of the app which uses FCM for notifications and revoke network permissions for play services, would that theoretically prevent the app from falling back to using the websocket as it believes it is sending notifications to FCM?

Dumdum

[deleted]
Wouldn't turning notifications off be enough in this case?? Or am I misunderstanding what you want?

mmmm

Dumdum I did think this too. The work around the op seems to be suggesting would effectively just turn off notifications unless I too have missed something.

[deleted]

Dumdum

mmmm

I think turning off notifications from android settings just stops the notification from being displayed to me, I don't think it stops the app from searching for notifications. I currently have notifications off for the app and the background app time is still high and so is the battery usage.

missing-root

Interesting idea. Good apps allow you to disable that, like SimpleX. But I guess as its Signal or Element, the FCM trick could work.

ve3jlg

I don't know. But I have used NetGuard app firewall to prevent or minimize comms from specific apps.You can target the destinations addresses and ports, so often isolate notifications or specific net access by an app.