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 Optimization #22

Open
karmanyaahm opened this issue Jan 3, 2022 · 1 comment
Open

Battery Optimization #22

karmanyaahm opened this issue Jan 3, 2022 · 1 comment
Labels
android android

Comments

@karmanyaahm
Copy link
Member

karmanyaahm commented Jan 3, 2022

This is not the perfect repo for this, but:

Please describe your experiences of battery utilization - list as much information as you know and can publicly disclose, like:

  • The distributor(s) (or any other foreground service apps) (and version numbers) running during that time period
  • Time period
  • Battery usage in apps mode and full device mode (to see full device click on the 3 dots in the top right)
  • Network conditions during that time period (home network/corporate network/mobile network, ipv4/v6)
  • The timeouts and/or configuration of any of the above apps (or just the server if it's a public server not selfhosted)
@karmanyaahm karmanyaahm added the android android label Jan 3, 2022
@karmanyaahm
Copy link
Member Author

karmanyaahm commented Jan 3, 2022

  • Ntfy 1.5.1, Nextpush 1.0.1 and Gotify 2.2.0-UP2
  • 18 hrs
  • Apps mode: Ntfy, Nextpush - both 12% (.66%/hr) Gotify 1% (.08%/hr). Full device mode: information unavailable
  • Home network, None of the connections ever dropped due to small keepalive times anyway
  • Ntfy 45sec (on ntfy.sh), NextPush - 30s, Gotify defaults

It's possible running multiple distributors could've interfered with one waking at a different time than the other. I'll run more tests in the future to rectify that.

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

No branches or pull requests

1 participant