General JP2601 AppSupport Tweaks

General
1

Hi everyone, this is my first post here on the forum!

I wanted to share some of the patches and tweaks I’m using to get a better experience within Android apps on my new Jolla Phone 2026

Restore transition_animation_scale setting

This fixes some janky animations within some apps such as Discord, where instead of animating as intended, items would immediately snap to their position when released.
This also fixed interaction with the map in Google Maps, making it usable.

This is done by adding the following init script into /etc/appsupport.conf.d/init/start-post-hook.d:

#!/bin/sh
appsupport-attach /system/bin/sh -c "settings put global transition_animation_scale 1"

Note: This specific key is explicitly set to 0 by AppSupport (in /opt/appsupport/init/start-post-hook.d/50-setup.sh), thus this modification may break some other stuff.

Rounded corner patch

This patchmanager patch I made overlays masks for the top corners right below the notch area when an Android app is in foreground, making it match the bottom radii for a less jarring experience. This is purely for aesthetic purposes.

Status bar patch

This other patch shows the Sailfish OS status bar in the notch area when an Android app is in foreground. This fills the blank space left there while giving useful information. It’s also properly animated and fits in pretty well.

If you have any feedback for the patches, feel free to reply and I’ll consider making updates :slight_smile:

I’ll update this post should I make more patches or find other tricks!

14 Likes
2

Looks nice. The notch patch looks a bit goofy on light ambience though.

1 Like
3

Canonically this should be added under /etc/appsupport.conf.d

According to the functions in /opt/appsupport/init/appsupport-common that directory will be traversed much in the same manner as /opt/appsupport.

Following that logic I put the script in /etc/appsupport.conf.d/init/start-post-hook.d/ and also made it executable. I also added an informative message hoping it shows up during startup.

#!/bin/sh
settings put global reduce_motion 0
echo "Reduce animations"

journalctl -f | grep -w Reduce
Aug 19 18:57:41 Xperia10III appsupport-init[21064]: Reduce animations

But:

appsupport-attach settings get global reduce_motion
null

Hmm. setting the value to 1 in the script doesn’t help either, and judging from other start-post-hook scripts you need to prepend appsupport-attach:

#!/bin/sh
appsupport-attach settings put global reduce_motion 0
echo "Reduce animations"

appsupport-attach settings get global reduce_motion
0

Better. But are you sure 0 is the desired value, not 1? Or that reduce_motion is even the right key? A web search on that reveals nothing to me.

2 Likes
4

Oh I forgot to check that during testing haha

I just uploaded a new version that fixes that if you want to give it a try!

5

tl;dr: You’re right, that was useless and I’ll edit the original post to correct it.

I came to the reduce_motion in a collection of various animation-related settings. After trying a bunch of them I thought that was the correct one as it had solved my issue after restarting the app, but indeed it was one of the other keys I had modified while testing.
The correct way was to run settings put global transition_animation_scale 1, which may actually not be desirable as in /opt/appsupport/init/start-post-hook.d/50-setup.sh that key is explicitly set to 0; note: my goal was to enable animations, not reduce them

Your note about needing to appsupport-attach is right, so my script did nothing either way

6

Tested it, looks perfect!

One thing you may also want to fix is to mark the patches as compatible with .17, as they’re only currently marked compatible with the .16 update. I had to disable the version checking in Patch Manager.

1 Like
7

Interesting. Thoughts:

  • Which Android version does this refer to
  • What are the default value for all the keys that aren’t set or in other words, how can one list all possible keys with their defaults, not just those that have been explicitely defined (the latter is what settings list global will do)
8

Which Android version does this refer to

Not entirely sure, that pdf came up after a bunch of failed attempts so I was just trying stuff out of desperation, without any methodology haha

how can one list all possible keys with their defaults

I don’t think there is a way, as far as I know there’s no standard for those (and no fixed schema, as new keys can be added by setting them)

9

you may also want to fix is to mark the patches as compatible with .17

Yup, aware of that issue
I think patchmanager’s web catalog website has to add support for each version, as .17 is not yet present in the multi-choice form on there, and it seems I can’t manually specify one that’s not already there.

As soon as they update it, I’ll mark it compatible