Mobile and Embedded

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.

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 . In case OpenSTLinux ad STM32MP157f-DK2 , necessery is to turn on CAN0 by editind device tree.
Device tree is generated by STM32CubeMX.
Just make sure to install the appropriate version of the STM32Cube* tools - supplied with the Ecosystem version you are using.

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

Keyboard hide on RETURN seems to be solved in Qt6.7.3

I understand that only with Qt we can control DRM properties because it is the master and DRM can accepts only one master. But I don't need to implement any other drm interface, but I have to use qtplatform library, because they are speaking with drm.

So, investigating inside the code I have found a solution, but it use QPlatformScreen that is a Private Api:

add to cmake:

target_include_directories(appeturnix-qt6 PRIVATE ${qt_include_path}/QtGui/6.8.1/QtGui )

and then you can use QPlatformScreen that is a private library...so...

QPlatformScreen *pScreen = screen->handle(); pScreen->setPowerState(QPlatformScreen::PowerStateOff);

@harlan56 Hi, have you tried QApplication::desktop()->grab(); function?

Hello, Have you figured it out what was the problem? I'm having a similar issue.

In the past, I had problems with touchscreen devices running on Linux. I don't know what your situation is exactly, but in my case, I had to run calibration routines. I assume that Windows could have the same issues. Could you be facing the same problem?

@jack_study_qt Hi Jack,

I'm facing kinda the same issue about libc:

19:31:14: Package deploy: Running command "C:\Users\MadGuy\AppData\Local\Android\Sdk\platform-tools\adb.exe -s emulator-5554 pull /system/bin/app_process64 D:\Projects\Qt\DiceRoller\build\Android_Qt_6_8_1_Clang_x86_64-Release\android-app-process\app_process". 19:31:14: Package deploy: Running command "C:\Users\MadGuy\AppData\Local\Android\Sdk\platform-tools\adb.exe -s emulator-5554 pull /system/bin/linker64 D:\Projects\Qt\DiceRoller\build\Android_Qt_6_8_1_Clang_x86_64-Release\android-app-process\linker64". 19:31:15: The command "C:\Users\MadGuy\AppData\Local\Android\Sdk\platform-tools\adb.exe -s emulator-5554 pull /system/bin/linker64 D:\Projects\Qt\DiceRoller\build\Android_Qt_6_8_1_Clang_x86_64-Release\android-app-process\linker64" terminated with exit code 1. 19:31:15: Package deploy: Running command "C:\Users\MadGuy\AppData\Local\Android\Sdk\platform-tools\adb.exe -s emulator-5554 pull /system/lib64/libc.so D:\Projects\Qt\DiceRoller\build\Android_Qt_6_8_1_Clang_x86_64-Release\android-app-process\libc.so". 19:31:15: The command "C:\Users\MadGuy\AppData\Local\Android\Sdk\platform-tools\adb.exe -s emulator-5554 pull /system/lib64/libc.so D:\Projects\Qt\DiceRoller\build\Android_Qt_6_8_1_Clang_x86_64-Release\android-app-process\libc.so" terminated with exit code 1. 19:31:15: Package deploy: Failed to pull "/system/lib64/libc.so" to "D:\Projects\Qt\DiceRoller\build\Android_Qt_6_8_1_Clang_x86_64-Release\android-app-process\libc.so".

Here are the gradle.properties:

org.gradle.jvmargs=-Xmx2500m -XX:MaxMetaspaceSize=768m -XX:+HeapDumpOnOutOfMemoryError -Dfile.encoding=UTF-8 # Enable building projects in parallel org.gradle.parallel=true # Gradle caching allows reusing the build artifacts from a previous # build with the same inputs. However, over time, the cache size will # grow. Uncomment the following line to enable it. #org.gradle.caching=true #org.gradle.configuration-cache=true # Allow AndroidX usage android.useAndroidX=true androidBuildToolsVersion=34.0.0 androidCompileSdkVersion=android-34 androidNdkVersion=26.1.10909125 androidPackageName=com.diceroller.app buildDir=build qt5AndroidDir=C:/Qt/6.8.1/android_x86_64/./src/android/java qtAndroidDir=C:/Qt/6.8.1/android_x86_64/./src/android/java qtGradlePluginType=com.android.application qtMinSdkVersion=28 qtTargetAbiList=x86_64 qtTargetSdkVersion=34

The tools downloaded are shown in the screenshot. GPT said some latest Google Play images doesn't allow pulling system files. But I found this post. I'm suspicous about the SDK Version 16.0 in the screenshot.

Screenshot 2024-12-14 195906.png