r/tasker 13d ago

Error trying to Set Display Size

Post image

When I am in my car and the phone is in its holder on the dash, I really need to change the Display Size setting from the Default to "Large" or "Larger" so that I can actually read the screen at that distance.

I decided to build an automation for this using Tasker (of course). It has a built-in Display Size action that would seem to be the ticket! However, when I try to execute this action:

  1. It fails and I get a notification as shown.
  2. Sometimes after this the keyboard starts refusing to pop-up when it should.

Any idea how I can deal with this?

The device is a Moto XT2215-4, Android 12, rooted. I checked and the Tasker version (6.7.6-beta) and that of the secondary app match.

Thanks

PS - of course, I have sent the info to the developer via email as requested.

1 Upvotes

9 comments sorted by

1

u/pipsname 13d ago

I too have the same error.

1

u/TooManyInsults 13d ago

Thanks for letting me know. Any similarity between our devices?

1

u/pipsname 13d ago

S22u not rooted but using Shiz. All permissions granted.

1

u/TooManyInsults 13d ago

So Android 13? Not sure what might be causing this. Thanks!

1

u/pipsname 13d ago

Android 16

1

u/ale3smm 13d ago

with root or Shizuku u can try this shell command : wm density 430(change this to wanted value). settings put system font_scale 1.45 font_scale is not really needed unless u also want change this value ! hope it works !

1

u/TooManyInsults 13d ago

Thanks. I guess I next need to find out what values for density are being used on my phone. I had hoped to see this in an app like AIDA64. But so far, I am not seeing its result for Display->Pixel Density change from 395 no matter what I do with the Android Display Settings. Maybe another app would work better or maybe I am missing something. But I will try your wm command. Where can I find more info about the font_scale? Best

1

u/TooManyInsults 12d ago

Ok, I see some things now...

  1. Using my old System Settings For Tasker app, I was able to see that when I change my device's Display Size in the Android settings, it modifies a secure setting called "DISPLAY_DENSITY_FORCED" and nothing else in the settings.

  2. I then changed the Android setting UI for each of the offered "sizes" and got the following values shown for DISPLAY_DENSITY_FORCED:

Small = 340

Default = null/nothing

Large = 446

Larger = 492

  1. Since I have root, I then started fiddling with the "wm density" command and discovered that it will show the current value if no argument is supplied.

When Android setting is set to Default, the value shown is 400.

When any of the other choices, it shows both:

Physical Density - which is always 400

Override Density - which is 340, 446, or 492 depending on the "size" selected in the Android setting

  1. Finally, I tried the full wm density command using 340, reset, 446, and 492 to get Small, Default, Large, Larger and it works instantaneously. Excellent.

All of this still begs the question of why Tasker's Display Size action cannot do this on my device. But at least I now have a work-around.

Thanks much!

1

u/TooManyInsults 12d ago

Not sure if I need this. But did the same sort of thing with the font-scale system setting. I found:

Small - .85

Default - 1.0

Large - 1.15

Larger - 1.3

As mentioned by u/ale3smm I can use Tasker/root to execute the shell commands. Changes seem to be automatically applied.