yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
I either edit it on my device using whatever built-in editor my file explorer has (I use AntTek), or I use Notepad2 on my desktop. It lets you change from CR+LF (Windows/DOS) to LF (Unix/Linux) to CR (Mac/BSD) just by clicking on part of the status bar at the bottom - Android of course requires LF. Super easy and, if you hide the toolbar, looks about the same as trusty old Notepad. :)
[Samsung Galaxy Nexus] Khrushy:
Went with Notepad2. Boom - fixed it all in one go. Cheers guys!
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I always used Jotatext editor till I installed rom toolbox lite and now have RB text editor as default. Give me more options to play with and I wind up getting myself in trouble.

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Random amusing fact: I've rebooted so many times today that 4% of my battery usage is by "bootanimantion".
[Samsung Galaxy Nexus] The Gingerbread Man:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I use root explorer on my devices with its built in editor

That's quite funny, I never heard of that before :D
[Samsung Galaxy Nexus] exzacklyright:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

So how do you add these turn tables for row
[Samsung Galaxy Nexus] pagratios:
Is it easy to make a widget for your fk.u with device monitor?
[Samsung Galaxy Nexus] haxor:
Just today, Google opened an experimental kernel repository for Linux kernel 3.8. The repo consists of Androidified standard linux kernel.

Currently the official Android 4.2.2 Jelly bean comes with Linux kernel 3.4 and supports 3.0 and 3.3 versions. Manufacturers usually embed their own modified Linux kernel with the current version of Android which Google releases. Only the Nexus runs on the latest Linux kernel used by Google.

Introduction of Linux kernel 3.8 will be great for Android as it will bring NVIDIA Tegra and Samsung Exynos DRM drivers. It will also have a low memory foot print than previous linux kernel, which will reduce the space used by system in the internal memory, giving more space for users to store and install applications and data. Flash memory file system also goes really well with this kernel, which means smoother interface and processes. Overall this is really great news.

As this is not a small change, we are thinking that this kernel is in preparation for Key lime pie which will be the next version of Android, so Google is preparing itself for their launch of the new O.S, which I guess is not very far away. As this kernel is natively supported, the development time with this kernel will be brought down for both Google and third party developers. Hence Google will be able to bring out OTA updates and fixes at a much faster rate .
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I hope they will bring it also to gnex

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

That wont happen!
[Samsung Galaxy Nexus] shreddintyres:
Agreed, seeing as how the gnex still has the 3.0.x kernel despite the n4 having the 3.4.x kernel its rather unlikely that the newer 3.8 kernel will be backwards compatible
[Samsung Galaxy Nexus] shawnaye:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Seems like r366 is working well for all you guys? No freezes or anything?
[Samsung Galaxy Nexus] whitedragonz83:
r366 on 4.2.2 stock ROM has been great. The only minor issues were i/o scheduler or Google Play App issues. Ignoring this, I had easily no slow downs and great uptime of ~1 week with 365 and am sitting at about 5-6 days uptime now with 366 after changing my scheduler to CFQ. Phone feels smooth always to me at least. My goal is to make it until Key Lime Pie before I reboot again. Unless Franco works some magic tweaks and I need to flash his kernel update. ;)
[Samsung Galaxy Nexus] mrdevil_25:
just my observation for the last couple days regarding constant wifi disconnect and reconnects

R361 - constant reconnects

R365 - no problems at all.

R366 - constant reconnects

dont know what / if anything has changed from 365 -> 366 regarding wifi drivers. or how i can fix this. tried changing wifi channel, tried to use 5g instead of 2.4g but nothing seems to help =(
[Samsung Galaxy Nexus] osm0sis:
Yup. Maybe we'll get some choice picks from it though like we did with the new interactive, etc. :)
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I hope so.

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Linux kernel 3.8!.... I choose YOU! BATTLE

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] .:Crack:.:
Just did some very quick tests on how lp_swrite_quantum (probably some other tunables, too?) behaves when echoing a value.

For X € N [1;12] it seems like echo X > [...] results in cat [..] = X/3

i.e. if you echo 3, it will be 1, if you echo 9, it will be 3 and so on. for bigger values I did not really figure out how the applied value is calculated, i.e. if you echo 36 (to get 12) you*ll end up having 10; 40 will result in 11.

So does anybody know how and why these values are calculated as they are?

PS: Please note that I'm using an SGS I9000; the scheduler should be the same version/patch.
[Samsung Galaxy Nexus] CADude:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Would be nice if you could port kernels from device to device easily but that 3.8 kernel is probably headed to the Nexus coming out this Fall and that's it.
[Samsung Galaxy Nexus] malaroth:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Currently we don't know... though we hadn't gone AS in depth with equations I'd been searching for that answer myself. However... we have come up with some better default values through experiments than are currently set. A general consensus on improvement is located in my signature. However check back as that is currently still being tested

** probably be helpful if I'd read the post you referred to :P no. I'd surmised that was how it was and osm0sis did more definite calculations but as to why there still isn't a hard and fast rule

Franco r365

JBSourcery 4.5.5

---------- Post added at 04:52 PM ---------- Previous post was at 04:30 PM ----------

Also...I'd be glad if it WERE finalized.. I prefer deadline and finishing row before tackling cfq (if that even needs doing) would wonderful

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] Raijin:
Malaroth:

1. The settings of Row in the files of your signature, 900row-tuna.txt and 950iosettings.txt, are different.

2. While in 900Deadline-tuna.txt there are settings for nomerges and rq_affinity, in 900row-tuna.txt there are not.

3. Missing some simecolons in the end of sentences.

What is the final decision? More fluid with Row or with Deadline, both tweaked?

I hope I can help. Thank you for your work!
[Samsung Galaxy Nexus] Edward Stanbury:
over all after the tweaks i personally find deadline snappier and smoother :P
[Samsung Galaxy Nexus] gauravraw:
Excellent kernel Franco, as always. Just wanted to point something out though- the new racing game, Real Racing 3, best racing game available as of now for mobile platform, is NOT working with your kernel. I have tried re-downloading data thrice but it freezes up at the boot sequence and the device turns itself off. The game WORKS fine on AK's and stock kernel btw. Hope you can fix it, would love to go back to your kernel asap :)
[Samsung Galaxy Nexus] malaroth:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I'll have to go back over those but to answer the last first I'll share direct from Franco

The schedulers were written for spinning HDD to keep them from having to increase and decrease speed and thus prevent wear and tear.

950io is a generalized all Franco nexus script so either/or might be updated first while the others might change based on whatever currently is being tweaked. There's a constant flux of back and forth and I'd rather that once I've posted up to dropbox I leave it knowing it's stable while my device has the ongoing changes. If what we test turns out not to be so great I'd rather everyone not have downloaded it. But alas the semicolons are my fault. I do most of this at work between customers.

Deadline is my daily driver while others still maintain preference for row. But regardless the tweaked versions trump the default

Franco r365

JBSourcery 4.5.5

---------- Post added at 06:01 PM ---------- Previous post was at 05:50 PM ----------

All but 950io are gonna be down for a couple hours while I do some updating and can upload them again. 4 more hours of work so on later than midnight cst

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] joelmonty:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Franco I'm having a bug in which when I'm listening to music with headphones and while the music is playing and someone calls at that time I unplug my headphones since I don't have a mike and answer the call the voice quality is very low ,I confirmed that this isn't there in the stock kernel anyone else facing this issue? BTW I'm using r366
[Samsung Galaxy Nexus] Raijin:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I love when I receive detailed answers like that.

Will stay tuned. Thank you again.
[Samsung Galaxy Nexus] osm0sis:
Interesting, so lp_swrite is completely different scales on each device so far.

I found you need to go up to at least 100 (I did 1000) to know how the scale works. On the GN it's 0=1 8=2 16=3 etc but then it jumps by 7 once in awhile so I haven't worked out the equation for it yet. The scale on the N7 is far easier, 1=1 11=2 21=3 etc, so y=(x+9)/2.
[Samsung Galaxy Nexus] Empty Hand:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Just to verify, no text editing is needed with the 950io all in one script? My gnex will ignore the grouper settings and the settings for the scheduler I'm not using? Thank you!
[Samsung Galaxy Nexus] osm0sis:
Pretty much! With the all-in-one the values automatically go to the correct ones for GN or N7, and are set correctly for whatever scheduler you chose in f.Ku or Trickster. And the wait should work regardless of ROM or boot conditions (eg. cleared dalvik, etc).
[Samsung Galaxy Nexus] mcampbell:
Except very few HD's actually have variable speeds, and schedulers are not written for them. Generally these are the ones labelled "Green" or "energy saving".

But that said, yes; most schedulers are written for "spinning rust" storage.
[Samsung Galaxy Nexus] creeve4:
Are we any closer to finding a resolution to the freezes that occur when Play Store is installing apps? I had another freeze today while upgrading an app. Phone completely locked up, had to pull the battery, no last_kmsg was created.

I've only experienced these freezes when the Play Store is installing an app. Doesn't happen when installing an apk with adb or from a file manager (doesn't even lag in these situations).

I'm running r366, deadline and interactive with franco's settings.
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Does that last statement in parentheses scream "Google's fault"? I think we might mitigate most of the effects with tweaks but ultimately it'll have to be a revamp on Google's part

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] foueddyf:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I certainly agree with you but we can't ignore the fact that this also seems to only happen with Franco's kernel.
[Samsung Galaxy Nexus] sajty:
Guys,r366 has 3.0 or 3.4 WiFi drivers?
[Samsung Galaxy Nexus] reysonance:
3.0, the 3.4 is kind of wonky anyway.
[Samsung Galaxy Nexus] Khizar:
3.0

Edit- reysonance already answered :good:
[Samsung Galaxy Nexus] .:Crack:.:
I guess you meant y=(x+9)/10 :P

I'll see how it scales for the i9000, i.e. I'll try the N7 equation and in case it doesn't apply I'll try to find out that equation. But it should be somewhere in the sourcecode shouldn't it?

edit: for i9000 it seems to be y=(x+4)/4
[Samsung Galaxy Nexus] ToMeRv32:
4.2.1, R364.

No GPU OC options?
[Samsung Galaxy Nexus] reysonance:
Hardcoded to 512.
[Samsung Galaxy Nexus] osm0sis:
Err yup. :o

Weird stuff though, eh? Makes it tricky to have one set of values for multiple devices. So far so good for the N7 and GN though, since lp_swrite at 2 for a final outcome value can be set GN 8-15 and N7 11-20 so we went with 12 to cover both. ;)

The other one we found was different was read_idle. malaroth found it's 7 + 8s on the GN, and multiples of 10 on the N7. With 15 the GN sweet spot and 20 too high for the N7 the universal script instead sets 10 because on the GN 10 will result in an outcome value of 15 while leaving it at 10 on the N7. :good:

---------- Post added at 08:57 AM ---------- Previous post was at 08:30 AM ----------

For reference, what kernels have you personally tried where it doesn't occur? Has anyone tried disabling Verify apps under Security settings to see if it's related? Has anyone tried setting the iosched and/or governor tunables back to their defaults to see if those are related? There's a lot of troubleshooting still to be done here, and people are always way too quick to shout "kernel!" without wanting to do any of the work. :rolleyes:
[Samsung Galaxy Nexus] Fenvarien:
AW: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

This "fact" is simply not true, I tested Leankernel and Fancykernel when the freezes occurred on my device. And with both I had those freezes too. But maybe there's something else bugging the updates that has nothing to do with kernels?
[Samsung Galaxy Nexus] osm0sis:
Finally something useful on the topic that isn't just repeated hearsay. Thank you.
[Samsung Galaxy Nexus] stevensoaj:
[KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Since you asked, I've been trying different versions of AK Kernel on both 4.2.2 Stock and SlimBean for the past week or so and I haven't had this issue at all. And I didn't do a backup when I flashed SlimBean, so there were plenty of app installs for it to occur.

That being said, I've also tried r365 and r366 and I've had the play store issue only a handful of times.

Currently on AK I am using 710 Cylon Edition with fiops io scheduler, 180 min 1350 max frequencies, 512 KB read ahead. I can give more specifics (governor tuneables) if you think they may help.

Edit:

Also note that while on Franco, I pretty much stuck with the defaults. I didn't use

Malaroth's scripts (no offense, it was mainly out of laziness). I'm also not saying they have something to do with it, I'm just giving more information. :p
[Samsung Galaxy Nexus] lippol94:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Can you please post franco interactive values? :)

Thank you so much!!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Angelakaro:
A reboot will restore them,unless you set them by default on each boot. However,here you are
[Samsung Galaxy Nexus] Khizar:
uncheck set on boot and then reboot your phone
[Samsung Galaxy Nexus] creeve4:
I tired AK kernel, Purity 023, for several days and purposely installed many different apps from the Play Store. I experienced lag during installation using FIOPS, deadline, and SIO schedulers with the interactive governor.

I've also tried franco 366 using Wheatley and Interactive with each of the IO schedulers, the result is the same for each combination:severe lag during app installation from the Play Store.

Also, disabling the Verify apps option makes no difference.

Looking like it is not a kernel issue.
[Samsung Galaxy Nexus] ak:
From my point of view this problems aren't related to the kernel .... you can try to use old gapps binary and old rom (not linaro opt) for verify if the problem persist.. :highfive:
[Samsung Galaxy Nexus] lippol94:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Yeah i know that but I'm not on franco due to those freezes many users have reported. Still, I enjoyed interactive values and wanted to know them in order to try em on other kernels. Just out of curiosity.

Btw, in the screenshot you've posted you can't see above high speed delay. Could you kindly write it? Thanks!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Angelakaro:
See that anyone posted it yet,so i'm posting it now: is anyone using franco kernel playing real racing 3? I can't access the game,opening it will freeze my phone and will force me to do a battery pull. No problems on trinity. I can't help in anyway,since i have to do a battery pull. Any ideas?

EDIT: i saw just now that's already been said,but no one answered

---------- Post added at 04:52 PM ---------- Previous post was at 04:32 PM ----------

Sorry,i saw your post just now. It's 30000
[Samsung Galaxy Nexus] lippol94:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

No problem mate :) Thank you so much for minding to answer :)

Cheers!

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Gimic26:
Real Racing issues

For those having issues with Real Racing 3d it seems the game wants to default to the high settings with Franco's kernel. I'm guessing we don't have enough RAM to run the game on high so we need to use medium. To do that using a file explorer navigate to sdcard/Android/data/com.ea.games.r3_na/.depot/eds and you'll see the settings files. Rename AndroidHigh.plist to _AndroidHigh.plist or AndroidHigh.bak. Then make a copy of AndroidMid.plist in the same folder and rename it to AndroidHigh.plist. The game should work fine after that.
[Samsung Galaxy Nexus] abalam:
Hello all. Have been working for some time TWRP a rom related theme to give. Now Franco kernel nearby. More info:

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

Comment on this theme give the right topic (TWRP rom related) so this also meant toppic stays where it is intended!!!!

Tnx
[Samsung Galaxy Nexus] Angelakaro:
It worked,but the game crashed after a while and the phone freezed,battery pull again
[Samsung Galaxy Nexus] jcmm11:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Defaults work just fine. There's a reason that the values chosen have been set as defaults.
[Samsung Galaxy Nexus] Wynnded:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Have you tried not unplugging the headphones and answering the call then speak into the mic on the device? That's what I do while listening to music and a call comes in.

Sent from my Galaxy
[Samsung Galaxy Nexus] osm0sis:
That's the reason the headphones volume boost and hi perf sound patches weren't included for a while there; the low in-call volume bug. Workaround is switching to speakerphone and back.
[Samsung Galaxy Nexus] nuwan32:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

You can actually talk using a pair of headphones that doesn't have a Mic. It sends the audio through your headphones but uses the built in Mic on your phone
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I did nothing of the sort :-\ I am not about to have an adventure. No, no. No adventures for THIS hobbit. Stay in the shire and run stock default for the rest of my days I will

Franco r365

JBSourcery 4.5.5
[Samsung Galaxy Nexus] gaich:
Experiencing problems with init.d again, so I just support this question above - shoul I change anything in the script?:confused:
[Samsung Galaxy Nexus] osm0sis:
"Problems"? Elaborate please. You shouldn't need to change anything, just set your scheduler of choice in f.Ku or Trickster, reboot and let the init.d do the rest. Just make sure of the usual: permissions on folder and file.
[Samsung Galaxy Nexus] tjackbjorn:
Sv: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

This thread is seriously a hell of a good place of learning! With Rise Against in my ears I read through pages. Me like.

Sent from my super fast Prime filled with beans.
[Samsung Galaxy Nexus] rop12770:
HI

I have installed the Free Updater for my Nexus 4. The latest version available is r95 and here it's the r366. Is this right?

How can I install the latest version? Can I manually update it?

Thanks
[Samsung Galaxy Nexus] osm0sis:
Two problems: 1. You're in the wrong thread. 2. The free updater hasn't been updated for ages.

Paid is powerful and well worth it. Do it.

Edit: Ah, actually I see free was updated Feb. 25th; looks like it has all the latest again. :) Either way, GN != N4 and r95 is the most recent for the N4. :good:
[Samsung Galaxy Nexus] gaich:
Thank you, that was what I did wrong - I forgot the permissions...:cyclops:

By the way, are there some ideas to tune LAZY? There are some values in Trickster Mod...

View attachment 1777060
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

You know I wish I heard that more round here :thumbup:
[Samsung Galaxy Nexus] osm0sis:
It's kinda like ondemand with a higher wait and threshold, so if you want it a bit more responsive you could play with that. But, then it wouldn't be so lazy anymore so what'd be the point? ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I guess to tune lazy by definition you would have to make it take longer to do stuff which might end up in laginess so switching to on demand would be the better choice as they are similar. I think lazy was built from on demand like BFQ from CFQ its a variation of the original product
[Samsung Galaxy Nexus] osm0sis:
Ah see I was thinking that it'd be better to make lazy more responsive to try and remove the lag that governor already brings, but exactly, you might as well just make ondemand less aggressive; same difference.
[Samsung Galaxy Nexus] bigknowz:
Wheatley Tunables

What about wheatley? Any ideas for that?
[Samsung Galaxy Nexus] osm0sis:
It has tunables?
[Samsung Galaxy Nexus] gaich:
The point is the battery saving! OK, I`ll try to play, but should I descend or increase these values? And would it do some harm if I turn on the toggles above?:confused:
[Samsung Galaxy Nexus] Khrushy:
You'll probably be the first to really play around with Lazy. Just nandroid backup first and really, what's the worst that can happen? Even if you input something wrong in the kernel tuneables and bootloop it, you just restore from your backup - Easy.
[Samsung Galaxy Nexus] J-Hop2o6:
Re: [KERNEL][GPL][GN] franco.Kernel

Seems like CFQ is a winner for Play Store updates/installs. I never got lockups to a point of a battery pull before CFQ. I was mainly using row, and that always slowed my phone down greatly with high cpu and system usage (updating apps or serious multitasking/big apps in the background). Plus it will take a while for the cpu to "settle down" after an app update for whatever reason. CFQ updated my apps with ease. So I suggest you guys try CFQ out.

I will see how it goes for a few days without a reboot.
[Samsung Galaxy Nexus] osm0sis:
Cool. cfq is next on the list. ;)
[Samsung Galaxy Nexus] sajty:
Noop is safe too, never had freeze even when downloading files and updating some app at same time.
[Samsung Galaxy Nexus] wavedashdoc:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Not having any lock up with Mmuzzy 3/1 with 366 and new deadline 512 tunables.