Blastoidea I would give a few suggestions rather than criticize here, because games should and do work on GrapheneOS. But the user is free to decide to switch to stock OS or not at the end of the day.
But OP hasn't given us much to work with.
shroom So my questions to you are:
Blastoidea GrapheneOS doesn't change anything which would interfere with this.
@Blastoidea I would prefer that the operating system works as intended, not
killing off apps that are meant to be running.
yore It has been happening since I installed Graphene. Yes developer options are enabled but mostly set to defaults, I have not changed anything other than what was mentioned in my initial post.
@fid02 I was following suggestions from this very forum.
@GrapheneOS No, it is not due to any changes I made. It has been happening since I installed the OS with all defaults.
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 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.
shroom I was following suggestions from this very forum.
It's unfortunate that someone advised users to permanently enable Developer options on a device not used for development. Even if it is not the cause of this specific issue, developer options in general increases the likelihood of future stability issues and data loss. See this thread for some examples.
Another question which arises is whether or not you have been using adb to make system changes, or if system apps have been disabled or permissions from them revoked. These are relevant questions because the issue you're describing is an unusual one – but can occur if you make these unsupported changes to the system.
Also, it's still not clear which specific app(s) you are referring to.
shroom 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.
If notifications are delayed, your friend can check if Play services have unrestricted background permission enabled as well as granted it unrestricted usage of mobile data.
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.
@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.
@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.
