yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] timbck2:
I had refrained from playing with the governor control settings because there were so many different sets of settings flying around, everyone had a different opinion on which settings were best. Now that the dust seems to be settling a little, I decided to give them a try and wow! I can really feel the difference in my phone's smoothness and responsiveness! For the record, I'm on nightly r295 on Affinity Series ROM with dyninteractive governor and the settings 20000/50/40000/20000. (I get the impression that the general consensus is now that those are close to the optimal settings, please correct me if I'm wrong.)
[Samsung Galaxy Nexus] dracon6ai:
Thanks for the heads up, I moved it down to 775MHz and SR seems to like to run it on that (at least according to Franco's app). Will go down to 725MHz now to see how it goes.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] osm0sis:
Just to clarify, SR is limited to 830mV as a lower limit so by putting 192MHz lower than that, it's outside of SR entirely. :good: :)
[Samsung Galaxy Nexus] pkgnex:
I wasn't too scared! My phone has only come close to scaring me once... a mod I tried got me stuck a boot-loop coupled with a loss of my on-screen soft keys... but I digress.

My rationale for the slot-mismatch / heat correlation was that I've auto-flashed every Franco nightly since r230, and this has only happened to me once before... and that was when I was flashing back from LeanKernel (had to try it just to confirm Franco's better, right?) to Franco and I had to go back and re-configure all the frequencies.

You may be right that there is no relationship... but my anecdotal experience, statistical-sample size of 1, and uncorroborated wild inductive reasoning seemed to fit right in with other noobs in this thread, so I figured I throw it out there!
[Samsung Galaxy Nexus] IAmAN00bie:
Don't use dyninteractive. It automatically overrides those settings. Use interactive instead.
[Samsung Galaxy Nexus] joaquinf:
On a completely different note. Guess who is in the most thanked post of all time podium? :p

That was a hell of a post, very informative and user friendly :highfive:

Thanks again yellowdie and all of you who thanked him. That's the kind of things we need to encourage and we should learn from.
[Samsung Galaxy Nexus] yellowdie:
Actually, what we've semi settled on is 60000/70/60000/30000 (That's r295 defaults now). And for now, you should try Interactive not Dyninteractive. :)
[Samsung Galaxy Nexus] pkgnex:
Also... I think the consensus (if there really is one) is what Franco set as the new default in r295, namely:

60000/70/60000/30000
[Samsung Galaxy Nexus] jjhiza:
Hey guys, quick question in regards to Yellowdie's summary post on pg. 3046:

I use ROM Toolbox Pro for many systctl tweaks, and I'm interested in trying out the governor tweaks that were presented in that post. However, my hispeed freq is well over 1 million by default (interactivex/sio combo), and I was wondering if there is a recommended value for that particular category. I've set up all the other values, and things seem to be running alright, but when I lower that particular frequency, I start experiencing a fair amount of system wide lag. Again, could someone recommend a value, and also explain a bit more about what hispeed freq does? Thanks in advance guys, and keep up the great work that's going on here!! :)
[Samsung Galaxy Nexus] yellowdie:
That's so awesome. I have been beaming ear to ear all day. Lol. Thanks! I am glad the summary post was helpful to people. :) This has been a fun party! But we're not done yet!
[Samsung Galaxy Nexus] Blackcrx:
wow, so much to read and absorb in the past 24hours. I have been trying all the suggested settings from 192-1228 6/7/6/3, input 1036, hi load 729 (also tried 1036 and 1228) . Seems a little laggy compared to what I'm used to. The lag is most noticeable during text messaging or whenever the keyboard is being used. May I please ask why you guys are testing such low cpu speeds and undervolting? Just for battery life I assume?

I went back to my old settings of 729-1228 6/5/6/3, input 1036, hi load 1036. With these settings I can still get a full day of use with 2-3hrs screen time and about 30% battery remaining by bedtime
[Samsung Galaxy Nexus] The Gingerbread Man:
So if I understand your saying we should set the 192mhz voltage to 830mv in the CPU frequency tab and smart reflex will take care of any voltage change if it wants and on reboot make sure we apply the voltage again because voltage changes won't stick accross reboots?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
:D

---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------

Hispeed_freq is what clockspeed your phone jumps to when it gets under load. You should have it at 1036800. But I recommend clearing all your other tweaks and try r295's default settings for a bit. :D

---------- Post added at 06:43 PM ---------- Previous post was at 06:41 PM ----------

No, set it to 725 or 750. SR can only go down to 830, so if you set it below that, the that specific freq is taken out of SR's control. :)

---------- Post added at 06:47 PM ---------- Previous post was at 06:43 PM ----------

Start with the summary post on page 3046. I would link you to it but I am on my phone right now. That should help get you up to speed (literally! Lol)
[Samsung Galaxy Nexus] The Gingerbread Man:
OK set to 725 will see how that goes. I ended up confused as previously 230 was hard coded to not be smart reflex and 192 freq hasn't so I thought we were trying to control it by smart reflex.... just need to remember to set CPU voltage on reboots now then I guess :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Exactly right. :) Because...

:good:

As for setting UV on boot there is a sysfs command I discovered for that awhile back, but you should apply your voltages manually for a few days to make sure it's stable on your device first.

echo "1450 1425 1400 1300 1250 1275 1250 1225 1150 1025 725" > /sys/class/misc/customvoltage/mpu_voltages;

Running that via init.d while leaving SR enabled will selectively UV 1536MHz@1300mV, and 1420MHz@1250mV (since SR stops at 1305MHz), as well as 192MHz@725mV. All others remain under SR.
[Samsung Galaxy Nexus] The Gingerbread Man:
Right I'm with you now must of missed that post, thanks for clearing that up for me!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] yellowdie:
Correct, 230 was taken out of SR manually by Franco. But this post from 20 pages ago will help:

:) That's actually what started THIS WHOLE THING!! :D lol

---------- Post added at 06:55 PM ---------- Previous post was at 06:53 PM ----------

How could you possibly miss a post?! I mean, it's not like there's one every thirty secon....oh wait.

---------- Post added at 06:57 PM ---------- Previous post was at 06:55 PM ----------

btw, joaquinf, yesterday I was excited because I hit 200 Thanks and 400 posts. lol.
[Samsung Galaxy Nexus] timbck2:
Thanks for the tip! I wonder why my experience changed when I changed those settings then? I know it's very subjective, but I don't think it was just a placebo effect, it was very noticeable. Hmmm...
[Samsung Galaxy Nexus] ciprianruse88:
Franco,i just updated to kernel updater 7.1 app but still if i set my color profile,after reboot the colors change to stock franco kernel.please, if you can add an ,,set on boot'' option to the color manager in the next update it will be much apriciated :good:
[Samsung Galaxy Nexus] osm0sis:
No problem! This place is a mad house, I'm very nearly missing my own posts. :p

Haha yeah that's crazy, very nice posts-to-thanks ratio you've got there sir. ;):)
[Samsung Galaxy Nexus] The Gingerbread Man:
haha I see :p well we have made good progress then for 20 pages of work and congratulations on your thanks meter it will grow quickly I'm sure ;)

If you use supersu app and update the binary instead of using super user app it should work

Sent from my Galaxy Nexus

---------- Post added at 12:21 AM ---------- Previous post was at 12:18 AM ----------

I'm aiming for 'recognised spam bot' title as mine is no where near as good, 1000s of posts and a select few thanked, mostly jokes these days and had quite a few from my x10 days :rolleyes:

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ciprianruse88:
i've never use superuser.i am on super su.the cpu changes are loading on boot but not the color changes.with trickster mod app works fine but i want to use franco app.
[Samsung Galaxy Nexus] EDNYLaw:
Just to their in my two cents, I'm at 715mv for 192 and totally stable. For my script I also put a sleep 60 line in there via ROM Toolbox to give me a minute to disable the script should it become unstable. Just a little hedge against bootlooping.

Sent from my Galaxy Nexus using Xparent Blue Tapatalk 2
[Samsung Galaxy Nexus] Savant:
Trickster can be overriding Franco's app so do a boot delay or you're going to uninstall one of them.
[Samsung Galaxy Nexus] ciprianruse88:
i've just tested with trickster to see if it works but i unistalled it.it just doesn't work with franco app
[Samsung Galaxy Nexus] Savant:
Yeah I put mine on boot delay then it works perfectly fine.
[Samsung Galaxy Nexus] dyepnoodle:
everything is just a placebo. :)
[Samsung Galaxy Nexus] ciprianruse88:
where is the boot delay option because i can't find it in the app?thanks for the replyes
[Samsung Galaxy Nexus] Savant:
Its under the boot option and if you didn't donate you won't be able to see it.
[Samsung Galaxy Nexus] ciprianruse88:
now i've found it.i think i'm really tired :).Thanks!and yeah...i hit the thanks button :)
[Samsung Galaxy Nexus] Savant:
Yeah no problem .
[Samsung Galaxy Nexus] Wynnded:
I'm sorry guys, but where is it? In Franco's App right? Under what heading? Sorry, somehow I'm just not able to spot it....:silly:
[Samsung Galaxy Nexus] L-ViZ:
Westwood is better in the test. for which reason is cubic the standard one? more stabality, using less cpu power. call me a noob, but the results are better with westwood, so i just asked myself why cubic is preset.

cubic:

1st run: 15ms - 10,75Mbps - 7,82Mbps

2nd run: 14ms - 10,84Mbps - 8,06Mbps

westwood:

1st run: 11ms - 17,65Mbps - 8,30Mbps

2nd run: 13ms - 13,28Mbps - 8,29Mbps
[Samsung Galaxy Nexus] osm0sis:
Hopefully I'm not spoiling the surprise here for anyone who wasn't following the last cluster**** of settings pages and changes ;), but a newly tweaked deadline is now the default IO scheduler in r295. Now, I could be mistaken, but I think switching back to bfq still makes things a bit smoother in the app drawer and scrolling menus.

echo "bfq" > /sys/block/mmcblk0/queue/scheduler

Thoughts?

With bfq back in the mix I'm finding 192MHz min and franco's new default tunables quite bareable, even lowered my hispeed_freq back down to the default 729MHz (from 1036MHz where I've had it almost since switching to franco.Kernel, ages ago). Apps drawer still seems a little slow to move that first page at times, but no worse than 230MHz. Between the lower hispeed_load and my nice selective UV of 192MHz@725mV, I'm very much looking forward to testing the battery life of this release. :D

Well first, when you're talking TCP Congestion Control, throughput is just one metric for testing. For example, an algorithm may perform best for speed but fail at other things like # of packet resends. Your question has a pretty straightforward answer though: Franco has the default at cubic because that's what the Linux kernel has for a default. I do prefer westwood myself to the other ones available just based on "feel" though. :)
[Samsung Galaxy Nexus] Savant:
Its in tricksters app under boot settings.
[Samsung Galaxy Nexus] Wynnded:
Ahhh, I didn't pick up on the fact that it was in a different app. Thanks.
[Samsung Galaxy Nexus] Savant:
Yeah its not a bad app free and made for the nexus. http://xdaforums.com/showthread.php?t=1768315
[Samsung Galaxy Nexus] Sik-1:
1350-1050uv

1228-950uv

1030-900uv

729-850uv

384-800uv

I run much lower on my wife's phone, when I get a chance I'll post those also.

But I can't seem to get them to stick on boot :confused:

I'm hating having to reboot and reapply those even tho its a couple clicks lol
[Samsung Galaxy Nexus] franciscofranco:
Yes its not made to be set on boot by design.
[Samsung Galaxy Nexus] L-ViZ:
tested it myself, westwood felt more responsive :) just love the speed of the gnex, it´s getting closer n closer to desktopspeed :)
[Samsung Galaxy Nexus] yellowdie:
Interesting, I don't know if there's a difference but I've always echoed UVs to /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table. I just looked at both files and they look the same, but I'm not sure which one would have "rank" or if they are the exact same. :confused:

On r290 or r292 (don't remember which), Franco made some "secret sauce" changes to deadline and stuck it as default. I haven't tried going back to bfq, but it sounds interesting. I'd be interested to get Franco's thoughts on what he changed and how it applies. :)
[Samsung Galaxy Nexus] gm007:
I tried several interactive settings and those one is the best for performance
[Samsung Galaxy Nexus] jjhiza:
Thanks for the quick reply. I'm running much better since readjusting the hispeed freq to the value you suggested. I'm privately testing a pre-release version of a new kernel, and I'm playing around with anything that could possibly help make it better, but I have no aversion to running Franco kernels in the future. Thank you again for your help...I really appreciate it. :)
[Samsung Galaxy Nexus] osm0sis:
If I recall correctly, /sys/class/misc/customvoltage/mpu_voltages is where the updater app writes them to, and if you check it out, iva and core are in there too. One stop shop for UV on boot. :)

As for the newly tweaked deadline, I think it was r292. I'd love to hear what the differences are too, all I see on the github is a boolean switch change turning off "front merging"? No idea what that is though. Either way, I think bfq definitely feels a bit smoother with 192MHz as min freq. :good:
[Samsung Galaxy Nexus] yellowdie:
@The Gingerbread Man: Totally off topic, but I have to admit, everytime I see your name, I read it as GB-Man and I think of this. lol. :cowboy:
[Samsung Galaxy Nexus] SpecRek9:
Hi Yellowdie, some pages ago I read you asking FranciscoFranco wheter r295 should be used on 384 or 512, though I've been searching and couldn't find the answer, now, I've just flashed r295 on GPU512 since I'm playing some graphic intense games, my question is: Should I run 295 on 384 or 512?

Thanks a lot :)
[Samsung Galaxy Nexus] osm0sis:
The idea was 384GPU would be preferred if you want to help us test out the new tunables and other changes, since with the slower GPU clock you're more likely to feel the effects of them. You can do what you like though sir. :)
[Samsung Galaxy Nexus] Antob125:
I use these settings on r290. 729-1228

Should I be changing any of this on r295 to match the speed I get now?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] SpecRek9:
Oh!, I'm sorry not being able to help, I don't own any credit card, so I can't buy the app from the market, I just use the Franco kernel as is released, sorry :(
[Samsung Galaxy Nexus] yellowdie:
Yeah, Os is right. the r294 test build was only 384, so if you want to compare 294 and 295 then you want 295/384. If you're not "testing" then you can use whichever you prefer normally. :) I'll switch to 512 once we're done with all the testing stuff.

That's totally okay, dude. You can still test it and see. r295 has the settings we've been talking about built into it. You can also install TricksterMod from the Play Store and use that to change the Gov settings. :)

I would try r295 with the default settings and see what you think compared to what you were running before. It's pretty nice!! :highfive:
[Samsung Galaxy Nexus] osm0sis:
Again, totally up to you. Preferrably please try out the new defaults by unchecking set CPU and Governor settings on boot, rebooting, then dropping min to 192MHz to mess around with the tunables and feel their effects. Let us know if you think you've come up with something better! That's how this all started. :)
[Samsung Galaxy Nexus] yellowdie:
Os, I just wanna give you a big virtual high five! :highfive: lol
[Samsung Galaxy Nexus] osm0sis:
Here's the lowdown on front merging/IO schedulers: http://sylab.cs.fiu.edu/_media/paperclub/lkd3ch14.pdf - Pg 299 (11), they talk about what merging is. Then they talk about deadline next.

"Performing front merging is optional in the Deadline I/O scheduler, however. It is not always worth the trouble because many workloads have few requests that can be front merged."

So makes sense, remove something that's rarely, if ever used, to improve efficiency slightly.

My money's still on franco's pimped out BFQv5. :D;):good:
[Samsung Galaxy Nexus] Savant:
Download trickster app if you need something to control it and you can always go to his website to download the kernel's.
[Samsung Galaxy Nexus] franciscofranco:
I disabled front_merging on deadline thats why I made it default and it seemed better for me in the long run. BFQ causes a very rare boot lockup which made some users bootloop after flashing a kernel, but it was rare.
[Samsung Galaxy Nexus] Wynnded:
Oh, I'm guessing that there will likely be another release before you've convinced yourself that you're done "testing" this one. :D
[Samsung Galaxy Nexus] osm0sis:
Ahh so that was the reason for those bootloops some people had. That's too bad. BFQ definitely feels smoother on my device. Cue obligatory beg/ask for scheduler changing in the updater app now. ;)

Edit: Although, here's a sneaky thought... have it be deadline by default in the kernel to avoid the bootloops but then have the boot service in the app change it to bfq. Best of both worlds. Perhaps finally a good argument for having it in the app. :p
[Samsung Galaxy Nexus] franciscofranco:
Yes IO scheduler thingy is planned. I have to do a major app re-write soon so that will go with it.
[Samsung Galaxy Nexus] yellowdie:
Oh, most definitely. :D

lol. I'm comparing the two, but so far don't have a preference either way. :cool:
[Samsung Galaxy Nexus] nikulogical:
I haven't been following this thread lately, is there a consensus to which tcp algorithm works the same or is it still different for everyone?

Sent from my PARANOID ANDROID
[Samsung Galaxy Nexus] Wynnded:
I took a look into Set CPU and saw that it was set to BFQ and I thought to myself, "I wonder if that's why with the last dozen or so releases, when I flash and let my phone sit, it locks up when it goes to sleep?" (If I kept it awake, it would be fine.) I think that you have unwittingly solved that for me with that post. Thanks man.

---------- Post added at 08:02 PM ---------- Previous post was at 07:54 PM ----------

There hasn't been much talk about it lately, but I imagine that most leave it stock (cubic) or change it to westwood (of the ones that I've read semi-recently).
[Samsung Galaxy Nexus] yellowdie:
Gosh... My phone is flippin' flapjacks fast...

Just sayin'... :)
[Samsung Galaxy Nexus] Sik-1:
Westwood algorithm is definitely better than cubic, its like NA -> turbo boost lol
[Samsung Galaxy Nexus] nikulogical:
Download speed is faster for me but at the expense of upload and ping.

Sent from my PARANOID ANDROID
[Samsung Galaxy Nexus] garuhhh:
I'm trying 6/7/3/3 and 3/7/3/3, but couldn't seem to find a difference in performance. In that case, going for 3/7/3/3 will be the best for battery, right?

I'm running r295, 192-1036MHz, default voltages, input_boost_freq = 1036800, hispeed_freq = 729600.

Oh, by the way, how do you test for responsiveness?

In my case, I just go and swipe the application drawer as fast, and go to the heaviest website I found (desktop site of nfl.com) -- not sure if my methods are correct. Anybody want to share theirs?

by the way, I don't have the "tweaked" settings by default, as i have set setCPU to load mine on default, forgot to change that.
[Samsung Galaxy Nexus] yellowdie:
In the case of 6/7/3/3 vs 3/7/3/3, the first number is "lower = better speeds, worse battery." So 6/7.. is what we think will be the best of both worlds. The main difference in your settings there is the third number. Lower is better for battery, but we think 6 might be the best choice there as well. Good performance with good battery. :) The best thing to do is clear setcpu and reboot. That should get you back to our default settings of 6/7/6/3. =D

As far as testing, that's kinda what I do as well. :)
[Samsung Galaxy Nexus] BigBake88:
Two things. First, min sample time is still 6 with 295, I thought it was going to be lower? Two, in your app Franco the current CPU frequency tab is showing my CPU pegged at 729, rarely if ever getting below it, but CPU spy does not mesh with this. CPU spy is showing 192 MHz being used almost all of the time whole I am not touching the screen. Is this a "bug" in the app? What am I missing?

Edit: yellow answered my question above about min sample time! Still need to know about app!
[Samsung Galaxy Nexus] osm0sis:
Yup, and don't bother with 192 for your min since you're just slowing things down for no reason at default voltages. :)
[Samsung Galaxy Nexus] franciscofranco:
min_sampling_timer is 60ms by default on r295 yep.
[Samsung Galaxy Nexus] BigBake88:
Ya idk if I'm liking 192. Going to test it a little more but will most likely be switching back to 384:good:
[Samsung Galaxy Nexus] yellowdie:
As far as I can see, the only benefit of 192MHz is if you undervolt it to 725mV or 750mV. I am normally against UVing, but in this case I think it will work well. :)
[Samsung Galaxy Nexus] BigBake88:
Undervolt the slot just for battery savings, for it to run better, or both?
[Samsung Galaxy Nexus] osm0sis:
Battery savings. Since the slot currently uses the same voltage as 384MHz (same once both are calibrated by SR = 830mV).

So I think it should either get cut entirely, or be hardcoded to 725mV by default to avoid confusing the average user that sees a lower frequency and thinks it will be better for battery, but really just ends up slowing down their device for no savings whatsoever. :eek:
[Samsung Galaxy Nexus] yellowdie:
Battery. If battery is not important, then 384 is a good min. :)

---------- Post added at 11:26 PM ---------- Previous post was at 11:24 PM ----------

I agree. 725 is the lowest I can go (700 SODs on me). So I think for stability, 750 would be the best default. But that's Boss Man's call, and I don't think he wants to UV that low.
[Samsung Galaxy Nexus] franciscofranco:
I can't hardcode that much. In fact I don't want to hardcode 192Mhz voltage at all and let users decide what to do. If they don't know then its time they start searching.
[Samsung Galaxy Nexus] osm0sis:
715mV for EDNYLaw, 675mV for nuwan32, so I think 725mV is fair. Maybe 730 or 735mV for that extra bit of safety you crave. ;)

Fair enough.. just not looking forward to the confusion and ad nauseum re-explanations to follow, which is already beginning I feel. :(
[Samsung Galaxy Nexus] yellowdie:
Do you have a way of putting a popup message that comes up when people select 192 as the min in your app? That would be a cool.

And in all reality, is there gonna be much difference between 730mV and 830mV? If you ran 100% at that voltage nonstop, would it save you hours or just minutes?
[Samsung Galaxy Nexus] creeve4:
Running 295 with default settings. I've noticed that the Current CPU Frequency displayed in app will often stay at 384 when I scroll the screen. Sometimes it jumps to 729 and even less often to 1036.

I thought that scrolling initiated the input_boost frequency, 1036?
[Samsung Galaxy Nexus] osm0sis:
I know undervolting tiny amounts isn't really worth it for anything other than heat reduction, but ~100mV difference might have a real world effect on battery life, no?