Ubuntu12.0464-bit Android Solution

Problem 1: Google has released the ADT17.0.0 and SDKR17 versions. As a result, the adb command cannot be run on Ubuntu12.04X64. The error is as follows: adb: errorwhileloadingsharedlibraries: libncurses. so.5: wrongELFclass: ELFCLASS64, Google's problem is quite common, especially for 6

Question 1:
Google has released ADT 17.0.0 and SDK R17. As a result, it has been installed on Ubuntu 12.04X64 and cannot run the adb command. The error is as follows:

Adb: error while loading shared libraries: libncurses. so.5: wrong ELF class: ELFCLASS64

Check du Niang, Google this problem is quite common, especially for 64-bit Ubuntu, in fact, in a word, did not find the public library, run the following command to deal with it.

Append question: After the system is recently reinstalled, the environment variable configuration is complete, and the adb command is clearly run in the adb directory, but the old display is sudo: adb: command not found, the solution is to download the 32-bit support library.

$ Sudo apt-get install ia32-libs

Question 2:

Adb devices does not have permission

1. $ Adb devices
2. List of devices attached
3. ???????????? No permissions

There are many solutions on the Internet, which are roughly the same. I will record the Processing Methods of my machine.

1. View USB device information using lsusb

1. $ Lsusb
2. Bus 001 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub
3. Bus 002 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub
4. Bus 001 Device 002: ID 8087: 0020 Intel Corp. Integrated Rate Matching Hub
5. Bus 002 Device 002: ID 8087: 0020 Intel Corp. Integrated Rate Matching Hub
6. Bus 001 Device 003: ID 138a: 0007 Validity Sensors, Inc. VFS451 Fingerprint Reader
7. Bus 001 Device 004: ID 17ef: 600e Lenovo
8. Bus 001 Device 005: ID 05c8: 0403 Cheng Uei Precision Industry Co., Ltd (Foxlink) Webcam
9. Bus 002 Device 003: ID 1058: 1110 Western Digital Technologies, Inc.
10. Bus 002 Device 004: ID 062a: 0201 Creative Labs Defender Office Keyboard (K7310) S Zodiak KM-9010
11. Bus 002 Device 007: ID 05c6: 9015 Qualcomm, Inc.

My machine is a Qualcomm-based model, so it shows Bus 002 Device 007: ID 05c6: 9015 Qualcomm, Inc. if you do not know what your machine is, paste the English part to google and check it.

2. Use vim to create a configuration file.

$ Sudo vim/etc/udev/rules. d/70-Android.rules

Enter the following content:

SUBSYSTEM = "usb", ATTRS {idVendor} = "05c6", ATTRS {idProduct} = "9015", MODE = "0666"

In fact, there are two differences between idVendor and idProduct. For more information, see lsusb Bus 002 Device 007: ID05c6: 9015 Qualcomm, Inc.

3. Run the following command:

Sudo chmod a + rx/etc/udev/rules. d/70-android.rules
Sudo/etc/init. d/udev restart

4. Run it in the tools directory of the Android sdk (this step is very important and must be sudo, otherwise it will not work)

Sudo./adb kill-server

5. After the modification is complete, disconnect the USB cable of the mobile phone from the computer. OK will be displayed after the connection!

$ Adb devices
List of devices attached
1234567890 ABCDEF device

References

Ubuntu ADB debugging Android can not find the device solution http://www.linuxidc.com/Linux/2011-04/34131.htm