DSCS9 and display oversize issue

[Carlo_Venturi]

Hello,
I’ve troubles displaying content like weather or clock because their dimension exceed region assigned and so is not fully showed.
The issues it happen also with default layout as you can see in the screenshot below were
text is not centered into the framework and not fully readable.
I’ve already checked both Display (small) and Text size (small).
If I put other setup the issue is worst.
Thank you for your help.

General Information
Date: 2022-12-01 23:18:15
Version: 3
Code Version: 308 - 2ba095a (2022-11-20 01:16:53)
Content Management System: http://192.168.1.124/xmds.php (tcp://cms.example.org:9505 - 2022-11-01 00:00:00 - 1 month, 23 hours, 18 minutes, 15 seconds and 193 milliseconds ago)
LAN IP: 192.168.1.63
Last Heartbeat: 4 minutes, 13 seconds and 397 milliseconds ago.
Storage Selected: Internal Storage. 99.0%
Display Name: DSCS9-DSCS9
Licenced: true (full)
Registered: true
Current Layout: Normal: 1
Screen Size: 1920 x 1080
Memory Limit: 512 MB
Memory Allocation: 61 MB
Image Cache Hit Rate: 0.89
Screen Shot Request Interval: 0
Use Surface View for Video Rendering?: true
Video Engine in use: ExoPlayer
Use multiple video decoders: true
Number of Stats ready to send: 0 - 2021-12-01 22:35:17
Number of Logs ready to send: 6511 - 2022-12-01 23:18:15

CMS Status
Register: Registered. Checked at 2022-12-01 23:18:14
Schedule: Up to date
Required Files (Inside Download Window): Up to date. 56/56
Queued Network Connections - F: 0 / N: 1. HTTP: 3 / Idle: 3
Number of Concurrent Failed XMDS Connections: 0

Schedule Status
All layouts (* = not scheduled): 1, 61, 1 (D),
Scheduled Layouts: 1, 61,
Valid Layouts: 1, 61, 1,
Invalid Layouts:
Next Schedule Update: 2022-12-01 23:18:17

Faults

Last 5 log messages
Method: XFA:XmdsService. Message: onHandleIntent: XMDS intent received at 2022-12-01T23:18:14.614+01:00. There are 2 HTTP client connections in the pool and 2 idle…
Method: XFA:LayoutManager. Message: startNextLayout from outside…
Method: XFA:LayoutManager. Message: startNextLayout: setting next layout false, next layout is already set.
Method: XFA:LayoutManager. Message: startNextLayout: Proceed with starting the next Layout. instanceId: 6696, layoutId: 1.
Method: XFA:LayoutManager. Message: startNextLayout: Stopping current Layout instanceId: 9441, layoutId: 61 .

Install Service Status
Update Window: 00:00 - 00:00
Version Information from CMS:

[Carlo_Venturi]

Hello,
so finally I found a solution.
I’ve enabled “Developer options” menu entering in Android System settings and clicking several time on “Build number”.
Entering in “Developer options” there is a set named “Smallest width” that was set to 799 (~800).
Having a look on internet about its meaning, I found that it should represent the quantity of pixel related to the short side of your device.
Because DSCS9 is connected to a full HD TV, I’ve changed the setup to 1080.
So now it works and all the content inside layout regions are properly showed.
Bye.

[Carlo_Venturi]

Hello again,
because I’m struggling with this topic for months I were so happy to had solved the issue for DSCS9 that I’ve immediately “exhumed” an Android device (X96 S400 - Android 10) bought from China few months ago that had the same issues.
I went directly in “Developer options” and with my regret that “Smallest width” option were not present.
I didn’t lost my confidence and so I’m starting googling and found that using ADB (Android Debug Bridge) is possible to change WM (Windows Manager) parameters: specifically I’ve changed two of them “size” and “density”: it’s not needed to root the device.
With size I’ve been able to fit the background into the whole screen, with the “density” I’ve solved the issue in topic: content in each region fitting the area and not are cut.
I hope it will help someone.