Wanted: debian stretch udev rule for FP Fairphone 2 with OpenOS 7.1.2 , v19.02.1

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

Did you search for “udev” already? How about this post

1 Like

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

69-libmtp.rules-ATTR{idVendor}==“2ae5”, ATTR{idProduct}==

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

grep -A1 Qualcomm *
51-android.rules:#Qualcomm
51-android.rules-SUBSYSTEM==“usb”, ATTR{idVendor}==“05c6”, MODE=“0664”, GROUP=“plugdev”

51-android.rules.ins:#Qualcomm
51-android.rules.ins-SUBSYSTEM==“usb”, ATTR{idVendor}==“05c6”, MODE=“0664”, GROUP=“plugdev”

69-libmtp.rules:# Qualcomm (for Nokia) 5530 Xpressmusic
69-libmtp.rules-ATTR{idVendor}==“05c6”, ATTR{idProduct}==“0229”, SYMLINK+=“libmtp-%k”, MODE=“660”, GROUP=“audio”, ENV{ID_MTP_DEVICE}=“1”, ENV{ID_MEDIA_PLAYER}=“1”
69-libmtp.rules:# Qualcomm (for Nokia/Verizon) 6205 Balboa/Verizon Music Phone
69-libmtp.rules-ATTR{idVendor}==“05c6”, ATTR{idProduct}==“3196”, SYMLINK+=“libmtp-%k”, MODE=“660”, GROUP=“audio”, ENV{ID_MTP_DEVICE}=“1”, ENV{ID_MEDIA_PLAYER}=“1”
69-libmtp.rules:# Qualcomm (for Gigabyte) GSmart G1342
69-libmtp.rules-ATTR{idVendor}==“05c6”, ATTR{idProduct}==“8800”, SYMLINK+=“libmtp-%k”, MODE=“660”, GROUP=“audio”, ENV{ID_MTP_DEVICE}=“1”, ENV{ID_MEDIA_PLAYER}=“1”
69-libmtp.rules:# Qualcomm (for Smartfren) Andromax U
69-libmtp.rules-ATTR{idVendor}==“05c6”, ATTR{idProduct}==“9025”, SYMLINK+=“libmtp-%k”, MODE=“660”, GROUP=“audio”, ENV{ID_MTP_DEVICE}=“1”, ENV{ID_MEDIA_PLAYER}=“1”
69-libmtp.rules:# Qualcomm (for OnePlus) One (MTP)
69-libmtp.rules-ATTR{idVendor}==“05c6”, ATTR{idProduct}==“6764”, SYMLINK+=“libmtp-%k”, MODE=“660”, GROUP=“audio”, ENV{ID_MTP_DEVICE}=“1”, ENV{ID_MEDIA_PLAYER}=“1”
69-libmtp.rules:# Qualcomm (for OnePlus) One (MTP+ADB)
69-libmtp.rules-ATTR{idVendor}==“05c6”, ATTR{idProduct}==“6765”, SYMLINK+=“libmtp-%k”, MODE=“660”, GROUP=“audio”, ENV{ID_MTP_DEVICE}=“1”, ENV{ID_MEDIA_PLAYER}=“1”
69-libmtp.rules:# Qualcomm (for Xolo) Xolo Black (MTP)
69-libmtp.rules-ATTR{idVendor}==“901b”, ATTR{idProduct}==“9039”, SYMLINK+=“libmtp-%k”, MODE=“660”, GROUP=“audio”, ENV{ID_MTP_DEVICE}=“1”, ENV{ID_MEDIA_PLAYER}=“1”
69-libmtp.rules:# Qualcomm (for PhiComm) C230w (MTP)
69-libmtp.rules-ATTR{idVendor}==“05c6”, ATTR{idProduct}==“9039”, SYMLINK+=“libmtp-%k”, MODE=“660”, GROUP=“audio”, ENV{ID_MTP_DEVICE}=“1”, ENV{ID_MEDIA_PLAYER}=“1”
69-libmtp.rules:# Qualcomm (for OnePlus) One Plus 2 (A2003) (MTP)
69-libmtp.rules-ATTR{idVendor}==“05c6”, ATTR{idProduct}==“f003”, SYMLINK+=“libmtp-%k”, MODE=“660”, GROUP=“audio”, ENV{ID_MTP_DEVICE}=“1”, ENV{ID_MEDIA_PLAYER}=“1”
69-libmtp.rules:# Qualcomm (for Highscreen) Omega Prime S
69-libmtp.rules-ATTR{idVendor}==“05c6”, ATTR{idProduct}==“f003”, SYMLINK+=“libmtp-%k”, MODE=“660”, GROUP=“audio”, ENV{ID_MTP_DEVICE}=“1”, ENV{ID_MEDIA_PLAYER}=“1”

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

Hi
Found the rule in debian sid source package
http://deb.debian.org/debian/pool/main/a/android-sdk-meta/android-sdk-meta_25.0.0+8.tar.xz

# Fairphone 2 aka Qualcomm, Inc.
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", ATTR{idProduct}=="901d", ENV{adb_user}="yes"

made a new file 51-android_fairphone2.rules with above contents. I will test now.
That goes fore a temporary fix. If it is final ?
BR Erich

Hello
This was successful

cat /lib/udev/rules.d/51-android_fairphone2.rules 
# Fairphone 2 aka Qualcomm, Inc.
#SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", ATTR{idProduct}=="901d", ENV{adb_user}="yes"
SUBSYSTEM=="usb", ATTR{idVendor}=="05c6", MODE="0666", GROUP="plugdev", ENV{adb_user}="yes" 

can debug now also as usr

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.