Related
Hi there,
I'd like to have an option for minimum light emission in situations like a party or other similar dark places.
Inverted colors and very low light would be great. I think the car mode is a similar option but can only be triggered by the docking station. Is that correct?
How would I achieve that?
Cheers
Though it does not do exactly what you want, I myself use an application to decrease brightness to a setting lower than default. It's called 'Screen Filter', and it's free. Perhaps it is of use to you.
Good luck
I read about those apps but it's not what I want. I would rather prefer a setting for white text on black background PLUS decreased brightness.
Thx anyways.
Often at night when I use phone lowest brightness is still bright so I found apps which can dim it further but then they loose screen contrast too.
Is there any app which can make night mode of selected apps background dark & font light / white similar to youtube app?
UC browser had this night mode earlier but latest version they have removed this feature.
This is what I am looking to acheive
http://forum.xda-developers.com/showthread.php?t=990102
ok, from my android tweaking and modding i know it can be somewhat hard to find everything you might need to make the most of your galaxy nexus so i will put links to them here along with providing support and my own little discoveries here...
This will include everything from guides to different type of tweaks, recommended settings, flashable mods, etc...you name it and it will probably be in here (as i update it)
Any suggestions are highly appreciated and will be added with proper credit
***disclaimer- I am not responsible for any damage you may do to your device, please make sure to have a backup before doing any of these tweaks***
(still a work in progress and expect much much more to come)
Guides/Toolkits
[GNex TOOLKIT] Drivers, Backup, Unlock, Root, CWM, Flash, Mods + MORE [VERIZON]
[EASIEST ROOT/UNLOCK TOOLKIT] Wugfresh Galaxy Nexus Root Toolkit v1.4
Build.prop tweaks
To use these just mount /system rw, open build.prop in a text editor, add/modify whichever lines you want, save, reboot recovery, wipe cache and dalvik cache, then reboot
Code:
#incoming ringer delay (already in build.prop) sets how soon (in ms) the phone starts ringing when a call comes in. set between 0 and 3000
ro.telephony.call_ring.delay=
Possible battery saver-
Code:
#disable sending usage data to google
ro.config.nocheckin=1
Code:
#sleep mode for battery savings. 0 power collapse suspend, 1 power collapse (best), 2 apps go to sleep, 3 show clock and wait, 4 wait for interrupt
pm.sleep_mode=
Code:
#change lcd density (already in build.prop), which is like changing the resolution on a windows computer can be anywhere from 240 to 360 (stock 320)
ro.sf.lcd_density=
Performance enhancement, may also help with battery life
Code:
#dalvik cache virtual memory size
dalvik.vm.heapsize= (stock 256m, recommended 320m)
dalvik.vm.heapstartsize= (stock 16m)
dalvik.vm.heapgrowthlimit= (stock 128m)
Can improve overall scrolling fluidity and speed
Code:
# This defines the max event window manager can
# handle in 1 s. We may adjust this # for performance
# reason later
windowsmgr.max_events_per_sec= (recommended 275)
General performance tweak
Code:
#disable the zygote loader
ro.wmt.blcr.enable=0
Extended jni checking is costly in terms of performance and battery life so disabling them is suggested
Code:
#disable extended dalvik jni checking
ro.kernel.android.checkjni=0
dalvik.vm.checkjni=0
Helps with overall performance
Code:
debug.performance.tuning=1
video.accelerate.hw=1
Helps increase picture/video taking quality and video viewing
Code:
#Raise Photo and video quality?
ro.media.enc.jpeg.quality=100
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.enc.hprof.vid.fps=65
Code:
#help to free up unused ram
persist.sys.purgeable_assets=1
Disables notification of usb debugging
Code:
#stop usb debugging on notification
persist.adb.notify=0
enables/disables (set to 0) dithering
Code:
#Improve screen quality at the cost of performance
persist.sys.use.dithering=1
Code:
#Use dalvik JIT compiler (Just In Time compiler is much faster and should be enabled by default)
dalvik.vm.execution-mode=int:jit
Code:
#disable camera sound?
persist.sys.camera-sound=0
Dalvik vm dexopt tweaks (USE ONE OR THE OTHER, NOT BOTH, i prefer option 2)-
option 1- disable dalvik checking, increases free ram but less optimized dalvik cache
Code:
dalvik.vm.verify-bytecode=false
dalvik.vm.dexopt-flags=v=n,u=n,o=v
option 2- enable more checking for a better performing dalvik cache but may use a little more ram
Code:
dalvik.vm.verify-bytecode=true
dalvik.vm.dexopt-flags=v=f,u=n,o=v
Init.d tweaks
To use mount /system rw, go to /system/etc/init.d create new file, add the lines in, save, and set permissions to rwxr-xr-x
Code:
#disable logcat
rm dev/log/main
Recoveries/Radios/Etc
List of flashable verizon radios-
radiosvzw-all-radios-in-flashable-zip/
Team win recovery project (custom touchscreen recovery-
twrp-212-touch-recovery-2012-04-20/
Clockwork recovery touch toro-
recovery-clockwork-touch-5.8.0.2-toro.img
clockwork recovery no skip edition-
recoverycdma-clockwork-recovery-v5504-no-skip-edition/
Mods/other
Suggested color control settings-
whitest whites
red 200
green 200
blue 265
gamma red -6
gamma green 0
gamma blue 8
omap4 gamma 6 (1.2 via franco app)
Morfic battery saving settings-
Red 135
green 135
blue 200
gamma red 0
gamma green 0
gamma blue 0
omap4 gamma 6 (1.2 via franco app)
Franco suggested settings-
Red 180
Green 192
Blue 200
gamma red -4
gamma green 0
gamma blue 5
omap4 gamma 6 (1.2 via franco app)
Custom auto brightness tweaks (super power save + conservative power save settings)
For both sets of settings-
Light sensor filter enabled yes
Window length 5s
Reset threshold 400 lux
Sample interval 5s
Use custom yes
Screen dim level 1
Allow light decrease yes
Decrease hysteresis 50%
Conservative power save settings-
Edit other levels under screen column-
15
17
19
21
23
25
27
30
32
40
49
54
65
75
100
125
146
179
211
225
Super power save settings-
Edit other levels under screen column-
6
8
9
11
12
14
16
19
23
27
33
40
50
64
85
97
111
146
178
225
Look here:
http://forum.xda-developers.com/showthread.php?t=1599025&highlight=battery
and here:
http://forum.xda-developers.com/showthread.php?t=1462020&highlight=battery
metalspring said:
Suggested color control settings for whitest whites-
red 200
green 200
blue 265
gamma red -6
gamma green 0
gamma blue 8
omap4 gamma 6 (1.2 via franco app)
Click to expand...
Click to collapse
Could you add the recommended overall color multiplier values?
Red 180
Green 192
Blue 200
Gamma (cannot remember, might be 1.2)
Hi,
Maybe an explanation for each tweaks would be great
X tweaks do this (for battery life or performance) but do this,etc...
The tweaks for the build.prop already exists (there is maybe 3/4 or more threads) in the Android section,some of these have not effect in ICS...
And maybe the general section is more appropriate...?
In any case thanks for this.
viking37 said:
Hi,
Maybe an explanation for each tweaks would be great
Click to expand...
Click to collapse
most have a simple explanation, the ones that dont are general performance/battery life tweaks
any in particular you dont understand?
I'll be happy to add in more detailed explanations on those
metalspring said:
most have a simple explanation, the ones that dont are general performance/battery life tweaks
any in particular you dont understand?
I'll be happy to add in more detailed explanations on those
Click to expand...
Click to collapse
Me,I understand because I've tested most of these and I use Google to understand what they do.But most of the users will ask,for sure...
You suggest some tweaks...I think you could suggest an explanation that comes with.
Not just a compilation of tweaks...
It's just my opinion...
Theshawty said:
Could you add the recommended overall color multiplier values?
Red 180
Green 192
Blue 200
Gamma (cannot remember, might be 1.2)
Click to expand...
Click to collapse
Those are included in the franco app but i guess i can put them in too, maybe morfics battery saver ones too if someone posts them (or i find them somewhere)
viking37 said:
Me,I understand because I've tested most of these and I use Google to understand what they do.But most of the users will ask,for sure...
You suggest some tweaks...I think you could suggest an explanation that comes with.
Not just a compilation of tweaks...
It's just my opinion...
Click to expand...
Click to collapse
I did add some explanations but i still think many explain themselves...unless you're talking about the dalvik dexopt ones...those are somewhat technical
metalspring said:
List of flashable verizon radios-
radiosvzw-all-radios-in-flashable-zip/
Team win recovery project (custom touchscreen recovery-
twrp-212-touch-recovery-2012-04-20/
Clockwork recovery touch toro-
recovery-clockwork-touch-5.8.0.2-toro.img
clockwork recovery no skip edition-
recoverycdma-clockwork-recovery-v5504-no-skip-edition/
Click to expand...
Click to collapse
These all look to be only Verizon / cdma versions,why post this in the GSM section?
For Trinity Spiceeeee use these values:
Multipliers:
Red 135(0000)
Green 135(0000)
Blue 200(0000)
Gamma: 0,0,0
Give your brain some time to adjust like Master Morfic says and you'll never wanna go back to stock colors again
Also play around with Gamma/Omap4 control for contrast
Verstuurd van mijn Galaxy Nexus met Tapatalk
odin13 said:
For Trinity Spiceeeee use these values:
Multipliers:
Red 135(0000)
Green 135(0000)
Blue 200(0000)
Gamma: 0,0,0
Give your brain some time to adjust like Master Morfic says and you'll never wanna go back to stock colors again
Also play around with Gamma/Omap4 control for contrast
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
Are you sure they're the same? also what about OMAP?
What do you mean?
Verstuurd van mijn Galaxy Nexus met Tapatalk
odin13 said:
What do you mean?
Verstuurd van mijn Galaxy Nexus met Tapatalk
Click to expand...
Click to collapse
1) Are you sure the values are the same or they're just similar?
2) What did you set for OMAP4 Gamma Interface?
3rdstring said:
These all look to be only Verizon / cdma versions,why post this in the GSM section?
Click to expand...
Click to collapse
I just put the Verizon/cdma versions up first since that's what I have, I'll add in the sprint and GSM versions too if someone can give me a link to them
Just tried some of your tweaks (build.prop) and coloursettings and everything seems to be working fine. Colours look similiar to Trinities, little better imo. While scrolling a bit it feels a little bit faster, but that can just be the result of a placebo though.
Thnx for posting this!
Added custom auto brightness tweaks for custom roms with that option (should help save a lot of battery, actually can go lower than manual brightness)
Well, after 5 months of looking out for the best values, I've experimented and all and found out these to be the best. Even at lowest brightness, the screen is crisp and clear just like it's supposed to be.
People who have the Purple Screen issue, I highly recommend you use these values.
Requirements -
1. Franco Kernel Updater (TKT wouldn't give that much brightness/crispyness to the screen)
2. ICS Gradient Fix (Check Signature)
3. Franco Kernel
First up, flash Franco's latest kernel.
Secondly, make sure you don't have any 2 or more applications which have Color Control options (Like, Franco Kernel Updater and TKT - Remove TKT and stay with Franco). If you do have 2 or more installed, please set all values to default on all applications including Franco's. (In TKT, click on menu and select reset preferences and reboot).
Third, fire up Franco Kernel Updater and get to the CC options and set these :
Color Multipliers -
Red - 280
Green - 292
Blue - 350
Gamma -
Red - 4
Green - 0
Blue - 9
Disable Contrast Adaptive Brightness - Yes (Tick)
Contrast Control : -24
OMAP Gamma - 1.2
These values work BEST with MoDaCo's JB Build. Tested on Jr1, Jr.1.1, Jr2.
Please note : This is simply a band aid, not a total fix. The purple screen and grain issue is probably a hardware issue. This settings are extremely crisp on my device. You need to get adapted to them.
Thanks to -
1. Franco for his amazing kernel and application.
2. Morfic for introducing contrast control into the kernel world and of course for his kindness. (You're the sweetest developer I've talked to).
Best of luck with these settings guys!
Please, don't forget to click "Thanks"!
It made everything look over-saturated for me.. plus, is it safe to jack up the settings like this?
It did improve the grainy screen on low brightness problem, though.
Well, i think the best values i've EVER Seen.
Oh dear, so f****ng awesome.
via Google Galaxy Nexus
Made my eyes hurt.. Too cold.. I'm trying to get my screen as close to 6500k as possible.
Sent from my Galaxy Nexus using Tapatalk 2
Thank you for this! By far the best optimization of colors I've ever seen. Maybe colors are a bit over-saturated but thats how Super AMOLED should produce.
Doesn't lacking the values up that high create burn in???
Sent from my Galaxy Nexus using xda premium
craigbailey1986 said:
Doesn't lacking the values up that high create burn in???
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Try reducing every multiplier value by 40. 280 to 240, 292 to 252 and 300 to 260.
This can never be an all-in-one "fix" because of the way screen technology works. Everyone's screen will have different degrees of the problem itself (purple tint & grain), on top of that they will all have a slightly different color temperature, contrast level, saturation etc. By providing the values that worked for you, you're just going to have a thread where half the people think it looks great, half think it looks awful, and everyone thinks everyone else is crazy.
A better idea might be to describe the steps you took to arrive at your own numbers, things you looked for, how you tweaked them to get to the best values.
Look Excellent to me - Screen absolutely Pops, so vivid and the gradient issues are not visible.
Thanks so much!
Those high values are gonna kill your screen
OP settings work well for me (similar to my 200 215 280, -2 0 10, -23, CAB off), but OMAP always makes things worse IMO. With OMAP at 1.2 I instantly see banding again where with it off the gradients are smooth. OP settings with OMAP 1.0 are excellent however, reducing the magenta and yellowing I was seeing with my others. I am worried about the burn-in though..
What's this about burn in? Do these settings cause it?
I sort-of mispoke. Burn-in is possible, but high multipliers are more worried to wear out those pixels/degrade them faster.
Edit: I'm going for more of a "Trinity Blue" sort of solution now: 215 235 280, -2 0 15, -24, CAD off, OMAP unset. Still trying to find that balance that gets rid of the magenta/yellow at all points.
Okay guys try out 180,192 and 250 as the color multipliers. No burn issues then. I'm on it right now. Its great!
I'm using Trinity kernel, TKT, and Display Tester Pro for calibration. The gamma test shows that my particular settings should be red=2, green=3, blue=2. The color gamma settings are not relative to one another and are not "mixed together" for adjusting color. Each one is a separate adjustment for that color's correct level of brightness for midtones, relative to darkest and lightest levels. Together, the three settings add up to correct gray brightness levels, not to correct gray colorlessness.
If you look at a chart containing only black, 50% gray, and white, the color multipliers should be adjusted to remove any trace of color tint from the gray. The easiest way to do it is set the weakest color to 200 and reduce the other two colors until the gray has no color tint at all. The properly set color gamma settings, on the other hand, should make the 50% gray have the correct lightness level.
If you have yellow tint, there's not enough blue. Magenta tint means not enough green. Cyan tint, not enough red.
The color multipliers, unlike the gamma settings, are relative to one another. Once you have them set correctly relative to one another, moving them all up or all down together pnly changes the overall brightness of the display. The wrong overall brightness level will remove detail from either the black end or the white end. Too much brightness is also bad for the screen, not to mention battery drain.
So anyway I'll shut up now and I hope everyone gets their screens looking perfect.
gsm gnex / cm9 / trinity / 1420 MHz
for whatever reason trinity seems to be giving me better screen color, but im sure I could do the same with franco, anyways, my gamma settings are untouched, I found that modifying the color to these values makes the purple tint go away for me:
Red:135
Green:135
Blue:190
Trinity Contrast -15 to -25
Have you tried adjusting it for 18% gray? I can nail it pretty close with 180,150,190 and 8,0,8 but gamma is a complete ***** on this display...
strumcat said:
I'm using Trinity kernel, TKT, and Display Tester Pro for calibration. The gamma test shows that my particular settings should be red=2, green=3, blue=2. The color gamma settings are not relative to one another and are not "mixed together" for adjusting color. Each one is a separate adjustment for that color's correct level of brightness for midtones, relative to darkest and lightest levels. Together, the three settings add up to correct gray brightness levels, not to correct gray colorlessness.
If you look at a chart containing only black, 50% gray, and white, the color multipliers should be adjusted to remove any trace of color tint from the gray. The easiest way to do it is set the weakest color to 200 and reduce the other two colors until the gray has no color tint at all. The properly set color gamma settings, on the other hand, should make the 50% gray have the correct lightness level.
If you have yellow tint, there's not enough blue. Magenta tint means not enough green. Cyan tint, not enough red.
The color multipliers, unlike the gamma settings, are relative to one another. Once you have them set correctly relative to one another, moving them all up or all down together pnly changes the overall brightness of the display. The wrong overall brightness level will remove detail from either the black end or the white end. Too much brightness is also bad for the screen, not to mention battery drain.
So anyway I'll shut up now and I hope everyone gets their screens looking perfect.
gsm gnex / cm9 / trinity / 1420 MHz
Click to expand...
Click to collapse
arzbhatia said:
Okay guys try out 180,192 and 250 as the color multipliers. No burn issues then. I'm on it right now. Its great!
Click to expand...
Click to collapse
It's been discussed few times already - going above 200 can lead to screen burn in. On SAMOLED screens blue color wear out first and peeps really shouldn't touch this setting. Better set lower red/green values. Screen will look a bit darker so don't cranck up contrast too much, -10 should be good enough.
herzzreh said:
Made my eyes hurt.. Too cold.. I'm trying to get my screen as close to 6500k as possible.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
look at the graphs.
http://forum.xda-developers.com/showpost.php?p=29037317&postcount=1
herzzreh said:
Have you tried adjusting it for 18% gray? I can nail it pretty close with 180,150,190 and 8,0,8 but gamma is a complete ***** on this display...
Click to expand...
Click to collapse
You can see where your gamma should by by installing the free version of Display Tester from the Play Store. Go to Color, Gamma, and slide the gray screen to the left to see the red page. Find the vertical bar that most closely matches the red bacground. The number on that bar is where your gamma should be set for that color. Mine is spot on at 2.3. Then slide to green page and do the same. Then the blue page. My green gamma reading is 2.8, meaning it isn't quite as bright as the red or blue, so I have to turn it up a hair. My blue is good at 2.3. The adjustment sliders in TKT only give me whole-number choices, so I get as close as possible with 2, 3, 2. I'm just guessing there, since TKT doesn't have normal gamma increments. Anyway good luck taming your gamma.
galaxy nexus (gsm) / cm9 / trinity @ 1.4GHz
Hi All!
Kindly share your KCAL settings here
Like this:
Kernel - my kernel - IceMan ( not for public )
OS - LineageOS build myself
My settings:
Red 216
Green 222
Blue 256
Saturation 65
Value 129
Contrast 129
Hue 0
Thank you!
250
240
255
40
132 (140)
132 (140)
10
Red 235
Green 248
Blue 256
Saturation 52
Value 132
Contrast 138
Hue 0
Tianma Panel
Excellent idea to open a thread like this. If anyone has a Kcal profile which makes blacks blacker, whites whiter and colors more vivid, please share your profile. :3. I'm on an LOS based rom by the way.
What app are you using to control the KCal?
techlogik said:
What app are you using to control the KCal?
Click to expand...
Click to collapse
Elementalx app its fine, but also required custom kernel for kcal.
240,240,256,50,130,132,0
Whiter screens
Sent from my HTC 10 using XDA-Developers Legacy app
Hmm, I think I found a profile which I like. I used the DarkDroid profile as the base and changed one value.I only changed saturation.
Red: 250
Blue: 250
Green: 256
Saturation: Default is 45 but I changed it to 65
Value: 120
Contrast: 145
Hue: 0
As different type of panel is available and implemented on our beloved HTC10, shouldn't we share what type of panel too ? it's easily available using DevCheck app
I don't think applying settings from a panel to a different brand is really productive.
It's like calibrating a Sony TV and applying the resulted calibrating profile to a Samsung one, just because models share the same IPS panel ? Hmmmm no !
Btw this topic is an excellent idea !)
Fre$h said:
As different type of panel is available and implemented on our beloved HTC10, shouldn't we share what type of panel too ? it's easily available using DevCheck app
I don't think applying settings from a panel to a different brand is really productive.
It's like calibrating a Sony TV and applying the resulted calibrating profile to a Samsung one, just because models share the same IPS panel ? Hmmmm no !
Btw this topic is an excellent idea !)
Click to expand...
Click to collapse
You are right; I have updated my post