yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Franco has updated his app so now you can use his app do set it. All we new now is to set he read ahead value but all in good time :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

15/90/0.7/45/15/80(target load) is giving me ridiculously good scrolling in tapatalk. Now to try 30 min sample time to see how that feels and perhaps save a little battery

Im using 1228/192 interactive with row, stock rom.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

+1

Same here, these values seem to be the sweet spot and battery life is much better than yesterday :) :good:

GNex with franco.Kernel r361 / CM10.1
[Samsung Galaxy Nexus] elboby:
Lagfix?

Does the app Lagfix(fstrim) will work with fanco's kernel or the changes are already on his kernel?
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

You can thank my man joaquinf. So far 30 min sample time has no negative effects :thumbup:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
Try 15/95/0.7/45/15; t_l 85 --> h/t osm0sis on the n7 thread :)

Then try 30/90/0.7/45/30; t_l 80 --> my experimental tuneables for the n7

Please share your thoughts
[Samsung Galaxy Nexus] Angelakaro:
Strangely,i have better scrolling/overall snappiness with go_hispeed_load set to 75 and target_loads set to 90. And you guys are repeating several times that go_hispeed_load must be higher than target_loads...puzzling. Also,for me with these settings battery is the same of stock value
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Will test os' for a bit on my gnex then yours after. At work so not got my n7 with me

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] vlc_marcos:
could someone givee me the name of the points of each value.

15/95/0.7/45/15
[Samsung Galaxy Nexus] joaquinf:
Bookmark this

The third value left to right is hispeed_freq/1000
[Samsung Galaxy Nexus] whitedragonz83:
above_hispeed_delay / go_hispeed_load / hispeed_freq / min_sample_time / timer_rate

If you see another number afterwards it usually is "t_l" or "target_loads"
[Samsung Galaxy Nexus] joaquinf:
Try both with the min freq set to 192 please.

I've lowered it and i feel zero difference and maybe this could help a little with batt life since we have now stellar performance :)
[Samsung Galaxy Nexus] vlc_marcos:
tahnks guys. and for this chnages you are using wich gov?
[Samsung Galaxy Nexus] joaquinf:
Interactive
[Samsung Galaxy Nexus] shreddintyres:
i had the understanding that setting the min freq to 192 was more or less useless, seeing as how the difference in voltage between 192 and 384 is practically negligible as well as the fact that 192 would keep the phone awake longer.

Is the difference in voltage between 192 and 384 really that substantial now to make an impact on battery life? or is there something else going on that im missing?
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Is no one else experiencing lag when returning to the home screen from within an app? I wonder if its launcher related...
[Samsung Galaxy Nexus] joaquinf:
Well i remember that. In r361 voltages are hardcoded for 192@800, 384@850, 537@900 ... My guess is that if we set the min freq to 537 i'm pretty sure that we will notice some impact on the batt life so it should be the same from 384 to 192 since the difference is the same (50 v)
[Samsung Galaxy Nexus] whitedragonz83:
No issues here with stock launcher using RasBeanJelly ROM

---------- Post added at 09:53 AM ---------- Previous post was at 09:51 AM ----------

Screen off benefits the most with a lower frequency because power consumption is still a function of frequency x voltage(squared), so it has an effect. Screen on, probably meaningless compared to the power consumption of the screen.
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I'm already using it, over all I feel 45 min sample is better to stop the CPU slowing so quick to keep things smooth. I think this (os' from n7 thread) is pretty much perfect settings tbh, will try yours when I'm home later on :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
Mine have m_s_t set to 45 too :)

30/90/0.7/45/30; t_l 80
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Yup only slight difference is go hi speed load and target load.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
I forgot a lil detail :p set the read ahead buffer to 2048
[Samsung Galaxy Nexus] osm0sis:
Haha so which settings of mine do we like now?

Just so people know, read ahead can be checked with:

cat /sys/block/mmcblk0/queue/read_ahead_kb

and set with:

echo 2048 > /sys/block/mmcblk0/queue/read_ahead_kb

You might have to su first. :good:
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Haha :p I'll just leave it as default till Franco updates the app again to change it. I prefer the fku interface than trickster and uninstalled it earlier when Franco updated his app

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] joaquinf:
THe one you posted on the n7 thread --> 15/95/0.7/45/15; t_l 85
[Samsung Galaxy Nexus] Sveke:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I don't have any lag on my GNex w stock settings.

My N7 on the other hand has seen great improvement messing with the variables.

GNex=good
[Samsung Galaxy Nexus] osm0sis:
OK. So just subbing in the different hsf for the GN (0.7 GHz here vs. 1.0 GHz for the N7). Got it. ;) :good:

Yeah it's weird that they work so well considering interactive received the same changes in both. The current GN defaults should cause oscillations as the governor tries to make it reach 90% target_loads, then inevitably hits 65% go_hispeed_load and jumps to hispeed_freq, lowering the load, so it tries to reach 90% again, hits 65% and jumps again, ad nauseam.
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Also running that. it's hard to notice differences between little changes in parameters .
[Samsung Galaxy Nexus] Kapetan:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Did I set tunables well?
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

You can see you did? Do you notice any difference?
[Samsung Galaxy Nexus] Kapetan:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Yes more responsive phone,that's without doubt. But I asked if there is a minor change or something.... :) Batt is now at 32% and I'll have to wait recharging for any improvements.

With stock settings I've got 4h2m display on and 12h of general usage.
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

They're good. 4 hours is impressive, doubt if you can get that better. The screen is the part of the phone that uses the most power.
[Samsung Galaxy Nexus] Kapetan:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

True indeed, but what I have also noticed is that Google Services are draining battery when stand by...That's reason I couldn't get more general usage. Need to find solution for that....

Recharging now, will test batt next 1-2 days.

To be honest, usage with franco kernel is as close as possible to fit my demands on daily usage in terms of speed/response/batt usage.
[Samsung Galaxy Nexus] Raijin:
Can we reduce the time between when we press a button and the animation starts? I know the way of work of Project Butter, 16 ms to generate the frames, but, I think this time is greater.

This happens always, months ago and now, using the stock governor and with customizations. The animations are very fluid, the phone works great, but this.

Also, this happens the first times I make a touch input. After the animation is stored in RAM and is showed at the moment.
[Samsung Galaxy Nexus] Sveke:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Yeah lower your animations to .5 in dev options.

Sent from my Nexus 7
[Samsung Galaxy Nexus] Raijin:
It has nothing to do with it.

Touch input > -----Time----- > Animation starts > Animation finish > New window
[Samsung Galaxy Nexus] nihalot:
Above high speed delay is supposed to be 15k or 150k?

Also timer rate has to be 15k or 150k?

TIA
[Samsung Galaxy Nexus] joaquinf:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

15k for both.
[Samsung Galaxy Nexus] supernova_00:
Does that mean franco changed the tunables to what you guys have been suggesting as better numbers? I'm curious because I'm on track for best battery life ever on my phone. Usually barely ever get to 2 hours and I'm at 2 1/2 with 35% left!
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I personally use slightly lower than Franco's at 180 192 200 RGB -24 contrast and 1.2 OMAP gamma CAB off

Edit*** and I'm using them set by init.d per osm0sis instructions in his signature

Shiny + Franco 361
[Samsung Galaxy Nexus] Kapetan:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I've tried higher values but contrast -5 and 150 152 179 looks fine for me. Maybe, maybe somehow to get white more - white. It's probably needed a fine tune..
[Samsung Galaxy Nexus] J-Hop2o6:
R 300

G 250

B 350

Trust me. Going above 200 is perfectly safe. Adjusting these values is mainly adjusting the BRIGHTNESS of these colors. So my 100% brightness is even brighter now. And this gives me the best color balance (not warm [dim/brown] whites, nor cold [blue hue] whites).

The rest:

R 0 or -1

G 0

B 1

CAB disabled

Trinity: -5 through -10

OMAP: 1.0 (5)
[Samsung Galaxy Nexus] Kapetan:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I clearly see difference :) but what about screen durability and batt usage? It's all brighter now and it has to drain more batt? Or not necessarily?
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

your brightness setting will determine that

Shiny + Franco 361
[Samsung Galaxy Nexus] Kapetan:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Auto brightness is on. I hate changing brightness any time I go in/outside...
[Samsung Galaxy Nexus] Raijin:
I've spent a lot of time tweaking the colors. They are almost perfect. No yellow tint, real white. Try them, you will not go back.

Red: 210

Green: 210

Blue: 225

Gamma Red: -2

Gamma Green: -10

Gamma Blue: 1

Trinity Contrast: 0

OMAP4 Gamma Contrast: Disable

Content Adaptive Brightness: Disable

Brightness: 100%

#!/system/bin/sh

echo "2100000000 2100000000 2250000000" > /sys/class/misc/colorcontrol/multiplier;
echo "-2 -10 1" > /sys/class/misc/colorcontrol/v1_offset;
echo 0 > /sys/module/panel_s6e8aa0/parameters/contrast
echo 0 > /sys/class/backlight/s6e8aa0/acl_set;

Base colors have a little boost. The trick is the difference between Red and Green vs Blue. And the Gamma Green -10.

You can tweak a bit the Gamma Red, -2 or -1. Gamma Blue 1 or 2.

Put the file inside the zip in init.d folder. Remember to make it rwxr-xr-x or chmod 755.
[Samsung Galaxy Nexus] osm0sis:
Every panel is different, so it's hard to say "you will not go back" since it probably won't look good on all screen variations. Plus color perception and preference is subjective. Jus' sayin'. ;)
[Samsung Galaxy Nexus] vigan_ks:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

im always using

400

400

400

0,0,0

and contrast -24

does this config. harms my phone ?
[Samsung Galaxy Nexus] osm0sis:
That's what CM technically runs out of the box. Theoretically it could cause more burn-in, or wear out the OLEDs faster, but in reality it would take so long to happen that nobody should care. We're talking like 4 years unless your panel is defective to begin with. So, just like BLX, it won't have any real-life gains during the lifespan of your device since odds are you'll have moved on something else at by 3 years.
[Samsung Galaxy Nexus] Raijin:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Try them and later speak to me.
[Samsung Galaxy Nexus] osm0sis:
No. I'm right about this. There are at least 5 different variations on panel color. I can guarantee those wouldn't look good on mine since I need r < g < b.

And all this talk should be in the color settings thread: http://xdaforums.com/showthread.php?t=1790325. That's where to go if you want to compare color settings for pages on end. :good:
[Samsung Galaxy Nexus] Raijin:
Sure, I've heard that many times. Don't devalue my values because all people post theirs. I'm only using marketing to encourage people. Maybe it fits perfect in the panel of the guy that insert it in his device.

You should have said that before to the other guys. This talk started few hours ago.

I appreciate you so much after reading you every night. Don't follow this.
[Samsung Galaxy Nexus] osm0sis:
I wasn't devaluing them, just advising against blanket statements like "THESE ARE THE BEST POSSIBLE VALUES FOR ALL GNs!" because they're wrong.

In fact I encourage everyone to try your settings, and hopefully they are the perfect fit for others who have a similar panel to yours. But any time someone makes a statement like the above the next 10 posts are "too red on mine", "OMGz it's so yellow", "way too blue", etc.

Sorry I offended you, that wasn't my intent, but if you're going to "market" your settings like that, expect a whole bunch of people calling you out and telling you you're wrong since they won't work on their panels. That's why it's better to just not make blanket statements. Again, no hard feelings. This is just the nature of color settings conversations so I was trying to get ahead of those comments. :)

I didn't see the conversation a few hours ago or I would have suggested moving it then.
[Samsung Galaxy Nexus] Raijin:
:good:
[Samsung Galaxy Nexus] osm0sis:
I know you're a guy and everything, but man, it's nearly impossible to get/stay angry when you're looking at Amy Pond. :laugh::p
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Tried those color settings and my whole screen turned green when I changed the green gamma value. I guess I have one of the other screens :D

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Adjust Trinity contrast first, it's the only thing that gives you some wiggle room with the green RGB Gamma, allowing you to put it below 0.
[Samsung Galaxy Nexus] J-Hop2o6:
I tried this trick before and just now tried it again. Still doesn't work for me going below 0 for Green gamma. This pic still applies lol
[Samsung Galaxy Nexus] osm0sis:
Yeah, it's pretty much a limitation of Ezekeel's interface that's always been there. Best just to leave it alone. ;):good:
[Samsung Galaxy Nexus] Raijin:
The Galaxy Nexus uses RGBG subpixels. There is more green because you have 2 green subpixels. I originally made ​​my adjustments comparing a screenshot of color menu in the Franco app displayed on the screen of my computer and in my phone. Screenshot colors do not vary although colors are customized, so I understand that these are the colors that Android designers wanted. Adjusted it as close as possible, and have those settings often retouched to make them as natural as possible.

Never had the failure of green screen when adjusting the gamma. I hope the Osm0sis suggestion will work for you. And if not, like I'm reading now, hopefully you fix it soon.

I don't understand why I don't have that problem being "a limitation of Ezekeel's interface that's always been there"... This is a software matter, not of different screen panels. :confused:

Hehe, she is very cute. Redheads are the best. Time ago, I had a girl quite like her. You have very good taste. :) Thanks for the work you make here.
[Samsung Galaxy Nexus] osm0sis:
Some people seem to be able to trigger the -1 Green screen and others can't. Franco has and said it's always been like that.

Personally I've found it just depends on what you've got the green multiplier and trinity contrast set to. My suggestion to those that do have it is to play around with those other two settings, and those that don't have it just keep lowering it eventually you'll reach the green-screen threshold. ;)
[Samsung Galaxy Nexus] RevengeFNF:
Those values correspond to this ones?
[Samsung Galaxy Nexus] supernova_00:
So I ended up with 3 hrs and 25 min!!! I've never gotten over 2.5 hours on wifi and 2 hours on 3G...don't even ask about LTE.
[Samsung Galaxy Nexus] _chanstar_:
I heard that it tends to work out best if the above_highspeed_delay and min_sample_time are multiples of the timer rate.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

LOL I get it... I need someone to take a pic of it so I can post but it looks like Kermit the Frog themed

Shiny + Franco 361
[Samsung Galaxy Nexus] LibertyMonger:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Just thought I'd pop in and say Franco kernel has been excellent with Baked BB7, I haven't had any issues, no sod's or anything. Great kernel. When I have tried other kernels I get sod's. Thanks Franco good job buddy.
[Samsung Galaxy Nexus] itasoulas:
+1 excellent battery life! I am using it with modded stock (OVERDRIVE). 3,45 average screen time... I also got 4,20.

row, westwood, oc to 1536, min 192, screen off 384
[Samsung Galaxy Nexus] JBNex:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I think it's time for Stable!
[Samsung Galaxy Nexus] bigbear6708:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

With all the tunable talk a few pages back... (I was lurking) think it may be even better for performance and battery to say set ahd way high and set hs to 1g? It would essentially under clock your phone... But keep the top freqs available... Just in case! BUT I am not a power user so yrmv
[Samsung Galaxy Nexus] Angelakaro:
I was having high idle drain with my previous settings (15/0/75/0.7/45/90/15/80) and i think that the cause is that i setted gohispeedload lower than targetloads,but consumption with screen on was better than stock. Now i'm using 80/80 for go_hispeed_load and target_loads and see if drain is fixed. Do you suggest also to lower min freq to 192 mhz? I saw strange jumps between frequency slots (with franco kernel updater) if i set it to 192
[Samsung Galaxy Nexus] whitedragonz83:
I'd keep the tunables to the ones you posted 15/0/75/0.7/45/90/15/80

How much of a drain are we talking about in change for idle?

If you have 'idle' drain issues, it is an app most likely. Maybe these settings would leave it in a lower frequency state longer, but only the difference of 65% load vs 90% load. Hard to believe that is enough to be significant.

As such, I'd suggest leave the settings and give it another cycle. If you were to lower go_hispeed_load to 80, change target_load to like 70 maybe.

Setting min. freq. to 192 sometimes feel sluggish to me with the screen on, but you should try and see for yourself how it works. It would be helpful a little if you listen to music a lot with the screen off as you should be at that cpu frequency longer.
[Samsung Galaxy Nexus] osm0sis:
A high ahd is better for battery, but now that ghl is so high, you shouldn't put ahd too high or the load w could become excessive from it not reacting soon enough and your device will be visibly laggy. We do have hsf at 1.0GHz on the N7 but the GN seems to get along fine at 0.7 so that's a bit of savings.

It wouldn't be good to have them the same either. It won't oscillate anymore but if you think about it your t_l means it will try to reach 80, then your ghl at 80 means as soon as it does it triggers hsf after ahd ms. You should have a healthy margin between the two, at least 5 or 6 by my tests. With t_l so low at 80 you should at least have ghl closer to 90.
[Samsung Galaxy Nexus] Wynnded:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I'd the read ahead buffer a component being tweaked on the Gnex as well? Sorry, sometimes it's difficult to keep track.

Sent from my Galaxy
[Samsung Galaxy Nexus] osm0sis:
I think read_ahead_kb is still set to 2048 here so it should be fine. On the N7 we trialed it down at 1024, but found 2048 to be best. Tests show above 2048 it actually gets slower again.
[Samsung Galaxy Nexus] Wynnded:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Thank you. Like I mentioned, it can be kind of tricky to keep track of what's being tweaked between the Gnex and the N7. Additionally, in my case, I'm implementing some of those on the kernel I'm running with my ROM of choice as I'm not able to run Franco's kernel with the changes that he's made to the ramdisk. Those changes will not allow this ROM to boot. Glad to be able to hang out here and ask questions though.:D

Sent from my Galaxy
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Ok,thanks for the suggestions. I'm not very familiar with these tunables,the only thing i'm doing it's to try and see which ones are better for me. However,any change i made to tunables make my phone a lot better than with the stock ones. I think next nightly/milestone must be carefully make based on the tunables we are tring,maybe we will find the best combination and we can consider to suggest them to franco

EDIT: again,based on my own experience, i'm using 80 for hsl and 90 for tl cause they gave me more smoothness than 90 hsl and 80 tl

Inviato dal mio Galaxy Nexus usando xda premium
[Samsung Galaxy Nexus] osm0sis:
What ROM is that? I don't think we're aware of any ramdisk incompatibilities since the CM10.1 ones were fixed.

Yeah, that's the general idea. ;) Franco will likely be including our best values for the next GN build like he already has on the N7 side.

It's smoother because you're forcing it to oscillate retardedly to and from hsf all the time. That's not the way to run it. Please go back and read the explanatory posts joaquinf and I linked to so that you understand the tunables.
[Samsung Galaxy Nexus] joaquinf:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Read ahead here is still set to 1048 so we need to bump it manually :)

On a side note, I've been running this setup and I think it could be a winner:

Row/2048

Cpu freq 192/1228

30/90/0.7/45/30/80

Thoughts?
[Samsung Galaxy Nexus] osm0sis:
I'll go ahead and suggest an alternative for comparison testing ;):

row/2048

192/1228

30/95/0.7/45/30/85.
[Samsung Galaxy Nexus] Angelakaro:
I know,i'm reading of tunables since about ten pages (even if,as i said,i'm not familiar just because is the first time i'm playing with them) however,as you suggest,i'll keep 90/80 for a while. Also row is helping ,with deadline i can't feel the same smoothness.

Sh** just read new posts,i'm going to try also those
[Samsung Galaxy Nexus] joaquinf:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

Trying them as I type :cool:
[Samsung Galaxy Nexus] whitedragonz83:
Re: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I did 192 min for a few days. Seems fine. I still like 15/90/0.7/45/30/80 better then going 30/95/0.7/45/30/85. Might try a bit more but used the other settings all day yesterday and it felt good
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel-r361 -&gt; 4.2 | r300 -&gt; 4.1

I'm tring osmosis and joaquinf setups,but they're very similar,i can't notice any difference. However both the setups are quiet slower compared to the previous

Inviato dal mio Galaxy Nexus usando xda premium