Mark- I think it would make sense to start with the ApiDemos tests, so that you can (at a minimum) start with a known good quantity.
The structure of these is that there are two packages - the Api Demos package itself (com.example.android.apis), and the package of tests that goes with it (com.example.android.apis.tests). So the first thing to do is to make sure that everything built properly and installed properly. It's easy to confirm that the ApiDemos package is on your emulator - you should be able to launch it from the home screen. To look under the covers, use this command: $ adb shell pm list packages | grep example And you should see (among other things) both of the packages I mentioned. If you don't see both packages, then fix that first (no point in launching the instrumentation yet). Finally, when you have instrumentation launch failure, did you take a look at what's happening in adb logcat? As you've discovered, the output from "adb shell am instrument" is pretty thin; Sometimes you can learn more about the problem from the logcat output. --Andy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
