How to lower brightness (it's too bright)?

Mikescotland

DUDU-Meng it is on lowest driver settings (10) and brightness night is 0 on the slider. It is still too bright as you can see. The pics are absolute minimum I can get.

Mikescotland

Screen driver 10 (can't get lower) and screen brightness 0.
For god sake, Dudu do something with it, in the night it's burning the retinas. Allow people to go less than 10 in the PWM driver. And no, extreme mode doesn't help, still like bright fog on the Dudu screen.
This is the most annoying thing so far. I don't know how people got to the point that screen was actually black with no backlight but it's not the case with 3.6.

JhonnyD

We are saying this for about a year now. But i think they have to build a new display to get this to work.

Mikescotland

JhonnyD no. As far as I can see from the board, it's a mosfet PWM regulator. Changing values in the driver would be sufficient. Currently allows min 10% PWM, I don't see any reason why it wouldn't go down do 2%. At least in the screen I've got, which doesn't experience any black flashes on low PWM.

79Red

I also would like to see reduced screen brightness at night other than using "extreme darkness" because that slider makes the contrast low and difficult to see at night.

I hope this gets resolved because the rest of the unit is fantastic but this is extremely painful to use at night.

DUDU-Meng

79Red Is the effect of the ultra-dark mode not up to your requirements?

Mikescotland

DUDU-Meng for me absolutely not. Contrast is very weak, and all is with "fog". Also, still lights bleeds around and disturbs, as the brightness of the screen isn't lowered, it's just a grey overlay.
For right side steering wheel cars like mine, also when this mode is active, looking from driver side at angle screen has a pink tint (9.5 inch) that is not visible if you look from left angle onto the screen.
Someone said in 3.5 it was possible to turn the brightness to 0 (literally black) and worked as supposed. I can't, driver adjustment stops at 10 and cannot get any lower. Perhaps display driver was altered between the versions? My screen does not flicker or flash when even at 10 in the PWM screen settings.
I've just done over 3000 km partially in the night and had to turn off the screen as on country roads even with that extreme dark overlay light bleeding from screen was distracting ( my settings min 10 in advanced brightness driver settings and 0 for night brightness settings). Too bright!
Besides, when this settings is buried in the menu, when it's just gets dark (sunset) and ILLUM kicks in, you don't see anything, so it's digging in the menu to turn it off and then in the night digging again to turn it on.

79Red

DUDU-Meng No, ultra dark mode does not work well - it reduces contrast but it still has backlight bleed so it is difficult to read and see, especially as the fonts are too small and can't be made larger.

@Mikescotland is correct. It needs much better contrast while in a darker mode.

DUDU-Meng

Mikescotland Previously, it could be set to 0, but some screens have different parameters, and setting it to 0 completely turns off the backlight. However, the touchscreen still works, and it is the same as a black screen. You need to shine a flashlight on the screen to slowly find this setting and adjust the value to greater than 0 to see the screen display.
Therefore, it is not allowed to be lower than 10 to prevent some screens from flickering and to prevent accidental operations from causing a black screen with no backlight. The human eye cannot see the screen content, so it is impossible to continue adjusting the parameters.

NeedMoreLion

DUDU-Meng
This issue is quite bothersome to me whenever I get home in the evening.
My understanding is that adjusting the value below 10 causes display abnormalities, but does not result in any hardware damage.
Would it be possible to implement a system, similar to how Windows handles resolution changes, where after a setting is modified, a confirmation is required, and if not confirmed within 10 seconds, it automatically reverts to the original value?
This would allow users to have this setting option available.

Mikescotland

DUDU-Meng please release a patch of something to let us PWM lower to 1 for instance. On our own responsibility.

DUDU-Meng

NeedMoreLion
Even when using a dark theme at night with the backlight set to the lowest level, is it still too bright?
We will discuss the issue of setting the lowest limit to 10, but I am not sure yet whether we will change it completely.

DUDU-Meng

Mikescotland Currently, there are no relevant patches or plugins available to achieve this. Modifying the code is the only option, but this requires approval through the feature request process before it can be added. There is currently no solution available.

DahTank

Mikescotland

Hey. Try these settings. I hate overly bright screens too and managed to find something that works for me

Pull down from the top of your screen first and reduce the brightness of the head unit from android settings to minimum then turn on night mode on the same page

I use 70% for day brightness settings and 0% for night brightness settings

Minimum brightness power 30. Max brightness power 70

Extreme dark mode
Below 30. Keep it slightly below 30(not lower than 21 to prevent too much “undesirable” effects

Mikescotland

DUDU-Meng please revert it to the 3.5 settings. It's a step backwards, not improvement. It became a safety danger now after change.

lorenbrown

old school, analog fix...
I thro a rag over the display at night..
yeah ... the display is bright at night.

Mikescotland

DahTank my screen even is too bright even much below your levels.

JhonnyD

There is nothing thst will help.
The backlight is to bright.
We need new sort if displays.

Mikescotland

JhonnyD you could bring it literally to zero black in 3.5

JhonnyD

But then there are absolutely no colors anymore.
No actual settings will do anything about it.
The only thing thst really work is, turn off the display.

Mikescotland

JhonnyD no, you could adjust brightness to zero. Blank screen. Without using the overlay "extreme mode". Some people set zero and had problems because they couldn't see anything to bring brightness back. So instead of letting people not to have zero but for instance 1 in the display driver settings, they restricted it to 10 in the 3.6E which is bright as hell.
It could have been solved much better by a dialogue when you select PWM max low value in the menu, Dudu changes it and asks after change if that's fine. But if you don't confirm, reverts to previous value.

Mikescotland

JhonnyD @DUDU-Meng I have measured the backlight for my 9.5 screen. Constant current driver with 19-21V output. PWM @ 390Hz from the MCU in 3.6E is set to minimum 17% duty cycle (it's setting 10 in the advanced brightness control, can't get lower due to DUDU software). I have simulated with ESP32 duty cycle with 390Hz and the screen and driver are happy with just 2-5% duty cycle which resolves any nighttime problems with bright screen. I think DUDU you should really bring back the advanced settings to be possible to lower to 1 (not to 0 as that would prevent people seeing complete darkness).
Now, the flashing black that is encountered in some screens, maybe due to a SY7200 LED driver IC. I can see on the oscilloscope it's 390 Hz PWM while the manufacturer as per their data sheet says min 20kHz PWM should be used. Not sure if you can set the PWM frequency in the driver but something to pass to the dev team.