yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] lippol94:
Well, it will hardly run bad as it's really simple compared to other I/O Scheduler (according to Wikipedia page: http://en.wikipedia.org/wiki/Noop_scheduler).

So it works just fine for easy processes, but I guess you'll find more lags when proceding heavy operations. On the other hand, more complex schedulers will choose "what to do" according to I/O activity status.

On a phone like ours, with the great work done by Franco Team, other schedulers may perform better than NOOP due to Galaxy Nexus hardware, which is not that powerful.

As a matter of fact, you won't even notice the difference by changing I/O scheduler on a 4-core x86 CPU .

See Bottleneck :) http://en.wikipedia.org/wiki/Bottleneck#Engineering
[Samsung Galaxy Nexus] Khrushy:
Noop isn't really any good for what we want to achieve as smartphone users. It has really good total throughput, but no prioritisation or fairness constraints at all so (for example) if you get a big file write it will completely finish that file write before moving on to any other operations - causing massive UI lag.

If you want to prioritise total throughput Deadline is a much better choice because it's almost as fast as Noop, but still has operation constraints to ensure your system doesn't get completely locked up just doing one thing, holding up everything else.

RoW is pretty self explanatory - read over write - and is really smooth most of the time as long as you don't have really heavy IO operations going on - then it can get backlogged on the writes and eventually its timeout will force it to write the data in large chunks, which will give UI lag.

Then there's CFQ and BFQ, which heavily prioritise fairness. They tend to have slightly lower total throughput than deadline (but still good!) but heavily prioritise fairness in the IO operations, which pretty much ensures that smooth feel that so many people like for their phones.

I didn't actually intend to list it like that, but I just listed it in terms of my personal "Least favourite" --> "Most favourite".

As for your original point - Noop probably works just fine on the N4 - it's default IO speeds are much much higher than the GNex's, meaning the threshold for actually taxing the system so much that it gives you noticeable lag is going to be a lot higher for the N4.
[Samsung Galaxy Nexus] shawnaye:
Hmm os. Using noop on my s2 two years ago was great paired with hyper.

I had basically no lags and that's the only reason that made me stick to dorimanx's kernels over there.

So noop was great on my s2 but not so here. Why is that so? Given we both got dual cores.
[Samsung Galaxy Nexus] Khrushy:
It's less about the cores and processing than it is about the memory/flash interface. I have no idea what the S2 had in that regard, so maybe it was just a bit more efficient (although I'd have assumed the Gnex's was better, being a slightly newer phone).

The more important factor I suspect is that current Android has a lot more background operations happening compared to Android of 2 years ago. Noop is pretty great if you only need to worry about efficiently processing a single thread/app.

Option 3 is the idea some of the changes made to optimise the kernel in general might have made things less optimal for Noop - although I find that doubtful given how simple Noop is.
[Samsung Galaxy Nexus] lippol94:
Are there any values we can set to BFQ to make it more performant?

Maybe these one?

http://xdaforums.com/showpost.php?p=40612150&postcount=41205

Thanks :)
[Samsung Galaxy Nexus] pkgnex:
Those are definitely the most important two.

My testing also showed setting raising_max_time to 0 and raising_max_softrt_rate to 2000 helped. Of these, raising_max_time seemed to have more confirmation from others in "Franco Team". Setting it to 0 actually just allows the BFQ algorithms to auto-tune this parameter based on your device's hardware performance. You will note that after you initially set it to 0, if you check the parameter later, it will have grown - usually to 256 first, then progressively higher over time. To me, it feels like BFQ continues to get smoother and smoother after a few hours as the auto-tuning of this parameter "settles in."

Raising_max_softrt_rate = 2000 showed as a definitive statistically significant sweet-point for increasing overall throughput in my testing, but other people have indicated they had problems with this setting and reverting to the default (7000) fixed their issues, so use this one with some caution.

If you try tweaking this last parameter and find a preference for 2000 vs 7000, please post in the thread!
[Samsung Galaxy Nexus] abalam:
I want to thank the whole team of Franco equally good support for what you give. I know that Franco is now primarily concerned with the N4 and is not as focused on the maguro. You love this toppic strong. So we still can enjoy this excellent kernel. Thanks guys!!!!
[Samsung Galaxy Nexus] thegtfusion:
for the record, i was using purity 5.5 and i got some extreme lags. (i think it has to do with one of the flags Dario changed.) now on stock 4.2.2 the kernel performs even better :D

awesome job team franco :D
[Samsung Galaxy Nexus] Starsream88:
Awsome work franco team ! Really great kernel :thumbup:
[Samsung Galaxy Nexus] dracon6ai:
This is probably off-topic but in the whole concept of smoothness I stumbled across this site.

https://code.google.com/p/android/issues/detail?id=40961

I set the values for the build prop as listed and noticed a nearly immediate difference. Noticed it on stock kernel, Franco and Lean kernel. Running PA right now and used these for over a week. Figured it would be a good contribution in the quest for smoothness.

dalvik.vm.heapgrowthlimit=64m (was PA original)

dalvik.vm.heapsize=384m (was 256 on PA)

Edit- on a side note, besides normal day to day use the main impact I've seen was in Google Chrome. It's actually usable now, no more major lag when opening it and in general runs a ton smoother. It's back as my main browser. :D
[Samsung Galaxy Nexus] Spoderman:
Thanks for the advice, using it right now :)

I had no effect, since i had an extremely smooth ROM (aosp r11) with this extremely smooth kernel (r378) but it might help in other departments!
[Samsung Galaxy Nexus] bunnahabhain:
[MENTION=3554609]thegtfusion[/MENTION] :I am also searching for a Stock Rom cuz i heard the lag is a Problem of custom compiled aosp Roms.

Would Android Revolution Hd count as Stock or custom ROM?

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] Pootch:
no more leankernel updater in the new version (updater app)????????????
[Samsung Galaxy Nexus] nktje:
If you're looking for a stock-like experience with great performance you should give MiNCO a try. V7 with the build.prop adjustments runs like a champion.
[Samsung Galaxy Nexus] bunnahabhain:
Hmm... Is trat ROM based on the Stock Google Image as ARHD is?

The thing that bugs me most is the unresponsiveness of any 4.2.2 custom ROM. When i Hit the back or home button i want to go back or home and not wait for christmas. Even thought to go back to 4.1.2 and Franco r300:rolleyes:

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] Godra:
Minco is AOSP based ROM
[Samsung Galaxy Nexus] Khrushy:
It was a trap anyway. If you tried to use it the f.Ku just crashed.
[Samsung Galaxy Nexus] Rimher:
A couple of changes in the tunable have actually improved this a lot for me. May i suggest you try this:

gohispeedload 85

hispeedfreq 729

minsampletime 55000

Best smoothness I've achieved on osmod 378
[Samsung Galaxy Nexus] The Gingerbread Man:
By lowering go hispeed load to 85 from 95 your just making it easier for the CPU to use faster speeds easier, so yes it could be smoother but at the cost of battery. Hi speed freq you haven't changed that was already 729 and increasing the min sample time to 55000 your telling the CPU to wait longer before ramping down, again costly to battery.
[Samsung Galaxy Nexus] osm0sis:
ghl the same as tl is unwise. That means you'll be running at hf a lot of the time, if not all the time.
[Samsung Galaxy Nexus] The Gingerbread Man:
The only thing we could do with improving here is keeping the galaxy nexus smooth for long periods without rebooting, you need to reboot it once every 24 hours to keep things as nice as possible. Maybe too much **** gets into the ram or some apps being resource hogs but I love how well this performs with a fresh boot after running lag fix over system, data, cache then run forever gone and run lag fix again over all partitions again whilst rebooting after each stage. It takes about an hour to do though due to quite **** io speeds
[Samsung Galaxy Nexus] thegtfusion:
61h uptime here and things are as smooth as it just booted. (Stock + r378-osmod)

Sent from my Nexus Prime
[Samsung Galaxy Nexus] osm0sis:
That's kinda crazy haha. With osmod discard is enabled, so lag fix shouldn't be necessary.. Also forever gone accomplishes pretty much the same thing as lag fix, just does it by filling up all the space instead. :)
[Samsung Galaxy Nexus] Rimher:
Yeah I've found a useful link on governors and tunables, and set them accordingly to what I thought was best. The performance is very good indeed and the battery feels pretty good too.

What I thought is that if the CPU uses faster speeds, it accomplishes something easier instead of hanging constantly whilst struggling (that must not be very battery friendly either); so once it's finished, it can ramp down more easily. Moreover it is likely that if the CPU is ramping up, it'll need to perform some heavy computation, thus the min sample time that is higher.

This is again just my personal opinion and preference, since I favor smooth performance over battery life - but I have to say that I'm getting pretty good battery life (around 2h15m of screen on time) and very good Idle Drain (~1% per hour).
[Samsung Galaxy Nexus] osm0sis:
Hopefully you lowered target_loads as well then. They should not be the same.
[Samsung Galaxy Nexus] Rimher:
Nope I haven't and they actually are the same. Should I change it how?
[Samsung Galaxy Nexus] splus:
How come no one here is using Cataclysm ROM?

It's a stock Google GNex ROM with a whole bunch of incredibly useful additions not present in any other ROM, but without themes, halos, pies and these things that affect performance and stability.

Because it's built on stock ROM and not on AOSP it doesn't have any problems common to AOSP ROMs, you can run it for weeks (literally, I'm not kidding) without any slow down. Performance is great.

Since I started using it it cured my ROM flashocholic habit. :) Highly recommended ROM.

Here's the thread link:

http://xdaforums.com/showthread.php?t=1995801

Oh, and of course, it works great with Franco kernel.
[Samsung Galaxy Nexus] osm0sis:
Target was lower than ghl for a reason; that's what your device is constantly trying to maintain the load at by ramping the freq up and down. The default gap is 10, but I don't recommend putting target lower than 80 either way.

Like I said by setting ghl and tl the same you're being cruel to your device. It meets target load and immediately jumps to hi speed freq, which lowers the load, so it ramps down, then it wants to reach tl again; repeat. We call that oscillation. ;)

Basically I would make ghl 90 and tl 80 at the lowest. Battery hit would likely be too great any lower. :)
[Samsung Galaxy Nexus] SahilC:
Same here mate. 5+ days and it's all good :D
[Samsung Galaxy Nexus] thegtfusion:
I use this one. simple fast and good battery life.

http://xdaforums.com/showthread.php?t=1882248

---------- Post added at 09:45 AM ---------- Previous post was at 09:42 AM ----------

@osm0sis, how do I change the RAB in franco app? i dont see an option for it.. (v10.0.1)

---------- Post added at 09:46 AM ---------- Previous post was at 09:45 AM ----------

@osm0sis, how do I change the RAB in franco app? i dont see an option for it.. (v10.0.1)
[Samsung Galaxy Nexus] pikso:
Does not work with miui v5 on 4.2.2
[Samsung Galaxy Nexus] neo-X:
Excuse my ignorance but isn't stock the built on AOSP? I thought that's where the official google code is done.

Sent from my Nexus 7
[Samsung Galaxy Nexus] AutomaticFailure27:
[MENTION=4544860]osm0sis[/MENTION] I was attempting to search but came up short.

For your osmod version, is there a need for any of the init.d scripts you have created? I see that deadline still hasn't been implemented, so I assume you still need the 950iosettings script to set the deadline tunables. Nevermind, can just set that in Trickster. Though for things like the lmkwhitelist or mntsettings, is that needed or was that for the testing period before? Again, nevermind, kept clicking back until I found my answer.

Thanks for any help. Just came back from AK Kernel, so I am playing a lil' catchup.
[Samsung Galaxy Nexus] Khizar:
i remember reading somewhere that you have to flash the 4.2.2 libs zip before you can flash 4.2.2 kernels on miui
[Samsung Galaxy Nexus] The Gingerbread Man:
Accidental thanks there haha I agree with Osmosis about how the governors and schedulars are set and personally taken alot of time in testing them to find the best results in performance along with osmosis, pkgnex, maloroth, krushy, yellowdie and joaquinf (I think that's everyone) we all have spent a lot of time in working out these values already to be pretty much optimal, and osmod 378 is the result of it.

To elaborate a little more on what my original point was is that just occasionally things don't feel as smooth for me at least after long period of up time, and its not difficult to reboot everyday once so I'll stick with that as a solution for now.

[MENTION=1143630]osmosis[/MENTION] do you know why on nexus 7 lag fix on data partition takes basicly no time to run and on gnex it takes quite a long time?
[Samsung Galaxy Nexus] Rimher:
Alright, I'll try with this and see how it goes! Thanks for the clarifications, in the link I posted there were not references about tl :)

The performance is top notch no doubt. Isn't what you're talking about the infamous SystemUI memory leak that most ROMs have? If so, I'm currently using Vanir and it is definitely very smooth with no such problems.
[Samsung Galaxy Nexus] akash3656:
I'm not osmosis but I do notice that my Galaxy Nexus before samsung service centre screwed up my phone during a screen replacement and replaced my motherboard, I had much lower I/O scores and lag fix didn't do much and it took forever to run lag fix.

I recently had my motherboard replaced and now I'm using a slightly newer NAND that's slightly faster and needs to be lag fixed often (every 3 days or so). Else it starts to lag a lot. And lag fix only takes seconds to run just like my N7. But now with the latest 875mntsettings script, I don't seem to need to lag fix often. I still do it after flashing/restoring a rom though.

So I guess you're using the slower and older type of NAND that doesn't need frequent lag fixes.
[Samsung Galaxy Nexus] osm0sis:
Not added to f.Ku yet. Hopefully soon.

Haha good man. Welcome back! :)

No idea! I've noticed that too though. akash's explanation would make sense! Sounds like his newer chip requires discard.
[Samsung Galaxy Nexus] ChazzMatt:
I'm going to ask a stupid question, so please forgive me... Is this build prop change more a ROM setting or a kernel setting? That is, is this something that could be incorporated into Franco kernel (via osmod future tweaks) or is this something we should be forwarding to our favorite ROM makers?

We can easily change the setting using

Build Prop Editor

from Google Play.

But I notice my heapgrowthlimit is already 64m (not 96m) So, where did that come from? :confused: My Slim Bean ROM or Franco Kernel Osmod?

And of course using the app above, I can change the heapsize to 384m, from 256m.
[Samsung Galaxy Nexus] sajty:
Guys,is there any list of tunables for all schedulers?I found some for deadline (search button),for row (osm0sis signature),but what about others?Mainly i would like to know tunables for noop,bfq and cfq.
[Samsung Galaxy Nexus] osm0sis:
The heap tweaks were discussed and experimented with extensively awhile back. 96/256/0.75 are the default here. I did a bunch of research on all stock ROMs to see what changed. Either way I consider it more ROM territory, so it's not in osmod now or ever. I had an init.d script to alter it so check your scripts. Maybe you forgot it was in there.

noop is so simple that it doesn't have tunables, cfq and row are already tweaked by default in r378 to our researched values. The deadline values which we finalized should be in the next build and have also been posted recently. The results of pkgnex's "quick-tune" of bfq for Franco's Dev Team were posted a few pages back.
[Samsung Galaxy Nexus] The Gingerbread Man:
I dont know could be, I'm running stock ROM here, have been since pretty much as long as I can remember. Perhaps just one of those 4.2.2 bugs that google is clearly taking their time to fix

[MENTION=2548902]akash3656[/MENTION] thanks, that's helpful to know.
[Samsung Galaxy Nexus] misterk267:
This kernel goes great with AOSPAL. Smoothest combo I've had with this phone. Just kinda figured I'd report in on my experiences. :D
[Samsung Galaxy Nexus] nex_t:
I want to install Cyanogenmod 10.1 and Franco kernel but i can't find a link for the kernel.

Would you please help me, guys ?

Thank you

LE : i found it, i hope that's the right link

http://minooch.com/franciscofranco/Galaxy Nexus/JB/JB-4.2.2/zips/

So, i downloaded the franco kernel nightly r378 and the cyanogenmod 10.1 nightly toro

Do i need gapps, too ?
[Samsung Galaxy Nexus] nexusmaniac:
Try Google, it's the first link for me...

http://xdaforums.com/showthread.php?p=19794530
[Samsung Galaxy Nexus] Khizar:
seriously? did you even bother reading the OP?

why are you linking him to the n4 thread? he is posting in the gnex section so he most likely has the gnex...
[Samsung Galaxy Nexus] nexusmaniac:
My mistake I went to the wrong thread :rolleyes:
[Samsung Galaxy Nexus] nex_t:
So, what now ? :o

I have the Cyanogenmod, the kernel, but what about the gapps ?
[Samsung Galaxy Nexus] nexusmaniac:
http://xdaforums.com/showthread.php?p=34610569
[Samsung Galaxy Nexus] :
What the?!?!?
[Samsung Galaxy Nexus] osm0sis:
[MENTION=3292224]franciscofranco[/MENTION] Would it be possible for us to get an advanced option that hides the LeanKernel updater page from the menu in the new f.Ku? Thanks for the beautiful new interface, Boss Man! :D
[Samsung Galaxy Nexus] tylerdurden83:
A quick question guys, is NFC wakelock while nfc is disabled a known bug of android 4.2? If it is, I reckon it can't be fixed with a custom kernel either? Thanks!
[Samsung Galaxy Nexus] bigknowz:
I'm seeing some kennels with a deadline update referencing 0ms latency. Is that already in franco?
[Samsung Galaxy Nexus] nikulogical:
No
[Samsung Galaxy Nexus] osm0sis:
...Except yes. ;)

https://github.com/franciscofranco/Tuna_JB_pre1/commit/7958480e498a07d7ebab2e2c7f75ac8537c3b41f

It's in as of r378.
[Samsung Galaxy Nexus] dizzy1k:
where i can get the osm0sis version ?!
[Samsung Galaxy Nexus] bigknowz:
osmod

Having trouble finding the img file, here's the zip.
[Samsung Galaxy Nexus] dizzy1k:
thanks but : 404 Not Found ... the link doesnt work anymore
[Samsung Galaxy Nexus] AutomaticFailure27:
I think dev-host is down at the moment. It was giving me the same when I tried AOSPA.
[Samsung Galaxy Nexus] dizzy1k:
yep , it works now..

so its better than default franco's kernel ?! :p
[Samsung Galaxy Nexus] Khrushy:
It's Franco's with a few tasty additions. Franco has seen the changes so they should be rolled into the next Franco release when that comes.

Edit: Also, I don't think I said Franco enough there (3 times in one line?) So .... Franco Franco Franco Franco Franco.

There, that's enough.
[Samsung Galaxy Nexus] fk.gregor:
Anyone having issues backing up kernels on the app?
[Samsung Galaxy Nexus] nikulogical:
Oh wow
[Samsung Galaxy Nexus] Broadleynine:
Not sure but you might want to let others know you're talking about Franco, you know, to avoid any confusion. ;)
[Samsung Galaxy Nexus] DanielSanchez:
Instructions weren't clear enough, got my winnie stuck in the microwave.
[Samsung Galaxy Nexus] bunnahabhain:
Is the latest franocokernel still copatible with the actual CM nightly since there were made some changes to ramdisk on CMs side?
[Samsung Galaxy Nexus] abalam:
Running it with cm 10.1 here, and no problems. Verry good combination.
[Samsung Galaxy Nexus] kuronosan:
Dunno, I'm getting nothing but lag on my phone from clean install... didn't have this problem with any other kernel but with the latest Franco my phone hogs battery, gets super hot, and slows to a crawl.
[Samsung Galaxy Nexus] wavedashdoc:
Were you on one of the AK kernels at any point without doing a clean install before installing Franco?
[Samsung Galaxy Nexus] jesssiii:
I haven't used Franco since ICS. Wasn't that impressed, loved Leankernel. But since 4.2.2, my phone seems more picky and sluggish, and I find myself kernel hopping.

So flashed the Osmo-modded one above. No lag or hot reboots thus far, and no problem with deep sleep. I'm very impressed! Only changes were lowering min/max frequencies, turning off CAB, and slight color adjustment.

So I'd like to know where future Osmo-modded versions can be found... Or was this a one off?

Also, thanks for the link, bigknowz :o:P

Toro GNex
[Samsung Galaxy Nexus] mrazndead:
Digging the battery life from Franco so far on my GN. Also have Franco kernel for my N7
[Samsung Galaxy Nexus] kuronosan:
I was on it but I did reflash the cm kernel he provided, should I have just reflashed cm?
[Samsung Galaxy Nexus] gialandra:
For me one of the most important feature of a device is the USB AUDIO support to pass the audio data to an external and more sophisticated DAC.

Is it possible add support only tweaking the kernel? Here seems possible. Is it possible implement this primarily and great feature without struggling?
[Samsung Galaxy Nexus] franciscofranco:
r382:

* Merge up to 3.0.81

* Merge the latest interactive patches from Google fixing some timer issues, race conditions and null pointer deferences

* Merge all the work from the usual suspects in which its included better mounting options for the partitions

Hope this is the last one before M7. Enjoy.
[Samsung Galaxy Nexus] Midomad:
Flashing...

Thanks a lot

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] thegtfusion:
Did you also.include all osm0sis tweaks? :D

Sent from my Nexus Prime

---------- Post added at 03:37 PM ---------- Previous post was at 03:26 PM ----------

R381+ stock 4.2.2 = so fukking smooth, i almost cried of how fast and smooth this is omfg good job franco!!!!!! :D:beer::beer:

Sent from my Nexus Prime

Sent from my Nexus Prime
[Samsung Galaxy Nexus] franciscofranco:
He sent me a package to my email I copy pasted everything.
[Samsung Galaxy Nexus] ToMeRv32:
Wohoo, update!

PA + Franco + Nexus louder updates in few days - flash time! :D
[Samsung Galaxy Nexus] thegtfusion:
Awesome man! You are the damn boss! I have never seen my gnex so smooth on 4.2.2 !!!

:D:D:D

Sent from my Nexus Prime
[Samsung Galaxy Nexus] franciscofranco:
Yeah my Tuna is working great too. Just want to get the Milestone out so that I can finally add some cool beans on interactive that I have been working on Mako.
[Samsung Galaxy Nexus] thegtfusion:
I saw them in the mako yes. Let us test this for the milestone, then you add the "weed" beans :D

Sent from my Nexus Prime
[Samsung Galaxy Nexus] duduzinho15:
Really nexus with franco kernel and stock is perfect !
[Samsung Galaxy Nexus] jjhrrsn:
Rasbean and Franco is how the phone should of came
[Samsung Galaxy Nexus] creeve4:
r382 still does not have the latest Deadline optimizations/tweaks (i.e. fifo_batch, read_expire, etc). I'm not complaining, just pointing it out.

Is Discard enabled for Cache, Data, and System in 382?
[Samsung Galaxy Nexus] DanielSanchez:
http://queue.acm.org/detail.cfm?id=2492433

https://github.com/Feh/nocache
[Samsung Galaxy Nexus] jesssiii:
:eek:
[Samsung Galaxy Nexus] Khrushy:
382 seems great.

The winning settings for BFQ and Deadline still need to be hardcoded in, but otherwise everything seems perfect.

Many thanks Franco!