Qt 5.1 and Android unable to start 'org.qtproject.example.myFirstAndroidApp'
-
i have the same problem.i find out that the config of the emulator is bo be blamed.you can try to config it using "armeabi-v7a" instead of "armeabi",or just to choose the android-15 api or above.
-
I tried to run the Qt Quick 2 Application (Built in elements) on my android device (version 4.2.2) using API 17. It compiles successfully but on application output window i get this:
"Starting remote process.Unable to start 'org.qtproject.example.Sample2'."On my device, i see a black screen.
In compile logs i see - "WARNING: No minSdkVersion value set. Application will install on all Android versions.", which seems to be favourable.Can anyone suggest where am I going wrong?
-
I have only tested this stuff on linux (ubuntu 12.04 and 13.04), talking about qtcreator. For me it runs great. What do you use?
I guess usb debugging is turned on, otherwise it would try to start the emulator
Maybe check adb logcat if it says more than qtcreator
-
I am using Qt Creator 2.7.2 based on Qt 5.1.0 on Windows7 32-bit OS.
Yes, USB debugging is ON (I think that is a mandate)Firstly i want to make it work on the emulator.
On that too, it displays the same error and black screen.AVD Manager settings: Data partition size: 1024 Mb
AVD Target: API17
CPU/ABI: armeabi-v7a -
What does "adb logcat" say when you try to run the app?
-
Moster, which api Level do you use?
-
17, since my devices run on 4.2.1 and 4.2.2, but Im using linux, since the windows version is supposed to be less stable
-
Moster,
adb logcat shows the following error on start of application:
E/Qt ( 1469): Can't create main activity
E/Qt ( 1469): java.io.FileNotFoundException: /data/data/org.qtproject.example.Sample/lib/lib--Managed_by_Qt_Creator--plugins_platforms_android_libqtforandroid.so: open failed: ENOENT (No such file or directory) -
What are your deploy configurations?
-
Use Qt libraries from device - checked
Use local Qt Libraries - checked
Rest unchecked. -
Do you have a chance to test it on linux?
-
I'm experiencing the same problem. However, during the deploy step i notice when it tries to install the apk to the emulator, it spits out the following error. This is on windows with almost the same setup.
Error: Could not access the Package Manager. Is the system running?
-
So, I fixed my problem. One I didn't have the emulator using the host gpu. Second, I wasn't giving the emulator enough time to boot up.