Qt Forum
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Unsolved

    Call for Presentations - Qt World Summit

    Solved Android ABI is incompatible

    Mobile and Embedded
    4
    10
    6223
    Loading More Posts
    • 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.
    • M
      mfashby last edited by

      Hi all,
      I'm trying to get started using Qt creator to create an Android app, however I can't get it to run on my device.
      I have a nexus 6p on the latest Android version (7.1.1)

      When I press 'run', the device selection menu says 'ABI is incompatible, device supports ABIs: .' for my actual device.

      This is a fresh install of Qt Creator. I already have Android Studio, and I have used the SDK manager in there to update everything to the latest version.

      Any help appreciated!

      jsulm 1 Reply Last reply Reply Quote 0
      • jsulm
        jsulm Lifetime Qt Champion @mfashby last edited by

        @mfashby For the device you need ARM build of your app and Qt. Did you install Qt for Android/ARM?

        https://forum.qt.io/topic/113070/qt-code-of-conduct

        1 Reply Last reply Reply Quote 2
        • M
          mfashby last edited by

          Yeah I have installed QT5.8 for Android for ARMv7:

          0_1493416811920_upload-9673f8dd-4aa5-4b9e-b77c-31bfd53820a8

          I'll try installing the x86 version as well since this will be useful for emulators.

          1 Reply Last reply Reply Quote 0
          • M
            mfashby last edited by

            Nope, makes no difference. When I try to run a project, I get the following dialog:
            0_1493417425650_upload-c8c79253-5c83-468e-8341-615ee265d387

            M 1 Reply Last reply Reply Quote 0
            • M
              mvuori @mfashby last edited by

              Two ideas:

              • Perhaps the processor isn't compatible with either, see:
                https://android.gadgethacks.com/how-to/android-basics-see-what-kind-processor-you-have-arm-arm64-x86-0168051/
              • Whenever there are problems, NDK is a suspect... People usually use the latest one, but I think that the 10f (or some other letter...) is the recommended one (I use 11).
              1 Reply Last reply Reply Quote 0
              • M
                mfashby last edited by

                Thanks, you may be right about processor architecture​ incompatibility. The phone has ARMv8-A CPU. I don't see an option for installing pre-built Qt libraries for this CPU architecture though.

                1 Reply Last reply Reply Quote 0
                • M
                  mfashby last edited by

                  Looks like someone has done this already for an Android ARM-v8 device, they've had to compile QT themselves..:

                  http://blog.qt.io/blog/2017/02/24/building-latest-greatest-android-aarch64-vulkan-teaser/

                  I guess since more devices are using this architecture it might be useful to have it available pre-built to download. I'll find / file a bug report for it. I'll mark this as resolved if the above walkthrough works.

                  1 Reply Last reply Reply Quote 0
                  • M
                    mfashby last edited by

                    None of that was my problem at all. The problem was I hadn't configured my udev rules to access the device properly! Android studio will still allow you to deploy to the device, but QT creator won't. See step 3 on the following page for how to configure:

                    https://developer.android.com/studio/run/device.html

                    After I had done this, the device correctly reported the supported ABIs including both arm64-v8a and armeabi-v7a (which is available as a pre-built binary, no need to build it yourself).

                    T 1 Reply Last reply Reply Quote 1
                    • T
                      tuxcoder @mfashby last edited by

                      @mfashby where is the step 3? and how u did, pls post it here,i m facing same issue with oneplus 3

                      T 1 Reply Last reply Reply Quote 0
                      • T
                        tuxcoder @tuxcoder last edited by

                        @tuxcoder got the answer. actually it needs rsa fingerprint for secure communication...solution is:

                        Try to restart the Adb server.

                        sudo adb kill-server

                        and then

                        sudo adb start-server

                        then connect your device turn Debugging on and type

                        adb devices

                        source : https://askubuntu.com/questions/908306/adb-no-permissions-on-ubuntu-17-04

                        1 Reply Last reply Reply Quote 3
                        • First post
                          Last post