permissions do not apply to some devices

[532910]

I have exactly 12d1:1c2c, but this is not the only device which is not available users.

I'm in the plugdev group, and while for example 22d9:2769 (OnePlus 9 Pro) and 22d9:2769 (OPPO Watch) works fine:

% adb devices
List of devices attached
<ID removed>	device
<ID removed>	device

for 12d1:1c2c adb says:

% adb devices
List of devices attached
<ID removed>	no permissions (missing udev rules? user is in the plugdev group); see [http://developer.android.com/tools/device.html]

Looking at 51-android.rules it seems like 12d1:1c2c is not the only device which is not available users, other Huawei devices are also affected:

#   MediaPad T3
ATTR{idProduct}=="107d", SYMLINK+="android_adb"
#   P10 Lite
ATTR{idProduct}=="107e", SYMLINK+="android_adb"
#   Watch
ATTR{idProduct}=="1c2c", SYMLINK+="android_adb"
#   Mate 9
ATTR{idProduct}=="107e", SYMLINK+="android_adb"

And not only Huawei, but also HTC, LG, Motorola are affected.

[JoesCat]

Hi @532910,
51-android.rules was devolving into a bit of ambiguity, so I went and re-wrote a lot of the code to be more specific. You'll see several commits at upto about 2023nov26 with titles like ..."use more specific adb GOTOs"...

This helped clean-up several phones, but there were a lot of phones that also were big question marks that had to be left aside for a future date due to lack of info, and lack of anyone with more info to help push this further ahead.

Problem lines were like:

ATTR{idProduct}=="????", SYMLINK+="android_adb"

which really did not provide enough info as to what was happening. You have a couple of them listed above, and yes, Huawei, plus a couple of other phones also lacked sufficient info to push this ahead further.

If you can read through issue #264, this gives you a pretty good idea of the wealth of info that could be helpful in helping solve all the devices you have mentioned.

For example, you have '12d1:1c2c', and it is included at about line 391, but may be listed incorrectly as adbfast, maybe it should be something else like adbmtp or some other code.

Can you cycle through the various modes and provide info, similar to issue#264 ?
This would be helpful to help clean this up.

You also mentioned other phones and devices, if you can provide us similar info and details, we can also clean-up those phone connection problems too/now. :-)

[JoesCat]

sorry meant line 405, not 391 for '12d1:1c2c'
Any help you can provide will be much appreciated.

[JoesCat]

Hi @532910, can you test #346 to verify your watch works?

[M0Rf30]

Closed as stale,