Android DDMS: 22.2.1.v201309180102-833290 BT_Core 3.0 Self Hosted Eclipse Version: 4.2.1.v20120814-120134 JUNO Targeting all test devices: Android 4.0 API 14 SDK Manager updated, installed latest packages Operations on MacBook Pro Lap Latest OSX No matter what test device I launch, I get- "app unfortunately stopped running" Log Cat shows Success! When I drag the lock icon to open home screen, I get two "stopped running" messages. One for the app and one for a "connection?" I delete devices and try other ones, same thing. The only thing I did that may a bit "off" is I had a similar project in the workspace and deleted it, then I Imported my new project (compiled for Android core 3.0 from the self hosted BT workbench) into the workspace and kept the same google-plays-services_lib package but I simply pointed the existing .lib to the new project in the workspace and all 300 errors went bye, bye. Eclipse Environment Issue? I dunno! Do I need to delete and re-import a new gps.lib? Or, is there something else i can do. I notices the emulator setting in in "fast". Any ideas what's going on?

Hi Glenn, So, when the app stops running, there's nothing in LogCat to indicate what's going on? Make sure you're looking in LogCat and not the Console, which shows whether the app loaded or not. Mark

Hi Mark, it is the Log Cat that reads "success" but the emulator reads otherwise.

Can you paste what you see in LogCat around the time it crashes so we can see what other messages might give us a clue? Thanks!

Emailed you