yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] yellowdie:
True. If you have Force GPU Rendering on (which you should because it makes things that much smoother), then you'll see things improve overall, but not hugely so. Going from

384 with Force GPU Render

to

512 with F.GPU.R

is not as much of a difference as

384 withOUT F.GPU.R

to

384 WITH it

. Does that makes sense?
[Samsung Galaxy Nexus] wavedashdoc:
Same here. Though this new kernel flat lines even better than r282 so that is more important to me.
[Samsung Galaxy Nexus] --__LoRiS__--:
Franco i have a question for you: is there any improvement turning off overlay HW and forcing GPU rendering??
[Samsung Galaxy Nexus] yellowdie:
That's odd. My Franco app has the 1036 option, so I'm not sure why yours doesn't show it (see attachment). :confused:

And the reason I only need 1036 is because in the past, I would run 384 as the min and 1.3-1.4 as the max because it felt like it was slower without going into higher speeds. But when I tried setting the min up higher, it made the phone feel SOO much faster, that I realized I didn't need high clockspeed to do normal day to day stuff. It was only slow when it was running at 384. So after playing with it for a while, I realized that 729-1036 feels a lot faster than 384-1420 and uses a LOT less battery. Really, give it a try for a day and see how it feels.

:):D:laugh::good:

As for the Gov, I use Interactive because it's what Google and The Boss Man recommend. :)
[Samsung Galaxy Nexus] franciscofranco:
Not a single idea about that.
[Samsung Galaxy Nexus] sruel3216:
yup i agree with everything you say. i always use 729 or 700 on other kernels. much bettter then 384 or 350 performance wise, whille not effecting battery. default screen off is 700 from google btw. so people saying 729 is too high, is false. correct me if im wrong
[Samsung Galaxy Nexus] yellowdie:
Yep, you are correct. 7xx is stock because of the "race to idle" debate. If you set screen off max to 3xx (like I used to in the past), it will take longer for your phone to finish what it's doing before going into deep sleep (which is obviously the best place for it to be). But if you set the screen off max to 7xx (which again is stock) it will work harder, yes, but it finishes the tasks faster, therefore it gets into deep sleep faster, thus you save more battery by letting it work harder. :highfive:

:):D:laugh::good:
[Samsung Galaxy Nexus] osm0sis:
Yeah, I realize/agree it makes no sense, but I really didn't notice the difference until r281, which is why I thought maybe something else other than just removing the vfs and lmk tweaks was a factor in it becoming more laggy. r283 does seem to be good again, but perhaps not quite back to what r275/6 felt like. I'll have to flash back to those two and see if my feeling is right.

Disable HW overlays will remove the buffering of Project Butter, so should actually make things worse. Force GPU rendering can improve performance in apps that don't explicitly use GPU rendering already; the flipside being it can reduce stability in those that handle the switch poorly.

I use Force GPU rendering, and also set Transition animation and Animator duration scales to .5x. The animation tweaks really make things feel snappier.

I think the real question is when you have your min jacked up to 729MHz, will it still use lower frequencies when the screen is off? Since if it only needs to wake up and run at 384 to get the job done (instead of being pushed to the screen-off max of 729MHz), using a lower min might still be better overall with respect to idle battery drain.
[Samsung Galaxy Nexus] yellowdie:
And you changed the vfs back to 300! But that shouldn't cause any problems. lol

Franco, thanks again for all your amazing work. :D
[Samsung Galaxy Nexus] sruel3216:
yes i am all about race to idle. i was trying to explain this to some guy in the codenameandroid forum and he just refuses to believe that 700 is ideal. i cant even tell a difference in battery when playing music.

my settings are:

729min

1228max

interactive

input_enabled (franco is on by default i believe)

hispeed_freq 1036

**** is smooth
[Samsung Galaxy Nexus] yellowdie:
I completely and totally agree. I have my animations settings the same.

I don't think so because the min overall is 729, but I think the battery used there is negligible. And the battery saved by way UNDERclocking the max makes a much bigger difference. :)
[Samsung Galaxy Nexus] sruel3216:
no it wont use a lower slot, 384 for screen off, if min is 729. 729 is default from google and performs the best for me
[Samsung Galaxy Nexus] GCbard:
Lockscreen weather not working with franco 283 on CNA 3.6.6. I even reflashed the rom with a full wipe and it is broken with 283. Works with 283 though.
[Samsung Galaxy Nexus] yellowdie:
Well tell the dude at codenameandroid: "Hey, Google (you know, the big guy that write all this junk) sets their max screen off to 700, so there must be a good reason for it."

But I have to disagree with you, four stars in a row is not very smooth at all. Just look at all the pointy parts of those stars. [****] that is not what I would call 'smooth.' Just sayin'...

:p:silly:
[Samsung Galaxy Nexus] rodnar77:
My phone has been awesome

No lag, no WiFi issues.... great battery. Thanks Franco!

BTW.... normal usage.... gmail, text, twitter etc.... limited gaming,usually while plugged in though
[Samsung Galaxy Nexus] yellowdie:
lol. "broken with 283 but works with 283." You sure? :p

Just givin' you a hard time. I don't think a kernel affects lockscreen weather in anyway. I'm running CNA 3.6.5 with r283 and my weather is fine. :cowboy:
[Samsung Galaxy Nexus] TEK112:
Agreed.

To yellow, try wiping both caches.
[Samsung Galaxy Nexus] osm0sis:
Those who felt r283 was a bit laggier again should try bumping vfs back up to 1000, since people still felt r282 was better with that tweak even though lowmemorykiller was still running at the lower values.

No, 729 is the default screen off max from Google, which I agree completely about regarding race-to-idle, but I'd guess that you're right regardless about it probably not using anything lower than your global min if you also have that set to 729 as well. Just too bad, in a way, that we don't also have a seperate screen off min that we can set.
[Samsung Galaxy Nexus] slvrarrow:
A ridiculously high vfs cache pressure, eg 1000 hurts battery because the phone is more regularly functioning to clear caches where it would ordinarily be idle. I saw a couple of people complain about idle drop using 282. Default is 100 and 300 i would say is more than enough if there is to be any change at all.
[Samsung Galaxy Nexus] yellowdie:
Wait, what? I don't need to wipe anything, my junk is fantastic. :) It was the guy I was quoting that had an issue.

Yeah, I agree. That would make a hecka lot more sense. Two maxes, one min... hmmm... :rolleyes:
[Samsung Galaxy Nexus] Wh1t3Rose:
Zenzip use a lower brightness setting. That will help a lot. Also lower your max clock speed. Too high IMO. I use 230-1036. Feels great.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] GCbard:
lol. I meant works with 282. It's working though.
[Samsung Galaxy Nexus] mssam:
I believe the point of that conversation was when it comes to custom kernel/rom combinations, there are different ideas and differences of opinion, on what's most efficient all around. :)
[Samsung Galaxy Nexus] ChazzMatt:
A week or so ago I went with your 729 minimum recommendation, but I still OC the maximum to 1305. (1305 seemed to be the "prudent" OC for reasons I can't immediately find. Something about some internal adjustments maxxing out at 1305 and not supported any higher?)

Running interactive governor for same reasons you are.

Still a little confused about the governor control sub-menu. But this is what I have:
[Samsung Galaxy Nexus] osm0sis:
The current implementation of SR has limitations and isn't built to calibrate high OC frequencies, so franco has disabled SR for those above 1305. That's probably what you were thinking of. :)

Running hispeed and input_boost freqs at 1228 seems a bit bold, but should definitely make things smooth at the expense of battery. Reducing your hispeed delay to 40000 (from the default 100000) means it'll ramp up to 1228 after going over your hispeed load of 50% for that amount of time, even though it might have been able to handle it at 1036, that might be costing you a bit too much battery that way. I personally just bump the hispeed freq to 1036 from the default 729, and leave input_boost and everything else at their defaults. Seems to work well.
[Samsung Galaxy Nexus] TEK112:
How very diplomatic. :fingers-crossed:
[Samsung Galaxy Nexus] burner07:
off-topic: I want to recommand my color settings for pure white imo:

-red:290

-green 200

-blue 350

-rgb stock franco

-trinity :5

-omap4 :1.2
[Samsung Galaxy Nexus] F_T_B:
Francisco, the latest kernel version tops at around 6450 points in Antutu on my Nexus (384GPU), and seems pretty consistent overall with maybe a touch of lag here and there due to my apps. Deep sleep works (as expected).
[Samsung Galaxy Nexus] yellowdie:
Yep, what osm0sis said about Smart Reflex is probably what you're thinkin'. As far as the other details, check out this page: http://xdaforums.com/showthread.php?t=1369817. Do a browser Find for '5.INTERACTIVE'

This is the gist of it:

i) hispeed_freq - Hi speed to bump to from lo speed when load burst. (Default value is scaling max freq)

ii) go_hispeed_load - Go to hi speed when CPU load at or above this value. (Similar to Up-Threshold in other governors)

iii) min_sample_time - The minimum amount of time to spend at a frequency before we can ramp down. (Sounds like Lazy governor?!)

iv) timer_rate - The sample rate of the timer used to increase frequency.

My recommended settings:

Min: 729

Max 1228

Highspeed_freq: 1228

go_hispeed_load: 50

input_boost_freq: 1036

min_sample_time: 40000

timer_rate: 20000

What that means is when you touch your phone, it spikes to 1036 (that way you get a smooth feeling all the time), and when you're phone gets to 50% used it spikes to 1228 to bump you up to handle harder stuff.

Right now I'm actually testing:

Min: 729

Max 1036

Highspeed_freq: 1036

go_hispeed_load: 50

input_boost_freq: 729

So far it's great! Spend all my time at those two settings and deep sleep. Phone runs amazing smooth and my battery wants to kiss me. :highfive:

:):D:laugh::good:
[Samsung Galaxy Nexus] mssam:
...you know the business... :)
[Samsung Galaxy Nexus] bat0nas:
FEATURE REQUEST:

Franco, could you make your kernel a bit slower? :) But dont say that in the release notes.

I bet everybody will tell you that new version runs faster :D:D

LOL

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
I'm still waiting for him to repackage the original stock kernel and release it as one of his new ones. :)

"OMG, Franco, this new kernel is soo kul! hows do you do it? its sooo better than the stock one!!! wow"

:cowboy:
[Samsung Galaxy Nexus] teriemer:
Well .... After some intensive testing (opening apps and browsing) I'm must admit I'm back on r276 w/gpu384. Min/max frq 729/1228 and phone is great. The main reason for switching back is that rendering on webpages it better with r276. The responsiveness is the same imo.
[Samsung Galaxy Nexus] sk8oldschool74:
Maybe behind but r282 nice... Like figure a couple days to know for sure....
[Samsung Galaxy Nexus] hotnikkelz:
Ok. 283 is awesome coming from 277. Wifi is stronger more reliable and my battery drain on idle time with wifi on is better. Thanks man. Ready for a milestone 6. Btw all nightlies have been smoothe to me so it's hard to discern
[Samsung Galaxy Nexus] simms22:
thanks for the maturity that you are showing, oh i mean immaturity. obviously the quality of the kernel is exemplified by the people, friends, posting in a thread. trinity kernel is obviously not for your device then since immature people post off topic in a thread. btw, thanks for reporting the thread for posting off topic, a lot of good that did.
[Samsung Galaxy Nexus] yellowdie:
lol. Simms, I totally agree. Gotta love people maturity levels...

Both threads, Franco and Trinity, are where I live, and I read them both equally every single day (okay, that's a lie, it's more like every single hour (sometimes minute)).

:):D:laugh::good:
[Samsung Galaxy Nexus] wai10691:
r283 is so much smooth. Thanks
[Samsung Galaxy Nexus] akaleshnikov:
r277 was a nightmare for me

r283 is buttery smooth...and I mean SMOOTH. Running 384/1.5 + 512gpu + dyninteractive = ohhhh yessss
[Samsung Galaxy Nexus] sk8oldschool74:
I agree on most being stable just wifi and deep sleep well 282 is snappy compared to281... Guess I will have to try 383... Did you change anything or running kernel as is?

---------- Post added at 12:37 PM ---------- Previous post was at 12:36 PM ----------

Did you change anything? What rom are you running if you don't mind me asking?
[Samsung Galaxy Nexus] ChazzMatt:
Thank you for your answers, both of you.

Yes, the SR is what I was thinking of, for the 1305 overclock.

Still sorting through everything but I think I understand better. Thank you.
[Samsung Galaxy Nexus] sruel3216:
hahah i thought s h i t was smooth tho.

---------- Post added at 12:58 PM ---------- Previous post was at 12:56 PM ----------

how do you tweak vfs?

thanks

---------- Post added at 01:01 PM ---------- Previous post was at 12:58 PM ----------

hahahaha stalker!!!

im trying francos again now lol
[Samsung Galaxy Nexus] dracon6ai:
Rom Toolbox Pro is what mine is. By Jrummy.

On topic now. R283 is running like a champ right now. I put VFS Cache Pressure to 10 just to see how'd it ran and I have had no issues at all so far. Going to play with freq's and govs a bit now. Everybody's talking about it now so now I'm curious. Lol. 3rd party mind games. :eek:

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] nuwan32:
Yea but this sucks if you listen to music since it'll use 729 and that drains so much battery specially if you listen to music for 2-3 hours a day
[Samsung Galaxy Nexus] yellowdie:
I can see that. One thought would be to set up custom Power Modes in Franco's app (or there are alternatives) and have it running 729 min most of the day, then just *click click* change modes to Music and start playing it, then take five seconds afterwards (or later in the day) and change it back. It's a few extra seconds, but it makes your phone faster overall and saves battery. But it's all personal preference. :)
[Samsung Galaxy Nexus] boki2911:
can someone write some good settings, the balance of performance and battery life, thanks
[Samsung Galaxy Nexus] sruel3216:
idk i have been getting very good battery life while listening to music with 729 as the min. i listen to 2-3 hours a day. at the end of the day i easily have 50% left. I feel like the phone is not working hard at all to play the music even though its at 729

---------- Post added at 02:08 PM ---------- Previous post was at 02:05 PM ----------

the last few pages have many settings for performance/battery

mine is

729min

1228max

interactive

input_boost enabled (on other kernels. default is on in francos)
[Samsung Galaxy Nexus] mssam:
lol...what a coincidence, so am I - r18. Haven't had a chance to use r283 yet. Probably try it a little while...

Sent from my Nexus 7
[Samsung Galaxy Nexus] yellowdie:
Nuwan, I would be interested to see what freq you're actually listening to music at. Turn your music on, open CPUSpy, reset the timer data (from the menu), then turn off your screen and listen to music for a bit without turning your screen on. Then turn it on and refresh (not reset, lol, done that before) CPUSpy and see what freq you were running while playing music with the screen off. Then set your min cpu to 729 and try the process again. :)
[Samsung Galaxy Nexus] mssam:
@sruel3216, all right I'm on 283 and I just set the min/max to 729/1228, as well as some of the other settings suggested by others. Let's see how it goes...
[Samsung Galaxy Nexus] BigBake88:
Is 283 as good as 275/276? Still rockin it because it is so good. Haven't had an urge to flash any updates lol
[Samsung Galaxy Nexus] IgnorantNerd:
R283 is definitely smoother and faster than previous nightlies but it feels like my battery is draining faster than ever. I hope it gets better after a full cycle because the performance is really good.
[Samsung Galaxy Nexus] CaspaTheGhost:
I've been a 729 min advocate from way back and I don't think it has a major impact on battery whilst listening to music, at least that was the case when I did some testing.

Have to say that 283 is running very well at the moment, proper feedback in due course.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] slvrarrow:
2hr 40 screen on with 4hr 30 total usage 60 percent remaining. 2g, on wifi. 1036mhz max 384 min. Smooth as butter. Browsing, whatsapp, Ricky Gervais show on Google music in background. Cm10

---------- Post added at 12:37 AM ---------- Previous post was at 12:34 AM ----------

About your gapps, are all the icons and stuff stock? The only ones I've seen beforehave like a cyan mmessaging icon for example. All gapps/stock apps with just inverted backgrounds and text is what I'm after
[Samsung Galaxy Nexus] drawde40599:
Franco stock setup. ....
[Samsung Galaxy Nexus] nuwan32:
It uses the lowest available, not deep sleep
[Samsung Galaxy Nexus] osm0sis:
Even with the altered lowmemorykiller, I still feel like r283 is kind of laggy/stutters at times on 384GPU where it wasn't with r275-7.

Oddly enough, echo 500 > /proc/sys/vm/vfs_cache_pressure still seems to improve things a fair amount, especially in the app drawer and homescreens.

Now I know in r275 vfs was at 300, and lmk was roughly where it is now in terms of minfree values, so I wonder if some of the lmk stuff that got reverted was actually helping? Or if there is something else that happened with r281 that is slowing things down; the gpu sync, or something from 3.0.44?
[Samsung Galaxy Nexus] franciscofranco:
I don't feel any lag or stutter :(
[Samsung Galaxy Nexus] 11768:
How come hispeed_freq will always overwrite input_boost_freq? For example, I have min freq at 386mhz, input_boost_freq at 729mhz, and 1036mhz for hispeed_freq it will still pump the cpu to 1036mhz whenever the screen is touch although the load is below 50% (the default threshold)?
[Samsung Galaxy Nexus] joaquinf:
r283 (512gpu) from yesterday is running like a boss. Silky smooth and performance is just amazing. I think I'll be flashing 512 versions from now on

Great nightly Francisco
[Samsung Galaxy Nexus] osm0sis:
Just loaded r277 and r276 into the kernel_backups directory and switched between them and r283... both are definitely smoother. I can't explain it, since I know r277 has the lower lmk minfree, but it's still somehow faster than r283, and then r276 seems even faster.. :(:confused:

Edit: Huh.. seems like r276 even has the lower lmk values.. this **** is crazy. Somehow it smokes!
[Samsung Galaxy Nexus] sruel3216:
haha. let me know how you like it, either here or in the cna forum lol
[Samsung Galaxy Nexus] Antob125:
So are people who weren't able to run 512gpu, able to run it now?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sruel3216:
idk but i have the same thing. i set my input_boost to 1036 and hispeed_freq to 1228. it goes to 1036 and about half a second after it spikes to 1228. but if i set the hispeed_freq to 1036 its fine and will still hit 1228 when there is a heavy load
[Samsung Galaxy Nexus] CADude:
I have a feature request for Franco that I think a lot of people will agree upon.

Instead of just relying on the backup feature in the updater app, can we also have an interface where we can choose which recent nightly we want to auto flash instead of just the latest one?

It would really make things easier for people who try the latest nightly but had a better experience with the one before it and forgot to back up.
[Samsung Galaxy Nexus] RoscoeDpG:
i feel bad because i never notice anything wrong with the newest nightlys lol i have got more use/batt life off the last 2 so thats a plus and smooth so im good :D
[Samsung Galaxy Nexus] Wh1t3Rose:
My battery today. 20% on 4G 80% on WiFi. Only at 50%. I'm on 281. Should I stay?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] franciscofranco:
Because the device boosts up to hispeed_freq if the load is above go_hispeed_load.

I thought about it first, but I decided not to do that. I want people to use the latest nightlies and not just wander off in older ones. If one wants to run other versions best to back it up first, thats why I designed that interface in the first place.
[Samsung Galaxy Nexus] sruel3216:
thank you for the reply
[Samsung Galaxy Nexus] mixtapes08:
I know right.. I have the nightly 249,268,276,277 as my favorites. 268 is my most favorite of the 4 when it comes to battery and performance

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] hotnikkelz:
As is. I usually use default settings when I'm testing a new nightly to see how things go.
[Samsung Galaxy Nexus] timbck2:
I am.
[Samsung Galaxy Nexus] dracon6ai:
Got a new max. Definitely not my day to day settings that I used to hit these but good to know I can if I needed. Another grand slam by Franco via r283. And I know benchmarks mean nothing but damn do numbers like that make me tingle inside. Also my regular settings are giving me some of the best battery I've had (still playing on Wheatley and got VFS to 10).

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] sk8oldschool74:
What make is this?
[Samsung Galaxy Nexus] gaich:
I know,there`s no much screen time, but, in general, 283 makes me optimistic! More than 17 hours and 74 percent left.
[Samsung Galaxy Nexus] Wh1t3Rose:
Stock battery #281

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] shawnaye:
I'm not sure exactly if my gnex is a magical flying unicorn or anything. But I've never experienced any stutter EVER using the xda app.

I've absolutely no idea what people are talking about whenever they post 'xda stutters, help!'

It's a small stutter. Does it completely prevent you from browsing the forum/pages?

If so bump up your frequency or close some background apps!

Small stutters I can definitely live with, but not how laggy it is when I launch chrome or whatsapp.

Cmon guys. Stop whining over how small stutters still occur with every nightly.

UNLESS it's a huge issue. Then I stand corrected.

Just my two cents. Hope you guys can understand how irritating it is to continously see the word stutter every single day.
[Samsung Galaxy Nexus] dracon6ai:
Made a typo. I meant R283. That benchmark set up was:

R283 384gpu

Wheatley 1228min-1728max

Fsync off.

Those were the only changes I've made besides the VFS to 10. Might of got higher with the 512gpu but I'm content for now.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] Pkt_Lnt:
In franco app, under power profiles, activate the Music one and see the settings. 384/384, music does not require much cpu to play.
[Samsung Galaxy Nexus] CADude:
Fair enough. Just thought I'd ask. I'll try to keep backups from now on.
[Samsung Galaxy Nexus] 11768:
But the problem is my load is below 50 percent according to Cool Tool cpu load monitor.. It just pump up to 1036 without going through 729.

For example, just a simple touch on the screen will jump up to hispeed_freq instead of input_boost_freq.
[Samsung Galaxy Nexus] Fenvarien:
Yes, 512 GPU works great now (for my phone).

GNex with franco.Kernel / MiNCO ROM
[Samsung Galaxy Nexus] Kappa Lamda:
r283 looks great for me with Baked blackbean-5

Great battery life/performance. Phone feels a lot smoother

thumps up :thumbup:
[Samsung Galaxy Nexus] CaspaTheGhost:
Mine is like you've seen, so the cyan coloured icon for MMS. I'm without a laptop at the moment so haven't been able to update them so the MMS doesn't have quick reply, I'll update as soon as I can (need to change Wallet and TiBu and check everything over for versions).

The icons shouldn't be an issue though as they are easily changed, I personally use Nova with Tersus icons.

Using the same combo!

Sent from my Galaxy Nexus