Skip to content
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

Samsung GalaxyBook Pro 360 on Windows 11 not attaching to WearAuthn on Samsung Watch 4 on Wear 3.0 #15

Open
oluwadiya opened this issue Jan 18, 2022 · 7 comments

Comments

@oluwadiya
Copy link

What went wrong?

I have a Samsung GalaxyBook Pro 360 running Windows 11 paired with Samsung galaxy watch 4 running Wear 3.0. When selecting GalaxyBook in the WearAuthn app, it just stays at "Attaching". The computer shows that the watch is connected. I have paired and unpaired and I have reinstalled Wearauthn to no avail.
NB: I tried the "Make discoverable" trick. It didn't work as well

Steps to reproduce

  1. Install app on watch
  2. Connected the computer and the watch on Bluetooth
  3. Click on the Computer in the list of devices
  4. Click "Make discoverable"

Which model is your watch?
If you don't know your watch's model, you can find it under Settings -> System -> About.
Galaxy Watch 4
Which Android version is running on your watch?
You can find it under Settings -> System -> About -> Version.
Wear 3.0
Which version of WearAuthn are you using?
You can find the version of WearAuthn you are currently using in the About screen available from the app's main menu.
0.9.17
Screenshots
If you think that it could be useful, consider adding a screenshot. To take a screenshot of your watch, open the "Wear OS by Google" app on your phone, open themenu in the top right and select "Take screenshot of watch". After a few seconds, you will receive a notification on your phone that allows you to download or share the screenshot.

@oluwadiya oluwadiya changed the title GalaxyBook Pro 360 on Windows 11 not attaching to WearAuthn Samsung GalaxyBook Pro 360 on Windows 11 not attaching to WearAuthn Jan 18, 2022
@oluwadiya oluwadiya changed the title Samsung GalaxyBook Pro 360 on Windows 11 not attaching to WearAuthn Samsung GalaxyBook Pro 360 on Windows 11 not attaching to WearAuthn on Samsung Watch 4 on Wear 3.0 Jan 18, 2022
@fmeum
Copy link
Owner

fmeum commented Feb 3, 2022

Thanks for the report!

Have you tried connecting your watch to other devices? It would be interesting to know whether this likely a problem specific to this watch model or a problem specific to this combination of laptop and watch model.

@oluwadiya
Copy link
Author

oluwadiya commented Feb 3, 2022 via email

@DerpSpears
Copy link

You're right I will try that on my windows 10 laptop Kehinde S Oluwadiya MBBS(Ib), MD, FMCS, NUCViHEP. Professor of Surgery (Orthopedics & Traumatology) Ekiti State University, Ado-Ekiti Consultant Orthopaedic Surgeon Ekiti State University Teaching Hospital, Ado Ekiti Personal: www.oluwadiya.com University: www.eksu.edu.ng Chairman, Governing Council College of Health Sciences and Technology, Ijero-Ekiti, Nigeria.

On Thu, Feb 3, 2022, 07:56 Fabian Meumertzheim @.> wrote: Thanks for the report! Have you tried connecting your watch to other devices? It would be interesting to know whether this likely a problem specific to this watch model or a problem specific to this combination of laptop and watch model. — Reply to this email directly, view it on GitHub <#15 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/APWBTNJU6GHU2RQVPTNI7ITUZIRKNANCNFSM5MF7PGYA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you authored the thread.Message ID: @.>

so a quick question did it work?

@DerpSpears
Copy link

It seems to be a windows 11 issue I think because on windows 10 it works fine.

@fmeum
Copy link
Owner

fmeum commented Mar 4, 2022

I don't have access to a Windows 11 device atm, but will give this a try when I get the chance. Windows keeps locking down access to non-standard FIDO devices more and more, so I wouldn't be surprised if there isn't much to do against it unfortunately.

@oluwadiya
Copy link
Author

oluwadiya commented Mar 4, 2022 via email

@VNRARA
Copy link

VNRARA commented Aug 22, 2023

Check in bluetooth advanced profiles if a hid device is causing issues (CODE10) and reset that. I'll provide instructions later on how to find it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants