NITdroid is working on N8x0 hardware quite well, and I'd like to collect some info on where we can get apps and how well they run. First, here's a quick summary of how to load apps onto NITdroid. To get adb working, follow the instructions at http://code.google.com/intl/fr/andro...devicehardware. If you're using Windows, you'll need gowen's modified android_usb.inf file from http://www.internettablettalk.com/fo...&postcount=243 as well. FYI, the adb program will be in android-sdk-windows-1.0_r2/tools after you've downloaded and unpacked the SDK.

To check that adb can talk to your tablet, run

If adb reports `offline' instead of `device', try unplugging the USB cable. I need to do this after rebooting the tablet to make adb happy again.

You can use adb for lots of things other than loading apps. For example, to start a root shell on the tablet use the command:

This provides a handy way for rebooting off the tablet too:

To load applications onto the tablet, you first need to download the .apk files to your host. For example, http://www.androidfreeware.org/ has a few applications, and Meebo.apk seems to run just fine. To install Meebo, I used the command:

and Meebo showed up in the tray automatically.

So, where can we find more apps? I'd really like to find a native multiprotocol IM app, as the one provided with Android doesn't seem to work on my tablet (I can't find a way to add accounts) and Meebo is actually using an HTTP proxy service rather than talking to the IM servers directly. Is there a way to get apps from the marketplace without using the app shipped with the G1?

Thanks to gowen, maxkilla, and jcl for info I've summarized here.

There are some apps too, like this great IRC software.

i read there is IM Plus for android...

http://www.androidapps.org/
Reviews: http://www.androidapps.com/

I'm still having trouble with the adb.
I did just what the instructions said, and it still doesn't work.

Trying to run sudo ./adb devices but it just doesn't show my NIT...

Should the NIT show something on the screen when you plug the USB?

No, there's nothing different on the tablet screen to show that adb is working. If you list the USB devices on your host will see a device named `adb driver' when the USB cable is connected. This device will show `Android' as the manufacturer, with product ID 0x0001, serial number 0123456789ABCDEF, and vendor ID 0x18d1.

What OS are you using for adb?

EDIT: I think I've found the problem, at least for MacOS. The adb source code only recognizes the following vendor and product IDs (see http://android.git.kernel.org/?p=pla...09a44e;hb=HEAD and http://android.git.kernel.org/?p=pla...1a6482;hb=HEAD)

Since the product ID for NITdroid isn't 0xd00d or 0xdeed, adb doesn't properly attach to the tablet. We either need to build our own adb binaries, or figure out how to get NITdroid to use a different product ID :-(

Note that this isn't a problem for Windows, as the .inf file specifies the product IDs. So for now, adb only works from a Windows host.

Good store here: andapps.com

"AndApps is website for those who don't have access to the Android Marketplace. Here will be uploaded as much as possible free and/or open source applications for the Android platform."

And my favorite (for now)

http://andappstore.com/AndroidPhoneApplications/apps/



For those in trouble with adb, do not plug in the device before Android starts. Windows gets confused if it is a Android device or a Nokia. Also, make sure in DevTools, adb is enabled.

Also, you install apps like this:
This is the "proper" way, but makes no difference IMO.

Yep, it looks like solca chose that product ID. Looking at http://guug.org/nit/nitdroid/nitdroid_kernel.patch.bz2, in his version of linux-nitdroid/drivers/usb/gadget/android_adb.c he specifies the following:

If we change the product ID to 0xDEED, then the precompiled adb binaries may work with NITdroid. Of course, solca may have had a good reason for choosing a different product ID...

Yeah, that part really messed me up. Lucky, I had experience changing the Vendor ID's to support "unsupported" hardware. Was not that bad, and gowen's modified android_usb.inf file (look at first post) makes it even easier.

No, I didn't, was Google.