Can't start Android AVD Emulator



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








0















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:
enter image description here



enter image description here



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.










share|improve this question
























  • 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











  • 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

















0















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:
enter image description here



enter image description here



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.










share|improve this question
























  • 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











  • 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













0












0








0








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:
enter image description here



enter image description here



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.










share|improve this question
















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:
enter image description here



enter image description here



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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 15 '18 at 10:20







cyphics

















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 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











  • 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











  • 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











  • 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












3 Answers
3






active

oldest

votes


















1














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/






share|improve this answer






























    0














    I got the same issue after updating my nvidia driver to nvidia-390 on Ubuntu 18.10. I removed AVD, rebooted PC and recreated AVD. This steps solved the issue.






    share|improve this answer






























      0














      I had this issue on Ubuntu 18.04 and fixed it by doing exactly the following:



      1. Updating NVidia drivers via:

      ubuntu-drivers devices
      sudo ubuntu-drivers autoinstall


      1. Deleting my AVDs

      2. Rebooting

      3. Creating a new AVD

      You could probably skip step 2 and just create a new AVD to use but my old emulators didn't contain anything special so I just blew them all away because sometimes emulator problems impact all previously created emulators. So I feel better making fresh ones rather than trying to remember which are out-dated.



      Prior to rebooting, I also took these related steps which probably did not directly fix the problem but are still worth mentioning:



      • updated my environment (via .zshrc in my case) to use $ANDROID_SDK_ROOT instead of $ANDROID_HOME, which has been deprecated.

      • put the 'new' emulator location ($ANDROID_SDK_ROOT/emulator/) earlier in my PATH than the 'old' location ($ANDROID_SDK_ROOT/tools/) , per this post.





      share|improve this answer























        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
        );



        );













        draft saved

        draft discarded


















        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

























        3 Answers
        3






        active

        oldest

        votes








        3 Answers
        3






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        1














        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/






        share|improve this answer



























          1














          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/






          share|improve this answer

























            1












            1








            1







            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/






            share|improve this answer













            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/







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jan 25 at 16:06









            0xMohamed0xMohamed

            112




            112























                0














                I got the same issue after updating my nvidia driver to nvidia-390 on Ubuntu 18.10. I removed AVD, rebooted PC and recreated AVD. This steps solved the issue.






                share|improve this answer



























                  0














                  I got the same issue after updating my nvidia driver to nvidia-390 on Ubuntu 18.10. I removed AVD, rebooted PC and recreated AVD. This steps solved the issue.






                  share|improve this answer

























                    0












                    0








                    0







                    I got the same issue after updating my nvidia driver to nvidia-390 on Ubuntu 18.10. I removed AVD, rebooted PC and recreated AVD. This steps solved the issue.






                    share|improve this answer













                    I got the same issue after updating my nvidia driver to nvidia-390 on Ubuntu 18.10. I removed AVD, rebooted PC and recreated AVD. This steps solved the issue.







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Mar 8 at 17:45









                    UfkokuUfkoku

                    1,4081128




                    1,4081128





















                        0














                        I had this issue on Ubuntu 18.04 and fixed it by doing exactly the following:



                        1. Updating NVidia drivers via:

                        ubuntu-drivers devices
                        sudo ubuntu-drivers autoinstall


                        1. Deleting my AVDs

                        2. Rebooting

                        3. Creating a new AVD

                        You could probably skip step 2 and just create a new AVD to use but my old emulators didn't contain anything special so I just blew them all away because sometimes emulator problems impact all previously created emulators. So I feel better making fresh ones rather than trying to remember which are out-dated.



                        Prior to rebooting, I also took these related steps which probably did not directly fix the problem but are still worth mentioning:



                        • updated my environment (via .zshrc in my case) to use $ANDROID_SDK_ROOT instead of $ANDROID_HOME, which has been deprecated.

                        • put the 'new' emulator location ($ANDROID_SDK_ROOT/emulator/) earlier in my PATH than the 'old' location ($ANDROID_SDK_ROOT/tools/) , per this post.





                        share|improve this answer



























                          0














                          I had this issue on Ubuntu 18.04 and fixed it by doing exactly the following:



                          1. Updating NVidia drivers via:

                          ubuntu-drivers devices
                          sudo ubuntu-drivers autoinstall


                          1. Deleting my AVDs

                          2. Rebooting

                          3. Creating a new AVD

                          You could probably skip step 2 and just create a new AVD to use but my old emulators didn't contain anything special so I just blew them all away because sometimes emulator problems impact all previously created emulators. So I feel better making fresh ones rather than trying to remember which are out-dated.



                          Prior to rebooting, I also took these related steps which probably did not directly fix the problem but are still worth mentioning:



                          • updated my environment (via .zshrc in my case) to use $ANDROID_SDK_ROOT instead of $ANDROID_HOME, which has been deprecated.

                          • put the 'new' emulator location ($ANDROID_SDK_ROOT/emulator/) earlier in my PATH than the 'old' location ($ANDROID_SDK_ROOT/tools/) , per this post.





                          share|improve this answer

























                            0












                            0








                            0







                            I had this issue on Ubuntu 18.04 and fixed it by doing exactly the following:



                            1. Updating NVidia drivers via:

                            ubuntu-drivers devices
                            sudo ubuntu-drivers autoinstall


                            1. Deleting my AVDs

                            2. Rebooting

                            3. Creating a new AVD

                            You could probably skip step 2 and just create a new AVD to use but my old emulators didn't contain anything special so I just blew them all away because sometimes emulator problems impact all previously created emulators. So I feel better making fresh ones rather than trying to remember which are out-dated.



                            Prior to rebooting, I also took these related steps which probably did not directly fix the problem but are still worth mentioning:



                            • updated my environment (via .zshrc in my case) to use $ANDROID_SDK_ROOT instead of $ANDROID_HOME, which has been deprecated.

                            • put the 'new' emulator location ($ANDROID_SDK_ROOT/emulator/) earlier in my PATH than the 'old' location ($ANDROID_SDK_ROOT/tools/) , per this post.





                            share|improve this answer













                            I had this issue on Ubuntu 18.04 and fixed it by doing exactly the following:



                            1. Updating NVidia drivers via:

                            ubuntu-drivers devices
                            sudo ubuntu-drivers autoinstall


                            1. Deleting my AVDs

                            2. Rebooting

                            3. Creating a new AVD

                            You could probably skip step 2 and just create a new AVD to use but my old emulators didn't contain anything special so I just blew them all away because sometimes emulator problems impact all previously created emulators. So I feel better making fresh ones rather than trying to remember which are out-dated.



                            Prior to rebooting, I also took these related steps which probably did not directly fix the problem but are still worth mentioning:



                            • updated my environment (via .zshrc in my case) to use $ANDROID_SDK_ROOT instead of $ANDROID_HOME, which has been deprecated.

                            • put the 'new' emulator location ($ANDROID_SDK_ROOT/emulator/) earlier in my PATH than the 'old' location ($ANDROID_SDK_ROOT/tools/) , per this post.






                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered Mar 25 at 18:56









                            gMalegMale

                            8,8991567102




                            8,8991567102



























                                draft saved

                                draft discarded
















































                                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.




                                draft saved


                                draft discarded














                                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





















































                                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







                                Popular posts from this blog

                                Kleinkühnau

                                Makov (Slowakei)

                                Deutsches Schauspielhaus