Then I guess you need to make it work without Windows first. sys-usb should behave in the same way as a regular Linux OS, so Android phone should be recognized. See this for details: Connecting GrapheneOS phone to Qubes .
See also:
opened 10:34PM - 05 Jan 21 UTC
T: bug
P: default
hardware support
C: usb proxy
needs diagnosis
affects-4.1
affects-4.2
<!-- IMPORTANT: Please read our issue tracker guidelines before submitting this … issue:
https://www.qubes-os.org/doc/reporting-bugs/
Please do not delete or remove any part of this issue template. -->
### Qubes OS version:
R4.0 up to date current, Android 11 (Pixel phone up to date 5 dec 20 - reference platform)
f32 target Qube, f32-min sys-usb
### Affected component(s) or functionality:
USB handling - dom0
---
### Steps to reproduce the behavior:
Attach Android 11 device with file transfer enabled to a Qube running Nautilus.
### Expected or desired behavior:
Entry for device appears in menu in Nautilus and I can select that item to browse the filesystem on the Android device.
### Actual behavior:
Menu item appears as expected, however selection goes away for 5-10 sec then gives a popup "Unable to connect to MTP device 00n,00n" and deletes the Nautilus menu item.
### General notes:
Please see forum thread for more details:
https://qubes-os.discourse.group/t/how-can-i-connect-to-android-via-usb/2101
An older v8 Android does partially work: same error popup in Nautilus, dismiss that, detach and reattach, then works as expected.
If looking into this I did notice another bug in the device widget communication - if Android file transfer is enabled or disabled while attached to a Qube the attachment is dropped in dom0, however the widget is not notified. Attempting detach in the widget gives a not attached error popup.
---
### I have consulted the following relevant [documentation](https://www.qubes-os.org/doc/):
### I am aware of the following related, [non-duplicate](https://www.qubes-os.org/doc/reporting-bugs/#new-issues-should-not-be-duplicates-of-existing-issues) issues:
opened 02:21PM - 09 Mar 20 UTC
T: enhancement
C: other
P: default
hardware support
**The problem you're addressing (if any)**
As discussed in the closed issue tic… ket here: https://github.com/QubesOS/qubes-issues/issues/2202
Android devices in debugging mode (ie: for Android app development) cannot be attached to a VM.
**Describe the solution you'd like**
Provide a way to connect the Android device while in USB debugging mode. Even a special-case script or some kind of config option would be better than nothing.
**Where is the value to a user, and who might that user be?**
Android developers can use Qubes for work.
**Describe alternatives you've considered**
There is an ADB over TCP workaround, but this is not ideal, and also requires that the user be connected to a network.
EDIT: This workaround isn't even feasible on most Android devices, as the `ADB over network` setting is not exposed via any UI, and must be activated by a shell command via ADB. So, you still need a working USB ADB connection in order to hand over to WiFi ADB. Additionally, this setting reverts when the phone is rebooted, making it impossible to "set and forget."
**Related, [non-duplicate](https://www.qubes-os.org/doc/reporting-bugs/#new-issues-should-not-be-duplicates-of-existing-issues) issues**
https://github.com/QubesOS/qubes-issues/issues/2202