Weird overscan bug

Product support
1

Using the pi3 Raspbian image.

When I set the overscan values to 0 in device configuration, the values found in the pi after startup is actually 48. So I have to assume 0 equals to 48 as starting point to calculate the actual overscan value.
Tried on two monitors with the same result.

Is this a device or raspbian problem?

2

Hello, how do you define the config variables? Can you confirm they’re named like RESIN_HOST_CONFIG_overscan_left, RESIN_HOST_CONFIG_overscan_right, etc.?

BTW, you can manually inspect the config.txt if you insert the SD card in your computer and open config.txt from the boot partition.