Status Update
No update yet.
Comments
ga...@google.com
Hello,
Are you able to supply example code for when this is happening, for both phone and watch side?
Are you trying to use BIND_LISTENER in your own app, or is this an issue with the underlying data layer API?
(BIND_LISTENER has been deprecated for a long time, so am wondering whether this is an issue in the Wear API themselves or not:
Thanks
bh...@gmail.com
up...@gmail.com
From
on 6/6/2014: issue 36996391
Same here. Face looks squished and tablet doesn't recognize it. Resetting and reregistering didn't help. The feature is completely broken.
ga...@google.com
This is a known issue when targeting API level 33. A fix is being prepared.
bh...@gmail.com
th...@gmail.com
bh...@gmail.com
is this issue fixed?
bh...@gmail.com
did you figure out why WearableListenerService was no longer working once I targeted API level 33?
bh...@gmail.com
Is any Update for the watch to phone sync not working when the targeted API level set to 33?
ma...@udisc.com
ch...@gmail.com
ty...@udisc.com
ju...@gmail.com
ju...@gmail.com
ki...@gmail.com
ja...@gmail.com
ma...@udisc.com
If you use a phone running Android 12 or earlier, it works fine. This is rendering our WearOS app completely useless for anyone with a newer phone that runs Android 13, and there is no known workaround so we're having to tell hundreds of customers that our app just straight up doesn't work right now.
If your app is impacted, please make sure to star this issue to get Google's attention, and tell all the other devs at your company and your customers that are impacted to star this issue as well.
am...@gmail.com
am...@gmail.com
gr...@gmail.com
ja...@gmail.com
ph...@gmail.com
na...@gmail.com
ga...@google.com
This issue should be fixed now. The fix has been rolled out via GMSCore and will also require using the latest com.google.android.gms:play-services-wearable:18.0.0 release.
Note that you don’t need to add BIND_LISTENER manually, it has been deprecated for a long time and it continue to remain so (read more at
For more details, see
Would you be able to test again after updating and confirm whether the fix works for you?
Many thanks
ma...@udisc.com
We can confirm that updating our Android and WearOS apps to com.google.android.gms:play-services-wearable:18.0.0 has fixed the watch -> phone communication issue when targeting API level 33!
We're uploading new versions to the Play Store now, and we're hopeful it will be approved quickly so we can get our WearOS users back up and running.
Thanks again for the prompt action and response, we really appreciate it!
bh...@gmail.com
Would you be able to test again after updating and confirm whether the fix works for you?
Yes, Working fine after updating the API.
Thanks.
ga...@google.com
Thank you for confirming this - much appreciated.
ar...@gmail.com
ar...@gmail.com
I can confirm that updating my Android and WearOS app to com.google.android.gms:play-services-wearable:18.0.0 has fixed the connectivity issues. my app is being used daily by many WearOS users -> much appreciate that you have fixed it. developer of "BVR pro" app.
bh...@gmail.com
jl...@gmail.com
ch...@gmail.com
ar...@gmail.com
It worked for me only if I added back the deprecated <intent-filter> <action android:name="com.google.android.gms.wearable.BIND_LISTENER"/> </intent-filter>
error before I added it back: 16:37:25.470 W Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=com.xxx.xxx/.Receivers.DataLayerListenerService } U=0: not found 16:37:25.470 E packages/modules/Bluetooth/system/gd/hci/hci_layer.cc:156 on_command_status: Received UNEXPECTED command status:COMMAND_DISALLOWED opcode:0x804 (EXIT_SNIFF_MODE) 16:37:25.471 I packages/modules/Bluetooth/system/stack/acl/btm_pm.cc:697 btm_pm_proc_cmd_status: Clearing pending power mode link state:immediate:sniff 16:37:25.472 W Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=com.xxx.xxx/.Receivers.DataLayerListenerService } 16:37:25.472 W Access blocked: ComponentInfo{com.xxx.xxx/com.xxx.xxx.Receivers.DataLayerListenerService}
ru...@gmail.com
ma...@gmail.com
Galaxy watch 4 + Pixel 2 XL
da...@gmail.com
da...@gmail.com
Pixel 7 pro + Samsung Watch 5 pro.
da...@gmail.com
packages/modules/Bluetooth/system/gd/hci/hci_layer.cc:156 on_command_status: Received UNEXPECTED command status:COMMAND_DISALLOWED opcode:0x804 (EXIT_SNIFF_MODE)
all the time when I'm trying to send something from the watch to the phone
Description
Version used:
Devices/Android versions reproduced on:
If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue.
- A screenrecord or screenshots showing the issue (if UI related).
Hi,
the issue is Phone to Watch data sync working fine but the Watch to phone Data sync not working after Update Target SDK version 33, a warning is shown when sending data from the watch to the phone.
- Intent does not match component's intent filter: Intent { act=com.google.android.gms.wearable.BIND_LISTENER cmp=packageName/.wear.DataLayerListenerServices }
- Access blocked:ComponentInfo{packageName/packageName.wear.DataLayerListenerServices}
- Unable to start service Intent { act=com.google.android.gms.wearable.BIND_LISTENER
cmp=packageName/.wear.DataLayerListenerServices } U=0: not found