4.5.0.18 - XA2 - Android display size is not saved after restarting Android support

Bug Reports
#1

REPRODUCIBILITY: 100%
OS VERSION: 4.5.0.18
HARDWARE: Xperia XA2
UI LANGUAGE: German
REGRESSION: Yes

DESCRIPTION:

When opening the Android settings via Terminal and run command

apkd-launcher com.android.settings

you can select “Display” and “Advanced”. Then you can find “Display size”. When changing the display size it will always keep the naming “default” but the size can actually be changed. When I stop android support and restart it my previous selection/change of the display size is reset. If have to reselect/change the display size every time android support is started.
In the previous Sailfish OS version the change of display size was saved when starting the android support again.
Interestingly when I do the change the setting for “Font size” which is in the same menu the change is saved even after restarting android support.

PRECONDITIONS:

Sailfish OS 4.5.0.16 or 4.5.0.18, running android support and and changing the value for “Display size”

STEPS TO REPRODUCE:

  1. Call up Android settings via terminal and

apkd-launcher com.android.settings

  1. Change “Display size” setting
  2. Stop and restart Android support

EXPECTED RESULT:

I expect that the “Display size” setting is save even when restarting android support as it was in Sailfish OS versions < 4.5.0.x and as it still works for e.g. “Font size”

ACTUAL RESULT:

The setting for “Display size” is lost after every stop/restart of Android support.

MODIFICATIONS:

ADDITIONAL INFORMATION:

MircoG is installed but that souldn’t be an issue as it was working in Sailfish OS version < 4.5.0.x as well.

2 Likes
#2

Anyone got the chance to look into that issue?

It is annoying to manually adjust the display size after every (re-) start of Android support…
In the newest release 4.5.0.21 it is still the same behaviour

#3

I doubt it, because the bug report hasn’t been submitted, there’s no tracked tag, and in summertime everything is slower.

#4

By opening the appsupport shell (with appsupport-attach in devel-su) one can observe that the setting changes value of density, here I toggled it by going one left from default and back several times:

# wm density
Physical density: 384
# wm density
Physical density: 436
# wm density
Physical density: 370
# wm density
Physical density: 370
# wm density
Physical density: 426
# wm density
Physical density: 362

the density seems to be set cumulatively wrong, not in set steps. (unless this is expected in Android)

After a reboot the density value is at 480, on Sony XA2.

Setting the density via shell (for example wm density 380) works correctly and the display is scaled, but the menu still says that “Display Size” is default and the density is reset when appsupport is restarted (whether on reboot or manually).

One can run the command without entering the adb shell like so: devel-su appsupport-attach wm density 400. Note that it needs to be run as root.

I actually found a way to set this automatically when appsupport launches:

aliendalvik.service runs /usr/libexec/appsupport/alien-post-startup.sh after startup, so just put a new line in it with the command: appsupport-attach wm density 400

Now this probably gets overridden on update, so a systemd service would be better. I tried to create a new systemd unit that would run when appsupport is started but I did not get it working because I havent really messed with systemd.

1 Like
#5

The same annoying thing in xperia 10iii and ii. This issue is not bad as the lockscreen password that is broken in android support but it is very annoying to set the size each time the support is restarted.
Is there any chance somebody to check those issues…

#6

Hi Okxa, after updating to Sailfish OS verion 4.6.0.13 your mentioned file alien-post-startup.sh is no longer in the directory you described.
Any idea how and where to implement your workaround in 4.6.0.13?

#7

It’s moved to /opt/appsupport/init and the file renamed as appsupport-start-post.
I’m not 100% sure that its the same file, but I have already added the density command to it and works perfectly.

#8

Thanks! It works for me as well.
Happy that I do not need to change it manually after every Android Support (re-)start anymore!

1 Like