yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] splus:
With Content adaptive brightness on (which is the default) the screen will become darker/dimmer when there's more whites on the screen. The more white on the screen the more dimming will occur. This basically means that, for example, when you use your browser, the whites will turn into a very light gray. This is "normal" Nexus screen, and this is the reason why Nexus screen looks darker at max brightness compared to other Samsung super AMOLED phones like Note or S2/S3.

When you turn adaptive brightness off dimming of whites won't happen and you'll have a noticeably brighter screen with much better whites. Just go into Gmail or a browser and look at the difference...

So, if you want your screen to look better and clearer you want to turn this option OFF.

I haven't noticed any difference in battery life although, since the screen is brighter when there's more whites with this option turned off, it's logical to assume the power drain would slightly increase. With darker themes there's practically no difference.

I personally prefer having a much better looking screen than having maybe 5% less on screen time.
[Samsung Galaxy Nexus] dandyqb:
until now androidpit is stuck with franco updater old version (5.3.1) what's happening to androidpit? :(
[Samsung Galaxy Nexus] The Gingerbread Man:
Omap gamma 1.2 and the individual colour gamma set to 0

Content adaptive brightness. You set the contrast in Francos latest app and latest kernels

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] jenicekk:
I set up MAX CPU to 1,3 or 1,4Ghz but after screen on/off is back to 1200. Its bug only on my devices or in Franco Kernel 210???
[Samsung Galaxy Nexus] TunedFish:
Apparently, it's a JB kernel problem that is yet to be solved.
[Samsung Galaxy Nexus] splus:
Yeah, I can confirm this. Newest Franco app and r210.

Just turn the screen off and back on, and the max CPU freq will go back to 1200 MHz. :(
[Samsung Galaxy Nexus] cyanoviper:
Thank you so much for the new app version, awesome! Thank you very much!
[Samsung Galaxy Nexus] splus:
I was playing with governors a bit to try to figure what's up with a slight lag when launching any app (there's a slight lag between touching an icon and app starting). All governors but interactive are incredibly laggy, only interactive is good. But even interactive has this slight lag if you wait and not touch the screen for a little while.

It looks like JB has changed the way frequencies change and how governors work.

I notice that if I set max CPU to whatever value (together with hi freq in gov control) then only 350 and that max CPU frequencies will be used.

Which, I guess isn't a bad thing IF the CPU would instantly go to max freq when screen is touched (which Google actually said they changed it). But it almost looks like the CPU isn't changed instantly to max frequency when screen is touched but it takes some time to do it, and hence there's a slight lag in UI response.

Or there's simy some mess up with changing the frequencies upon touch, which causes the lag that can be noticed every now and then, esp when launching the app drawer or opening some apps.

Just some observations and thoughts... R210 and new app, BTW.
[Samsung Galaxy Nexus] The Gingerbread Man:
Can you share your apk of su 3.0.3.2 as the ones (cwm zip) I downloaded won't flash in recovery keep getting installed failed code 0. I really want my colours to set on boot and in the market app I can't see a button to get older versions

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ThatTechShow:
So after setting the right colors... I rebooted the phone cause I installed something on my GNEX. I had to set the colors again :/ is there anyway to permanently set it to that even after reboots?
[Samsung Galaxy Nexus] The Gingerbread Man:
We need to find a copy of super user version 3.0.3.2 which I'm having problems with

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] rogersnm:
You could use an init.d script :victory:
[Samsung Galaxy Nexus] impulse101:
You want it unchecked for best picture
[Samsung Galaxy Nexus] bboran:
So do you say c.a.b on less image quality but more battery saving, c.a.b off more image quality but battery consuming?
[Samsung Galaxy Nexus] sago62:
now the colors are great .... shame that restarting the phone should do the setup ...
[Samsung Galaxy Nexus] ragnarokx:
see below
[Samsung Galaxy Nexus] Bram77:
Thought I'd share my color setting which I'm very happy with.

Omap: 1.2

Gamma: - 4, 0, 5

Color multipliers: 135, 135, 214

Contrast interface: - 5

Content adaptive brightness: on
[Samsung Galaxy Nexus] franciscofranco:
Flash this http://minooch.com/franciscofranco/Galaxy Nexus/CWM-SuperSU-v0.89.zip, update it once you're back to the system and see if its fixed.
[Samsung Galaxy Nexus] jnr21:
Not worked for me. Multipliers are always back to 200 after reboot, even init.d script doesn't work. Trinity contrast works ok.

And my phone uses only min and max frequencies (700-1200) with interactive gov.
[Samsung Galaxy Nexus] franciscofranco:
Ok thats not good news. I need you to do me a favor, write this command on terminal/adb: cat /data/data/com.franco.kernel/shared_prefs/com.franco.kernel_preferences.xml paste the output to pastie.org and share the link here please. I have to rely on users to fix this because everything sticks on reboot for me =(
[Samsung Galaxy Nexus] sago62:
to me it does not work ...
[Samsung Galaxy Nexus] franciscofranco:
That was very useful :D ...not.
[Samsung Galaxy Nexus] rogersnm:
After setting the colours (180, 192, 200/-4, 0, 5):

http://pastie.org/4182078

After Reboot:

http://pastie.org/4182079

No change to the xml file, however multiplier and v1_offset are now set to the default values rather than the custom values.

Upon reopening the app there is still no change.

Upon going to the Color Control panel and opening the multiplier settings:

http://pastie.org/4182080

The RGB multipliers reset to 200.

The gamma offset values in the app still read -4, 0 and 5 but the values in v1_offset are still 0. If you click on red then it says -4 but then if you hit OK, the v1_offset values still say 0 0 0. You have to change one of the values and hit ok in order to set the values in v1_offset.

Hope this helps
[Samsung Galaxy Nexus] sago62:
I know .... I'm a genius!:D
[Samsung Galaxy Nexus] dandyqb:
@franco

andriodpit is still stuck to the old version of your updater, when we can enjoy your latest version? :confused:
[Samsung Galaxy Nexus] aeroseek:
I can confirm that settings DO stick for me upon reboot. R196, latest app.
[Samsung Galaxy Nexus] rogersnm:
There were no problems for me on the earlier builds either, this is specific to the r210 build (I can't comment on 200/201/207, I never checked).
[Samsung Galaxy Nexus] jnr21:
http://pastie.org/4182067
[Samsung Galaxy Nexus] aeroseek:
ah ok. I thought it was an app issue since Franco recoded how the preferences get saved.
[Samsung Galaxy Nexus] rogersnm:
I just tried an init.d script and it set the colour multipliers and v1_offset no problem :)

My init.d script: /system/etc/init.d/99colorcontrol

#!/system/bin/sh

echo "1800000000 1920000000 2004318071" > /sys/class/misc/colorcontrol/multiplier
echo "-4 0 5" > /sys/class/misc/colorcontrol/v1_offset

Make sure you have busybox in /system/bin and chmod the script to 0755. If you don't have /system/bin/busybox, download Busybox by Stephen from the play store, open it, set the install location to /system/bin and install busybox. After that reboot and your custom colour settings should be applied.
[Samsung Galaxy Nexus] mingkee:
This applies to ICS, not JB.

You need either 4.9.2 or switch to DER Kernel + app.
[Samsung Galaxy Nexus] metalspring:
BTW, slightly off topic but still relevant-

Since so many are running the jb roms that have no reboot options, are all of these reboot commands safe to use with fsync off? (I'm pretty sure the first 2 are but not sure about the third (hot reboot to clear kernel/system caches)

reboot

reboot recovery

pkill zygote
[Samsung Galaxy Nexus] aeroseek:
I'm not running jb ;)
[Samsung Galaxy Nexus] franciscofranco:
Thanks that will be very useful. I'm gonna get a nice cup of coffee by the beach with Mr. cgollner, will check that **** when I'm back :)
[Samsung Galaxy Nexus] jnr21:
I have already busybox ofcourse :)

This is my 99colorcontrol in /system/etc/init.d (rwxrwxrwx):

#!/system/bin/sh

echo -4 > /sys/module/panel_s6e8aa0/parameters/contrast

echo 1350000000, 1350000000, 2000000000 > /sys/class/misc/colorcontrol/multiplier

But it not work. I will try yours.
[Samsung Galaxy Nexus] rogersnm:
afaik you need to wrap the multiplier values in quotes and seperate them by spaces not commas, as in my script above.
[Samsung Galaxy Nexus] jnr21:
Just tested yours but it's not work, all multipliers 200 again.

Edit: Maybe franco app changes multipliers back to 200 after init.d script.

Edit: Just tried to uninstall franco app and reboot but init.d script still not work, so i think my init.d support is broken?
[Samsung Galaxy Nexus] osm0sis:
No problem! Here's the binary. Just a regualar zip. Unpack and push to /system/bin then chmod 06755. I don't have the apk though.. and I'd like to roll that back too since 3.1.3 is messed up.. not sure what Chains is up to lately.

Somehow with BusyBox installed to /xbin/ and with f.k #196 init.d started mysteriously working on my Stock ICS rom. If init.d support is working your color settings should be applied just before the initial "Google" logo switches to the bootanimation. Franco app does change them again once it loads so I ended up disabling it for now - no distracting graphics "glitch" during the switch.

Here's what it takes to fix my display:

/system/etc/init.d/900colorsettings

#!/system/bin/sh
echo "2000000000 2000000000 2800000000" > /sys/class/misc/colorcontrol/multiplier
echo "2 0 10" > /sys/class/misc/colorcontrol/v1_offset
echo 5 > /sys/devices/platform/omapdss/manager0/gamma
echo -24 > /sys/module/panel_s6e8aa0/parameters/contrast
echo 0 > /sys/class/backlight/s6e8aa0/acl_set

..I had serious purple banding, even at full brightness, and yellowing that Telus refused to warranty replace.. So happy with my display at the above settings now. :D

Edit: attachment removed because SuperUser is broken and everyone should move to SuperSU for franco.Kernel.
[Samsung Galaxy Nexus] jnr21:
I have busybox in /system/bin and /system/xbin.
[Samsung Galaxy Nexus] metalspring:
??? no answer???

sorry, i just want to know if these reboot commands are safe with fsync off?
[Samsung Galaxy Nexus] willl03:
Reboot is safe
[Samsung Galaxy Nexus] sago62:
The best setup for me is:

200_200_265 colours

-6

0

+8

1.2 omap4

-20 contrast

Great!
[Samsung Galaxy Nexus] superbobup:
Yup, SR has always been off when I have tried to UV....When I try to re enable it, I get a crash....

The issue of UV not working persists across all frequencies too :(

Anyone with any ideas? @rogersnm, since you inspired me with the UV spreadsheet I turn to you for a fix! :p
[Samsung Galaxy Nexus] spinkick:
Check out the color settings I use.. looks beautiful

135,135,200

-4,0,5

contrast -24

omap 1.2

cab=off
[Samsung Galaxy Nexus] Bram77:
Maybe som color-presets could be integrated in the app?
[Samsung Galaxy Nexus] sago62:
this is settings of trinity....good colours,but i prefer my settings....:D
[Samsung Galaxy Nexus] metalspring:
btw franco, it sounds like imoseyon found the root problem of frequencies not sticking (hopefully this is the final fix for this)

[quote name='imoseyon' timestamp='1341155574' post='772752']

I do have a fix for JB reverting max freq to 1.2ghz in my kernel/ramdisk. I'll have another test build in a bit.

[/quote]

[quote name='imoseyon' timestamp='1341156958' post='772782']

google, in their infinite wisdom, decided to have a running background process that messes with various cpufreq settings. My kernel/ramdisk will install a slightly modified so that prevents it from messing with maxfreq. Modifying the OS isn't something I like doing but in this case it should be pretty harmless.

[/quote]

[quote name='imoseyon' timestamp='1341157541' post='772799']

Yeah for some reason folks who worked on JB forgot all about screen off max, and decided to control it in the OS. Pretty odd. Anyway, dev14 should fix it

[/quote]
[Samsung Galaxy Nexus] rogersnm:
You can't re-enable it at all with low voltages. Once SR is off and you have a voltage profile applied, keep it off.
[Samsung Galaxy Nexus] spinkick:
hahaha, thats great, I thought trinity looked great and I was trying to copy those, but I couldnt find them in search. Awesome!
[Samsung Galaxy Nexus] rogersnm:
Got a link to the dev14 build/source?
[Samsung Galaxy Nexus] superbobup:
Yes I know that, I always leave SR off if I try to UV. My issue is that I can set the voltage for a CPU frequency to 0mv and it will still work. For example, I can set the 384mhz slot to 0mv and it will still work (see attached SS)

SR is disabled by the Franco app and I checked to make sure the autocomp value is 0 and it is
[Samsung Galaxy Nexus] spinkick:
Ive also noticed the color multipliers not sticking on reboot, governer control settings not sticking on reboot and the contrast interface settings not sticking
[Samsung Galaxy Nexus] coreylhs:
too dark for my liking. :)
[Samsung Galaxy Nexus] metalspring:
His fixed kernel isnt out yet, but I'm sure he'll post it in his rootzwiki thread when its ready

http://rootzwiki.com/topic/13092-leankernel-minimalistic-kernel-390-6912/page__st__11720
[Samsung Galaxy Nexus] sago62:
white is so white .....de gustibus...
[Samsung Galaxy Nexus] jnr21:
@FRANCO: I changed /data/data/com.franco.kernel/shared_prefs/com.franco.kernel_preferences.xml permissions to rw-rw-rw- and now color settings stick after boot!

It was rw-rw---- previously.
[Samsung Galaxy Nexus] franciscofranco:
Yes I was just checking and that seems like a plausible solution. I think I know what to do.
[Samsung Galaxy Nexus] spinkick:
:good: Yes very tasteful :D
[Samsung Galaxy Nexus] sago62:
happy:D
[Samsung Galaxy Nexus] rogersnm:
Didn't work for me
[Samsung Galaxy Nexus] coreylhs:
feels like a slight blueish tint. xD

im sticking with the 135,135,200 0,0,0 contrast -10. c.a.b is user preference.
[Samsung Galaxy Nexus] jnr21:
Strange, now it works for me even if i set permissions back to rw-rw----, what a **** is going on? :D
[Samsung Galaxy Nexus] rogersnm:
Do you still have that init.d script in place?

I also seem to have problems with the governor defaulting back to wheatley :(

ADB Log:

http://pastie.org/4182799
[Samsung Galaxy Nexus] theMaDHakkeR:
Yep that seems to get the CPU settings to stick. Still can't get colours to stick after reboot though. I can't seem to find that script someone had posted earlier.
[Samsung Galaxy Nexus] jnr21:
No, i deleted it.

Edit: For me gov also was changed to weathley, but now it works ok too.

Edit2: Max cpu freq still goes to 1200mhz.
[Samsung Galaxy Nexus] coreylhs:
i've checked on set cpu when i set 1200000 on hispeed_freq my cpu frequency only changes from 350 right to 1200 doesn't use any frequencies in between. what am i doing wrong?
[Samsung Galaxy Nexus] theMaDHakkeR:
Seems the XML file has to be edited after every reboot. Anyone know how to make a script for this?
[Samsung Galaxy Nexus] franciscofranco:
Sigh...I'm getting out of ideas. I simply read from the preferences and set the read values on reboot with a BootService running in a separate Thread for faster applying without interfering with the OS boot speed. I can't find a pattern, each user has its own problem, or its the colors, or its the cpu settings, or its the governor... I wonder how it works for me.
[Samsung Galaxy Nexus] theMaDHakkeR:
Nevermind it doesnt seem to stick at all. Just goes back to rw rw.
[Samsung Galaxy Nexus] metalspring:
as for the cpu speed settings, imoseyon says he found the issue and fixed it in his new test release

could the os running something constantly to set its own cpu settings be causing the issue on JB?
[Samsung Galaxy Nexus] jnr21:
Yes it goes to rw-rw but my colors still works, i don't know why because previously they didn't work...

Maybe there is something in os which is messing up things or something...
[Samsung Galaxy Nexus] sotoskawasaki:
Do we have to use busybox? If yes which version do you have?
[Samsung Galaxy Nexus] osm0sis:
My colours only wouldn't stick when I had su 3.1 binary. If you're experiencing the problem currently, at what version is your su?
[Samsung Galaxy Nexus] franciscofranco:
I call busybox echo in the root command yes, but I doubt thats the issue. I have this one: BusyBox v1.18.1 (2010-12-22 14:33:36 GMT) multi-call binary.

I will try to include my busybox into the assets of the app and call it from there, might be more intelligent than relying on the rom/install su app/installed binary.

By the way thanks for everyone who's trying to help me with logs and experiments, it's very important.
[Samsung Galaxy Nexus] dwang:
512 gpu oc using jb lean kernel makes a huge difference in fps with nenamarks.
[Samsung Galaxy Nexus] franciscofranco:
Yep it does. I will compile with 512GPU in the future, dont worry.
[Samsung Galaxy Nexus] theMaDHakkeR:
The XML file and CPU settings reset with every s screen on/off. Still messing around with it.
[Samsung Galaxy Nexus] dwang:
Thanks. Modern combat 3 runs smoother (with all effects enabled). Nova 3 doesn't seem to work with jelly bean so I can't try that out.
[Samsung Galaxy Nexus] Kas206:
Has touch sensitivity changed in this kernel or is that a jelly bean thing?

I'm pressing alot harder than usual for the touch to register.
[Samsung Galaxy Nexus] Hussainally:
Same here.anyways thanks Franco...appreciate our work
[Samsung Galaxy Nexus] Hussainally:
Could someone recommend the best display settings,from what I see the suggested ones a few posts back are not to my liking as they seem kinda blurry and dark...appreciate it.thanks
[Samsung Galaxy Nexus] dracon6ai:
Seems Content Adaptive brightness has a very noticeable impact on battery. At least for me. I tried it disabled with these settings with stock auto brightness (yes I know I run it bright, screen burn in problem, etc etc. Burn in = New free phone so I'm not worrying about it)

310

310

375

-6

0

8

1.2

-12

C.A.T off

On my extended battery I usually get 3 ½+ hours screen on on wifi. I'm at 50% battery now with 1hr 16mins screen on. At this rate I'll lose 1 hr of screen on time with it disabled. Will keep testing but that's what I've seen the last 2 days (1 full charge a day, phone never last more than 16hrs for me.)

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] rogersnm:
I haven't noticed any change in touch sensitivity going from ICS to Jelly Bean and then to this kernel. I can still barely touch the screen and it registers it no problem.
[Samsung Galaxy Nexus] sing1gnis:
Give these a shot:

http://xdaforums.com/showpost.php?p=26611033&postcount=375

Using OMAP4 gamma 1.2 and Trinity Contrast -10 it looks amazing.
[Samsung Galaxy Nexus] thanksgiving60:
how can one not be impressed with this kernel!

this is awesome!

thanks franco!
[Samsung Galaxy Nexus] Hussainally:
Thank u...this is perfect
[Samsung Galaxy Nexus] atsavlis:
Franco, do you run the jelly ROM with all the standard Google apps that come with it, or have you removed any of the apps to prevent wake locks etc?
[Samsung Galaxy Nexus] franciscofranco:
I remove lots of stuff every time I install a new rom.
[Samsung Galaxy Nexus] RayGarden:
Can you plz share your Kernel Settings? What ROM are you currently on?

Tnx
[Samsung Galaxy Nexus] franciscofranco:
Ok now the boot service is now using my busybox version bin from inside the app, this HAS to fix the ****.
[Samsung Galaxy Nexus] derPianist:
The newest nightly for ICS is 196? The app is showing me that but the Thread Title says r200?

Franco? Please help me i am really confused now?!

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] superbobup:
r200 has a few JB stuff into it, but it is used specifically for ICS. There's a changelog somewhere in here. The app is also available on the server (check the OP) :highfive:
[Samsung Galaxy Nexus] mullemulle86:
r200 is based on jelly bean and experinental because of that it is not in the app but you can download it from 1st page

r196 is the newest kernel based on ics

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] derPianist:
Thank you two!

What do you think is now better? I am on AOKP B40

What do you guys are running, r196 or r200?

Thanks!

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] danielvc:
Just go with 196. Or else, make a nandroid and find our for yourself :-)
[Samsung Galaxy Nexus] atsavlis:
Would you mind sharing thoughts on what apps you remove?
[Samsung Galaxy Nexus] simms22:
my guess is that francisco is like me, i remove every system app i dont use.. books, calculator, calendar, calendar provider, currents, email, exchange, facelock, geniewidget, magazines, nfc, soundrecorder, tag, videos, and wallet. all this equals less crap(**** ;) ) that i dont use opening up in the background.
[Samsung Galaxy Nexus] franciscofranco:
No, because my own usage will break stuff for some users.
[Samsung Galaxy Nexus] franciscofranco:
YES :D Thats why our phones run so well. No **** = no problems.
[Samsung Galaxy Nexus] leelaa:
Same here, i also get rid of live wallpapers.
[Samsung Galaxy Nexus] simms22:
absolutely!(im out of thanks already for the day :eek:)

plus, it also means that much more free ram available to you. autostarts is a good app to use too, i dont let anything, besides for a few needs apps, start up on their own. its nice being in control of your phone instead of it controlling you.
[Samsung Galaxy Nexus] franciscofranco:
Hmm I've said that before in one of my rants, I'm gonna sue your ass.
[Samsung Galaxy Nexus] mullemulle86:
can i do this by deleting those apk files in the system folder or do i need to do sth else?

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] simms22:
yup, i use root explorer. /system/app/. delete what you dont need then reboot. if you delete nfc, you might get force closes before you reboot. the reboot will fix that.
[Samsung Galaxy Nexus] arzbhatia:
Franco, you're working on the init.d problem right?
[Samsung Galaxy Nexus] simms22:
but i have proof of usage before you stated it :eek:
[Samsung Galaxy Nexus] Francois88:
I wasn't too sure whether to ask here or in CM's thread. I'm used to my older SGS where there were kernels for "normal" roms and some for CM exclusively.

Currently it seems your kernel works for either. Is this gonna remain like that or will that change once CM9 is more advanced?
[Samsung Galaxy Nexus] franciscofranco:
Dunno, I have to compare ramdisks, can't predict the future =)
[Samsung Galaxy Nexus] Ascenca83:
So basically you are saying that by not using JuiceDedender I would loose less than 4% (or even 0%) through the always active 3G connection. Is this right?

Shouldnt the battery life be better when the 3G connection is only established once every hour instead of being constantly active?

Thanks for the replies.

Sincerely,

Ascenca
[Samsung Galaxy Nexus] daandman:
How do you guys find the battery life on AOKP?

I had amazing battery life with franco 7.1 on Eaglesblood, switched to AOKP 13 & updated to franco 8, and battery life was terrible. Not sure if it was the rom, the new kernel or just that I was messing with it a bit more.
[Samsung Galaxy Nexus] nicandris:
waiting :)

Changelog:

Coming next for #9:
* Internet tweaks added directly to the ramdisk - more speeeed
* Writeback settings tweaked a bit
* During screen_on frequency is ramped up to the maximum frequency and stays there for 5secs. This will get rid of the lag when unlocking the screen and makes sure the device wakes up propely
* Also added cpu1 suspended when screen_off and when screen_on it comes back to life. This works no matter what governor is choosen
[Samsung Galaxy Nexus] nicandris:
i use aokp 13 with franco's latest. no issues here
[Samsung Galaxy Nexus] DJ "suMo*:
That's what I'm talking about...

Sent from my GN