Mobile and Embedded

@Medievil As far as i know dunfell is the most stable branch.i used yocto from dunfell and meta-qt5 from dunfell.I did not make any modification to package configurations.Everything is working fine

@Vignesh-R said in How to receive serial data sent as Struct and convert it to decimal: I am not sure if I am losing precision when I am doing this. I will have to look into it. But from my current guess looking into the value, I don't think I am losing any precision. Just so you know. If your original int x value is greater than +32767 or less than -32768 you will not get the right result back after conversion, because the number uses more than 16 (signed) bits in the first place. If you don't have values like that then that is fine, but then you might as well store x in a int16_t in the first place so that you will know the allowable range. What is the possible range of "the sensor in a floating point something like -9.81"?

@Sajjad-Ali Start here: https://doc.qt.io/qt-6/qudpsocket.html You will also find links to example applications there.

@Ronel_qtmaster But the Pi2 has a different core than the zero 2. How can that work? The top of my toolchain.cmake will look like this: cmake_minimum_required(VERSION 3.18) include_guard(GLOBAL) set(CMAKE_SYSTEM_NAME Linux) set(CMAKE_SYSTEM_PROCESSOR arm) set(TARGET_SYSROOT /home/nils/zero-sysroot) set(CMAKE_SYSROOT ${TARGET_SYSROOT}) set(ENV{PKG_CONFIG_PATH} $PKG_CONFIG_PATH:/usr/lib/arm-linux-gnueabihf-gnu/pkgconfig) set(ENV{PKG_CONFIG_LIBDIR} /usr/lib/pkgconfig:/usr/share/pkgconfig/:${TARGET_SYSROOT}/usr/lib/arm-linux-gnueabihf-gnu/pkgconfig:${TARGET_SYSROOT}/usr/lib/pkgconfig) set(ENV{PKG_CONFIG_SYSROOT_DIR} ${CMAKE_SYSROOT}) # if you use other version of gcc and g++ than gcc/g++ 9, you must change the following variables set(CMAKE_C_COMPILER /usr/bin/arm-linux-gnueabihf-gcc-11) set(CMAKE_CXX_COMPILER /usr/bin/arm-linux-gnueabihf-g++-11) set(CMAKE_C_FLAGS "${CMAKE_C_FLAGS} -I${TARGET_SYSROOT}/usr/include") set(CMAKE_CXX_FLAGS "${CMAKE_C_FLAGS}") set(QT_COMPILER_FLAGS "-march=armv8-a") set(QT_COMPILER_FLAGS_RELEASE "-O2 -pipe") set(QT_LINKER_FLAGS "-Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed")

@iSolve_Tech The real challenge of your program is how to save video recordings on Android. Opening the camera is not an issue! I couldn't find any usable QT6 APIs for this purpose, so in the end, I had to resort to calling the native Android API to allow users to specify the destination and file name for saving!

Sorry, I didn't realize someone had actually replied to this old thread. We determined it wasn't worth it and just used GStreamer directly (in C code, with the qmlglsink plugin). If I remember correctly, when I was trying the QtMultimedia route, after all my trouble, I was just barely able to get the basic example to work. As soon as I tried pulling in some other gstreamer elements to parse actual RTSP or other types, I had other library errors. Probably needed to link against more plugins or something. And it just wasn't worth the hassle to figure out the rest, especially considering I had to rebuild Qt from source every time I wanted to try. Not to mention the fact that even if I was successful, building Qt from source creates a serious challenge to our development workflow. We'd either have to host our custom built Qt somewhere, or just have every developer build from source themselves. Plus since then we've encountered some requirements that required pipeline manipulation that I don't think would have been possible through the QtMultimedia interface anyway. We've had to do some dynamic pipeline stuff that you really need to be able to write C code for. Tl;dr don't bother with QtMultimedia GStreamer on Android. Its either not possible or not worth the trouble.

@BerndJ Great! Thank you, saved me a lot of time reading every possible (wrong) answer..

@Vince_SiriusXM yes, I have a static library that results in conflicts when compiling for different apks and I found this solution. Haven't had a Problem with it since then. Android section of the pro file: android { # Android Version code, needs to be upped by 1! ITERATION=24 ANDROID_VERSION_CODE = $$ITERATION QT += androidextras OBJECTS_DIR = generated/$${ANDROID_TARGET_ARCH}/obj .... LIBS += -L$$OUT_PWD/Dependencies/ThCommunication/ -lThCommunication_$${ANDROID_TARGET_ARCH} PRE_TARGETDEPS += $$OUT_PWD/Dependencies/ThCommunication/libThCommunication_$${ANDROID_TARGET_ARCH}.a .... }

@Nitish875 said in Build error: 10:20:04: The kit supports "arm64-v8a", but the device uses "x86_64". Error while building/deploying project daqudwqw (kit: Android Qt 6.5.3 Clang arm64-v8a) When executing step "Deploy to Android device": same issue I am getting but unable to find the solution Did you try what was suggested in that thread? "already i changed but getting same issue always" - what exactly did you change? You need to select a different Kit (one that matches the target device architecture).

@PR1G0RYAN QTCreator has a bug where it defaults to compiling with QT6 for Android. If you want to use QT5.15, please refer to my reply in the other thread.

@lilili hi and welcome to devnet, By following the information from the link posted by @Pablo-J-Rogina.

@JoeCFD Thanks for the input, but I ended up using a new image.

@SGaist Thanks both of you. But Ive swapped to X11 and that fixed my problems.

@RogueWarrior https://doc.qt.io/qt-6/android-services.html https://developer.apple.com/documentation/uikit/app_and_environment/scenes/preparing_your_ui_to_run_in_the_background/using_background_tasks_to_update_your_app

Adding PrivacyInfo.xcprivacy to your iOS/macOS App NOTES NOTE : Your post does not tell me if you're trying to release for iOS or macOS - hopefully this addresses both NOTE : I found this same issue late last night. I've coded what you will see below but as it is a long weekend at Apple HQ I'm still waiting for my app to be reviewed. I will update if these instructions need changing. As of May 1st 2024 Apple require your application to identify the reasons that various OS features are used. This is mostly to deter the use of information such as boot time and file system statistics to fingerprint users without their permission. One needs to create a PrivacyInfo.xcprivacy file and place it in your app bundle. This file is an XML file in PLIST format (XML not binary). Essentially the file has the same content on both platforms but the app bundle location is different. iOS : PrivacyInfo.xcprivacy files is located in the bundle root macOS : PrivacyInfo.xcprivacy files is located in Content/Resources My project still uses qmake (for a lot of reasons). If you're using CMake please adjust your instructions (if you are then a follow-up with CMake instructions would be beneficial to all) Note that I have ios and macos folders under my project root that contain platform specific files. Add this code to your qmake files.. ios { app_privacy_declarations.files = $$files($$PWD/ios/PrivacyInfo.xcprivacy) QMAKE_BUNDLE_DATA += app_privacy_declarations } NOTE is have not tested this macOS as I have not released a macOS application yet. macx { app_privacy_declarations.path = Contents/Resources app_privacy_declarations.files = $$files($$PWD/macos/Contents/Resources/PrivacyInfo.xcprivacy) QMAKE_BUNDLE_DATA += app_privacy_declarations } Here is my PrivacyInfo.xcprivacy file. I will admit I don't quite understand the root cause for all the warnings. Some are, clearly, from Qt's libraries whereas others are from my purchasing library. As long as we obey "the letter of the law" in terms of Apple's rules on fingerprinting and taking data off device we will be fine. <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>NSPrivacyAccessedAPITypes</key> <array> <dict> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategorySystemBootTime</string> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>35F9.1</string> </array> </dict> <dict> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategoryFileTimestamp</string> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>C617.1</string> </array> </dict> <dict> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategoryDiskSpace</string> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>E174.1</string> </array> </dict> <dict> <key>NSPrivacyAccessedAPIType</key> <string>NSPrivacyAccessedAPICategoryUserDefaults</string> <key>NSPrivacyAccessedAPITypeReasons</key> <array> <string>CA92.1</string> </array> </dict> </array> </dict> </plist> LINKS Please find additional content on the Apple website https://developer.apple.com/documentation/bundleresources/privacy_manifest_files/describing_use_of_required_reason_api https://developer.apple.com/documentation/bundleresources/placing_content_in_a_bundle