Eclipse - Target "unknown" in Android device chooser

Question

I am using LG-P500. When I try to select it in the 'Android device chooser', Eclipse recognizes the phone but not the target. It says target "unknown". Because of this problem, I can't choose the phone as the Android device.

How can I get Eclipse to recognize the target?

What's your android version in mobile? And, what's your project version in your manifest? Have you set any `minSDKVersion` or `maxSDKVersion` etc — Praveenkumar, May 24 '12 at 04:58
The minSDKVersion is set to 6. The mobile Android version is 2.2.1. I am actually trying out the BluetoothChat sample app. — user1357350, May 24 '12 at 05:02
Once just unplug your device from eclipse. Restart your eclipse. And, try it out. I've same problem like this — Praveenkumar, May 24 '12 at 05:12
My Eclipse does the same for my phone because I'm running a custom ROM. However, I can launch apps on it through Eclipse without a problem. Are you sure you can't launch them when you try to select the phone, regardless of it saying "unknown"? — Sander van't Veer, May 24 '12 at 05:36
When i'm connecting my device to Eclipse. My DDMS will shows like this [image](http://i.stack.imgur.com/fkw0e.png) with my device. So, has your device shows like this or not? — Praveenkumar, May 24 '12 at 05:55
Had the same problem with an LG phone. Rebooting it worked for me — IncrediApp, May 24 '12 at 06:56
@user1357350 remember to accept answers if you someone/something solves it. — Anders Metnik, May 24 '12 at 07:19
Its solved! @IncrediApp is right. I rebooted the phone and now its working fine. Thank u all for ur help! — user1357350, May 24 '12 at 10:47
Linux users, this did it for me: http://stackoverflow.com/questions/7419964/eclipse-android-device-chooser-unknown-android-2-3-4-device — Nathan H, Nov 25 '13 at 10:05
I had the same problems on a Samsung S4 that was Update to version 4.3 of android without being restarted. After restart it works good. — Flavio Capaccio, Feb 21 '14 at 10:43

score 88 · Accepted Answer · edited Apr 16 '14 at 09:48

88

Had the same problem with an LG phone. Rebooting it (phone) worked for me

edited Apr 16 '14 at 09:48

Mohamed Taher Alrefaie

15,698
9
48
66

answered May 24 '12 at 10:56

IncrediApp

10,303
2
33
24

1

Linux users, this did it for me: http://stackoverflow.com/questions/7419964/eclipse-android-device-chooser-unknown-android-2-3-4-device – Nathan H Nov 25 '13 at 10:05
4

After rebooting I had a pop up come up to allow the connected PC to debug, after selecting ok here, I was able to see the device in my list. – Ian Jamieson Jan 20 '14 at 09:07
I can confirm changing USB port in my case. Much less time consuming then phone reboot. – Anderson Feb 07 '15 at 11:53

Brian Peterson · Answer 2 · 2013-09-14T00:57:02.663

65

One solution I am aware of is to just turn off and on USB Debugging on your phone. It also happens to solve a bunch of other device-not-recognized kinds of problems.

edited Sep 14 '13 at 00:57

answered Sep 17 '12 at 03:41

Brian Peterson

2,800
6
29
36

gratitude to you my friend – Loknar Feb 10 '15 at 10:11

score 22 · Answer 3 · edited Sep 15 '14 at 06:51

22

Follow these steps, if your device is recognised but the eclipse is stating it as unknown:

->open cmd   
->go to the your android sdk directory --> Go to platform-tools
->adb kill-server
->adb start-server

this will definitely solve your problem :)

If you already installed USB driver and still your device showing as unknown then follow this solution. I had same problem with my MOTO G and this solution works fine for me

edited Sep 15 '14 at 06:51

Bhupendra Piprava

228
2
7

answered Apr 12 '13 at 15:33

Yash

5,225
4
32
65

This need to done always when i want to debug on device, isn't there a permanent solution – ameya rote Oct 02 '13 at 08:43
this did the trick for my nexus 9, while all the other solutions did not work. – bolvo Nov 19 '14 at 18:56

Ponmalar · Answer 4 · 2012-05-24T10:47:49.537

9

Check your device that

USB connected

and

USB debugging connected

or Check the following

The solution was to create a udev rule for the device. See http://developer.android.com/guide/developing/device.html#setting-up for how to setup a udev rule for your specific vendor device.

With the rule in place. Eclipse was able to launch and debug.

enter image description here

edited May 24 '12 at 10:47

answered May 24 '12 at 06:54

Ponmalar

6,871
10
50
80

Yes... both connected. Still the same problem. – user1357350 May 24 '12 at 10:40
I had my device connected properly, but it did not have "USB debugging connected" selected. I could not get this selected without changing from MTP (media device) to PTP (camera) and then back again. Mine was a Samsung Galaxy III. – Mike Williamson Dec 30 '13 at 02:12

score 8 · Answer 5 · edited May 05 '14 at 00:57

8

One simple trick works fine for me.

Disconnect device from PC
Tap revoke USB debugging authorization in phone setting
Reconnect device to PC
Tap OK for RSA authorization

edited May 05 '14 at 00:57

andrewsi

10,807
132
35
51

answered May 05 '14 at 00:37

Imam

81
1
1

score 6 · Answer 6 · answered Dec 16 '12 at 02:42

6

The reason that my SCH-I535 device was not being targeted... is because I had the device plugged into a USB 3.0 port. Once I plugged it into a 2.0, everything began to work properly.

answered Dec 16 '12 at 02:42

Anonymous

61
1
1

score 6 · Answer 7 · answered Dec 12 '14 at 12:34

6

Also try this, On your phone:

Go to "USB computer connection"
Select Connect as "Media Device (MTP)"

answered Dec 12 '14 at 12:34

vanguard69

840
1
10
18

score 5 · Answer 8 · answered Jul 09 '13 at 13:50

5

I tried these suggestions, but unfortunately, nothing worked.

What worked for me was:

close Eclipse
end the adb.exe process (using Windows Task Manager)
restart Eclipse (the device was now recognized in Android Device Chooser)

answered Jul 09 '13 at 13:50

kahmali

557
6
10

score 3 · Answer 9 · answered Feb 24 '15 at 11:37

3

Go to Settings -> Storage -> Click on Top right menu button -> USB computer connection-> Check Media device(MTP) is enable or not

answered Feb 24 '15 at 11:37

Krunal Shah

1,438
1
17
29

score 1 · Answer 10 · answered May 24 '12 at 05:41

1

Do you have a driver for your phone installed on your computer, eclipse doesn't automaticly come with drivers for phones.

answered May 24 '12 at 05:41

Anders Metnik

6,096
7
40
79

Yes, I do have the driver installed. – user1357350 May 24 '12 at 10:39

score 1 · Answer 11 · answered Jul 02 '13 at 09:28

1

My problem solved by changing the cable. Nothing else worked for me.

answered Jul 02 '13 at 09:28

seekme_94

162
1
4
17

score 1 · Answer 12 · answered Mar 02 '14 at 10:17

For this problem I had tried disconnecting/reconnecting the USB cable, toggling on/off the USB debugging and relaunching Eclipse with no effect. Trying a different android device showed exactly the same eclipse errors, with two entries marked 'offline' and after disconnecting the USB connection it still showed one entry while nothing was connected. My problem was solved by rebooting my computer and starting again. Probably ending the adb.exe programme (answer 4) would have done it too in my case.

score 1 · Answer 13 · answered May 01 '14 at 03:17

1

GALAXY S5

I know this has been answered heaps of times already but if you have a Galaxy S5 then the turn off and turn on of USB debugging works to resolve this problem

answered May 01 '14 at 03:17

timv

3,346
4
34
43

score 1 · Answer 14 · answered Nov 16 '14 at 03:33

1

When the phone is plugged in and the Eclipse window shows the "Unknown" icon...on the phone turn off USB Debugging then on again, it will then ask to allow that computer to connect, and you can say to always let it do so. Then it comes up OK.

answered Nov 16 '14 at 03:33

LARRY the BRAVE

11
1

score 0 · Answer 15 · answered May 24 '12 at 07:03

0

create a udev rule for your development device.

answered May 24 '12 at 07:03

CMA

2,758
5
28
40

score 0 · Answer 16 · edited May 23 '17 at 10:29

0

I had this same issue, and I found this post, which fixed it for me.

Just download http://dl.google.com/android/repository/platform-tools_r16.0.1-windows.zip unzip it and replace your "C:\Program Files (x86)\Android\android-sdk\platform-tools" directory with that

Credit goes to hack_on

Here is his post that helped me: https://stackoverflow.com/a/15000565/342497

Thanks! :-)

edited May 23 '17 at 10:29

Community

1
1

answered Mar 18 '13 at 19:46

Jared

2,999
1
28
39

score 0 · Answer 17 · answered Mar 19 '13 at 17:46

If you cannot select the ok button when choosing a device it probably means you cant do things like adb logcat either in my experience.

I usually kill adb from Task Manager and it starts working. I noticed adb kill-server only sometimes works, and that there are often multiple processes called adb running... not sure if this is a bug or by design.

score 0 · Answer 18 · answered Apr 10 '13 at 18:54

0

step 1 : rigth click on the project => properties => android => select api level that your device suport.

step 2 : restart your phone

work for me ...

answered Apr 10 '13 at 18:54

idan

1,508
5
29
60

score 0 · Answer 19 · answered Jun 06 '13 at 06:02

Had the exact same problem. Working fine for over two years then all of a sudden this error pops up. The fix for me was running the SDK Manager.exe located here on my machine: C:\Program Files (x86)\Android\android-sdk Turns out I did not have the ability to run on the device with Android operating system 4.2.2, only 4.0.2. After the SDK updated recognition worked perfectly. Turns out my phones operating system was updated and I forgot to update the SDK.

score 0 · Answer 20 · answered Oct 28 '13 at 09:55

0

Had the same problem. Turns out I had changed my USB connection mode from MTP to MSC. Changing it back to MTP solved the problem. Thanx.

answered Oct 28 '13 at 09:55

M4rius

1
1

score 0 · Answer 21 · answered Jan 22 '14 at 18:13

I used to debug w/o problems in my HTC One X, I broke the screen and until they repair it I managed to get an HTC One (M7 I think it's called internally).

I was unable to debug with this same problem, what actually happened is that besides having to follow a weird procedure to make Debug options appear (press 7 times in the firmware version in "About" menu) the phone was showing a message asking me to verify that the computer trying to debug on it was authorized.

I had not seen this behavior before in any the the phones I have used, not sure if this is a new functionality or simply it was not enforced on the other ones.

score 0 · Answer 22 · answered Mar 27 '14 at 14:27

0

It is because that you didn't allow your phone to be debug by this computer.

Lock your screen, unplug and plug it then unlock screen click allow in the dialog.

answered Mar 27 '14 at 14:27

David Liu

16,374
12
37
38

score 0 · Answer 23 · answered Jul 10 '14 at 10:47

0

KITKAT 4.4.2+ users, TRY to switch from ART to DALVIK or from DALVIK to ART. :) solved mine.

answered Jul 10 '14 at 10:47

user3821158

71
1
5

score 0 · Answer 24 · answered Jul 19 '14 at 19:06

0

I tried different drivers, turning USB debugging on/off, rebuilding program with lower level API, killing ABD and restarting. Then I saw post on here regarding cable swap. Changed USB cable to Samsung USB cable and worked immediately.

answered Jul 19 '14 at 19:06

user3856568

1
1

score 0 · Answer 25 · answered Jul 29 '14 at 17:26

0

you need to authorize the device to that computer. I was connecting the phone to my centos VM and kept getting this. I had to kill the adb server and then run it as root user. then you will get the prompt on the phone to authorize machine.

answered Jul 29 '14 at 17:26

Tanzeel

455
6
16

score 0 · Answer 26 · answered Sep 25 '14 at 10:35

0

For me it worked by disabling and enabling the USB-Debugging option while ADB is running. Thanks for all the suggestions.

answered Sep 25 '14 at 10:35

kalyan

11
3

score 0 · Answer 27 · answered Nov 11 '14 at 19:25

0

I had the same problem, restarting the PC worked for me.

answered Nov 11 '14 at 19:25

Nazia

1

score 0 · Answer 28 · answered Nov 29 '14 at 21:14

(Debugging was already on, USB cable plugged in, fresh restart)

SOLUTION: Switched USB connection from Media Device (MTP) to Camera (PTP). When I did this it the PC installed device drivers, then phone gave me my computer's fingerprint and had a dialog concerning allow device to use USB Debugging. Accept. Device shows up in eclipse. All good.

(On Samsung Note II API 19) Note: it's good habit to always try toggling the USB mode. I don't think it's the act of designating Camera (PTP), but the dialogs that are generated when doing so. Also, I had my phone replaced: I remember seeing this dialog before but not on this phone. Maybe there's an option somewhere to enable it per device?

score 0 · Answer 29 · answered Dec 01 '14 at 19:06

0

I had the same problem. Turns out my device was prompting a dialog asking me whether I should allow connecting to my laptop or not. After clicking yes this problem went away.

answered Dec 01 '14 at 19:06

flameshimmer

321
3
3

Jaka · Answer 30 · 2015-10-14T18:48:05.650

The problem for me turned out to be insufficient rights of adb server.

I run Android Studio through remote desktop (used laptop to connect to a local, more powerful computer). Apparently i didn't have all the privileges when running through remote desktop.

After stopping adb server and restarting it with root privileges solved the problem.

sudo ./adb kill-server
sudo ./adb root

Edit:

Turns out i had to do this just the first time. Since the first time i don't have to do this anymore.

Eclipse - Target "unknown" in Android device chooser

30 Answers30

Linked

Related