yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] y3mita:
the zip is in this thread, search and you shall find!

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

http://xdaforums.com/showpost.php?p=20552503&postcount=46
[Nexus S Android Development] AskingBen:
Best Kernel available for Nexus S. Thank you for this amazing work! Everything is super smooth and fast. Batterylife is also unbelievable good.
[Nexus S Android Development] bravo04:
hi everyone.

based on your exp, what is the best rom pair with this kernel?
[Nexus S Android Development] sperelli:
Not yet, the work of this CyberGr was for me the best on GB, therefore i'm giving it a deep testing on ics... thx for the clues, i'll try them.

;)
[Nexus S Android Development] KrisMurdrum:
I'd have to say Peter Alfonso's

Carved into the Void using my ICS powered Magic Rune Stone

(Peter Alfonso's latest nightly and Eugene373's ICUP-Speedy4)
[Nexus S Android Development] y3mita:
eugene373, would you please add lulzactive governor to your work? I had been testing it on mathkid95's Kernel... and I had just flashed Peter Alfonso's ROM and would love to try your next speedy! If you could throw that *bonus* governor, please.

Thank you much!
[Nexus S Android Development] eugene373:
kernel work is never done :cool:

This release was to get everyone off of the other Kernels ( Speedy-3 & Below ) due to Data & System Corruptions that was Causing reboots...
[Nexus S Android Development] invd:
Got a strange behaviour: I flashed your Speedy-4 over Speedy-3 (on AOSP+) without any problems. Worked great. Then I read, that a wipe is absolutly neccessary and so I did a wipe... after that I installed all apps again and now I get random freezes and reboots (what never happend before). I used the same config as before in NSTools. Any idea what could have gone wrong?

EDIT: Nevermind, got it fixed by restoring all apps and settings with titanium backup...
[Nexus S Android Development] y3mita:
Tks Eugene for considering the option to include lulzactive into your kernel.
[Nexus S Android Development] Auxilium:
Definitely the best kernel for battery life, which is what I'm all about.

Thanks Eugene.

Sent via Nexus S
[Nexus S Android Development] santeana:
I am using Irtehun's "Nuhetri" 1.0.0 ROM. It's incredibly responsive! There is zero lag when opening contacts, phone and app drawer. Scrolling is smooth and buttery like many of the roms here. Only thing is, his newest version comes with Nova Launcher and I prefer Trebuchet so I just flashed that one over and use it instead. But really... this is a kernel thread, so probably should post your question in the general section instead
[Nexus S Android Development] bravo04:
i think that's not necessary. this is just a simple question but not general, besides my question is related to the kernel. :)
[Nexus S Android Development] jalyn02:
Could we get a better color or...?
[Nexus S Android Development] moinsheriff:
what nstools tweaks are you using for battery life?
[Nexus S Android Development] aLNG:
undervolt?
[Nexus S Android Development] Emama:
If I dont have reboot on speedy3 I don't need to flash speedy4?

coz I don't wanna wipe factory reset
[Nexus S Android Development] Auxilium:
You only need to wipe cache/dalvik to install the kernel

Sent via Nexus S, running CyanogenMod 9
[Nexus S Android Development] Emama:
but

http://xdaforums.com/showpost.php?p=21398933&postcount=944
[Nexus S Android Development] aLNG:
that if u have prob with speedy-3
[Nexus S Android Development] Auxilium:
Ah, coming from speedy 3. I guess you do. Sorry. I came from a different kernel so I didn't have too.

Sent via Nexus S, running CyanogenMod 9
[Nexus S Android Development] phillevy:
I've had Speedy 4 flashed over 3 with just a dalvik wipe for a few days now - I didn't see the advice to do a full wipe however everything is totally fine fast and stable with CM9 alpha 20.
[Nexus S Android Development] provolinoo:
I guess bad colours are related to high refresh rate... the same problem was present in steve garon's kernel and he fixed it going back to 56fps default rate :)
[Nexus S Android Development] adamus123:
me too on stock rom, no issues/reboots
[Nexus S Android Development] hr_kaleu:
when I try to download speedy4 I always gettin' an error:

This webpage has a redirect looip

The webpage at http://www.multiupload.at/LTRNGI13AM has resulted in too many redirects

already tried different browsers, different PCs,...

anyone else suffering this problem?
[Nexus S Android Development] spitzedanese:
I had Speedy-3 before and some of my camera pictures became corrupted. So I did a Wipe and installed Speed-4.

It's faster than before, more smooth and battery is very very very good.

The best kernel so far.
[Nexus S Android Development] nadiros:
Eh - I've used all of your kernels as they've been released and gotta say just how

great Speedy-4 has been.

My favorite new feature (besides stability, speed, and frikkin sweet battery) is

the much awaited 1100mhz step ! :cool:

Thanks for your work

-peace-
[Nexus S Android Development] mrruin:
same problem here
[Nexus S Android Development] climhz:
It's not multiupload.at, try multiupload.com
[Nexus S Android Development] hr_kaleu:
still the same...

original link goes to multiupload.com, but still no luck...

update:

I managed to download it on a different workstation...
[Nexus S Android Development] Gonzomino:
Can not open the Downloadlink
[Nexus S Android Development] koax88:
thx for this great work eugene, i got excellent battery life with your kernel, no reboot at all, all stock setting, completely stable for me..right now im at 18% and phone had been running for 22hours ++ with kinda heavy usage, xda, 3d gaming, browsing and the list goes on..:):):)
[Nexus S Android Development] flodb113:
+1

Transmitted from somewhere in space... from my Nexus S... and Tapatalk.
[Nexus S Android Development] demo23019:
missread.....
[Nexus S Android Development] Serious_Beans:
I'm seeing so many people with really good battery but I can't get more than 18hrs-20hrs out of a day, I think I need a new battery, this battery is a year + old.
[Nexus S Android Development] vhgomez36:
Most people would do anything for that. I counted over 100 emails just today a few text. Just 7 hrs into work and I had to recharge.
[Nexus S Android Development] vhgomez36:
Delete...double post
[Nexus S Android Development] hay112:
How does a kernel make this much difference in battery life!?!?

Eugene, this kernel is amazing, my battery life is about 1/3 better than it was before. Stability is also better than every other kernel I've tried. <3 it!
[Nexus S Android Development] t3xboar:
guys depends what your usage is...

my 3d12h romp with his-2 kernel was only doing phone calls, text and emails... no video, no net etc.. as a test.

Nobody in the world will hit 3 days with browsing, video, games etc on the stock battery lol.

I've just flashed the new beam rom and this -4 kernel. now im going to do a "real" world test of video, browsing etc... I'll post up how it goes.
[Nexus S Android Development] MFire:
You're kidding ,

I am at 2 (two) days of usage on stock kernel and still have 30% battery left with 1.5 hours of calls, heavy online gaming, browsing, SMS and lots (and I mean lots) of music.

Too bad I didn't take a screenshot but trust me stock OTA kernel is also very good when it comes to performance and battery life.
[Nexus S Android Development] Emama:
cannot turn on wifi after flashing 4 from 3

seems its better wipe factory setting
[Nexus S Android Development] rickbosch:
I skipped Speedy-3, but needed to update my ROM today so flashed Speedy-4 with Pete Alfonso's BuglessBeast. Wow. So far, so very very good.

edit: the green screen flash still happens and I unfortunately don't want to stop using voodoo sound, but will definitely keep my eye on this thread.
[Nexus S Android Development] aLNG:
+1 with this setup it make me think 1000x times to try other roms
[Nexus S Android Development] :
Eugene, sent you a PM, but thought I'd let your thread readers know too:

Anyone who was looking at the benchmarks yesterday (16th Jan) they were WRONG :eek: because I was doing an experiment late at night, and forgot to put the original raw data back. More details here: http://xdaforums.com/showpost.php?p=21507978&postcount=133
[Nexus S Android Development] t3xboar:
hmm thanks for the heads up. got a link for the one you installed by any chance?

I'm just waiting until someone dips their fingers into the newest kernel series that was on the arch... aparently they give even better preformance. ;)
[Nexus S Android Development] y3mita:
About the 200mhz block, eugene373 I do not think it is the ROMs fault. I had run Peter Alfonso's with mathkid95's kernel and I was able to use the lower frequency of 100mhz...

Now, I'm on a fresh install of same ROM and your kernel and I can confirm that NSTOOLS only let me go below as far to 200mhz as well....

So, it is not the ROM limiting you to 200
[Nexus S Android Development] steve.garon:
The 200 Mhz limit is a kernel limitation. There is a patch available to remove the limitation. Not sure if eugene has that patch in his kernel.
[Nexus S Android Development] tchaari:
I think NSTOOLS is not fully compatible with this kernel. Try setCPU...
[Nexus S Android Development] aLNG:
nstools works fine with this kernel

for me its fine with 200Mhz as long the battery usage still the same
[Nexus S Android Development] y3mita:
Right but isn't that being a little egoist with others who do not share your point of view?

Yes 200mhz is okay and it may not be much of a difference! I'm sure but when it comes to play with governors and testing yes all possibilities are appreciated!

Anyhow, I'm about to give my report later today as I did on mathkid95's thread using his kernel.

So far, I had only one reboot while using tweetdeck phone froze up and a reboot followed!

All default settings! nothing changed!
[Nexus S Android Development] tchaari:
Just read few pages ago that you can use 100Mhz only with setCPU and not with NSTOOLS...
[Nexus S Android Development] y3mita:
Hmm, good to know. I will leave at 200mhz since I might change Kernel and NSTOOLS is more complete IMHO
[Nexus S Android Development] tchaari:
I think that speedy4 needs a full wipe and a fresh ROM install. I read that few pages ago...
[Nexus S Android Development] Serious_Beans:
200mhz is pretty much the same as 100mhz, I can under volt both steppings to the same 915mv so I'm just sticking at 200, its faster and uses the same amount of energy as 100mhz
[Nexus S Android Development] :
Not sure about this. Someone around here recently posted about the power usage being a function of processor capacitance and frequency. Can't remember the formula he stated, but if he was correct then double the frequency is double the power drain. I had to put down my book on Maxwell's Field Equations halfway through the first chapter, so don't take my word as gospel!

Sent from my SNES
[Nexus S Android Development] aLNG:
can u find again that source...i would like to take a look at it

because i dont experienced big difference when using 200/100

i still get 3 days for light use, 1-2 days for normal use and 1 day for heavy use
[Nexus S Android Development] ragnarokx:
I've actually become very good at using init.d scripts because of this 200MHz/NSTools thing. Could write and set permissions in my sleep :p
[Nexus S Android Development] eugene373:
Speedy-5 will be released tonight.. Fixes a few minor issue..

Regarding 100Mhz

100Mhz is only active if set to 100-1000 freq.

If you over clock, 200Mhz become the default, hope that clears the 100Mhz Q. up.
[Nexus S Android Development] tchaari:
Eugene, thank you so much for keeping this amazing Kernel updated ;)
[Nexus S Android Development] ragnarokx:
Is this an upcoming feature for Speedy-5? Or are you saying this is how it works with Speedy-4? Because I never overclock and NSTools doesn't let you set below 200MHz. Same for built-in CPU control in AOKP ROM.
[Nexus S Android Development] y3mita:
Thanks for the update...

Regarding 100Mhz, I have not touched your kernel it has default settings which are supposed to be 100-1000 smartassv2 and sorry to disapoint but mine stays at 200Mhz only.

Steve.granon suggested is a kernel problem and there's a patch for it.

Thanks again for your contribution to the Nexus S device!
[Nexus S Android Development] ragnarokx:
Steve must have done something, because NSTools has no problem setting his kernel below 200MHz. Although his is overclocked to 1.1GHz by default, don't know if the 100-1000MHz rule applies to his kernel as well.

Love your kernel btw Eugene. I'm always surprised at how fast it is after I come back from a different kernel. Hopefully one day I'll learn my lesson and stick with yours :)
[Nexus S Android Development] eugene373:
okay I'll look into this before releasing the update tonight.
[Nexus S Android Development] zyrtek69:
I usually under clock to 800mhz and when I do it takes away 100mhz too. Doesn't really matter to me just sayin.
[Nexus S Android Development] steve.garon:
https://github.com/stevegaron/SG-NS-ICS/commit/c4aa5f374fe75c5ab266590ddfcc415dd8de0e9a

;)
[Nexus S Android Development] bioan:
Will you include BLN for missed calls ?
[Nexus S Android Development] eugene373:
thank you :)

I don't have that patch, but that tells me what to fix :)
[Nexus S Android Development] rickbosch:
As far as I've read, the 100 option is overwritten by 200 when you have GPU acceleration selected under development.

There is a patch for it, Eugene just hasn't implemented it, yet... ; )

Sent from my Nexus S
[Nexus S Android Development] y3mita:
I don't have that enabled though!
[Nexus S Android Development] ragnarokx:
If you look one page back, Eugene said he will fix it. Calm down :/
[Nexus S Android Development] y3mita:
I'm calmed, always am.
[Nexus S Android Development] :
Couldn't find the post I'm referring to, but found this:

The power consumed by a CPU, is approximately proportional to current CPU frequency, and to the square of the CPU voltage: [1]

P = CV^2*f

(where C is capacitance, f is frequency and V is voltage).

Source: http://en.m.wikipedia.org/wiki/CPU_power_dissipation

Sent from my SNES
[Nexus S Android Development] demo23019:
using since released no issues at all with speedy 4 daily 200/1.3
[Nexus S Android Development] ragnarokx:
So voltage is more important since it is exponentially related to power, but frequency is still directly related so there is a real difference between using 100MHz and 200MHz..
[Nexus S Android Development] uansari1:
Good question..
[Nexus S Android Development] :
Not exactly. In this case 200mhz has 950mv, 400mhz has 1050mv.

V squared:

950 > 902500

1050 > 1102500

So the impact of v squared in this frequency step from 200mhz to 400mhz is just 12% increase

The impact of f being doubled is 100% increase!

Sent from my SNES
[Nexus S Android Development] zyrtek69:
How'd u get xda app to work on SNES? ;]… wish school was this interesting , I might learn something.
[Nexus S Android Development] tchaari:
So undervolting combined with a 100Mhz max frequency decrease may lead to some interesting extra hours without recharging...

Hey bedalus, Eugene will bring you some work to do in your benchmark tonight after the update :D
[Nexus S Android Development] :
The main power draw is the screen, and when that is off, the processor is probably asleep, so it wouldn't make much difference really!

Yep, new kernel soon = more testing!

At last, the SNES joke is appreciated!

Sent from my SNES
[Nexus S Android Development] TheLastMirana:
will download speed 5 when released
[Nexus S Android Development] tchaari:
Not before me :D:D:D:D:D

Sorry for the spam I couldn't resist :D:D:D
[Nexus S Android Development] y3mita:
First report Speedy 4 - Default settings

cpuspy: http://yfrog.com/nw3ppgp

Battery 52% discharging

Usage: 6h 44m

Screen on: 1h 55m 22s

NSTOOLS settings:

Governor: smartassv2

Min-Max: 200-1000

OC: 100%

Screen Off freq: OFF

BLN-BLD: ON

Touchwake: OFF

IO Scheduler: cfq

I did a fresh install of latest Peter Alfonso's ROM; wiped dalvik and flashed SPEEDY 4.

As you see, usage has not been much after full charge barely almost 7 hours. And I understand usually after a second charge things must improve. But I'm doing this test almost the same way I did with Matr1x Kernel when I was testing lulzactive v2 governor.

I will wait till I'm about 15% or less to start the charging process again.. and then I will change the settings to:

IO scheduler: bfq

Governor: lazy

leaving everything else default

If I see a better battery without affecting performance I might start playing with the voltages.

Hope this helps for reference to people trying to decide settings for your kernel.

Personal Note: I hope on my second report battery improves, with other kernel I was testing using *lulzactive* governor... my battery was barely used and performance near affected.
[Nexus S Android Development] aLNG:
This proved the formula is not correct in our matter.plus that is taken for Intel processor and still get many critics in oc forums.but about voltage relationship is true.I hope u can try to benchmark this relationship, what is the effect doubling the freq without changing the voltage :)
[Nexus S Android Development] juliano_q:
1h 55m 22s screen on is a lot man. Having 52% battery left after that is awesome, imo.
[Nexus S Android Development] y3mita:
I got more using this:

http://xdaforums.com/showpost.php?p=21493356&postcount=1570
[Nexus S Android Development] eugene373:
then please use that instead :rolleyes:

You have chooses in kernels

~Eugene
[Nexus S Android Development] y3mita:
Sorry if I offended you, not my intention.

And yes choices we have, therefore I am testing them and ultimately I will make my choice.

Thanks again for your work!
[Nexus S Android Development] jjhrrsn:
Mt
[Nexus S Android Development] eugene373:
oh no no no... :)

That was a " Use what works best for you" Comment, Didn't mean for it to come off rude if that is the way it was taken..

Sorry about that,

~Eugene
[Nexus S Android Development] eugene373:
Kernel Update

Kernel Update will be for in the morning or evening.. still a few more requests to add in & finish up on.
[Nexus S Android Development] y3mita:
You're a genuine gentleman there!

And lemme apologize as well for taking it the wrong way!
[Nexus S Android Development] bravo04:
nice.. i'll wait for it bos.. :D
[Nexus S Android Development] :
That's good to know. That'll teach me for trusting wikipedia. And what a good idea to test the power consumption at different frequencies. I am pretty sure I can make that happen. I might need a couple of days!
[Nexus S Android Development] cpaixao:
I might say the same thing as you did, just adding a word:

"I got more REBOOTS using this..."

I am out and off Matr1x kernel. Not just the kernel problems, but dev doesnt hear testers.
[Nexus S Android Development] aLNG:
this is not necessary..u can keep ur opinion to ur self
[Nexus S Android Development] d_phekt:
Eugene has stated that he is not building kernels to fit everyone's needs. All of our needs will be different anyways. He is basically sharing his personal built kernel with us. No need to be a spoiled brat about it.
[Nexus S Android Development] KrishhBhola:
I want this root for my phone, but I dont now, how I must do it.

I have ICS 4.03.

So is this kernel possible for my phone?

And if it is possible, how do I flash the Kernel?
[Nexus S Android Development] y3mita:
Let's come down a little bit.... eugene373's kernel has its goodies! his deep idle implementation rocks!!! And when I used it a while back was one of my preferred kernels.

And it is a matter of testing and check what works best for your phone with your needs! I'd say you experiment with all and just choose the one works the best for you. And by now, we all know not all phones can handle UV or OC , it is your job to play with them and make a decision.

I am switching to steve.garnon for now, speedy 4 gave me a few reboots! and not even changing default settings! I only played with it for two days! and I may have needed to stay a little longer to adjust voltages but steve just added governors that IMHO think are great if not better ones!

---------- Post added at 09:45 PM ---------- Previous post was at 09:30 PM ----------

Thanks a lot for adding more governors and boy lemme tell you! I'm donating nowwwww!

Thanks eugene373 ;)
[Nexus S Android Development] eugene373:
Speedy-5 is now Posted in all Flavors
[Nexus S Android Development] y3mita:
Please have a pizza pie and a soda on my name! Thanks again! violetrose225 ;)
[Nexus S Android Development] jalyn02:
Links are down or is it me?
[Nexus S Android Development] eugene373:
@y3mita

Thank you! That was greatly appreciated!!
[Nexus S Android Development] sean1984:
mirror link is working fine:D
[Nexus S Android Development] mkoch820:
Links are down for me too

Oops, sorry, mirror is working though
[Nexus S Android Development] navillos:
Why all with different scheduler's? why not one with all integrated. That's ridiculous you have to compile 10 different kernels because people won't use NSTools. So which one do you use Eugene?
[Nexus S Android Development] eugene373:
I use Noop to be honest.. and I was just trying to give options out of the gate without needing to adjust anything.
[Nexus S Android Development] navillos:
Well hell while your at it make one more with all schedulers in. :)
[Nexus S Android Development] y3mita:
+1 for those of us testers/ that'd be awesome! The more the merrier ;)
[Nexus S Android Development] eugene373:
all schedulers are active on all kernel.. the one's list is default schedulers.
[Nexus S Android Development] cpaixao:
Yes. Just if i want it to. But i dont want.
[Nexus S Android Development] demo23019:
edit

working great
[Nexus S Android Development] tchaari:
Thanks Eugene, I think it is more clear for everyone now. We need just to use NSTOOLS to select the scheduler that we want.

Just a small question please, the included Lulzactive gavernor is v2?
[Nexus S Android Development] demo23019:
thanks for the update but for some reason it laggy

noticeable when scrolling not smooth

using same setting that used with speed 4 on stock 4.0.3

200/1.3 ondemand/deadline
[Nexus S Android Development] bioan:
eugene, when will you include bln for missed calls ?
[Nexus S Android Development] eugene373:
yea Lulzactive governor is v2 :)
[Nexus S Android Development] eugene373:
they work last night when my wife called & missed it..

if not work, idk.
[Nexus S Android Development] benrees21:
Any one else having lagness? Do not wish to update until other people report back that's all. ;)
[Nexus S Android Development] eugene373:
I don't, but I using SIO at the moment..
[Nexus S Android Development] benrees21:
OK I'm gonna try now. Mistake on your download links. You named SIO kernel ISO lol.

Spat out from my Nexus S!
[Nexus S Android Development] dsellers2:
None Here.....USing SmartAss V2, Deadline, OC'd to 1100. Running just as smooth as it did on 4. Now I got to learn how to tinker around with this LuLz governor. Not sure what it is, but it looks very interesting.
[Nexus S Android Development] y3mita:
SIO SCHEDULER gets along with lulzactive2 very well! They're like a matrimony!
[Nexus S Android Development] spitzedanese:
Cleared dalvik cache before installing speedy-5 (on cfq). Got one restart when it optimized applications. But after that it's very smooth.
[Nexus S Android Development] (THE REAL) Neo:
Eugene,if you'll come to Italy,one day,tell me when you are here,i will offer you an original italian Pizza...

Neo on Nexus S with Tapatalk®
[Nexus S Android Development] sean1984:
no lag at all with cfq scheduler and lulzactive gov 1200 100:D
[Nexus S Android Development] benrees21:
Can't download. getting a problem saying redirect loop and to try again later. Sorry Eugene.