Eclipse Real-Machine debug shows a workaround for target unknown

Eclipse's Android simulator debugging is a flawed, very very card, seriously affecting the efficiency. Personal recommended use of third-party simulator Genymotion, do not understand can search under installation. You will find it really useful, but need to register the official website.

All kinds of debugging, you need to test on the real machine.

A new Android, do not understand the connection, directly plugged in, Eclipse-->run as-->target-->active devices. The connection is not found, and the target unknown is displayed.

Search all kinds of methods, but also tried the following first method, and then eggs.

Back again check the Android phone driver, USB debugging license on the phone. On the phone for a long while did not find the latter, I was puzzled. It suddenly occurred to me that there was a developer mode on the Android and it wouldn't be the problem. Baidu also the mobile phone developer mode settings, the successful connection. The original part of the Android machine will be deliberately hidden up.

So, when the connection is not up, please check whether the phone driver is installed, the phone is set up USB debugging . If you do not connect again, please refer to the method below.

Other methods

Method One:

1. Close Eclipse (Close eclipse)
2. End the Adb.exe process (using Windows Task Manager) (end Adb.exe process with Task Manager)
3. Restart Eclipse (the device is now recognized in Android device Chooser) (restart Eclipse)

Method Two:

http://blog.csdn.net/yuanjingjiang/article/details/11297433

Eclipse Real-Machine debug shows a workaround for target unknown