Stock on "Getting watch details"

Moderators: garrywadams, Chintannapster, Aathif Mahir, Sabertooth

User avatar
Sabertooth
Posts: 251
Joined: Tue May 15, 2018 2:18 pm
Cash on hand: Locked
Bank: Locked
Location: New York
Contact:

Re: Stock on "Getting watch details"

Post by Sabertooth » Tue Sep 10, 2019 3:03 pm

prodigy wrote:
Sun Sep 08, 2019 3:10 pm
Two more things - as I said before, pairing on Xiaomi Redmi 5 Plus completes in under 5 minutes, I've checked just a moment ago.
I'll try to leave the watch overnight for pairing, hope that will help.
Greetings prodigy!

I'm guessing that the watch was first connected to the Redmi 5 plus and then you got a new phone, the Redmi Note 7. If I'm getting this wrong, let me know. Please check the Redmi 5 Plus Bluetooth and be sure to remove the watch from the Bluetooth devices list (Connected devices/Bluetooth/tap the gear and select unpair). it could be still trying to auto-connect to the old phones Bluetooth creating a conflict.

Sabertooth
Mobvoi Global Moderator

no avatar
erinnis
Posts: 1
Joined: Thu Sep 12, 2019 8:12 am
Cash on hand: Locked

Re: Stock on "Getting watch details"

Post by erinnis » Thu Sep 12, 2019 9:56 am

Exactly same problem. I'm waiting for replies...

User avatar
Sabertooth
Posts: 251
Joined: Tue May 15, 2018 2:18 pm
Cash on hand: Locked
Bank: Locked
Location: New York
Contact:

Re: Stock on "Getting watch details"

Post by Sabertooth » Thu Sep 12, 2019 1:50 pm

erinnis wrote:
Thu Sep 12, 2019 9:56 am
Exactly same problem. I'm waiting for replies...
Greetings erinnis!

It will help if you can provide details of your phone make and model and watch model. Also, the specific problem being investigated in this topic occurs after you factory reset the watch. Have you recently factory reset the watch?

As I mentioned before the connection and syncing process can take extra time in some cases. Please allow at least an hour or two to be sure the process fails. It may also help to restart the phone before beginning.

We have referred this issue to Google so we suggest you also submit feedback via the Wear OS app and document this issue with Google directly. Open the Wear OS app, tap the three dots on the upper right and tap help & feedback then send feedback. Please provide as much detail as possible to aid in resolution of the issue.

Sabertooth
Mobvoi Global Moderator

no avatar
Perks
Posts: 2
Joined: Fri Sep 20, 2019 11:37 pm
Cash on hand: Locked

Re: Stock on "Getting watch details"

Post by Perks » Fri Sep 20, 2019 11:50 pm

Hello
I've the exact problem. The watch doesn't pair while my zenwatch works perfectly, at it worked with my previous phones

Please, can you give me some help?

User avatar
Sabertooth
Posts: 251
Joined: Tue May 15, 2018 2:18 pm
Cash on hand: Locked
Bank: Locked
Location: New York
Contact:

Re: Stock on "Getting watch details"

Post by Sabertooth » Sat Sep 21, 2019 4:42 pm

Perks wrote:
Fri Sep 20, 2019 11:50 pm
Hello
I've the exact problem. The watch doesn't pair while my zenwatch works perfectly, at it worked with my previous phones

Please, can you give me some help?
Greetings Perks!

We'll need some more information. Which TicWatch are you using and your phone make and model? Did you reset your watch when the issue occurred? After a factory reset, there are numerous apps that need to be updated and this can cause the process to proceed very slowly. Have you allowed a couple of hours for software and firmware updating to complete before deciding the process failed?

Sabertooth
Mobvoi Global Moderator

no avatar
prodigy
Posts: 7
Joined: Sun Sep 08, 2019 1:00 pm
Cash on hand: Locked

Re: Stock on "Getting watch details"

Post by prodigy » Wed Sep 25, 2019 7:11 am

I've already unpaired it from Redmi Note 5.
If performing factory reset on both the C2 and Redmi Note 7 (which I did) doesn't fix the problem, then something is wrong. (And leaving it overnight did nothing, there was an ~"Error connecting" or something message).

You can't deny that there's a problem, there are quite a few posts on your forum regarding this issue (even with this watch + phone model combo).

User avatar
Sabertooth.
Posts: 58
Joined: Mon Sep 23, 2019 2:02 pm
Cash on hand: Locked
Bank: Locked

Re: Stock on "Getting watch details"

Post by Sabertooth. » Wed Sep 25, 2019 2:28 pm

prodigy wrote:
Wed Sep 25, 2019 7:11 am
I've already unpaired it from Redmi Note 5.
If performing factory reset on both the C2 and Redmi Note 7 (which I did) doesn't fix the problem, then something is wrong. (And leaving it overnight did nothing, there was an ~"Error connecting" or something message).

You can't deny that there's a problem, there are quite a few posts on your forum regarding this issue (even with this watch + phone model combo).
Greetings prodigy!

Thank you for being one of the few to provide some actionable information about the issue. Most of those with the problem have not given many details so it makes it difficult to track the source of the problem. Thank you also for cross posting to Google since we feel this is an issue with Google Wear OS. While we may not be able to fix Wear OS issues, we can and do collect your information on the issue and connect with Google to push for the issue to be prioritized. I'm sorry I can't do more than assure you that I do put your issue in front of the engineers who have contact with Google and I trust that they are raising the issue with Google when they say they are.

I have stated (to the engineers) that there are increasing numbers of users experiencing this issue and I will link the engineers directly to this topic so they can see your experience first hand. If you can provide images or video of the issue that always helps get the engineers to take a look at the topic.

Sabertooth
Mobvoi Global Moderator

no avatar
prodigy
Posts: 7
Joined: Sun Sep 08, 2019 1:00 pm
Cash on hand: Locked

Re: Stock on "Getting watch details"

Post by prodigy » Thu Sep 26, 2019 6:40 am

I could provide you with Logcat logs, if there is any specific tag or package that you believe to be worth observing.

no avatar
prodigy
Posts: 7
Joined: Sun Sep 08, 2019 1:00 pm
Cash on hand: Locked

Re: Stock on "Getting watch details"

Post by prodigy » Thu Sep 26, 2019 8:49 pm

For example i found the following:

Code: Select all

09-26 21:40:55.634  2329  2344 W BroadcastQueueInjector: Unable to launch app com.spotify.music/10188 for broadcast Intent { act=android.bluetooth.device.action.ACL_DISCONNECTED flg=0x5000010 (has extras) }: process is not permitted to  auto start
09-26 21:40:55.640  3181  3181 I TrustAgent.Tracker: [BluetoothConnectionTracker] Bluetooth disconnect broadast for TicWatch C2 98:28:A6:E6:E8:D4
09-26 21:40:55.837  3695  3711 W System  : A resource failed to call close. 

Code: Select all

09-26 21:40:45.014  3181 22632 I WearableConn: Connecting to "TicWatch C2"
09-26 21:40:45.015  3181 22632 W BluetoothAdapter: getBluetoothService() called with no BluetoothManagerCallback
09-26 21:40:45.061  3181 22632 W WearableConn: Failed to connect, error: read failed, socket might closed or timeout, read ret: -1
09-26 21:40:45.061  3181 22632 D BluetoothSocket: close() this: android.bluetooth.BluetoothSocket@345a59c, channel: -1, mSocketIS: android.net.LocalSocketImpl$SocketInputStream@fc53ba5, mSocketOS: android.net.LocalSocketImpl$SocketOutputStream@5c4db7amSocket: android.net.LocalSocket@a0ccf2b impl:android.net.LocalSocketImpl@4d57f88 fd:java.io.FileDescriptor@6f2ed21, mSocketState: INIT
09-26 21:40:45.062  3181 22632 I WearableConn: Waiting 2.0 seconds to retry connection
09-26 21:40:46.036  2531  2545 I chatty  : uid=1000(system) HeapTaskDaemon expire 2 lines
09-26 21:40:47.067  3181 22632 I WearableConn: Connecting to "TicWatch C2"
09-26 21:40:47.068  3181 22632 W BluetoothAdapter: getBluetoothService() called with no BluetoothManagerCallback
09-26 21:40:47.120  3181 22632 W WearableConn: Failed to connect, error: read failed, socket might closed or timeout, read ret: -1
09-26 21:40:47.120  3181 22632 D BluetoothSocket: close() this: android.bluetooth.BluetoothSocket@70c34, channel: -1, mSocketIS: android.net.LocalSocketImpl$SocketInputStream@cf03a5d, mSocketOS: android.net.LocalSocketImpl$SocketOutputStream@4ff5fd2mSocket: android.net.LocalSocket@e59f8a3 impl:android.net.LocalSocketImpl@722b7a0 fd:java.io.FileDescriptor@37b1f59, mSocketState: INIT
09-26 21:40:47.120  3181 22632 I WearableConn: Waiting 4.0 seconds to retry connection
09-26 21:40:48.142  2531  2828 I chatty  : uid=1000(system) SysUiNetBg expire 12 lines
09-26 21:40:48.184  2329  7078 W ActivityManager: Unable to start service Intent { pkg=com.miui.hybrid cmp=com.miui.hybrid/.PersistService } U=0: not found
09-26 21:40:48.308  2329  2475 W MiuiGesturePointerEventListener: onActionDown end: mGestureStatus = 0
09-26 21:40:48.649   754   754 W memtrack@1.0-se: type=1400 audit(0.0:38922): avc: denied { read } for name="mem" dev="debugfs" ino=2728600 scontext=u:r:hal_memtrack_default:s0 tcontext=u:object_r:qti_debugfs:s0 tclass=file permissive=0
09-26 21:40:48.649   754   754 W memtrack@1.0-se: type=1400 audit(0.0:38923): avc: denied { read } for name="mem" dev="debugfs" ino=2728600 scontext=u:r:hal_memtrack_default:s0 tcontext=u:object_r:qti_debugfs:s0 tclass=file permissive=0
09-26 21:40:51.129  3181 22632 I WearableConn: Connecting to "TicWatch C2"
09-26 21:40:51.130  3181 22632 W BluetoothAdapter: getBluetoothService() called with no BluetoothManagerCallback
09-26 21:40:51.229 22419 22419 I chatty  : uid=10158(com.google.android.wearable.app) expire 7 lines
09-26 21:40:51.275 22419 22430 I chatty  : uid=10158(com.google.android.wearable.app) expire 1 line
09-26 21:40:51.096  2329  2475 W MiuiGesturePointerEventListener: onActionDown end: mGestureStatus = 0
09-26 21:40:51.287  2329  2344 W BroadcastQueueInjector: Unable to launch app com.spotify.music/10188 for broadcast Intent { act=android.bluetooth.device.action.ACL_DISCONNECTED flg=0x5000010 (has extras) }: process is not permitted to  auto start
09-26 21:40:51.287  2492  2492 I chatty  : uid=1002(bluetooth) expire 12 lines
09-26 21:40:51.290  3181  3181 I TrustAgent.Tracker: [BluetoothConnectionTracker] Bluetooth disconnect broadast for TicWatch C2 98:28:A6:E6:E8:D4
09-26 21:40:51.306  2329  8315 I chatty  : uid=1000(system) Binder:2329_1F expire 33 lines
09-26 21:40:51.308  2329  2339 I chatty  : uid=1000(system) Binder:2329_1 expire 19 lines
09-26 21:40:51.321  3181  3181 I NearbyDiscovery: onAclChange: state=DISCONNECTED, device=98:28:A6:E6:E8:D4 [CONTEXT service_id=49 ]
09-26 21:40:51.398 22435 22493 I chatty  : uid=10158(com.google.android.wearable.app) expire 84 lines
09-26 21:40:51.556  2329  2344 W BroadcastQueueInjector: Unable to launch app com.spotify.music/10188 for broadcast Intent { act=android.bluetooth.device.action.ACL_CONNECTED flg=0x5000010 (has extras) }: process is not permitted to  auto start
09-26 21:40:51.564  3181  3181 I TrustAgent.Tracker: [BluetoothConnectionTracker] Bluetooth connect broadast for TicWatch C2 98:28:A6:E6:E8:D4
09-26 21:40:51.619  3181 22632 W WearableConn: Failed to connect, error: read failed, socket might closed or timeout, read ret: -1
09-26 21:40:51.619  3181 22632 D BluetoothSocket: close() this: android.bluetooth.BluetoothSocket@75b7bf6, channel: -1, mSocketIS: android.net.LocalSocketImpl$SocketInputStream@7fcebf7, mSocketOS: android.net.LocalSocketImpl$SocketOutputStream@e9fea64mSocket: android.net.LocalSocket@d974cd impl:android.net.LocalSocketImpl@1bb6182 fd:java.io.FileDescriptor@10a5093, mSocketState: INIT

Code: Select all

09-26 21:47:09.432 23519 23588 W WearableHostUtil: Unsuccessful GMScore request: Status{statusCode=ERROR, resolution=null}
09-26 21:47:09.432 23519 23588 W WearableHostUtil: java.lang.Exception
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.host.WearableHostUtil.awaitInternal(AW771527612:50)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.host.WearableHostUtil.await(AW771527612:62)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.host.WearableHost.await(AW771527612:28)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.companion.device.DefaultOemSetupItemFetcher.fetchItem(AW771527612:4)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.companion.device.DeviceManager$RebuildDeviceInfoListTask.doInBackground(AW771527612:20)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.common.concurrent.CwAsyncTask$WorkerRunnable.call(AW771527612:7)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.common.concurrent.InstrumentedTask.run(AW771527612:35)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.common.concurrent.PooledThreadPoolExecutor$Worker.run(AW771527612:16)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.common.concurrent.CwPriorityRunnable.run(AW771527612:14)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at java.lang.Thread.run(Thread.java:764)
09-26 21:47:09.432 23519 23588 W DfltDevicePrefsHlpr: OEM settings is null for config: ConnectionConfiguration[ mName=TicWatch C2 0879, mAddress=98:28:A6:E6:E8:D4, mType=1, mRole=1, mEnabled=false, mIsConnected=false, mPeerNodeId=null, mBtlePriority=true, mNodeId=null]

User avatar
Sabertooth.
Posts: 58
Joined: Mon Sep 23, 2019 2:02 pm
Cash on hand: Locked
Bank: Locked

Re: Stock on "Getting watch details"

Post by Sabertooth. » Fri Sep 27, 2019 2:43 pm

prodigy wrote:
Thu Sep 26, 2019 8:49 pm
For example i found the following:

Code: Select all

09-26 21:40:55.634  2329  2344 W BroadcastQueueInjector: Unable to launch app com.spotify.music/10188 for broadcast Intent { act=android.bluetooth.device.action.ACL_DISCONNECTED flg=0x5000010 (has extras) }: process is not permitted to  auto start
09-26 21:40:55.640  3181  3181 I TrustAgent.Tracker: [BluetoothConnectionTracker] Bluetooth disconnect broadast for TicWatch C2 98:28:A6:E6:E8:D4
09-26 21:40:55.837  3695  3711 W System  : A resource failed to call close. 

Code: Select all

09-26 21:40:45.014  3181 22632 I WearableConn: Connecting to "TicWatch C2"
09-26 21:40:45.015  3181 22632 W BluetoothAdapter: getBluetoothService() called with no BluetoothManagerCallback
09-26 21:40:45.061  3181 22632 W WearableConn: Failed to connect, error: read failed, socket might closed or timeout, read ret: -1
09-26 21:40:45.061  3181 22632 D BluetoothSocket: close() this: android.bluetooth.BluetoothSocket@345a59c, channel: -1, mSocketIS: android.net.LocalSocketImpl$SocketInputStream@fc53ba5, mSocketOS: android.net.LocalSocketImpl$SocketOutputStream@5c4db7amSocket: android.net.LocalSocket@a0ccf2b impl:android.net.LocalSocketImpl@4d57f88 fd:java.io.FileDescriptor@6f2ed21, mSocketState: INIT
09-26 21:40:45.062  3181 22632 I WearableConn: Waiting 2.0 seconds to retry connection
09-26 21:40:46.036  2531  2545 I chatty  : uid=1000(system) HeapTaskDaemon expire 2 lines
09-26 21:40:47.067  3181 22632 I WearableConn: Connecting to "TicWatch C2"
09-26 21:40:47.068  3181 22632 W BluetoothAdapter: getBluetoothService() called with no BluetoothManagerCallback
09-26 21:40:47.120  3181 22632 W WearableConn: Failed to connect, error: read failed, socket might closed or timeout, read ret: -1
09-26 21:40:47.120  3181 22632 D BluetoothSocket: close() this: android.bluetooth.BluetoothSocket@70c34, channel: -1, mSocketIS: android.net.LocalSocketImpl$SocketInputStream@cf03a5d, mSocketOS: android.net.LocalSocketImpl$SocketOutputStream@4ff5fd2mSocket: android.net.LocalSocket@e59f8a3 impl:android.net.LocalSocketImpl@722b7a0 fd:java.io.FileDescriptor@37b1f59, mSocketState: INIT
09-26 21:40:47.120  3181 22632 I WearableConn: Waiting 4.0 seconds to retry connection
09-26 21:40:48.142  2531  2828 I chatty  : uid=1000(system) SysUiNetBg expire 12 lines
09-26 21:40:48.184  2329  7078 W ActivityManager: Unable to start service Intent { pkg=com.miui.hybrid cmp=com.miui.hybrid/.PersistService } U=0: not found
09-26 21:40:48.308  2329  2475 W MiuiGesturePointerEventListener: onActionDown end: mGestureStatus = 0
09-26 21:40:48.649   754   754 W memtrack@1.0-se: type=1400 audit(0.0:38922): avc: denied { read } for name="mem" dev="debugfs" ino=2728600 scontext=u:r:hal_memtrack_default:s0 tcontext=u:object_r:qti_debugfs:s0 tclass=file permissive=0
09-26 21:40:48.649   754   754 W memtrack@1.0-se: type=1400 audit(0.0:38923): avc: denied { read } for name="mem" dev="debugfs" ino=2728600 scontext=u:r:hal_memtrack_default:s0 tcontext=u:object_r:qti_debugfs:s0 tclass=file permissive=0
09-26 21:40:51.129  3181 22632 I WearableConn: Connecting to "TicWatch C2"
09-26 21:40:51.130  3181 22632 W BluetoothAdapter: getBluetoothService() called with no BluetoothManagerCallback
09-26 21:40:51.229 22419 22419 I chatty  : uid=10158(com.google.android.wearable.app) expire 7 lines
09-26 21:40:51.275 22419 22430 I chatty  : uid=10158(com.google.android.wearable.app) expire 1 line
09-26 21:40:51.096  2329  2475 W MiuiGesturePointerEventListener: onActionDown end: mGestureStatus = 0
09-26 21:40:51.287  2329  2344 W BroadcastQueueInjector: Unable to launch app com.spotify.music/10188 for broadcast Intent { act=android.bluetooth.device.action.ACL_DISCONNECTED flg=0x5000010 (has extras) }: process is not permitted to  auto start
09-26 21:40:51.287  2492  2492 I chatty  : uid=1002(bluetooth) expire 12 lines
09-26 21:40:51.290  3181  3181 I TrustAgent.Tracker: [BluetoothConnectionTracker] Bluetooth disconnect broadast for TicWatch C2 98:28:A6:E6:E8:D4
09-26 21:40:51.306  2329  8315 I chatty  : uid=1000(system) Binder:2329_1F expire 33 lines
09-26 21:40:51.308  2329  2339 I chatty  : uid=1000(system) Binder:2329_1 expire 19 lines
09-26 21:40:51.321  3181  3181 I NearbyDiscovery: onAclChange: state=DISCONNECTED, device=98:28:A6:E6:E8:D4 [CONTEXT service_id=49 ]
09-26 21:40:51.398 22435 22493 I chatty  : uid=10158(com.google.android.wearable.app) expire 84 lines
09-26 21:40:51.556  2329  2344 W BroadcastQueueInjector: Unable to launch app com.spotify.music/10188 for broadcast Intent { act=android.bluetooth.device.action.ACL_CONNECTED flg=0x5000010 (has extras) }: process is not permitted to  auto start
09-26 21:40:51.564  3181  3181 I TrustAgent.Tracker: [BluetoothConnectionTracker] Bluetooth connect broadast for TicWatch C2 98:28:A6:E6:E8:D4
09-26 21:40:51.619  3181 22632 W WearableConn: Failed to connect, error: read failed, socket might closed or timeout, read ret: -1
09-26 21:40:51.619  3181 22632 D BluetoothSocket: close() this: android.bluetooth.BluetoothSocket@75b7bf6, channel: -1, mSocketIS: android.net.LocalSocketImpl$SocketInputStream@7fcebf7, mSocketOS: android.net.LocalSocketImpl$SocketOutputStream@e9fea64mSocket: android.net.LocalSocket@d974cd impl:android.net.LocalSocketImpl@1bb6182 fd:java.io.FileDescriptor@10a5093, mSocketState: INIT

Code: Select all

09-26 21:47:09.432 23519 23588 W WearableHostUtil: Unsuccessful GMScore request: Status{statusCode=ERROR, resolution=null}
09-26 21:47:09.432 23519 23588 W WearableHostUtil: java.lang.Exception
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.host.WearableHostUtil.awaitInternal(AW771527612:50)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.host.WearableHostUtil.await(AW771527612:62)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.host.WearableHost.await(AW771527612:28)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.companion.device.DefaultOemSetupItemFetcher.fetchItem(AW771527612:4)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.companion.device.DeviceManager$RebuildDeviceInfoListTask.doInBackground(AW771527612:20)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.common.concurrent.CwAsyncTask$WorkerRunnable.call(AW771527612:7)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:458)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at java.util.concurrent.FutureTask.run(FutureTask.java:266)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.common.concurrent.InstrumentedTask.run(AW771527612:35)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.common.concurrent.PooledThreadPoolExecutor$Worker.run(AW771527612:16)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at com.google.android.clockwork.common.concurrent.CwPriorityRunnable.run(AW771527612:14)
09-26 21:47:09.432 23519 23588 W WearableHostUtil:      at java.lang.Thread.run(Thread.java:764)
09-26 21:47:09.432 23519 23588 W DfltDevicePrefsHlpr: OEM settings is null for config: ConnectionConfiguration[ mName=TicWatch C2 0879, mAddress=98:28:A6:E6:E8:D4, mType=1, mRole=1, mEnabled=false, mIsConnected=false, mPeerNodeId=null, mBtlePriority=true, mNodeId=null]
Greetings prodigy!

I'm sorry to say, I'm not making any progress yet. I am still pushing this with one of the engineers but, so far, I haven't been able to get any useful answers. I'll let him know that you posted some logs and see if he can take a look at those.

Thanks for providing more information. You can't have too much..
Sabertooth
Mobvoi Global Moderator

Post Reply