Mobile and Embedded

@J.Hilk oh yes it is working great ; P

@X-Krys said in Cross compilation issues Qt + libmatrix_creator_hal: So it means I should use GCC 6 to match the compiler that lib has been built with ? 6 is the library version, so you should use the same major version of the stdc++ (assuming they keep binary compatibility, which I'm not sure about). Also you need to use a compiler that produces code that is binary compatible with the compiler used to build that library, unfortunately I have no clue which version is that exactly, but I really doubt it's as old as gcc 4.8.3.

Yep. I'm having trouble too. I'm documenting my frustration in this thread: https://forum.qt.io/topic/98432/analog-clock-example-build-run-on-android

So I thought I should close this one out. It turns out the issue in the title was a red herring. What happened was I had set the API level to a higher level when I built the APK to deploy to google play. The higher level was not compatible with my device. I then updated android SDK, which created a new issue that is preventing me from building. Thus I was not able to build for my API level (API level 24) and I got the device incompatible message. That said, I still have a problem that has me stumped. I've found two other threads where people have encountered the exact same problem I have and I have not seen a solution posted. I have completely re-installed SDK, NDK, JDK. I've wiped out my build config settings and my .pro.user file. I've also tried the example projects in addition to my project. I get the same error. Here are the threads describing the issue I still have: https://forum.qt.io/topic/91958/android-not-working-in-qt5-11-1/2 https://forum.qt.io/topic/91310/cant-build-qt-example-for-android/

If you built Qt for Raspberry it will default to eglfs platform plugin. Try starting your app with the "-platform xcb" parameter to use the X11 platform if you are running your app from X.

@Yassinec_chb the only thing that will be slower than a cross compile build would be the actuall compiling of the code. But it is reasonably fast enough if you have a Raspberry Pi 3 or later

got it, thanks. btw, i am test the QUdpSocket with QT5.12.0, the readDatagram does get the sender's ip back well.

You can do that using the "Topic Tools" button.

Found the working solution: use mipmap property for smooth downsampling (https://stackoverflow.com/questions/23286666/qml-image-smooth-property-not-working ). But I still wonder why only 8" tablet MediaTek MT8735, GPU Mali-T720 produces this issue?

Shouldn't that rather be done using push notifications ?

Out of curiosity, what is the limitation for not using Wayland ?

Did you ever resolve this? I'm getting the same error. I followed the guide posted by @raven-worx and I don't see any issues with my setup. FWIW, my QtCreator doesn't seem to recognize gcc as a a compiler option (it only has MinGW and several flavors of Clang). Also, I'm using Qt 5.9.3, Android SDK 26.1.1, JDK 8 update 121, and ndk r10e.

Take a look at https://www.bartslinger.com/cx-10-quadcopter/debugging-stm32-from-qtcreator/ and similar articles. Key words: "qtcreator debugging stm32"

Well, if you have Xorg, why not use it in mirror mode ? Doing so you won't have anything special to do from your application.

I found the solution. I needed to turn on SSP by using a call to the system system("hciconfig hci0 sspmode 1");