Mobile and Embedded

Indeed, the problem seems to be on my side. I'll continue to dig in order to find a solution. Thanks

Hi, I don't know in the future QWidget camera will be supported fully on android in the future, but in Qt5.2.1, we could access the raw frame data. "camera bug":https://bugreports.qt-project.org/browse/QTBUG-35243

No problemo good luck & have fun :)

try "grabwindow":http://doc-snapshot.qt-project.org/qdoc/qquickwindow.html#grabWindow

Without any details, it's impossible to understand where is your problem. I've never had any problems on developing QtQuick 2 applications for iOS. So, if you can post more details about your setup, I'll check if there is something strange for me, or different from my setup.

I will read the articles. When I can make a something, I will write post.

It works if MouseArea is embedded in the PinchArea except for onWheel on desktop.

The example show how to call Java from Qt. And do you need to call Qt from Java, right?

In case anybody is interested: I did not manage to cross-compile the library, but I realized that Qt includes Sqlite3 and a XML parser, which was all I needed. I ended up rewriting the old code and removed the external libraries, so now I hopefully won't have to care about platform-specific libraries anymore. Thanks for the help!

Once you connect your phone to the computer, using the terminal or the cmd navigate to the sdk-directory/platform-tools then type in linux: @./adb devices@ in windows: @adb devices@ you should get a list of android devices, if you did not find your device there try to unplug it and plug it again, at the end you must see you device when you run the command,

The full compiling report: @14:55:19: Führe Schritte für Projekt accelbubble aus... 14:55:19: Starte "/usr/bin/make" clean rm -f qrc_accelbubble.cpp rm -f main.o qrc_accelbubble.o rm -f *~ core *.core 14:55:19: Der Prozess "/usr/bin/make" wurde normal beendet. 14:55:19: Unveränderte Konfiguration, qmake-Schritt wird übersprungen. 14:55:19: Starte "/usr/bin/make" /opt/android-ndk-r9b/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/arm-linux-androideabi-g++ -c -Wno-psabi -march=armv5te -mtune=xscale -msoft-float -ffunction-sections -funwind-tables -fstack-protector -fno-short-enums -DANDROID -Wa,--noexecstack -std=gnu++0x -g -g -gdwarf-2 -marm -O0 -fno-omit-frame-pointer -Wall -Wno-psabi -W -D_REENTRANT -fPIE -DQT_OS_ANDROID_GCC_48_WORKAROUND -DQT_QML_DEBUG -DQT_DECLARATIVE_DEBUG -DQT_QUICK_LIB -DQT_SVG_LIB -DQT_QML_LIB -DQT_WIDGETS_LIB -DQT_XML_LIB -DQT_SENSORS_LIB -DQT_NETWORK_LIB -DQT_GUI_LIB -DQT_CORE_LIB -I/opt/Qt5.2.0/5.2.0-rc1/android_armv5/mkspecs/android-g++ -I../accelbubble -I/opt/Qt5.2.0/5.2.0-rc1/android_armv5/include -I/opt/Qt5.2.0/5.2.0-rc1/android_armv5/include/QtQuick -I/opt/Qt5.2.0/5.2.0-rc1/android_armv5/include/QtSvg -I/opt/Qt5.2.0/5.2.0-rc1/android_armv5/include/QtQml -I/opt/Qt5.2.0/5.2.0-rc1/android_armv5/include/QtWidgets -I/opt/Qt5.2.0/5.2.0-rc1/android_armv5/include/QtXml -I/opt/Qt5.2.0/5.2.0-rc1/android_armv5/include/QtSensors -I/opt/Qt5.2.0/5.2.0-rc1/android_armv5/include/QtNetwork -I/opt/Qt5.2.0/5.2.0-rc1/android_armv5/include/QtGui -I/opt/Qt5.2.0/5.2.0-rc1/android_armv5/include/QtCore -I. -I/opt/android-ndk-r9b/sources/cxx-stl/gnu-libstdc++/4.8/include -I/opt/android-ndk-r9b/sources/cxx-stl/gnu-libstdc++/4.8/libs/armeabi/include -I/opt/android-ndk-r9b/platforms/android-9/arch-arm/usr/include -I. -o main.o ../accelbubble/main.cpp arm-linux-androideabi-g++: error trying to exec '/opt/android-ndk-r9b/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86/bin/../lib/gcc/arm-linux-androideabi/4.8/../../../../arm-linux-androideabi/bin/as': execv: Exec format error make: *** [main.o] Error 1 14:55:25: Der Prozess "/usr/bin/make" wurde mit dem Rückgabewert 2 beendet. Fehler beim Erstellen/Deployment des Projekts accelbubble(Kit: Android für armeabi (GCC 4.8, Qt 5.2.0)) Bei der Ausführung von Schritt 'Make' 14:55:25: Verstrichene Zeit: 00:06.@

Never mind the ios kit - just have your Qt app ready and run qmake: ~/Qt5.2.0/5.2.0-rc1/ios/bin/qmake (replace the path with your install location ofc :p), then open the Xcode project file in Xcode and hit build. Just tried this with a QtQuick 2.0 app and it works - app runs very slowly, but works otherwise perfectly. Matti

I did look for it on the bug report system and did not find anything. So here is the feature request https://bugreports.qt-project.org/browse/QTBUG-35295

I don't know what you need, but the general answer is that everything accessible using the android APIs are accessible using androidextras. So, to find your answer take a look to the android developer APIs: http://developer.android.com/reference/android/os/Environment.html

Ok, just another step… to be sure you did everything well. When you download the android sdk … the installer of the 'sdk' does not install anything ! Yep… it's true. What you need to do after, is to run the "android" manager. You found it into the /path/to/sdk/tools/android When you run it, it appear a list of available developer packager organized on the basis of the Android version and API level you want to develop for. Select and install some of these (like API 19, API 10). After that, try to reopen the Qt creator and set the sdk and ndk path, now it should see that there is some kits.

Thanks AlterX. I'm not sure if this is what you mean, but for me another problem was simply the project name on QtCreator - this contained hyphens/dashes, which were not present in the names of the harmattan executables, but were present in the executable command in the .desktop file. For example, my project name on QtCreator was madde-test-3. The files exported to the N9 were called maddetest3 (e.g. /opt/maddetest3/bin etc), but the manifest file was looking for madde-test-3. Changing the filenames in the .desktop file, and re-exporting the project to the N9 worked for me. My .desktop file Exec line in the end was: Exec=/usr/bin/invoker --single-instance --type=d /opt/maddetest3/bin/maddetest3

[quote author="trusktr" date="1385808227"]I really hope Windows Phone can be supported sometime.[/quote] Before that I hope the support of android and ios could become mature, they are the biggest player in the market of smart phone and tablet.

Ok, then using the qmake you've have configured in Qt Creator, what does qmake -query return ?

Hi, I am having similar problem and I am quit new to qt programing. Do you have an example of how to use the CaputureToBuffer ? I do not know how to listen to QCameraImageCapture::imageAvailable() signal. Thanks. [quote author="Yoann Lopes" date="1383734227"]QCameraImageCapture::setCaptureDestination(QCameraImageCapture::CaptureToBuffer) is what you need. Then listen to the QCameraImageCapture::imageAvailable() signal to get notified whenever the buffer is available. You'll notice that what you get is a QVideoFrame, and you'll have to convert it to a QImage if that's what you need.[/quote]