StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>Poking around I found a <a href="http://thisisignite.com/android-development-on-toshiba-at200-with-omap4430/" rel="nofollow">blog entry</a> that seems to have a fix. Here's a copy and paste of <a href="http://thisisignite.com/author/michal/" rel="nofollow">Michal's</a> tutorial:</p> <p>...[F]or half of the day the ADB didn’t want to hear about the new tablet that it supposed to cooperate with.</p> <p>Here is how you can force it to listen:</p> <ol> <li>Downloading Android SDK is necessary. Also, we will need additional android USB drivers that can be installed through the SDK manager.</li> <li><p>After installing the Android SDK, go to <code>../sdk/extras/google/usb_driver</code>. We will modify the android_winusb.ini file a little bit. Edit the file and find <code>[Google.NTx86]</code> or <code>[Google.NTamd64]</code> lines. Paste provided code right below those two lines. Don’t modify anything else.</p> <pre><code>; OMAP-3/4 %SingleAdbInterface% = USB_Install, USB\VID_0930&PID_D101 %CompositeAdbInterface% = USB_Install, USB\VID_0930&PID_D102&MI_01 %CompositeAdbInterface% = USB_Install, USB\VID_0930&PID_D106&MI_02 %CompositeAdbInterface% = USB_Install, USB\VID_0930&PID_D107&MI_03 %SingleAdbInterface% = USB_Install, USB\VID_0930&PID_FFFFE %CompositeAdbInterface% = USB_Install, USB\VID_0930&PID_FFFE&MI_01 %SingleAdbInterface% = USB_Install, USB\VID_0930&PID_D022 %CompositeAdbInterface% = USB_Install, USB\VID_0930&PID_D022&MI_01 %CompositeAdbInterface% = USB_Install, USB\VID_0930&PID_D10A&MI_01 ; OMAP-3 / 4 - ICS %CompositeAdbInterface% = USB_Install, USB\VID_0930&PID_D109&MI_01 </code></pre></li> <li><p>The next step requires modifications in android_usb file that can be found in <code>“%USERPROFILE%\.android\</code>. By <code>%USERPROFILE%</code> O mean the Documents and Settings folder of your current logged user. The .android folder won’t be visible so you have to enable the visibility of hidden files.</p></li> <li>Edit android_usb to change vendor ID to match your device’s vendor. The ID I used is 0930 which matches Tochiba vendor ID listed on Android’s official web site. If you’re trying to enable your OMAP4 Android device and it is not Tochiba, then just modify 0930 in both edited files to match your gadget. You can get the vendor ID’s from <a href="http://developer.android.com/tools/device.html" rel="nofollow">here</a>.</li> <li>When you connect the tablet via USB, Windows will try to look for appropriate drivers and install them. And no suprise, it will fail. Go to ‘Device Manager’ in Windows and you should see yellow ‘?’ sign for an unknown device. Click on it and install or update the driver. Choose driver manualy from your hard drive and navigate to the android_winusb.ini file that you modified before. Ignore warnings and install the driver.</li> <li>Navigate with the <code>cmd</code> to <code>../sdk/platform-tools/</code> and use <code>adb kill-server</code> command. It will kill the ADB server.</li> <li>You can connect your tablet via the USB cable. To check if ADB sees the tablet, type ‘adb devices’. As an output you should get the ID of your device and from now on Eclipse should be able to detect it.</li> </ol>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload