Bug 509649 - Wrong UI positioning
Summary: Wrong UI positioning
Status: REPORTED
Alias: None
Product: kasts
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.08.1
Platform: Android Other
: NOR normal
Target Milestone: ---
Assignee: bart
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-09-18 20:18 UTC by Michal Breškovec
Modified: 2026-01-28 10:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
Screenshot with wrong buttons positioning on main screen. (124.35 KB, image/png)
2025-09-18 20:18 UTC, Michal Breškovec
Details
Wrong UI positioning on play screen. (2.57 MB, image/png)
2025-09-18 20:21 UTC, Michal Breškovec
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Breškovec 2025-09-18 20:18:59 UTC
Created attachment 185061 [details]
Screenshot with wrong buttons positioning on main screen.

SUMMARY
After upgrade Kasts UI positioning is wrong, see attached screenshots. 

STEPS TO REPRODUCE
1. Run Kasts.
2. Play any podcast.

OBSERVED RESULT
1. Bottom icons are too high on main screen.
2. Buttons are too low on play screen, so the are oberlayed by system buttons.

EXPECTED RESULT
UI have right position to be able use buttons.

SOFTWARE/OS VERSIONS
Android 15 with One UI 7.0
Samsung Galaxy S25 Ultra
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2

ADDITIONAL INFORMATION
Comment 1 Michal Breškovec 2025-09-18 20:21:20 UTC
Created attachment 185062 [details]
Wrong UI positioning on play screen.
Comment 2 Michal Breškovec 2025-10-01 06:36:48 UTC
Upgraded to Kasts 25.08.2, GUI issues persists. 

Mobile phone upgraded to Android 16 with One UI 8.0 meantime.
Comment 3 bart 2026-01-25 21:16:54 UTC
I think I've seen a report for this before. It's got to do with the virtual keyboard. For some reason the app is trying to reserve space for the keyboard, even when it's not showing. This will of course garble the display.

I don't really know what triggers it. I haven't even been able to reproduce it myself. I do know that it's not related to anything the app has control over. This is functionality offered by the toolkit(s): qt, kde frameworks.
Comment 4 Michal Breškovec 2026-01-28 10:15:38 UTC
(In reply to bart from comment #3)
> I think I've seen a report for this before. It's got to do with the virtual
> keyboard. For some reason the app is trying to reserve space for the
> keyboard, even when it's not showing. This will of course garble the display.
> 
> I don't really know what triggers it. I haven't even been able to reproduce
> it myself. I do know that it's not related to anything the app has control
> over. This is functionality offered by the toolkit(s): qt, kde frameworks.

I think you are absolutely right, it looks like it expecting that keyboard will be shown.
Question is why keyboard is not shown as well.