I ran into this same error today and it appears that the problem is network related. In my ~/home folder is the .android/avd folder. For each AVD I created there is a *.ini file and a folder with the same name. I was able to modify each .ini file and relocate the AVD folders to my local drive. The *.ini files have to remain where they are, but once you update the path, you can move the folders. Once the AVD folders were local, I didn't get that error.
>From your screenshots and that it works some times but not others, that doesn't look like your problem. The other way I know how to get that error is by trying to run a second instance of the same AVD on emulator. Cheers, Jon On Nov 16, 3:06 pm, Susan <[email protected]> wrote: > No solution yet. I found that when it occurs, some user data files in > the AVD directory are locked and I can unlock them using Unlocker. > Unfortunately, though, after I did that there was no change in > behavior. (IE, I still got the same error message when I tried to run > my code.) > > For reference, here's where I found the AVD directory on Vista: > C:\Users\<your username>\.android\avd\<your AVD name>.avd > > Here's where you can download Unlocker: > http://download.cnet.com/Unlocker/3000-2248_4-10493998.html > > I also noticed that when the problem occurred the AVD directory > contained three new folders: > > sdcard.img.lock > userdata-qemu.img.lock > cache.img.lock > > When I deleted them and then tried to run my code, a new emulator > started up even though the old one was just sitting there. So deleting > those directories is clearly not the solution. It seems like the error > message and this directory must be pretty related -- "user data image" > sounds a lot like the file userdata.img located in that AVD directory. > > On Nov 14, 8:47 am, dadaowuwei <[email protected]> wrote: > > > Have you solved your problem? > > I get the same problem, is there any solution yet? > > > thanks > > > On 12 Nov, 21:36, Susan <[email protected]> wrote: > > > > I have read the many threads regarding this issue, but none of the > > > proposed solutions has actually solved the problem for me. And judging > > > by the frequency of threads about it, that hasn't solved it for a lot > > > of other people either. =) > > > > Here's the problem: When I run my code, seemingly out of nowhere I'll > > > get theerrorshown in the subject line: > > > > ERROR: theuserdataimageisusedbyanotheremulator.aborting > > > > This *seems* straightforward, but I only have oneemulatorrunning. =\ > > > As evidence, please see this screenshot: > > > > http://screencast.com/t/YzQ5MGUyNTkt > > > > This happens after I run a varying number of successful executions. > > > Sometimes I may get three in before theerror, sometimes I may get > > > twenty. In this most recent case I had probably run the code fifteen > > > times in 45 minutes. Here's the output from the console: > > > > http://screencast.com/t/YjAzYzk1NmYt > > > > When this happens, I can try to run it as many times as I like, but > > > I'll continue to get the sameerrorevery time: > > > > [2009-11-12 20:14:21 - AnalogClockWidget]Android Launch! > > > [2009-11-12 20:14:21 - AnalogClockWidget]adb is running normally. > > > [2009-11-12 20:14:21 - AnalogClockWidget]No Launcher activity > > > found! > > > [2009-11-12 20:14:21 - AnalogClockWidget]The launch will only > > > sync the application package on the device! > > > [2009-11-12 20:14:21 - AnalogClockWidget]Performing sync > > > [2009-11-12 20:14:21 - AnalogClockWidget]Automatic Target Mode: > > > launching newemulatorwith compatible AVD 'savd2' > > > [2009-11-12 20:14:21 - AnalogClockWidget]Launching a newemulator > > > with Virtual Device 'savd2' > > > [2009-11-12 20:14:21 -Emulator]emulator:ERROR: > > > theuserdataimageisusedbyanotheremulator.aborting > > > > The first million times this happened I thought there might be some > > > sort of conflict with having more than one AVD set up -- maybe somehow > > > one started automatically if the other was busy or something -- so I > > > finally deleted all my AVDs and created one single AVD that is now the > > > only one in existence. Here is a screenshot of the SDK and AVD manager > > > showing that there is only one AVD hanging around: > > > > http://screencast.com/t/YjM4NmMwNG > > > > The problem is fixable by closing theemulatorand making a new one, > > > but as we all know that takes a painful 3-6 minutes each time. > > > > Does anybody know what could be causing this? The first twenty times I > > > restarted theemulatorthis afternoon, I was able to spend the > > > intervening five minutes straightening up the kitchen. But I'm running > > > out of stuff to clean. =( > > > > Thanks! -- 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
