KDE Android applications: disable animations

Help
,
1

I use KDE Itinerary 24.08.1 installed via the KDE Android Release Builds F-Droid channel. Is there any way to disable or accelerate the transition animations? On my wayland system setting Units.longDuration=0 and Units.shortDuration=0 via ~/.config/plasmarc mostly gets me there.

2

@mimo1, you can set the animation scale AOSP-wide, just like you can in kcm_workspace:

      1. com.android.settings.Settings$ColorAndMotionActivity

      2. Remove animations

        This method obviously isn’t very useful unless you want to remove them and easily restore them to the default later.

      1. com.android.settings.Settings$DevelopmentSettingsDashboardActivity

        • Window animation scale

        • Transition animation scale

        • Animator duration scale

      This method is still GUI-based, but lets you set them to custom (albeit solely sane) values. They’re incremented integrally.

    1. #!/usr/bin/env sh
speed = 0.25

adb shell

      • settings put global window_animation_scale $speed

      • settings put global transition_animation_scale $speed

      • settings put global animator_duration_scale $speed

    [1]

If these don’t affect KDE’s Kirigami applications, I’ll file a bug for it.

  1. xdaforums.com/t/animations-set-scale-set-to-25.4365695/#post-85987489 ↩︎

3

Disabling animations in ColorAndMotionActivity does not remove all animations. For example, the Departure/Arrival button in Plan Trip, the side menu, or settings screens are still animated.

1 Like
4

@mimo1, those’ll be bugs that someone shall need to report at bugs.kde.org. Are you willing to? If not, provide a screenshot and application version, and I shall:

Is it solely those things that aren’t affected — other animations in the same applications aren’t?

5

Toggling the option in the accessibility menu and restarting the application, I don’t see a difference. The application version is KDE Itinerary 24.12.3 (556bc32) tested on GrapheneOS 15. I’ve attached a screenshot to indicate the menu in question. Thanks for offering to file this bug report, I’m a bit overwhelmed with the number of different accounts and platforms used by the KDE project.

5b858a82
5b858a82720×1600 65.9 KB

1 Like
6

@mimo1, that’s understandable. Luckily, most of those platforms exist for solely developers’ usage. That includes Phabricator and GitLab. For us mere users, this forum exists to discuss problems (et cetera), and Bugzilla exists to formally file and track them.

7

This reproduces on every control exposed via the undermentioned:

  1. AOSP [1]

    versionName= applicationId=
    25.03.70 org.kde.neochat
    24.12.3 org.kde.itinerary
    25.03.70 org.kde.elisa

  2. Windows

    ProductID       : 9pb5md7zh8tl
PackageFullName : KDEe.V.Elisa_22.401.1150.0_x64__7vt06qxq7ptv8

    InstallLocation: "file:///$Env:SystemDrive/Program%20Files/WindowsApps/KDEe.V.Elisa_22.401.1150.0_x64__7vt06qxq7ptv8"

    See superuser.com/revisions/1884748/2 for reproduction steps.

Consequently, I’ll consider it to be a bug with Kirigami itself. I’ll post the report when I’ve filed it, although that’ll take some time due to the amount of affected platforms.

Environment

As goes the Bugzilla template:

SOFTWARE/OS VERSIONS

Windows: Affected
	WindowsBuildLabEx: 26100.1.amd64fre.ge_release.240331-1435
	WindowsCurrentVersion: 6.3
	WindowsEditionId: Professional
	WindowsVersion: 2009
	OsBuildNumber: 26120
macOS: Unknown
Linux/KDE Plasma: Unknown
Android: Affected
	ro.build.version.release: 15

  1. cdn.kde.org/android/fdroid/repo ↩︎

8

Finally reported to bugs.kde.org/show_bug.cgi?id=501702#c1.

I’d advise that you try PMOS with Plasma Mobile if you really need this, but you’ll have to ascertain the solution to the undermentioned first: