Cwtch not great at staying alive on Android (GrapheneOS) #717

New Issue

n00q · 2023-09-06T23:50:47Z

n00q commented

2023-09-06 23:50:47 +00:00

I have been using Cwtch on an Android phone running GrapheneOS for over a year now. Despite trying to fiddle with all the possible related system settings, I have never been able to keep Cwtch running for more than 24 hours. Cwtch will shutdown or "log out" or otherwise become offline (without a notification) and require logging back in. I assume this is due to the system shutting down Cwtch, and I understand it can be difficult to keep apps like Cwtch online and running on Android, especially without something like Google Play Services.

However, I do not have the same problem with the very similar app Briar on the same phone. Either when both Briar and Cwtch are running at the same time, or when one or the other running. Briar never has any trouble staying open and online. Cwtch never lasts over 24 hours.

I find this to be a great impedance to using Cwtch on my phone as a reliable communication tool, since I have to remember to check if I'm online, and re-enter my password periodically. There isn't a notification telling me when Cwtch has gone offline, so I am also not alerted right away.

I'm not sure if this is a problem specific to GrapheneOS (which I can see being more aggressive and shutting "idle" apps), or general for Android.

Happy to try any suggested tests or possible hidden settings that could help! If this is an issue beyond just Graphene, I can imagine improving Cwtch's ability to stay alive would be really good for a Stable release!

I have been using Cwtch on an Android phone running GrapheneOS for over a year now. Despite trying to fiddle with all the possible related system settings, I have never been able to keep Cwtch running for more than 24 hours. Cwtch will shutdown or "log out" or otherwise become offline (without a notification) and require logging back in. I assume this is due to the system shutting down Cwtch, and I understand it can be difficult to keep apps like Cwtch online and running on Android, especially without something like Google Play Services. However, I do not have the same problem with the very similar app Briar on the same phone. Either when both Briar and Cwtch are running at the same time, or when one or the other running. Briar never has any trouble staying open and online. Cwtch never lasts over 24 hours. I find this to be a great impedance to using Cwtch on my phone as a reliable communication tool, since I have to remember to check if I'm online, and re-enter my password periodically. There isn't a notification telling me when Cwtch has gone offline, so I am also not alerted right away. I'm not sure if this is a problem specific to GrapheneOS (which I can see being more aggressive and shutting "idle" apps), or general for Android. Happy to try any suggested tests or possible hidden settings that could help! If this is an issue beyond just Graphene, I can imagine improving Cwtch's ability to stay alive would be really good for a Stable release!