-
Notifications
You must be signed in to change notification settings - Fork 19
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
lsusb after libusb setup crashes debian bookworm root session #44
Comments
What to blameWhat happenedART / Dalvik (I have no idea of your Android device) VM crash. How does it workThe libusb wrapper library accesses LibUsbManager to:
Where it could crashTaking into account that you has an output about at least one device:
What to do
|
Another possible cause or "Hello, Android 10"
I need one more day to recheck. |
The crashes were happening on Android 13 on a Pixel 7a, so definitely could be some newer platform changes causing issues.
I was able to use I can open a new issue for that so we can dig in a bit more without polluting this crash beyond "it mostly worked on Android 10". |
Yes, please open a new one. The fix for this one is almost there: green-green-avk/LibUsbManager@7a1c4f2 |
…een-avk:libusbmanager:1.11 #44
…een-avk:libusbmanager:1.11 #44
In review on Google Play now... |
The fixed version should be available on Google Play now. Please, check. |
I tested the version from GitHub and it is working, I'll go check the Play Store one shortly but I'm pretty confident it should work as well as long as the Android 10 plugin is also installed. |
Fixed due to my own tests. |
I'm trying to interface with a USB device and Termux wasn't really helping, so when I found your excellent tool I decided to try it out. My first attempt with Alpine had some other issues with the software I was trying to compile but I got things built under Debian, but now when I try to list the devices I get the permission prompt and can accept it, and it prints the correct device info, but then immediately kills the session which must close the USB connection because running the compiled application in a new session reports it can't find a compatible device.
To add a few more details, the device I'm attempting to access presents various HID interfaces for programming and interacting with the device, I've been able to interact with it from Linux easily, from a Chromebook with a couple limitations in the Crostini Linux apps environment, and now Android is my next battlefield.
lsusb
https://photos.app.goo.gl/gMNgYaLzggH4hCYa8
with -v and -d 1209:
https://photos.app.goo.gl/jy4J3hiTwzq6MTxz8
The text was updated successfully, but these errors were encountered: