Mobile and Embedded

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. [image: d32b9064-46b9-4946-9d4b-1fe8fbcd6a45.png]

I had the same problem (on other platforms as well). I fixed it by using a Flickable for my display object, and modifying the contentY property when I displayed the keyboard: flickable.contentY = Math.max(0, (yValue + (height / 2)) - ((flickable.height - inputPanelPopup.height) / 2)) You'll probably need to modify the algorithm for your application, but the idea should work.

The missing identity file warning says that the local ssh client can't find credentials to log into the i.MX6. The connection to the debugee isn't established, so the debugging process aborts. The ssh connection to the remote system needs to be fixed.

To achieve what I described above, it have to add next deploy step, like below: [image: d18bd488-8c4a-4d5d-8d6a-40662ca6c7cd.jpg]

Hi, Do you mean something like QCA ?

Although this is a very old question I think it's worth to mention this (I searched 3+ days to find a solution). In Qt 6.8 if you set this environment variable it causes the Accessibility manager in QtAccessibilityDelegate.java to completely disable itself: qputenv("QT_ANDROID_DISABLE_ACCESSIBILITY", "1");

Hi @jsulm thanks for answering... the only shortcut i have for qt environment is Qt 6.6.3 MinGW (11.2.0) 64 bits... i tried with it.. but still cant build for Android... i think it should be somewhere or somehow the same shortcut but for ARM and Intel Kits for Android.... that could have more sense...

@Prabhakaran said in need help on build for android: give me any sample codes for android What sample code do you need? Also take a look at: https://doc.qt.io/qt-6/android-getting-started.html https://doc.qt.io/qt-6/android.html

SOLVED: I had to type this command: sudo chmod $USER:$USER $ANDROID_SDK_ROOT I hope this will help unfortunate people like me, who couldn't figure this out for days or even months.

@jsulm , Thank you so much. Now I understood. You got a new follower now.

I have resolved the issue, as the /usr/share directory was not included in the sysroot.