Android ABI is incompatible
-
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!
-
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!
-
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).
- Perhaps the processor isn't compatible with either, see:
-
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.
-
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).
-
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).
-
@mfashby where is the step 3? and how u did, pls post it here,i m facing same issue with oneplus 3
@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