Fedora14 connects to the mobile phone (HTCG1) through USB debugging)

Although there are also simulators for Android development under Fedora, some things need to be tested on a real machine after all, such as gravity sensing and cameras. I thought that I had configured the development environment. After selecting "USB debugging", I inserted the USB to connect to the computer for a real machine test. I did not expect that although Fedora could detect my mobile phone or even the phone model, it could not be correctly recognized by Eclispe, leading to USB debugging failure. Google has encountered many problems, but many of them are Ubun.

Although there are also simulators for Android development under Fedora, some things need to be tested on a real machine after all, such as gravity sensing and cameras. I thought that I had configured the development environment. After selecting "USB debugging", I inserted the USB to connect to the computer for a real machine test. I did not expect that although Fedora could detect my mobile phone or even the phone model, it could not be correctly recognized by Eclispe, leading to USB debugging failure.

Google has encountered many problems, but many of them are the solution of Ubuntu. Of course, the same method is similar for Linux. Sadly, it seems that Ubuntu and Fedora are both Linux, but they have different advantages. When the failure ended, Huang Tianyan had no worries and finally found the clue:

Install Android development environment in Linux and USB debugging mode link mobile phone Development http://www.linuxidc.com/Linux/2010-06/26659.htm

For my Fedora 14 and HTC G1, the specific practices are as follows:
1. Find the device number

[Liang @ localhost ~] $ Lsusb
Bus 006 Device 001: ID 1d6b: 0001 Linux Foundation 1.1 root hub
Bus 005 Device 010: ID 04fc: 0003 Sunplus Technology Co., Ltd CM1092 Optical Scroller 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 008: ID 0bb4: 0c02 High Tech Computer Corp. Dream/ADP1/G1 Phone (Debug)
Bus 002 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b: 0002 Linux Foundation 2.0 root hub

The ID of G1 is "0bb4"

2. Create a file:

[Liang @ localhost ~] $ Sudo gedit/etc/udev/rules. d/50-android.rules

Then write the following content in the file:

SUBSYSTEM = "usb", SYSFS {idVendor} = "0bb4", SYMLINK + = "android_adb", MODE = "0666", OWNER = "liang"

I will not elaborate on each parameter, that is, the OWNER changes it to his username, And the SYMLINK is followed by "+ =". I have not typed it wrong !!! Save and exit.

3. Make the configuration file take effect:

[Liang @ localhost ~] $ Sudo udevadm control -- reload-rules

I added the following step based on my situation (for the Fedora 14 Environment ):

[Liang @ localhost ~] $ Sudo/etc/init. d/udev-post reload

4. then execute the following command in the directory where the adb program is stored (My adb is not placed in the tools directory, but under the platform-tools directory, alas, it was found for a while ):

[Liang @ localhost platform-tools] $ sudo./adb kill-server
[Liang @ localhost platform-tools] $ sudo./adb start-server

After completing the above steps, you should be able to identify your mobile phone.

Before setting:
[Liang @ localhost platform-tools] $ sudo./adb devices
List of devices attached
???????????? No permissions

After setting:
[Liang @ localhost platform-tools] $ sudo./adb devices
List of devices attached
HT93FLD01220 device

HT93FLD01220 is my HTC G1.