Invalid Android Wear connection problem


iShockwave

Members
Dec 8, 2019
8
13
I just installed the rom on my Mi Note 10 and I am very happy so far.
Unfortunately since the installation I cannot get my Fossil Gen5 Android Wear watch to pair.
The Wear OS app sees the watch and initializes the pairing, but when i tap on "pair" at the bluetooth code confiomation nothing happens.
The dialog closes and the app sits on "connecting to watch".

I tried multiple thing, including:
  • Giving wear os all permissions by hand
  • Disabling battery optimisation for WearOS and bluetooth
  • Clearing data of Playstore/Google/WearOS after every attempt
I even looked into the logcat while pairing but nothing to obvious. There was an error about AVRCP:
Code:
12-08 00:22:13.016  3088  3762 W bt_device_profile: profile_feature_fetch:AVRCP_0103_SUPPORT found 0
12-08 00:22:13.017  3088  3762 E bt_sdp  : sdp_get_stored_avrc_tg_version unable to open AVRC Conf file for read: err: (No such file or directory)
12-08 00:22:13.017  3088  3762 E bt_sdp  : Restore Profile version
12-08 00:22:13.017  3088  3762 W bt_device_profile: profile_feature_fetch:profile 1
12-08 00:22:13.017  3088  3762 W bt_device_profile: profile_feature_fetch:AVRCP_0103_SUPPORT found 0
12-08 00:22:13.017  3088  3762 E bt_sdp  : sdp_get_stored_avrc_tg_version unable to open AVRC Conf file for read: err: (No such file or directory)
12-08 00:22:13.017  3088  3762 E bt_sdp  : Stored AVRC TG version: 0x0
12-08 00:22:13.017  3088  3762 E bt_sdp  : Reset Browse feature bitmask
12-08 00:22:13.017  3088  3762 W bt_device_profile: profile_feature_fetch:profile 1
12-08 00:22:13.017  3088  3762 W bt_device_profile: profile_feature_fetch:AVRCP_0103_SUPPORT found 0
12-08 00:22:13.017  3088  3762 E bt_sdp  : sdp_get_stored_avrc_tg_version unable to open AVRC Conf file for read: err: (No such file or directory)

I tried with all AVRCP values in the developer menu, no luck but the error disappeared sometimes.

I will attach a full adb logcat log that starts the moment of patting "pair" with all default setting in developer menu.
As a sidenote, issue is present in weekly/stable for me. Currently on weekly rom
 

Attachments

  • log.txt
    249 KB · Views: 614
Try an official ROM, we have no info about this issue and no way to test this.