I will see if I can reproduce it consistently. I didn't notice it a few
weeks back when I first started on the app. I've not noticed it on some
"test" apps I've done while learning Android. I have only noticed it with
regards to the MapActivit project I am working on. I will try this.. I will
reboot my machine, load eclipse fresh, run my app via the debug command
without loading the UI AVD and starting the emulator that way. The debug
will start the emulator for me. I'll check the first run, make a change,
press debug again, see what happens. I assume I don't have to actually stop
the emulator each time.. that would kill development time for quick changes.
Should I stop the DDBS threads in the DDBS perspective before relaunching..
or is it ok to just make a change and relaunch every time? I was doing that
before with basic text widget button demo apps and that seemed to work fine.
I don't know if this is related..but I can't get any LogCat info out. I've
got Log.v("MAPS","it worked") logs at different locations, and when I filter
on MAPS or create a new filter, or look in the long initial start LogCat
list, I can't see anything. However, this issue of the emulator not working
ALSO did this before I ever put Log.v calls in there, so I don't think the
logging itself is the issue.
Do you guys have any idea what is causing this yet and working on a fix?
Thanks.
On Thu, Jan 28, 2010 at 3: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%[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]<android-developers%[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
