yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Empty Hand:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Thank you for the suggestions. Unfortunately, none of those potential issues apply. The permissions were set right, and the reason I knew it wasn't working is the row tunables were not setting despite row being selected and sticking on boot. Just a mystery I guess.
[Samsung Galaxy Nexus] osm0sis:
Check your PMs.
[Samsung Galaxy Nexus] Samhain77:
I think malaroth should add a commented line to the script with last modification date, so everyone is really sure to use the latest version. ;)
[Samsung Galaxy Nexus] osm0sis:
Haha well it's only for testing anyway, since eventually these will make it into the code of an upcoming build. No biggie. ;)
[Samsung Galaxy Nexus] Samhain77:
Ok, sure. That sounds good. :good:
[Samsung Galaxy Nexus] malaroth:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

That's strange... I'll double check my file but I'm pretty sure it's set with permissions
[Samsung Galaxy Nexus] shreddintyres:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I had the same issue before what you need to do is go and check if your rom has a sysctl.conf file in the /etc directory removing that allowed my scripts no matter how long to work properly. You may also want to take a look at what other initd scripts your room is using

And lastly make sure you are writing your script in an editor that uses the Unix style line break if you are copying and pasting into a txt file with the windows line break the file will not work (courtesy of osmosis)
[Samsung Galaxy Nexus] Kurre:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

hmm.. Interesting.. http://xdaforums.com/showthread.php?p=38819834:rolleyes:

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] Angelakaro:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

:eek:

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

It would be wonderful to get 3.4 stable, but would the efforts and hard work be worth it? Our 3.0 base is good for tuna?
[Samsung Galaxy Nexus] Angelakaro:
It's development. If developers would have never started to code custom kernels and to try impossible things,we wouldn't have enjoyed the great kernels that they offer now today. It's always worth it
[Samsung Galaxy Nexus] agayabag:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

At least, sir Franco always took something from his N4 kernel, which is 3.4.xx.

Which means, our kernel actually has something similar to it. And if he has different decision, he'll make it.

Let's see what up.
[Samsung Galaxy Nexus] Samhain77:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I've done some tests with this values (512 read_ahead_kb, and 1 both to nomerges and rq_affinity) and it seems much more comfortable than before. Now I had 3 big updates and no more big freezes. :thumbup:
[Samsung Galaxy Nexus] osm0sis:
Can you try it with only the read ahead changed? It'd be nice to narrow it down.
[Samsung Galaxy Nexus] Samhain77:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Just tried before this. Not so good, still have some freezes.
[Samsung Galaxy Nexus] osm0sis:
Perfect so part of it could be the nomerges setting then. Thanks for the help guys!
[Samsung Galaxy Nexus] aeroseek:
For me the issue was extra spaces after ";" in the script. Works as advertised now.
[Samsung Galaxy Nexus] osm0sis:
No spaces in my local copy, not sure how that happened? Glad you got it working though.
[Samsung Galaxy Nexus] creeve4:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I just downloaded malaroth's all in one script and there are blank spaces at the end of every line (both in the root explorer text editor and notepad2).
[Samsung Galaxy Nexus] osm0sis:
Ah poop. He must have copy+pasted instead of uploading my original file. I don't think Groups or Dropbox would do that on its own.

Edit: Spaces really shouldn't make a difference, but those with issues, try the attached. Please download directly rather than copy+paste so that you know the original newline formatting has been preserved. You know the drill: rename away the ".txt" extension, put it in /system/etc/init.d/ and then run su -c chmod -R 755 /system/etc/init.d in Terminal Emulator to set the correct permissions all at once. :good:

P.S. Got some very early days cfq tweaks in there if some people want to try them out vs. stock cfq.

I'd also like some feedback regarding different settings of:

nr_requests (1024, 512, 256, 128),

back_seek_max (2147483647, 1000000000, 0),

group_idle (15, 7, 0),

and quantum (64, 32, 16, 8).

If you'd like to help with testing please restrict yourself to one of the above variables to change at a time so you know what's making a difference. :cowboy:

[ Attachment removed, since malaroth updated his sig again to one more recent. ]
[Samsung Galaxy Nexus] Zadeis:
If you don't mind me asking what are the new couple lines in the script you posted. (I hope this wasn't already asked) I am referring to

echo 1024 > /sys/block/mmcblk0/queue/nr_requests;

and

echo 0 > /sys/block/mmcblk0/queue/iostats;

I mostly like to know what things do before I do ahead and try them on my devices. A quick Google search for iostats yielded something lines of device monitoring and nr_requests had something to do with scheduler queue size. Any more explanation would be awesome though :D
[Samsung Galaxy Nexus] osm0sis:
Sure, here's a little "light" reading for you. ;):laugh:

http://www.mjmwired.net/kernel/Documentation/block/queue-sysfs.txt

http://www.mjmwired.net/kernel/Documentation/block/cfq-iosched.txt

https://access.redhat.com/knowledge.../6/html/Performance_Tuning_Guide/ch06s04.html

http://lwn.net/Articles/395769/

Most of what I've done so far is try to handle both of the main cfq complaints; optimize it for non-rotational disks (ie. flash/ssd), and reduce the overhead a little (disable iostats might help here).
[Samsung Galaxy Nexus] pkgnex:
This is it!!! Changing read_ahead to any vslue didn't help play store lag / freeze, but changing nomerges and rq_affinity to 1 fixed it for me instantly (after force-running the init.d script, of course).
[Samsung Galaxy Nexus] osm0sis:
rq_affinity is already 1 in r366 (and setting it to 2 like we do in the script resolves to the outcome value of 1 on the GN), so it was definitely nomerges. Glad we at least handled our half of it. Google Play could still play better, I'm sure, since people are reporting similar things on other kernels and it still (has always) choked at least somewhat during updates on my device.

nomerges 1 should hopefully be a happy medium, allowing simple merges for cfq/row schedulers to perform well and *****y apps/services like Play Store, while also not allowing all merges so that deadline and row can be a little more like sio/noop. For our finalized tweaks we also favored read a little more for deadline to make it faster, and favored writes a little more on row to make it less of a fat cow when writes get heavy. Now... back to cfq! :D
[Samsung Galaxy Nexus] Zadeis:
Now upon reading through those links... two things stuck out for the CFQ scheduler immediately since I was going through the default values as I was reading.

Slice_idle and back_seek_max. I then looked at your script again and noticed you already tweaked these so I may give your tweaked cfq settings a try and see how that pans out.

Thanks for the info though. Like I said I like to know what things do before I put the tweak on my devices.
[Samsung Galaxy Nexus] creeve4:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt

I am not experiencing any improvement with nomerges=1. I'm using the script you posted a few back, there is still plenty of lag when installing even smaller (~6 mb) files from the Play store.

CFQ is slightly better, but still significant lag.

Deadline and Interactive. AOKP ROM built today.
[Samsung Galaxy Nexus] agayabag:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I'm sorry, I didn't see your signature, sir.

Hi sir osmo, I just wanna ask something.

How do I know the script that you wrote is working on my device?

I downloaded the file that you shared just now, then I took away .txt extension, I copied to /system/etc/init.d, applied 755 on that file, then I reboot.

After reboot, I looked at /sys/block/mmcblk0/queue/read_ahead_kb, but it still 1024. It supposed to be 512, ain't it?

Did I miss some'em? Thanks in advice.

Oh yeah, I'm using latest CM nightly and r366 Franco's.
[Samsung Galaxy Nexus] osm0sis:
You both need to check to make sure your ROM isn't overriding the settings later in the boot. agayabag, init.d is a directory, I hope you mean you put the file in the init.d directory and applied correct permissions to both. This is getting a little ridiculous. If you aren't advanced/don't already have init.d working/don't know how your ROM works/don't plan on helping to tune cfq then please don't bother with the script because this thread is turning into an init.d support thread, and that's annoying.
[Samsung Galaxy Nexus] creeve4:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

None of the settings are being overwritten.

After setting CFQ as the default and rebooting, I am seeing a large improvement, but deadline is still super laggy even with nomerges=1
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2

For the AOKP users, another thing is the VM background ratio and VM dirty ratio.

By default some of the AOKP builds use a very high VM dirty ratio and very long writeback values for (ostensible) battery savings. I found in my subjective testing that it clashes pretty nastily with some of the franco kernel tweaks.

You could try some of these adjustments to the VM settings - either in AOKP Performance Control, or by adding or adjusting these commands in your init.d. They seemed to improve things for me (Just FYI, I use RoW as my primary scheduler, so I offer no guarantees as to what this will do with deadline or cfq).

echo 20 > /proc/sys/vm/dirty_ratio

echo 5 > /proc/sys/vm/dirty_background_ratio

echo 200 > /proc/sys/vm/dirty_expire_centisecs

echo 500 > /proc/sys/vm/dirty_writeback_centisecs

echo 0 > /proc/sys/vm/swappiness

echo 300 > /proc/sys/vm/vfs_cache_pressure
[Samsung Galaxy Nexus] osm0sis:
There will be differences from device to device and ROM to ROM. Probably what you're looking at. deadline is vastly improved over its own defaults, as is row. I find row best on my GN right now, and deadline best on my N7. Some people in our testing group find deadline better on their GN over row still. Every device is different, especially once you throw custom ROMs into the mix; there're also the elements of preference and usage.

What are your interactive settings? r366 defaults or our winning tunables (on my settings post)?
[Samsung Galaxy Nexus] creeve4:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I'm using the winning tunables for interactive.

The deadline tunables do make a noticeable difference, but don't help with the lag when installing apps through the Play store.
[Samsung Galaxy Nexus] osm0sis:
Good, I still think our winning ones out-perform the current defaults. ;)

Anyway, the Play Store update/install lag is a Google problem, not a Franco problem - I have it too; we're just trying to make it a little better, and nomerges 1 apparently helps for those who were having extreme cases.
[Samsung Galaxy Nexus] creeve4:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

What should the write speed be for the sd memory on theses phones? I'm getting around 1 MB/s with several sd speed testing apps. Seems slow.
[Samsung Galaxy Nexus] osm0sis:
Play with different read_ahead_kb settings (128, 256, 512,1024, 2048, 4096) and schedulers.

For an idea of roughly how they perform, here is some similar benchmarking for the N7: http://xdaforums.com/showthread.php?t=2111084

Note that Fsync on drastically reduces I/O.
[Samsung Galaxy Nexus] creeve4:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I've done some research about Fsync, but in real world scenarios, how likely are we to experience data loss or corruption due to a reboot/freeze while having Fsync off?
[Samsung Galaxy Nexus] osm0sis:
I've had some data loss from leaving it off, app and system, so I keep it on. Others swear by leaving it off and say they've never had any problems. I just turn it off when I know an app will perform a little better, and then reenable it when I'm done. Hmmm.. it'd be handy to have a toggle for that in my Notification Toggle setup.. Guess I'll go make a suggestion. ;)
[Samsung Galaxy Nexus] Kurre:
It's interesting how there haven't been any discussion about the vfs_cache_pressure value since Franco seemed to drop it to "1" some builds ago(?) Or have I totally missed it (even search didn't bring up any recent discussion about the matter) :eek:

Just wondering since some time ago, when it was tweaked, there was little "debate" if it should be high or low or what.. :)

Or maybe this is one of Franco's mental experiments again :p

But yeah those other default values act quite nicely :)
[Samsung Galaxy Nexus] Hawks556:
Thanks for this, I've noticed it too that franco's kernel and AOKP doesn't play well together. Hopefully this will help.
[Samsung Galaxy Nexus] reysonance:
Oh god it took me two weeks but I finally find the root cause of this bug that renders the stock browser unusable, I happen to stumble upon a couple of redditor that suffers from the same problem: http://www.reddit.com/r/GalaxyNexus/comments/19sodz/anyone_having_problems_with_the_stock_browser/

It was Lightflow. How the hell does a notification light management app affected the browser confounds me.
[Samsung Galaxy Nexus] hotnikkelz:
Not sure if this has been asked before, but does this kernel has 3.4 WiFi drivers similar to anarkia's kernel yet? I get best performance with these drivers but I like the convenience I've had with Franco's. Thanks in advance, sorry if its noob question :angel:
[Samsung Galaxy Nexus] reysonance:
No, it has the 3.0 driver.
[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

We have used them, they do work better but they don't work with WEP (which is ancient and ****) and lots of people complained so Franco chose to revert to older drivers. Those who had working WiFi all reported increased speed and signal strength. We lost to the noobs on that day....

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

Nah, there was no further convo that I saw. It's a bit weird - the combination of a low vfs_cache_pressure and low (or 0) swappiness is a pretty bad one imo. Caches that don't empty over time, and you're forcing the kernel and system to stay in ram. It's asking to get bogged down after a days use as the caches grow.

I'm still playing with the cache pressure and swappiness values to try and find what I think is a sweet spot. I quite like the current dirty ratio settings with RoW - it dumps stuff to disk aggressively enough that it never needs to do a big (ie noticeably laggy) write in the course of normal usage.

---------- Post added at 02:50 PM ---------- Previous post was at 02:46 PM ----------

No. The 3.4 drivers don't support WEP (and something else that I forget), and that always causes issues for people, so we're still on the old WiFi drivers.

But yeah, I agree, on WPA networks, the 3.4 drivers are noticeably better.
[Samsung Galaxy Nexus] reysonance:
Hooray for people clinging to 1999 standards! :D

I honestly don't get why people stick with WEP, with so many tools to crack it these days might as well set it to open.
[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

The other thing it broke was WiFi tethering, thanks for reminding me. Personally if it were my kernel I'd use the new 3.4 WiFi on new builds and then tell people to use the kernel back up restore feature in the app for the rare occasion you want tether etc I guess Franco is kinder than me :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] hotnikkelz:
It didn't break WiFi tethering for me, may be its a ROM issue?! I'm using the tethering right now :) bummer. I know about the WEP issue, what a shame. Impossible to have both?
[Samsung Galaxy Nexus] Khrushy:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

The current kernel doesn't use the 3.4 drivers. That test was a few months back.
[Samsung Galaxy Nexus] whitedragonz83:
So I've been mostly on CFQ with everything else stock Franco. However, I did try ROW with the tweaks listed earlier. ROW was my favorite when Franco first added it to his kernel, and I am glad I went back with the tweaks. For 99% of my time on the device, this feels very smooth and perfect. The 1% of the time I need to do an app install/update, I decided to just be more patient and not multitask. Though I could with ROW, it was still a little rough at times compared to when no installs/updates were occurring (obviously).

This is more of a post to thank those who worked on tweaks for Deadline and ROW.

Maybe when CFQ is tweaked a little I will go back to it for some tests.

Thanks again for the hard work!
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Malaroth thank you for posting that init.d script for the schedulers, very useful.

As a reply to that fsync discussion little earlier I've had a freeze while using the camera once. I had to pull battery and when booted the pictures were just a gray square. Missed some nice pictures! So I leave it on for now, I'm not noticing difference.
[Samsung Galaxy Nexus] szale9001:
Just wanted to post incase others were having trouble. When I downloaded the revised io script with nomerges=1, I had trouble with that value actually being changed. rq_affinity I knew would not stick to 2 but nomerges kept defaulting to 2 as well despite having the script executed on boot. Script permissions were correct and everything and the other values were showing up as modified as well. Not sure why this was an issue in my case but what fixed it for me was to move the first series of echo statements below the "wait for android os" statements. After I did that, nomerges began to show up as 1 and the rest of the values still seemed correct as well. Not sure if anyone else had this issue but I figured I would post. Using CM10.1 most recent nightly with franco r366.
[Samsung Galaxy Nexus] Samhain77:
R: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I've just tried. The same happens to me :confused:
[Samsung Galaxy Nexus] creeve4:
nomerges must be set after a delay, this works:

# wait for android os
until [ `pidof com.android.systemui` != "" ]; do
sleep 1
done;
sleep 25;

echo 1 > /sys/block/mmcblk0/queue/nomerges;
[Samsung Galaxy Nexus] CADude:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

I hope the WEP people get their WiFi cracked for that.
[Samsung Galaxy Nexus] irminsul:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

He Os i used your color init.d script, but it gives me a slightly pinkish view on keyboard with low brightness. Any idea what parameter to change?
[Samsung Galaxy Nexus] dracon6ai:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Seems like a easy way out but I updated to the latest Lean Kernel available in Franco's app and did some SD card testing and got Deadline, Sio, and Row to perform around the 8-9mbs range (with varying buffer sizes) compared to the 0.8-1.7mbs I was getting on Franco's latest. Also no more play store lag and Fx Guru runs like a champ again. Don't know what Imo did (haven't had time to dig, sorry) but thought I'd throw it out there for you true testers that love to dig.

Laziness is nothing more than the habit of resting before one gets tired!
[Samsung Galaxy Nexus] stevensoaj:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

What are you using to test SD card read and write rates?

Maguro | SlimBean 4.2.2 | AK Cylon 728
[Samsung Galaxy Nexus] ChazzMatt:
Maguro Samsung Galaxy Nexus I9250 on 3.4 kernel

What does everybody think about this? :fingers-crossed:

Maguro Samsung Galaxy Nexus I9250 on 3.4 kernel

http://xdaforums.com/showthread.php?p=38819834
[Samsung Galaxy Nexus] supernova_00:
Less red
[Samsung Galaxy Nexus] creeve4:
It's a lie! :p

Edit: for those unable to tell, this is a sarcastic remark.
[Samsung Galaxy Nexus] pkgnex:
Hey Osmosis (and company), I started some CFQ tunable evaluations by playing with back_seek_max over the last 20 hours or so. I can honestly not tell any difference between the values you list (0, 1000000000 and 2147483647) no matter what I do or how I use the device - which I guess may make sense for steady-state memory. Unless someone else has a different experience, maybe we should just set it to 1 for convenience.

I'll move on to group_idle now for the next day or so.
[Samsung Galaxy Nexus] thegtfusion:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Its true! I talked to anarkia, and its true. But really unstable.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] ak:
This is the source:

git@github.com:erik96/Linux-Kernel-3.4.git

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

http://www.xda-developers.com/andro...-for-everyone-tizen-os-info-xda-developer-tv/

no one can afford on the efforts of others to tell a lie.

no promises or promised, and only a shared work on my thread.

your statements leave the time they find
[Samsung Galaxy Nexus] creeve4:
sarcasm
[Samsung Galaxy Nexus] osm0sis:
That's cause they're all massive numbers and I was hoping 0 would behave like infinity, that way it's basically saying "no limit on back seeks"; 1 would be a bad idea though. ;)
[Samsung Galaxy Nexus] Pseudonym:
Re: [KERNEL][GPL][GN] franco.Kernel r366 -&gt; 4.2.2 | r364 -&gt; 4.2 | r300 -&gt; 4.1

Nice alibi :p

Sent from my Galaxy Nexus