Database Users

Screen auto turns off. Quadcore R16 1.6G

I have an unidentified Head unit (this one http://www.preston-i-c-e.co.uk/vw-006-oem.php) and I've obviously changed something with buttons and now the screen turns itself off after a few seconds.
Brightness is set on auto, and to keep awake. Sat Nav stays lit all time, but any other app turns screen off.
Attached is system details. I'd love to know more about it!

contact the guys you bought it from?
i think there's a setting for screen auto off time, but you have to look for it. my unit(s) don't have this.
try display settings, under brightness, or factory settings somewhere...

zerozoneice said:
contact the guys you bought it from?
i think there's a setting for screen auto off time, but you have to look for it. my unit(s) don't have this.
try display settings, under brightness, or factory settings somewhere...
Click to expand...
Click to collapse
Thanks, I actually flashed iqnavi on it instead, that worked!

Auto dim the screen when the headlights are on

I am wondering if it's possible to have the screen dim to let's say 25% when the headlights are switched on?
Thank you.

Sassokee said:
I am wondering if it's possible to have the screen dim to let's say 25% when the headlights are switched on?
Thank you.
Click to expand...
Click to collapse
Yes..the autodim...is automatic
If you have the illum wire correctly plugged (by canbus or by direct connection from your car to the headunit) you have to enable the option on factory settings ("other" tab) under the option "brightness"
Enviado desde mi SM-G950F mediante Tapatalk

For my head unit that only illuminates the physical buttons of the unit but the screen is still bright.
Sent from my SM-N910F using Tapatalk

This autodim feature is enabled on my 2018 Mistubishi Outlander Android Auto and pretty much renders the screen and GPS navigation useless during the day with headlights on, and I'm looking for a way to turn it off. It's required in my state to have headlights on during several driving conditions during the day, which dims the screen to the point of being effectively unviewable, especially with navigation apps, which also switch to night-mode display. So I have GPS map displaying black roads on dark black background in a dim screen that is a no-kidding-this-is-honestly-unusable level of ridiculous.

OhmEye1 said:
This autodim feature is enabled on my 2018 Mistubishi Outlander Android Auto and pretty much renders the screen and GPS navigation useless during the day with headlights on, and I'm looking for a way to turn it off. It's required in my state to have headlights on during several driving conditions during the day, which dims the screen to the point of being effectively unviewable, especially with navigation apps, which also switch to night-mode display. So I have GPS map displaying black roads on dark black background in a dim screen that is a no-kidding-this-is-honestly-unusable level of ridiculous.
Click to expand...
Click to collapse
Any solution to this ? My 2018 Outlander GT same issue basically unreadable. I'm thinking of replacing it with a better display all together if possible. I can't stand a display on any device that isn't bright enough.

Issue with brightness night mode (witson unit)

Hi,
I have Chevrolet sonic and I buy witson unit direct fit with canbus, px5 4gb ram 32 rom.
The unit have 2 brightness settings, default and night mode.
the night mode suppose to activate when car lights are on, on my can I have automatic lights system and the automatic light is activated, when I turn on the car druing sunny day the drl (day running lights) are on, and the android thinks that lights are on so the night mode is activated al the time..
if I shutdown the lights on the car completely, then the android brightness is OK.
I can't find any solution for that issue, I do needs drl by law in Israel druing winter, but I need lower brightness from the android at night too.
Anyone had such issue and found a solution? Maybe there is some app thsr can change brightness by time of day?
Thanks!

Anyone?

dalet11 said:
Anyone?
Click to expand...
Click to collapse
Yes...
https://play.google.com/store/apps/details?id=com.microntek.romavaleev.backlightautolevel

Try going into the factory setting menu, password 126 and on the last page there is a setting for brightness trigger method - I can't remember the exact name but have a look. It worked for me on my Eonon MTCE PX5

Dimming PX6 MCPE Display

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.

Dasaita HU Brightness control stopped working

Hi,
The issue has appeared only in last few days.
- HU is running fine but always appears to be on the lowest brightness setting. It's usable by night but too dim for sunlight.
- If I try to adjust brightness, the UI shows the slider but it has no effect on the screen brightness.
- I've looked for and disabled any and all "auto brightness" settings which could be interfering.
- The unit can also auto-dim the screen when my headlights are on. I can tell it's getting this signal because the buttons on the unit light up when my headlights are on but it has no effect on screen brightness.
That's about all. Wondering if anyone has any ideas what could be going on? This is my 2nd Android Head Unit in as many years so I'm getting unbelievably frustrated.
Thanks.