Question

I am just starting to learn on Android development. I use Ubuntu 11.10 and Eclipse. I have installed the needed plugins from android development, and I have also write yet some examples that compiles and run fine on the emulator.

但是,像多图象这样的东西无法在投稿人身上测试,因此,我想在我的三星银河S2号真正装置上测试。问题在于,我已经尝试了我在网上发现的所有东西,但是仍然未能使用。

当我操作“adb”装置时,该装置确实没有显示,尽管该装置是附属的。

$ lsusb
...
Bus 001 Device 012: ID 04e8:6860 Samsung Electronics Co., Ltd 
$ ./adb devices
List of devices attached

我已经根据网络指示多次修改了/etc/udev/rules.d/51-android。目前,我有这一行文:

SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", ATTRS{idProduct}="6860", MODE="0666", GROUP="plugdev"

当然,我试图重新启动乔夫和堡服务,甚至重开整个系统,但都没有工作。

任何 h?

预兆

Answer 1

编造装置从设计到设计; 申请-设计; 发展

Answer 2

Try Samsung kies, it delivers suitable ADB driver: http://www.samsung.com/uk/support/usefulsoftware/KIES/JSP

右堡司机(从 k或其它地方)应无谓地工作。

EDIT: on linux: http://developer.android.com/tools/device.html

If you re developing on Ubuntu Linux, you need to add a udev rules file that contains a USB configuration for each type of device you want to use for development. In the rules file, each device manufacturer is identified by a unique vendor ID, as specified by the ATTR{idVendor} property. For a list of vendor IDs, see USB Vendor IDs, below. To set up device detection on Ubuntu Linux: Log in as root and create this file: /etc/udev/rules.d/51-android.rules. Use this format to add each vendor to the file: SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666", GROUP="plugdev"

In this example, the vendor ID is for HTC. The MODE assignment specifies read/write permissions, and GROUP defines which Unix group owns the device node. Note: The rule syntax may vary slightly depending on your environment. Consult the udev documentation for your system as needed. For an overview of rule syntax, see this guide to writing udev rules. Now execute: chmod a+r /etc/udev/rules.d/51-android.rules

Answer 3

Try 另一个USB电缆

如果你有这种可能性,如果它使用另一种装置,就会进行检查。

解决你的问题,确保与软件(如果是的话)相差错

Answer 4

撤出一个终点站的以下指挥系统:

$ echo "0x04e8" >> ~/.android/adb_usb.ini

替换

$ adb kill-server
$ adb start-server

使用<代码>adb 装置列出的装置

Answer 5

我在Mac OS X与Eclipse问题上也经历了同样的问题。简单地将电话放在 de(Settings -> Applications -> Development->USB debugging)上,并不能解决问题。我不得不在指挥线下解决该问题。

sudo adb kill-server
sudo adb start-server

友情链接