Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Android app v 3.26.0 drains much more battery than before #11983

Closed
4 tasks done
lckarssen opened this issue Sep 21, 2023 · 2 comments
Closed
4 tasks done

Android app v 3.26.0 drains much more battery than before #11983

lckarssen opened this issue Sep 21, 2023 · 2 comments
Labels

Comments

@lckarssen
Copy link

lckarssen commented Sep 21, 2023

⚠️ Before posting ⚠️

  • This is a bug, not a question or an enhancement.
  • I've searched for similar issues and didn't find a duplicate.
  • I've written a clear and descriptive title for this issue, not just "Bug" or "Crash".
  • I agree to follow Nextcloud's Code of Conduct.

Steps to reproduce

  1. Upgrade Nextcloud Android app to v3.26.0.
  2. Use phone in the same way as before
  3. Observe battery emptying more than before. The Nextcloud app is listed at the top of the list of battery consumers.

Expected behaviour

The Nextcloud app should be found somewhere at the bottom of the list of top power consumers.

Actual behaviour

The app is found at the top of the list of battery power consumption. In my case it is now using roughly between 8% and 12% of battery, easily beating Firefox at ~7% and Always on Display at ~ 5%.

Android version

13

Device brand and model

Samsung S22

Stock or custom OS?

Stock

Nextcloud android app version

3.26.0

Nextcloud server version

27.1.0

Using a reverse proxy?

Yes

Android logs

No response

Server error logs

No response

Additional information

No response

@joshtrichards
Copy link
Member

This seems related to #11974 (comment) so let's focus on addressing that. If this matter remains afterward, we can re-open it.

@lckarssen
Copy link
Author

This seems related to #11974 (comment) so let's focus on addressing that. If this matter remains afterward, we can re-open it.

The issue has remained, unfortunately. Instead of reopening this issue, I think follow-up in #7663 makes more sense.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants