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

Option for Active Background Sync #49

Open
Dondrejohnson5 opened this issue Sep 29, 2024 · 0 comments
Open

Option for Active Background Sync #49

Dondrejohnson5 opened this issue Sep 29, 2024 · 0 comments

Comments

@Dondrejohnson5
Copy link

Dondrejohnson5 commented Sep 29, 2024

A similar app for Wear OS is able to consistently synchronize battery percentage/status, etc for its complications/tiles, using background processes from the mobile (phone) app counterpart (that relies on the Android's "Device & App Notifications" permission). As a result, its watch complications/tiles only update when the phone's companion app in the background signals a status change (like phone charging/discharging) (regardless of Bluetooth connection or Wi-Fi connection between phone and watch), instead of the Wear OS app updating itself at 5-(or so)-minute intervals to check for the phone app's response. This proves to save the watch's battery life, and I would like to see something similar in SimpleWear, for battery status and the whole suite (hotspot enabled, flashlight on/off, do not disturb status, etc), especially considering that when I'm using the tiles sometimes, it gets stuck at this screen only until the next interval or I hit the reload button:
screenshot-2024-09-29-19-34-04
I should not have to do that, and it defeats the purpose of a "shortcut" that is the tile. It's just rather annoying.

Watch: Google Pixel Watch 3 LTE (45mm)
Wear OS version: 5
Watch app version: 1.15.4
Phone: Motorola Edge 40 Pro
Phone Android version: 14
Phone app version: 1.15.3

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

No branches or pull requests

1 participant