-
-
Notifications
You must be signed in to change notification settings - Fork 0
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 sync interval and/or manual update #326
Comments
There used to be an option to pick an interval between 15 and60 minutes, as well as manually refresh. Both were removed due to a lack of use, but you should see battery refresh when you launch the feature 🙂 As for reducing the interval further, 15 minutes is a system limitation. To get below 15 minutes, we'd need a foreground service, which might actually be detrimental to battery life |
I see, thank you. It's a bit of a shame because when charging my watch, I sometimes receive the notifications 13% late of what I set to be notified about (due to rare updates). I normally wish to avoid overcharging past 80% (just a battery saving technique), so I set 70% in the app as kind of a workaround. You mentioned this though:
However, I'm afraid I am not seeing that. It works on the watch, when I tap the charge indication it updates, but that doesn't happen on the phone. Am I missing something? |
It's probably just me forgetting what's live in Google Play again, there's been a fair bit of work without a published build for a while now 😅 |
It would be great to have the ability to set up the battery sync interval, and also make it smaller than 15 minutes (this is because I don't want to miss a certain level of charge while charging).
I see on screenshots in Google Play that there is such a setting, but I cannot find it in the app. Maybe it was removed for some reason? (I have Galaxy Watch 4 Classic + OnePlus 8).
It would also be great to be able to trigger a manual update. It seems to be possible from the watch already, but not from phone.
The text was updated successfully, but these errors were encountered: