Mobile and Embedded

@jfurtak good to hear that my app was helpful. ...yep, life isn't easier now with edge-to-edge windows ;-) BTW: did a short test on iOS, where you always (in Landscape and Portrait) have a navigation line at bottom. There it's also not possible, to swipe from bottom to open the Drawer. if it's important for you to open Drawer from bottom by swiping you should create an Issue at Qt Bugreports with all your screenshots and code. Feel free to mention me there. Would be better to continue discussing there.

That message "Android support is not yet configured" comes from https://code.qt.io/cgit/qt-creator/qt-creator.git/tree/src/plugins/android/androiddevice.cpp?h=20.0#n1296 - that would suggest like @JKSH suggested that the Qt for Android is not yet installed. Whether it should not be even possible to Add -> Android Device when Qt for Android is not yet installed is another way to look at this. @TP850 Please install Qt for Android first from Qt Installer or Maintenancetool

Hello @ap.sirius, I'm not able confirm how this works in Qt 5 or what would be the proper workaround if the fixes in QTBUG-97503 or related fixed tickets indeed do not work for you, but this is fixed in Qt 6 and I'm not seeing this kind of behavior there. I would suggest migrating to Qt 6 (6.8 LTS or newer) if possible.

I would suggest trying tools recommended by Android: https://developer.android.com/ndk/guides/memory-debug HWASan works, but it also has some limitations ( Only for 64 bit apps, for example)

had similar problems, but only with some versions of GBoard this is workaround for Landscape keyboard: do not anker the keyboard [image: 4c87dcdb-5de5-457f-be37-3e5288800222.png] [image: d762d5f3-a841-4ac0-867d-b394cfd72fd5.png]

I'm not using 6.8.x, but with Qt 6.10.1+ Safe Areas are working for me see also my Test App https://github.com/ekke/ekkesTestStatusBar

for me it's working on Android and iOS with Qt 6.10.1+ see also my test app: https://github.com/ekke/ekkesTestStatusBar

Bug report here.

Hi, Boot2Qt being a commercial offering, you would need to contact the Qt Company directly about that matter.

Hi and welcome to devnet, Based on the module documentation and the simple example, I would say yes.

@WR.Kim Qt version is not set in your Kit. CMake is not set in your Kit.

Did you find a solution to that ? I have the same problem.

I made some more digging and I found that it helps qtbase/src/platformsupport/input/tslib/qtslib.cpp:58 void QTsLibMouseHandler::readMouseData() { static ts_sample sample; while (get_sample(m_dev, &sample, m_rawMode)) { and also works this: void QTsLibMouseHandler::readMouseData() { ts_sample sample; qCDebug(qLcTsLib) << "hello"; while (get_sample(m_dev, &sample, m_rawMode)) { but why !?

@jcelerier said in qt.permissions: Could not find permission plugin for QBluetoothPermission. Please make sure you have included the required usage description in your Info.plist: I had this situation, it turns out you have to link explicitly with Qt6::QDarwinBluetoothPermissionPlugin Thank you!! This is exactly what I needed, and did not find anywhere else. If could give up-vote your reply multiple times, I would! 😊

@The-Qt-Mayssa I think we're talking in circles. If you want someone in the forum to analyze the problem, you need to provide a minimal reproducer. In the unlikely case that it's a bug in Qt, it won't be fixed in an EOL version. You will have to upgrade at some point anyway.