I've never seen filtered values lower than 33 on my Gratia (even in the very dark room). Is it OK, or sensor fault?
I think you not understand how that working in our aria. Aria hardware sensor have only 10 fixed steps (0, 0x21, 0x4D, 0xDC, 0x134, 0x18D, 0x1E5, 0x2BA, 0x35C, 0x3FF) and nothing more! In kernel its defined same! To understand, you can watch at top of screen raw sensor value (filtered/raw) that is filtered directly from hardware!
In android settings: there is 4 rows: lower, upper, screen, buttons. Lower and upper mean "range" for screen and buttons: for example 0 to 32 giving light level66 for screen and level 255 to buttons, 33 to 76 giving 96 for screen and 255 for buttons... etc
You need to know. Buttons have only 2 levels:0 is "buttons light off" and 255 in "buttons light on" !!!
But for screen its diferent. Screen have range from 0 to 255... so you can adjust screen lights for your needs!
You can change only screen and buttons levels for your needs, but do not change first row (lower) because these raw values is in kernel (confirmed raw values from aria sensor!)
So for example: if filtered/raw value from hardware (look at top of screen to get idea) is 33 (that will set your screen level light to 96 and turn your buttons light on), if you not like screen level 96 and you no want your buttons to be "on" when raw value is 33, you can adjust these in 3rd and 4rd row for your needs. For example you can increase or decrease light level for screen to for example 111 (or 255 or whatever) and if you want buttons off, set buttons value to 0...
Understand now?
Ok, i understand the reason for the values. but, if there are two ranges that share the same limit, then won't that make one, like the first row, never get used?
Sent from my Liberty using XDA
If I understand you... there no two ranges that share the same limit (for example if raw filtered value is 33, than will be used range 33 to 77, so display value and buton key value will be used from column 3 and 4). You never will see raw/filtered values for example 36, or 47...etc, these values from sensor have always step 33,77,...etc, so do not edit first column. Expose your phone over light and you will see what I mean. I don't know why Cyanogen opened first column for write/read option instead of read only like seccond column, but first column I set/is set default, same as a defined in kernel so you do not touch these values in first column, only you can experiment with 3rd and 4rd column)
Hey guys, if im on a call and my screen goes off, it wont turn back on regardless of what button I hit. anyone else have this problem? or a solution?
So, what you're saying is the first row is useless. Right? Because the lowest raw value the phone can hit is 33. So it will display values from the second row (33,76).
Sorry for the confusion.
did you replace the digitizer? sounds like a problem with the proximity sensor.
@Munjeni: Could you please post the MD5 signature for the new update? thx.
Hey guys, if im on a call and my screen goes off, it wont turn back on regardless of what button I hit. anyone else have this problem? or a solution?
Battery drain is an inherent problem with Android. This ROM isn't any better or worse than the rest. When we improve how batteries work we will improve battery life.
No, some devices have null (0) value, some devices have 33 as a first...