Mobile and Embedded

I've tried with Android Studio, similar situation. Emulator works, device doesn't. failed to connect to socket 'localabstract:/io.qt.dice-0/platform-1751563898159.sock': could not connect to localabstract address 'localabstract:/io.qt.dice-0/platform-1751563898159.sock' 2025-07-03 19:31:39.736 28518-28521 nativeloader io.qt.dice D

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.

I had to add this to CMakeLists.txt: https://doc.qt.io/qt-6/qt-add-ios-ffmpeg-libraries.html

@houyawei It may sound silly, but can you try to run the project from a shorter file path?

Another workaround I could see (but it's just an idea) is to have a transparent layer between the popup and the rest of the application so you don't have add that disabling logic everywhere.

@piervalli Oh, that's new, I'll try it out. Thanks!

Putting additional dependencies directly in the android/build.gradle file is the correct way to do it, apparently. This will only be overwritten if you generate templates again.

@TP850 Have you installed Qt for Android yet?

Thanks @hskoglund @SGaist @JKSH Now solved, and build qt can communicate with TLS 1.3 server. After link with OpenSSL, need load cert files to support, system default one will be blank. Cheers. thanks all!

It seems this is QTBUG-135808. Also the updateNativeActivity issue is benign and unrelated.