Bug 462936 - [Android] Krita's UI glitches out right after creating a new document
Summary: [Android] Krita's UI glitches out right after creating a new document
Status: RESOLVED FIXED
Alias: None
Product: krita
Classification: Applications
Component: Usability (other bugs)
Version First Reported In: nightly build (please specify the git hash!)
Platform: Android Android 13.x
: NOR normal
Target Milestone: ---
Assignee: Krita Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-12 03:14 UTC by Tyson Tan
Modified: 2023-01-06 11:20 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tyson Tan 2022-12-12 03:14:46 UTC
On Android, Krita's UI glitches out after creating a new document. The contents in Krita's window would freeze, menu bar tear apart, cursor is not being drawn on screen. Hovering the pen around things does not trigger any reaction. One would assume the app has either crashed or locked up, but it is in fact running fine. Do something that force the screen to refresh -- clicking on menu, changing the device's orientation -- immediately restores the display of the app's UI.

Maybe we need to update Krita's window more aggressively? 

I have also noticed that when Krita is running in the front, even during full-screen, my device will lock and turn off the screen, almost immediately after my S-pen is lifted away from the screen, SOMETIMES. Screen lock time, power settings don't affect this behavior. Maybe it has something to do with this issue too.

Tested on:
Samsung Galaxy Tab S8 with One UI 5.0 (Android 13).
Krita 5.1.2 and latest Krita Next nightlies (5.2.0).
Comment 1 Halla Rempt 2023-01-06 11:20:51 UTC
Fixed in Author: Sharaf Zaman <shzam@sdf.org>
Date:   Fri Dec 23 13:51:11 2022 +0000

    Revert "Disable the touch docker on Android"
    
    This reverts commit 56456f59f898536a470bcf19832788aa8bb0d6bb.
    
    Not having touch docker caused this bug. I don't exactly know the reason
    why this happened in the first place and given the difficulty associated
    with bugs involving events pipeline, I think it is best to leave it in
    the same state as it was before. But maybe fix the touch docker to
    disable or delegate the buggy actions.
    
    BUG:463318
    CCBUG:462848