Hi,
My automatic brightness setting just leaves the brightness exactly on what it was before. E.g If I manually put slider to max, and turn on automatic brightness it stays on max (even if in a dark room), and if I put it minimum and go outside or shine a torch on it, it doesn't go higher at all.
I'm not sure when this first started happening, it always used to, I'm running ARHD 5.1.11 (a ginger-sense rom), with golauncher ex. I can't think what's causing it. Elixir says that the sensor is working (the numbers adjust as I put light on the sensor).
Any ideas would be much appreciated.
Not a direct fix for your problem but I downloaded OnOff Widget Pack. This has a great brightness control. Running Auto Brightness for most situations seems to be a drain on the battery.
Related
Hi,
My automatic brightness was not working properly so i downloaded sensor test. The sensor works fine but it cuts in and out.
It keeps switching from 10/10 to the real value than back to 10/10.
Any ideas on how to fix this?
Was working fine before i installed cyano
Thanks
Bumping this as I have a similar problem.
The sensor doesn't seem to recognise any light values between 10 and 300-350, it either says it's pitch dark or that I'm outdoors (checked with two different light sensor apps). I'm using the stable release of CM7.
It's causing problems with automatic brightness obviously, as I can only adjust the settings to either have a dimmed screen during the day, or have my eyes burnt out when it's actually pitch dark.
Any ideas?
CM7 has settings for auto brightness and it actually works. They're in the CM settings.
I've got a bog stock Desire running 2.2 and according to Sensor Test, the light sensor doesn't work at all!
Sometimes this has happend to me in CM7... but I reset the levels then it was working gud....
http://forum.xda-developers.com/showthread.php?t=1003592
you can check this thread where all the levels are explained in detail for CM7
CM7 has its own brightness levels... but they are somewhat slow to update. I've tried changing their values - but it only helps a bit.
I must say that I was testing it indoors... not outdoors.
I've never been happy with the way the autobrightness works on my phone, and after checking with AndroSensor and the calibration in Total Screen Control, it seems the ambient light sensor doesn't read anything below 160 lux in sense roms, and 320 lux in CM7.
Is there anything that I can do regarding drivers, settings etc. , or is a replacement my only option?
I don't really want to go there, because I paid for a SIM unlock code and everything else is working perfectly, but it annoys me that I have to use workarounds to deal with the brightness, and I always find myself get stuck with an unreadable screen (too dark), when out and about, because I forget to set the brightness higher before leaving.
Can anyone tell me where I can find the relevant files for the ambient light sensor on the Dinc2?
This is where it's at on a Desire, for example:
/sys/devices/i2c-0/0-0066/ls_adc
And what would be a good stock rom to see if it happens with that one, too?
I Honestly just use the quick settings slider to adjust screen brightness
I do, too, but it doesn't do me any good, when I have to use the phone outdoors, and have forgotten to set it to full brightness, before leaving the house!
That happens to me frequently, and the screen is unreadable then, so I can't find the brightness settings.
go to Setting,display.
Well, yes, but if my screen is too dark to see anything, I can't navigate there.
That's why I'm trying to pinpoint the sensor problem, so I can use AutoBrightness.
I've had my One X for a week or so now and seem to be having some issues with the Auto Brightness since upgrading to 1.28.
I am still using stock, un-rooted rom and I leave Auto-brightness on most of the time. Sometimes when my battery might be nearing empty I use a widget called 'Dimmer' which just toggles between whatever the current setting is and the lowest possible brightness (it represents that as 10 out of 255). If you use the normal brightness slider, the lowest value (at least according to 'Dimmer' ) is 30.
Now recently when I unlock my phone, the screen has been constantly dim and the brightness is set to 30, which means that Auto Brightness is NOT on and Dimmer is not on. When I check in the settings, the brightness slider is all the way down and I never set this up.
I used dimmer for about a year before now on my old Desire and it was flawless so I doubt its that, and it seems to work on 1.26 fine.
Just wondering if anyone else had been seeing random brightness drops or Auto Brightness disabling sometimes? If so, are you using a 'Dimmer' like widget?
Thanks,
Tinytom21
I've seen a couple posts about delays with adaptive brightness, but this is a different item. I'm seeing that the adaptive brightness alters the brightness a little too dramatically. In a somewhat dark room (not pitch black) the brightness will be at absolute minimum even when the brightness is about 1/3 up on the slider. In a moderately bright room that same brightness setting will be near maximum.
Does anyone else notice this as an issue? I'm just wondering if it's normal (ie, software calibration issue) or if the brightness sensor might not be seated correctly.
It's normal. Or at least it sounds like it is working the same way mine is. And yes, IMO it is a little too sensitive. The Lux app works beautifully if you want an alternative. Also, the goog is known for tweaking this feature over time with updates.
I've noticed this too. The biggest thing for me is walking down the street at dusk (so not dark out yet) I can't read the screen as it turns it all the way down, then, when I walk under a street light, it turns it all the way up to full! It's one extreme or the other, there seems to be no middle ground.
In other words "adaptive brightness has mind of its own!"
This is why I have always kept this setting off. The brightness just changing on its own always annoyed me.
When it works properly (and it should) for ones uses, it's great, it's automatic, what's not to like? It's a pita to always have to change brightness manually just to see a phone display depending on ambient lighting which varies immensely for many users.
jbdan said:
When it works properly (and it should) for ones uses, it's great, it's automatic, what's not to like? It's a pita to always have to change brightness manually just to see a phone display depending on ambient lighting which varies immensely for many users.
Click to expand...
Click to collapse
I agree. I have it set to maybe around 15-20% (centered over the WiFi symbol below it) and I never need to touch it. Gets dark enough for night driving and bright enough to read outside. Never found it stuck on one or the other when it shouldn't be.
Sent from my Nexus 5X using Tapatalk
If you buy the app Lux you can customize how it adapts your brightness. The free version is good to but you have to use mostly default settings. By default it only adapts brightness when the screen turns on.
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)