Issue by VladimirWrites
Saturday Jul 21, 2018 at 17:52 GMT
Originally opened as googlearchive/android-WatchFace#20

This is more of a question and not an issue.
According to the documentation onTimeTick inside WatchFaceService.Engine will be called when the time-zone is changed.
https://developer.android.com/reference/android/support/wearable/watchface/WatchFaceService.Engine.html#onTimeTick()
Would it be enough to call

 mCalendar.setTimeZone(TimeZone.getDefault());
 invalidate();

inside onTimeTick() and not use BroadcastReceiver to handle the change like it's done in this project?

https://github.com/googlesamples/android-WatchFace/blob/88ae4adfabdcf3c432d957b84f6fe069b3c8ed14/Wearable/src/main/java/com/example/android/wearable/watchface/watchface/AnalogComplicationWatchFaceService.java#L186-L193

I wanted to use the ChannelClient to send a file and additional information (string/int information) bundled with it to a wearable. The ChannelClient seemed best for it as: 1) it saves disk space over the DataClient 2) from the wearable perspective, it is not exclusive to Android phones 3) the MessageClient does not guarantee delivery.

I can only find 2 incomplete examples of the wearable sending to the phone and both seem to use deprecated methods (GoogleApiClient and ChannelApi.OpenChannelResult). Can you add a ChannelClient example to this?

Issue by Elizabeth-Mezias-Bose
Wednesday Aug 14, 2019 at 22:46 GMT
Originally opened as googlearchive/android-JumpingJack#2

The MainActivity class import is using Android Jetpack.
import androidx.wear.ambient.AmbientModeSupport;

However, the build.gradle does not declare AndroidX. Instead of:
androidx.wear:wear:1.0.0

you find the following dependencies:
implementation 'com.google.android.gms:play-services-wearable:16.0.1'
implementation 'com.android.support:support-v13:28.0.0'
compileOnly 'com.google.android.wearable:wearable:2.4.0'
implementation 'com.google.android.support:wearable:2.4.0'

That means the project won't build if you import this sample.

hi,
Something is not clear to me : if you design a watch face with android studio, do you put the result in the google wear os companion app, or do you create an own companion app for your own watch faces ?
thanks
regards
ludo

Issue by hazexzo
Monday Apr 08, 2019 at 09:28 GMT
Originally opened as googlearchive/android-WatchFace#24

I get this error when opening the companion app on the phone. Watchface on the real watches is installed and selected. Watches and phone are paired correctly. All other applications work correctly. The problem is only with this sample app. What is the reason?

Hey guys, since this will be a new popular feature to add to new Wear apps would be good to update?
like Kotlin
and also RemoteIntent not found?

if (resultCode == RemoteIntent.RESULT_OK) {
ConfirmationOverlay().showOn(this@MainActivity)
} else if (resultCode == RemoteIntent.RESULT_FAILED) {
ConfirmationOverlay()
.setType(ConfirmationOverlay.FAILURE_ANIMATION)
.showOn(this@MainActivity)
} else {
throw IllegalStateException("Unexpected result $resultCode")
}

hi,
maybe I overlooked it, but I cannot find an explication on how to import a watch face from wear os companion app to android studio.
I just want to change the position of month/day to day/month, which seems always to be set to US , not to European format.
thanks in advance
regards

I checked out the Wear Tiles Sample and have a question about the buttons.

The tiles media sample contains a Play icon button. As described in the sample, the buttons do not do anything at the moment. However, I am not sure how to set the click action to send a broadcast.

I would assume this play button is supposed to start the music without opening the app. I would like to do something similar, turn on a smart light without opening the app.

However, I cannot find an ActionBuilders.Action that sends a broadcast. It would be great if you could add a click action to this sample so it is clear how to actually implement a play button or something similar.

Issue by Scienticious
Thursday Jun 21, 2018 at 07:31 GMT
Originally opened as googlearchive/android-WearAccessibilityApp#2

AcceptDenyDialog perfectly working in After API 23,
But oneActionDialog.get().show showing the warning i.e Call requires API Level 24
How to Show AcceptDenyDialog in API 23 , is there alternative ?

I try to compile the project, but I get the following error

Error: Project depends on com.google.android.support:wearable:2.3.0, so it must also depend (as a provided dependency) on com.google.android.wearable:wearable:2.3.0 [GradleCompatible]

This is part of my build gradle (Application):

dependencies {
compile 'com.android.support:support-v4:27.1.0'
compile 'com.android.support:support-v13:27.1.0'
compile 'com.android.support:cardview-v7:27.1.0'
compile 'com.android.support:appcompat-v7:27.1.0'
compile 'com.google.android.support:wearable:2.3.0'
compile 'com.google.android.gms:play-services-wearable:11.8.0'
compile 'com.android.support:support-v13:27.1.0'
wearApp project(':Wearable')
}

and this is part of my build gradle (Wear):

dependencies {
compile 'com.android.support:palette-v7:27.1.0'
compile 'com.android.support:wear:27.1.0'
compile 'com.google.android.gms:play-services-wearable:11.8.0'
compile 'com.android.support:support-v13:27.1.0'
compileOnly 'com.google.android.wearable:wearable:2.3.0'
compile 'com.google.android.support:wearable:2.3.0'
}

And tried with compileOnly and with provided but always shows the same error

What can I do or what am I doing wrong?
Thanks

Hi 👋,

I am developing and maintaining Analog Watch Face. https://github.com/VladimirWrites/AnalogWatchFace
A lot of users are asking for the second hand in ambient mode for devices using 3100+ processors, and right now it's only possible using undocumented DecompositionWatchFaceService.
I wanted to check with you if there is a plan for long-term support of Decompositions, or if some of the libraries that are currently being developed will replace its functionality.
If Decompositions are there to stay it would be great to have some documentation or examples. 😊

Issue by IceNerd
Wednesday Jul 04, 2018 at 19:56 GMT
Originally opened as googlearchive/android-WatchFace#18

Didn't review the contributing guidlines, I just fixed the thing. Pull the project and build. I was unable to track a file to add to the repo that would persist the Android Studio setting so here is another note about it!

To deploy the Application or Wearable, update the run configurations -> General -> Launch Options -> Launch: Nothing

IceNerd included the following code: https://github.com/googlesamples/android-WatchFace/pull/18/commits

I run the demo Tile sample ,but don't can see at list of select page
我在 Tile 选择页面没有找到运行起来的 demo ,我做了各种尝试。

I have installed this app into my smartwatch emulator, but I can not see this app when I select the Pick a tile from the watch. How can I add a tile after installing the app?

Issue by yingding
Wednesday Dec 12, 2018 at 14:16 GMT
Originally opened as googlearchive/android-DataLayer#6

Feature Request

Since sometime it is not desired to send data or messages between the wearable and handheld devices in case the (1) bluetooth/wifi connection is off on the phone, (2) watch disconnected in WearOs App, or (3) bluetooth/wifi connection is off on the watch.

The onCapabilityChanged method can be modified to catch the connection status via the available remote nodes by the given capability name. If the reachable wear nodes is empty set, than the data and message exchange can be pause to save RAM and Battery. After the connection between the nodes are reestablished, the data and message exchange shall go on.

In the Analog Complication WatchFace sample, the ComplicationData are stored in a SparseArray, that, if I'm not mistaken, is not used anywhere. So this should be removed completely to simplify the sample.

The line where they are saved is: https://github.com/googlesamples/android-WatchFace/blob/master/Wearable/src/main/java/com/example/android/wearable/watchface/watchface/AnalogComplicationWatchFaceService.java#L397

You can see that mActiveComplicationDataSparseArray is not used anywhere else.

Are there any documented APIs that we can use to create an iOS companion app to work with WearOS watchface?
WearOS 2.0 is supposed to be compatible with Android and iOS, however there is no official documentation as to how to achieve this cross platform compatibility

Reference links in DataLayer/README.md indicate wrong sites (404).

Issue by haidar786
Thursday Feb 08, 2018 at 09:43 GMT
Originally opened as googlearchive/android-WearVerifyRemoteApp#3

Please update deprecated fields if you have time,that will be helpful for me.thanks

is it need phone and watch 's package name should be same when to send and syncing data?
when i test,
if package name is different between phone and watch,
it's can't to use data layer api to send/receive data.

Issue by BoD
Sunday May 13, 2018 at 12:59 GMT
Originally opened as googlearchive/android-WatchFace#16

In the Analog Complication WatchFace sample, the ComplicationData are stored in a SparseArray, that, if I'm not mistaken, is not used anywhere. So this should be removed completely to simplify the sample.

The line where they are saved is: https://github.com/googlesamples/android-WatchFace/blob/master/Wearable/src/main/java/com/example/android/wearable/watchface/watchface/AnalogComplicationWatchFaceService.java#L397

You can see that mActiveComplicationDataSparseArray is not used anywhere else.

Issue by IgorGanapolsky
Thursday Jun 27, 2019 at 22:51 GMT
Originally opened as googlearchive/android-WatchFace#25

Hello,
I am getting the following build error:

AAPT: error: duplicate value for resource 'attr/progress' with config ''.

The incremental values.xml look like this:
<declare-styleable name="SeekArc"><attr format="dimension" name="arcWidth"/><attr format="color" name="arcColor"/><attr format="integer" name="startAngle"/><attr format="integer" name="sweepAngle"/><attr format="integer|reference" name="maxProgress"/><attr format="integer|reference" name="progress"/><attr format="color" name="progressColor"/><attr format="boolean" name="roundCorner"/><attr format="color" name="thumbColor"/><attr format="dimension" name="thumbRadius"/><attr format="string" name="seekDirection"/></declare-styleable>

It would be nice to have an example on how to use ChannelClient as right now there is not much information on how to use it around internet.

Issue by IgorGanapolsky
Wednesday Oct 10, 2018 at 10:30 GMT
Originally opened as googlearchive/android-WearVerifyRemoteApp#4

Make the project compatible with Android Studio 3.3

IgorGanapolsky included the following code: https://github.com/googlesamples/android-WearVerifyRemoteApp/pull/4/commits

Original issue created by @IgorGanapolsky in the old repo location (googlesamples/android-WatchFace):

Hello,
I am getting the following build error:

AAPT: error: duplicate value for resource 'attr/progress' with config ''.

The incremental values.xml look like this:
<declare-styleable name="SeekArc"><attr format="dimension" name="arcWidth"/><attr format="color" name="arcColor"/><attr format="integer" name="startAngle"/><attr format="integer" name="sweepAngle"/><attr format="integer|reference" name="maxProgress"/><attr format="integer|reference" name="progress"/><attr format="color" name="progressColor"/><attr format="boolean" name="roundCorner"/><attr format="color" name="thumbColor"/><attr format="dimension" name="thumbRadius"/><attr format="string" name="seekDirection"/></declare-styleable>

Hello, thank you so much for these samples. I am learning how to build Android Wear apps thanks to these. However, can you please update your code to Kotlin and use Coroutines + Architecture Components instead of Handlers and Alarms? All these samples seem extremely outdated practices compared to IoSched and Sunflower samples which Google advocates.

Igor

Please update the demo to the latest public libs

androidx.wear.tiles:tiles:1.0.0-alpha03
androidx.wear.tiles:tiles-renderer:1.0.0-alpha03

There a huge breaking changes compared to the used old libs.
androidx.wear:wear-tiles:1.0.0-alpha01
androidx.wear:wear-tiles-renderer:1.0.0-alpha01

It's hard to understand what's the recommended implementation.

I am trying to explore Wear apps after loading the Always app I get the following error

=========================
Error:No such property: GradleVersion for class: JetGradlePlugin

Consult IDE log for more details (Help | Show Log)

IDE Log errors
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:201)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:105)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:101)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:93)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:82)
2021-02-16 14:58:26,359 [se-915-b01] ERROR - ctionCallback.TimedOutCallback - Android Studio 3.0.1 Build #AI-171.4443003
2021-02-16 14:58:26,359 [se-915-b01] ERROR - ctionCallback.TimedOutCallback - JDK: 1.8.0_152-release
2021-02-16 14:58:26,359 [se-915-b01] ERROR - ctionCallback.TimedOutCallback - VM: OpenJDK Server VM
2021-02-16 14:58:26,359 [se-915-b01] ERROR - ctionCallback.TimedOutCallback - Vendor: JetBrains s.r.o
2021-02-16 14:58:26,359 [se-915-b01] ERROR - ctionCallback.TimedOutCallback - OS: Windows 7
2021-02-16 16:30:41,749 [se-915-b01] INFO - build.invoker.GradleTaskFinder - Unable to find Gradle tasks for project 'AlwaysOn' using BuildMode REBUILD
2021-02-16 16:30:41,754 [se-915-b01] INFO - ild.invoker.GradleBuildInvoker - About to execute Gradle tasks: []
2021-02-16 16:31:18,856 [se-915-b01] INFO - ide.actions.ShowFilePathAction -
Exit code 1

Gradle version from the Project Structure is 6.5

Please let me know if you need more information/details or I am missing some plugin to build this app

idea.log
threadDump-20210216-145152.txt

I get this error when opening the companion app on the phone. Watchface on the real watches is installed and selected. Watches and phone are paired correctly. All other applications work correctly. The problem is only with this sample app. What is the reason?

This is more of a question and not an issue.
According to the documentation onTimeTick inside WatchFaceService.Engine will be called when the time-zone is changed.
https://developer.android.com/reference/android/support/wearable/watchface/WatchFaceService.Engine.html#onTimeTick()
Would it be enough to call

 mCalendar.setTimeZone(TimeZone.getDefault());
 invalidate();

inside onTimeTick() and not use BroadcastReceiver to handle the change like it's done in this project?

https://github.com/googlesamples/android-WatchFace/blob/88ae4adfabdcf3c432d957b84f6fe069b3c8ed14/Wearable/src/main/java/com/example/android/wearable/watchface/watchface/AnalogComplicationWatchFaceService.java#L186-L193

Issue by IgorGanapolsky
Thursday Nov 08, 2018 at 12:58 GMT
Originally opened as googlearchive/android-WatchFace#21

Update the project to be compatible with latest devices and android studio.

IgorGanapolsky included the following code: https://github.com/googlesamples/android-WatchFace/pull/21/commits

Please migrate these deprecated classes to use androidx classes.
android.app.Fragment = androidx.fragment.app.Fragment
android.app.FragmentManager = androidx.fragment.app.FragmentManager

I have tried to do this in my own projects and it appears to me that this sample will no longer work using classes that are not deprecated. Specifically the the NavigationAdapter for the top navigation drawer will error out from my experience. I cant seem to find any documentation about fixing this problem or I wouldn't bother you with it. Thanks.

Issue by AmandaBeuno
Monday Feb 04, 2019 at 22:07 GMT
Originally opened as googlearchive/android-JumpingJack#1

Good day,

I opened my Android Studio->File->New->Import Sample and run the "JumpingJack" sample on my "Huawei Watch 2" but the counter remains on zero.

I tried to figure out what is not working with it on the MainActivity, but I guess it is in vein.

Hope you can give me any pointers on why this sample is not working or if it is anything wrong on my part.

All the best,

new Handler() is deprecated in the WearVerifyRemoteApp MainMobileActivity.java line 88

Issue by moneytoo
Wednesday Feb 14, 2018 at 21:01 GMT
Originally opened as googlearchive/android-WearAccessibilityApp#1

In both this sample and https://github.com/googlesamples/android-WearNotifications, Activities featuring WearableRecyclerView display scrollbar that doesn't take the full display height on watches with square displays. The height of scrollbar is the same as the height of an item. It's ok on round watches but this doesn't look right.
(I know I can tweak ScalingScrollLayoutCallback to make it look better/different but I'm not aware of anything related to the scrollbar there.)

The app drawer/launcher looks ok.

I tested it in the latest emulator though.

Issue by ccruz17
Thursday May 31, 2018 at 02:01 GMT
Originally opened as googlearchive/android-WatchFace#17

I try to compile the project, but I get the following error

Error: Project depends on com.google.android.support:wearable:2.3.0, so it must also depend (as a provided dependency) on com.google.android.wearable:wearable:2.3.0 [GradleCompatible]

This is part of my build gradle (Application):

dependencies {
compile 'com.android.support:support-v4:27.1.0'
compile 'com.android.support:support-v13:27.1.0'
compile 'com.android.support:cardview-v7:27.1.0'
compile 'com.android.support:appcompat-v7:27.1.0'
compile 'com.google.android.support:wearable:2.3.0'
compile 'com.google.android.gms:play-services-wearable:11.8.0'
compile 'com.android.support:support-v13:27.1.0'
wearApp project(':Wearable')
}

and this is part of my build gradle (Wear):

dependencies {
compile 'com.android.support:palette-v7:27.1.0'
compile 'com.android.support:wear:27.1.0'
compile 'com.google.android.gms:play-services-wearable:11.8.0'
compile 'com.android.support:support-v13:27.1.0'
compileOnly 'com.google.android.wearable:wearable:2.3.0'
compile 'com.google.android.support:wearable:2.3.0'
}

And tried with compileOnly and with provided but always shows the same error

What can I do or what am I doing wrong?
Thanks

Issue by littleariel
Sunday Feb 24, 2019 at 19:36 GMT
Originally opened as googlearchive/android-WatchFace#22

Running Google Fit 2.08.21, WearOS 2.3, and Google Play Services 15.0.90 on Ticwatch Pro, the STEP_COUNT system provider isn't working anymore.

To reproduce the issue, just add the following at the end of initializeComplicationsAndBackground()

// TEST SYSTEM PROVIDERS
// Watch battery works:
setDefaultSystemComplicationProvider(LEFT_COMPLICATION_ID, SystemProviders.WATCH_BATTERY, ComplicationData.TYPE_SHORT_TEXT);

 // Steps do NOT work (that's a bug):
setDefaultSystemComplicationProvider(RIGHT_COMPLICATION_ID, SystemProviders.STEP_COUNT, ComplicationData.TYPE_SHORT_TEXT);

When running this on the watch, the left complication shows the watch battery as expected. The right complication shows "--" for the steps instead of the daily step count, which is a bug.

I confirmed the Google Fit app shows non-zero steps on the watch. Note that going into the watch face configuration activity and explicitly replacing the default step count with the Google Fit step count works and shows the right value.

Running Google Fit 2.08.21, WearOS 2.3, and Google Play Services 15.0.90 on Ticwatch Pro, the STEP_COUNT system provider isn't working anymore.

To reproduce the issue, just add the following at the end of initializeComplicationsAndBackground()

// TEST SYSTEM PROVIDERS
// Watch battery works:
setDefaultSystemComplicationProvider(LEFT_COMPLICATION_ID, SystemProviders.WATCH_BATTERY, ComplicationData.TYPE_SHORT_TEXT);

 // Steps do NOT work (that's a bug):
setDefaultSystemComplicationProvider(RIGHT_COMPLICATION_ID, SystemProviders.STEP_COUNT, ComplicationData.TYPE_SHORT_TEXT);

When running this on the watch, the left complication shows the watch battery as expected. The right complication shows "--" for the steps instead of the daily step count, which is a bug.

I confirmed the Google Fit app shows non-zero steps on the watch. Note that going into the watch face configuration activity and explicitly replacing the default step count with the Google Fit step count works and shows the right value.

Issue by andrew-codechimp
Tuesday Jan 09, 2018 at 10:21 GMT
Originally opened as googlearchive/android-WearVerifyRemoteApp#2

When trying to use this sample I'm getting errors trying to resolve Remote Intent

error: package com.google.android.wearable.intent does not exist
error: cannot find symbol variable RemoteIntent

I'm getting the same on my own project which implemented this as well, updating all dependencies to the latest versions didn't resolve the issue either.

1. created a release version of the mobile app [which has an embedded wear apk]
2. on the successful installation of the mobile app, the wear app should appear on the Wear PlayStore .but it's not showing.

I can see the wear app on Wear OS by Google on 2.24 but not 2.27
FYI: I had tried running RuntimePermissionWear sample and the issue is happening with my app as well
I even analyzed the Mobile Apk and I can the micro_wear apk embedded in it.
Any help will be appreciated.
Thank you in advance

Trying to use a constrainCircle in wearOS app along with a rotation using the new ConstraintLayout library. For some reason, the element rotates fine however the constrainCircle is not working.

        @Override
        public void run() {
            xAnimation = animateForGivenTime(TimeUnit.SECONDS.toMillis(40));
            xAnimation.addUpdateListener(new ValueAnimator.AnimatorUpdateListener() {
                @Override
                public void onAnimationUpdate(ValueAnimator valueAnimator) {
                    int degrees = (Integer) valueAnimator.getAnimatedValue();
                    constraintSet.constrainCircle(R.id.textView1, R.id.center,
                            50,
                            degrees);
                    constraintSet.setRotation(R.id.textView1, degrees);
                    constraintSet.applyTo(constraintLayout);
                    invalidate();

                }
            });


            xAnimation.start();
        }
    });```


Is there some compatibility issues with the constrainCircle function with wearOS? Or did I miss something crucial?

Anlayışın için teşekkür ediyorum.

I am getting this while trying to deploy the weareable module on my watch. "Warning: The activity must be exported or contain an intent-filter". I searched the internet and added this: <intent-filter> <action android:name="android.intent.action.MAIN" /> </intent-filter> to AndroidManifest.xml but that deployed weird app that looks like the handheld one and doesn't feel like weareble compatible. The deployment guides didn't really helped with this issue.

If matched the tile example and got my tile previewed the the preview Activity. It all looked good so I published it, but the tile does not show up in the list of available tiles.

Here is my manifest service:

        <service
            android:name=".provider.StorageProviderService"
            android:label="NavExplorer"
            android:description="@string/tile_description"
            android:icon="@mipmap/ic_launcher"
            android:permission="com.google.android.wearable.permission.BIND_TILE_PROVIDER">
            <intent-filter>
                <action android:name="androidx.wear.tiles.action.BIND_TILE_PROVIDER" />
            </intent-filter>

            <meta-data android:name="androidx.wear.tiles.PREVIEW"
                android:resource="@drawable/tile_preview" />
        </service>

Is there another step required?

Issue by mores
Sunday Jun 16, 2019 at 11:20 GMT
Originally opened as googlearchive/android-WearStandaloneGoogleSignIn#3

"The button included in this sample should be used as throwaway code for all Wear integrations until the final version lands in Play Services, and maintained there going forward."

Issue by yingding
Wednesday Dec 12, 2018 at 13:38 GMT
Originally opened as googlearchive/android-DataLayer#5

Since sometime it is not desired to send data or messages between the wearable and handheld devices in case the (1) bluetooth/wifi connection is off on the phone, (2) watch disconnected in WearOs App, or (3) bluetooth/wifi connection is off on the watch.

onCapabilityChanged method is modified to check if there are active reachable wearable remote nodes. In case the connection between the watch and phone is broken through case (1),(2),(3) no more data and messages are sent among the devices. After the connection is reestablished, the data and message exchange is going on again.

yingding included the following code: https://github.com/googlesamples/android-DataLayer/pull/5/commits

I followed the example to use RemoteIntent, but have run into a problem I cannot seem to get past.

I have this import in my class:
import com.google.android.wearable.intent.RemoteIntent;

But am getting an error:

Cannot resolve symbol 'RemoteIntent'
The red lightbulb recommendation is to:

Add Library 'Gradle: com.google.android.support:wearable:2.8.1@aar' to classpath
But when I click on it nothing happens.

And this line in my mobile app gradle dependencies:

compileOnly 'com.google.android.wearable:wearable:2.8.1'
What am I doing wrong?

When I try to build I get this error:

package com.google.android.wearable.intent does not exist error