... my quick fix is to create a new AVD, delete the broken AVD, and get on with my life.
On Feb 3, 4:53 pm, Richard Kasperowski <[email protected]> wrote: > For me, this has been happening consistently on my Mac. After running > it mostly successfully for weeks, today I can't get the emulator to > start successfully. > > I haven't really looked through the qemud source code, but > athttp://gitorious.org/0xdroid/external_qemu/blobs/3a0c4d9eed9ba76e2744... > I notice: > > 1228 /* we don't expect clients of char. services to exit. Just > 1229 * print an error to signal an unexpected situation. We should > 1230 * be able to recover from these though, so don't panic. > 1231 */ > 1232 static void > 1233 _qemud_char_client_close( void* opaque ) > 1234 { > 1235 derror("unexpected qemud char. channel close"); > 1236 } > > Any ideas? > > On Jan 28, 6:46 pm, David Turner <[email protected]> wrote: > > > > > This is an emulator bug that is unrelated to your application. I could never > > reproduce it but several people have reported it. > > Can you confirm that you have a 100% way to reproduce it ? > > > On Thu, Jan 28, 2010 at 3:24 PM, Kevin Duffey <[email protected]> wrote: > > > Hi all, > > > > I've seen other posts on emulators, but none seem to match my issue. > > > Basically on a clean boot of my Ubuntu 9.04 64-bit system, I fire up > > > Eclipse, load my project, and run it in debug (or not) mode. Either way, > > > the > > > emulator fires up, takes about 30 to 45 seconds to initialize, and my app > > > shows up. When I make some changes and rebuild my app, sometimes it > > > reloads > > > properly. However, if I shut down the emulator at all, then relaunch it > > > fresh, I am constantly getting the following error in the console output: > > > > emulator: ERROR: unexpected qemud char. channel close > > > > Now, I run in DDMS perspective as well, and I see a bunch of threads start > > > up. I also see my app being deployed. Then slowly, all the threads > > > including > > > the normal ones like Alarm clock, etc disappear. Then that error line > > > shows > > > up. At this point, my app somehow shows up in the emulator (it's a google > > > maps app), and I have NOT had to press the menu key to get past the normal > > > lock screen. Not sure why when this thing crashes like this, I've not had > > > to > > > use the lock screen menu press to see my app like I usually do. > > > > I've not found any useful info on the specific error either. > > > > Thank you for any help. > > > > -- > > > 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]<android-developers%2Bunsubs > > > [email protected]> > > > For more options, visit this group at > > >http://groups.google.com/group/android-developers?hl=en -- 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
