Mobile and Embedded

Hi, I was able to change the NDK root and it compiled all the way till the Generating Android Package step. The next issue i think is a gradle version mismatch. I have the latest gradle version installed and on my system path, but it downloads 5.6.4 during the build and uses that I think which is not compatible with JDK 17:

7d0cb23c-1b18-4fbb-af2a-0664e6fe459d-image.png

9f5e0144-a8c6-47c3-8398-e088d6c1620c-image.png

Any workarounds to that would be highly appreciated

This is a known issue with Qt 6.8.1

Here's the issue in the Qt Bugtracker

The comments describe a workaround: copy the androiddeployqt binary from Qt 6.8.0 to the appropriate folder for Qt 6.8.1

I've found the solution! (Qt doc is wrong)

set_target_properties(SamsungRC PROPERTIES QT_ANDROID_EXTRA_LIBS "${CMAKE_CURRENT_SOURCE_DIR}/ssl/android/${ANDROID_ABI}/libcrypto_3.so;${CMAKE_CURRENT_SOURCE_DIR}/ssl/android/${ANDROID_ABI}/libssl_3.so" )

The values in QT_ANDROID_EXTRA_LIBS need to be separated by a semicolon.

Have you set the target SDK level and build tools?
I have this for my app targeting API level 34

set_target_properties(appskywalker PROPERTIES QT_ANDROID_PACKAGE_SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/android QT_ANDROID_TARGET_SDK_VERSION 34 QT_ANDROID_SDK_BUILD_TOOLS_REVISION 34.0.0 QT_ANDROID_VERSION_NAME ${APP_VERSION} QT_ANDROID_VERSION_CODE ${VERSION_CODE})

I use ApplcationWindow instead of Window in my Android app. That one is automatically full screen on Android.

This is not a Pixel issue, but an Android 15 issue. Seems QML does not properly render emoji on Android 15. Started a new topic for that.

Opened https://bugreports.qt.io/browse/QTBUG-132481 for this issue

Oh right, thanks for letting me know. At least I know it's not something I've done wrong

Interesting. I have the same issue when I try to run my own app on the emulator, i.e. it looks very similar to your screen shots.,
I could not find a solution.

@jsulm
@mrdebug
I probably found appropriate knowledge about approach to programming STM32MP1.
The STM32MP1 series is based on Cortex-A7 and Cortex-M4 cores architecture.

First Way:
First of those (Cortex-A7) is required to create GUI (ex. Boot2Qt) .
But second one (Cortex-M4) is required to communicate with STM32 peripheral (ex. by STM32CubeProgrammer).
Data processed in Cortex-M4 can be send to GUI (Cortex-M7) over the “Inter processor Communications” (IPC) virtual UART.

Second Way:
All programing by userspace Linux .... -> desktop PC-like approach to programming ?

Does anyone know how to implement Firebase Core and Firebase Analytics for both Android and iOS using CMakeLists.txt in Qt ?

I thought it is transparent for us.

in this section https://developer.android.com/guide/practices/page-sizes?hl=en

...
If your app uses any native code, then you should rebuild your app with support for 16 KB devices. If you are unsure if your app uses native code, you can use the APK Analyzer to identify whether any native code is present and then check the alignment of ELF segments for any shared libraries that you find.

..

But I don't understand if it is mandary where devices are page size 16KB.

@Aaron-Liao
Check this: https://bugreports.qt.io/browse/QTBUG-130576

I have created a bug report for this issue.

Fixed in 6.7.3

FIxes in 6.7.3