[TRACE] Launch output: Starting: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] cmp=com.nolanwright.kitchensink/.KitchensinkActivity }
[TRACE] Error type 3
[TRACE] Error: Activity class {com.nolanwright.kitchensink/com.nolanwright.kitchensink.KitchensinkActivity} does not exist.
[TRACE]
[INFO] Deployed KitchenSink ... Application should be running.
[TRACE] D/dalvikvm( 60): threadid=17: bogus mon 1+0>0; adjusting`

13 Answers

• Accepted Answer

  This looks to be the culprit:

  E/PackageManager( 53): Package com.nolanwright.kitchensink requires unavailable shared library com.google.android.maps; failing!
  

  You need to make sure you're using "APIs 1.6" when you launch KitchenSink. "APIs" is short for "Google APIs" which is needed for any app that has a dependency on Maps

• Would you mind dropping the entire log into a pastie so I can see if there are compile errors before it.

• Many encounter problems with the android emulator because of the longer waiting time for the emulator to load.

  Have you waited until the emulator to be fully loaded; may take a few minutes.

• Not sure this is related, but I'm also not able to run KS with 1.2. I see these errors:

  *** Unable to locate valid config! Falling back to auto-detection...
  *** Unable to locate PAC! Falling back to direct...
  *** Unable to locate valid config! Falling back to auto-detection...
  *** Unable to locate PAC! Falling back to direct...
  

  The SDK and Screen just sit at "Loading…".

  Other apps where I've specified the sdk work just fine.

• @Dan when you see Loading Loading it's usually a tools version problem or a path problem.

  What does the very first part of your log look like at Trace level?

• Please see above ^

• Hello,

  Please refer to my pastie.

  Again, any help is much appreciated.

  Regards,
  Ben

• Ben, thanks for the pastie. Here is the clue

  [DEBUG] /Users/bbabics/Documents/android-sdk-mac_86/tools/adb -e devices
  [TRACE] wait_for_device returned: List of devices attached
  [TRACE] emulator-5560  offline
  

  Basically it can detect that the emulator is there, but it is unable to communicate with it.

  Try the following

  adb kill-server && adb start-server && adb devices
  

  from the command line. If it lists your emulator w/ it being offline then try and launch again. You don't need to stop Developer or the Emulator when you try this. If it doesn't work then.

  1) Kill the emualator
  2) Try to restart the adb server using the command above
  3) Launch the app again.

• Don- Do I enter this in /Documents/[my-android-sdk-dir]/tools ? Apology in advance for the silly question. :)

• Don- Do I enter this in /Documents/[my-android-sdk-dir]/tools ? Apology in advance for the silly question. :)

• Not a problem. If the adk is in your path, than anywhere. If not then you'll want to make a small change and to be able to execute it from there.

  ./adb kill-server && ./adb start-server && ./adb devices
  

• Don,

  I've tried using the command and re-launching the app to no avail. :(

  BTW- this time I used 1.6.

  I've included pasties of both the Command Line and the Log.

  Thanks for your help.

• Oh Snap, it worked! I didn't realize it had to be APIs 1.6 and not just 1.6. Thanks for your help, guys. :)