One other thing. It looks like Graphene OS does not come pre-installed with Google Play Services. Summit uses Crashlytics for crash reporting which is part of Firebase which uses Google Play Services. I wonder if this is causing issues. You can also try disabling Firebase within the app. To do so go to Settings > Logging > Log crashes to Google Firebase. Let me know if this helps.

If it’s so bad that your phone is literally heating up by having the app open, it points to an infinitely loop within the app. The only issue is I cannot reproduce anything like it so this infinitely loop must be some rare case. I just have no idea what the case is :/

Just to rule this out, can you check if you have any pending actions that are retrying? You can check by going to You > Your actions > Pending actions tab. This tab should be empty.

Thanks for the feedback. Added to the roadmap.

I did a 20minute test with your exact settings and unfortunately was unable to reproduce anything close to what you saw. I tried browsing both video heavy feeds and just “All” and neither feeds caused any noticeable battery issues.

Just want to sure we cover the all the bases, can you check to see if there is maybe some rogue pending action that is just retrying forever? You can check by going to You > Your Actions > Pending actions. Make sure there isn’t any actions there. If there is could you send me a screenshot (or if it’s sensitive DM me).

Wow that’s insane. 40% in just 1 hour. Bleh back to the drawing board.

Me when a single grain of sugar falls into my pasta sauce.

My goalpost goes to another school.

Thanks for reporting this issue. I think I need to revisit the entire Settings implementation in the future. Settings have to be manually added to search (not hard but I have to remember to do it each time) and sometimes I forget. I’ll add a roadmap item to rework Settings in the future. In the meantime i will add this setting to the search index.

Hello again. I just released a new version of the app with some fixes related to performance/battery usage. Could you please give it a try and see if it helps with battery usage? The release is live as v1.58.2.

Thank for the information. One change which should still help is that the latest release fixed a bug with error identification. Old clients did not identify rate limit errors correctly and just treated them like regular errors. The new release identifies rate limit errors correctly and will retry after a delay. Moreover the latest release has unique error messages for a lot more network errrors. This might help with identifying what is happening. Eg. Whether its rate limiting or cloudflare blocking.

@kratoz29@lemm.ee maybe the issues you observed and went away are related to the changes in rate limits. In any case please give the new release a try.

A new release is now live as v1.58.2. This release has some special logic for rate limit issues. It also comes with some new tools to try to troubleshoot the issues reported on lemm.ee. Could you please give this release a try when you have a chance?

If you are still encountering network-like issues you can try the new tool in v1.58.2. You can find it as Settings > Misc > Client user-agent. This setting allows you to change how Summit appears to the Lemmy server. You can try any of the settings but the one I would try first is “Use test user-agent 2”.

Let me know if the release works better for you or if certain user-agent settings work.

A new release is now live as v1.58.2. This release has a special tool to help with the cloudflare issue. You can find it as Settings > Misc > Client user-agent. This setting allows you to change how Summit appears to the Lemmy server. You can try any of the settings but the one I would try first is “Use test user-agent 2”. Let me know if it resolves the cloudflare issues.

The release is now live as v1.58.2. Please give it a try and let me know if the battery usage is better.

I think a Cloudflare 403 means the server is blocking you on purpose. I’m going to add some features to the app to see if there is some eay around this issue. I’ll update here once they are available so you can test them.

Thank you for sending me your settings. I’ve gotten a couple of performance/battery usage complaints recently. The one commonality I identified so far is “Mark post as read on scroll”. I’ve made some performance improvement changes related to this feature in the next release which will hopefully reduce battery usage.

I’ve been testing with a lemm.ee account for the past several days but I have still not gotten into a state as you’ve described where things refuse to load.

I also reviewed network code within the project however not must has changed there between the latest version and v1.54.x.

I am continuing with the release of v1.58.x which has some performance improvements and some specific changes to how rate limit issues are handled. I’m not sure if it will fix the issue. I will update this thread once that release is fully rolled out.

We believe so! But he was a rescue so he’s likely a mutt.

Have you tried sugar cane. Its pretty close and its sweet too :D