Mobile and Embedded

Not QML so with Qt widgets? Just start a new Qt Widgets project in Qt creator, it will work on mobiles too. For pages you can use QStackWidget.

Meanwhile, i have found the reason for QCoreApplication::instance() == 0. I have to wait some time after starting the thread that calls QCoreApplication's exec(). (void) QtConcurrent::run(&runQCoreApplication); do { this_thread::sleep_for(std::chrono::milliseconds(10)); } while(!QCoreApplication::instance() && (++to < 300)); assert(QCoreApplication::instance());

Hi, do you have found a solution for this issue? I have the same problem an try to start a QCoreApplication in an other thread. On Android, it works even if the QCoreApplication does not run on the main thread. THX

You don't need Qt for Automation. It just says that if you have that licence, then you don't need to buy QtMqtt from the Market Place separately. As for the pre-built nature, sorry I do not know. Note that building that module is not that hard. You open it in Qt Creator, build it, and you can even add a custom build step that calls make install.

Ok I changed the way of doing that : I created a *.desktop file in .config/autostart [Desktop Entry] Path=/home/jetson/Startup/Camera_quick Exec=/bin/bash /home/jetson/Startup/Camera_quick/run.sh Type=Application and the run.sh file is : #!/bin/bash export LD_LIBRARY_PATH=/usr/local/Qt-5.15.2/lib/ /home/jetson/Startup/Camera_quick/Camera_quick And that works ! Thanks

Hi and welcome to devnet, Looks like you could be interested by QFileSystemModel coupled to a QListView

@Dmitriano How did you update the build.gradle

I'm getting these following warnings while compiling: warning: 'UIResponder' may not respond to 'application:openURL:options:' return [super application:pApplication openURL:pURL options:pOptions]; ld: warning: method '-application:openURL:options:' in category from /path to file/ overrides method from class in plugins/platforms/libqios_debug.a(qiosapplicationdelegate.mm.o) Are these Okay?

@ad1170 hi! i'm still using Qt5. But yes, you need to run the scheduler in the main loop of your qt application in order to solve it.

First of all I believe QT is GREAT. It allows one to accomplish GREAT work, even though we used to have bumpy rides with it over the years (bugs in framework, Creator hitting the fan). One thing is for sure though. Which made us loose lots of time. - the need for additional gluing between elements always used to be very imminent. I know it can now autonomously download Android SDK and stuff but still we don't even EXPECT that...it never was like ..one common language, with QML portable among many platforms, without the need to be using additional native Mac OS X deployment tools and stuff. Was it? But you can't really attach to a running process on Android and stuff... half of UI options around these lines do no really work...it even says 'non implemented' once you click on it, in log files. Once you get everything setup and running for the project. It's fine. Until sh** happens, and it WILL, with some of the internal files and you have no idea how to approach it. Suddenly it turns out some files can't be opened.. and suddenly you need to be well familiar with native Android, Gradle, Maven, everything. Long ago we began to employ virtualization to offset for that. Turned out to be the best choice. Anyhow, not to cry a river: in file gradle-wrapper.properties changed version to: https://services.gradle.org/distributions/gradle-6.7-bin.zip no idea if that's the right one. It works. Good luck to everyone.

@CodeinSipper said in installing Qbluetooth module: how to install it on windows? Using Qt Maintenance Tool from your Qt set-up.

A hack that I had to do for this to work is to manually copy the so file. if(ANDROID) add_custom_command(TARGET cook-ui-modular-qt POST_BUILD COMMAND ${CMAKE_COMMAND} -E copy ${CMAKE_BINARY_DIR}/App/ConnectedSocket/libConnectedSocket_${ANDROID_ABI}.so ${CMAKE_BINARY_DIR}/App/UserInterface/android-build/libs/${ANDROID_ABI}/libConnectedSocket_${ANDROID_ABI}.so ) endif() This is obviously not the right way to do it. But I don't know how to do it the right way

@raven-worx As I guessed. thank you for the information

Just if anyone interested in. I have used the configure option -qt-host-path /home/[user]/Qt/6.2.2/gcc_64 when building e.g. qt for android on ubuntu.

Thanks @SGaist That was I thought, no other way than make hands dirty with JNI.