Mobile and Embedded

@garycho said in Android 15 (API 35) / Qt 6.9.1: SafeArea=0 at startup in plain Window; content under notch/nav until TextField focus: SafeArea margin is set correctly on start great to hear that it also works for you :)

you need link Qt6::QuickEffectsPrivate libraries.

6.9.3 will come out next week https://wiki.qt.io/Qt_6.9_Release

See also https://www.qt.io/blog/android-15-and-16-support

See also https://www.qt.io/blog/android-15-and-16-support

See also https://www.qt.io/blog/android-15-and-16-support

Hi @Anand-Sethu , As mentioned above, the upcoming "content projection" feature in Qt for Android Automotive "streams" the content to a remote consumer, but it's a video stream. The purpose of the feature is not exactly what you are looking for, as injecting user touch input from your Yokto system back to Android is a different story that should be evaluated separately (by using AccessibilityService to inject touch input + Qt Content Projection).

@Aldebaran there was some discussion at https://discord.com/channels/457523061650882570/1017293621063602186/1412677580439687248 also see https://bugreports.qt.io/browse/QTBUG-131514 Fix Version/s: 6.5.10, 6.8.6, 6.9.3, 6.10.0, 6.11.0 FF if you're using OpenSSL, please watch https://github.com/KDAB/android_openssl/issues/68 ekke

makeQCurrent(); eglDisplay_ = eglGetCurrentDisplay(); eglCtx_ = eglGetCurrentContext(); if (eglDisplay_ == EGL_NO_DISPLAY || eglCtx_ == EGL_NO_CONTEXT) { fprintf(stderr, "[Core] Cannot get native EGL resources form qt.\n"); } doneQCurrent(); ———————————————— 版权声明：本文为CSDN博主「SweerItTer」的原创文章，遵循CC 4.0 BY-SA版权协议，转载请附上原文出处链接及本声明。 原文链接：https://blog.csdn.net/qq_40087136/article/details/151912946

yes I am trying to solve

It may have been a while, but I have the same problem with a waveshare display: Exact half the real size (1280x800 here) is reported in Qt. Has a solution been found in the meantime? Greetings lowPerformer

Hello, i'm currently exploring the whole fileDialog/picking files things and i'm not sure i get all that's been said above. On IPadOS, i've never had to request explicit permissions to ask users for a file through a file request, either through native or QtWidget. In both cases i can easily show a file dialog and then through NSURL, do a startAccessingSecurityScopedResource on it, giving read access on that file, being the way it worked for the last couple of years, maybe they changed that recently ? Anyhow, the access scope method still works today for me. Now, when doing the same thing in QML, i get the same url string from the QML's fileDialog, but when going through NSURL, it gives me a weird absolutePath comming from /Bundle/myApp.app/<theOriginalURL>, not sure what's going on. Both QWidgets and QML test apps have the same Info.plist, so not sure how else permissions should be given, if any is required. If anyone knows how QML and QWidgets are different regarding this, it would be immense help.

I added the links to the image in the description above but adding under again :- https://gist.github.com/wahabshah/a36cd8524e098a58e3909cc5c3592436#jpeg-progressive https://gist.github.com/wahabshah/a36cd8524e098a58e3909cc5c3592436#jpeg-baseline yeah sure i added that as a bug to be checked by the Qt Team :- https://bugreports.qt.io/browse/QTBUG-140124

@jsulm So from what you write I assume you would recommend to give a try with the Qt builds for Android via the online installer. I will have a look at that, and report the outcome here.