yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] formula84:
Question do both versions boot with the same colors and the second one is just 65 FPS? I like the more blue color set at boot but i heard 65 FPS can cause issues with display reliability...
[Nexus S Android Development] stojshic:
I just can't believe that this kernel has 4 stars!? I mean, there so many kernels and roms out there, of which many deserve 2 stars, but still they have 5 stars, jet this kernel has 4 stars, even tho it's surely one of few good kernels...
[Nexus S Android Development] ezio84:
Installed just now :D Loving it!

A little textual bug in the updater-script:

ui_print("* AIR Kernel v3.0 ICS Kernel *");
ui_print("* Made by r_data *");
ui_print("* 02-10-2012 *");
ui_print("* *");
ui_print("******************************");

There's v3.0 instead of 3.1 :p
[Nexus S Android Development] screeny2:
Ooooh no. Installed via CWM on Kangy and all i get is the Google-screen followed by a black screen followed by the Google-screen and so on.

Looping...:'(

Update: Looks like the zip without boot animation works fine. Strange...
[Nexus S Android Development] darth7:
I'm on Kangy too, no problem at all. Running great.

Enviado desde mi Ice Cream Nexus Sandwich usando Tapatalk
[Nexus S Android Development] gotjazz:
Hrm for some reason 3.1 doesn't perform quite as well as the test kernel did. I assume everything beside deep idle was still based on the last release in the test kernel?
[Nexus S Android Development] :
I've updated to v3.1 in the kernel benchmark sheet. Looks like the reason for the slight slowdown is due to I/O.
[Nexus S Android Development] droidance:
How is Lionheart governor?

And what is the best governor for v3.1?

Thanks! :D
[Nexus S Android Development] :
What are you looking for, performance or battery life?

kernels ; battery ; ROM ; gov/sched
[Nexus S Android Development] droidance:
I'm looking for more balance between perf and battery (though I would prefer more battery life if I had to choose). I did a little search and I suppose Lionheart is geared towards performance?
[Nexus S Android Development] gotjazz:
Yeah I noticed that too. Still in love with this kernel though. Best first impression yet :-)
[Nexus S Android Development] xzilem:
I'll stay with test kernel until v3.1 achieve the same benchmark as test kernel then
[Nexus S Android Development] y3mita:
Well, I can't compare with test version since I never ran it... but on 3.1 it's my first time I get a reboot! :(
[Nexus S Android Development] dictionary:
It looks like you may have your reasons for not making this kernel with blue colors and no 65fps. Would love a kernel with just blue. Is there any way I can modify it on my end to eliminate the 65fps? Thanks!
[Nexus S Android Development] flibblesan:
Are you overclocking? Are you undervolting? Have you changed any of the kernel settings? Which governor are you using? Did the phone reboot whilst you were doing something or did it reboot whilst it was idle?
[Nexus S Android Development] y3mita:
Using smartassv2 cfq default everything! It was browsing and it rebooted
[Nexus S Android Development] ferdi7103:
Just moving from SG kernel to Air Kernel 3.1..very nice and smooth

Just reporting some problem when hearing music, with screen off, the sound is glitch and sometimes stop, set on Governor :SmartassV2 & Active scheduler : noop

In SG kernel, with same setting , the music running smooth

Thanks in advance
[Nexus S Android Development] gotjazz:
Don't wait. It's nothing that anyone would call a real difference
[Nexus S Android Development] jodtalingchan:
Use voodoo version. Its not that bad ...
[Nexus S Android Development] y3mita:
Voodoo is fine no flicker bug here
[Nexus S Android Development] :
I recommend smartassV2.

kernels ; battery ; ROM ; gov/sched
[Nexus S Android Development] ezio84:
I had a lag problem just now, reactivating the phone from airplane mode:

http://xdaforums.com/showpost.php?p=22818701&postcount=35

I will try Conservative + cfq

EDIT: it seems there's a problem with nstools, sometimes the scheduler change without my action...
[Nexus S Android Development] gotjazz:
If I may be so bold as to say that smartassv2/noop/deepidle/min400 is a great combination no matter whether you're looking for performance or battery-life. Great screen of battery conservation and great screen-on performance.
[Nexus S Android Development] spupuz:
what do you mean with min400??
[Nexus S Android Development] ezio84:
Min cpu frequency, 400 is probably the best value to use when deep idle is enabled and top=off status is available ;)

EDIT: remember, only in this situation (deep idle, screen off and cpu working)
[Nexus S Android Development] dictionary:
Don't have full control over it, and like the blue colors. Meh
[Nexus S Android Development] spupuz:
i can't find the top=off and why using 400 as min cpu it is not better to save energy using 100 as min cpu?
[Nexus S Android Development] adam900710:
Thanks for your kernel。

Would you please add NLS-UTF8 support for your kernel？

It would be great help for ones using cifs with non-ascii characters like Japanese and Chinese。
[Nexus S Android Development] ezio84:
With Conservative governor and cfq scheduler the last version is working like a charm :D

Changing to smartass V2 in Nstools is probably buggy for now.

Only some modded roms with patched bluetooth framework can use the complete deep idle state (top=off), e.g. the stock rom can't do it, and google talk app has a bug that prevents phone going in deep idle state: http://xdaforums.com/showthread.php?t=1377029

Read this article for more information: http://xdaforums.com/showthread.php?t=1297535

You can verify in

Nstools-->cpu-->idle stats

if your rom is deep idle compatible (if not, only top=on cicle will be in the counter).

There are some benchs that confirm 400mhz as the best value for cpu min frequency with deep idle (= screen off and cpu working): http://xdaforums.com/showthread.php?t=1478406

EDIT: remember, only in this situation (deep idle, screen off and cpu working).

PS: Ciao! :)
[Nexus S Android Development] ljordan2:
Found a golden setting for this kernel.

Conservative, 880/220(liveoc:110%)

And with this setting.

This is a setting used in Franco's kernel. So it is pretty snappy:)

Sent from my Nexus S from Tapatalk
[Nexus S Android Development] gotjazz:
Because if your phone wakes up to do something, it finishes sooner and goes back to deep idle or even deep sleep earlier.
[Nexus S Android Development] :
Setting 400 as your minimum will not save power. It can, but only in one situation, if you use ondemand as your governor, and use deep idle while the screen is off, i.e. listen to music. However, it saves so little it isn't worth the effort.

Set 100 min and use ondemand if you want to save power.

kernels ; battery ; ROM ; gov/sched
[Nexus S Android Development] spupuz:
what about smartassv2? and which governor?
[Nexus S Android Development] :
Do you mean scheduler? Use noop. Same for smartassV2. smartassV2 is the best choice for power saving and high performance. Use min 100 even if you use deep idle

kernels ; battery ; ROM ; gov/sched
[Nexus S Android Development] spupuz:
thanks :) a lot :D
[Nexus S Android Development] StyxD:
The weird thing is, I get higher Quadrant scores with conservative/deadline than with smartassV2/noop (both at 400/1000) on nuhetri v2.3.0.

And battery drain stays at the same level (2-2,5% checked with BatteryDrainAnalyzer).
[Nexus S Android Development] joebarkho:
I read a battery thread that shows 200min/800max at lazy & didle gives the best battery life.

Doing that will prevent the CPU to jump to too many states. 100-1000 takes several steps to go up and down vs 200-800.
[Nexus S Android Development] :
It's because conservative keeps the frequency at max too much.

Ondemand 100 min is best for battery. If you are using deep idle, it doesn't make any difference what your governor is when your screen is off. I'm not basing this on an impression, it's been thoroughly tested here: http://xdaforums.com/showthread.php?t=1507204

kernels ; battery ; ROM ; gov/sched
[Nexus S Android Development] y3mita:
Guys check CPU tuner in market for better battery life yet!
[Nexus S Android Development] gotjazz:
Why not with smartassv2?

Ah! doesn't it go that low anyway as long as it's active??

but then again it'd be with most govs as long as you use deep idle. I mean if the cpu isn't active it isn't active. And it - as you say in yor battery thread "With the screen off, and the processor is active, the best power saving state is 400 Mhz with Deep Idle (and remember there is no measurable benefit to undervolting." then why let it go below that? And with the screen on you'll probably be actually using the phone so moste governors with sufferable performance will be above 400 anyway.

Or am I missing something here?
[Nexus S Android Development] :
I need to remove that point about 400MHz from my battery thread. After further calculations in this thread: http://xdaforums.com/showthread.php?p=22745572

... it turns out when deep idle is in use, it makes very little difference what governor is in use, or what frequency for that matter. The power saved by being in this ideal 400MHz zone is not enough to merit opening the app to raise the lower limit.
[Nexus S Android Development] gotjazz:
Haha fair enough - never used deep idle with 100min. That used to be unstable at some point, right?
[Nexus S Android Development] :
Yeah, I think I heard that. But in my testing it's been fine.
[Nexus S Android Development] lvnatic:
Still no lulzactive v2? :(
[Nexus S Android Development] dictionary:
As stated numerous times, the lulzactive that is included is v2
[Nexus S Android Development] darth7:
I'm back to test kernel, I have better performance and battery life.

Enviado desde mi Ice Cream Nexus Sandwich usando Tapatalk
[Nexus S Android Development] jodtalingchan:
So do I ...
[Nexus S Android Development] unattached:
hey guys,

I was running a rooted stock 4.0.3. rom and then flashed this kernel. everything is running fine and smooth except I get a terrible battery drain now.

Can I easily revert to the stock kernel or can I try another kernel? I already wiped dalvik and cache, but I didn't try fix permissions..

any help?
[Nexus S Android Development] ljordan2:
Of course. All you need to do is wipe dalvik cache and flash the kernel you need to use. I switch kernels almost daily basis:)

Sent from my Nexus S from Tapatalk
[Nexus S Android Development] screeny2:
Had a complete loss of signal today. Reboot necessary - never had this before on Kangy, so this should be kernel-related.

SmartassV2

Noop

100/1000

DeepIdle enabled

No OC/LiveOC/UV
[Nexus S Android Development] ljordan2:
I am really not sure what is the problem but I think it's deep idle problem since I've seen few people with the same problem. So turn the deep idle off.

Sent from my Nexus S from Tapatalk
[Nexus S Android Development] spupuz:
in your opinion what is the best governor scheduler for battery long life?
[Nexus S Android Development] r_data:
Released v3.2

I released air kernel v3.2 :)

I think v3.2 is more stable than v3.1 !
[Nexus S Android Development] glennkaonang:
As it is comprehensively tested in bedalus' thread, lazy - deadline is best for battery life if you're running Air Kernel.

You could take a look at it here http://goo.gl/ThVzX

Anyway, regarding the update, what's the full change log?

Thanks.

EDIT: nevermind, I'm just late for few secs :D
[Nexus S Android Development] r_data:
I recommend 'Conservative + deadline' or 'Smartassv2 + Sio'.

The source of this information is bedalus's Battery Saving Governor Benchmarks thread :)

(http://xdaforums.com/showthread.php?t=1507204)
[Nexus S Android Development] glennkaonang:
Yes, but it seems that conservative mostly uses high frequencies when in medium use.

Could you suggest the best parameter adjustment for conservative?

Thanks.
[Nexus S Android Development] spupuz:
what do you think about juice defender application?
[Nexus S Android Development] glennkaonang:
Some people say better not to use it since it causes a lot of wakeups to our phones.

CMIIW
[Nexus S Android Development] nexus_junkie:
Thanks for the update

smartassV2 / sio ? OK I'll try :)
[Nexus S Android Development] droidance:
Is ONDEMAND 1000/100 noop good setting for battery life?

And what is good setting - sampling rate, up threshold, sampling down factor, and powersave bias?
[Nexus S Android Development] spupuz:
i before sandwich and modedded roms i had it but i'm not sure if it works ok with ics and modded rom / kernel i give it a shot again i have the paid apps (pro version)...
[Nexus S Android Development] :
Ondemand noop is a good combination, i would avoid conservative. For air kernel, best battery life seems to come from lazy.

kernels ; battery ; ROM ; gov/sched
[Nexus S Android Development] y3mita:
These two work fine on my device.
[Nexus S Android Development] y3mita:
Hands down!! What a snappy kernel this last version!! CONSERVATIVE rocks!
[Nexus S Android Development] spupuz:
what about intellidemand in what it change from ondemand?
[Nexus S Android Development] nexus_junkie:
http://xdaforums.com/showthread.php?t=1369817
[Nexus S Android Development] defia:
i googled ksm support which added in v3.2,it said that /sys/kernel/mm/ksm/pages_shared and /sys/kernel/mm/ksm/run should not be zero if ksm really takes effect.

the /sys/kernel/mm/ksm/run is 1,

but the pages_shared is actually zero, so does ksm really takes effect in android?
[Nexus S Android Development] bluelyd:
Excellent Kernel ever!!

Actually I've never stayed on any roms & kernels.

But I love this kernel and keep usin' on it for more than 3 weeks.

Fast, smooth and stable. Very nice color I think.

Please keep on this working for many users of your kernel.:D

Great job!!:)
[Nexus S Android Development] :
Air Kernel 3.2 updated on the sheet: https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdFZ6VDRQV0cxRXFVT2dKYm94bWJyQ0E

I/O score back to normal. Thanks r_data
[Nexus S Android Development] gotjazz:
Had that too - remember the discussion about min frequs? Happened a couple of hours after I lowered mine to 100 - now I'm back on 1000/400 - still smartassv2 and deep idle and it hasn't happened since. Might be a coincidence though.

Come to think of it: I'm back on the test kernel and I'm not quite sure if that happened to me on this one or 3.1 :\

---------- Post added at 06:03 PM ---------- Previous post was at 06:00 PM ----------

could you maybe provice md5 checksums to confirm downloads? Much appreciated :)
[Nexus S Android Development] flibblesan:
I have the same issue. Never had it on any AIR kernel until deep idle was added. It would happen quite often using radio KI1 so I downgraded to KF1 and the issue didn't happen again until this morning. Complete loss of radio and only a power off and power on sorts it out.

I now think it's deep idle causing the issue and not the radio.
[Nexus S Android Development] androidphone2012:
maybe r_data release the alternate version "CPUIdle instead of Deep Idle"

then he must be the crack-kernel-builder :p
[Nexus S Android Development] OCedHrt:
What governor are you using?

Probably not related, but could be:

I'm having a weird problem with smartassv2 on startup - 100% system cpu. If I choose any other governor it will drop back to normal, then I can switch back to smartassv2.

Or I can set another governor (such as ondemand) and it will be normal on startup.

I'm using NSTools on CNA 1.4.
[Nexus S Android Development] flibblesan:
Using conservative
[Nexus S Android Development] OCedHrt:
Seems not related then.

I've had a loss of radio happen once, maybe twice - and not on Air Kernel. Don't remember which exact, but probably ICUP.
[Nexus S Android Development] flibblesan:
I have noticed that the default min CPU freq is 100 on Air kernel. Screeny2 who had the radio loss had min CPU freq set to 100 as well. Could very well be a combination of deep idle enabled and 100 min freq? I read somewhere that it's recommended to use 400 as the min freq when using deep idle.

I'm probably clutching at straws here but it's a problem I'd really like to find the cause and get it sorted.
[Nexus S Android Development] stremax:
Great kernel, I suggest to switch to 200MHz sometimes lower causes reboot, just look at my quadrant, not so much significative but really smooth on daily use
[Nexus S Android Development] ferdi7103:
Thanks for your update.

Hope some error when use NS tools fixed with smartass v2,because always use cpu with 1000 mhz
[Nexus S Android Development] ferdi7103:
Could you give other download link, because dropbox got error in first post..

Thanks and kamsamida...
[Nexus S Android Development] androidphone2012:
This is all I have.
[Nexus S Android Development] y3mita:
http://db.tt/8e1DaRIM

3.2 voodoo no boot animation

MD5: 8eb64a49c89fa46a67d3d17d5bc7cfff
[Nexus S Android Development] ferdi7103:
Thanks mate...
[Nexus S Android Development] gotjazz:
Thanks a lot. Think you could also post the md5 on your end? Been having a wonky connection lately - flashed bad dl already of rgis (couldn't boot)
[Nexus S Android Development] flibblesan:
Definite issue with NSTools and Smartass v2 in this kernel since I set the minimum speed manually to 400 but on a reboot it's reset to 100. NSTools is definitely set to save settings and it remembers everything else I changed.

Also with Smartass v2, noop, 400 min 1000 max and deep idle on I had radio death after the phone was screen off for about an hour. So that's 3 people with the same issue using the same settings.

I'm now testing things with deep idle disabled. Could very well be an incompatability between smartass v2 and the deep idle code.
[Nexus S Android Development] y3mita:
Done, added MD5 hash to my file.

---------- Post added at 03:02 AM ---------- Previous post was at 03:01 AM ----------

Those having issues with NSTOOLs and want to try a great app until app gets fixed by dev... go to market and download CPU tuner.
[Nexus S Android Development] flibblesan:
Most people would be happier if r_data increased the minimum freq from 100 to 400 since so many people have issues at 100.
[Nexus S Android Development] y3mita:
Why?

You can do this yourself, all ICS ROMs now incorporate a tab under settings where you can set your min or max

And there are plenty of tools in the market that allows you to do so.
[Nexus S Android Development] NicholasQ:
Drop box has disabled downloads :(
[Nexus S Android Development] flibblesan:
I understand that but surely if people are having problems with Smartass v2 set to 100 then why not set it to 400? power users can still set it to 100.

Just my 2c
[Nexus S Android Development] glennkaonang:
I'm running 100/1000 lazy - deadline with no problems here.
[Nexus S Android Development] iGoogleNexus:
Lmao!!! This whole time I was like... wtf... I NEVER GOT THE TEXT For Throttling... xD glad this got worked out =]

- Google
[Nexus S Android Development] aLNG:
r_data can u fix smartassv2, so that users can change the tunable parameters via terminal or nstools.
[Nexus S Android Development] benniebeeker:
i see that the bulk of you are running i9023 models... has anyone flashed 3.2 to a i9020t??? curious before i give it a stab....
[Nexus S Android Development] ranasrule:
"This account's public links are generating too much traffic and have been temporarily disabled!"

please provide alternate download link...thx
[Nexus S Android Development] sean1984:
http://xdaforums.com/showpost.php?p=22887357&postcount=511

http://xdaforums.com/showpost.php?p=22887206&postcount=510 :D
[Nexus S Android Development] ranasrule:
thanks a bunch
[Nexus S Android Development] flibblesan:
Works fine on i9020T. No reason why it wouldn't.
[Nexus S Android Development] OCedHrt:
I recently read that only at 100 Mhz do you get downclocked GPU, so you don't want to lose that during idle. Deep idle at 100 mhz was fine for me on other kernels - I think...
[Nexus S Android Development] _yaz_:
here comes the fourth ppl. i had regular radio issues since the air test version. it occurs when i reach an area where the signal strength is very low AND i'm listening music while the phone is in didle. it is the definite condition for a radio death.

i use conservative/cfq, so i think it has nothing to do with the gov/sch but it's didle, definitely.

an other issue since air 3.1; in didle the frequency is not allowed to drop below 200MHz, so i guess the drain is higher than without didle. 100MHz was quite safe before, so I don't understand ... now i'm testing it with didle off
[Nexus S Android Development] screeny2:
I can confirm half of this. Radio death occurs when the signal strength is low and the phone is in Deep Idle.

Had the exact same problem already on Gingerbread with Deep Idle Kernels, so something must be wrong with it. Disabling it now and see if battery life decreases significantly.
[Nexus S Android Development] r_data:
Read Me!

There is controversy about the Cpu Idle backport and Deep Idle.

Also, I do not feel good about Deep Idle.

When listening to music may be good, but usually there are times when the effect is not good.

So, I try to start voting for them.

Please vote them! :)
[Nexus S Android Development] :
If deep idle is causing problems for some people, they can disable it. There's no point including cpu idle as it doesn't do anything!

kernels ; battery ; ROM ; gov/sched
[Nexus S Android Development] gotjazz:
I was sceptical for a long time too but I really like it lately - has everyone with radio deaths tried raising the min freq to 400 and kept in mind that nstoools is a bit buggy when it comes to smartassv2 should that be in use?
[Nexus S Android Development] nexusphone:
r_data, bedalus right!!!!

Sent from my Nexus S
[Nexus S Android Development] r_data:
I checked smartassV2 problem.

I'll modify it as soon as possible :)
[Nexus S Android Development] r_data:
You're right :)

Deep Idle will be retained!

Thank you!
[Nexus S Android Development] ezio84:
Voted for cpu idle, i'm not using deep idle.

But we can disable it in nstools, so instead of creating a new release without it (deep idle can be usefull for some users) you could only write a big bold warning in the first post of the thread, something like this: "Please disable deep idle mode with Nstools to increase radio stability if you are using 100mhz as min cpu frequency and you are not usally listening to music when display is off".

Or place WWE logo with "don't try this at home" :D:D

BTW: 3.2 is amazing, stable and fast with ics 403 stock, conservative+noop (waiting your fix for smartassV2+noop) ;)

Thank you!!!
[Nexus S Android Development] aLNG:
nice..definitely will try it
[Nexus S Android Development] r_data:
Read Me !!!!!!!!!!!!

SmartassV2 problem(LiveOC, minclock ...) was due to NSTOOLS v1.15(the latest version).

Therefore, please use the NSTOOLS v1.14!

arifhn's thread(v1.14 Link) : http://xdaforums.com/showpost.php?p=19070492&postcount=1
[Nexus S Android Development] android_nexus:
that's right. thank you, sir :)
[Nexus S Android Development] Imppy:
Hey the download link is down due to high traffic!
[Nexus S Android Development] r_data:
I have uploaded mediafire.

Here it is! :)
[Nexus S Android Development] Imppy:
Thanks man...do you have any idea why deep idle doesn't work for me? I installed codename from...with the idle patch and still doesn't work...I tried full wipe as well...by the way tried this on deep idle capable kernal
[Nexus S Android Development] nexus_junkie:
What rom? that rom with bluetooth sleep patch?
[Nexus S Android Development] ezio84:
I can confirm, with Nstools 1.14 i can set smartassV2+noop and it doesn't change to other governor or scheduler after reboot :o
[Nexus S Android Development] Imppy:
Codename rom

And yes the sleep idle patch

Both my off and on is 0