resolved issue by:
- going to project and selecting clean
- going to window>avd manager>delete and create a new avd
- relaunch application, emulator will take a few minutes to load.
clean the project and run on emulator with same api level.
if it still not resolves change once the api level of project and run on emulator with same api level.
in my case it runs ..........
it is easier. you just have to change the name of your virtual android device and then delete the one you do not charge and ready :)
got this problem. and found a way. when i do not change anything in configuration, but just starting emulator once again. you need to click "power" button in emulator and then close it. one annoying thing that happens after start from snapshot is - i need to click power button to be able to unlock emulator.
in my case, this error was shown when i plugged a device whose usb debug mode hadn't been enabled. so no device could be found and running the application caused this error message to show depending on my last run configuration.
its because of the process of exiting emulator not done properly. try finding the running emulator by
ps -ef |grep emulator
then it will list all the emulator tasks. try killing the running emulator by
note: don't kill the following
user 0 11:27 pts/11 00:00:00 grep --color=auto emulator
please note : closing the emulator after the eclipse will cause this same error too. in that case there is no hardware change ofcourse but this error will show up:
unable to load vm from snapshot. the snapshot has been saved for a different hardware configuration.
so always close eclipse, before the emulator.
in case anyone uses intellij, in order to disable snapshot do the following:
- open avd
- select your device and press start...
- uncheck launch snapshot
in my case, it seems due to the fact that i closed my avd between 2 launches of the same app, i got this error message at the second launch.
i didn't need to "clean" the project, just launched the avd manually using the avd manager, waited for it to boot and launched the app again once booting was completed. worked for me.
you may have been trying to start the emulator from avd before this, and from the command line now. most avds use arm instruction sets, so you may have to try something like:
emulator64-arm -avd <your avd label> -no-snapshot-load -no-snapshot-save
finally i got the solution follow these
1)open avd manager
2)select the avd which is givin this err-"error: unable to load vm from snapshot. the snapshot has been saved for a different hardware configuration."
3)click on start
4)now uncheck these two options-"launch from snapshot" and "save snapshot"
5)now check "wipe user data"
6)start the avd now
7)as soon as the"android" is displayed, close the avd
8)now open avd manager again
9)uncheck "wipe user data"
10)check on these two options-"launch from snapshot" and "save snapshot"
11)now start the avd, it would be easily loaded from snapshots without errors
maybe try to disable the hardware snapshot in the android virtual device manager? it should be installed wherever you installed the android sdk.
go to window-> android virtual device manager, choose your virtual device and disable the launch from snapshot and keep save to snapshot option and click launch.
i had the same issue as timmmm, nothing would resolve it.
through the command line emulator.exe -avd avdname -snapshot default-boot gives me that same error. but i also noticed that it launches from the gui just fine.
i went into the
c:\users\uname\.android\avd\the_avd\ and deleted the
snapshots.img.default-boot snapshot and the snapshots iso file.
it's easier than recreating the machine, but deletes your snapshot(s), and then you can use it again like normal.
to remove the list of stored snapshots in your system:
the problem isn't with your app, it is with the saved avd snapshot. the avd configuration has been edited since you last ran it successfully. even changing skin/display resolution will produce this error. you could either:
- change the avd configuration back to how it was originally.
- edit the avd to disable the snapshot. or
- when you next start the avd, uncheck the launch with snapshot, but keep save snapshot checked. this way the snapshot will be ignored at start-up, but overwritten when you exit. you will then be able to use snapshot for subsequent runs as before.
- Android Emulator snapshot error
- Android Emulator Out of memory error when launched from snapshot
- Error "AdbCommandRejectedException: device not found" in Eclipse using Android emulator
- "No Target Selected" error on Android tablet emulator in Eclipse
- Android Emulator error in running simple project
- Android Wear Emulator show Error SERVICE_VERSION_UPDATE_REQUIRED for Google Play services
- Error when trying to initialize Android 1.6 Emulator from Eclipse
- error installing .apk in android emulator
- Error in running application in android emulator
- When trying to run the hello android test app i get an error APPCRASH and the emulator will not open
- Android Emulator Error Eclipse Juno
- android emulator shows windows error while starting
- Wont run android apps when I launch my emulator from snapshot
- "Unfortunately, MainScreenActivity has stopped" ERROR message in Android Emulator
- Very strange android error when attempting to start emulator
- Android / Eclipse / Emulator / WAMP: Error 503 and timeouts
- Eclipse error while running android emulator
- Google Play Services error in android emulator (eclipse)
- "Debug certificate expired" error in Eclipse Android plugins
- R cannot be resolved - Android error
- frequent issues arising in android view, Error parsing XML: unbound prefix
- Android Failed to install HelloWorld.apk on device (null) Error
- When I load ADT why do I receive the error "The Android SDK requires Android Developer Toolkit version XX.X.X or above?"
- Reload Android application in emulator without restarting emulator in Eclipse?
- Android Error - Open Failed ENOENT
- Error Message : This Android SDK requires Android Developer Toolkit version 22.6.1 or above
- Android emulator error: "System UI has stopped"
- Android Error in Eclipse: "Unable to execute dex: Cannot merge new index 65799 into a non-jumbo instruction!"
- Android SDK Error when loading the SDK:
- Sending and receiving text using android emulator
More Query from same tag
- GLFW 3.0.4 - ‘GLFW_FSAA_SAMPLES’ was not declared in this scope
- Eclipse debug mode not opening
- Eclipse Web Application Project. Introduced CSS properties doesn't work
- Android Maps v2 works only the first time is launched
- Difference between eclipse pulsar, mtj, me
- Eclipse plugin rt.jar semms not to be in classpath
- Using multiple External JARs in Spring Boot Eclipse
- script async defer undefined attribute name
- How to install eclipse PDT 3.1 in Eclipse Juno?
- how to create a not runnable/not executable jar with other external jar dependencies in Eclipse
- java graphic library(processing, Piccolo, and JOGL)
- Spring 4.0.6 release - @RequestMapping issue
- Eclipse dont mark correctly occurrences
- svn update <directory> -r HEAD --force Still leaves dirty copies of local files
- How do I add an entry into the File Association preferences programmatically?
- Does TestNG affect the already existing project which have not used TestNG
- How to use a eclipse to create a project to write the JSP?
- Textview data is false android
- JUnit Test (w JNA) Silently Failing?
- How AND between two operators works?
- Android JSON Object is returning null
- exception in InitialContext jboss
- Eclipse doesn't compile classes in source/main/resources directory in maven project
- Eclipse remove error text from code lines
- Eclipse proposals(ctrl+Space) needs to be in curly braces
- Eclipse StatusManager do not show detail
- FancyOverFlow on swipe listener
- Transparent SWT Canvas