Mobile and Embedded

@JoeCFD Thanks for the insight but my path is qt6 and that is my focus.

Page { id: detailPage title: "Detail Page" property StackView stackView property int selectedIndex: -1 property real overlayOpacity: 0.5 property var maskImages: [ "qrc:/images_nose/nose_01.png", ] property string savePath: StandardPaths.writableLocation(StandardPaths.PicturesLocation) + "/QtMultiMedia" CaptureSession { id: captureSession camera: Camera { id: camera } audioInput: AudioInput {} imageCapture: ImageCapture { id: imageCapture onImageSaved: (id, path) => { console.log("📸 Fotoğraf kaydedildi:", path) } } recorder: MediaRecorder { id: recorder onRecorderStateChanged: console.log("🎥 Durum:", recorder.recorderState) onActualLocationChanged: (path) => console.log("🎞️ Video kaydedildi:", path) } //videoOutput: videoOutput videoOutput: videoFrame } Column { anchors.fill: parent spacing: 10 padding: 10 // Kamera + maske alanı Rectangle { id: previewArea width: parent.width * 0.95 height: parent.height * 0.7 color: "#000" // Kamera görüntüsü VideoOutput { id: videoFrame anchors.centerIn: parent width: videoFrame.paintedWidth height: videoFrame.paintedHeight fillMode: VideoOutput.PreserveAspectFit } // Maske overlay (aynı boyut ve pozisyon!) Image { id: overlay anchors.fill: videoFrame width: videoFrame.paintedWidth height: videoFrame.paintedHeight source: selectedIndex >= 0 && selectedIndex < maskImages.length ? maskImages[selectedIndex] : "" opacity: overlayOpacity visible: selectedIndex >= 0 fillMode: Image.PreserveAspectFit smooth: true } // Kamera kapalıysa bilgilendirme Text { anchors.centerIn: parent text: "📷 Kamera görüntüsü buraya gelecek" color: "white" font.pixelSize: 16 visible: !camera.active } } // Maske seçim satırı ScrollView { width: parent.width height: 60 Row { id: maskRow spacing: 8 padding: 4 Repeater { model: maskImages delegate: Rectangle { width: 48 height: 48 border.color: index === selectedIndex ? "red" : "#999" border.width: 2 radius: 4 Image { anchors.fill: parent source: modelData fillMode: Image.PreserveAspectFit } MouseArea { anchors.fill: parent onClicked: selectedIndex = index } } } } }

Thx for the topic and ticket, discussion continuing in https://bugreports.qt.io/browse/QTCREATORBUG-33203

@danish777 Thank you! But I noticed that the same code appear twice in two git repository. (or may be the sub Android Studio project is a temporary one so does not need a repository?) And additionally, the gradle files is not identity so reproducibility might be a problem. Is this the commonly used approch in Qt for Android projects?

Thank you so much for your support . it works now.

@J.Hilk thx for the offer... I already did changes - but it's not public yet give me some weeks to publish a first raw Qt 6.9 / CMake release then you can take a look if I missed something ;-)

My full blown test app now runs on the X86_64 simulator it looks awful its ui was not designed for phone use but all the bells gongs and whistles are there and information from my database is populating the widgets which is good. Time now to reflect on what I have learned and tidy up loose ends, thanks to those who helped on this journey.

Is there a way to specify a custom Makefile file name inside the .pro file itself, so that it doesn't need to be provided externally on the command line?

Haha I think I did it :D After just changing <meta-data android:name="android.app.extract_android_style" android:value="default"/> to <meta-data android:name="android.app.extract_android_style" android:value="none"/> in my AndroidManifest.xml the issues seems to be gone :D

Just to manage expectations: The loggers will tell you what happened, not why it happened. If the application uses a static variable, the initialisation of which you won’t show, if it uses system calls and can’t be compiled on a desktop, there’s a severe architecture problem. Don’t expect more help here. Better fix the application.

@jsulm Thanks for that, added the "add_link_options" near the top of the Qt 6.9.1 top level CMakeLists.txt and the completed build is now 16k aligned: ... qt_internal_top_level_setup_autodetect() add_link_options(-Wl,-z,max-page-size=16384 -Wl,-z,common-page-size=16384) project(Qt VERSION "${QT_REPO_MODULE_VERSION}" DESCRIPTION "Qt Libraries" HOMEPAGE_URL "https://qt.io/" LANGUAGES CXX C ) ...

We have a fix for the Android debugging going to disassembly. It's as simple as setting settings set plugin.jit-loader.gdb.enable off in Preferences > Debugger > GDB > Additional Attach Commands! With this debugging is fast, and reliable. It doesn't stop in disassembly anymore. 🥳

@Gautham-G-B Just to make sure I understand correctly: do you show only one video at given time or several?

Its funny, modules such as these even though they are not mentioned as dependencies, they often "go together", I myself assume if one is installed the other is, but it seems that is not the case and you must specifically ask for each of these per each version to have them installed and available: webkit/engine->webkit/enginewidgets->positioning, all in the maintenence tool but hiding under the <version>->extensions group. Also note that QT does minimal or no set-up of your environment when it comes to runtime libraries. You will find more often than not that you have to either put these libraries into your system's library install folders OR (what I prefer to do) tell your library config tool about the additional locations. Example: For Linux 64-bit debian distributions: /etc/ld.so.conf.d/x86_64-linux-gnu.conf holds locations of all 64-bit libraries. Note there are some naming and directory structure requirements for complex hardware architecture requirements such as sub-archetecture (for example, under x86, we have emt64, mmx, etc) please see your system's ld.so(8) manpage for your system's specific understanding of that (yes the manpages can and will differ from system to system).

Ok instead of copying (and purging) all needed subproject java source files, I solved this issue by having a function in my root projects cmake that append to a global variable: function(include_java_sources PATH) # Create variable for additional subfolders for plugin sources message(STATUS "including extra java sources from path: ${PATH}") set_property(GLOBAL APPEND PROPERTY JAVA_SRC_DIRS "\"${PATH}\"") endfunction() which I call for each subproject to include the needed source directories. Those variable then later gets parsed and inserted into an additional build.gradle file: # Include supproject java source directories get_property(java_dirs GLOBAL PROPERTY JAVA_SRC_DIRS) #message(STATUS "ALL_JAVA_SRC_DIRS: " ${java_dirs}) # Join the paths into a comma-separated string or Gradle list and write to a .gradle file string(JOIN ", " gradle_joined ${java_dirs}) file(WRITE "${CMAKE_CURRENT_SOURCE_DIR}/android/java_dirs.gradle" "ext.extraJavaDirs = [${gradle_joined}]") And finally in my root project build.gradle file I can utilize this and forward it to the project sourceSets: // import generated java_dirs.gradle if present def extraPathsFile = new File(rootDir, "java_dirs.gradle") if (extraPathsFile.exists()) { apply from: extraPathsFile println("Reading extra Java Dirs: " + extraJavaDirs) } ... java.srcDirs = [extraJavaDirs, qtAndroidDir + '/src', 'src', 'java']

seems like this was actually a bug and should be fixed in Qt6.10: https://bugreports.qt.io/browse/QTBUG-138057 So for no I am using .wav files instead and wait for Qt to release 6.10 stable

@jsulm QT Android extras module was removed in QT 6. I have tried to make this work by adding a Java class for the service part. When I called startForegroundService(), I got this error from Android W/Qt JAVA : A QtService tried to start in the same process as an initiated QtActivity. That is not supported. This results in the service functioning as an Android Service detached from Qt. The manifest was set up to handle a foreground service, and all the permissions the app needed running as a forground service. When I researched this error, I found nothing useful from Google, but ChatGpt gave this explanation: "you’ve declared your Qt-based service to run in the same Linux process as your QtActivity, so Qt will refuse to spin up its own event loop inside the service. Instead your stub will simply behave like a plain Java Service and won’t hook into the Qt C++ world—so all of your C++ “keep-alive” logic never runs, and Android kills the process once the UI goes away.... Every QtService must live in its own process. " That was why I posted here, to ask if it is possible to make a QT 6.8.3 app run as a foreground service under Android. If nobody has done it, or know how to successfully do it, then I just have to move on to plan B.