Keyboard issue when trying to change the server

[PatrikMizera]

In the latest version 2025.7.0. when you try to change the server in the log in menu, the keyboard covers the screen and you can not see what you are typing. The issue is present when using Gboard as well.

Samsung A56

https://github.com/user-attachments/assets/42c14a21-ddc0-473f-add8-5ac536eaa258

[Withalion]

@IvaKuklica could you please try to replicate this issue on our samsung.

[kaustuvpokharel]

Hmm, it likely because the softkeyboard was changed abit since qt6.1 like here said in the forum; https://forum.qt.io/topic/157124/qt-6-7-1-and-qt-6-6-1-android-softkeyboard-handling?_=1763231228613

I guess the same working screen now getting covered by the keyboard instead of being resized or panned could be the same changes qt made around 6.7 to how it integrates with Android window insets and soft-keyboard handling Also, In our Android port we dont set android:windowSoftInputMode on MMActivity, so Android falls back to the default stateUnspecified or adjustUnspecified. But KDE recommends explicitly using it here in the documentation https://develop.kde.org/docs/packaging/android/porting_applications/basic/#:~:text=android%3AwindowSoftInputMode%3D%22adjustResize%22

It could be if included:

<activity
    ..
    android:windowSoftInputMode="stateHidden|adjustResize">

(or stateHidden|adjustPan if we prefer panning over resizing) This is in line with what the Android docs recommend for scrollable content and what many Qt/Android examples use. http://yatmanwong.medium.com/android-how-to-pan-the-page-up-more-25fc5c542a97

On the QML side, the project doesnt seem to use Qt keyboard geometry APIs (such as Qt.inputMethod.keyboardRectangle or Window.softKeyboardHandling) to adjust layout, the only usage I noticed is a Connections handler that calls Qt.inputMethod.commit() on visibleChanged, which only commits pre-edit text and doesnt touch the UI. So at the moment we are seem to be relying entirely on the platform’s default handling, but I believe the manifest change alone should already restore the expected behaviour

[IvaKuklica]

Hi @Withalion - I replicated this issue on our Samsung Galaxy A53/Android 15 and the keyboard did not cover the field for changing the server. Please, see attachment below:

However, I already describe a similar issue in a comment in the open issue https://github.com/MerginMaps/mobile/issues/3380

Screenrecord: Samsung Galaxy A53/Android 15:

https://github.com/user-attachments/assets/d0e9c367-2f08-4f87-ba68-bd86561c3b44

[Withalion]

@kaustuvpokharel thanks for the dive in!

@IvaKuklica thanks for testing it out, looks like the bug is still floating around...

[MF-Aichinger]

https://github.com/user-attachments/assets/b250535f-33d5-4ba5-ad58-ed5580703872

@tomasMizera: On the Samsung A56, we have the problem that the keyboard overlaps the text field in the project, so you don't know what you're typing. This makes the normal work a little bit difficult for us.

[tomasMizera]

Hi @MF-Aichinger, let me add that to the development queue. Sorry for the trouble!

[gabriel-bolbotina]

I tried to replicate the same behaviour on two devices:

• on Samsung S10e/ Android 12

https://github.com/user-attachments/assets/0f472ea4-48c5-49f2-ab31-2edbda5bfaa0

• on Samsung S21/ Android 15

https://github.com/user-attachments/assets/77749124-3845-477c-add6-b13fb8bae240

The issue did not occur with the current master build. However, I will investigate further to check if it is a device-specific bug.

[MF-Aichinger]

It seems to be device-specific. I tried it on other devices and everything worked fine. The only problem is that we have 10 of these in use :/

I also reset the keyboard to default and tested Gboard. The problem persists.

[MF-Aichinger]

Samsung A34 as well.

https://github.com/user-attachments/assets/06760509-b1d3-42b0-8bd0-b177a69b5094 https://github.com/user-attachments/assets/65d0a9a0-2648-4922-b7d0-8174b602dad9 https://github.com/user-attachments/assets/a76b9398-e194-44c2-90a9-5dc4d7b9d933