Mobile and Embedded

Partial solution is found: https://bugreports.qt.io/browse/QTBUG-138915

Sure thing ! No problem with asking first here :-) Thanks for the link !

@Axel-Spoerl said in Finding config files in Android runtime deployments (Qt6.9.1): QDirIterator it(":", QDirIterator::Subdirectories); while (it.hasNext()) qInfo() << it.next(); Thanks for that but I see files I have in my images directory and stuff from the qt project but nothing from :/assets, but as I said the file is there if I unpack the Apk file. Do I need to add something to the AndroidManifest.xml or my qrc file ?

@neuehier, although not 1:1, wxWidgets is usable for EFI GUIs (I've a LINX 1010 with one), and it can delegate to wxQt when required. I can't imagine a situation in which you'd run the preboot application outside of a preboot environment, though, so, in practice, it wouldn't delegate to it frequently. If you needed the application to be versatile enough to be able to operate in both environments, though, it'd work.

@zvoopz said in QT for Qnx Project Configuration / Kit Error: Look at the sreenshots he has provided - qmake This is how you add a Qt version in QtCreator - by pointing to qmake

I have tried various ways to get "getWindow().addFlags(WindowManager.LayoutParams.FLAG_KEEP_SCREEN_ON)" running however the only solution that works for me is to put it in the "onCreate" method in the QtActivity java class (Qt6.9.1) . It really needs to be conditional but I don't know enough about java to do that. Any suggestions welcome.

@SMF-Qt Found the solution: changed the static method call in my C++ file to: batteryLevel = QJniObject::callStaticMethod<jdouble>("QtBattery","getBatteryPercentage",QNativeInterface::QAndroidApplication::context()); And it now works.

@SMF-Qt I have noticed that after I click the Quit button and my application has exited main I sometimes get the following abort message from the QtCreator debugger: W/qtMainLoopThrea: type=1400 audit(0.0:64483): avc: denied { read } for name="/" dev="tmpfs" ino=1 scontext=u:r:untrusted_app:s0:c209,c256,c512,c768 tcontext=u:object_r:device:s0 tclass=dir permissive=0 app=com.home.QtTest4 W/qtMainLoopThrea: type=1400 audit(0.0:64484): avc: denied { read } for name="devices" dev="sysfs" ino=4521 scontext=u:r:untrusted_app:s0:c209,c256,c512,c768 tcontext=u:object_r:sysfs:s0 tclass=dir permissive=0 app=com.home.QtTest4 D/EGL_emulation: app_time_stats: avg=171.19ms min=6.22ms max=947.76ms count=6 I/ImeTracker: com.home.QtTest4:89e0e728: onRequestHide at ORIGIN_CLIENT reason HIDE_SOFT_INPUT fromUser false I/ImeTracker: com.home.QtTest4:c4e121a7: onRequestHide at ORIGIN_CLIENT reason HIDE_SOFT_INPUT fromUser false D/EGL_emulation: app_time_stats: avg=2462.04ms min=33.03ms max=10232.86ms count=5 I/default : main() returned 0 D/VRI[QtActivity]: visibilityChanged oldVisibility=true newVisibility=false W/default : java.lang.NullPointerException: Attempt to invoke virtual method 'void android.content.Context.unregisterReceiver(android.content.BroadcastReceiver)' on a null object reference W/default : at org.qtproject.qt.android.network.QtNetwork.unregisterReceiver(QtNetwork.java:49) W/default : at org.qtproject.qt.android.QtNative.startQtApplication(Native Method) W/default : at org.qtproject.qt.android.QtNative$$ExternalSyntheticLambda4.run(D8$$SyntheticClass:0) W/default : at org.qtproject.qt.android.QtThread$1.run(QtThread.java:25) W/default : at java.lang.Thread.run(Thread.java:1012) W/default : F/libc : FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x749993a02ab8) F/libc : FORTIFY: pthread_mutex_lock called on a destroyed mutex (0x749993a02ab8) F/libc : Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 20289 (hwuiTask0), pid 20225 (.home.QtTest4) 09:24:14: Android target "com.home.QtTest4" died.

Hi, If memory serves well, it was usually around every three releases. 5.6 -> 5.9 -> 5.12 -> 5.15. 6.5 -> 6.8

I have done some more research. Using Android services with Qt is problematic. There is however a simple flag in the manifest file that allows a QT app to keep it's main thread-loop running when the app is in the background, so that it can be used for audio playback, or receiving push notifications that can trigger actions in the main Qt thread, when the user is not actively using it. <meta-data android:name="android.app.background_running" android:value="true"/> This setting, in the application entity gave me the most important functionality I was looking for.

Hi @Isaias , I have achieved to run two displays (LVDS + HDMI) using Wayland Weston, and running an instance of Weston in clone-mode: /usr/bin/weston --modules=systemd-notify.so --tty=1 --device=/dev/fb0,/dev/fb2 --clone-mode Here, the content of fb0 is cloned to fb2. It works, but on my SoM (i.MX6 based), I now experience severe lag on the LVDS screen and the touch inputs are also delayed. Additionally, I had to tune down the HDMI resolution to 900x600 to get it to work. On my SoM, using DRM/KMS is not an option, since my kernel version does not support it. I use fbdev instead. Maybe this helps a bit. If anybody has another solution, please share!

@ekkescorner , your post in another thread helped: https://forum.qt.io/post/829606

Yep, I was able to install everything I need from Qt6 on RPi Ubuntu. Setting... set(CMAKE_PREFIX_PATH "usr/lib/aarch64-linux-gnu/cmake/") ...allowed CMake to find everything. Like one of my highschool maths teachers used to say, "Don't do it how I've shown you on the board."

it is Webview issue. will update soon when find the fix.

@Pruza For android build VS C++ compiler is not needed anymore. You can simply do it with QtCreator.

@cristian-adam Tested qtcreator 17.0.1 with my Samsung A06 Phone and Tab9 Tablet and both now deploy correctly. Thankyou.