Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Cannot create a AVD for ABI Armeabi-v7a/Arm64-v8a. Install an image for it
QtWS25 Last Chance

Cannot create a AVD for ABI Armeabi-v7a/Arm64-v8a. Install an image for it

Scheduled Pinned Locked Moved Unsolved General and Desktop
13 Posts 2 Posters 12.7k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K koahnig

    @tomy

    IIRC I had to download AVDs through AndroidSuite before using wiuth creator.

    tomyT Offline
    tomyT Offline
    tomy
    wrote on last edited by
    #3

    @koahnig
    Do you mean that I must install Android suite apart from Android Studio too?

    Android Studio 3.3 has removed System Images for the Arm architecture. So the only way to see the real behavior and output of Android programs is physical devices seemingly.

    K 1 Reply Last reply
    0
    • tomyT tomy

      @koahnig
      Do you mean that I must install Android suite apart from Android Studio too?

      Android Studio 3.3 has removed System Images for the Arm architecture. So the only way to see the real behavior and output of Android programs is physical devices seemingly.

      K Offline
      K Offline
      koahnig
      wrote on last edited by
      #4

      @tomy

      Naming failure on my side. I have installed AndroidStudio and started the AVD manager there.

      0_1549194561085_2da0f5b4-0015-408e-ba5b-1a51dec2132b-image.png

      As marked you can get those AVDs under "Other Images". This is on a windows machine. It took me a while to find this possibility.
      I receive everytime a warning and recommendation to use x84 device, because it is 10 times faster. So far I did not see differences in testing with either machines.

      Vote the answer(s) that helped you to solve your issue(s)

      tomyT 1 Reply Last reply
      0
      • K koahnig

        @tomy

        Naming failure on my side. I have installed AndroidStudio and started the AVD manager there.

        0_1549194561085_2da0f5b4-0015-408e-ba5b-1a51dec2132b-image.png

        As marked you can get those AVDs under "Other Images". This is on a windows machine. It took me a while to find this possibility.
        I receive everytime a warning and recommendation to use x84 device, because it is 10 times faster. So far I did not see differences in testing with either machines.

        tomyT Offline
        tomyT Offline
        tomy
        wrote on last edited by
        #5

        @koahnig

        I'm installing system images for API 25, and don't know if it's a good choice or not!

        As well as, do you mean testing programs on ARM AVDes have no difference from X86? I got the speed difference but can we trust X86 to give us the real and same behavior as real devices?

        K 1 Reply Last reply
        0
        • tomyT tomy

          @koahnig

          I'm installing system images for API 25, and don't know if it's a good choice or not!

          As well as, do you mean testing programs on ARM AVDes have no difference from X86? I got the speed difference but can we trust X86 to give us the real and same behavior as real devices?

          K Offline
          K Offline
          koahnig
          wrote on last edited by
          #6

          @tomy

          I believe Nougat was the newest I could see. However, I am not sure if this was because of other selections.

          @tomy said in Cannot create a AVD for ABI Armeabi-v7a/Arm64-v8a. Install an image for it:

          As well as, do you mean testing programs on ARM AVDes have no difference from X86? I got the speed difference but can we trust X86 to give us the real and same behavior as real devices?

          I was trying to get an initial environment to see where the crashes might happen. For me it worked out with the faster x86 AVDs. I was a bit reluctant as well because it is for sure a different tool chain. At day 's end I would not bet on final results before I have not tested on device anyway. However, solving the issues first on x86 and go afterwards for arm seem to be safe.

          Vote the answer(s) that helped you to solve your issue(s)

          tomyT 1 Reply Last reply
          1
          • K koahnig

            @tomy

            I believe Nougat was the newest I could see. However, I am not sure if this was because of other selections.

            @tomy said in Cannot create a AVD for ABI Armeabi-v7a/Arm64-v8a. Install an image for it:

            As well as, do you mean testing programs on ARM AVDes have no difference from X86? I got the speed difference but can we trust X86 to give us the real and same behavior as real devices?

            I was trying to get an initial environment to see where the crashes might happen. For me it worked out with the faster x86 AVDs. I was a bit reluctant as well because it is for sure a different tool chain. At day 's end I would not bet on final results before I have not tested on device anyway. However, solving the issues first on x86 and go afterwards for arm seem to be safe.

            tomyT Offline
            tomyT Offline
            tomy
            wrote on last edited by
            #7

            @koahnig
            OK, so it's good to first test the app using the X86 ADV and then ARM.
            What is the correct way of creating an AVD, please?

            0_1549204579714_1.PNG

            I mean, I created two ones using Android studio but they're not shown on the list of Qt Creator when I run the app. (Below image)

            2- And when I create another AVD there, using Qt Creator, I then face an error:

            0_1549204633642_Capture.PNG

            K 1 Reply Last reply
            0
            • tomyT tomy

              @koahnig
              OK, so it's good to first test the app using the X86 ADV and then ARM.
              What is the correct way of creating an AVD, please?

              0_1549204579714_1.PNG

              I mean, I created two ones using Android studio but they're not shown on the list of Qt Creator when I run the app. (Below image)

              2- And when I create another AVD there, using Qt Creator, I then face an error:

              0_1549204633642_Capture.PNG

              K Offline
              K Offline
              koahnig
              wrote on last edited by
              #8

              @tomy

              Go to Create Virtual Device
              0_1549206655744_c0e3e553-a90d-4cfb-a633-913e632ddebb-image.png

              Select one you like and press next. You will see download suggestions, but you have to go to "Other Images"

              Vote the answer(s) that helped you to solve your issue(s)

              tomyT 1 Reply Last reply
              0
              • K koahnig

                @tomy

                Go to Create Virtual Device
                0_1549206655744_c0e3e553-a90d-4cfb-a633-913e632ddebb-image.png

                Select one you like and press next. You will see download suggestions, but you have to go to "Other Images"

                tomyT Offline
                tomyT Offline
                tomy
                wrote on last edited by
                #9

                @koahnig
                Please take a look at the screenshot I sent in my previous post. there I created two AVDes, one by X86, and the other Arm. But none is shown when running the app

                K 1 Reply Last reply
                0
                • tomyT tomy

                  @koahnig
                  Please take a look at the screenshot I sent in my previous post. there I created two AVDes, one by X86, and the other Arm. But none is shown when running the app

                  K Offline
                  K Offline
                  koahnig
                  wrote on last edited by
                  #10

                  @tomy

                  Do not know. I have installed Android Studio on standard path. Creator did find AVDs when created with Android Studio. There was no further fuzz.

                  Under "devices" tab "Devices" I have this:
                  0_1549214396844_966a9151-6515-4fc9-bdcd-047125f076b6-image.png

                  Vote the answer(s) that helped you to solve your issue(s)

                  tomyT 1 Reply Last reply
                  0
                  • K koahnig

                    @tomy

                    Do not know. I have installed Android Studio on standard path. Creator did find AVDs when created with Android Studio. There was no further fuzz.

                    Under "devices" tab "Devices" I have this:
                    0_1549214396844_966a9151-6515-4fc9-bdcd-047125f076b6-image.png

                    tomyT Offline
                    tomyT Offline
                    tomy
                    wrote on last edited by
                    #11

                    @koahnig
                    That option was on Local PC but I changed that to yours. Yet, no success!

                    0_1549215088885_Capture.PNG

                    I tested that with all three kits (arm 7a, arm 8a and X86).

                    K 1 Reply Last reply
                    0
                    • tomyT tomy

                      @koahnig
                      That option was on Local PC but I changed that to yours. Yet, no success!

                      0_1549215088885_Capture.PNG

                      I tested that with all three kits (arm 7a, arm 8a and X86).

                      K Offline
                      K Offline
                      koahnig
                      wrote on last edited by
                      #12

                      @tomy

                      Did you restart creator?
                      Sometimes this last resort heals together with an old fashioned reboot everything.

                      Vote the answer(s) that helped you to solve your issue(s)

                      1 Reply Last reply
                      0
                      • tomyT Offline
                        tomyT Offline
                        tomy
                        wrote on last edited by
                        #13

                        I even restarted the OS, but no change in result!

                        1 Reply Last reply
                        0

                        • Login

                        • Login or register to search.
                        • First post
                          Last post
                        0
                        • Categories
                        • Recent
                        • Tags
                        • Popular
                        • Users
                        • Groups
                        • Search
                        • Get Qt Extensions
                        • Unsolved