Comment on Google Confirms Non-ADB APK Installs Will Require Developer Registration
markko@lemmy.world 3 weeks agoI wasn’t denying the fact that you’re experiencing this issue, but since this is the first I’ve heard of something this bad in my 3 years of using GrapheneOS, this does appear to be a fairly unique case.
Provided you are using an otherwise well-functioning and currently supported device (and not an emulator), and that you are using a stable release installed via an official method (and there were no install issues), your best bet would be to ask for help in one of the community chats or forums: grapheneos.org/contact#community
You will be asked to share which device you are using though, which you did not seem comfortable doing in the post you linked to.
Unrelated, but I learned about the Android “task manager” (Running Services) from that post of yours, so thanks for sharing that.
LodeMike@lemmy.today 3 weeks ago
That’s not a proper task manager
markko@lemmy.world 3 weeks ago
That’s why I put it in quotes. Being able to view the RAM usage is useful though. Best of luck with resolving your issue.
LodeMike@lemmy.today 3 weeks ago
Thanks. It seems the only option is to restart the phone every day. It’s manageable.
markko@lemmy.world 3 weeks ago
Yeah that unfortunately seems to be the only option if you don’t want to completely reset your device or remove apps one at a time to find the culprit. And there’s no guarantee either of those will work anyway.
I’ve actually found a small number other users reporting a similar issue, though dev responses all seem to believe the issue is likely caused by apps rather than the OS. The fact that the issue is exclusive to GrapheneOS doesn’t appear to have swayed them into looking into it unfortunately.
If I were in your position I’d probably use the Auto Reboot setting so at least you don’t have to do it manually every day. It reboots after a specified number of hours without an unlock, so it’s ideal for when you’re asleep.