Solutions for Eclipse Phone recognition

Problem Description: The mobile device is not recognized when running the Android program (using DDMS to see the device), the phone is MX4 (Meizu 4), and the simulator is very slow, suffering from obsessive-compulsive nature to want to solve. This problem is again under Linux and Windows, the following is the solution:

Environment: ubuntu14.04+adt+ Meizu 4

Solution:

This is normal phenomenon, online including Xiaomi and other mobile phones, Macs and other operating systems will encounter this problem.

(1) terminal use LSUSB, check the connection of USB, how to know which is mobile device? By inserting and unplugging the phone, the change is just. The ID is followed by two two-byte IDs separated by colons, and we take the previous one, which is hexadecimal;

(2) Open the following file:

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

Fill in the following contents:

subsystem== "USB", sysfs{idvendor}== "2717", mode== "0666" subsystem== "Usb_device", sysfs{idvendor}== "2717", MODE== " 0666 "subsystem==" USB ", attr{idvendor}==" 2717 ", attr{idproduct}==" 9039 ", symlink+=" android_adb "

The data are respectively filled in the previously seen Vid and PID;
(3) Restart the Udev service:

(4) Generally here, you can identify the mobile phone, if still not, put this number (such as 0x1782, in lowercase) to the file ~/.android/adb_usb.ini.

--------------------------------------------------------------------------------------------------------------- -----------------------------------------------

In front of the Linux solution below, the Windows scenario is similar.

Online search for a lot of information, there are said to restart the system and the like, there is said to open the Pea pod (this method can really, do not know why?) When you open the Pea pod and connect the phone, eclipse can identify the phone. The reason for the Internet is to install the driver, but the driver is not already installed? After a general search or found a solution similar to Linux:

(1) Also find Vid, in Device Manager, find the ADB driver, find the corresponding vid, as shown in, Vid is 0x2a45:

(2) in the current user directory, locate the. Android directory (hidden files, open hidden files you understand), and then find the Adb_usb.ini file, like Linux, fill in the Vid is OK.

This makes it easy to find mobile devices, no longer listen to others say restart the system.

Ps:

The ADB server uses 5037 ports and uses commands to view the PID of the process:

Netstat-ano | Findstr "5037"

Go to Task Manager to see the corresponding process name (view-Select column-pid), or use the command to view the corresponding process name:

tasklist | Findstr "2404"

You can see the results:

If it is not the ADB, it may also affect the display of mobile devices (anyway, the pea pod connected to the phone when prompted by this service, let the service shut down).

Reference article:

Click to open link

Click to open link

Solutions for Eclipse Phone recognition