yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] droid_legacy:
Sd Read/Write speed

Hey guys.

Just a question. I do not give much about benchmarks but I do always test SD IO Speeds with Antutu and Fancy Kernel works really great but my results alternate a lot!

Currently on SIO READAHED 512. I did try different read ahed sizes but i always get the follwoing results:

Score: 276

SD Card write: (8.6 MB/s) 86

SD card read: (20.9 MB/s) 190

Standard GNexus values are a lot higher and also with AK Kernel I get a score over 320+

with:

SD Card write: (13.6 MB/s) 124

SD card read: (30.9 MB/s) 194

tried Fsync On/off. No difference. Thats not a curious problem at all, because kernel feels good. Just wanted to know how this is for you, guys.

Currently running fresh purity 5.4.1 and FancyKernel r24 (exp)
[Samsung Galaxy Nexus] Pelide:
Super kernel! Great work! Thank you boype

I've used at least ten versions of fancy and till r24, r21 was the best for performance and battery.

But r24 (I skipped r22 and r23) is insanely good in terms of performance, but I find r21 is better regarding battery consumption.

Is this related to the improvement of performance?

(same kernel config as r21, ondemand+)

Tapatalkeggiato
[Samsung Galaxy Nexus] boype:
I usually don't run benchmarks, but I'll see if I can get to the bottom of this.

[EDIT] I get an initial 10.3 write / 32.5 read speed with rab 256 and sio. I tried other settings, but the results are just jumpy as hell. One time I'm getting 14 MB/s read speed, in another run I'm getting 30 MB/s, even though I didn't change anything. I'd just say (once again): screw benchmarks.

It is possible that you get better synthetic benchmark scores because the SIO in AK has different settings (in fact, AK currently uses some SIO settings I introduced a few releases back). But I introduced some other SIO settings recently, because the other ones were too aggressive and were causing some UI jerks.

Let the kernel settle a bit... In my opinion, there's no reason why r24 would perform considerably worse in terms of battery life.
[Samsung Galaxy Nexus] mixtapes08:
Your fairly right about that.. But the thing is it doesn't delay with other kernels such as trinity and ak.. Weird isn't I'm using liquid rom btw.

-3StarsAndaSun

---------- Post added at 08:38 PM ---------- Previous post was at 08:36 PM ----------

Only thing I'm noticing is my brightness slider having delay when adjusting and sometimes my systemui redraws itself.

-3StarsAndaSun
[Samsung Galaxy Nexus] boype:
I'm using CM myself and I'm not having any lags with the brightness slider whatsoever :confused:

Someone else was reporting that the systemui redraws itself. I guess I could change the launcher's lowmemorykiller class to prevent that...
[Samsung Galaxy Nexus] Pelide:
Thank you boype for the quick feedback, I'll update in a couple of days.

P.s. A very difficult question :eek: which rom do you think is the best coupled with your kernel? I know this is a very personal thing, but I don't know if, from a kernel dev point of view, there's something particular in one of the million gnex roms (yes, you can pretend you did not see this question XD :D )

Tapatalkeggiato
[Samsung Galaxy Nexus] thegtfusion:
I use purity 5.4.1, hands down the best rom i ever used.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] boype:
The best ROM? I don't know, really.

I cannot say I have tried many ROMs anyway. I have always used CM10 / 10.1 nightlies since I got my GNex. I only installed Paranoid Android a few days ago to fix some bugs in the kernel, but went straight back to CM.
[Samsung Galaxy Nexus] differentstyles:
For me too. If you want a rom which is not overloaded but has enough for good handling and is also after weeks still fast and of course bug free then this should be your first choice. I've tested so many but Purity is still my absolute favorite rom.
[Samsung Galaxy Nexus] TnK8iD:
I flashed the standard version few hours ago on purity 5.4.1 rom and the results looks like incredible, everything smooth and really snappy and the wifi doesn't lose the connection. Thanks great job
[Samsung Galaxy Nexus] bunnahabhain:
Boype did you compare the official CM Roms to the jellybro kangs? They're compiled with built optimisations and should give better performance.

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] HessNL:
Thanks :)
[Samsung Galaxy Nexus] bolanrox:
Personally i am using Nexus evolution cm based and add rock stable as this kernel.

Sent from my Nexus 7
[Samsung Galaxy Nexus] differentstyles:
Same here. Since yesterday no wifi drops anymore.
[Samsung Galaxy Nexus] mohaimed:
I left my phone stand by at 100%. After 5 hours the battery fell down to 91%. Wifi,mobile data, gps all turned off. The phone was just lying. Is this normal? I did a clean flash for the kernel. Using paranoidandroid 3.5.. Is this normal? Do i need to change the kernel or rom or sth. Btw, i am on r24 with stock settings.
[Samsung Galaxy Nexus] stuffynet:
This is my battery drain after almost 8 hours. I did used wifi for sync and various updates (10min I think). Does anyone have this weird battery "thing" (before I turn my screen off it had 90%, when I turn it on it had 91%)? Is it normal?
[Samsung Galaxy Nexus] zoomy942:
I like that idea.
[Samsung Galaxy Nexus] BOY_:
Giving this a go. So far so good and super smooth!
[Samsung Galaxy Nexus] Invicta:
do you guys switch multicore value to 0 or are you leaving it at 2?
[Samsung Galaxy Nexus] omid900:
I am leaving it at 2, it just work great :)
[Samsung Galaxy Nexus] RevengeFNF:
How it works that multicore thing, with 0, 1 or 2?

I use the default, 2.
[Samsung Galaxy Nexus] Toushiro Hitsugaya:
This kernel is awesome. Battery still in test, but the smoothness is absolutely nice. Using stock ROM. Perfect work boype.
[Samsung Galaxy Nexus] Droiddude24:
I'm on r21 with stock settings battery is off the hook on wifi! Gonna test on LTE today
[Samsung Galaxy Nexus] differentstyles:
Impressive. In combo with Purity Rom. Still 33% left and over 3 h screen on time.
[Samsung Galaxy Nexus] lippol94:
Can you point me the page where it has been discussed :) It seems to be a common problem across multiple roms!

Thanks!
[Samsung Galaxy Nexus] boype:
http://xdaforums.com/showthread.php?t=2050596&page=404 <-- post #4031

http://xdaforums.com/showthread.php?t=2050596&page=406 <-- post #4058

I suggest you leave it at 2. Saves the most power, has very negligible downside. More info is in the knowledge base section in the OP.
[Samsung Galaxy Nexus] namtombout:
Since boype put fancy kernel out this has been the kernel of the moment. Many people are just now realizing it :D
[Samsung Galaxy Nexus] Gafanhotz:
I have that too.

Sent from my Galaxy Nexus through XDA Developers App.
[Samsung Galaxy Nexus] lippol94:
Do you know what they did to fix it on CM?

I'm experiencing the same on Purity after 24h+ of Fancy. Only on homescreen. If I open any app lag just disappears.

The only solution seems to be rebooting.

But that's really sad. I have no idea of what is going on as it happens suddenly.

EDIT: After a few researches I found out that you can "fix" the bug for a while changing static wallpaper to any live one and then back to static. I works.

Too bad that is not a final fix. Just a workaround until it happens again.

EDIT 2: Another thing I read is that, to fix it completely, you have to disable autorotation.

plus, new steps to fix it:

*Enable autorotation

*Click on recent apps button

*Rotate device to landscape

*Press home button

*Disable autorotation

Now, you'll have an obvious downside but at least lag is fixed.

I do hope Google will fix it in 4.3
[Samsung Galaxy Nexus] Gafanhotz:
I noticed that battery life is a bit bad here, 2 hrs on screen and with 17% left. On CM stock kernel I'm having a better battery life. ):
[Samsung Galaxy Nexus] scadilla:
Install problems

Not sure if anyone else has had or seen this. After I flashed r23 & 24 phone boots but I keep getting system ui stopped errors. I wiped dalvik and cache then flashed but still no luck. Any thoughts? BTW I'm running muzzy 4.2.2.
[Samsung Galaxy Nexus] lippol94:
Try switching to interactive applying osmosis tunables. You can find those values in his signatures.

They're wonderful and suits really well with this amazing kernel! :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TnK8iD:
The r24 combined with purity 5.4.1 runs really well, but the battery go down really quickly : any suggest?
[Samsung Galaxy Nexus] motorazrv3:
Install CPU spy from play store and look if your deep sleep is working.

Had the same issue. I wiped cache and dalvik cache. Now deep sleep works.

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] sergini:
Had 2 sod in the last 24h.

On the first I was using camera, on the second the phone was sleeping.

I had to remove battery to turn it on again.

Latest axiom rom with fancy 24 all default.

Tell me what info do you need so that I can help you.

Tried last_kmsg but it isn't possible, maybe because I had to remove battery.
[Samsung Galaxy Nexus] lippol94:
Stock settings? Did you have ak kernel installed previously?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] xFuGiToiDx:
Fancy r24 runs great with purity 5.4.1 even when under clocked to 1.06 GHz and still running buttery smooth. Almost pulled of 4 hours on screen time on my first test. :)
[Samsung Galaxy Nexus] gwindlord:
Also avoid using cores-disabling governors, like hotplug, intellidemand and so on, this could be a reason.
[Samsung Galaxy Nexus] sergini:
Like I said, all default.

Only changed rab to 256 (which doesn't seem very important) and the colors.

I clean installed axiom and flashed fancy on top of it.
[Samsung Galaxy Nexus] zoomy942:
Dang. UI studder is back.
[Samsung Galaxy Nexus] Charmacas:
How long are you running your phone without a reboot until this appeared?

My phone is now 26 h online and I did not have a single lag so far. I never had this before.

Also it would be interesting to know what ROM you're running. I am on Carbon Nightly from the 11th of May.

Also about battery life. I am a not a gamer but I am using my phone very often during the day. So far it seems like I am going to get about 3 hours of Screen On Time which is very good I think. I saw not much people who got more. The most are about 3 hours. So no problem here for me. It's only getting better. Thank you [MENTION=4615478]boype[/MENTION] !

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] lippol94:
For me it's only on homescreen. Disappears when running any app. Can you confirm?
[Samsung Galaxy Nexus] boype:
Probably (or even most likely) the same memory leak lippol94 and I experienced. It's a ROM problem, not a kernel problem. The latest CM versions have this fixed.
[Samsung Galaxy Nexus] lippol94:
Are you sure CM fixed it? Can you point me the commit which fixes it?

I can't find it anywhere!

Thanks!
[Samsung Galaxy Nexus] Charmacas:
Which launcher do you use?

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] lippol94:
Nova. But I tried in the past with Holo Launcher, Apex and Stock. Same problem.

It's a known 4.2.2 bug, which drives me crazy!
[Samsung Galaxy Nexus] bunnahabhain:
RC2 or only the latest nightly?

BTW: Can i ask again what you think of the linaro optimized Jellybro Kangs?

-> http://fitsnugly.euroskank.com/?rom=cm10&device=maguro
[Samsung Galaxy Nexus] agritux:
i am using nova prime. i have no lags on home screen or app drawer with fancy kernel. i am using stock fancy settings.
[Samsung Galaxy Nexus] zoomy942:
Im using the latest CM nightly, which i think is RC2 also. Ondemandplus with 384/1400.

I'll agree it's a ROM thing. CM says to have fixed it but it still happens so I'm debating on rolling back to CM10 or waiting till this Google I/O thing to see whats happening there.
[Samsung Galaxy Nexus] Rufufu:
Today, I tried using 1400 MHz for the max frequency for the first time. I've got the same lag problem than someone had before. The phone was very very (very) laggy until I came back to 1200MHz. I was using interactive gov, and the same thing happened with ondemandplus.

I'm on CM10.1 RC2 with r24 std release.

I stay at 1200MHz which is fast enough for me, but I wanted to report this.
[Samsung Galaxy Nexus] Charmacas:
This sounds like a voltage problem. Try raising it a 25 mV step and see if it appears again. And so on. :)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] Rufufu:
Thanks! I need to download the ext version for that, maybe I will try but I think 1200 MHz is enough for me.
[Samsung Galaxy Nexus] zoomy942:
Maybe we can have the kernel voltage upped a bit by default? I'm trying 384,1200 Interactive Deadline right now
[Samsung Galaxy Nexus] Charmacas:
As far as I remember boype already raised the voltage of the 1400 frequency. Maybe your ROM does run some script or you do. Did you all check if something reconfigured the voltages?

These are the default ones:

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] differentstyles:
Same combo here and for me it's amazing. Never had such good results with Ak.
[Samsung Galaxy Nexus] Rufufu:
Since I'm using the standard version of the kernel, I can't change the voltage neither check the values in trickster. In fact I am not very motivated in overvolting, maybe it is stupid, but I don't want to damage my phone. Plus I'm good with 1200 MHz.

But thanks, it must be a voltage problem, you are right. When I was using ak kernel, the 1400 MHz step was OK.
[Samsung Galaxy Nexus] boype:
Apart from all other discussions here: I found a bug in SIO which is rather big. I have already fixed it and guess what: more smoothness.
[Samsung Galaxy Nexus] zoomy942:
Update incoming?
[Samsung Galaxy Nexus] bunnahabhain:
Great... I am using deadline cuz I realised that sio doesn't perform very well. I'm using this tunables :

250/2500/1/1/8

Would you like compare this to the fixed sio?

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] boype:
Most likely within the next 24 hours.

The new values I set in the fixed SIO are not too far away from that :good:
[Samsung Galaxy Nexus] zoomy942:
Are you going to include that memory idea for the home screen studder?

---------- Post added at 07:19 PM ---------- Previous post was at 07:14 PM ----------

This
[Samsung Galaxy Nexus] ReMuSeR:
one question boype what ROM are you using atm :P
[Samsung Galaxy Nexus] fr4nk1yn:
Cyanogenmod.
[Samsung Galaxy Nexus] wai10691:
Booting takes shorter time now! Less than 30 seconds, build 24 :D
[Samsung Galaxy Nexus] lippol94:
That's because the kernel trims cache and data partitions only when you wipe cache and dalvik.

Otherwise, boot process runs as usual

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] tylerdurden83:
On r24 I have some lag while playing bluetooth streamed songs to my car's stereo.

My frequencies are:

min - 384

max - 1.228

max screen off - 384

min screen on - 384

Everything else is on default (governor, voltages, hd audio etc).

I didn't have lags on ak kernel with lower screen off and min frequencies (230).

Is there anything I could change in the settings to make it smoother?

Thanks for an amazing work!
[Samsung Galaxy Nexus] Charmacas:
I would try to change Max Screen Off to 537.

-- EDIT --

Yes and [MENTION=2564730]parkson[/MENTION] is right. Try to set MCPS to 0. :)
[Samsung Galaxy Nexus] parkson:
Multicore power saving: 2 may be too aggressive. I set to to 0; don't really notice a hit in battery and experience less stuttering and freezes (mostly music and games related)
[Samsung Galaxy Nexus] tylerdurden83:
Could it be causing the lags I described two posts above? Cause on ak kernel it didnt lag with 230 mhz, so I'd think that the frequency of 384 would suffice. But I remember having multicore saving to 0 on ak as default...
[Samsung Galaxy Nexus] boype:
In fact, the lagging bluetooth audio streaming has been reported before. I'm sorry to say that I don't really know what's wrong, as it is kind of a dealbreaker for people using bt audio.
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4615478]boype[/MENTION] maybe you could have a talk with Stefano aka [MENTION=3685904]anarkia1976[/MENTION] because as reported he seems to have solved the problem. :)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] mpokwsths:
Tried r24 but experienced some kind of occasional lag in the UI (not the systemUI leak, I use the latest Cm 10.1). Went back to r22, the smoothest kernel (except some scheduler lags) I have ever tried on the GNex. Actually r22 with the strange color settings fixed my purple screen tint, after some serious tuning by me of course...
[Samsung Galaxy Nexus] buckmarble:
I wish Google wouldn't have changed the blue tooth stack. Bluez was much better than blue droid.
[Samsung Galaxy Nexus] JonBsbB:
I see some of you are running this with cm10.1 rc2. As i am too. I'm very noob with what governor/scheduler combo is battery savey but still smooth going. And what is good for a screen off profile. Probably been asked before. I looked but didnt see anything that seemed to help me.

Thank you
[Samsung Galaxy Nexus] namtombout:
Boype stock settings are good.

If you're feeling adventurous play around with different combos until you find what you're looking for. Try reading different kernel threads because different users have posted some good tweaks. (osmosis and nephlim to name a few)
[Samsung Galaxy Nexus] JonBsbB:
Thank you
[Samsung Galaxy Nexus] ReMuSeR:
Waiting for new update heared its da bomb hahaa
[Samsung Galaxy Nexus] boype:
Sorry to disappoint you, but I can't make it today. Tomorrow for sure, I have almost everything ready.
[Samsung Galaxy Nexus] stevensoaj:
boype, if I wanted to increase systemui priority in an init.d script, how would I do so? I see this in your github, but how would it translate to an init.d script?

+#*increase*systemui*process*priority

*97 +sleep*20

*98 +

*99 +loopcount=1

*100 +

*101 +while*[*$loopcount*-le*18*]

*102 +do

*103 +**if*[*$($busybox*pgrep*com.android.systemui)*]*;*then

*104 +****$busybox*renice*-20*$($busybox*pgrep*com.android.systemui)

*105 +****exit

*106 +**else

*107 +****((*loopcount++*))

*108 +****$busybox*sleep*10

*109 +**fi

*110 +done
[Samsung Galaxy Nexus] x.v_:
Well, I'm no kernel dev, but that looks to be some kind of oddly formatted shell script. (I'm sure there is a reason, I just don't know it.)

The essence of it is

renice -20 `pgrep com.android.systemui`

Running that may or may not work, but your answer is at least something similar. :) I'm unfamiliar with shell syntax so I can't really refactor much more than that. (Everything else is just checks, nothing critical. -- I think)

P.S. I've yet to post in the thread, but loving your work boype! Keep it up! :)
[Samsung Galaxy Nexus] stevensoaj:
It was copy and pasted from github on my phone. That's why it looks weird. But I did find the answer.

# wait for systemui and increase its priority

until [ `pidof com.android.systemui` ]; do

sleep 1;

done;

renice -20 `pidof com.android.systemui`;
[Samsung Galaxy Nexus] JonBsbB:
Loving this kernel
[Samsung Galaxy Nexus] boype:
r25

Hi all,

r25 is ready for download now. The change log is:

introducing SIOplus i/o scheduler (modifications: functionality for specifying the starvation of async reads against sync reads; starved write requests counter only counts when there actually are write requests in the queue; fixed a bug)

swapped the 729 MHz CPU OPP with an 806 MHz OPP (someone told me ~810 MHz was a 'sweet spot' for responsiveness)

updated to Linux 3.0.78

set sched_mc_power_savings = 1 to get rid of microlags

scheduler system fine tuning

use dirty_bytes instead of dirty_ratio

increased read_ahead_kb to 384 (good intermediate setting between the sometimes more snappy 512 and the sometimes more responsive 256?)

nr_requests down to 160 (anything above causes slight stutter)

renice systemui process to -17 instead of -20 (-20 should only be given to very critical processes)

added lowmemorykiller launcher whitelist (makes the launcher 'unkillable'; thanks to franciscofranco)

As you can see, I modified SIO and made my own 'SIOplus' out of it. I only made the changes yesterday, so I hope it performs well over longer system-on-times. That said, this is kind of its testing phase, so please report if you experience any problems.

The reason for making the SIOplus version: I examined the scheduler's code and found a write starvation related bug, which I fixed. Other than that, I noticed I wasn't happy with the way SIO prioritizes read requests. It would always pick sync reads over async reads. So I implemented the functionality to pick an async read every X number of sync reads. (Hope the interested can understand what I'm talking about ;))

Overall, I hope this release can keep up to your expectations.

Best regards

P.S.: I'm uploading the source to github later today, as I'm currently not on my desktop PC (this is where the stuff is on).
[Samsung Galaxy Nexus] sergini:
This kernel has made a long path and is now behaving like an adult. Thank you boype for your awesome work.

I'll test sio plus right now.
[Samsung Galaxy Nexus] bunnahabhain:
Moin!

Thanks for the update!
[Samsung Galaxy Nexus] Rufufu:
There is definitely a problem with 1400MHz OC and my phone.

I downloaded the r25 ext version and tried to up the voltage for the 1420MHz step from 1330 mV to 1430 mV by 25 mV steps, and the was stayed very laggy. Is it a good idea to try upper voltages?

I'm still on cm10.1 rc2.

Strange thing is my phone went until 1600MHz when I was using AK kernel (a few months ago, I started using your kernel since r10 approx.)

Anyway thanks Boype for your kernel, which is almost perfect! I love your work!
[Samsung Galaxy Nexus] wai10691:
Flashing it over r24 and it took awhile to boot. Like 5 minutes like that. Just to let those who are going to flash this beast. :D
[Samsung Galaxy Nexus] mixtapes08:
Dude you should apply for RD. Your definitely worth it. :).. Technicality and writing your own tweaks will definitely move you up to RD status. :)
[Samsung Galaxy Nexus] boype:
I already applied once, but the RD application system was broken and my application got lost. Maybe I should try again

I'll have to dig deeper into this. Strange thing is that 1400 MHz works just fine for some users (like me), but for others it doesn't. I already increased the voltage last release...
[Samsung Galaxy Nexus] Rufufu:
Maybe my phone is getting to old, or something in the hardware has changed. I bought my gnex in feb 2012. Anyway, I am very happy with 1200MHz, 1400 is just for fun in my case. So if it bother you, don't look at this.
[Samsung Galaxy Nexus] parkson:
r25 feels magical on latest cm nightly (toro). Min freq bump to 384 and I'm ready to go :thumbup::thumbup::thumbup:

Thanks for this wonderful update, boype!

*edit*

Possible cause slight variances in binning process used for gnex chips?

Have you always been able to run at 14XX without issue, no matter the kernel?
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4615478]boype[/MENTION] those changelogs you're giving are really good. You also give your thoughts why you've done something. So first of all thanks for that! ;)

r25 booted up well and there were no problems. As usual I changed the max freq to 1420. Anything else is on default.

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] Rufufu:
Only tried with ak kernel and it worked. Never tried with something else.
[Samsung Galaxy Nexus] Lancez:
Ho Lee Sh!t, you are a helluva dev :thumbup: loving your work :D
[Samsung Galaxy Nexus] xFuGiToiDx:
Will flash r25 after I'm done testing the modded Franco r378. Let's see if I'm also able to get 4 hrs on screen time with new fancy kernel. So far I'm down to 13% and 3:53 hrs on screen time with an uptime of 11 hrs..
[Samsung Galaxy Nexus] shawnaye:
ditto on the 1400mhz working fine, been using it for quite some time now.
[Samsung Galaxy Nexus] Argasil:
With r24 (ondemandplus + sio) i madre 16 hours with 4 hours of screen on, and about 2 band half hour of WiFi and half hour of 3g, awesome!! I left all kernel i tried and absolutly stato with this kernel, this evening a flash r25 anyway good work Boype,this kernel become one of the best for pur nexus!