Android 15 (API 35) / Qt 6.9.1: SafeArea=0 at startup in plain Window; content under notch/nav until TextField focus

[J.Hilk]

I actually react on the onCompleted

Component.onCompleted: {
        applyNewMargins()
    }

to fetch the safe area margins

function applyNewMargins(){
        if(isMobile){
            var map =           safeMargins.getSafeAreaMargins(mainWindow)
            safeMarginLeft =    map["left"] * 2 / 3
            safeMarginRight =   map["right"] * 2 / 3
            safeMarginTop =     map["top"] * 2 / 3
            safeMarginBottom =  map["bottom"] * 2 / 3
        }
}

from my c++ backend. Haven't noticed any new timing issues. But this was ma solution way back in the day where the margins weren't available on application start. Don't see any flickering either

[ekkescorner]

thx for the info.
I want to use the Qt 6.9 SafeArea. works well on iOS and hopefully with 6.9.2 on Android, too - so ATM I'll wait for 6.9.2

[ekkescorner]

BTW: if you want to opt-out from Android-35 edge-to-edge
you have to add styles.xml and add in Manifest... activity... android:theme="@style/NormalTheme"
see the details here:
https://codereview.qt-project.org/c/qt/qtbase/+/630376

[BTSTOnline]

@ekkescorner said in Android 15 (API 35) / Qt 6.9.1: SafeArea=0 at startup in plain Window; content under notch/nav until TextField focus:

BTW: if you want to opt-out from Android-35 edge-to-edge
you have to add styles.xml and add in Manifest... activity... android:theme="@style/NormalTheme"
see the details here:
https://codereview.qt-project.org/c/qt/qtbase/+/630376

This worked for me...Thanks!

[ekkescorner]

@BTSTOnline cool :)

[garycho]

@Pann Tapping into a a TextField , brings up the virtual keyboard - this is what corrects the safeArea . Programmatically bring up the virtual keyboard to achieves the same effect.

[garycho]

I figured out a temporarily workaround by bringing up the virtual keyboard, which initializes the SafeArea margins correctly, and hide the keyboard immediately. At your constructor add this

connect(QGuiApplication::inputMethod(),SIGNAL(visibleChanged()),this,SLOT(closeKeyboard()));
QGuiApplication::inputMethod()->show();

Then create a slot

void MyApp::closeKeyboard()
{
    if (QGuiApplication::inputMethod()->isVisible())
    {
        QGuiApplication::inputMethod()->hide();
        disconnect(QGuiApplication::inputMethod(),SIGNAL(visibleChanged()),this,SLOT(closeKeyboard()));
    }
}

On activation of the virtual keyboard, the visibleChanged() signal will trigger the closeKeyboard() slot. This hides the keyboard and disconnects the signal/slot. You may get a glimpse of keyboard animating in/out... I find this to be a reliable workaround and easiest to undo , once this bug is fixed.

[ekkescorner]

Qt 6.9.3 should fix this and is scheduled for today - or coming soon ;-)

current state of Bugs around Safe Areas:

6.9.3:

• fixes getting SafeArea values at startup for Android 9 to 16, Android SplitScreen should also work
• (https://bugreports.qt.io/browse/QTBUG-135808)
• Android NavigationBar in SwipeViews and more fixed in 6.9.3 and 6.10.1, but NOT in 6.10.0 !
• (https://bugreports.qt.io/browse/QTBUG-139690)
• fixes Android orientation -flicker and half-screen-glitches
  (https://bugreports.qt.io/browse/QTBUG-132718)

6.10.0:

• same as 6.9.3, BUT:
• Android NavigationBar in SwipeViews and more fixed in 6.9.3 and 6.10.1, but NOT in 6.10.0 !
• (https://bugreports.qt.io/browse/QTBUG-139690)

6.10.1:

• Android problems with color scheme fixed
• (https://bugreports.qt.io/browse/QTBUG-137248)
• Android NavigationBar in SwipeViews and more fixed in 6.9.3 and 6.10.1, but NOT in 6.10.0 !
• (https://bugreports.qt.io/browse/QTBUG-139690)

[garycho]

@ekkescorner Thanks for the information Looking forward to the fix. I've been spending too much time, finding ways around this bug.

[ekkescorner]

and 6.9.3 is here :) https://www.qt.io/blog/qt-6.9.3-released

edit: just did first tests with 6.9.3 on Android: now SafeArea values are there from start, also NavigationBar much better now :)

[ekkescorner]

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

I've been spending too much time, finding ways around this bug

yep. always much time spending to report and follow all the bugreports and writing test applications like https://github.com/ekke/ekkesTestStatusBar
will update my test app next days with experiences from 6.9.3

[garycho]

@ekkescorner Excellent. Just compiled with 6.9.3 and the SafeArea margin is set correctly on start . The navigation bar is now grey instead of black.

[ekkescorner]

@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 :)