Yeah, there is something wrong with Graphene. It looks like sometimes the OS doesn't send the pause notification to the app when you send it to the background. I am not sure how to solve this.
Discussion
Thanks for looking into it a bit. Glad to know its not Amethyst. Concerned about what Grapheme is doing now. #privacy
This isn't really about privacy yet. We also don't have all the facts on the table.
nostr:nprofile1qqsvzkj6vkvxu745zdx7uw4c2f2d5hzafvzw0z60zmyzsdce9564rpgpzdmhxue69uhhwmm59e6hg7r09ehkuef0lkfddm Can you raise awareness with the Graphene team on this issue? I have the exact same problem.
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
Thank you! Whatever it is, the issue seems to be specific to GOS, not stock Pixel. nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tcpz9mhxue69uhkummnw3ezuamfdejj7qgwwaehxw309ahx7uewd3hkctcscpyug & nostr:nprofile1qqs9g69ua6m5ec6ukstnmnyewj7a4j0gjjn5hu75f7w23d64gczunmgpz4mhxue69uhhyetvv9ujumt0wd68ytnsw43qz9thwden5te0v35hgar09ec82c30wfjkcctexf34p3 need to talk. This has been wrecking havoc on battery life for too long.
