Sizing the width (pixels) of a dashboard - Layout card

Configuration
1

Hi there,
I am building a wall tablet (Lenovo M10 plus) whic has if My data is correct a width of 1900 x 1200 pixels.
I am configuring my Dashboard with layout-card and mentions there is a total width of 1920 pixels, but then all cards are not filling in the width but I need to scroll left and right ?!?

views:
  - title: Home
    type: custom:grid-layout
    icon: mdi:home
    layout:
      grid-template-columns: 500px 500px 920px
    badges: []
    cards:
      - type: gauge
        entity: sensor.netpower
      - type: gauge
        entity: sensor.netproduction
      - type: gauge
        entity: sensor.hp_officejet_pro_9020_series_black_cartridge_2
      - type: gauge
        entity: sensor.hp_officejet_pro_9020_series_cyan_cartridge_2
      - show_current: true
        show_forecast: true
        type: weather-forecast
        entity: weather.maison
        forecast_type: daily
        name: AccuWeather

Instead, when I set my width around 1200 pixels, then all seems to fit.
When resolution says 1900 x 1200 pixels, 1900 is well the width being in landscape right ??

2

Still struggling with this …

Why a dashboard of 1340 pixels :

grid-template-columns: 50px 370px 500px 420px

Seems to entirely fit my dashboard on my Lenovo M10 plus tablet with reolution 1920 x 1200 ???

3

Does this tablet have sort of ‘retina’ display? Then physical resolution is double of the logical one. If larger than that it could scale down. Can you try to size your dashboard for resolution below 960x600 and see what portion of screen is taken?

4

I have no clue … it is a lenovo M10 plus if it can help.
I think it is 1920 with but dashboard completely filled with like 1320 pixels :

1000021635
10000216351920×1440 135 KB

Tablet settins “about” tells 2000×1200 …

5

Mml really strange … see with an online resolution tester :

1000021636
10000216361920×1440 179 KB

6

From Android developers page:

Avoid using pixels to define distances or sizes. Defining dimensions with pixels is a problem because different screens have different pixel densities, so the same number of pixels corresponds to different physical sizes on different devices.

To preserve the visible size of your UI on screens with different densities, design your UI using density-independent pixels (dp) as your unit of measurement. One dp is a virtual pixel unit that’s roughly equal to one pixel on a medium-density screen (160 dpi, or the “baseline” density). Android translates this value to the appropriate number of real pixels for each other density.

So it seems that your tablet is using 1/1.5 scaling (physical pixel to density independent pixel), which explains difference in physical specification (2000x1200) and what tester shows (1334x800).
So if you wan to scale your cards to not take full screen real estate, you should use, as guidance available resolution of 1334x800 pixels.

7

I also found this in the tablet settings, whuch seem to explain why I am not at 2000 px, but at 1334 :

1000021656
10000216561920×1440 136 KB

“Display size”, seels to be not at 100% …

If I set it to 100, then tablet screen passes from :

1000021659
10000216591920×1440 121 KB

To

1000021658
10000216581920×1440 60.9 KB

Where we can clearly see resolution increased.