Arnav Singh
Arnav Singh
`drop(env_logger::init());` -> `env_logger::init();` looks fine, but `drop(A::new());` -> `A::new();` looks like a typo. I think it would be better to suggest `let _ = env_logger::init();` and `let _ = A::new();`
Looking at `ADB_TRACE=all adb server nodaemon`, I see: ``` 08-01 00:25:08.657 16626 16626 D adb : adb_trace.cpp:187 Android Debug Bridge version 1.0.41 08-01 00:25:08.657 16626 16626 D adb : adb_trace.cpp:187...
Forgot to say, according to strace it certainly seems to be enumerating all the USB devices. But again I don't have debug symbols right now to see what exactly libusb...
I built debug packages of adb and libusb and found the issue. [adb calls:](https://android.googlesource.com/platform/packages/modules/adb.git/+/ce9ea51f30f69f7560db692f7cb4d5d5502c3653/client/usb_libusb.cpp#1064) ```c rc = libusb_hotplug_register_callback( nullptr, static_cast(LIBUSB_HOTPLUG_EVENT_DEVICE_ARRIVED | LIBUSB_HOTPLUG_EVENT_DEVICE_LEFT), LIBUSB_HOTPLUG_ENUMERATE, LIBUSB_HOTPLUG_MATCH_ANY, LIBUSB_HOTPLUG_MATCH_ANY, LIBUSB_CLASS_PER_INTERFACE, hotplug_callback, nullptr, nullptr); ```...
(Just to repeat what I wrote in the Alpine issue, I don't plan to talk to Android upstream about this bug or the patch myself. omasanori brought it up in...
Just based on eyeballing [the code,](https://android.googlesource.com/platform/packages/modules/adb.git/+/1cf2f017d312f73b3dc53bda85ef2610e35a80e9/client/usb_libusb_hotplug.cpp#225) the bug is still not fixed in current main branch, but I haven't tested it to be sure.
>The `PinePhone` was released in 2020, after CTS started to mandate `Base Class 00h`. They are not Android certified compatible phones. (Nit: The device in question is not the PinePhone...
https://docs.rs/crate/reqwest_mock/ perhaps? I haven't used it myself.
These are standard errors for all Steam games because Steam puts both the 32-bit and 64-bit libs in preload env var for every process. One of them will work and...