yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] ragnarokx:
I believe Eugene recommends wiping (check the first post).

I've been getting great battery life with awesome performance using conservative and cfq, even overclocked to 1.1GHz.

Sent from my Nexus S
[Nexus S Android Development] aLNG:
just flash..use deadline/smartassv2
[Nexus S Android Development] GideonX:
The only one you may need to wipe is cache (if you run into booting problems), dalvik wiping does nothing for the kernel.

I'm using SIO/Intellidemand. Your usage will vary and most likely differ from other users using the same combo they suggest. Try them all, best way to find out.
[Nexus S Android Development] ciwek90:
Thanks! gonna try that one. BTW, at 1st post he not said anything. Just put in CWM and flash.

Thanks again! :D

alright mate! gonna try that! thanks! :D

awesome! try what been recommended 1st, if not good enough then i'm gonna try it all one by one. hehe. Thanks! :D
[Nexus S Android Development] KrisMurdrum:
What he said ;)

But I've been using sio/Lulzactive and get pretty hefty performance and battery out of medium- med. heavy use...both doing 100-1100 and 100-800 (both LOC at 105%)
[Nexus S Android Development] ciwek90:
awesome! Thanks! but when i go to governor, i cannot find lulzactive. Only lulzactiveV2. After choose that, lulzactive menu is available to be adjust. Am i correct? If yes, what is good choice? From inc CPU load until Down sample time? or just leave it as default? Thanks again! :D

BTW, sorry for my bad english -.-"
[Nexus S Android Development] stewarta:
When I am coming from an earlier version, I wipe the cache and flash dalvik-cleaner to wipe the Dalvik Cache.

I use LulzactiveV2 with SIO and set Max CPU to 1000 and Min to 200Mhz and then Live OC 10% giving 1100Mhz and 220Mhz respectively. The action is smooth (partly the ROM) and I go for days with just a half hour top-up charge in the car to and from work. Never a reboot. One cannot ask for more. :rolleyes:
[Nexus S Android Development] KrisMurdrum:
On Speedy 7 I just use Eugene's stock settings

Carved into the Void using my ICS powered Magic Rune Stone
[Nexus S Android Development] demo23019:
quick question

i understand this kernel has LCD under volt and I every once and while parts of the screen become unresponsive and putting phone into stand by and turning back on fixes, not really a concern.

Been using speedy7 since it was released and its been perfectly stable.

But two time when in this last week for some weird reason heptic feedback becomes really soft. Rebooting phone fixes

its really random to isolate.

never had this on other speedy kernels.

Anyone else experience this? not sure if its kernel/lcd under volt related

or phone is on the fritz also im using stock voltages for cpu
[Nexus S Android Development] GideonX:
+1

Haptic feedback got turned way down out of the blue last night. A reboot fixed it, first time it did that for me.
[Nexus S Android Development] demo23019:
alright good at least not me

probably nothing to be concerned about

wonder if it has to do with the screen being under volt juts weird it came out of nowhere been using this kernel for a while now and just recently started
[Nexus S Android Development] Serris:
I think I found a rather weird bug. First time this happened, I turned on the phone, when it came to enter pin,

the screen was going dimm, and it looked like too much saturation and contrast was applied, and every second it went more dimmer/saturated/contrasted.

Besides that static was coming out of speaker, and phone was unresponsive, had to pull battery. Second time occured during playing a game, everything happened as above.

I have no idea what went wrong, could be the lower voltages?

Scheduler: deadline

Govenor: lazy

Min: 100/925mV

Max:1000/1235mV

No LOC
[Nexus S Android Development] aLNG:
does it happen everytime u do that? have u tried different kernel?
[Nexus S Android Development] _yaz_:
i guess, u meant mHz and not mV. if so, i suspect 1235mHz, kicking in typically at startup and when gaming. using different min and max may be also the reason.

my i9023 is very sensitive to oc/uv, some combination kills immediately. first, try to vary gov/sch and check oc/uv step by step.
[Nexus S Android Development] sk3201:
Where can I get speedy 6?
[Nexus S Android Development] jabbeboy:
Hi, just installed this on my phone, but then im in NStools i cant se the Deep idle alternative. Why?

And one question more, whats DIDLE? Deep idle
[Nexus S Android Development] renna1992:
cause the deep idle version used here is different implemented than the one ezekeel uses.

you can read more about deep idle heere: http://xdaforums.com/showthread.php?t=1297535
[Nexus S Android Development] tchaari:
Deep idle is an intermediate CPU state between idle and deep sleep. It is supposed to save battery. There are different implementations for deep idle. Eugene has his own implementation and it doesn't show in NSTools. It is hard coded and enbaled by default.
[Nexus S Android Development] Serris:
No it happens at random times, thats why its more confusing.

Havent tried different kernel yet, love speedy too much :D

No I ment

FreqMin: 100mhz, Voltage: 925mV;

FreqMax: 1000mhz, Voltage: 1235mV,

its a bit UnderVolted, I will try to reproduce the bug with different settings, maybe try different kernel.
[Nexus S Android Development] KrisMurdrum:
This just reaffirms my love affair with Speedy 7...

My settings are:

Loc @ 105%

105 - 1050 mhz (effective)

Sio - lulzactiveV2 (kept Eugene's settings)

UV = -25 on all

------ >_<

Plugged my phone on the charger before staying this post but didn't realize it wasn't plugged into the wall... Damned thing powered off a split second before I pressed submit... Had to start over LOL

Carved into the Void using my ICS powered Magic Rune Stone

---------------------------------------

I love how clearly you can see when I slept on there...

And there was lots of browsing (opera mobile + XDA), a ton of socializing (Facebook, twitter and G+) , twenty Words w/friends; twenty each Pandora and google music... Thats as much as I can remember

Carved into the Void using my ICS powered Magic Rune Stone
[Nexus S Android Development] aLNG:
still a lot u can improve :)
[Nexus S Android Development] jabbeboy:
Okeej. But dosnt this kernel have deep idle or any powersaving thing going on in it??
[Nexus S Android Development] aLNG:
yea..

+hard coded deep idle

+lcd voltage drop
[Nexus S Android Development] jabbeboy:
Ohh i see, so the deep idle is hardcoded in the kernel already, so its not changable or anything.. Okey, sounds fair enought:)

Thanks for the answerss..:) Cheers
[Nexus S Android Development] KrisMurdrum:
So... What improvements would you recommend? ;þ

Carved into the Void using my ICS powered Magic Rune Stone
[Nexus S Android Development] Roscopcoletrain:
Very nice kernel!

Sent from my Nexus S
[Nexus S Android Development] cpaixao:
Man, Who said?
[Nexus S Android Development] cool_yking:
battery

what are the best settings for lulzactive v2 to get best battery backup..

as my wifi on phone is always on..

thanks in advance
[Nexus S Android Development] lukappaseidue:
these are mine:

gov: lulzactiveV2

freq 100min 1000max

Inc. CPU load 75%

Pump up step ( 1 step)

Pump down Step (2 step)

Screen off (6@400Mhz)

Up sample time (30000)

Down sample time (40000)

Scheduler CFQ

Battery time: 2 day 15 H - 1 hour of calls; 30 sms, surfing, wifi, 3g always on, :)
[Nexus S Android Development] cool_yking:
thankss

trying these settings

and any way to keep free memory available

mine always less den 100
[Nexus S Android Development] GideonX:
Google what dalvik cache does. You'll see why wiping it really has no affect on the kernel.
[Nexus S Android Development] spupuz:
are these settings safe?
[Nexus S Android Development] b1337:
Your phone will explode
[Nexus S Android Development] aLNG:
lol

boOmM
[Nexus S Android Development] cool_yking:
wel its runing ok .... but u guys scaring me
[Nexus S Android Development] KrisMurdrum:
I lost my uv notes... Could anyone provide a list of stock voltages both int and arm?

Carved into the Void using my ICS powered Magic Rune Stone
[Nexus S Android Development] aLNG:
https://github.com/eugene373/Nexus_S_ICS/blob/master/arch/arm/mach-s5pv210/mach-herring.c#L432

only at 1000MHz, the arm voltage is 1250
[Nexus S Android Development] cpaixao:
i dont think i will google it because i learned it at school for 4-5 years. And i advise everyone to wipe any branches kernel could have, including the DC ones. DX files... aff. That old history...
[Nexus S Android Development] GideonX:
Nice, I've always wanted to ask this question to someone who's studied this stuff for years in a school.

Since dalvik cache is there for DalvikVM to build dependencies for your apks and framework, how does wiping it have anything to do with flashing a kernel?

I'm 100% behind wiping Dalvik when moving from ROM to ROM, that's silly not too because of your obvious file changes. But from kernel to kernel? Please elaborate if you can, thx.
[Nexus S Android Development] nadiros:
Back once again to Speedy-6 . . .

I hate to say it but 7 is the first one that just doesn't feel right. Screen I swear

is not as responsive, and it's gotta be the UV eh? At least after raising the bottom to 200mhz I could unlock my phone. Still I like 6 and think it's more stable so don't mind at all ;)

These are definitely the best kernels I've used, and is suga with Team Kang M3
[Nexus S Android Development] sk3201:
7 wasnt snappy for me...decided to use 5 after fresh from flash (do not have 6 on my SD card). Phone is fast as hell. Anyway, do not need hundreds of governors, but can anyone tell me which speedy kernels have LCD UV?
[Nexus S Android Development] :
I believe it was added with version 6

For kernel benchmarks and more, see here: http://goo.gl/mpeHI
[Nexus S Android Development] stewarta:
@eugene373: I have a dumbass question: If I am using Speedy 7 (and I am) why does the report I get indicate Streamline #6?

It is off-topic but I am faithful to your kernel having given GLaDOS the flick some time ago (with apologies to ezekeel and his fine work).
[Nexus S Android Development] baolongn:
Any problems running at -25 mv?
[Nexus S Android Development] cpaixao:
Recompiling is the point. The phone learns how to handle every task for the system and apps, and this knowledge, how fast it was done, in what instance and time it was done, and how priority it should be, all that stuff is written on DC for future use. I am not talking about the app path, size in memory or something else - that is the cache job, not DC.

IF (and just IF) you flash a new kernel that uses a new governor or scheduler , and have a new clock, new voltage settings , over a old pre Dalvik cache kernel, you're about to say that man: "hey guy, i know you're used to drive my Volkswagen, but dont worry: take this FERRARI and go on...you already know where you have to go..."

Yes, the kernel already knows what it have to do, since its DCached, but the way it will do it now is TOTALLY different. You might ask now: "And why should i care about that?" Its clear like crystal water: If you care with your battery life you should really care, because when you're about to do something over/bellow power/time/priority it really needs at THIS TIME, and it may cause power wasting, in other word, you'll have you battery drained and soon, you'll come here bring stuff like thak "Hey, why the he** 'android os' task is taking over 30% of my battery usage?" Now, you know the answer: Just because every single time you ask for system to do in somewhere to you, you force it to go from a to c, then f or d... soooooo it comes the the point b, where you wanted.

Apart from that, i am investigating a eminent relation between DC and UV settings over "blackout" issue. But, for now, i cannot prove it yet.
[Nexus S Android Development] KrisMurdrum:
No problems at all buddy... Not even with my current set up.

LulzactiveV2 -sio

-lulz settings:

Live OC 105%

- 105 - 840 MHz effective

UV:

-arm

-- 800 = 1125 mV

-- 400 = 975 mV

-- 200 = 850 mV

-- 100 = 825 mV

-int

-- 800 = 1025 mV

-- 400 = 1000 mV

-- 200 = 950 mV

-- 100 = 925 mV

Carved into the Void using my ICS powered Magic Rune Stone
[Nexus S Android Development] torchie:
NS4G user here. Stock 4.0.4. Still breaks my Camera. It opens now, but stuttering, non-responding, and failed picture takings.
[Nexus S Android Development] cpaixao:
This kernel is not ready for 4.0.4 yet.
[Nexus S Android Development] baolongn:
Works great on my ns 4.0.4
[Nexus S Android Development] cpaixao:
This kernel isnt ready for 4.04 yet.
[Nexus S Android Development] heX79:
I can confirm that its working great on the 4.0.4 NS4G IMM26 port for the NS.

Edit: Speedy 6 that is....
[Nexus S Android Development] baolongn:
Its going pretty well though. I wouldnt say it doesn't work.
[Nexus S Android Development] aLNG:
Eugene is busy with sg2, hope he still give an update to his speedy here. Want to share some screenshots here for light usage:
[Nexus S Android Development] y3mita:
Amazing!! Setup?
[Nexus S Android Development] spupuz:
this is the most stable kernel i tryed
[Nexus S Android Development] macacao:
After installing speedy-7 kernel over latest peter alfonso's nightly i got this weird progress bar when i turn my phone on.

http://www.youtube.com/watch?v=vqOC-WVWtJQ

Does anyone knows why?
[Nexus S Android Development] :
It's just an animation eugene373 added. Nothing serious.
[Nexus S Android Development] GerManiac:
Yes, cause Eugene wants it that way cause he likes it
[Nexus S Android Development] alienmind:
Hi @eugene

Interested in dm-cache feature. What is the expected gain in I/O with this feature?

Is there anything needed to be done on our side to enable? (script to enable via sysfs interface or something... module to be loaded... anything?)

Thanks!
[Nexus S Android Development] MaXmeOliver:
Will USB OTG be added?
[Nexus S Android Development] trystan2k:
I really hope so ! :D
[Nexus S Android Development] LorD ClockaN:
I just noticed in his kernel that he uses brazilianwax governor :)

didn't know that my governor mod will become so popular LOL
[Nexus S Android Development] italia0101:
Kernel settings ? And what Rom ?
[Nexus S Android Development] tchaari:
aLNG is calling a 6 hours screen on time in one day "light usage" :D
[Nexus S Android Development] thegtfusion:
Wtfffff which ROM????
[Nexus S Android Development] aLNG:
For me if we use the phone lot for browsing and play light games,that is light usage.but if u play a lot of heavy game like shine runner,reckless gateway,..that heavy use plus if 3g always on and bla bla bla
[Nexus S Android Development] thegtfusion:
Which rom did you use
[Nexus S Android Development] aLNG:
U are xdaing using ur phone :) that why u can't see my sig. I'm always using bugless beast. Governor smartassv2 to maintain smoothness and freq 200-1Ghz
[Nexus S Android Development] keb00:
I have the same problem with NexusBeam rom. :(

Bruno M. Através do Nexus S @ ICS NexusBeam & ICUP
[Nexus S Android Development] aLNG:
what problem? :eek:
[Nexus S Android Development] jedijos:
Not a problem exactly, just the progress bar Eugene added while booting...
[Nexus S Android Development] eugene373:
Currently working on SGS2, but I'll be making an update soon to the NS Kernel

~Eugene
[Nexus S Android Development] _yaz_:
th best news today :D
[Nexus S Android Development] aLNG:
Good news..

Just to test how battery life without gaming.we can see balance use of dvfs

I will try next to tweak smartass2 for more battery life without effecting the smoothness.will report back
[Nexus S Android Development] heX79:
Not sure if radio dumps are related to the kernel or not. But I suspect the kernel plays a roll. They occurred on both 4.0.3 (AndroidME 1.2.3) and 4.0.4 (IMM26 my current) while using speedy 6. Since flashing speedy 7 I have yet to recieve one, so that's good news.

They aren't a big deal, really, as most happen when the phone's sleeping. But I find it annoying after ending a call (or mid call) when the radio drops and takes about a minute to reconnect to the network. The Radio I'm using is the one out of the box I9020AUCKF1, never touched.

FYI, love these Kernels and patiently await your next release!
[Nexus S Android Development] aLNG:
http://xdaforums.com/showthread.php?t=1488100
[Nexus S Android Development] thekenderman:
Bug less beast and icup have given me amazing results. Idled on wifi fi about 11hrs received a couple emails and texts....listened to a 2 hr podcast and only broke 70% at 14.5 hrs.

19020a, Smartassv2 @ 200 - 1000 bln on, and I am impressed.
[Nexus S Android Development] lolokman:
aLNG

Are you using 9023 or 9020?
[Nexus S Android Development] aLNG:
9023. Why?
[Nexus S Android Development] _yaz_:
i use the same rom/kernel combo on the same phone like u. but why do u restrict 100mHz ? (i guess u don't have a cyber model of nexus s w/proc running on GHz ;) ) one of my main activities is listening music w/screen-off when 100mHz is the standard freq for the cpu. i think, i spare a lot w/it.
[Nexus S Android Development] aLNG:
i tried/tested with 100MHz but because of my usage i got better battery life with 200MHz.it really depends on what are u doing with ur phone.
[Nexus S Android Development] Serious_Beans:
I don't think it matters much since 100mhz and 200mhz have the same voltage.
[Nexus S Android Development] _yaz_:
it was quite a long time ago, but iirc from school, power is proportional to voltage AND frequency, isn't it.
[Nexus S Android Development] aLNG:
quadratically to voltage and proportional with freq
[Nexus S Android Development] :
Check post #212

http://xdaforums.com/showthread.php?t=1478406&page=22

Then go watch my latest video, there is a bit on undervolting near the end!
[Nexus S Android Development] heinst:
Speedy-4 or Speedy-5

does anyone have Speedy 4 or 5 they can attach for me please? or a download link? I cant seem to find one
[Nexus S Android Development] y3mita:
now if you read these thread, you'd know eugene do not like people linking to his kernels.
[Nexus S Android Development] heinst:
What do you mean? Its still his kernel and people are still using it and hes still getting credit. That doesnt make sense.
[Nexus S Android Development] heX79:
Spoke too soon, think I'm going to return to stock GB and see if I get drops... I'm outside atm and just had two with a signal of -54dBm which I find strange. Can't find much explanation on this forum for what causes this, and my radio is stock...
[Nexus S Android Development] _yaz_:
yep. for simple-minded like me, it is the rule of thumb ;)
[Nexus S Android Development] WarByte:
Agreed on that, yet I respect the OP's desires. If you search through this thread I found speedy 6 linked.

Googling I found Speedy 5. Now I ended up with a 3.1.9 Speedy 6 and a 3.1.10 also speedy 6. I guess this is why the OP doesn't like mirrors but if I could request something it'd be to keep a list of the official previous releases, some of them just work better than others for some people :)
[Nexus S Android Development] syntax_gosong:
Hi, I'm a newbie on kernel stuffs...

What are the advantages speedy 5 or 6 rather than speedy 7 ?

Can somebody give me some examples and explain to me please?
[Nexus S Android Development] aLNG:
speedy-7:

~~~ Fixed issues with MIUI & Other Rom's

~~~ GPS 100% Fixed for NS4G Users

~~~ Tweaked Conservative Gov.

~~~ Tweaked lulzactive Gov.

~~~ Added brazilianwax Gov.

~~~ Added intellidemand Gov.

~~~ Added lionheart Gov.

~~~ Added ondemandx Gov.

~~~ Added savagedzen Gov.

~~~ Added Wheatley Gov.

speedy-6:

~~ Updated to 3.1.10

~~ USB Tethering Fixed

~~ CFQ I/O By Default now

~~ misc Fixes

~~ Camera Fixed for NS4G Users

~~ VR I/O Added

~~ LCD Voltage Drop

~~ Lagfree Governor

~~ Interactivex Governor
[Nexus S Android Development] syntax_gosong:
Thanks aLNG for your explaination... :)

As far as I read from the points above, speedy 7 has more cpu government and

some fixes. That means, more better choices and increasing performance.

And any features that contain in speedy 6 shall also include in speedy 7.

I'm just curious why do people still using speedy 5 or 6 ?

Isn't that mean, go back to deals with some limitations (govs), buggy features (gps), and so on.

Is speedy 7 not stable enough comparing to its predecessors?
[Nexus S Android Development] Wario86:
i have a problem with bln.... when i unlock the phone the light of the soft key go off and the soft key work but without light... what can i do?

thank you
[Nexus S Android Development] y3mita:
Nothing against you my friend... but eugene has stated he does not like people linking/mirroring his kernels. That's all.
[Nexus S Android Development] _yaz_:
i guess it's rather blD. check ur setup for light-off, by default it's quite quick. what rom and device, anyway ?
[Nexus S Android Development] WarByte:
You are correct and I'm gonna take the time to explain a little at least from a very personal experience.

When I change to a custom kernel either to try it or to use it I overclock as much as I can and check with default voltages how stable it behaves. As I don't care about battery life (reasonable values that is) I go after the minmax governor so speedy 5, 6, or 7 don't make a difference against the change logs. Speedy 7 mentions MIUI roms and 4G users so Speedy 6 or 7 are the same for me, and in reality that was the case, very stable.

From speedy 5 to 6, VR was added, which does not affect me as I use noop, more governors, that does not affect me, and fixes for 4G users which I can ignore. The base was changed to 3.1.10 and I didn't experienced too much of a difference. There was an LCD voltage drop which some users reported as a lack of responsiveness in the screen, I can't confirm as it was not my case but if it happened to you I guess you could blame it on that change.

Speedy 5 does seem to include very critical changes that didnt affect me before but that I rather not mess with using previous releases.

Now I can tell you, Speedy 3 was a very high performer for me. I left it behind based on the data corruption mentioned in the change logs, Speedy 5 was excelent, just a tad behind Speedy 3. Now with Speedy 6 and 7 I did experience a very minor lag in my launcher, not as much as to make me go back, but I know it is there. Overclocking all the way with Speedy 3 or 5 was flawless, Speedy 6 and 7 cause a reboot once in a while (when loading Shadowgun saves) but overall all releases have always been very stable for me. Sorry for the lengthy text, just thought I'd share my reasons with you.
[Nexus S Android Development] cpaixao:
I agree. Speed-3 is the most stable so far, maybe due the linux kernel version. But beside that, I also see Speed-7 more responsive.
[Nexus S Android Development] :
What governor are you using?

I kept all my kernel benchmarks from Speedy4 onwards, speedy7 is the highest scoring so far, check the data: https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdFZ6VDRQV0cxRXFVT2dKYm94bWJyQ0E
[Nexus S Android Development] CrackDaddy:
Deep Idle ( DIDLE )

Hi eugene373, can yourself or somebody please explain in more detail: (Deep Idle ( DIDLE ) Not to be confused with Ezekeel Deep_Idle Mod) please!? Bit confused as to why it doesn't show up in NSTools as an option to control :confused:

Thanks in advance.

PS: excellent kernel by the way, thanks for all your hard work!
[Nexus S Android Development] :
Eugene is busy with the Galaxy Nexus at the moment, so to save you waiting an indefinite time for an answer, it might be worth your while checking out the work done by Harbb (summarised in the second post of my battery thread: http://xdaforums.com/showpost.php?p=22126806&postcount=2) Eugene's DIDLE has no effect on battery drain. It isn't controllable through NSTools either.