As in the subject, I never tried it before. Now I attached it to my sys-usb but only camera is recognized. I’d prefer to attach it so to be recognized as storage too and I choose File transfer on a tablet to no avail.
I am on a 4.3 and I have no policy or entry that sounds like InputTablet, if that is relevant at all.
Where to start, please?
I am on a 4.3 and I have no policy or entry that sounds like InputTablet, if that is relevant at all.
That is in /etc/qubes/policy.d/50-config-input.policy but unlikely what you need for storage.
Where to start, please?
If it is storage, then you set the storage option on the tablet itself (it seems you have done this with “file transfer”). Then it should appear as storage when you connect it. If it doesn’t, then it is not recognized as storage. Perhaps looking at sys-usb’s journalctl -f at the time you connect the device will tell you more.
This is all it happens:
Jul 04 16:19:41 sys-usb kernel: usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jul 04 16:19:41 sys-usb kernel: usb 1-1: Product: HiddenByMe
Jul 04 16:19:41 sys-usb kernel: usb 1-1: Manufacturer: NNM
Jul 04 16:19:41 sys-usb kernel: usb 1-1: SerialNumber: 123456
Jul 04 16:19:41 sys-usb usbauth[282209]: Config file not found or empty.
Jul 04 16:19:41 sys-usb usbauth[282214]: Config file not found or empty.
Obviously, developer options have to be enabled on the tablet, then USB debugging to be enabled in order to be shown in Device widget, same as with Android mobile phones. Meaning, no attaching to other qubes too…
It is interesting that in Device widget it is listed under Other and not as a storage device, whatever I choose on a tablet for an USB connection. It’s either Camera, or Other.
What template are you using for sys-usb?
Thy using a Fedora template. It has much newer drivers and will be more compatible with newer electronics connected to it.
Maybe try a non-minimal template, if that is what you are running. Also check that the minimal-usbvm is not enabled in the qubes Settings, Services.
This will give you the majority, if not all of the functionality from the device and you don’t have to enable developer options or USB debugging.
If there is still functionality that you can’t get that way, then you’ll have rebuild the kernel with the driver for your device and set the qube Kernel to (provided by qube) in the Settings.
This is advance though, and requires tinkering, and also reduces Qubes OS security since the qube is using its own Kernel.
Thanks. I think it’s not about computer, it’s about attaching Android to computer. I just forgot that, if I can properly recall, it is not possible to attach Android storage to another qube, but it’s only browsable in a sys-usb qube when mounted. And I am not kin to mount it in sys-usb, even in a fully non-named usb dispVM in order to prevent controller poisoning,
Also, beside accessing the storage and using the tablet as pointing device (is that what qubes.InputTablet is for or is it for laptops with thouch screen?), I am not aware of any other functionalities I could get from a tablet? I am complete noob to tablets (unlike “dkms-ing” and using qube’s own kernels), so most probably I am wrong about all of these and I admit you are entitled to laugh now…
No, you are right. You can’t pass it to another qube, but you can get the same functionality as any other OS on sys-usb.
Yep, I guess with some android for linux qube, I am recalling intentionally archived memories about phones and Qubes and completing the picture now.
This whole topic was a complete waste of time for me, but especially for you guys, so I’m apologizing.
It’s all good. You know something you didn’t before, not a waste of time.