An app designed to fill in feature gaps in the Wear OS platform
License: Apache License 2.0
An app designed to fill in feature gaps in the Wear OS platform.
Find out more on our our wiki.
Find the Privacy Policy here: PRIVACY.md.
The license can be found here: LICENSE.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
There's a lot of errors related to invalid widget config behind the scenes, we should have a view for widgets to notify users when they should recreate the widget to fix issues.
Currently as the user dismisses messages they continue to build up in message history. We need a way to clear these old messages.
Any change to buildSrc requires the whole module to be rebuilt, which is not a good thing when any library update goes through it.
As the title says, watch status defaults to "error" and doesn't update
No app icons are loaded via App Manager. Not even the fallback icons.
With the new Jetpack Compose UI, many animations are missing.
I am unable to use the widget for this app. When I try to add it to my desktop I am presented with a blank black screen (I attach screenshot) with no content on it. I have no option but to press back but then that terminates the widget set up.
Phone: Moto G 5G Android 10
Watch: Huawei Watch 2 Sport
PS This is a fantastic app. I have been using it for years now and the widget had worked really well for me in the past.
Sadly the Samsung Gear S3 doesn't work with Wearable Intentions - I know this is an older watch, however, there are still a few of us using them. (My Son gave me his old one)
The functions there are rather large and the code was written for an older platform.
The interface still works, but feels rather dated and there aren't many options.
GitHub supports a wiki, we should create one and possibly link to it in-app so users can find out more about features etc
After setting up the app for the first time, the app closes. This doesn't appear to affect functionality, and you can just open the app again.
This should reduce the need for the user to open specific settings pages, and make it quicker and easier to find info about the systems provided by Wearable Extensions.
To do:
Need to find out what the new method is, and replace the deprecated calls.
The phone battery widget does not display properly. Multiple battery numbers are displayed on top of one another 
Unless you're an experienced user, you may not know you need to continue the uninstall process on your watch.
Seems like it's not being called when updating the app, it's unclear currently whether it's called on boot.
This will give us a more streamlined way of discovering new and registered watches, as well as making it easier to add new watch discovery protocols
Battery stats don't seem to update automatically anymore, and trying to refresh stats on the watch always results in an error
This will make it easier to add support for other watches in the future
It adds unnecessary overhead to the project, and it's the only use of kotlin-reflect.
This could be caused by the database being automatically closed when the app is put in the background (stopped but not destroyed). This causes multiple bugs, like dashboard status being blank, watch manager being empty and watch info not showing any capabilities.
Current implementation isn't very flexible, and can be generalized more.
Currently, the onboarding flow reports no new watches found, and retrying gets the user stuck on the loading screen. Tapping back and trying to proceed again causes a crash, and upon opening the app again watches are registered.
This should also be occurring when registering watches from the watch manager activity, but I haven't confirmed anything.
We should start making the switch now, it's shaping up to be the future of UI design for Android
Seems like a lot of the code is now obsolete, and we should be able to add a few new features to the activity now.
As the title say, currently battery sync workers will keep running after clearing preferences, and WatchBatteryStatsDatabase will remain populated, wasting space.
It often shows disconnected, navigating between screens enough will update the status and show connected. We should probably trigger a refresh more often (possibly app onResume?)
According to system logs, it's taking around 6.2 seconds to launch MainActivity on my Fossil Gen 5 smartwatch. Surely we can improve this
Seems like we can detect capabilities on the watch side and programmatically add them to the list of capabilities
Describe the bug
When toggling Battery Sync, if you go back to the dashboard you'll see the battery status view hasn't updated to reflect the changes.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Battery Status on dashboard updates to reflect the current state of Battery Sync
Device:
Describe the bug
When setting up the app, no watches are found when "Searching for Watches"
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The watch is found and setup is completed
Device:
Since an update a few months back, the app has stopped reporting its connection status to my phone properly in Watch Manager
The status now always reads "Error" no matter what connection status.
The status is displayed properly on the front screen however.
Phone: Moto G 5G
Watch: Huawei Watch 2 Sport
As the title says, my Fossil Gen 5 shouldn't support toggling Do not Disturb due to API limitations, but the capability gets broadcast anyways.
It's been replaced by new packages in the androidx.wear family
After uninstalling an app, App Manager on the phone side ends up in an error state This is likely due to the way the wearos module sends uninstall messages
Is your feature request related to a problem? Please describe.
Forwarding from Reddit: https://www.reddit.com/r/WearOS/comments/mktjpt/how_would_i_make_the_watch_vibratealert_me_when/?utm_medium=android_app&utm_source=share
I've also had users asking for this via beta feedback on the Play Store
Describe the solution you'd like
Add a new extension group to allow getting notifications when your devices lose connection, and possibly when they're reconnected too. This would require running services on one or both devices to listen for connection changes.
Describe the bug
As per the title, restarting the app results in no watch selected.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Wearable Extensions persists selected watch across app launches
Device:
FirebaseAnalytics has a built in function to enable/disable analytics, so there's no need to check SharedPreferences every time we want to log an event. We can also pass parameters to events, as well as log screen usage.
Describe the bug
After setting up Wearable Extensions for the first time, the watch picker just shows "Connecting".
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Either select a watch automatically, or Show a more descriptive message than just "Connecting"
Device:
Trying to lock your phone from your watch results in an error
Sometimes on start the watch connection may report an error, when in reality it's connected
I've had feedback from users regarding the app name, it's a bit of a mouthful and doesn't clearly convey what the app does best. Creating an issue to get some ideas rolling
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.
