Mobile and Embedded

@SGaist Thank you, your answer helped me!

Interesting, I received complaints from some users that this happens with and Android app I developed. They experience a grey screen on Android 15 (Qt 6.8.3) on Pixel phones. I have not experienced this myself on Android 14 on a Samsung Galaxy S22.

Qt is very sensitive to the environment, and releases often contain bugs.
The main conditions for successful assembly and debugging in my case:

Android build-tool version: should be the latest, i.e. the maximum with which the build is successful. If the build is not successful, then the version should be downgraded. Android build platform SDK: should be the latest, i.e. the maximum, with which the build is successful. If the build is not successful, then you should downgrade the version (https://doc.qt.io/qt-6/android.html + select your Qt release on the page). By the way, on 04/02/2025, the application using API 35 is not built and you should select the previous API version (34). Android NDK must be exactly the one specified in the documentation for the Qt version used (https://doc.qt.io/qt-6/android.html + select your Qt release on the page).

For example, for version Qt 6.8.3 and Qt creator version 16.0.0, successful building and debugging were provided by the following set of components:
-build-tool version: 35.0.1
-build platform SDK: 34 or 33
-android NDK: 26.1.10909125
Снимок.PNG
Снимок1.PNG

@Shrinidhi-Upadhyaya
hello,I followed the same method to test, and the test has been successful, but it still reminds me that some libraries are missing,why is this?
library "libcrypto.so.1.1" not found
library "libcrypto" not found
library "crypto.so.1.1" not found
library "crypto" not found
library "libmaliinstr.so" not found
library "libresolv.so" not found
library "libresolv" not found
: library "resolv.so" not found
library "resolv" not found

That example does not use Python, it's a C++ example.

That said, why not use the C++ SDK for Firestore ?

You are mentioning "various platforms". If it is not just macOS and iOS/ipadOS it is not portable to choose any Apple Framework. And since Qt is mostly about portability (at least on desktop and mobile) it will only/mostly have features that are common on all these platforms. I guess that most people that intend to use Apple's RoomPlan Framework are using Apple frameworks exclusively (including UI).

The easiest way to interface with Apple frameworks used to be Objective-C++. I am not sure how much that has changed with the introduction of Swift. I believe they share the same underlying runtime and so you can still use Objective-C++.

The documentation to launch a custom app on startup is now here

https://doc.qt.io/Boot2Qt/b2qt-customization.html#booting-to-a-custom-application

So here is my findings. Maybe someone can give me a hint
Applying any styleSheet on Android shifts Z-order of QMessageBox which makes its buttons unclickable

Here what is going on:

//setting styleSheet to any widget breaks interactivity on Android setStyleSheet("QPushButton { }"); QMessageBox::information(this,"Check the message", "Is it clickable?" ); //it is not clickable on Android

But if we manually set Z-order to the message this message becomes clickable. But further ones ARE NOT

setStyleSheet("QPushButton { }"); //applying styleSheet QMessageBox msgBox; msgBox.setText("StyleSheet is set. Z-order fixed"); //set stayOnTop flag and it becomes clickable msgBox.setWindowFlags(Qt::Dialog | Qt::WindowStaysOnTopHint); msgBox.exec(); //Next message is unclickable QMessageBox::information(this,"Check next message", "Is it clickable?" ); //No it is not clickable

How to restore correct Z-order for all of my windows and messages after apllying a styleSheet in Android?

@sharan16k said in how to use virtual keyboard for stm32mp157d-dk1:

when i try toimplement as given in the below page

So, does it work or not?

@scottm1982 That's good. Then to help other readers you can Mark as Correct your own final post.

The problem is CMake tries find in /qtbase/lib/cmake/Qt6Core/Qt6AndroidMacros.cmake, but Qt6AndroidMacros in /qtbase/src/corelib. Very stupid solution is change path in qtbase/src/corelib/Qt6CoreConfigExtras.cmake.in line 33 to absolute

@Kaguro Please post whole build log.

@iamnotsad said in Qt5.15.2 for Android: How to make tcp connection keepalived:

Is there any solutions for this issue?

https://developer.android.com/training/run-background-service/create-service

@J-Hilk It all looks fine to me as well, this is why it's even more difficult to find the issue. Oh well, guess I have to spend more time on this than I had planned to. Thanks for all your help tho, I highly appreciate it! :)

Thank you for the support. I will use this tool for further analysis.

Hi @Chai18 Did you find any solution ? I have a similar issue but in the client side (QModbusClient) , this is my function to write data to the holding registers , but I'm all the time getting the response timeout, and master is actually handling incoming requests and send appropriate responses automatically.

void Serial::writeData(int start, const QList<quint16> &holdingRegisters) { if (!modbusDevice) return; startAddress = start; numberOfEntries = holdingRegisters.size(); // Switch to Transmit Mode switchGPIO->setValue(true); // enables TX QModbusDataUnit writeUnit = writeRequest(); QModbusDataUnit::RegisterType table = writeUnit.registerType(); for (qsizetype i = 0, total = writeUnit.valueCount(); i < total; ++i) { const auto addr = i + writeUnit.startAddress(); if (table == QModbusDataUnit::Coils) writeUnit.setValue(i, m_coils[addr]); else writeUnit.setValue(i, holdingRegisters[addr]); } if (auto *reply = modbusDevice->sendWriteRequest(writeUnit, serverAddress)) { if (!reply->isFinished()) { QModbusDevice::connect( reply, &QModbusReply::finished, this, [this, reply]() { // Switch back to Receive Mode usleep(1000); // Small delay before switching switchGPIO->setValue(false); // Enable RX mode const auto error = reply->error(); if (error == QModbusDevice::ProtocolError) { qDebug() << "Write response error:" << reply->errorString() << "(Modbus exception:" << reply->rawResult().exceptionCode() << ")"; } else if (error != QModbusDevice::NoError) { qDebug() << "Write response error:" << reply->errorString() << "(code: 0x" << QString::number(error, 16) << ")"; } reply->deleteLater(); }); } else { qDebug() << "Write error: " << reply->errorString(); reply->deleteLater(); } } else { qDebug() << "Write error: " << modbusDevice->errorString(); switchGPIO->setValue(false); // Ensure RX mode is enabled on failure } }

Thanks in advance

https://bugreports.qt.io/browse/QTBUG-135011

for anyone else encountering this, I have opened a bug with the upstream https://bugreports.qt.io/browse/QTBUG-135011