1. Question:
In Ubuntu, when using the real machine to debug the Androi program, found that the phone is not recognized, for example, to display 2.37 column before the display is full of garbled characters. This is the figure that solves the post-cut.
2. Cause of the problem:
Under window We can install the driver to achieve the ABD connection, and in Ubuntu there is no mobile phone driver to install the concept, then we certainly need a what to achieve this drive function.
This Android website is very specific.
3. Record the following process for the resolution:
First step: Open terminal, enter: sudo gedit/etc/udev/rules.d/51-android.rules (note: rules.d under no 51-android.rules will be himself
Create
The second step: in the pop-up, for example, in the edit file in a fixed format to enter your phone model corresponding ID number. The official website format is as follows:
subsystem= "USB", attr{idvendor}== "0bb4", mode= "0666", group= "Plugdev"
We actually apply the group item in general, i.e. the following format:
subsystem== "USB", attr{idvendor}== "your phone corresponding ID", mode= "0666".
The corresponding ID of the phone can be viewed on the official website. Or just like me. Copy such as the following. All-in-one add, after save.
For example, with:
subsystem=="USB", attr{idvendor}=="18d1", mode="0666"
subsystem=="USB", attr{idvendor}=="0502", mode="0666"
subsystem=="USB", attr{idvendor}=="0b05", mode="0666"
subsystem=="USB", attr{idvendor}=="413c", mode="0666"
subsystem=="USB", attr{idvendor}=="0489", mode="0666"
subsystem=="USB", attr{idvendor}=="04c5", mode="0666"
subsystem=="USB", attr{idvendor}=="091e", mode="0666"
subsystem=="USB", attr{idvendor}=="109b", mode="0666"
subsystem=="USB", attr{idvendor}=="0bb4", mode="0666"
subsystem=="USB", attr{idvendor}=="12d1", mode="0666"
subsystem=="USB", attr{idvendor}=="24e3", mode="0666 "
subsystem=="USB", attr{idvendor}=="2116", mode="0666"
subsystem=="USB", attr{idvendor}=="0482", mode="0666"
subsystem=="USB", attr{idvendor}=="17ef", mode="0666"
subsystem=="USB", attr{idvendor}=="1004", mode="0666"
subsystem=="USB", attr{idvendor}=="22b8", mode="0666"
subsystem=="USB", attr{idvendor}=="0409", mode="0666"
subsystem=="USB", attr{idvendor}=="2080", mode="0666"
subsystem=="USB", attr{idvendor}=="0955", mode="0666"
subsystem=="USB", attr{idvendor}=="2257", mode="0666"
subsystem=="USB", attr{idvendor}=="10a9", mode="0666"
subsystem=="USB", attr{idvendor}=="1d4d", mode="0666"
subsystem=="USB", attr{idvendor}=="0471", mode="0666"
subsystem=="USB", attr{idvendor}=="04da", mode="0666"
subsystem=="USB", attr{idvendor}=="05c6", mode="0666"
subsystem=="USB", attr{idvendor}=="1f53", mode="0666"
subsystem=="USB", attr{idvendor}=="04e8", mode="0666 "
subsystem=="USB", attr{idvendor}=="04DD", mode="0666"
subsystem=="USB", attr{idvendor}=="054c", mode="0666"
subsystem=="USB", attr{idvendor}=="0FCE", mode="0666"
subsystem=="USB", attr{idvendor}=="2340", mode="0666"
subsystem=="USB", attr{idvendor}=="0930", mode="0666"
subsystem=="USB", attr{idvendor}=="19d2", mode="0666"
Third step: Terminal input:sudo chmod a+r/etc/udev/rules.d/51-android.rules
Once again, the phone is OK.
Eclipse in Ubuntu does not recognize Android phone issues