Two quick ways to launch the AVD Manager from Eclipse: 1. Click on the AVD Manager icon on the icon bar (it looks sorta like a BlackBerry); or, 2. Select Run -> Run Configuration... and click on the AVD Manager... button.
>From there it should clear how to delete and create AVD's. On Sep 16, 11:26 am, Timothy Collins <[email protected]> wrote: > Stupid question (And this really exposes how new I am to Android development > so treat me like an imbecile) : How do you delete the AVD and recreate it > from Eclipse? (I am somewhat new to Eclipse as well - I have used Aptana for > years - which is a derivative of it - but this is the first time I have > consistently used Eclipse itself for anything) > > On Wed, Sep 16, 2009 at 11:22 AM, Nmix <[email protected]> wrote: > > > This has happened to me a few times. When it does, the AVD seems to be > > permanently broken, or at least I have yet to figure out how to fix > > it. If you monitor logcat, it always freezes at the following point > > (assuming it's the same problem you're seeing): > > > ... > > 07-15 02:13:41.373: INFO/SystemServer(573): Starting System Content > > Providers. > > 07-15 02:13:41.384: INFO/ActivityThread(573): Publishing provider > > settings: com.android.providers.settings.SettingsProvider > > 07-15 02:13:41.454: INFO/ActivityThread(573): Publishing provider > > sync: android.content.SyncProvider > > 07-15 02:13:41.464: INFO/SystemServer(573): Starting Battery Service. > > 07-15 02:13:41.483: ERROR/BatteryService(573): Could not open '/sys/ > > class/power_supply/usb/online' > > 07-15 02:13:41.504: ERROR/BatteryService(573): Could not open '/sys/ > > class/power_supply/battery/batt_vol' > > 07-15 02:13:41.514: ERROR/BatteryService(573): Could not open '/sys/ > > class/power_supply/battery/batt_temp' > > 07-15 02:13:41.544: INFO/SystemServer(573): Starting Hardware Service. > > 07-15 02:13:41.554: DEBUG/qemud(546): fdhandler_accept_event: > > accepting on fd 10 > > 07-15 02:13:41.554: DEBUG/qemud(546): created client 0x10fd8 listening > > on fd 11 > > 07-15 02:13:41.564: DEBUG/qemud(546): client_fd_receive: attempting > > registration for service 'hw-control' > > 07-15 02:13:41.564: DEBUG/qemud(546): client_fd_receive: -> > > received channel id 2 > > > The only solution I've found is to delete the AVD (I used Eclipse to > > do it), restart Eclipse, create a new AVD, and then run an app that > > launches the emulator with the new AVD. This is inconvenient if you > > have lots of app data in the emulator, but it does work. > > > Hopefully this problem is gone in the 1.6 SDK. > > > On Sep 16, 10:16 am, Timothy Collins <[email protected]> wrote: > > > Hmmm - I will try that. My machine isn't exactly the most powerful piece > > of > > > equipment ever created... But all I am running is Eclipse and the > > emulator > > > (And, of course, the JDK that underlies Eclipse). And it was working > > quite > > > nicely before this... > > > > I suspect it might be a corrupted data file, but it seems odd to me that > > it > > > would cause the emulator to hang up like it does - it seems it ought to > > be > > > one of those "It works or it doesn't" rather than "It works but not > > > completely" things... > > > > On Wed, Sep 16, 2009 at 10:12 AM, JoaJP <[email protected]> > > wrote: > > > > > In my experience (all the way from m3), the emulator isn't quite as > > > > stable as one would expect... although it's improved considerably. > > > > Before you go out and buy new equipment, try to delete the emulator's > > > > data image. If the emulator doesn't find it, it creates a fresh one, > > > > so all you really lose is database and preferences data. Since 1.5 > > > > it's two files, userdata-qemu.img and cache.img > > > > They are tucked away somewhere in your home directory, see if you can > > > > find .android/avd/<avd name>.avd (that's the XP directory > > > > layout) > > > > > On Sep 16, 6:43 am, Timothy Collins <[email protected]> wrote: > > > > > I'll take that under consideration... That might be a very good > > point. > > > > > > On Wed, Sep 16, 2009 at 9:40 AM, Mark Murphy < > > [email protected] > > > > >wrote: > > > > > > > furby wrote: > > > > > > > I actually am starting it using Eclipse... Really, just running > > the > > > > > > > project. (I have to admit, I am rather new at Android > > development). > > > > > > > > I created an AVD earlier (While I was attempting to use Netbeans > > to > > > > > > > develop Android apps - it didn't work out very well)... I am just > > > > > > > wondering - how can it work one day and then the next day > > suddenly > > > > > > > stop? > > > > > > > Depending on the speed of your PC and other things that are going > > on at > > > > > > the time, the Android emulator may get "hung up" at the graphical > > > > > > Android logo. I am not aware of a workaround other than to improve > > > > > > system performance, either through hardware (e.g., more RAM) or > > > > software > > > > > > (e.g., less stuff running). > > > > > > > -- > > > > > > Mark Murphy (a Commons Guy) > > > > > >http://commonsware.com|http://twitter.com/commonsguy > > > > > > > Android Training in Germany, 18-22 January 2010: > > > >http://bignerdranch.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
