为什么Eclipse和亚洲开发银行不承认我的Andr​​oid设备?我的、亚洲、不承认、开发银行

2023-09-03 23:03:47 作者:陌顏兒

我的设备是阿尔卡特的OneTouch 890与Android 2.1。我配置的 rules.d 51 android.rules / etc / udev以文件夹。

我的操作系统是Ubuntu Linux系统。

我启用了在我的设备中的USB调试模式。

HTC和三星设备的检测,但不是我的阿尔卡特,

下面是我的 51 android.rules 文件。

  #HTC
SUBSYSTEM ==USB,SYSFS {idVendor} ==0BB4,MODE =0666
SUBSYSTEM ==USB_DEVICE,SYSFS {idVendor} ==0BB4,MODE =0666
#samsung
SUBSYSTEM ==USB,SYSFS {idVendor} ==04e8,MODE =0666
SUBSYSTEM ==USB_DEVICE,SYSFS {idVendor} ==04e8,ATTRS {idProduct} ==689e,MODE =0666,OWNER =ABCD
#alcatel
SUBSYSTEM ==USB,SYSFS {idVendor} ==1BBB,MODE =0666
SUBSYSTEM ==USB_DEVICE,SYSFS {idVendor} ==1BBB,MODE =0666


根@ ABCD:/家庭/ ABCD#的lsusb
公交005设备002:ID 0461:4d15致伸电子有限公司戴尔光电鼠标
公交005设备001:ID 1d6b:0001 Linux基金会1.1根集线器
公交004设备001:ID 1d6b:0001 Linux基金会1.1根集线器
公交003设备001:ID 1d6b:0001 Linux基金会1.1根集线器
公交002设备001:ID 1d6b:0001 Linux基金会1.1根集线器
公交001设备006:ID 1BBB:00F2 T&放大器;移动电话//什么是T&放大器;一个在这一行....?
公交001设备001:ID 1d6b:0002 Linux基金会2.0根集线器
根@ ABCD:/家庭/ ABCD#的Andr​​oid / Android的SDK-linux_86 /平台工具/ ADB设备
设备名单附后
 

解决方案

首先,检查那种在你的udev规则正在使用引号。它看起来像您可能使用非ASCII双引号。看到周围的引号之间的差异 USB USB_DEVICE 等。

  SUBSYSTEM ==USB,SYSFS {idVendor} ==1BBB,MODE =0666
SUBSYSTEM ==USB_DEVICE,SYSFS {idVendor} ==1BBB,MODE =0666
 

您也可以只使用须藤与亚行建议的那样,@JeremyD。这样做,使这个文件基本上是无关紧要的。

其次,

编辑〜/ .android / adb_usb.ini (或者,如果你以root身份运行,检查 /root/.android ) 如果该文件已经存在,添加 0x1bbb 来结束;否则什么:回声0x1bbb>> adb_usb.ini ADB杀死服务器 亚行启动服务器 检查 ADB设备输出设备

希望这有助于。

My device is Alcatel OneTouch 890 with Android 2.1. I configured in 51-android.rules in rules.d of /etc/udev folder.

My operation system is Ubuntu.

I enabled the usb debugging mode in my device.

HTC and Samsung devices are detecting, but not my Alcatel,

Here is my 51-android.rules file.

#HTC
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="0bb4", MODE="0666"
#samsung 
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", MODE="0666"
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="04e8",ATTRS{idProduct}=="689e", MODE="0666",OWNER="abcd"
#alcatel
SUBSYSTEM=="usb", SYSFS{idVendor}=="1bbb", MODE="0666"
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="1bbb", MODE="0666"


root@abcd:/home/abcd# lsusb
Bus 005 Device 002: ID 0461:4d15 Primax Electronics, Ltd Dell Optical Mouse
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 1bbb:00f2 T & A Mobile Phones  // what is T & A in this line....?
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@abcd:/home/abcd# Android/android-sdk-linux_86/platform-tools/adb devices
List of devices attached 

解决方案

First, check the kind of quotes you are using in your udev rules. It looks like you might be using non-ASCII double quotes. See the difference between the quotes around usb and usb_device, etc.

SUBSYSTEM=="usb", SYSFS{idVendor}=="1bbb", MODE="0666"
SUBSYSTEM=="usb_device", SYSFS{idVendor}=="1bbb", MODE="0666"

You can also just use sudo with ADB, as suggested by @JeremyD. Doing that makes this file essentially irrelevant.

Second,

Edit ~/.android/adb_usb.ini (or if you are running as root, check /root/.android) If the file already exists, add 0x1bbb to the end; otherwise do: echo 0x1bbb >> adb_usb.ini adb kill-server adb start-server Check output of adb devices for your device

Hope this helps.