-
Notifications
You must be signed in to change notification settings - Fork 51
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
Not work on windows #3
Comments
Maybe you need to open your terminal as administrator but here linux-adk for Windows works fine. |
Still not work.
Is there any other operation you do before run it? |
No, actually I confirm that on my end it works fine without admin rights:
Note that this is my libusb revision: f38f09da98acc63966b65b72029b1f7f81166bef |
maybe it's vendor related? I don't have other phones to test... |
1 similar comment
maybe it's vendor related? I don't have other phones to test... |
Nah, the whole point of ADK is not to be vendor specific. But is your phone properly recognized in Windows Device Manager? |
I have a Samsuna Android Device (or something similiar). |
If you're not answering my questions I can't help you. |
I mean it's recognized in Device Manager. I'll try this version tomorrow. |
Do you have an update? If not I'll close this issue as can't repro. |
Please close it because I am on vacation and cannot try it, I'll reopen if I can try and reproduce it. |
Sounds good, thanks for your feedback |
I am implementing HID over AOAv2 for scrcpy, and I found libusb does not work on Windows (related info is https://libusb-devel.narkive.com/vENuKzdR/getting-the-serial-number-of-the-camera-fails), it cannot open Android device and read infos. Then I found this project which starts android accessory first, and I've built this on Visual Studio 2019, run it. Got the same error that it cannot open device:
04E8:6860
is for my Galaxy S9+, did you test it for your phone on windows? How do you manage to make libusb work on Windows?Plus, C macro for Windows is
_WIN32
, notWIN32
.The text was updated successfully, but these errors were encountered: