Joined
·
277 Posts
Doesn't seem to work with ssx2.1 but it was working with miui."droidxchat said:
Light Sensor Values Information (Updated 8/22/2011)
41 - 60 of 71 Posts
Joined
·
68 Posts
I'm not sure if I caused this or it was the script but all of sudden my sensor reads -1. It doesn't change the brightness anymore.
Sent from my DROIDX using Tapatalk
Sent from my DROIDX using Tapatalk
Joined
·
277 Posts
I had this issue when I updated miui to the latest version. I had to wipe data/cache to fix it. I restored everything but system settings with miui backup."insuusvenerati said:
Joined
·
68 Posts
@droidxchat All of them . I have the 3g booster and the hard to kill launcher.
Edit: oh my bad. These script were from a different thread. The data wipe worked.
Sent from my DROIDX using Tapatalk
Edit: oh my bad. These script were from a different thread. The data wipe worked.
Sent from my DROIDX using Tapatalk
Joined
·
16 Posts
I don't know if anyone knows it, but if you hold menu and volume up it makes your screen brighter, it voids the auto levels until your screen shuts off again. does on my phone anyway.
Joined
·
11 Posts
This is not entirely true. The settings can still mean something valuable, and this thread can be useful.droidxchat said:
AFAIK, the advanced auto brightness settings in CM74DX are the only way to consistently override the default minimum brightness value and the default dim value. There may be a settings file adjustment somewhere that lowers the minimum, but I don't know enough to find it and I've never found an app that could do it successfully.
So there are two benefits. 1) You use these settings to set the "dim" level, which is effective whether you have auto brightness turned on or not. More importantly, 2) read below...
In my setup, I use rather complex profiles, rules and conditions in the paid version of the Setting Profiles app. I have several profiles, many of which activate automatically based on location, docking state, time, etc. The homescreen widget allows me one- or two-click access to manually switch to a profile as needed, too.
As you've shown, there are only 4 levels of auto-brightness available on the DX, and for me, they aren't very useful. The sensor reads 10 everywhere from pitch black to soft shadows in a lighted room, and reads 100 in almost any other indoor light, including a brightly-lit room. So in practicality there are only 3 available brightness modes - dark/shadows, indoor light, and outdoor light. The profiles I have set up are actually better at auto-brightness than auto-brightness is! Like, I have a level set for when I'm at work, at home, in my car, etc. I have 5 or 6 different static brightness levels set in different profiles, and most of those profiles set themsleves automatically based on conditions that end up being more useful to me than the light sensor.
Anyway, here's the point: whenever I try to set a static brightness level below 20, even when creating a profile in the Setting Profiles app, it defaults back to 20. This is WAY too bright for one of my most important profiles - the one I use for bed and movie theaters. I need a screen as dark as possible, one that isn't even visible in lighted areas but that still allows me some quick, basic interfacing as needed. I'm guessing this is the point of some of the lower custom levels in your option 2. So, for me, this "bed" profile is the only one that I've set to turn on "automatic brightness" in the stock Android settings. This prompts my CM7 custom levels kick in.
Well, custom level, anyway. 2 levels, 0 - 3400 and 3401 - infinity, both of them 2, 0. No filter, no hysteresis, allow decrease. The custom levels won't let you set a brightness lower than your dim level (sort of makes sense, because then dim wouldn't be dim), so I had to set dim to 2 first before I could set it this way. But I don't want my dim at 2, because in any light I can't tell the difference between dim and off. So after setting the custom level, I go back and put dim at 4 or 5 or so.
Effectively, I'm not using any "auto" brightness at all. I'm enabling auto-brightness with a single custom level as a hack to enable a static brightness level of 2, because it's the only way I think I can do that. If there's an easier way, I'd like to know, but this works great. I just have to remember not to allow the screen to dim, becuase dim is actually brighter at this level. But even that is a big help, because occassionally I find the bed/theater profile still active after I'm in the light, and I can't see the screen at all. Waiting a few seconds for it to "dim" is my failsafe so I can see enough to switch the profile. Another option I've tried is setting 100 to also be 2 , 0, but then setting 3600 and 8600 to be 20 or 50 or so. But I feel better knowing that I've hard-set it to 2, so right now I'm on the one level.
Joined
·
88 Posts
Thanks OP this is much snappier IMO on my X, auto-brightness lagged trying to find the "g-spot" for a stable light sensor haha. With this guide and values it is more responsive. Plus not to mention you really dumb ed it down so I could understand it. Still sorta new with this whole scene.
Very useful.
I want to add that the CM7 Auto-Dim-40-100 toggle appears to be using fixed values of 26 (Dim - 10%), 102 (40%), and approximately 224 ("100%" -- maybe closer to 230, but definitely NOT 255.).
As it's been pointed out, the screen can't keep up with either 3600 or 8600, so there's almost no value in differentiating between them.
I used these values:
0-99 16 255
100-3599 80 255
3600-8599 224 0
8600+ 255 0
This way my dimmest auto is actually lower than "dim" on the widget.
I found the 100-3599 level often not bright enough to light the keys, so I left backlighting on.
Any kind of daylight goes to the widget's version of "max," but in direct sunlight it actually pushes the display to 255 ("true" 100%).
This way I know that auto is both the dimmest and brightest that I have, and the widget's only useful for overriding in conditions where it might actually make a difference.
For such a sophisticated device, this would seem to be a surprisingly primitive system. But the display's actually quite good in anything less than bright daylight.
EDIT:
I spent some time with this, and found that 16 was just too dim for many of the conditions below 100. Same with the second one -- it has to hold a long way to make it to 3600. So I changed the first two levels:
0-99 42 255
100-3599 96 255
3600-8599 224 0
8600+ 255 0
I figure 96 is the level it'll spend most time at, and that's not going to seem overly bright in office space. We'll see.
I want to add that the CM7 Auto-Dim-40-100 toggle appears to be using fixed values of 26 (Dim - 10%), 102 (40%), and approximately 224 ("100%" -- maybe closer to 230, but definitely NOT 255.).
As it's been pointed out, the screen can't keep up with either 3600 or 8600, so there's almost no value in differentiating between them.
I used these values:
0-99 16 255
100-3599 80 255
3600-8599 224 0
8600+ 255 0
This way my dimmest auto is actually lower than "dim" on the widget.
I found the 100-3599 level often not bright enough to light the keys, so I left backlighting on.
Any kind of daylight goes to the widget's version of "max," but in direct sunlight it actually pushes the display to 255 ("true" 100%).
This way I know that auto is both the dimmest and brightest that I have, and the widget's only useful for overriding in conditions where it might actually make a difference.
For such a sophisticated device, this would seem to be a surprisingly primitive system. But the display's actually quite good in anything less than bright daylight.
EDIT:
I spent some time with this, and found that 16 was just too dim for many of the conditions below 100. Same with the second one -- it has to hold a long way to make it to 3600. So I changed the first two levels:
0-99 42 255
100-3599 96 255
3600-8599 224 0
8600+ 255 0
I figure 96 is the level it'll spend most time at, and that's not going to seem overly bright in office space. We'll see.
Joined
·
52 Posts
Anyone else have issues with a stuck sensor? Mine sticks at high settings, so if I'm outside in bright sunlight, it'll stay at 8600 when I come back in, and the only way to reset the sensor is to reboot.
Joined
·
10 Posts
Is "Allow light decrease" checked? If it is not, the result will be exactly as you describe.Wuffpack99 said:
Joined
·
52 Posts
Yes it is. It's an intermittent problem, so I know the settings are usually right. But there are times when it just sticks.cygnusloop said:
Joined
·
277 Posts
I've had this issue also. Never found a permanent fix but rather than rebooting you should be able to turn auto brightness off and back on to get it unstuck."Wuffpack99 said:
Joined
·
51 Posts
Mine sort of does the same. When indoors it stays stuck at 0 unless it's close to the light source. As a result my screen is almost always at 6 (changed it from 2 suggested in OP).Wuffpack99 said:
Edit: lol now it's stuck at 100 and wont adjust down. Sensor, at least on my device, doesn't seem to react well, if at all to changes in lighting conditions.
Joined
·
51 Posts
Settings??droidxchat said:
41 - 60 of 71 Posts
