Building for aarch64-linux-android in a privileged/root context

[chris2402]

I'm trying to use nusb in a project targeting aarch64-linux-android, but the binary runs as root with full access to /dev/bus/usb/ — it's not a sandboxed Android app.

Because nusb gates the Linux usbfs APIs behind cfg(not(target_os = "android")), I lose access to list_devices and other core functionality when compiling for the Android target, even though the underlying kernel interface is available to me.

Is there a recommended way to handle this today?

I noticed PR #150 is working on Android support through the Java UsbManager path, which makes sense for normal apps. My use case is different — I just need the same Linux backend that works on desktop Linux, since my environment has the same access.

Thanks!

[kevinmehall]

Would Java UsbManager work in your use case if that were merged, or is there a scenario where you're on Android but that is not available? I hadn't planned on supporting sysfs enumeration on Android, but if it's necessary we could look at a configuration option or something.