Mobile and Embedded

Hi Jason, We are too facing similar keyboard integration error for embedded linux. In this case did you rebuild the whole QT source code of v5.11 OR just QtQuickControl2 module only?

@JKSH Thank you, In fact, on this aarch-linux mechine, qtvirtualkeyboard works well on Konsole, I don't know how Konsole did it. I even tried Pyside2 5.12.5 and it didn't help. I just install qt5, and tried a QTextEdit case under Qt/C++, qtvirtualboard works well. Aren't C++ and pyside calling the same underlying library? # apt show konsole Package: konsole Version: 4:19.12.3-0ubuntu1 Priority: optional Section: universe/kde Origin: Ubuntu Maintainer: Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> Original-Maintainer: Debian/Kubuntu Qt/KDE Maintainers <debian-qt-kde@lists.debian.org> Bugs: https://bugs.launchpad.net/ubuntu/+filebug Installed-Size: 3,951 kB Provides: x-terminal-emulator Depends: konsole-kpart (= 4:19.12.3-0ubuntu1), kio, libc6 (>= 2.17), libkf5configcore5 (>= 4.98.0), libkf5configwidgets5 (>= 4.96.0), libkf5coreaddons5 (>= 5.2.0), libkf5crash5 (>= 5.15.0), libkf5dbusaddons5 (>= 4.99.0), libkf5globalaccel5 (>= 5.0.0), libkf5i18n5 (>= 4.97.0), libkf5iconthemes5 (>= 4.96.0), libkf5kiowidgets5 (>= 4.96.0), libkf5notifyconfig5 (>= 4.96.0), libkf5widgetsaddons5 (>= 4.96.0), libkf5windowsystem5 (>= 4.100.0), libkf5xmlgui-bin, libkf5xmlgui5 (>= 4.98.0), libqt5core5a (>= 5.10.0), libqt5gui5 (>= 5.9.0~) | libqt5gui5-gles (>= 5.9.0~), libqt5widgets5 (>= 5.9.0~), libstdc++6 (>= 4.1.1) Suggests: lrzsz Breaks: kde-l10n-ar (<< 4:16.04.3-6~), kde-l10n-ast (<< 4:16.04.3-6~), kde-l10n-bg (<< 4:16.04.3-6~), kde-l10n-bs (<< 4:16.04.3-6~), kde-l10n-ca (<< 4:16.04.3-6~), kde-l10n-cavalencia (<< 4:16.04.3-6~), kde-l10n-cs (<< 4:16.04.3-6~), kde-l10n-da (<< 4:16.04.3-6~), kde-l10n-de (<< 4:16.04.3-6~), kde-l10n-el (<< 4:16.04.3-6~), kde-l10n-engb (<< 4:16.04.3-6~), kde-l10n-eo (<< 4:16.04.3-6~), kde-l10n-es (<< 4:16.04.3-6~), kde-l10n-et (<< 4:16.04.3-6~), kde-l10n-eu (<< 4:16.04.3-6~), kde-l10n-fa (<< 4:16.04.3-6~), kde-l10n-fi (<< 4:16.04.3-6~), kde-l10n-fr (<< 4:16.04.3-6~), kde-l10n-ga (<< 4:16.04.3-6~), kde-l10n-gl (<< 4:16.04.3-6~), kde-l10n-he (<< 4:16.04.3-6~), kde-l10n-hi (<< 4:16.04.3-6~), kde-l10n-hr (<< 4:16.04.3-6~), kde-l10n-hu (<< 4:16.04.3-6~), kde-l10n-ia (<< 4:16.04.3-6~), kde-l10n-id (<< 4:16.04.3-6~), kde-l10n-is (<< 4:16.04.3-6~), kde-l10n-it (<< 4:16.04.3-6~), kde-l10n-ja (<< 4:16.04.3-6~), kde-l10n-kk (<< 4:16.04.3-6~), kde-l10n-km (<< 4:16.04.3-6~), kde-l10n-ko (<< 4:16.04.3-6~), kde-l10n-lt (<< 4:16.04.3-6~), kde-l10n-lv (<< 4:16.04.3-6~), kde-l10n-mr (<< 4:16.04.3-6~), kde-l10n-nb (<< 4:16.04.3-6~), kde-l10n-nds (<< 4:16.04.3-6~), kde-l10n-nl (<< 4:16.04.3-6~), kde-l10n-nn (<< 4:16.04.3-6~), kde-l10n-pa (<< 4:16.04.3-6~), kde-l10n-pl (<< 4:16.04.3-6~), kde-l10n-pt (<< 4:16.04.3-6~), kde-l10n-ptbr (<< 4:16.04.3-6~), kde-l10n-ro (<< 4:16.04.3-6~), kde-l10n-ru (<< 4:16.04.3-6~), kde-l10n-sk (<< 4:16.04.3-6~), kde-l10n-sl (<< 4:16.04.3-6~), kde-l10n-sr (<< 4:16.04.3-6~), kde-l10n-sv (<< 4:16.04.3-6~), kde-l10n-tr (<< 4:16.04.3-6~), kde-l10n-ug (<< 4:16.04.3-6~), kde-l10n-uk (<< 4:16.04.3-6~), kde-l10n-wa (<< 4:16.04.3-6~), kde-l10n-zhcn (<< 4:16.04.3-6~), kde-l10n-zhtw (<< 4:16.04.3-6~) Replaces: kde-l10n-ar (<< 4:16.04.3-6~), kde-l10n-ast (<< 4:16.04.3-6~), kde-l10n-bg (<< 4:16.04.3-6~), kde-l10n-bs (<< 4:16.04.3-6~), kde-l10n-ca (<< 4:16.04.3-6~), kde-l10n-cavalencia (<< 4:16.04.3-6~), kde-l10n-cs (<< 4:16.04.3-6~), kde-l10n-da (<< 4:16.04.3-6~), kde-l10n-de (<< 4:16.04.3-6~), kde-l10n-el (<< 4:16.04.3-6~), kde-l10n-engb (<< 4:16.04.3-6~), kde-l10n-eo (<< 4:16.04.3-6~), kde-l10n-es (<< 4:16.04.3-6~), kde-l10n-et (<< 4:16.04.3-6~), kde-l10n-eu (<< 4:16.04.3-6~), kde-l10n-fa (<< 4:16.04.3-6~), kde-l10n-fi (<< 4:16.04.3-6~), kde-l10n-fr (<< 4:16.04.3-6~), kde-l10n-ga (<< 4:16.04.3-6~), kde-l10n-gl (<< 4:16.04.3-6~), kde-l10n-he (<< 4:16.04.3-6~), kde-l10n-hi (<< 4:16.04.3-6~), kde-l10n-hr (<< 4:16.04.3-6~), kde-l10n-hu (<< 4:16.04.3-6~), kde-l10n-ia (<< 4:16.04.3-6~), kde-l10n-id (<< 4:16.04.3-6~), kde-l10n-is (<< 4:16.04.3-6~), kde-l10n-it (<< 4:16.04.3-6~), kde-l10n-ja (<< 4:16.04.3-6~), kde-l10n-kk (<< 4:16.04.3-6~), kde-l10n-km (<< 4:16.04.3-6~), kde-l10n-ko (<< 4:16.04.3-6~), kde-l10n-lt (<< 4:16.04.3-6~), kde-l10n-lv (<< 4:16.04.3-6~), kde-l10n-mr (<< 4:16.04.3-6~), kde-l10n-nb (<< 4:16.04.3-6~), kde-l10n-nds (<< 4:16.04.3-6~), kde-l10n-nl (<< 4:16.04.3-6~), kde-l10n-nn (<< 4:16.04.3-6~), kde-l10n-pa (<< 4:16.04.3-6~), kde-l10n-pl (<< 4:16.04.3-6~), kde-l10n-pt (<< 4:16.04.3-6~), kde-l10n-ptbr (<< 4:16.04.3-6~), kde-l10n-ro (<< 4:16.04.3-6~), kde-l10n-ru (<< 4:16.04.3-6~), kde-l10n-sk (<< 4:16.04.3-6~), kde-l10n-sl (<< 4:16.04.3-6~), kde-l10n-sr (<< 4:16.04.3-6~), kde-l10n-sv (<< 4:16.04.3-6~), kde-l10n-tr (<< 4:16.04.3-6~), kde-l10n-ug (<< 4:16.04.3-6~), kde-l10n-uk (<< 4:16.04.3-6~), kde-l10n-wa (<< 4:16.04.3-6~), kde-l10n-zhcn (<< 4:16.04.3-6~), kde-l10n-zhtw (<< 4:16.04.3-6~) Homepage: http://www.kde.org/ Task: kubuntu-desktop Download-Size: 746 kB APT-Manual-Installed: yes APT-Sources: http://ports.ubuntu.com/ubuntu-ports focal/universe arm64 Packages Description: KDE终端模拟器 Konsole 是一个建立在 KDE 平台上的终端模拟器。它可以在单窗口内使用可分离标签 打开多个终端会话。 . Konsole 支持多种强大的终端功能，如色彩方案定制、会话保存和输出监控。```

As I already said, QtWidgets has never been intended to work with mobile devices. So knowing the history of Qt, knowing why QtQuick has been created ... I wouldn't expect this bug to be addressed.

Not solved in 6.8 :(

Not solved in 6.8 :(

HA ! then you must verify that the version code is different for the archs and with each release higher take a look at my pages HowTo do this for CMake: https://t1p.de/ekkeCMakeAndroid for QMake: see in this example: https://github.com/ekke/c2gQtWS_x/blob/master/c2gQtWS_x.pro

easiest way is to use an empty folder for 'Android SDK Location' and hit 'Set Up SDK'. QtCreator will download all what's needed

@Axel-Spoerl Thanks, this is very helpful. I have been putting off the upgrade to 6, so time to just get it done.

One other option is to rebuild the ffmpeg backend (just it) with your system provided librairies.

There is nothing general in the docs, that would say: This is faster, because…. Qt 6 follows a general trend: Use more caching for the sake of speed. There were some optimisations in container classes and string views. We fixed a mem leak in the Quick pixmap cache. The downside of more caching, in other words higher memory consumption, is that older memory constrained setups (mainly embedded) need to swap out and actually become slower. But I guess that’s not a Qt specific phenomenon. All frameworks and other tools I use on a daily basis, have increased their appetite for memory as RAM becomes cheaper and larger.

Solution found... in android manifest, in <application> i must deactivate enableOnBackInvokedCallback, so correct is: android:enableOnBackInvokedCallback="false" from this point, all works as expected seems as new thing from android 13 according to google search

Before you file a bug report: Can you boil this down to a simple reproducer? I am asking, because I can't help the feeling that the issue is caused by the application. The crash happens, when the input connection dies, before the delayed restart is executed. That shouldn't be the case under normal circumstances. => Is there a Qt version where this didn't happen? Even if there is, a small change in event processing can uncover this issue.

Hello, I ran into the same log error messages, when handling a ComboBox in a Qt program running on a custom Compositor. @ulmstefan any outcome to this?

After doing some research, I was able to integrate QtFirebase into my Qt Android application, but I am encountering the RunTime issue below. I have tried various solutions, but the issue still persists. I am encountering a runtime issue with my Android project using Qt and Firebase. Upon attempting to launch the app, it crashes with the following error: `W Zygote : Unable to open libbeluga.so: dlopen failed: library "libbeluga.so" not found. E AndroidRuntime: java.lang.RuntimeException: Unable to instantiate activity ComponentInfo{com.croyance.messenger/com.croyance.messenger.Main}: java.lang.ClassNotFoundException: Didn't find class "com.croyance.messenger.Main" on path: DexPathList... The full logs can be found below. It seems that both the libbeluga.so native library and the Main activity are missing from the APK, which causes the application to fail at runtime. Additionally, there are several warnings related to Firebase initialization and some ANR (Application Not Responding) logs, which may be relevant. `W Zygote : Unable to open libbeluga.so: dlopen failed: library "libbeluga.so" not found. I libc : SetHeapTaggingLevel: tag level set to 0 I yance.messenge: Late-enabling -Xcheck:jni I yance.messenge: Unquickening 21 vdex files! E yance.messenge: Unknown bits set in runtime_flags: 0x40000000 E RefClass: java.lang.reflect.InvocationTargetException I OneTrace: Mark active for pid=25278? true E AndroidRuntime: Caused by: java.lang.ClassNotFoundException: Didn't find class "com.croyance.messenger.Main" on path: DexPathList[[zip file "/data/app/~~AaqN-4a0auFr8HV_MJwQ3g==/com.croyance.messenger-itiNKy_Da7NGfGLvDCWqRw==/base.apk"],nativeLibraryDirectories=[/data/app/~~AaqN-4a0auFr8HV_MJwQ3g==/com.croyance.messenger-itiNKy_Da7NGfGLvDCWqRw==/lib/arm64... I have correctly configured the AndroidManifest.xml file with the following activity declaration for Main: <activity android:configChanges="orientation|uiMode|screenLayout|screenSize|smallestScreenSize|layoutDirection|locale|fontScale|keyboard|keyboardHidden|navigation|mcc|mnc|density" android:name=".Main" android:label="FireBaseQTVersion1" android:screenOrientation="unspecified" android:launchMode="singleTop"> </activity> I have followed the setup guidelines for Android in the QtFirebase documentation, specifically as outlined in the Setup. Environment: Qt Version: 5.15.2 Firebase C++ SDK Version: 6.7.0 Android NDK Version: 21.3.6528147 Gradle Version: 5.6.4 Operating System: Linux

firstly thanks Axel for noticing. I'm very new to boot2qt & yocto and laying at beginning of the learning curve. I've followed not so complete documentation of Boot2Qt and created my own layer trying to set my own build. The truth is I don't know which variables nor arguments to use. I'm familiar with Windows desktop builds and so far i've tried the same approach passing a "-skip qtdecalarative" to EXTRA_QMAKEVARS_PRE variable, which is incorrect. Any help welcome and highly appreciated.

Which Android SDK/NDK Version is installed on the desktop?

embedded this code into main.cpp to see, would it change behavior or not int fontId = QFontDatabase::addApplicationFont("qrc:/assets/fonts/Expansiva.otf"); QStringList availableFonts = QFontDatabase::families(); if (fontId == -1) { qDebug() << "Error: Failed to load custom font from resource."; } else { QStringList fontFamilies = QFontDatabase::applicationFontFamilies(fontId); if (fontFamilies.isEmpty()) { qDebug() << "Error: No font families loaded."; } else { qDebug() << "Font family loaded successfully: " << fontFamilies.first(); // Step 2: Set the font style (font family, size, and optional weight or style) QFont customFont; customFont.setFamily(fontFamilies.first()); // Use the loaded font's family name customFont.setPointSize(12); // Set desired font size customFont.setBold(true); // Make the font bold (optional) customFont.setItalic(false); // Set italic (optional) // Step 3: Apply the custom font globally app.setFont(customFont); } } this address does not provide access to font file: "qrc:/assets/fonts/Expansiva.otf" this, yes: ``` "calc_salary/fonts/Expansiva.otf" resource.qrc looks like <RCC> <qresource prefix="/assets"> <file>fonts/Expansiva.otf</file> <file>fonts/ExpansivaBold.otf</file> <file>fonts/ExpansivaBoldItalic.otf</file> <file>fonts/ExpansivaItalic.otf</file> <file>fonts/ArtsyNight.otf</file> <file>fonts/ROSEMERO.ttf</file> </qresource> </RCC> is it right or not, smart people has to estimate it