Mobile and Embedded

@J-Hilk Alright in that case I think it's easier for me to change the module and use BLE API rather than using objective-c. Thank you so much for clearing that out for me!

Hi Could you try to add brightness & rgbLed: :getBrightness() { return obj; // or what you called it } to class rgbLed : public QObject then in main.cpp QObject::connect(window, SIGNAL(submitTextField(QString)), my_rgbLed.getBrightness(), SLOT(brightnessText(QString))); and remove all brightness my_brightness; as we dont want to use brightness alone ever, only via rgbLed.

@satyanarayana143 Solution for what exactly? Please ask more specific questions. To start with Qt on Android: https://doc.qt.io/qt-5/android-getting-started.html

@jsulm Installing NDK-21 solved my problem, how i understand the problem was NDK-17. Regards, Jasur

Hi, From a quick look at the Qt Sensors module sources, there is support for the light sensor on Android but not on iOS, however it seems that using the light sensor is discourage by Apple and may get your app rejected.

Because you requested the adequate context version.

Hi, Use an older version of Qt or rebuild Qt yourself with an SDK that supports iOS10. Note that it might not possible depending on the API used with your current version of Qt.

Issue closed. Solution is: Setup in Info.plist this value Set the UIViewControllerBasedStatusBarAppearance to NO in the plist <key>UIViewControllerBasedStatusBarAppearance</key> <false/> In main.qml set the flags for Window component import QtQuick 2.12 import QtQuick.Window 2.12 Window { flags: Qt.Window | Qt.MaximizeUsingFullscreenGeometryHint; color: "red" } Create Objective-CPP class and inside of it use this Objective-C code (The example of creating Objective-CPP/Objective-C class published here): [UIApplication sharedApplication].statusBarStyle = UIStatusBarStyleLightContent; and for getting size of status bar use something like this: float ObjectiveCClass::mStatusBarHeight(void) { return [[UIApplication sharedApplication] statusBarFrame].size.height; } Be aware of the previous version of code that switching status bar text marked deprecated, something like this deprecated: [[UIApplication sharedApplication] setStatusBarStyle:UIStatusBarStyleLightContent]; Official Apple guide is here https://developer.apple.com/design/human-interface-guidelines/ios/bars/status-bars/ This 3 steps will make for you something like this [image: c45e9802-5b74-4355-a249-09dbe5dd9d2e.png]

Update: Now I just use a QWidget instead of a QDialog and everything is working fine... dialogwidget.h signals: void WidgetClosed(bool); dialogwidget.cpp: void deletewindowusurewidget::on_btnabort_clicked() { emit WidgetClosed(false); } void deletewindowusurewidget::on_btnok_clicked() { emit WidgetClosed(true); } mainwindow.h private: dialogwidget *usure = new dialogwidget(this); mainwindow.cpp //constructor: connect(usure, SIGNAL(WidgetClosed(bool)), this, SLOT(dialogwidgetclosed(bool))); //start dialog usure->setWindowModality(Qt::ApplicationModal); usure->setWindowFlags(Qt::Tool | Qt::Dialog | Qt::FramelessWindowHint); usure->move(this->rect().center() - usure->rect().center()); usure->show(); //finished signal void MainWindow::deletewindowusureclosed(bool deleteall) { usure->close(); if(deleteall) { //btnok pressed } else { //btnabort pressed } }

@KroMignon said in Issue with mkpath on Android: @koahnig I guess the files are written under /data/user/0/<packagename>/files/ You are correct that this is the path shown with writableLocation. It is also generated under /storage/emulated/0/Android/data/<packagename>/files. However, you cannot simply this /data/user/0/<packagename>/files/ for absolute path' with ofstream under C++. These files are not generated. I was previously wrong. The issue is the same for Android 9 and Android 10. When using /storage/emulated/0/Android/data/<packagename>/files this might be used as basis for absolute path' generation and std::ofstream of C++.

Ok my bad, it seems the problem was caused by my device that was not recognized... Following this link, I've created the udev rule, reloaded the rules so my device is now seen with adb bruel@riyad:~/android$ ./sdk/platform-tools/adb devices -l List of devices attached 5b516a12 device usb:1-1 product:whyred model:Redmi_Note_5 device:whyred transport_id:1 And the application is installed using QtCreator and launched properly \o/ Do I have to manually create a udev rule for all the new device I wish to test?

@sierdzio Thank you for explaining

I install qt 2.12.3; android SDK24,NDK 19; this worked for me!

I am not sure whether both TSLIB and EVDEV can be used at the same time. Does it work if you only use EVDEV ?

Hi, With that much information nobody is going to be able to help you. You shall: explain what you are doing give the exact details of your setup: NDK, SDK, Android version, target spec, etc. provide a minimal compilable example that shows the issue.

@martial123 said in Re-connection automatic after deconnect, BLE: if there is parameter to put a certain value to reconnect automatically I'm not aware of such a parameter

Sorry guys for reopening this one: setting up a device worked like a charm now. But now it says that this Version of SDK Tools does not contain gradle skripts. Working with Android studio they are there and work fine... How can i make QT fin them?