I had the same problem many times. And I guess it depends on the CPU load of the emulator when it starts/initializes.
What helped was the freeware program "process tamer", which automatically lowers the process priority of a program/application when it consumes 100% CPU time. I installed this freeware and never had the "emulator disconnected" troubles anymore... On 25 Feb., 12:46, "Jose María González" <[EMAIL PROTECTED]> wrote: > I also have found that it can be dependent on the CPU load. > If I maintain theemulatorin foreground it starts ok, but if I send > it to background and I use another aplication (firefox, for example) > then the error appears. > > On 25 Feb, 09:00, Yoshi <[EMAIL PROTECTED]> wrote: > > > > > Hi, thank you for comments. I was so confused by this problem then > > wondered many sites > > about this error. Fortunately, I got a solution on another > > discussion. > > >http://groups.google.com/group/android-developers/browse_thread/threa... > > > Such thetcperror may be so related to errors of layout files on the > > project. > > > On Feb 21, 4:17 am, "Jose María González" <[EMAIL PROTECTED]> > > wrote: > > > > I installed the new m5 version and all worked fine, but one day that > > > error appeared. > > > Now I have to relaunch two high-memory consumming emulators. Because > > > with the firstemulatorI obtain that error. > > > I think my laptop is going to break down with such a high load :S > > > > On 18 Feb, 23:26, kdavis95139 <[EMAIL PROTECTED]> wrote: > > > > > Have the same problem. What works for me (If you can call it that) is > > > > that I kick off firstemulatorand get the disconnect error. Then > > > > without killing thatemulator, I kick off a secondemulator. Every > > > > time I do this the secondemulatorcomes up OK. Then I simply kill the > > > > firstemulator. If you kill the firstemulatorbefore starting the > > > > second you get the same error. No clue why this is happening but my > > > > upgrade to latest SDK was not as straight forward as I had hoped > > > > either. Seems there were some pretty important details left out of the > > > > instructions. But except for this little nag, I seem to be up and > > > > running on the latest SDK. > > > > > On Feb 17, 11:37 am, rezar <[EMAIL PROTECTED]> wrote: > > > > > > I had the same sometimes you need to restart adb, when it doesn't work > > > > > -wipe-data and sometimes I restart my PC > > > > > > On Feb 16, 8:35 am, Yoshi <[EMAIL PROTECTED]> wrote: > > > > > > > A trouble happened after new SDK was released. I rewrite the > > > > > > manifest > > > > > > file not to > > > > > > appear the error statement about a project which works perfect on > > > > > > last > > > > > > version of > > > > > > SDK. After all, I could not make the project work on the newemulator > > > > > > because of > > > > > > the error. > > > > > > >emulator-tcp-5555disconnected! Cancelling > > > > > > > What is lacking on my project?- Hide quoted text - > > > > > > - Show quoted text -- Zitierten Text ausblenden - > > - Zitierten Text anzeigen - --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
