Mobile and Embedded

@zvoopz Right, that's what I do in my non-QML widget code. For my QML code, exposing a C++ object class may be the best solution, if only because QRegularExpressionValidator can do an intelligent "fixup" that would let me accept a paste while filtering out any invalid characters, but it's odd to me that [a] TextEdit still doesn't have a validator property, and [b] QML is still stuck on ECMA 7th edition, which is now nine years old.

Newer versions of Android are able to read native libs directly from the apk without extracting them if they are stored uncompressed in the apk. This is done to save disk space on the device, and the new default during apk creation, but Qt 5.12 does not handle this. To compress native libs again add android:extractNativeLibs="true" in AndroidManifest.xml to the application tag.

One Solution Without QML I've figured a way to get the QVideoWidget to stack behind QPushButton and QLabel in a Widgets application without using QML - the camera has to be started before the stacking order is set. Otherwise, the QVideoWidget gets forced to the front no matter what you do. This worked for me.

When creating a project, selecting "Qt Quick Application (compat)" to generate a .pro-based project allows normal template creation under the "Build Android APK" option. However, choosing "Qt Quick Application" with CMake (generating CMakeLists.txt) causes the issue. This suggests the problem relates to legacy .pro (qmake) vs modern CMake build systems in Qt Android packaging.

Found out this is a known bug: https://bugreports.qt.io/browse/QTBUG-136493

I actually found a solution to my problem :DDD In fact this was a bug in Qt since 6.7.3: https://bugreports.qt.io/browse/QTBUG-135978?gerritReviewStatus=Open which now seems to be fixed https://codereview.qt-project.org/c/qt/qtbase/+/643588 A workaround for now suggest here https://bugreports.qt.io/browse/QTBUG-132412 is to Configure with cmake 3.29+ and the extra -DQT_FORCE_CMP0156_TO_NEW=ON option. which I did by setting the policy in my root project cmake file right before find_package: # Enable CMP0156 explicitly to prevent duplicate symbol errors when using -ObjC linker flag if (POLICY CMP0156) message(STATUS "Setting CMP0156 policy to NEW...") set(QT_FORCE_CMP0156_TO_NEW ON CACHE BOOL "Force CMake policy CMP0156 to NEW behavior for Qt6") elseif () message(ERROR "CMP0156 policy not available! Please switch to cmake 3.29+ and Qt6.9") endif ()

Usually this happens when the Icon itself has white space. Usually people try to accommodate round corners to match the other Icons on the phone. But the round corners come from the OS itself, so the Icon has to be "fullscreen"

Can you try to use 6.8 instead of 6.9.0 ?

I found a global solution for it (resp. ChatGPT :-) and will share it here. class AndroidApplication : public QApplication { public: AndroidApplication(int &argc, char **argv) : QApplication(argc, argv) {} bool notify(QObject *receiver, QEvent *e) override { // Erstmal normal weiterleiten bool ok = QApplication::notify(receiver, e); // Bei jedem UpdateRequest-Event erzwingen wir einen Frame-Swap if (e->type() == QEvent::UpdateRequest) { // Prüfen, ob das Ziel ein QWidget ist if (auto w = qobject_cast<QWidget*>(receiver)) { if (auto wh = w->window()->windowHandle()) { wh->requestUpdate(); // sofortigen Flush anstoßen } } } return ok; } }; It works ! Is this ok in general and for performance issues ?

I found a solution for me hw.gpu.enabled = yes hw.gpu.mode = angle ... what ever it means

Are you sure? This seems pretty nonprofessional. I have no better explanation, though. I would assume, that this affects every fullscreen app... I write a media player, for example. They recently implemented this: https://www.qt.io/blog/expanded-client-areas-and-safe-areas-in-qt-6.9 Which seems to me quite similar. Yes, as a workaround, i use the height of the hidden status bar... Producing wasted space on old phones without rounded corners.

It's already reported as a bug. https://bugreports.qt.io/browse/QTBUG-133228 And i found a workaround: TapHandler, HoverHandler and MouseArea are not affected.

Thank you for the help. I was a little bit stupid and forgot the feature.