Mobile and Embedded

Hi @Vince_SiriusXM. Did you ever found a fix or workaround for this issue?

i made it myself

hi @Axel-Spoerl - sorry it took me so long to respond. I don't see any typos in my code. It turns out that the deployment didn't work because the target directory didn't exist. I created it manually, and got this to work. Thanks...

@KroMignon being super sassy here as someone who is new to this is trying to understand the landscape. If the system you're deploying to and emulating are both arm, I don't think you would need the google intel x86 system image. that should be for a different type of device.

I ended up switching to QML to solve these issues.

I ended up solving this by using QML instead.

my host machine lists the GLIBC version 2.17 - 2.31 and the g++ -- version is 9.4.0, aarch64-linux-gnu-g++ --version is 9.4.0 and the target board GLIBC versions list from 2.17 -2.36 i was able to cross compile and run my normal c++ projects without any trouble so i don't think the GLIBC versions will be any problem for the qt cross compilation

https://bugreports.qt.io/browse/QTBUG-128829 for what it's worth. I don't understand it yet. But for you, it was working anyway, despite all the warnings?

@Farias I guess Qt5 uses gstreamer and might have only a playbin in it. It may not handle hardware acceleration. Maybe try Qt6 for luck. Or write your own pipeline to make HW acceleration.

The height is in native scale. It is required to devide it by devicePixelRatio: Qt.inputMethod.keyboardRectangle.height / Screen.devicePixelRatio

@Ivelin like this install(FILES android/AndroidManifest.xml android/gradle/wrapper/gradle-wrapper.jar android/gradlew android/build.gradle android/gradlew.bat android/gradle/wrapper/gradle-wrapper.properties android/res/values/libs.xml android/src/com/example/ExtendsQtWithNative.java android/src/com/example/ExtendsQtWithJava.java DESTINATION . )

@Faust-Faust said in QTimer not work: I tried the code you suggested and it actually crashes Which proves that the timer is working. This was intended by @Axel-Spoerl , nothing absurd about it. Please read https://doc.qt.io/qt-5/qtglobal.html#qFatal - qFatal will terminate your app ("If you are using the default message handler this function will abort")

have you tried QDesktopServices (https://doc.qt.io/qt-6/qdesktopservices.html) to open the pdf inside your app with Pdf app outside ?

That's actually independent from Qt version used. Android now requires a signed certificate for remote deployment. Previously you only needed that for deployment in the playstore, but that changed a while ago. I'm not sure if all builds require it, but release builds for sure! @adddeeee in Qt creator, click on project, in the section Build Steps expand the entry Build android APK First entry there should be Application Signature. If you already have a key, link it there and enter your password. If not click on create and follow the steps. [image: 1ba19b8a-32e3-48c8-9250-f468b87f3548.png]

It is inside application binary. You can access it using qtc:/ or :/ paths (this will work only in Qt code, not in Java). More info: https://doc.qt.io/qt-6/resources.html

That doesn’t help. Post a minimal reproducer please, without using designer.

I have just discovered that you can trigger this problem simply by unchecking: Edit -> Preferences ... -> Build & Run -> "Always deploy project before running it" then making changes and rebuilding the project. Turning this option back on solves the problem - without having to use the sledgehammer of removing the AppData/Roaming/QtProject folder! It makes sense, I suppose, though I believe this was not the case in earlier versions of Qt. I am using QtCreator 14.0.1 on Qt6.7.2.