Solved Device incompatible?
-
Devices shouldn't become incompatible by themselves, so try to figure out what has changed during those 2 months in your Qt environment or the device.
Also, it is not common to suffer from problems before realising that hmm... perhaps I could reboot both of these things... Many problems have been solved that way. -
Is there no way to get more information about why it isn't compatible?
-
Hi,
Did you do any update to your system in between ? For example: NDK, Android OS, Qt Creator ?
-
-
Can you get it listed if you use the
adb
command directly ? -
@SGaist yes the
adb devices -l
command lists the device. -
Do you have only one adb executable in your system ?
-
@SGaist that's the only one I know of. the
adb
command only works when I'm in the/AndroidSDK/platform-tools
directory. -
It's the same that's is configured in Qt Creator ?
-
@SGaist I'm not really sure. Where is that configured?
-
I would say path to the NDK.
-
@SGaist Yes its the same location that I have configured for devices > android
-
I just realised, did you build your application using an API version which is higher than what your Android version supports ?
-
I tried building for API level 24. It says my device is API level 24. I was building for API level 25 at some point but I think I may have switched it after I was finished testing in order to deploy to google play.
-
@kgregory I would also try a different USB-cable, I spend a couple of hours with a similar problem. Apparently my cable broke just enough that the device was detected, but I was unable to transfer any data in-between.
-
@J.Hilk I tried a couple of different USB cables and ports to no avail.
I then thought it would be a good idea to update Qt, so I did (to 4.8.0). After that, creator will no longer launch at all. I get a brief 'busy' graphic and then nothing happens when I try to launch it. So I un-installed Qt and re-installed from scratch but I have the same symptom now. I also tried re-booting my machine.
-
Could it be you've hit QTCREATORBUG-21780.
Try starting QtCreator with
-noload Android
parameter and see if that helps. -
@aha_1980 yes I can successfully launch it that way, but I need Android. Sounds like I'm stuck waiting for a bug fix or a work around?
-
@kgregory it should be fixed in Creator 4.8.1
till then use the workaround described in the report.
-
@aha_1980 ok I followed the work around and am able to launch QtCreator.
However, now I get the following messages when I select a kit:
The system cannot find the path specified. The system cannot find the path specified. 2019-01-04T22:34:33 Clang Code Model: Error: The clangbackend executable "C:\Qt\Tools\QtCreator\bin\clangbackend.exe" could not be started (timeout after 10000ms). clang++.exe: error: unknown argument: '-mthumb-interwork' Project ERROR: failed to parse default search paths from compiler output
I had been using the mingw compiler previously. I tried to set up the mingw compiler and none of the Auto-Detected kits use it. I tried to create a kit manually and when I select that compiler for c++, the icon next to the kit turns to a red exclamation point. I don't see any messages about what the issue is there.
Thanks for the help so far... this is super annoying... Me right now >:-|