nostr:nprofile1qqsvzkj6vkvxu745zdx7uw4c2f2d5hzafvzw0z60zmyzsdce9564rpgpzdmhxue69uhhwmm59e6hg7r09ehkuef0lkfddm Can you raise awareness with the Graphene team on this issue? I have the exact same problem.

Reply to this note

Please Login to reply.

Discussion

Thank you! I'm glad to know I'm not the only one experiencing this issue.

Yeah, this has been an issue for some time. We need to disable the websockets connection when the app goes to the background. Graphene might be just killing the app instead, which leaves the connections hanging 🤔

I've alerted this but note certain situations lets apps still run. I'm not able to reproduce it. Also note minimizing the app =/= closing the app. They're different, you must use the recents screen.

Apps have to go out of their way and have a prominent notification / remain a foreground service and that stops it. Apps and foreground services can also re-start other apps (that's why the disable feature exists)

Anyways CCing so everyone else can see: nostr:nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qz9thwden5te0v35hgar09ec82c30wfjkcctexf34p3

There's an issue aswell with the 'Background Data' toggle, when you restart the device the toggle turns on again.

So much for a private OS. Jeeze.

There's an issue tracker here, but I don't have the expertise or understanding of the issue to write this up. Perhaps someone else can run with it?

https://github.com/GrapheneOS/os-issue-tracker/issues?q=is%3Aissue%20state%3Aopen%20