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

Add app action to trigger auto-upload #13926

Open
trallen opened this issue Nov 1, 2024 · 1 comment
Open

Add app action to trigger auto-upload #13926

trallen opened this issue Nov 1, 2024 · 1 comment

Comments

@trallen
Copy link

trallen commented Nov 1, 2024

How to use GitHub

  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
I am struggling with battery usage on the Nextcloud Android app. I know the team is already working on this, and are doing a fantastic job, so this is not a question of battery usage per se. But I'd like to be able to turn on the normal battery optimisations and still be sure that the auto-upload functionality is working reliably.

Describe the solution you'd like
I'd love to see an App Action added to the app that can trigger the auto-upload functionality directly.

What I'd like to do is add a routine or task with conditions (in my case, when the phone is charging and connected to WiFi, and between certain hours), which then runs the auto-upload intent. Then I needn't be concerned if Android kills the app to save battery when the phone isn't connected to power.

I realise that this is quite a hack, and won't be accessible to many users. However, I'm hoping that it won't take a great deal of work to expose the intent as an app action.

Thank you!

@EmberHeartshine
Copy link

EmberHeartshine commented Nov 2, 2024

Related: #7019. Been an ongoing issue for years; the NC team doesn't seem too interested in addressing it.

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

2 participants