Mobile and Embedded

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.

Here is the same code using appDataLocation void DatabaseManager::OpenConnection() { // Configure the database connection parameters for SQLite m_db = QSqlDatabase::addDatabase("QSQLITE"); // Use QStandardPaths to get the application data location QString dbName = "identifier.sqlite"; QString dbLocation = QStandardPaths::writableLocation(QStandardPaths::AppDataLocation); QString fullDbPath = dbLocation + "/" + dbName; QDir dbDir(dbLocation); if (!dbDir.exists()) { if (dbDir.mkpath(dbLocation)) { qDebug() << "Created application data directory:" << dbLocation; } else { qDebug() << "Failed to create application data directory:" << dbLocation; return; // Exit if the directory cannot be created } } // Set the SQLite database file location m_db.setDatabaseName(fullDbPath); // Check if the database file exists in the application data location if (!QFile::exists(fullDbPath)) { qDebug() << "Database does not exist in AppDataLocation, copying from resources."; // Path to the resource database file QString resourceDbPath = ":/resources/identifier.sqlite"; // Adjust the path to your resource file // Attempt to copy the database from resources to the writable location if (QFile::copy(resourceDbPath, fullDbPath)) { qDebug() << "Database copied successfully to AppDataLocation."; // Set file permissions to writable (necessary for some platforms) QFile::setPermissions(fullDbPath, QFileDevice::ReadOwner | QFileDevice::WriteOwner); } else { qDebug() << "Failed to copy database from resources."; return; // Exit if the database cannot be copied } } // Open the database connection and handle success or failure if (m_db.open()) { qDebug() << "Database opened successfully."; // Sample query to verify the database contents } else { // Handle connection error qDebug() << "Database failed to open."; qDebug() << m_db.lastError().text(); } }

My workaround for the time being is as follows: Construct the Java class when the related C++ class is constructed Set Activity for the class Call static methods like before Java: private static Activity m_activity = null; public void setActivity(Activity activity) { m_activity = activity; return; } also change all methods that previously called QtNative.activity() to now check for and use m_activity instead. C++: mJNIInstance = QJniObject("the/qualified/ClassPath"); if (mJNIInstance.isValid()) { mJNIInstance.callMethod<void>("setActivity", "(Landroid/app/Activity;)V", QNativeInterface::QAndroidApplication::context().object()); } else { // output a warning or error }

I needed to add developer mode and trust the developer on my iphone