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

WF-C700N Support #107

Open
traversone opened this issue Dec 21, 2023 · 7 comments
Open

WF-C700N Support #107

traversone opened this issue Dec 21, 2023 · 7 comments

Comments

@traversone
Copy link

hi all,

when trying to connect this new headset, error 10049 comes out.

May I support the troubleshooting in some way? Thank you!
WF-C700N_error

@Plutoberth
Copy link
Owner

Hi, it's possible that you just need to recompile the app with the correct headset UUID. Please see the comment that was posted by @reformat0r in #105 and report back :)

@traversone
Copy link
Author

unfortunately I feel to be a simple "end user" and I am not able to follow your suggestion. Anyway, how to find out the headset UUID just to start? Thank you

@reformat0r
Copy link

On Linux, you can use bluetoothctl. Issuing the info-command yields:

Device AC:80:0A:XX:XX:XX (public)
        Name: WF-1000XM5
        Alias: WF-1000XM5
        Class: 0x00240404 (2360324)
        Icon: audio-headset
        Paired: yes
        Bonded: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        WakeAllowed: yes
        LegacyPairing: no
        UUID: Vendor specific           (00000000-deca-fade-deca-deafdecacaff)
        [...]
        UUID: Vendor specific           (443cce33-e85d-4b85-8d53-6e319ede53ae)
        UUID: Vendor specific           (45c93e07-d90d-4b93-a9db-91e5dd734e35)
        UUID: Vendor specific           (81c2e72a-0591-443e-a1ff-05f988593351)
        UUID: Vendor specific           (8901dfa8-5c7e-4d8f-9f0c-c2b70683f5f0)
        UUID: Vendor specific           (931c7e8a-540f-4686-b798-e8df0a2ad9f7)
        UUID: Vendor specific           (956c7b26-d49a-4ba8-b03f-b17d393cb6e2)
        UUID: Vendor specific           (9b26d8c0-a8ed-440b-95b0-c4714a518bcc)
        UUID: Vendor specific           (df21fe2c-2515-4fdb-8886-f12c4d67927c)
        UUID: Vendor specific           (f76acb00-7cab-495f-bb1a-e664598fd77f)
        UUID: Vendor specific           (f7a96061-a1b3-40de-aff0-e78ec45a151e)
        UUID: Vendor specific           (f8d1fbe4-7966-4334-8024-ff96c9330e15)
        [...]

@ElonGaties
Copy link

@reformat0r while that does return the UUID, how do you select the correct one? do you just test all of the UUIDs until you find the one that works?

@traversone
Copy link
Author

I am really sorry but I am not able to perform these checks because of my lack of knowledge on Linux

@jonathandw743
Copy link

jonathandw743 commented Sep 10, 2024

I tried this with all the UUIDs what didn't start with 0000 by changing the value in IBluetoothConnector.h and it didn't work.

@mirh
Copy link

mirh commented Sep 29, 2024

FWIW full(?) support was just added to GB
https://codeberg.org/Freeyourgadget/Gadgetbridge/pulls/4168

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

6 participants