Mobile and Embedded

@SGaist Thanks but I don't know how that is done on Android.

@ekkescorner Thank for replying. Now I am working in Qt6.6.3, With Android -35, Built the application Successfully, But on android device it shows only a white blank screen with the Name of the application at the top

@jsulm This compiles and runs: int main(int argc, char *argv[]) { #ifdef ANDROID QJniObject activity = QNativeInterface::QAndroidApplication::context(); if(activity.isValid()) { activity.callMethod<void>("setRequestedOrientation", "(I)V", 0); QJniObject window = activity.callObjectMethod("getWindow", "()Landroid/view/Window;"); if (window.isValid()) { const int FLAG_KEEP_SCREEN_ON = 128; window.callMethod<void>("addFlags", "(I)V", FLAG_KEEP_SCREEN_ON); } QJniEnvironment env; if (env->ExceptionCheck()) { env->ExceptionClear(); } } ... The call to fix the orientation into landscape works (solution from a previous topic). The call to keep the screen on does not work. The exception check returns false (if that is relevant ???). Am I setting the correct flags ?

@Pann sorry I forgot these lines in ApplicationWindow: flags: Qt.platform.os === "android"? Qt.Window : Qt.ExpandedClientAreaHint | Qt.NoTitleBarBackgroundHint and Component.onCompleted: if(Qt.platform.os === "android") { window.flags = Qt.ExpandedClientAreaHint | Qt.NoTitleBarBackgroundHint window.visibility = Window.Windowed }

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

@petero3 What env settings in main() you have? Show me the code how qml sink is applied.

Thank you. We have Laird's version of wpa_supplicant in our Yocto. Update is: We've done a POC using wpa_ctrl.c. Couple of issues currently: Initial connection works, but after restart, or reboot, wpa_supplicant fails to parse the conf file: failed to parse psk '*'. That was set using set_network ... psk ... scan while connected only shows currently connected SSID We've also done a POC using Qt Device Utilities and adding ConnMan to our Yocto too: That works better in terms of persisting the password. To stop ConnMan from trying to manage wired ethernet too, needed: [General] NetworkInterfaceBlacklist=eth0,eth1 Scanning for other Wi-Fi networks, while connected to one, is still an issue.

I got this issue when I had VPN running.

@Adla Thank you for sharing. GoogleMobileAds.framework in your Pods.zip works well. May I ask you how you generated this Pods.zip? I tried to generate it but it didn't work as yours. Here is my steps. Run Xcode Create an iOS app project with Interface: Storyboard Language: Objective-C pod init Edit Podfile pod 'Google-Mobile-Ads-SDK' pod install --repo-update But with the resulting GoogleMobileAds.framework, I got many errors, Undefined symbols for architecture arm64: "_$sBOWV", referenced from: $s15GoogleMobileAds24GADMarketplaceKitSignalsCMf in GoogleMobileAds(GADMarketplaceKitSignals.o) "$sScA15unownedExecutorScevgTj", referenced from: $sScTss5NeverORs_rlE8priority9operationScTyxABGScPSg_xyYaYAcntcfCyt_Tgmq5 in GoogleMobileAds(GADMarketplaceKitSignals.o) "$sScAMp", referenced from: _symbolic ______pSg ScA in GoogleMobileAds(GADMarketplaceKitSignals.o) ...

@SMF-Qt cool :)

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 } } } } }

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