DJFuego - Adding a stack trace to the thread would help James immensely!
Great! Btw, do you debug through 'Build & Run' ? If so, you can run ddms.exe and see the live traces, it's much easier and it's located inside your \program files\android sdk\ folder. This way you can copy/paste the errors and put into pastebin or attach to a thread
Seems that after the last tools update for android (yesterday), they change ddms.exe to monitor.exe, this is causing strange behavior inside MMF, sometimes it locks MMF as if it is still compiling and building the application.
... new things are coming ...
Yeah MMF has been doing this for a while now so it's not just me then.. I thought it was a build issue as files where locking and I could only free them if I closed MMF.
DJFuego - If you do a manual copy to phone won't work.
As far as I know it needs to be a Build & Run (adb) for the stack tracing through ddms, in which Fernando says it's now changed to monitor.exe, I was unaware of this change until now.
........................oooooooohhh...>I have used adb to install to the device. it took a few goes but for some reason the first two attempts failed. I did a device scan when it failed. "adb devices" and it saw my phone just fine. I then ran adb install nameofapp.apk and it installed and ran. FREAKIN COOLIO!
I should really calm down a bit now. It's more exciting than running with a VM.
Now you can just hit "Build & Run" from MMF and it should start up on your device.