Apps are disconnected as soon as they are minimized
In case I was unclear, I only enabled developer options and made any changes in settings AFTER I was having this issue, which has been ongoing since the very start of installing GrapheneOS. The issue was not present before installing Graphene OS.
This does not mean it's not a configuration issue with your device.
This is clearly an issue with the operating system. My friend has also been trying GrapheneOS for the first time and has been experiencing similar issues, such as Teams and other apps not functioning in the background and completely missing work notifications.
They do not have their device configured correctly. Teams depends on Firebase Cloud Messaging for push notifications which means sandboxed Google Play needs to be correctly installed and configured. It's not intended to function out-of-the-box and ignoring the prompt about the battery optimization exception will cause this, as will having data saver or battery saver enabled.
shroom GrapheneOS does work as intended. It's your configuration which is the problem. The starting point is disabling developer options. The next step if an app preferences reset followed by setting things back to how they should be including giving a battery optimization exception to apps requiring it like sandboxed Google Play services if you use it. If you've made changes via ADB which you haven't precisely documented, there's not much we can do beyond suggesting a factory reset.
- Edited
@GrapheneOS Except that it does not work out of the box with the default configuration, unrelated to any changes I made after finding it to not be working.
Any settings I changed were immediately changed back after changing them did not work. I am still using the default configurations other than ensuring that the app is allowed to run in the background and not having battery saver enabled.
I'm not sure why you are jumping to conclusions that I changed all sorts of settings resulting in having this issue, when I was pretty clear that this issue has been occurring since the OS was installed with no settings changed.
I was posting here hoping that someone could point me to what settings could be interfering with the app being able to run in the background, not being gaslit that I caused the issue by making changes I did not make.
@fid02 No, I did not make any changes like that. I did not change ANYTHING other than enabling developer settings once to try ONE setting that someone suggested, and subsequently turning it back off when it did not work. Developer settings are not even enabled currently and I certainly did not do anything with adb.
"Giving a battery optimization exception to apps requiring it like sandboxed Google Play services if you use it."
I already gave a battery optimization exception to the app having this issue, it did not change anything. I do not think the app is being killed in the background, as it does not have to start back up again after it is disconnected. It is merely being disconnected from the internet any time the screen is locked or it is switched out of the foreground.
- Edited
@shroom May we please know the name of the package and source, so we can attempt to simulate your issue?
The only feedback I have gotten here is that the issue is caused by settings that I have changed, despite me stating clearly that the issue has been ongoing since the device was freshly installed with no settings changed.
The only "setting" that I have changed to attempt to remedy this issue that is still in place is that I have enabled "Exploit protection compatibility mode" for this app per suggestions I read elsewhere on these forums. Should that be disabled?
@GrapheneOS If I "do not have my device configured correctly", then what configurations do I need to look at?
I am also having this (pixel 7a). If I switch away from an app it loses internet. Haven't done any fiddling with the settings, apps are allowed to run in the background
- Edited
There is only so much you can blame on the OS. Login sessions typically expire because of inactivity and you won't know whether the app detects it's been put out of focus unless you analyse the code.