Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upUSB connected android phone does not show up as USB block device #1375
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
|
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Nov 4, 2015
Member
Maybe... it isn't a block device at all, but expose some fancy media
transfer interface like PTP? Check lsusb -v to see what interfaces are
there.
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
Maybe... it isn't a block device at all, but expose some fancy media Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
unman
Nov 4, 2015
Member
Google switched to use MTP some time ago - you'll need simple-mtpfs installed and mtp libs.
My droid comes with a separate app for connecting media storage: much easier.
Not a Qubes issue.
|
Google switched to use MTP some time ago - you'll need simple-mtpfs installed and mtp libs. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Nov 4, 2015
Member
Yes, only fancy.
- media device (MTP)
- camera (PTP)
lspci -v
00:00.0 Host bridge: Intel Corporation Crystal Well DRAM Controller (rev 08)
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: bus master, fast devsel, latency 0
Capabilities: <access denied>
00:02.0 VGA compatible controller: Intel Corporation Crystal Well Integrated Graphics Controller (rev 08) (prog-if 00 [VGA controller])
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: bus master, fast devsel, latency 0, IRQ 77
Memory at f7800000 (64-bit, non-prefetchable) [size=4M]
Memory at e0000000 (64-bit, prefetchable) [size=256M]
I/O ports at f000 [size=64]
Expansion ROM at <unassigned> [disabled]
Capabilities: <access denied>
Kernel driver in use: i915
Kernel modules: i915
00:03.0 Audio device: Intel Corporation Crystal Well HD Audio Controller (rev 08)
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: bus master, fast devsel, latency 0, IRQ 80
Memory at f7e34000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) (prog-if 30 [XHCI])
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: bus master, medium devsel, latency 0, IRQ 76
Memory at f7e20000 (64-bit, non-prefetchable) [size=64K]
Capabilities: <access denied>
Kernel driver in use: xhci_hcd
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: bus master, fast devsel, latency 0, IRQ 78
Memory at f7e3f000 (64-bit, non-prefetchable) [size=16]
Capabilities: <access denied>
Kernel driver in use: mei_me
Kernel modules: mei_me
00:19.0 Ethernet controller: Intel Corporation Ethernet Connection I217-V (rev 05)
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: bus master, fast devsel, latency 0, IRQ 93
Memory at f7e00000 (32-bit, non-prefetchable) [size=128K]
Memory at f7e3d000 (32-bit, non-prefetchable) [size=4K]
I/O ports at f080 [size=32]
Capabilities: <access denied>
Kernel driver in use: pciback
Kernel modules: e1000e
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) (prog-if 20 [EHCI])
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: bus master, medium devsel, latency 0, IRQ 16
Memory at f7e3c000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 05)
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: bus master, fast devsel, latency 0, IRQ 81
Memory at f7e30000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d5) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 16
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.1 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #2 (rev d5) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 17
Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
Memory behind bridge: f7d00000-f7dfffff
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d5) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0, IRQ 19
Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
Memory behind bridge: f7c00000-f7cfffff
Capabilities: <access denied>
Kernel driver in use: pcieport
Kernel modules: shpchp
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 05) (prog-if 20 [EHCI])
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: bus master, medium devsel, latency 0, IRQ 23
Memory at f7e3b000 (32-bit, non-prefetchable) [size=1K]
Capabilities: <access denied>
Kernel driver in use: ehci-pci
00:1f.0 ISA bridge: Intel Corporation HM87 Express LPC Controller (rev 05)
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: bus master, medium devsel, latency 0
Capabilities: <access denied>
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 05) (prog-if 01 [AHCI 1.0])
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: bus master, 66MHz, medium devsel, latency 0, IRQ 75
I/O ports at f0d0 [size=8]
I/O ports at f0c0 [size=4]
I/O ports at f0b0 [size=8]
I/O ports at f0a0 [size=4]
I/O ports at f060 [size=32]
Memory at f7e3a000 (32-bit, non-prefetchable) [size=2K]
Capabilities: <access denied>
Kernel driver in use: ahci
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 05)
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: medium devsel, IRQ 18
Memory at f7e39000 (64-bit, non-prefetchable) [size=256]
I/O ports at f040 [size=32]
Kernel modules: i2c_i801
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5229 PCI Express Card Reader (rev 01)
Subsystem: CLEVO/KAPOK Computer Device 7410
Flags: bus master, fast devsel, latency 0, IRQ 79
Memory at f7d00000 (32-bit, non-prefetchable) [size=4K]
Capabilities: <access denied>
Kernel driver in use: rtsx_pci
Kernel modules: rtsx_pci
03:00.0 Network controller: Intel Corporation Wireless 3160 (rev 83)
Subsystem: Intel Corporation Dual Band Wireless-AC 3160
Flags: bus master, fast devsel, latency 0, IRQ 94
Memory at f7c00000 (64-bit, non-prefetchable) [size=8K]
Capabilities: <access denied>
Kernel driver in use: pciback
Kernel modules: iwlwifi
|
Yes, only fancy.
|
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Nov 4, 2015
Member
Not a Qubes issue.
I think it is. On Debian systems last time I tried, the very same device worked out of the box. Not so on Qubes. So I think it's s usability issue.
Google switched to use MTP some time ago - you'll need simple-mtpfs installed and mtp libs.
These would have to be installed in dom0? This might work as a workaround, but is this a good, secure solution, long term? If it was (rather unlikely, I guess...), then we should install these packages by default, no?
Perhaps #531 + #704 would be the proper fix for this ticket?
I think it is. On Debian systems last time I tried, the very same device worked out of the box. Not so on Qubes. So I think it's s usability issue.
These would have to be installed in dom0? This might work as a workaround, but is this a good, secure solution, long term? If it was (rather unlikely, I guess...), then we should install these packages by default, no? Perhaps #531 + #704 would be the proper fix for this ticket? |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
unman
Nov 4, 2015
Member
Not a Qubes issue.
I think it is. On Debian systems last time I tried, the very same device worked out of the box. Not so on Qubes. So I think it's s usability issue.
It's a Linux issue, if anything.
Whether MTP would work on Debian would depend on what you had installed - I don't think a vanilla install includes those tools. Certainly a vanilla fedora doesn't.
Yes at the moment I believe that would have to be installed in dom0. I wouldnt favour installing by default, but there should be guidance for anyone who needs it until those other issues are done.
It's a Linux issue, if anything. Whether MTP would work on Debian would depend on what you had installed - I don't think a vanilla install includes those tools. Certainly a vanilla fedora doesn't. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Nov 4, 2015
Member
In dom0 or USB VM if you have one. Anyway there is nothing Qubes
specific in accessing those devices.
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
|
In dom0 or USB VM if you have one. Anyway there is nothing Qubes Best Regards, |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Nov 8, 2015
Member
If you want to use the device in the AppVM, then yes - dup of #531. Otherwise (use the device in dom0 or USB VM directly), I don't see anything Qubes-specific here (even needing documentation) - standard usage of Android device.
|
If you want to use the device in the AppVM, then yes - dup of #531. Otherwise (use the device in dom0 or USB VM directly), I don't see anything Qubes-specific here (even needing documentation) - standard usage of Android device. |
adrelanos
closed this
Nov 12, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
Dec 15, 2015
Member
Whether MTP would work on Debian would depend on what you had installed - I don't think a vanilla install includes those tools. Certainly a vanilla fedora doesn't.
Yes at the moment I believe that would have to be installed in dom0. I wouldnt favour installing by default, but there should be guidance for anyone who needs it until those other issues are done.
so it sounds like this needs to be documented since it is a common user issue, and that also MTP tools should be installed by default, since most users will think Qubes is breaking it vs just lacking packages?
so it sounds like this needs to be documented since it is a common user issue, and that also MTP tools should be installed by default, since most users will think Qubes is breaking it vs just lacking packages? |
mfc
added
C: doc
UX
labels
Dec 15, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Dec 15, 2015
Member
MTP tools should be installed by default, since most users will think Qubes is breaking it vs just lacking packages?
We can't install everything by default. We already have problem with too big installation image.
We can't install everything by default. We already have problem with too big installation image. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
mfc
Dec 15, 2015
Member
I agree everything can't be installed by default. talking to phones is pretty basic tho, and because of usbvm etc 90% of users will think it is because Qubes is "too secure" or something.
maybe we can do a read-through of default installed apps with Patrick and find some that aren't required by default. if there is an easy link to that list I can check it out.
|
I agree everything can't be installed by default. talking to phones is pretty basic tho, and because of usbvm etc 90% of users will think it is because Qubes is "too secure" or something. maybe we can do a read-through of default installed apps with Patrick and find some that aren't required by default. if there is an easy link to that list I can check it out. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Dec 15, 2015
Member
Debian:
https://github.com/QubesOS/qubes-builder-debian/tree/master/template_debian (packages_*.list files)
in addition to Debian default list: https://github.com/QubesOS/qubes-builder-debian/blob/master/template_debian/02_install_groups.sh#L39-L48
Fedora:
https://github.com/QubesOS/qubes-builder-fedora/blob/master/template_scripts/packages_fc23.list
Also - most of the packages are just from Fedora default (@workstation-product-environment group)
|
Debian: Fedora: |
adrelanos
reopened this
Dec 15, 2015
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
adrelanos
Dec 15, 2015
Member
Could we create standard Debian templates with Qubes-Builder flavor no-recommends? That would give tighter control about what packages get installed.
Dunno if that would save more than marginal space. Has also potential to introduce new issues. Method to minimize:
- store the installed packages list of a recent Debian template
- create a new Debian template with Qubes-Builder flavor
no-recommends - create a installed packages list of that new template
- compare these package lists
|
Could we create standard Debian templates with Qubes-Builder flavor Dunno if that would save more than marginal space. Has also potential to introduce new issues. Method to minimize:
|
marmarek
added
help wanted
C: templates
labels
Jan 7, 2016
marmarek
added this to the Release 3.2 milestone
Jan 7, 2016
mfc
referenced this issue
Feb 25, 2016
Open
Meta-ticket: suggest/remove default applications in official templates #1781
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Rudd-O
Jun 8, 2016
Android phones stopped appearing as USB mass storage devices a LONG TIME AGO. This was a policy decision at the Android project, as far as I am aware of.
Rudd-O
commented
Jun 8, 2016
|
Android phones stopped appearing as USB mass storage devices a LONG TIME AGO. This was a policy decision at the Android project, as far as I am aware of. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
marmarek
Jun 20, 2016
Member
Original issue is unrelated to Qubes as Android phone is not a block device - closing
|
Original issue is unrelated to Qubes as Android phone is not a block device - closing |
adrelanos commentedNov 4, 2015
Android has two settings:
connected as camera
dom0 journalctl
dom0
lsusbconnected as media device
dom0 journalctl
dom0
lsusbEither way, the USB connected android phone does not show up as USB block device in Qubes VM Manager (QVMM). (Therefore cannot be attached to AppVMs, therefore the phone storage cannot be accessed using Qubes.)
The device also shows not up in
gparted. (Restarted between changing modes.)