Unable to develop Qt app for android 2.3.3
I started to test Qt for develop android app. As first test I tried to develop a very basic app using API 18 (android 4.3). I created the emulator profile based to 4.3, configured the project and compiled. All went ok and I was able to have my simple app workingon the emulator. However I want to develop my app for support older device also. I repeated all the previous step but basing the emulator to the API 10 (android version 2.3.3), recreated a new project and compiled. The compilation and packaging seem to work. The problem is that every time I start a new compilation, deploiment and run a new instance of the emulator is executed. If I close the new instance of the emulator just launched and leave open the first one (connecte to the default port 5554) Qt Creator return an error informing me that was unable to start the app....
Someone know how to fix this issue?
Let it run completely in the new instance. Close the older instance. Afterwards it will run in the newly created instance only.
Be aware that Qt supports Android 2.3.6+. if you go lower than that, you are on your own.
Thank you for your replies.
p3co: unfortunately your suggestion doesn't work. If I close the first instance a new instance is always executed at each new compilation. The first instance get port numebr 5554, the second 5556. If I close the first instance a new instance is alunched with the same number 5554. If a leave both the two firstinstance running a new instance with port number 5558 is executed and so on. If I close the new and leave the first Qt Creator make the deploy but the app doesn't run...
sierdzio: the officialdocumentation report as minimun version API 10 that is android versione 2.3.3. At least thi is what I can read by using the Android SDK Manager tool. The android version connected to API 10 is 2.3.3 and the next available is 3.0. There isn't the 2.3.6...
I stand corrected. I've just checked the documentation and it does indeed state that the minimal version is Android 2.3.3, so it should work for you.
The problem still remain. I'm the only person trying to develop for android 2.3.3 facing this issue?
Well actually i had also faced the same problem but the steps that i mentioned above worked for me. But i was doing for Android 4.0(Target 14)
If you are using linux try removing the .android directory (take backup first or just rename it to something else). The directory is present in user's home.
I'm developing on Windows. By the way, as written in the first post, working with android 4.3 plaftorm doesn't show any problem at all. The problem are only using 2.3.3...
Then can you check where this directory is created on windows and try removing it or taking backup and then start the new AVD instance.
Its contents are something like,
No way. All the files you mentioned was in the c:\user[username].android folder. Deleted the folder and recreated a new target emulator image as base 2.3.3 version but same issues. I tested Qt Creator in two different PC with installed Windows 7 and 8 but exactly same problem in both....
I'm thinking to wait for the release of 5.2 version of Qt where android support will be declared as "complete".
Hmm. Maybe this would be a bug in QtCreator.
Is possible however the thing surprise me a bit is that it seem no other tried to experiment qt for android using the old basic API 10 for develop?
Please check out Qt 5.2 alpha/ beta. This stuff definitely is being tested, but in Qt 5.1 it was all quite immature.
I have no hurry. I can wait for the official release since, it seem to remeber, is planned for the end if this year, correct?
I've also been trying to develop for 2.3.3, but with no success.
When I try to deploy to a Android device, Qt Creator tells me it couldn't find a device and returns me an error at Deploy Stage (see http://qt-project.org/forums/viewthread/33592/ for more information on this).
After some guidance from p3c0 I found out the Qt isn't building the Android APK. Does anybody knows what could be the reason for that?
Maybe I'll try the Qt 5.2 Alpha this weekend and see if I get any results.