Mobile and Embedded

Please use the code formatting tags provided in the composition widnow to format your code. Makes it so much easier to read and saves the time of volunteers trying to help you. The override syntax is correct. Virtual dispatch gets skipped in the class constructor. That could be one reason. Another reason could be, that the object isn't a ModbusTcpServer. Put some more qDebug() << Q_FUNC_INFO; e.g. in the class constructor. You could also make the override public and see what happens when you call it directly.

The question in this thread is how to trigger a keyboard shortcut, e.g. with a "button widget". That's quite different from a screen recorder. Keeping us in the dark is stealing volunteers' time. If you want to record key events (and probably mouse events, too), you need to install an event filter on the recording level (if you want to record everything, QApplication level - respectively qApp->installEventFilter(filterObject)). There you can intercept and record all events needed. Keep in mind, that for security reasons the window manager "keep" certain shortcuts for itself. For instance, the application will not even see CTRL+ALT+DEL (or what ever is the screen-lock shortcut on your system).

The error you’re encountering indicates a DNS resolution issue, which is often related to network problems. To resolve it, check your internet connection, ensure DNS settings are correct, and consider restarting the DNS service on your machine. If the problem persists, you may need to consult your network administrator or ISP.

Hi, I seen your Youtube video, but that don't work for me. I think I have another problem that's make this one failed. Thank's for the video. It will be helpful for others.

can we build the qt-receipe for Machine qemux86_64? both meta-qt5 and meta-qt6 don't provide machine images. for QEMU you can refer https://docs.yoctoproject.org/dev-manual/qemu.html maybe you are looking for Boot2Qt rather than just meta-qt. how can we write receipe for qt-application? see here https://doc.qt.io/Boot2Qt/b2qt-meta-qt6.html#building-your-own-qt-application

The same way you would build a classic CMake based project. You can use the qt-cmake wrapper to help set things up.

First, ensure that both your Redmi 8 and Redmi 9 devices actually have two physical microphones. Some phones have multiple microphones for noise cancellation or stereo recording, while others may have only one. Make sure your app has the necessary permissions to access the microphone. In Android, you need to request the RECORD_AUDIO permission in your app’s manifest file. QMediaPlayer* player = new QMediaPlayer; QAudioOutput* audioOutput = new QAudioOutput; player->setAudioOutput(audioOutput); player->setSource(QUrl::fromLocalFile("/path/to/coolsong.mp3")); audioOutput->setVolume(50); player->play();

reported the issue to qt support , its now a bug which they are working on: https://bugreports.qt.io/browse/QTBUG-125292 incase anyone else has the same issue, i have a work around fix: construct a timer and a loader. use the timer to delete the media player every time the video finished playing and reconstruct it with the loader. import QtMultimedia Item { /// the below is written as a work around for a bug with the multimedia player on raspberry pi's. /// i belive some kind of memory leak in the media player forms when the media player compiles for the r-pi. /// this causes the media player to slow down with each iteration fo the video loop /// as such , this code deletes the video player and constructs a new video player between each loop. id: root property point beginDrag property var source property bool hotReload Component { id: mediaPlayerContainer MediaPlayer { Component.onCompleted:{ console.log("Player loaded"); play()} Component.onDestruction: {console.log("Destruction Beginning!")} id: mediaPlayer videoOutput: vidya loops: MediaPlayer.Infinite source: root.source } } Timer { id: timer interval: 1000 property int counter: 100 repeat: true triggeredOnStart: true onTriggered: { counter += 1 //console.log(counter) if(counter > 55) { counter = 0 //console.log("hotReaload"); hotReload = true } else hotReload = false } Component.onCompleted:{ timer.start()} } VideoOutput { id: vidya anchors.fill: root } Loader { id:videoloader active: !hotReload sourceComponent: mediaPlayerContainer } Component.onCompleted: {console.log("ITEM LOADED");Loader.active=true; timer.start() } }

Done it, i turn around and do with qt quick

YOu can Ensure that your eglfs app properly handles focus. When the console appears, it might be taking focus away from your app. Check if there’s a way to prevent the console from stealing focus. And verify the stacking order of windows. The console window might be placed above your eglfs app. Adjust the stacking order to ensure your app remains on top.

@SGaist thx. Not all are ported yet, but I'm now prepared ;-) When 6.7.1 is released, I'll finally port all my apps using the recipes I developed for QMake-to-CMake.

Hi guys, did the environment variable help you to get rid of these ANRs? Didn't it backfire somewhere else?

I found the solution at https://professoreletrico.com/cursos/yocto/error-building-qt6-toolchain-in-with-yocto/ - many thanks to Djones Boni. Add a file qtpdf_git.bbappend to your meta-layer and add this content: DEPENDS += " cups"

I've the same warnings - the final build works fine, though. The message comes from com.android.repository.impl.manager.RemoteRepoLoaderImpl. According to the source, there's a loop that should output a list of errors, but it seems to be empty. No idea what exactly causes this yet.

Hi, Based on their documentation, you have to upload App bundles now.

I can confirm that Android 7.1.1 (API 25) works with Qt 6.6.3. I tried to run an app on Redmi 4X. Some information about an older device. I tried to run an application on a phone with Android 4.4.1 (API 19) from Qt 6.6.3, but it did not launch. Error during deployment: :-1: error: The command "E:\AppData\Android\SDK\platform-tools\adb.exe -s 0123456789ABCDEF pull /system/bin/app_process32 E:...\build\Android_Qt_6_6_3_Clang_armeabi_v7a-Debug\android-app-process\app_process" terminated with exit code 1. I installed SDK 19: [image: c5288072-e3e7-48b7-b8b0-9616a3ba7608.png] The phone was detected: [image: bac6f4c7-3bc1-4699-b580-d77b942ac0cb.png]