Disable automatic dim when car lights are switched on - MTCB Android Head Units Q&A

Hi,
I have recently bought an RK3188 Unit (KLD6) and am happily running Malayks ROM on it. However, when I switch on the lights of the car, the unit lowers the brightness of the screen. As I have to use lights during day in some parts of Europe, I would like to manage the brightness of the screen by an app. If it is a bright day and I have to drive with lights switched on, I can barely read the screen anymore. So is there any way to prevent this behavior? I know that I could just remove the lights wire, but I would like to have the LEDs to be switched on or off with the lights.

In case of Mtcd devices such option is in Factory Settings (password to enter it is 126). You can check it in case of your unit. I had the same problem - in my country it is mandatory to use head lights 24h per day so I lost screen visibility during the day.

Thanks for your answer. However, I wasn't able to find any option to turn off the brightness control. Do you remember how it was labeled/called? I found the option to turn on the LEDs permanently and also brightness control for reverse driving, but no option for the brightness with lights switched on.
Thanks in advance.

I found the solution, which obviously was too obvious to be found beforehand by myseld. :/ The normal system settings menu provides a tab 'Display', in which the brightness can be set as 'auto', 'light', and 'Dark', whereas 'Auto' means that the brightness depends on the status of the car lights, 'Light' means bright and 'Dark' means lower brightness.

Related

Keep softkey lights on?

I know this has probably been mentioned 1000 times but why doesn't anyone make an app that will let you manually turn the soft key lights on or off on a non-rooted dinc.
So many clock apps, etc have the option of forcing the softkey lights off, prove that it could be easily done since those apps are available for non-rooted dincs.
If anyone has a solution (other than the black e-tape one) please let me know. You can't see the buttons worth a crap unless the room is very well lit. in other words useless at night in the house with normal lighting. Yes I know I could cover the sensor with my thumb but there has to be a solution lurking out there somewhere.
thanks in advance.... johncal
There is. It's called Screen Filter. You can use it to do really low brightness (like when you use your phone in bed, not what she said ) and also manually turn softkey lights on or off. Actually, I'm not sure about forcing on, but it does turn off softkey lights for as long as you want.
Seriously, why do you want to turn them off? I sorta memorized the position of the softkeys.
I find the softkeys way too bright, so I've always used apps to turn them off in the past, never on.
In addition to trying Screen Filter as recommended above, give LEDs Hack a try. It's primarily designed to turn them off, but maybe the "ON" button will work... I'm really not sure.
For what it's worth, CM7 lets you control the softkeys. Specifically, if you go into the auto-brightness levels, you can turn them on/off for a given brightness level. From my experience, it seems that these settings stick even when you're not using auto-brightness. I turned off soft-keys at all the levels, and they stay off even when I'm not in auto-brightness.
With CM7, I no longer have to use Screen Filter for turning off the softkeys, but I do still use it to dim the screen very low.
I really want to keep the softkeys on not off. I'm also running a stock non-rooted rom. Phone's fine for me the way it is except that I just want the ability to keep the softkey lights on. I guess I'm just surprised that no one has come up with a solution for that.
Screen filter is for turning them off and unfortunately, LED hack is for rooted phones. Thanks for the suggestions though.
byrong said:
I find the softkeys way too bright, so I've always used apps to turn them off in the past, never on.
In addition to trying Screen Filter as recommended above, give LEDs Hack a try. It's primarily designed to turn them off, but maybe the "ON" button will work... I'm really not sure.
For what it's worth, CM7 lets you control the softkeys. Specifically, if you go into the auto-brightness levels, you can turn them on/off for a given brightness level. From my experience, it seems that these settings stick even when you're not using auto-brightness. I turned off soft-keys at all the levels, and they stay off even when I'm not in auto-brightness.
With CM7, I no longer have to use Screen Filter for turning off the softkeys, but I do still use it to dim the screen very low.
Click to expand...
Click to collapse
Where are the softkey settings in CM7? I looked under the autobrightness settings place but couldn't find anything.
Nightly 37 btw.
-CM7 ADR6300
dpwhitty11 said:
Where are the softkey settings in CM7? I looked under the autobrightness settings place but couldn't find anything.
Click to expand...
Click to collapse
Menu > Settings > CM Settings > Display > Automatic Backlight > Edit other levels
Lower / Upper = readings from the light sensor
Screen = the screen brightness you want based on the lower/upper light sensor values
Buttons = whether or not you want the softkeys on. Unfortunately, they cannot be dimmed (hardware limitations, from what I've read), so 255=on and 0=off
In the default configuration, for example, if the sensor value is 0-199, the screen will be set to brightness 25 and the softkeys will be turned on. If the sensor value is >399, notice that the softkeys turn off (button value changes to 0). If you want the buttons on all the time, set all button values as 255. If you're like me, and you hate the softkey lights, set all button values to 0.
For what it's worth, CM7 lets you control the softkeys. Specifically, if you go into the auto-brightness levels, you can turn them on/off for a given brightness level. From my experience, it seems that these settings stick even when you're not using auto-brightness. I turned off soft-keys at all the levels, and they stay off even when I'm not in auto-brightness.
Click to expand...
Click to collapse
Byrong, youre the man. Did not know about this. Bye bye softkey lights. Thanks!

When going into sleep, screen dims, but then lights back up

I've had the watch since tuesday, but am having a problem with it: when going into ambient, screen visibly dims, but ends up lighting back up... Tried several brightness settings, and it does it with all, except maximum brightness (ie 5).
So basically, when going into ambient, the screen progressively dims, but then brights up and ends up settling at the ambient brightness level it should reach when brightness is set at 5.
Have tried several watch faces, and factory resetting, but it doesn't change a thing.
Anyone experiences that?
Also tried setting brightness with Autowear: only the awake brightness is affected- the ambient brightness always stays the same...
For what is worth, it's particularly obvious with the Dandy default watch face, as it's the same in awake and ambient mode (minus the seconds hand). Set this one up, set brightness at 1, get in a low lit room, and then, I for one see the ambient brightness get dimmer, then get visibly brighter and settle there... Not that obvious in a bright room, but blatant in a dark one.
Also, I realized the watch reports the Android Wear version is 1.3.0.2176821 while it's the latest 1.3.0.2284253 on the phone. Same as, the watch reports the Google Play Services version is 8.1.20 (2283517-534) while it is 8.1.15 (2250156230) on the phone. Don't know if it matters...
Just turn on theatre mode when charging.
acp5533 said:
Just turn on theatre mode when charging.
Click to expand...
Click to collapse
That, I already do. But the sun sets long before I go to bed, and lay the watch on the charger. And it's as soon as the sun sets that the watch is much too bright to me in ambient mode...

Screen keeps auto dimming even when set to 100% - Eonon 5.1.1

Hi everybody, I recently updated my Eonon Androud HU to 5.1.1 using the first 5.1.1 custom ROM listed here. The DSA Prerooted ROM. Thus far it's been functional and fits my needs over the Malaysk ROM. However this ROM has some sort issue with it automatically dimming the screen to low, even though it's been set to 100%. When sliding the brightness slider to 100, the screen will still dim on its own, regardless of the adjustment still being set at 100%. I have gone through all the settings and found nothing that can help me. The display submenu only displays the option "Brightness". Which is just the standard slider to adjust the brightness. There is no option for Auto, Low, Bright, etc.
I've downloaded some apps to control the brightness to see if that would help, but something on this ROM is overriding any brightness apps from working. I even tried installing an xposedMTC module as it had an automatic dimming option, hoping to deactivate it completely but no luck. The way my car works is my headlights have an automatic DRL. When I turn my DRL's off, the headunit seems to activate it's full brightness, until I turn the automatic light control back on which turns on my DRL's, then the screen goes dim again. It's as if the headunit is going by the whole "Oh your headlights are on, it must be dark outside. Let me adjust the brightness to low for you".
Any help would be appreciated. I hope it's a simple fix. Thank you!
brian117 said:
Hi everybody, I recently updated my Eonon Androud HU to 5.1.1 using the first 5.1.1 custom ROM listed here. The DSA Prerooted ROM. Thus far it's been functional and fits my needs over the Malaysk ROM. However this ROM has some sort issue with it automatically dimming the screen to low, even though it's been set to 100%. When sliding the brightness slider to 100, the screen will still dim on its own, regardless of the adjustment still being set at 100%. I have gone through all the settings and found nothing that can help me. The display submenu only displays the option "Brightness". Which is just the standard slider to adjust the brightness. There is no option for Auto, Low, Bright, etc.
I've downloaded some apps to control the brightness to see if that would help, but something on this ROM is overriding any brightness apps from working. I even tried installing an xposedMTC module as it had an automatic dimming option, hoping to deactivate it completely but no luck. The way my car works is my headlights have an automatic DRL. When I turn my DRL's off, the headunit seems to activate it's full brightness, until I turn the automatic light control back on which turns on my DRL's, then the screen goes dim again. It's as if the headunit is going by the whole "Oh your headlights are on, it must be dark outside. Let me adjust the brightness to low for you".
Any help would be appreciated. I hope it's a simple fix. Thank you!
Click to expand...
Click to collapse
That's one of the main differences between Malaysk and DSA. DSA told me look out the window and figure it's night time. Secondly he told me to go to max at least two or even three times in a row. It will then STAY 100% bright till you reboot.
halloj said:
That's one of the main differences between Malaysk and DSA. DSA told me look out the window and figure it's night time. Secondly he told me to go to max at least two or even three times in a row. It will then STAY 100% bright till you reboot.
Click to expand...
Click to collapse
Whoa, thanks for the quick reply and useful information. Is there absolutely no way to bypass having to do that method? As that would be a chore doing it multiple times after exiting and entering my car multiple times a day. Maybe a simple build.prop edit possibly? Just naming ideas.
There is... Mtc manager has settings in it for brightness settings due to time. You can turn it off there. This didn't work for me so I went another route with changing some file. Its all detailed in the thread as to how.
miffymiffy said:
There is... Mtc manager has settings in it for brightness settings due to time. You can turn it off there. This didn't work for me so I went another route with changing some file. Its all detailed in the thread as to how.
Click to expand...
Click to collapse
You could disable brightness control entirely or just alter the brightness levels.
It's in file /system/etc/install-recovery.sh - at its end, comment out all 14 lines after comment line reading "#Brightness control (last, always)", in order to disable the algorithm.
OR, change line reading "nb=5 ### Night Brightness ###" to a different value for the night brightness (nb), eventually equal to day brightness (db, on next line).
Use a root explorer, or edit a copy of file on PC (with notepad+ if on Windows) and copy it back - with a root explorer or manually, if you can. File mode: 0755, owner & group: root:root.
If script /system/etc/install-recovery.sh gets "damaged", you must reinstall the firmware, but with NO wipe all, so fairly quickly and no loss of settings and apps.
Editing of script could also be done with @devilsoft app (with a name I can't recall).
brian117 said:
Hi everybody, I recently updated my Eonon Androud HU to 5.1.1 using the first 5.1.1 custom ROM listed here. The DSA Prerooted ROM. Thus far it's been functional and fits my needs over the Malaysk ROM. However this ROM has some sort issue with it automatically dimming the screen to low, even though it's been set to 100%. When sliding the brightness slider to 100, the screen will still dim on its own, regardless of the adjustment still being set at 100%. I have gone through all the settings and found nothing that can help me. The display submenu only displays the option "Brightness". Which is just the standard slider to adjust the brightness. There is no option for Auto, Low, Bright, etc.
I've downloaded some apps to control the brightness to see if that would help, but something on this ROM is overriding any brightness apps from working. I even tried installing an xposedMTC module as it had an automatic dimming option, hoping to deactivate it completely but no luck. The way my car works is my headlights have an automatic DRL. When I turn my DRL's off, the headunit seems to activate it's full brightness, until I turn the automatic light control back on which turns on my DRL's, then the screen goes dim again. It's as if the headunit is going by the whole "Oh your headlights are on, it must be dark outside. Let me adjust the brightness to low for you".
Any help would be appreciated. I hope it's a simple fix. Thank you!
Click to expand...
Click to collapse
Hi @brian117 !
In fact, there is a simple fix I found lately.
You need to enter factory settings first.
Go to SETTINGS -> Factory settings -> enter code: m123456
When you're there, go to last page, and tick the "Key light" option.
Now press "Apply" and "Exit". Confirm reboot.
It worked with me - now the screen has full brightness regardless of the car lights on or off (in Poland we need to have the lights on whole day, as well). Now you can use a software dimming, like MTC to auto dimm the screen according to actual day time. I did this. Works like a charm! (I set dimming after sunset to 75% brightness)

Screen not waking up in low brightness

Good day
Had a problem, searched but nothing found. Nexus 7 car instal. When dimming the screen to auto brightness on zero (or tasker setting 0 brightness) screen is properly dimmed, perfect for night driving. But after locking the screen and then unlocking the screen backlight doesn't turn on. I can still operate touchscreen (hear music, taps etc) but nothing on the screen. Resetting by holding the power button brings it back, with brightness set to zero and backlight on.
Any solutions?

Broken touchscreen - change brightness?

Hello all,
My baby son managed to damage the flat cable going to touchscreen and ambient light sensor (don't ask how, watch was on my hand) and now touchscreen and light sensor are not working.
Brightness is on low setting and I can't change it.
Is there any way to change the brightness via phone?
I would like to set it to higher level to be able to see anything during the day, until I get a new screen.
I've tried "Watch Display Brightness" app but it's not working. I think that issue is that brightness is not set to manual mode and that's why this app gives no results.
Thanks!

Categories

Resources