Hi
I am searching for a Proper udev rule for my Fairphone 2 with OpenOS
When I connect, dmesg reports :
[111345.496054] usb 2-1: new high-speed USB device number 2 using ehci-pci
[111345.650001] usb 2-1: New USB device found, idVendor=05c6, idProduct=901d
[111345.650006] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[111345.650009] usb 2-1: Product: FP2
[111345.650012] usb 2-1: Manufacturer: Fairphone
[111345.650014] usb 2-1: SerialNumber: xxxxxxxxxx
Looking for these numbers idVendor=05c6, idProduct=901d in the ${SEARCHENGINE}-world does not reveal any result.
Looking for idVendor=05c6 reveals Qualcomm
Looking for idProduct reveals nothing although that Qualcomm occupies nearby hexnumbers
Maybe FP as a client to Qualcomm can bring light to the issue either by looking in their papers or asking Qualcomm
This https://sourceforge.net/p/libmtp/support-requests/214/ shows some other values for the FP2 with OpenOS so What to do?
BR Erich
Hi Amber
Thank you for the hint
I feel that installing an android developer kit which is not from the debian stable for having a 2 line udev rule is a bit overkill. I am not an android developer and do not want to become one or to open another box of worms.
I am Just a client with a nextcloud app 3.5.0 which gets killed when releasing the internal access (after accepted username/password entry ).
I also feel that the result of
/lib/udev/rules.d# grep -A1 Fairphone *
69-libmtp.rules:# Fairphone Fairphone 2
69-libmtp.rules-ATTR{idVendor}==“2ae5”, ATTR{idProduct}==“f003”, SYMLINK+=“libmtp-%k”, MODE=“660”, GROUP=“audio”, ENV{ID_MTP_DEVICE}=“1”, ENV{ID_MEDIA_PLAYER}=“1”
69-libmtp.rules:# Fairphone Fairphone 2 OS
69-libmtp.rules-ATTR{idVendor}==“2ae5”, ATTR{idProduct}==“9039”, SYMLINK+=“libmtp-%k”, MODE=“660”, GROUP=“audio”, ENV{ID_MTP_DEVICE}=“1”, ENV{ID_MEDIA_PLAYER}=“1”
already results in a rule for the Fairphone OS, but there is no rule for the Fairphone OpenOS. the rule of Fairphone shall start with
Is there a setting on the FP2 which results in a idVendor / idProduct Combination which has a suitable rule?
Or can I consider it a bug in the OpenOS and then this has to be treated. Meanwhile a udev rule could be formulated for the goofed vendor Id .
There is a number of Qualcomm rules but none with this product id
77-mm-telit-port-types.rules:# NOTE: Qualcomm Gobi-based devices like the LE920 should not be handled
77-mm-telit-port-types.rules-# by this plugin, but by the Gobi plugin.
Probably or maybe a Qualcomm Fairphone2 OpenOS rule is missing.
BR
Erich