balena-dash - incorrect screen size reported by chrominium

Hi,

We have several apps configured - all using the same config (envs). Checked both envs and --config - they are the same.

We build the same code (same folder), deploy to each app. Even run on same device (switching device between apps).

When starting WPE/chrominium it sends “–window-size=480x800” (which is correct) in both cases.

When we look at the screen size reported by chrome it reports:
in one app: windows size 479 799
in another app: windows size 460 780

Chrome itself is reporting
in one app: id=1 rootWebArea FOCUSABLE (0, 0)-(479, 799)
in the other app: id=1 rootWebArea FOCUSABLE (0, 0)-(460, 780)

So, same device, same code, same config/envs, different balena apps. Both built on same machine. We tried to build with --nocache just to make sure both are built from scratch.

envs:
10 ROTATE_DISPLAY left
11 WINDOW_SIZE 480,800

envs --config:
36 BALENA_HOST_CONFIG_dtoverlay rpi-ft5406,touchscreen-swapped-x-y=1,touchscreen-inverted-y=1
35 BALENA_HOST_CONFIG_gpu_mem 128

Any ideas?!

Thank you!

Is the display the same for both devices? If you were to swap the displays over, does the problem also transfer over to the other device?

Considering that the software seems to be exactly the same, perhaps we should try to eliminate the chance of it being a hardware issue

Were you able to try swapping the screens or get this resolved Rani?

Rcooke, Dtischler,

The issue is on the same device, same software, different balena app.

We are now using cloud balena but still have some devices we still need to support on open balena. Some of the apps in our open balena setup are seeing different display resolutions (missing 20 pixels on horizontal and vertical) vs other apps.

Both apps are built on the same code base and same server, and both run on the EXACT same device. The only difference is the app. Also, as far as I can tell the envs and envs --config look the same.

Any idea what we might be missing?

Thank you.

I am wondering what happens if you physically swap the screens, just to see if for some reason there is a slight hardware failure or even firmware revision or small difference between the screens themselves.

It’s the same device with the same screen.

Only thing we change is the app (balena device move --app .

The apps are built on the same machine (same source code), run on the same device, and as far as we can tell the envs (both with and without --config) are the same.

This is why we’re confused as to why one would have a different resolution (20 pixels HxD missing) between the two apps.

That is very strange, I certainly have not heard of anything like this before. If you move the device back from balenaCloud to OpenBalena, do the 20 pixels come back to life?