I could not get the Emulator to run newly build Apps from within Eclipse when emulator is already up and running and I had to relaunch the Emulator every time. I tried different things but to no avail. Please help.
I am running Android SDK 1.5 r3, latest DDMS and Eclipse Galileo in Windows Vista. Any ideas will be greatly appreciated. THANKS. On Thu, Aug 27, 2009 at 6:49 PM, Dianne Hackborn <hack...@android.com>wrote: > There is a simulator build for Linux that compiles everything to native > code that (sometimes) works. Trying to do this kind of thing for Android is > pretty tricky, however, because the system relies heavily on basic operating > system objects like processes, various mechanisms for communicating between > them (such as sockets and binder), etc. > > Trying to get a somewhat realistic environment running natively on a > desktop is thus tricky enough if that desktop is Linux; it has actually been > a very long time since the simulator did anything besides run all of the > applications as threads inside of a single process, which is extremely > different than the real environment. Someone could maybe cobble this > together to work on Linux again (requiring you to install a desktop build of > the binder driver etc), but it's really difficult to maintain even the > single process version. Trying to get this running on something like > Windows would be a long long rough road. > > On Thu, Aug 27, 2009 at 9:49 AM, Chris Stratton <cs07...@gmail.com> wrote: > >> >> On Aug 27, 10:24 am, Moma <osm...@gmail.com> wrote: >> >> > It takes 35 seconds to cold start the emulator and acitivity from the >> > Eclipse IDE. >> >> Likely faster than cold booting an actual phone >> >> > It takes 12 seconds to reload the acitivity when emulator is already >> > up & running. >> >> Not significantly different from a hardware device either >> >> > Do you think these numbers are normal? >> > Is there any possibility to speed up the emulation speed of QEMU? >> >> You could use an x86 build of android running in a hypervisor-type >> virtual machine (VirtualBox, etc) so that the processor itself doesn't >> have to be emulated except when doing privileged/system things... >> that's how the palm pre development kit handles things. I think it's >> good that the android emulator is closer to current devices for >> accuracy in testing, but when just iterating over software issues >> having something that's faster (even unrealistically fast compared to >> any existing phone) would be handy. >> >> Actually, I keep thinking it should be possible to have a davlik >> environment running within an ordinary desktop linux, though you might >> have to do something like run everything under the current UID which >> would grossly break the security model... >> >> > > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
