Mobile and Embedded

@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]

Thanks a lot, I think I understand, but if it would not be a problem I would still ask not to close the thread for a few days. I'd like to test it on a "living organism" in the near future and it's quite possible that I'll have a problem with something else. Thanks again,

@Vignesh-R said in Help needed in converting 2 8 bit data into 16 bit: Is it possible that the error lies in how I receive the data from serial port ? See post from @J-Hilk

So there is no easy way to create files in the app and retrieve them on a PC, or reverse? create files on PC and transfer them to the phone to uses them in the app?

@arsinte_andrei said in running qt on Raspberry Pi using EGLFS or install a minimal KDE DE?: how can I get something minimal on rpi? By installing a lightweight window manager like http://www.lxde.org/ (which is written in Qt by the way :-)).

@jsulm Done it, thank you its works i think its just bug in 6.5 and fixed in 6.7 as stated in here https://bugreports.qt.io/browse/QTBUG-119059

Hi, In addition to @Axel-Spoerl, there was at some point a VNC backend added to Qt 5 however, as any of the platform plugins, it would be the only output so not really what you want. Beside the already good suggestion made, one question is: which backend are you currently using ?

Hi, You call show_recPo in get_sum which uses a local object if type CwWindow hence it will to nothing to your main CwWindow.

Hi @TyChapin, Upon connection, the MTU is set to the default value of 23. That's only a "we don't know yet" default, which is, frankly, pretty meaningless. As per the docs: Before the connection setup and MTU negotiation, the default value of 23 will be returned. @TyChapin said in BLE MTU Exchange: Then once I connect to a service, the MTU is 256 which is what the BLE device wants it to be at. Yep, that (256) would be the real, negotiated, MTU. @TyChapin said in BLE MTU Exchange: When I go to read the characteristic value that has 64 bytes, only 24 bytes come over. Does anyone have any advice on how to exchange the MTU size properly? I suspect the problem is not MTU related. In most cases, the MTU should not affect the characteristic data size (just performance), because the BLE stack will use as many MTU's as needed to transfer the characteristic's data. How are you checking the characteristic value's length? ie how do you know that the "value has 64 bytes", and "only 24 bytes come over"? (Also, if its a publicly documented characteristic, and you're able to share the UUID, that might help, but no worries if not). Cheers.

Hello @jsulm I have looked deeper into my problem and found some things. Could you help me by confirming as far as you can? Or recommend someone that may know the answer? I found a new documentation page I hadn't read: https://doc.qt.io/qt-5/ssl.html#enabling-and-disabling-ssl-support When I launched the configure program with the openssl-linked option, I finally got a QtNetwork/qtnetwork-config.h file without the definition that caused trouble (see above). However, when I tried to save the new qmake version and its Android kit, I get an error saying that the Android Clang compiler "can't produce code for the Qt version "Qt 5.15.13 (Qt-5.15.13)" (x86-linux-generic-elf-64bit)." What I understand is that I didn't activate the target for cross-compilation in the initial configuration step. So I went back and launched this OPENSSL_LIBS='-L~/android-sdk/android_openssl/ssl_1.1/arm64-v8a/include -lssl -lcrypto' \ ~/qt5/configure -openssl-linked -prefix /opt/Qt5.15 -xplatform android-clang \ -disable-rpath -nomake tests -nomake examples -android-ndk ~/android-sdk/ndk/21.3.6528147 \ -android-sdk ~/android-sdk -no-warnings-are-errors -opensource -confirm-license But I got the following error: ERROR: Feature 'openssl-linked' was enabled, but the pre-condition '!features.securetransport && !features.schannel && libs.openssl' failed. Check config.log for details. Please note that when I launch the mentioned command without -xplatform android-clang, it seems to work and I am asked to launch gmake. So for the time being I have found myself in an incompatibility of installing an SSL-supported Qt and cross-compiling for Android. Regarding the config log file that the error indicates me, I don't know what exactly to look at. What I find interesting is that at some point there is this SSL-related error (with the -xplatform option): + cd /home/diego/qt-build/config.tests/openssl && MAKEFLAGS= /usr/bin/gmake clean && MAKEFLAGS= /usr/bin/gmake > rm -rf /home/diego/qt-build/config.tests/openssl/android-build > rm -f main.o > rm -f *~ core *.core > /home/diego/android-sdk/ndk/21.3.6528147/toolchains/llvm/prebuilt/linux-x86_64/bin/clang++ -c -target aarch64-linux-android21 -fno-limit-debug-info -fPIC -fstack-protector-strong -DANDROID -O2 -fPIC -I. -I/home/diego/qt5/qtbase/mkspecs/android-clang -o main.o main.cpp > main.cpp:2:10: fatal error: 'openssl/ssl.h' file not found > #include <openssl/ssl.h> > ^~~~~~~~~~~~~~~ > 1 error generated. > gmake: *** [Makefile:193 : main.o] Erreur 1 The weird thing is that without the -xplatform option, I don't see this error, and yet the two command lines are otherwise the same one. Apart from that, there are many other errors, but as I said I don't know exactly what to look at.

@Gautham0517 said in Memory allocation Issue in Raspberry pi 4b 8GB Ram: GEM: F/E May 01 02:24:08.671 <Platform>gp::MemMgr::AllocFail Out of memory allocating The Raspberry is out of memory, I'd say.