Skip to content

Mobile and Embedded

The forum for developing everything embedded: Linux, WinCE, Symbian, MeeGo... you name it.
14.2k Topics 62.7k Posts
  • Qt6.8.2 on Android 15: 200+ java W/System.err when deploy using Qt Creator

    Unsolved
    9
    0 Votes
    9 Posts
    611 Views
    L
    @jsulm So from what you write I assume you would recommend to give a try with the Qt builds for Android via the online installer. I will have a look at that, and report the outcome here.
  • Sharing data between application with Qt 6. How?

    Unsolved
    2
    0 Votes
    2 Posts
    264 Views
    jsulmJ
    @bogong said in Sharing data between application with Qt 6. How?: For example some text in QML application selected and need to be shared with other mobile application on device? That should work out of the box by copying the text and inserting it in another application.
  • How to fill full Pixel 7 screen

    Unsolved
    2
    0 Votes
    2 Posts
    368 Views
    L
    Fixed. Added: leftPadding: 0 // ignore camera cutout / notch rightPadding: 0 // ignore camera cutout / notch
  • i.MX8MP NXP BSP 6.6.3 with QtWebEngine 6.9.1 and Chromium 130.0.6723.192

    Unsolved
    1
    0 Votes
    1 Posts
    175 Views
    No one has replied
  • This topic is deleted!

    Unsolved
    1
    0 Votes
    1 Posts
    9 Views
    No one has replied
  • Cross-compiling on Ubuntu for Android: Qt6 Linguist Tools missing

    Solved
    1
    1 Votes
    1 Posts
    167 Views
    No one has replied
  • Qt Quick 6.9+ ContextMenu on Android - does it work?

    Unsolved
    1
    0 Votes
    1 Posts
    157 Views
    No one has replied
  • This topic is deleted!

    Unsolved
    1
    0 Votes
    1 Posts
    11 Views
    No one has replied
  • Using Java/Kotlin with CMake Qt 6. How?

    Solved
    5
    0 Votes
    5 Posts
    480 Views
    B
    Solution found. Example published. It works for Java code. For using Kotlin haven't found any solution.
  • 0 Votes
    4 Posts
    390 Views
    M
    I moved my app to another directory. I apply new setting of API. I pass this error.
  • Android and fprint(stderr,"%s",message). How?

    Solved
    7
    0 Votes
    7 Posts
    2k Views
    B
    Finally found solution :-)))) Just been reading carefully manuals :-)))) Here published example for this issue
  • Qt 5.15.2 using SAME builtlibs directory for different ABIs

    Unsolved
    7
    0 Votes
    7 Posts
    784 Views
    F
    Hi everyone, I am getting crazy when trying to generate a multi-ABI apk based on a Qt 5.15.2 application, and perhaps this thread may reach someone who faced the same nightmare :-) TL;DR: I can successfully generate apk for armeabi-v7a and apk for arm64-v8a. Can launch these apks in devices supporting the corresponding architectures with no problem. But I would prefer my ci/cd pipeline to output a single "universal" .apk containing the necessary files of both architectures so that a app can run in a device supporting only armeabi-v7a or in a device supporting only arm64-v8a. When calling, qmake app.pro -spec android-clang CONFIG+=qtquickcompiler ANDROID_ABIS="arm64-v8a armeabi-v7a" the generated android-app-deployment-settings.json has the following content { "description": "This file is generated by qmake to be read by androiddeployqt and should not be modified by hand.", "qt": "/home/lin-deploy/Qt/5.15.2/android", "sdk": "/home/lin-deploy/Android/Sdk", "sdkBuildToolsRevision": "35.0.0", "ndk": "/home/lin-deploy/Android/Sdk/ndk/21.3.6528147", "toolchain-prefix": "llvm", "tool-prefix": "llvm", "ndk-host": "linux-x86_64", "architectures": {"arm64-v8a":"aarch64-linux-android", "armeabi-v7a":"arm-linux-androideabi"}, "android-extra-plugins": "/home/lin-deploy/Desktop/deploy/1368/android/plugins/5.15.2/arm64-v8a/plugins", "android-package-source-directory": "/home/lin-deploy/Desktop/deploy/1368/android/app", "android-min-sdk-version": "21", "android-target-sdk-version": "28", "android-extra-libs": "/home/lin-deploy/Desktop/deploy/1368/lib/cryptopp/crypto/bin/android/arm64-v8a/libcrypto.so,/home/lin-deploy/Desktop/deploy/1368/lib/cryptopp/crypto/bin/android/arm64-v8a/libcryptopp_arm64-v8a.so,/home/lin-deploy/Desktop/deploy/1368/lib/cryptopp/crypto/bin/android/arm64-v8a/libssl.so,/home/lin-deploy/Desktop/deploy/1368/lib/Qt5Psql/5.15.2/arm64-v8a/libpq.so,/home/lin-deploy/Desktop/deploy/1368/lib/libssh/bin/android/arm64-v8a/libssh.so", "qml-root-path": "/home/lin-deploy/Desktop/deploy/1368", "stdcpp-path": "/home/lin-deploy/Android/Sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64/sysroot/usr/lib/", "qrcFiles": "/home/lin-deploy/Desktop/deploy/1368/res/resources2.qrc,/home/lin-deploy/Desktop/deploy/1368/res/resources.qrc,/home/lin-deploy/Desktop/deploy/buildApp/app_ui_libs_libs_qmlcache.qrc,/home/lin-deploy/Desktop/deploy/1368/app/ui/fonts/fonts.qrc,/home/lin-deploy/Desktop/deploy/1368/app/ui/images/images.qrc,/home/lin-deploy/Desktop/deploy/buildPocket/app_ui_qml_app_qmlcache.qrc,/home/lin-deploy/Desktop/deploy/1368/app/ui/libs/libs.qrc,/home/lin-deploy/Desktop/deploy/1368/pocket/ui/qml/app.qrc", "application-binary": "App" } after calling make to build, the two targets (armeabi-v7a and arm64-v8a) get built successfully. But due to the lack of armeabi-v7a versions of android-extra-libs in the above mentioned .json file, when executing androiddeployqt, the resulting .apk seems to work only on devices supporting arm64-v8a. I forced already the inclusion of abiFilters in defaultConfig block of my build.gradle file with no effect defaultConfig { resConfig "en" minSdkVersion = qtMinSdkVersion targetSdkVersion = qtTargetSdkVersion ndk{ abiFilters "arm64-v8a", "armeabi-v7a" } } I am defining explicitly the additional libraries that must be deployed per architecture i.e. equals(QT_ARCH, "armeabi-v7a") { ANDROID_EXTRA_LIBS = blabla_armeabi-v7a.so ANDROID_EXTRA_PLUGINS += $$_PRO_FILE_PWD_/android/plugins/$$QT_VERSION/armeabi-v7a/plugins } equals(QT_ARCH, "arm64-v8a") { ANDROID_EXTRA_LIBS = blabla_arm64-v8a.so ANDROID_EXTRA_PLUGINS += $$_PRO_FILE_PWD_/android/plugins/$$QT_VERSION/arm64-v8a/plugins } This approach is working perfectly when deploying separate apks for each architecture, but no matter what I do it looks like arm64-v8a overrides everything in the process of generating the android-app-deployment-settings.json. I even swapped the order of the ABIS in the qmake call (arm64-v8a followed by armeabi-v7a) in order to test this possibility, but the resulting .json file would list arm64-v8a extra libs and plugins only. Did anyone successfully build AND DEPLOY a multi-abi apk using Qt 5.15.2? Any recomendation on how to tweak the .json so that androiddeployqt can make sense of it and generate the expected multi-abi apk with appropriate libs hierarchy and AndroidManifest? Thank you so much!
  • Qt Quick 6.9.2 on Android 15 - status bar text invisible in Light mode (works in Dark)

    Unsolved
    1
    0 Votes
    1 Posts
    85 Views
    No one has replied
  • Qt6 iOS custom SceneDelegate

    Solved
    3
    0 Votes
    3 Posts
    538 Views
    M
    Hey @nguyenbinh may I follow up on this question because I am facing the same issue :D What version of Qt you are using? Are you aware if Qt6.9.1 still only uses AppDelegate protocol and no Scene-"stuff" at all? I wasn't able to find any documentation or deeper info on this topic at all :s
  • Boot to Qt does not work with raspberry pi 5's touch display 2.

    Solved
    3
    0 Votes
    3 Posts
    3k Views
    A
    In case it might help, I solved the issue by replacing the dtoverlay given in the QT Doc : dtoverlay=vc4-kms-dsi-7inch With the one given on the Raspberry Website : dtoverlay=vc4-kms-dsi-ili9881-7inch Also, don't forget to make these changes in /etc/kms.conf, otherwise you will end up seeing just the console : { "hwcursor": false, "device": "/dev/dri/card1" }
  • 0 Votes
    5 Posts
    2k Views
    O
    @TheoSys said in Qt 6.5.3 - minSdkVersion and targetSdkVersion missing values or grayed out in AndroidManifest: This is because putting the SDK version into the manifest is deprecated. Where did you find this information? I tried searching both Qt documentation and Android documentation and I have not been able to find that this approach is deprecated. Also, this neither explains why some Android API levels are not listed.
  • Qt 6.5.1 android audio playback issue

    Unsolved
    1
    0 Votes
    1 Posts
    503 Views
    No one has replied
  • This topic is deleted!

    Unsolved
    1
    0 Votes
    1 Posts
    2 Views
    No one has replied
  • Qt 6.5.3 on Android: No audio device detected

    Unsolved andriod qt 6.5.3 c++ audio
    1
    0 Votes
    1 Posts
    962 Views
    No one has replied
  • QtCreator App Output Panel: stop/filter Android Messages

    Unsolved
    2
    0 Votes
    2 Posts
    255 Views
    Axel SpoerlA
    I guess you mean android debugging messages, not related to QLoggingCategory. From the top of m head, I see several ways to achieve less verbosity: Filter field: If you search a specific phrase, just enter it in the search field and anything else will be muted. Adb settings: In the Android Kit's Android Settings, you can toggle "Show logcat output" Specific logcat filters in Tools->Devices->Android