Mobile and Embedded

Thanks, that's working for me. One more question: How do you access the .ini file? I'm getting a 'permission denied' error if I try to access the file via an emulated terminal on the device. If i use your code, the ini file will be saved to the path: "/data/data/org.qtproject.example.textproject/files/.config/config.ini"

I was reading many different forums and came across this: "Mono toolchain compile c# script and .dll libs into ARM assembly code ( .s file), then assemble the assembly code into native executable code with Android SDK/NDK. (I'm not sure, whether Mono generate JVM code in the middle)" Does anyone know anything about this? or how it might work?

Hi, You may have found a bug. You should check the "bug report system":http://bugreports.qt-project.org to see if something known. If not, please consider opening a new report providing a minimal compilable example showing the problem.

You are leaking memory with your mobile variable that is never deleted and you don't start the sensor

I am trying to port a 4.7 class to 5.x, and I'm having this problem. However, its not a visual component, It is a QAbstractItemModel derived component. What is the resolution for that?

You're welcome ! If you're now able to cross-compile properly, please update the thread title prepending [solved] so other forum users may know a solution has been found :)

Do you know of any documentation that talks about the number followed by the Dalvik? I'm curious to why they chose that name.

This issue was associated with the ssl certificates. The embedded linux version of openssl does not create the certificates. We had to manually create all the certificates and then the secure connection happened. "Here is the site that showed us how to create the cert..":http://www.linuxfromscratch.org/blfs/view/svn/postlfs/cacerts.html

I do develop single source cross-platform apps for Win, Linux, MAC, Android and iOS. After you get the basics per platform, it's simple to port them :) Your pro file requires to have containers for platform specific code like JNI on android or the icons on iOS. E.g: @android { QT += androidextras@ or @ios { BUNDLE_DATA.files = $$PWD/iosImages/Icon-60.png @ I'm unsure about Qt 5.3, but with 5.2 I had problems using SSL connections on iOS. Such problems you need to add exceptions for the platforms with QtGlobal. @#ifdef Q_OS_ANDROID #endif@ Would only compile the code between if the target is an Android device. You do not need any special Qt version, the basic free one is fine. Libs are added as always, using your .pro file and @LIBS +=@

Afaik the gestures are not working properly on android, which is a little problem. Anyway, I'd start taking a look here: http://qt-project.org/doc/qt-5/qgesture.html For the items in the menu itself, I'd recommend QPushButtons. They look great in flat style on android. http://qt-project.org/doc/qt-5/QPushButton.html

Done !!

In general, QQuickView needs a QWindow, and not a QWidget (unless you use a QWindowContainer).

What board it is? Which processor it has? Edit: Ok i read email from you, and now i know that it is Beaglebone Black. I don't known how it works for new BBB with Debian (earlier default was Angstrom on internal flash ) because i haven't tested yet, but for Angstrom read this "thread":http://qt-project.org/forums/viewthread/35542 . Derek Molloy's tutorials are ok but little outdated.

Yea, the app runs for the most part. I am just trying to get to the underlying problem by troubleshooting each error one at a time. I suppose i could let this one go for now and move on...

Hi, To get additional options: @./configure -embedded --help@ Hope it helps

Hey, let us know if the "showMaximized() or showFullscreen()" worked for ya.