As you've figured out, both of your problems are related to having one but not both packages installed. Interestingly, it appears to be the opposite condition: It sounds as if your ApiDemos *tests* are not loaded, but your own app is also not loaded.
Yes, you've also figured out that the name "packages" has been overloaded here. In the context of the package manager, as well as the way that Instrumentation is applied, we are referring here to Android packages, which are mostly typically found in .apk files. In the case of ApiDemos, you'll note that there are two makefiles and two manifests. The android package string is set near the top of each manifest. Anyway, as I said before, at the end of the day for any given app+test pair, you should be able to build both packages, install both packages, and view them using "adb shell pm list packages". Only then, try running them.... --Andy --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] 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 -~----------~----~----~----~------~----~------~--~---
