Mobile and Embedded

Hi Pragmatik, You may take a look on this project. The library has supported to handle the "back button". You may check the example project. https://github.com/benlau/quickandroid

I will use XCB as people are recommending this one for my device. I created a new thread for my XCB-related-errors as it is not related to this one anymore. Thank you for your help!!

So serial printers ?

That I don't know, you should read their documentation and try submitting. Worst case you have to do some rewrites and try again.

With Qt 5.4, the new release, I could get it. I could see the QCompass as one of the available sensors on the device and with the help of the QCompassReading, I could get the azimuth.

You can always use the Java APIs: http://developer.android.com/reference/android/net/wifi/package-summary.html and hook them up to your Qt app via JNI: https://www.qtdeveloperdays.com/sites/default/files/BogdanVatra_Extending_Qt_Android_Apps_with_JNI.pdf

Sorry. I followed this tutorial to build Qt4.8.5, but now I want to use Qt5. There are many options to configure qt5 and I've have many doubts. I want to develop GUI Widgets and QML Applications to run on BBB with touch screen. Thank you

You're welcome ! Since your path are now found, please update the thread title prepending [solved] so other forum users may know a solution has been found :)

Declarative SM Framework is built on top the C++ SM Framework. You may find C++ examples useful. A SM transition can be used to trigger anything, be it a screen transition, network message, file operation etc. If your comfortable with manually triggered screen transitions, you can let the SM trigger that for you, however if the user is the source for screen transitions, an SM may be an overkill.

same problem here... you have any luck figuring it out... I've been screwing around with my Java JRE... wondering if I dorked my Qt/Android deployment somehow.

It's well known for me :)

I'm trying to contribute some money to Qt as well :). Customer does not want to risk the licensing issues later.

Hi, You hide the cursor easily by setting the environment variable like.. export QT_QPA_EGLFS_HIDECURSOR=1 Regards Fredrik

Hi SGaist, I try use qrc on the aplication and it fits perfectly with my needs and a Lot More! Amazing, this solve the problem since i have now the same folter for all platforms and being accessed at the same manner in the code. Beautifull! Since i will distribute the files with the software, now i dont need code a lot of stuff to mantain compatibility between the different plafforms...really Cool! Thanks so much for your help! Kind Regards.

Hi ZapB, Yes, i understand, but i use tha same inicialization routines for both platforms, so i just put the isValid() exactly to check it out if i have a valid context since the makeCurrent call is on the same place for all platforms. Anyway, thanks so much for your help! Too much appreciated! I solve the problem and the functions are working now without any modification on the above code.. I just check the option "Use QML" at the Run settings on the project...but why this affect how the OpenGLFunctions are initialized in Mobile i not discover yet... ;) Kind Regards.