Android development online debugging Motorola xoom mz606 tablet (Windows, Linux)

How can I solve the problem that ndk SDK programming cannot connect to a tablet (mz60x )???
Mz606/604/601 is also applicable
Prerequisites

First, eclipse-Helios has been used in the widows environment, and the simulator runs successfully in the 3.0 environment. However, the running on the device prompts that the connection is unavailable. Similarly, in Linux (UBUNTU), the device cannot be connected. It is worth mentioning that the device can be connected directly on Mac without any configuration. It can be seen that in actual work, iMac is more efficient than Linux and win.

1. Windows 7 Environment
Connect mz606 and wondows7 with data lines; prompt to open the tablet in memory mode (USB flash disk;

Click RUN configurations... menu ---- target option ----- Manual (device) and then click Run
This is the list
Select an Android device for choose a runnig Android device;
Problem:
The list is empty. It seems that the device is not connected;

Start solution:
1. Run the "ADB logcat" command on the command line (plattools In the android SDK directory). The system prompts you to wait for the device to stop. It seems that the device is still not found;
2. Set"Set "---" application "----" development"
Allows USB debugging to stay awake. Allows simulated locations.
Then run ADB logcat to find that the problem persists;

3. check the Windows Device Manager and find that mz606 is an unknown device. There is a question mark, prompting that the device cannot run normally. That is to say, the driver of mz606 is not found in win7. Strange, does this tablet need a driver ?? Or USB driver, but the storage content in the tablet can be opened .. When I went to the Motorola website to query, I couldn't find any driver to download to the word; suddenly I saw a media management software.Motorola Media Link, L similar to synchronizing PCs and tablets to software, just like Microsoft's Windows
Mobile sync or Apple's iTunes or Nokia's "Noida mobile phone management software" is average;Download and install the Motorola Media Link, and test it after installation. No device is found in the software .. Let the software be updated automatically. After the update, the software is ready;

4.Return to eclipse, and the choose a runnig Android device finally shows a device in the list. It is now connected to mz606, click run, and the application is successfully started on the tablet;

Latest discoveries Download the USB driver:

The above OEM drivers are often used in Chinese Android shanzhai...

Pay attention to the number corresponding to idvendor idproduct.
...
Bus 001 device 002: Id 22b8: 70a9 Motorola PCs
Device descriptor:
Blength 18
Bdescriptortype 1
Bcdusb 2.00
Bdeviceclass 0 (defined at Interface Level)
Bdevicesubclass 0
Bdeviceprotocol 0
Bmaxpacketsize0 64
Idvendor 0x22b8 Motorola PCs
Idproduct 0x70a9
Bcddevice 99.99
Imanufacturer 1 Motorola
Iproduct 2 mz606
Iserial 3 037c70c441e105d7
 Bnumconfigurations 1
Configuration descriptor:
Blength 9
Bdescriptortype 2
Wtotallength 62
Bnuminterfaces 2
...

Create a file named 10-motorola-droid.rules in the/etc/udev/rules. d/directory.
(The file name seems to have been obtained at will and cannot be determined)

Command: sudo Vim/etc/udev/rules. d/10-motorola-droid.rules
The content of this file is
========================================================== ========================
Subsystem = "USB", attrs {idvendor} = "22b8", attrs {idproduct} = "70a9", mode = "0666", owner = "Administrator"
========================================================== ========================

Note that:
 Attrs {idvendor} = "22b8" here, enter the idvendor value obtained from the lsusb-V command. The device may be different
Attrs {idproduct} = "70a9", here fill in the idproduct number obtained from the lususb-V command, different funeral devices may be different
Mode = "0666". Permission 0666 indicates that all users are allowed to read and write data.
Owner = "Administrator"Linux User name. This option is optional.

Then it is best to restart Linux; Ensure that mz606 is set to USB development mode;

Post: http://lockriver.blog.163.com/blog/static/487232242011425103633256/