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

Battery consumption is too high since the latest update #935

Open
5 of 9 tasks
ghost opened this issue Aug 22, 2017 · 8 comments
Open
5 of 9 tasks

Battery consumption is too high since the latest update #935

ghost opened this issue Aug 22, 2017 · 8 comments

Comments

@ghost
Copy link

ghost commented Aug 22, 2017

Since the latest update, Twidere is draining my battery. Even with the application closed, and using it for about 10-15 minutes per day, Twidere is at the top of battery consumption.

Android version: 6.0.1 Marshmallow

Network type:

  • Wi-Fi

App version: 3.6.24

Build variant:

  • Google

Micro-blogging service:

  • Twitter

App settings:

  • Custom API
  • Custom consumer key/secrets
  • Official keys
  • Using Thumbor
  • Connected through proxy
  • Media preview enabled
@oscarmlage
Copy link

I've noted the same here with Android 8 Oreo

  • App version 3.6.24
  • Micro-blogging service: Twitter + Mastodon

@brackenhill-mob
Copy link

Same problem in v3.6.29. Have gone back to v3.6.21

@Spinus1
Copy link

Spinus1 commented Oct 17, 2017

Same problem using 3.7.1.
It seems that twidere background process is periodically started, even if I kill twidere app; it is very strange, since I've disabled backround updates in twidere settings...

@mariotaku
Copy link
Member

I found the root cause to power draining problem. There'll be a fix for this in next release.

@andyleejordan
Copy link

@mariotaku Don't leave me hanging! What's the root cause? I'm curious.

@mariotaku
Copy link
Member

mariotaku commented Feb 17, 2018

@andschwa When a refresh task failed in background, it may keep device awake since old implementation only release wakelock after task finished successfully. Now with background service completely rewritten, wakelocks are released despite whether tasks successful or not, and all tasks will have a deadline to finish forcefully after a period of time.

@andyleejordan
Copy link

Oh cool. Thank you. Can't wait to try it out!

@eladhen
Copy link

eladhen commented Mar 15, 2018

The battery consumption is crazy on 3.7.3.

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

No branches or pull requests

6 participants