-
Notifications
You must be signed in to change notification settings - Fork 295
resurrect wear #1211
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
resurrect wear #1211
Conversation
1) Remove usage of NodeApi, it mostly works without it. And for the scenario where the phone and the watch looses connection, probably a human will intervene anyway. 2) Fix the intents so that one can use the buttons on the watch. note: not everything seems to be working (yet) 3) Fix build things a) it seems like gms for wearable is split from main gms? b) fix wear debug version applicationSuffix c) fix build without mapbox.properties TESTED=Manually tested that the wear apps seems to mostly function in debug build
gerhardol
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have not run, but I do not see this affecting use without Wear.
|
please take another look ? |
|
Updated dependencies in #1214, fixed a few lints too. Will not be able to test much, just spinning up on a Pixal 8 w Android 15. -- Lint found errors in the project; aborting build. Fix the issues identified by lint, or add the issues to the lint baseline via C:\dev\gc\runnerup\wear\src\main\java\org\runnerup\service\ListenerService.java:136: Error: When targeting Android 13 or higher, posting a permission requires holding the POST_NOTIFICATIONS permission [NotificationPermission] Explanation for issues of type "NotificationPermission": 1 errors, 0 warnings |
|
Hi again,
Thanks! |
WearOS uses a certain Android API. Nothing works before this PR, but this may fail newer watches |
|
Fixed the lint problem and some minor tweaks. Please take another look ? |
gerhardol
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only brief use in phone app, but do not see this to be affecting the normal functionality.
|
Thanks! |
Remove usage of NodeApi,
it mostly works without it. And for the scenario
where the phone and the watch looses connection,
probably a human will intervene anyway.
Fix the intents so that one can use the buttons on the watch. note: not everything seems to be working (yet)
Fix build things
a) it seems like gms for wearable is split from main gms? b) fix wear debug version applicationSuffix
c) fix build without mapbox.properties
TESTED=Manually tested that the wear apps seems to mostly function in debug build