Hello Folks.
I have a problem with Windows 8 and my Sony Bravia Television.
when i change my screen, for example from the desktop to a movie, or from youtube small screen to full screen, then it keeps flickering, the television says it is changing mode..
i already tried chaning the resolution and hz...
anyone had this problem with your screens ?
Hi All,
I came to know about PWM on amoled screens and was searching a ROM with support for DC screen dimming / disabling PWM . Any help will be appreciated.
Thanks
Ankit
I just installed an Atoto A6 Pro. For about a day, the brightness adjustments were working. It is set up to dim with the headlights and moving the brightness adjuster worked great. Today, I noticed that the screen would not dim when I turned on my headlights. The LED lights on the buttons would dim, however the screen would not change. I tried manually adjusting the brightness through sliding the slider back and forth and nothing is happening. I have restarted the system a few times and that did not work. I have installed Headunit Reloaded and I am wondering if this is what is causing this issue, but I deleted the app and restarted and the issue still persists. Anyone have any clue how to fix this?
What did the reseller suggest?
marchnz said:
What did the reseller suggest?
Click to expand...
Click to collapse
I contacted ATOTO support and they haven't responded just yet. I bought it directly from Amazon new. I am wondering if it is a software issue because the brightness adjuster doesn't even work.
Hi guys,
So I just recently got a Dasaita PX6 MCPE for my 2014 Honda Accord. The screen is so bright its insane, my dashboard can't even match it at the brightest night setting. Daytime it is good, but I can't dim the display enough for night use. I've contacted Dasaita about it and there response was "put window tint on your radio". The problem is it wouldn't be bright enough for day with window tint on it :/
I'm wondering if anyone has had any success with these units to make the screen brightness at night dimmer. I've tried using apps like Lux but my display is still putting out too much light. I live in the country and am on very dark roads, its tolerable when I hit the city. Right now I have to keep the screen off while driving on my road.
Now naturally, I'm not just posting "how do you fix it": instead I'd like to share what I've done so far and see if anyone else has any ideas:
1) Finding the PWM device in the kernel. Using the ADB root shell I've looked around to find some PWM devices. I figured they must be controlling the display brightness using one of the RK3399 PWM outputs. After a lot of searching, I found a PWM device which somewhere had been labelled as Backlight:
```
$ more pwm
platform/ff420030.pwm, 1 PWM device
pwm-0 (vdd-log ): requested enabled period: 24997 ns duty: 4246 ns polarity: inverse
platform/ff420010.pwm, 1 PWM device
pwm-0 (backlight ): requested enabled period: 24997 ns duty: 0 ns polarity: normal
```
`ff420010.pwm`
I tried sending a new brightness to the device by editing the power file in `/sys/devices/platform/ff420010.pwm/pwm/pwmchip0/power` using `echo "250" > power` but it didn't change anything. Perhaps I'm not editing this file right, but in my experiences in the past this is usually how screen brightness is controlled, via PWM driven off the main processor (for embedded applications of course).
If we can find how this device is driven, (wether its the MCU or CPU) I'm confident we can dim the display. I think the frequency for the PWM is too high, so even though the duty cycle may only be 5%, we get very little range as our eyes are compensating for it. I contacted Dasaita with this information and theory behind it but they don't care (they already have my money of course). This is something I've observed with LED's in the past when I set the PWM frequency too high.
2) My next plan was to modify the actual device driver circuit and add a RC filter so when the device was being given a shorter duty cycle it would start to ground out some of the power, effectively adding more range, as when the duty cycle neared 100% it would be DC and the circuit would no longer pass any power to ground. At this point I was still under the assumption that the backlight was LED, as it is 2020 of course. Upon further inspection I realized that it is not driven by LED, but is a CCFL driven display. I unplugged the harness for the backlight and voltages were above 30v, and you could hear the circuit trying to ignite the bulb. To be extra sure, the measured impedance across the terminals was immeasurable with my equipment. I have very little experience with this kind of florescent so I started messing around and was able to get the device to dim by putting a resistor inline, but the driver was struggling (you could hear it hissing) and I lost all range on the devices dimmer.
My theory is that the display is actually running off the MCU and not from the CPU... even though I can't prove it and it doesn't make sense to do it like that. Its a CCFL so it can't be easily dimmed with hardware modifications that I can do.
If anyone has any input on how to make the display dimmer it would be super appreciated. Normally I would find another solution but this is the only radio I can find for my car that isn't god awful. I'm pretty new to Android, but come from a Linux and embedded systems background so perhaps there is something I'm missing?
Have to tried something a bit simpler like using darker colours on your themes and apps? Most nav apps for example have "day" themes and "night" themes which makes a HUGE difference in glare and brightness.
Yes I have tried that, even with a screen filter app like lux the screen is still too bright. The problem is the display can only limit so much light itself. It just glows so bright.
Good write up and attempts to solve
Assume your device is an MTCD device and thread heading is a typo? (The MCU starts with MTCD, MTCE, or MTCP. If so, head over to the MTCD forums and also take a look at the schematics for the MTCD in my signature.
What you should try:
Connect via ADB (Laptop/PC and unit in the same WiFi network) to your unit and send this command to the unit:
Code:
adb shell settings put system screen_brightness 0
and afterwards
Code:
adb shell settings put system screen_brightness 255
If that works, you should think about using Tasker to get the unit to night view.
...and if it works, there is an alternative to Tasker: Just use the Fcc Car Launcher. There is a widget to get this done dependent on sunrise and sunset.
marchnz said:
Good write up and attempts to solve
Assume your device is an MTCD device and thread heading is a typo? (The MCU starts with MTCD, MTCE, or MTCP. If so, head over to the MTCD forums and also take a look at the schematics for the MTCD in my signature.
Click to expand...
Click to collapse
Haha yes you are right it is a typo. It was a long day. It is a MTCE MCU. I’ll see what I can dig up, I find it really difficult to navigate XDA and find anything lol
rigattoni said:
What you should try:
Connect via ADB (Laptop/PC and unit in the same WiFi network) to your unit and send this command to the unit:
Code:
adb shell settings put system screen_brightness 0
and afterwards
Code:
adb shell settings put system screen_brightness 255
If that works, you should think about using Tasker to get the unit to night view.
...and if it works, there is an alternative to Tasker: Just use the Fcc Car Launcher. There is a widget to get this done dependent on sunrise and sunset.
Click to expand...
Click to collapse
Good point! I did try actually to set the screen brightness using the settings command in ADB root mode but got no response on the screen which is why I believe it’s controlled by the MCU and not android. The brightness dials on the system are just addons. I didn’t write this part up another one of my mistakes lol
I have used a widget for that too, my screen does change based on brightness automatically (day/night mode) with my headlights fortunately but it doesn’t dim enough is all.
Hi Guys,
I have the Ticwatch Pro 3 and it's great.
But I have a little problem. I love Always on Display (AOD) and in some situations I also like to set the display not to go into dimming mode via StayLit Wear with the "indefinitely" mode. This also worked great with my Huawei Watch 2, even when I put my arm down on the home screen, even if you can see the time normally. If I set the "indefinitely" mode with the StayLit Wear app on the Ticwatch Pro 3, it works that the Ticwatch Pro 3 always remains active, but only if, for example, I have the settings open or I am in the app selection and if an app is open even if I put my arm down. It also works on the home screen when I have my arm up all the time and look at the clock. But as soon as I'm on the homescreen and I turn my arm away or take it down, the watch always goes into dimming mode, despite the "indefinitely" mode of StayLit Wear.
That could actually only be due to the fact that Mobvoi has specified this in some system file for Wear OS, right?
Can I possibly edit the specific system file, or do something via ADB Shell so that I can set it so that the Ticwatch Pro 3 does not go into dimming mode as soon as I turn the arm away or take it down so that it is only time-controlled again is when the display goes into dimming mode and is not forced to dim when I turn my arm away or take it down?
Possibly for better understanding:
So it works with my Huawei Watch 2.
However, with the Huawei it is also the case that the change to the dimming mode does not happen automatically when I turn my arm away or take it down, but it is purely based on the set time of seconds until the display in the AOD is dimmed.
With the Ticwatch, however, this is set somewhere in such a way that the display not only goes into dimming mode based on the set seconds, but also presumably controlled by a sensor, from a certain angle regardless of the set seconds, immediately goes into dimming mode.
And I want to get rid of the sensor, that the dimming mode is forced and my question is whether someone knows where I can do that.
Thank you in advance for your feedback.