Can't start Android AVD Emulator
I'm trying to make Android Studio and the associated emulator via AVD to work under Archlinux.
I've just installed android-studio, android-sdk, and all the dependencies that Android Studio requires. When I try to start the freshly created emulator (with no particular settings), here's the error messages I receive:
17:25 * daemon not running; starting now at tcp:5037
17:25 Emulator: Couldn't statvfs() path: No such file or directory
17:25 * daemon started successfully
17:25 Emulator: Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
17:25 Emulator: Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: Warning: QObject::moveToThread: Current thread (0x593c240) is not the object's thread (0x5a7d800).
17:25 Emulator: Cannot move to target thread (0x593c240)
17:25 Emulator: ((null):0, (null))
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 main loop'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU0 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU1 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU2 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU3 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 main loop'. No response for 15000 ms
17:30 Emulator: Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
I've reinstalled everything twice. I've also checked this topic without success. I don't understand most of these messages, so I'm a bit lost. I tried to start the emulator from the command line with the command
/opt/android-sdk/emulator/emulator -avd Android_Wear_Round_API_P, it gives me the same result.
I'd be very glad to get some ideas on what the problem could be.
EDIT
Here are the elements installed, in case it's relevant:
EDIT2
The type of emulator I'm trying to run is for WearOS. As a test, I tried to create an Android Nexus one. When graphics are set to 'Software', it works. Unfortunately, I can't change this option for the WearOS device. Therefore, it keeps crashing. Sometimes, it even completely crashes my system. My screen freezed, I have to manually reset my computer.
android 
android-studio android-emulator avd archlinux asked Nov 14 '18 at 16:44
cyphicscyphics
9513
add a comment |
I'm trying to make Android Studio and the associated emulator via AVD to work under Archlinux.
I've just installed android-studio, android-sdk, and all the dependencies that Android Studio requires. When I try to start the freshly created emulator (with no particular settings), here's the error messages I receive:
17:25 * daemon not running; starting now at tcp:5037
17:25 Emulator: Couldn't statvfs() path: No such file or directory
17:25 * daemon started successfully
17:25 Emulator: Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
17:25 Emulator: Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: Warning: QObject::moveToThread: Current thread (0x593c240) is not the object's thread (0x5a7d800).
17:25 Emulator: Cannot move to target thread (0x593c240)
17:25 Emulator: ((null):0, (null))
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 main loop'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU0 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU1 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU2 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU3 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 main loop'. No response for 15000 ms
17:30 Emulator: Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
I've reinstalled everything twice. I've also checked this topic without success. I don't understand most of these messages, so I'm a bit lost. I tried to start the emulator from the command line with the command
/opt/android-sdk/emulator/emulator -avd Android_Wear_Round_API_P, it gives me the same result.
I'd be very glad to get some ideas on what the problem could be.
EDIT
Here are the elements installed, in case it's relevant:
EDIT2
The type of emulator I'm trying to run is for WearOS. As a test, I tried to create an Android Nexus one. When graphics are set to 'Software', it works. Unfortunately, I can't change this option for the WearOS device. Therefore, it keeps crashing. Sometimes, it even completely crashes my system. My screen freezed, I have to manually reset my computer.
android android-studio android-emulator avd archlinux asked Nov 14 '18 at 16:44
cyphicscyphics
9513
Open the update manager and check if you have installed "Android Emulator" under the voice "SDK Tools"
– Lorenzo Vincenzi
Nov 14 '18 at 16:55
I've also faced this issue when Android Studio updated recently. Digging dipper into how the emulator is being run, I've figured out that the emulator itself lives in $HOME/Android/Sdk/emulator while the images are stored in $HOME/.android/avd. May bet statvfs() path: No such file or directoryhas something to do with it? I don't remember what was the directory layout of older emulator versions.
– Alexander Solovets
Dec 3 '18 at 15:00
Playing with strace I figured out that the message is about missing ram.img under .android/avd/<NAME>.avd/snapshots/default_foot.
– Alexander Solovets
Dec 3 '18 at 15:23
Try to run the emulator with software graphics. This helped me.
– Alexander Solovets
Dec 3 '18 at 23:38
I ran into a similar problem as yours but I think you're describing a much more serious issue. I'm running Manjaro linux and I just accepted the provided emulator upgrade to version 28.0.20. After upgrade emulator kept crashing with segmentation fault. Switching to software GL allowed me to get the emulator up. Once in there's some configuration in settings that allows you to flip back to hardware open GL I may have fiddled a few other things like cold boot and a reboot of computer but it's all working again magically. This problem feels like a settings migration issue w/ emulator code upgrade
– user3259330
Dec 13 '18 at 4:57
add a comment |
I'm trying to make Android Studio and the associated emulator via AVD to work under Archlinux.
I've just installed android-studio, android-sdk, and all the dependencies that Android Studio requires. When I try to start the freshly created emulator (with no particular settings), here's the error messages I receive:
17:25 * daemon not running; starting now at tcp:5037
17:25 Emulator: Couldn't statvfs() path: No such file or directory
17:25 * daemon started successfully
17:25 Emulator: Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
17:25 Emulator: Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: Warning: QObject::moveToThread: Current thread (0x593c240) is not the object's thread (0x5a7d800).
17:25 Emulator: Cannot move to target thread (0x593c240)
17:25 Emulator: ((null):0, (null))
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 main loop'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU0 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU1 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU2 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU3 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 main loop'. No response for 15000 ms
17:30 Emulator: Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
I've reinstalled everything twice. I've also checked this topic without success. I don't understand most of these messages, so I'm a bit lost. I tried to start the emulator from the command line with the command
/opt/android-sdk/emulator/emulator -avd Android_Wear_Round_API_P, it gives me the same result.
I'd be very glad to get some ideas on what the problem could be.
EDIT
Here are the elements installed, in case it's relevant:
EDIT2
The type of emulator I'm trying to run is for WearOS. As a test, I tried to create an Android Nexus one. When graphics are set to 'Software', it works. Unfortunately, I can't change this option for the WearOS device. Therefore, it keeps crashing. Sometimes, it even completely crashes my system. My screen freezed, I have to manually reset my computer.
android android-studio android-emulator avd archlinux asked Nov 14 '18 at 16:44
cyphicscyphics
9513
I'm trying to make Android Studio and the associated emulator via AVD to work under Archlinux.
I've just installed android-studio, android-sdk, and all the dependencies that Android Studio requires. When I try to start the freshly created emulator (with no particular settings), here's the error messages I receive:
17:25 * daemon not running; starting now at tcp:5037
17:25 Emulator: Couldn't statvfs() path: No such file or directory
17:25 * daemon started successfully
17:25 Emulator: Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
17:25 Emulator: Warning: libpng warning: iCCP: known incorrect sRGB profile ((null):0, (null))
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.abm [bit 5]
17:25 Emulator: Warning: QObject::moveToThread: Current thread (0x593c240) is not the object's thread (0x5a7d800).
17:25 Emulator: Cannot move to target thread (0x593c240)
17:25 Emulator: ((null):0, (null))
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 main loop'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU0 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU1 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU2 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 CPU3 thread'. No response for 15000 ms
17:30 Emulator: emulator: ERROR: detected a hanging thread 'QEMU2 main loop'. No response for 15000 ms
17:30 Emulator: Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
I've reinstalled everything twice. I've also checked this topic without success. I don't understand most of these messages, so I'm a bit lost. I tried to start the emulator from the command line with the command
/opt/android-sdk/emulator/emulator -avd Android_Wear_Round_API_P, it gives me the same result.
I'd be very glad to get some ideas on what the problem could be.
EDIT
Here are the elements installed, in case it's relevant:
EDIT2
The type of emulator I'm trying to run is for WearOS. As a test, I tried to create an Android Nexus one. When graphics are set to 'Software', it works. Unfortunately, I can't change this option for the WearOS device. Therefore, it keeps crashing. Sometimes, it even completely crashes my system. My screen freezed, I have to manually reset my computer.
android android-studio android-emulator avd archlinux android android-studio android-emulator avd archlinux asked Nov 14 '18 at 16:44
cyphicscyphics
9513
asked Nov 14 '18 at 16:44
cyphicscyphics
9513
edited Nov 15 '18 at 10:20
cyphics
asked Nov 14 '18 at 16:44
cyphicscyphics
9513
asked Nov 14 '18 at 16:44
cyphicscyphics
9513
asked Nov 14 '18 at 16:44
cyphicscyphics
9513
9513
Open the update manager and check if you have installed "Android Emulator" under the voice "SDK Tools"
– Lorenzo Vincenzi
Nov 14 '18 at 16:55
I've also faced this issue when Android Studio updated recently. Digging dipper into how the emulator is being run, I've figured out that the emulator itself lives in $HOME/Android/Sdk/emulator while the images are stored in $HOME/.android/avd. May bet statvfs() path: No such file or directoryhas something to do with it? I don't remember what was the directory layout of older emulator versions.
– Alexander Solovets
Dec 3 '18 at 15:00
Playing with strace I figured out that the message is about missing ram.img under .android/avd/<NAME>.avd/snapshots/default_foot.
– Alexander Solovets
Dec 3 '18 at 15:23
Try to run the emulator with software graphics. This helped me.
– Alexander Solovets
Dec 3 '18 at 23:38
I ran into a similar problem as yours but I think you're describing a much more serious issue. I'm running Manjaro linux and I just accepted the provided emulator upgrade to version 28.0.20. After upgrade emulator kept crashing with segmentation fault. Switching to software GL allowed me to get the emulator up. Once in there's some configuration in settings that allows you to flip back to hardware open GL I may have fiddled a few other things like cold boot and a reboot of computer but it's all working again magically. This problem feels like a settings migration issue w/ emulator code upgrade
– user3259330
Dec 13 '18 at 4:57
add a comment |
Open the update manager and check if you have installed "Android Emulator" under the voice "SDK Tools"
– Lorenzo Vincenzi
Nov 14 '18 at 16:55
I've also faced this issue when Android Studio updated recently. Digging dipper into how the emulator is being run, I've figured out that the emulator itself lives in $HOME/Android/Sdk/emulator while the images are stored in $HOME/.android/avd. May bet statvfs() path: No such file or directoryhas something to do with it? I don't remember what was the directory layout of older emulator versions.
– Alexander Solovets
Dec 3 '18 at 15:00
Playing with strace I figured out that the message is about missing ram.img under .android/avd/<NAME>.avd/snapshots/default_foot.
– Alexander Solovets
Dec 3 '18 at 15:23
Try to run the emulator with software graphics. This helped me.
– Alexander Solovets
Dec 3 '18 at 23:38
I ran into a similar problem as yours but I think you're describing a much more serious issue. I'm running Manjaro linux and I just accepted the provided emulator upgrade to version 28.0.20. After upgrade emulator kept crashing with segmentation fault. Switching to software GL allowed me to get the emulator up. Once in there's some configuration in settings that allows you to flip back to hardware open GL I may have fiddled a few other things like cold boot and a reboot of computer but it's all working again magically. This problem feels like a settings migration issue w/ emulator code upgrade
– user3259330
Dec 13 '18 at 4:57
Open the update manager and check if you have installed "Android Emulator" under the voice "SDK Tools"
– Lorenzo Vincenzi
Nov 14 '18 at 16:55
Open the update manager and check if you have installed "Android Emulator" under the voice "SDK Tools"
– Lorenzo Vincenzi
Nov 14 '18 at 16:55
I've also faced this issue when Android Studio updated recently. Digging dipper into how the emulator is being run, I've figured out that the emulator itself lives in $HOME/Android/Sdk/emulator while the images are stored in $HOME/.android/avd. May be
t statvfs() path: No such file or directory has something to do with it? I don't remember what was the directory layout of older emulator versions.– Alexander Solovets
Dec 3 '18 at 15:00
I've also faced this issue when Android Studio updated recently. Digging dipper into how the emulator is being run, I've figured out that the emulator itself lives in $HOME/Android/Sdk/emulator while the images are stored in $HOME/.android/avd. May be
t statvfs() path: No such file or directory has something to do with it? I don't remember what was the directory layout of older emulator versions.– Alexander Solovets
Dec 3 '18 at 15:00
Playing with strace I figured out that the message is about missing ram.img under .android/avd/<NAME>.avd/snapshots/default_foot.
– Alexander Solovets
Dec 3 '18 at 15:23
Playing with strace I figured out that the message is about missing ram.img under .android/avd/<NAME>.avd/snapshots/default_foot.
– Alexander Solovets
Dec 3 '18 at 15:23
Try to run the emulator with software graphics. This helped me.
– Alexander Solovets
Dec 3 '18 at 23:38
Try to run the emulator with software graphics. This helped me.
– Alexander Solovets
Dec 3 '18 at 23:38
I ran into a similar problem as yours but I think you're describing a much more serious issue. I'm running Manjaro linux and I just accepted the provided emulator upgrade to version 28.0.20. After upgrade emulator kept crashing with segmentation fault. Switching to software GL allowed me to get the emulator up. Once in there's some configuration in settings that allows you to flip back to hardware open GL I may have fiddled a few other things like cold boot and a reboot of computer but it's all working again magically. This problem feels like a settings migration issue w/ emulator code upgrade
– user3259330
Dec 13 '18 at 4:57
I ran into a similar problem as yours but I think you're describing a much more serious issue. I'm running Manjaro linux and I just accepted the provided emulator upgrade to version 28.0.20. After upgrade emulator kept crashing with segmentation fault. Switching to software GL allowed me to get the emulator up. Once in there's some configuration in settings that allows you to flip back to hardware open GL I may have fiddled a few other things like cold boot and a reboot of computer but it's all working again magically. This problem feels like a settings migration issue w/ emulator code upgrade
– user3259330
Dec 13 '18 at 4:57
add a comment |
1 Answer
1
active
oldest
votes
check your video card drivers. I had the same issue and installed the latest linux nvidia drivers (nvidia-390) in my case since i have a GTX 970.
https://www.mvps.net/docs/install-nvidia-drivers-ubuntu-18-04-lts-bionic-beaver-linux/
answered Jan 25 at 16:06
0xMohamed0xMohamed
11
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53305032%2fcant-start-android-avd-emulator%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
check your video card drivers. I had the same issue and installed the latest linux nvidia drivers (nvidia-390) in my case since i have a GTX 970.
https://www.mvps.net/docs/install-nvidia-drivers-ubuntu-18-04-lts-bionic-beaver-linux/
answered Jan 25 at 16:06
0xMohamed0xMohamed
11
add a comment |
check your video card drivers. I had the same issue and installed the latest linux nvidia drivers (nvidia-390) in my case since i have a GTX 970.
https://www.mvps.net/docs/install-nvidia-drivers-ubuntu-18-04-lts-bionic-beaver-linux/
answered Jan 25 at 16:06
0xMohamed0xMohamed
11
add a comment |
check your video card drivers. I had the same issue and installed the latest linux nvidia drivers (nvidia-390) in my case since i have a GTX 970.
https://www.mvps.net/docs/install-nvidia-drivers-ubuntu-18-04-lts-bionic-beaver-linux/
answered Jan 25 at 16:06
0xMohamed0xMohamed
11
check your video card drivers. I had the same issue and installed the latest linux nvidia drivers (nvidia-390) in my case since i have a GTX 970.
https://www.mvps.net/docs/install-nvidia-drivers-ubuntu-18-04-lts-bionic-beaver-linux/
answered Jan 25 at 16:06
0xMohamed0xMohamed
11
answered Jan 25 at 16:06
0xMohamed0xMohamed
11
answered Jan 25 at 16:06
0xMohamed0xMohamed
11
answered Jan 25 at 16:06
0xMohamed0xMohamed
11
11
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53305032%2fcant-start-android-avd-emulator%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Open the update manager and check if you have installed "Android Emulator" under the voice "SDK Tools"
– Lorenzo Vincenzi
Nov 14 '18 at 16:55
I've also faced this issue when Android Studio updated recently. Digging dipper into how the emulator is being run, I've figured out that the emulator itself lives in $HOME/Android/Sdk/emulator while the images are stored in $HOME/.android/avd. May be
t statvfs() path: No such file or directoryhas something to do with it? I don't remember what was the directory layout of older emulator versions.– Alexander Solovets
Dec 3 '18 at 15:00
Playing with strace I figured out that the message is about missing ram.img under .android/avd/<NAME>.avd/snapshots/default_foot.
– Alexander Solovets
Dec 3 '18 at 15:23
Try to run the emulator with software graphics. This helped me.
– Alexander Solovets
Dec 3 '18 at 23:38
I ran into a similar problem as yours but I think you're describing a much more serious issue. I'm running Manjaro linux and I just accepted the provided emulator upgrade to version 28.0.20. After upgrade emulator kept crashing with segmentation fault. Switching to software GL allowed me to get the emulator up. Once in there's some configuration in settings that allows you to flip back to hardware open GL I may have fiddled a few other things like cold boot and a reboot of computer but it's all working again magically. This problem feels like a settings migration issue w/ emulator code upgrade
– user3259330
Dec 13 '18 at 4:57