Home » Ubuntu » Ubuntu, AndroidStudio can not identify devices (mo...

Ubuntu, AndroidStudio can not identify devices (mobile / tablet) problems

pro test available.

The problems we face:

has a stack of AndroidStudio and null in the device selection box of the device, meaning.

is not recognized

executes the following command in the SDK Directory:

/Android/Sdk/platform-tools$, sudo,./adb, devices,

shows the following case:

List, of, devices, attached,

2013G50RB10820707 no permissions

Well, look at how to solve this problem, I also refer to some of the older generation of online practices, in this thank you


1. unplug the data line first, press Ctrl+Alt+T, and enter
at the terminal

You can see a list of.

2. connects the data line and the equipment to the computer and continues to enter
at the terminal

You can see the same list as you did just now, but there's one more item. Write down the more item.

You'll see a format like this:

Bus 002, Device, 014:, ID, 18d1:0003, Google, Inc.,

implementation steps:

1.Ctrl+Alt+T, enter

at the terminal

sudo GEDIT /etc/udev/rules.d/50-android.rules

will open a file

2. enters
in the file
"SUBSYSTEM==", "USB", "SYSFS{idVendor}==", "18d1", "ATTRS{idProduct}==", "0003", "MODE=", "0666", "


, now explain

SYSFS{idVendor} is the 4 digit ID that just follows the record,

ATTRS{idProduct} is the number just after that 0003, colon,

(check carefully, or it won't work until then).

3. save the file and exit.

4. enters sudo Chmod a+rx /etc/udev/rules.d/50-android.rules
at the terminal
The meaning of this sentence is to give the file we just created a permission (the path must be entered correctly and point to the file we just created).

5, enter sudo, /etc/init.d/udev, restart,
at the terminal
My prompt here is: Restarting udev (via systemctl): udev.service. (leave it aside, move on next),

6. enters
at the terminal
~/Android/Sdk/platform-tools$sudo./adb kill-server

then enters

~/Android/Sdk/platform-tools$, sudo,./adb, devices,

after the input prompt:

List, of, devices, attached,

* daemon, not, running., starting, it, now, on, port, 5037 *

* daemon, started, successfully *

2013G50RB10820707 device

indicates that the device has been successfully identified. To see AndroidStudio, it has the device option,.

referred to this blog, http://blog.csdn.net/hzqnju/article/details/18674239, thank you,