• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

[Verizon] [ROM][4.0.4] AOKP ICS B40/M6/Mods (7/8)

jbdan said:
Don't know about color settings I like mine just the way they are ;)

About the auto-brightness. The best way, because it will vary according to your liking, is to play with it throughout the day in different lighting and different situations. I'm very accustomed to it from CM days with the Inc. For now I've settled on this:

- Light sensor filter = enabled, window length 10s, reset threshold 400lux, sample interval 1s.

- Light levels = use custom check, screen dim level 20 default, allow light decrease check (I like it to lower automatically as well) and decrease hysteresis 50%

Here is my Edit other levels screen settings:

31ebf906.png


As for what all those terms mean there is a killer thread/post on XDA that explains it all very well and concisely. Problem is I can't find it atm. It's buried deep within!

Here is what I believe them to mean:

If you have auto brightness enabled and then go to the "Edit Other Levels" screen, you'll see in the top left corner filtered/raw. When you have the filter enabled, essentially what it does is slow down (filter) the abrupt changes that take place in the ambient light sensor to allow for smoother ramping (both up and down if you've enabled "allow light decrease").

The parameters under the "Light Sensor Filter" control this "filter".

Window length = how long the 'filtered' value remains in the vicinity of the 'raw' value. Lower = it will follow the 'raw' value closer and not have as smooth of ramping.

Reset Threshold = if your inside in a dark room and you walk outside into the sun, instead of ramping up slowly like the filter makes happen, this sudden burst of light resets the filter and it jumps up in the vicinity of the 'raw' value therefore brightening your screen much quicker like you would need it to. I use 400 lux because it's the lowest value therefore it jumps up quickly when I enter bright ambient light

Sample interval = self explanatory really. How often the sensor looks at the ambient light in order to make the changes it needs to make.

Allow light decrease = allows brightness to ramp down also

Screen dim level = don't really know here, but my guess is if you choose 20 then it will decrease 20 points at a time when lowering brightness.

Decrease hysteresis = reduces flicker when decreasing brightness

This is all what I think it means please don't take it as FACT :D
Click to expand...


Thanks so much!!!
 
jbdan said:
That is exactly right! Good to see you haven't seen you much, probably because I'm so busy lately :)
Click to expand...

You have been busy (and missed) and I wasn't around a lot last week cause I was furiously working on a wedding album for my friend. So I hope we see you around more!
 
Mr Patriot I have modified my 'Window Length' setting to 5s for a fluid, but yet speedier ramp up and down in brightness levels.
 
jbdan said:
Those are very nice results so far. Betting you that will change every day (maybe every 1/2 day even) I've never been able to repeat consistent battery drain days unless it's at night and I airplane mode it while sleeping....that, to me, is the most accurate/consistent way to see what kind of idle drain one can achieve.

I've stopped monitoring battery life, but was pleasantly surprised to see my CM9 w/ stock kernel has 70 minutes screen ontime, 15 minutes phone calls, 23 sms and 5 emails with an uptime of 5 1/2 hours = 84%. All on WIFI of course ;)
Click to expand...

Last night I had 3% drop in 7 hours of idle (screen off, wifi mode). :D
 
Tabarnak said:
0-255 is how intense a pixle can be. 0 is completly black, 255 is completly white
Click to expand...

I never understood why we haven't moved more towards a normalized (0-100) scale. I understand why it started off 0-255 (2^8 = 256, which is the maximum number of unique states one byte of memory can hold), but you'd think since we're not really concerned with individual bytes of memory anymore, we could start abstracting these numbers to a normalized scale.
 
Tabarnak said:
0-255 is how intense a pixle can be. 0 is completly black, 255 is completly white
Click to expand...
Thx!
iwoloschin said:
I never understood why we haven't moved more towards a normalized (0-100) scale. I understand why it started off 0-255 (2^8 = 256, which is the maximum number of unique states one byte of memory can hold), but you'd think since we're not really concerned with individual bytes of memory anymore, we could start abstracting these numbers to a normalized scale.
Click to expand...
Agreed!
 
Patriot123 said:
Thanks JB I'll change it now :)
Click to expand...

But I just moved it back to 10s :D. Reason? I'm sitting inside right by a window and it's bright outside. When facing the window ambient light is low (back of phone facing window, right?). I swivel in my chair so my back is facing the window and the brightness is bright (front of phone now facing window) then swivel back to me facing the window. To keep the brightness level from jumping up, then down, then up, then down, the 10s window length is just enough to keep it from jumping up and down so often. Again this will be dependent upon your setting and situation so play with it. Fun ehh? Kind of like looking for wakelocks! :p
 
jbdan said:
But I just moved it back to 10s :D. Reason? I'm sitting inside right by a window and it's bright outside. When facing the window ambient light is low (back of phone facing window, right?). I swivel in my chair so my back is facing the window and the brightness is bright (front of phone now facing window) then swivel back to me facing the window. To keep the brightness level from jumping up, then down, then up, then down, the 10s window length is just enough to keep it from jumping up and down so often. Again this will be dependent upon your setting and situation so play with it. Fun ehh? Kind of like looking for wakelocks! :p
Click to expand...


Lol I guess I have a lot of work to do between figuring out the auto brightness settings and figuring our how to get this faux's kernel working right
 
jbdan said:
lol. Good luck let me know if I can help in any way ;)
Click to expand...


Thanks, I'd appreciate maybe some kernel settings suggestions. I've seen a whole bunch of posts that people on 28 using Faux's 14 are running the smoothest they ever have, meanwhile I'm here at the point where it takes me 10 minutes to load a page in an app! The lag is ridiculous but I'm nervous to fiddle with the settings myself because kernel stuff is dangerous...
 
Patriot123 said:
Thanks, I'd appreciate maybe some kernel settings suggestions. I've seen a whole bunch of posts that people on 28 using Faux's 14 are running the smoothest they ever have, meanwhile I'm here at the point where it takes me 10 minutes to load a page in an app! The lag is ridiculous but I'm nervous to fiddle with the settings myself because kernel stuff is dangerous...
Click to expand...

What settings would you be referring to exactly?

I've stuck with teh stock kernel on aokp since b25-26 and it's just as good as any custom kernel out there battery life and speed. You just don't have all the tweak options with it.

So you're getting crazy lag using faux's? Did you wipe cache and dalvik before flashing?
 
jbdan said:
What settings would you be referring to exactly?

I've stuck with teh stock kernel on aokp since b25-26 and it's just as good as any custom kernel out there battery life and speed. You just don't have all the tweak options with it.

So you're getting crazy lag using faux's? Did you wipe cache and dalvik before flashing?
Click to expand...


Yessir. And my battery life has been bad...and I noticed that I was in 1200 a majority of the time....so I discovered that all day I was in constant wake lock. That issue I believe I can fix though. And settings meaning voltages and there are a couple of settings that aren't present in imos
 
Patriot123 said:
Yessir. And my battery life has been bad...and I noticed that I was in 1200 a majority of the time....so I discovered that all day I was in constant wake lock. That issue I believe I can fix though. And settings meaning voltages and there are a couple of settings that aren't present in imos
Click to expand...

Probably not what you want to try, but I'd suggest trying with the stock kernel. I haven't run faux's since 13 so I'm not familiar with all the tweaks he has implemented although I'm sure there not hard to figure out.
 
jbdan said:
Probably not what you want to try, but I'd suggest trying with the stock kernel. I haven't run faux's since 13 so I'm not familiar with all the tweaks he has implemented although I'm sure there not hard to figure out.
Click to expand...


I actually used the reset kernel because my phone wouldn't boot and am running it right now...definitely smoother so I may consider it..just the multipliers and fast charge I'll miss...and I'm worried about battery life ..
 
Oh and JB I'm having an interesting issue...I read a post in the rootz forum about someone having a media force close problem which I've had since I got my GNex. He said it was affecting the media scanner. He found a whole bunch of files from Currents left over in his SD card in media and he deleted them and the issue stopped. Now my wake locks are all coming from the media scanner so I'm assuming that's the issue. However when I try to delete them it hangs at loading, freezes, SystemUI crashes, and I have to battery pull. Then I can't boot unless I wipe cache wipe dalvik and reflash a kernel. Now I originally thought this was a Faux kernel issue, but the same happened with stock. Since I'm amongst so many distinguished wake lock hunters I figured someone might have come across a similar issue and can help me fix this :)
 
Patriot123 said:
Oh and JB I'm having an interesting issue...I read a post in the rootz forum about someone having a media force close problem which I've had since I got my GNex. He said it was affecting the media scanner. He found a whole bunch of files from Currents left over in his SD card in media and he deleted them and the issue stopped. Now my wake locks are all coming from the media scanner so I'm assuming that's the issue. However when I try to delete them it hangs at loading, freezes, SystemUI crashes, and I have to battery pull. Then I can't boot unless I wipe cache wipe dalvik and reflash a kernel. Now I originally thought this was a Faux kernel issue, but the same happened with stock. Since I'm amongst so many distinguished wake lock hunters I figured someone might have come across a similar issue and can help me fix this :)
Click to expand...

If you need to delete the files, I would try using adb (adb shell) to get a shell on it, and just cd to the dir and rm them...Should be able to do this while in CWM for example. Then once you've removed them, wipe dalvik and cache just to be safe and hopefully when it reboots it'll be fixed.
 
jkc120 said:
If you need to delete the files, I would try using adb (adb shell) to get a shell on it, and just cd to the dir and rm them...Should be able to do this while in CWM for example. Then once you've removed them, wipe dalvik and cache just to be safe and hopefully when it reboots it'll be fixed.
Click to expand...


I could but two issues there. First off, I'm worried about the effect it'll have. This directory is going as far as affecting my kernel, my systemUI, and even my capability to boot. Secondly, I don't have adb set up on a computer at the moment :D my computer had to get a whole load of files deleted including adb. So essentially I want to force it, but at the same time I don't want to push it to the point of no return and I'd have no way of knowing where that is if I do it from adb
 
You must log in or register to reply here.
Back
Top Bottom