Qt 5.1 and Android unable to start 'org.qtproject.example.myFirstAndroidApp'
- 
wrote on 27 Jun 2013, 09:51 last edited by
I already tried to check those options but the same error occurs.
I'm trying to launch the hello world generated when I choose qt quick 2 application. - 
wrote on 27 Jun 2013, 11:36 last edited by
If you had launched a qt application on android successfully can you tell me the operations that you had done?
thank you - 
wrote on 27 Jun 2013, 11:58 last edited by
Im already working with it on android.
Can I know which smartphone you tried to use + android version?
Did you actually download the SDK and the android APIs?
Do you use the latest NDK?
Have you set OpenJDK location and also ant location?
 - 
wrote on 27 Jun 2013, 12:34 last edited by
I have all this software and I have already set the paths, all this software is in the last version. I've downloaded all yesterday.
I can build the project so it work. I'm trying with the emulator (nexus 5), with API level 10 and 11.
there are not compile errors and the installation on device work correctly but when the application start I can see only a black screen,and the application output on qt creator tell that error.
I've tried with windows and Ubuntu, I've also formatted and reinstalled Ubuntu but it doesn't work.
I'm trying with qt quick 2 application.
which kind of project do you use? - 
wrote on 27 Jun 2013, 13:38 last edited by
Im using an empty qt project and write the stuff on my own.
 - 
wrote on 27 Jun 2013, 13:45 last edited by
Can you write me the code that works for you, please?. So I can try it
 - 
wrote on 27 Jun 2013, 18:51 last edited by
Ok, here is a small project that only contains an exit button
The name is simpleWidget. Please test it on a real device.simpleWidget.pro
@TEMPLATE = app
TARGET = simpleWidgetQT = core widgets gui
OTHER_FILES +=
android/version.xml
android/src/org/qtproject/qt5/android/bindings/QtActivity.java
android/src/org/qtproject/qt5/android/bindings/QtApplication.java
android/src/org/kde/necessitas/ministro/IMinistro.aidl
android/src/org/kde/necessitas/ministro/IMinistroCallback.aidl
android/res/values-el/strings.xml
android/res/values-nb/strings.xml
android/res/values-zh-rCN/strings.xml
android/res/values-id/strings.xml
android/res/values-ja/strings.xml
android/res/values-zh-rTW/strings.xml
android/res/values-de/strings.xml
android/res/values-fr/strings.xml
android/res/values-pl/strings.xml
android/res/values-ro/strings.xml
android/res/values-it/strings.xml
android/res/values-es/strings.xml
android/res/values-pt-rBR/strings.xml
android/res/values-fa/strings.xml
android/res/layout/splash.xml
android/res/values-rs/strings.xml
android/res/values-ms/strings.xml
android/res/values-et/strings.xml
android/res/values/strings.xml
android/res/values/libs.xml
android/res/values-nl/strings.xml
android/res/values-ru/strings.xml
android/AndroidManifest.xmlSOURCES +=
Main.cpp
window.cppHEADERS +=
window.h
@main.cpp
@#include <QApplication>
#include <window.h>int main(int argc, char** argv){
QApplication app(argc, argv); Window window; window.showMaximized(); return app.exec();}@
window.cpp
@#include "window.h"
#include <QPushButton>
#include <QApplication>Window::Window(QWidget *parent) :
QWidget(parent)
{
button = new QPushButton("Exit", this);button->setGeometry(10,10, 300, 300); connect(button, SIGNAL(clicked()), QApplication::instance(), SLOT(quit()));}
@window.h
@#ifndef WINDOW_H
#define WINDOW_H#include <QWidget>
class QPushButton;
class Window : public QWidget
{
Q_OBJECT
public:
explicit Window(QWidget *parent = 0);signals:
public slots:
private:
QPushButton *button;};
#endif // WINDOW_H
@ - 
wrote on 1 Jul 2013, 14:34 last edited by
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.
 - 
wrote on 2 Jul 2013, 08:34 last edited by
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?
 - 
wrote on 2 Jul 2013, 08:52 last edited by
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
 - 
wrote on 2 Jul 2013, 10:55 last edited by
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 - 
wrote on 2 Jul 2013, 11:01 last edited by
What does "adb logcat" say when you try to run the app?
 - 
wrote on 2 Jul 2013, 11:03 last edited by
Moster, which api Level do you use?
 - 
wrote on 2 Jul 2013, 11:09 last edited by
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
 - 
wrote on 2 Jul 2013, 11:09 last edited by
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) - 
wrote on 2 Jul 2013, 11:41 last edited by
What are your deploy configurations?
 - 
wrote on 2 Jul 2013, 11:42 last edited by
Use Qt libraries from device - checked
Use local Qt Libraries - checked
Rest unchecked. - 
wrote on 2 Jul 2013, 11:44 last edited by
Do you have a chance to test it on linux?
 - 
wrote on 10 Jul 2013, 23:33 last edited by
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?
 - 
wrote on 12 Jul 2013, 14:31 last edited by
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.