yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] harekris:
hi

sskharel@gmail.com
[Nexus S Android Development] DaX05:
PM me the link broham.

Beamed from my Nexus S
[Nexus S Android Development] SA-07:
On site:

http://matr1xkernels.com/matr1x-kernels/matr1x-kernel-for-nexus-s-and-nexus-s-4g-ics/
[Nexus S Android Development] eedou:
PMed, looking for great staff~~
[Nexus S Android Development] mobile_pc:
Matr1x Homepage

Thanks for the update :)

v16.5

- Put deep idle back in,

- added some performance tweaks,

- added any ezekeel bug fixes,

- updated kernel to 3.0.20,

- and added the Lionheart governor.
[Nexus S Android Development] moriz1:
Installed v16.5. I will report back about its battery life in a few days, since v16 was pretty spectacular on that front. Prior to flashing, I was sitting at 37% after 24 hours, with moderate overall usage. Let's see what v16.5 can do.
[Nexus S Android Development] SA-07:
Cool, ty
[Nexus S Android Development] SA-07:
Ok links are now on site!

http://matr1xkernels.com/matr1x-kernels/matr1x-kernel-for-nexus-s-and-nexus-s-4g-ics/
[Nexus S Android Development] DaX05:
Testing out Lionheart with deadline. :) Thanks for putting back deep idle.

Beamed from my Nexus S
[Nexus S Android Development] technogravy:
Downloading 16.5 any information on Lionheart? Is it performance or battery oriented.?

Mk....any reason for adding deep idle back? Is CPU idle gone now?

Loving 16 so far..
[Nexus S Android Development] moriz1:
Lionheart appears to be a tweaked conservative governor with better performance, but worse battery life. Seems like a waste of time to me.
[Nexus S Android Development] qtwrk:
v16.5 Put deep idle back in, added some performance tweaks, added any ezekeel bug fixes, updated kernel to 3.0.20, and added the Lionheart governor.

yes! yes !, deep idle back in !!!

a million, billion, quintillion, sextillion, septillion, octillion, nonillion, decillion, undecillion, duodecillion, tredecillion times of THANK You !!!!!!!!!!
[Nexus S Android Development] raulillo88:
I think deep idle wastes more battery than saves

Enviado desde mi Nexus S usando Tapatalk
[Nexus S Android Development] DarkhShadow:
OK so at night I'm having HUGE battery drain 40-60% and I can't work out what, here's some screenshots of betterbatterystats and ics battery

Sent from my ice cream powered Nexus S
[Nexus S Android Development] qtwrk:
pensaba en contrato...

i usually lost 2% in night when i sleep

and i loose aprox. 5% - 7% these day with version 16.0 :)

---------- Post added at 11:28 AM ---------- Previous post was at 11:21 AM ----------

guess what, i woke up this morning and see XDA via xda app

i saw matr1x updated to 16.5 and then see detail , i saw "put deep idle back in ":eek:

first of all , i thought i was dazed that i wasn't feel woke up or i was just dreaming ...:confused:

and then i washed my face with cold water in this 7 °C temperature to makes me feel wake up , i just finally see it is real !:)

i was so excited about it:D
[Nexus S Android Development] clocker66:
Dude, deep idle does not affect in any way your battery performance while the device is in deep sleep state
[Nexus S Android Development] :
Hello mathkid95, no response to this? I was just wondering what the point of having a BFS version is? If it is supposed to allocate more processor time to the foreground process, it should score better in benchmarks. On a test I did with GlaDOS BFS did worse than GlaDOS CFS.

If I test yours and it comes out worse, I think you should pull the BFS version, because a lot of users will be tempted because of its novelty, then be disappointed.

Also, thought you might be interested in the results produced by Harbb in his excellent series of Deep Idle tests, including some CPU Idle Backport tests, which show CPU Idle is not saving power.

Check out his spreadsheet: https://docs.google.com/spreadsheet/ccc?key=0AtAoMeg4HjUqdFRfU2ZrRDhpNEx6bEgyRWhWN0x0X1E

All credit to Harbb, he's a one man army!

EDIT: I see v16.5 has deep idle back in, so that's good. I'm really starting to believe I cocked up the test when I produced my deep idle battery drain benchmarks. I suspect I didn't even check to see if the deep idle stats were accumulating.
[Nexus S Android Development] 93ae8074:
I think that you mean "pensaba en alto". :D
[Nexus S Android Development] nexusphone:
Wow, cool!
[Nexus S Android Development] :
This page is well worth a read

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

(My battery drain benchmark thread)
[Nexus S Android Development] nexus_junkie:
Thanks for your work :)
[Nexus S Android Development] slonn:
How the heck do you download version 16.5? Have to go through 4 pages to get to a link that says Download Here - except the link isn't active.

Edit: had to reload the page a few times before an actual download link appeared.

http://downloadandroidrom.com/file/matr1x/NexusSandNexusS4G/16.5/Matr1x-cfs_v16.5.zip
[Nexus S Android Development] KBanause:
@mathkid:

It's nice that you have a dedicated download page for your kernel but there's way TOO much ad on that page. Those ads are even BETWEEN the different download links.

Is it possible to reduce them (or even completely remove them)?

Greetings from my TF201 and KBanause
[Nexus S Android Development] tchaari:
If these ads let him get some cash, we can live with them ;)
[Nexus S Android Development] KBanause:
Just tried to install the 16.5 cfs but didn't get past the Google screen.

Now I have seen that there are two different md5sums...

I have the second one on my phone (and on the second screen you can see how annoying the ads are. @mk please move them to the right side or remove them).

Greetings from my TF201 and KBanause
[Nexus S Android Development] Icecoldmeat:
Download links dont work :(
[Nexus S Android Development] caleb1783:
thanks mk...

your work is ur legacy...

^^
[Nexus S Android Development] b1337:
U needz a life bro!! And deep idle isn't that cool lol ;)
[Nexus S Android Development] nodstuff:
I am sick of people like you, I am willing to bet any colour of money that 90% of the people that voted for deep idle in the poll don't know how or when it works. I reckon most of them are like qtwrk and think it works when the phone is doing nothing. How many times must it be said before they listen.

Deep idle only works while using GPS, Bluetooth or music.

Even then the test was done over 10 hours and there aren't many people using Bluetooth, GPS or listening to music for 10 hours a day.

I think that in normal use the battery savings produced by deep idle are negligible, unless you are using the aforementioned GPS, BT or music A LOT. When your phone is idling in your pocket deep idle is NOT used

Cpuidle back port was actually used more in day to day running of the phone than deep idle.

And now it is gone because some people that don't even know how deep idle works want it back.

How about people read before they ask stupid questions or moan about something they think works for them while they leave.their phones overnight and they even post

a bull**** on xda for all to see. Do they not realise that there are people who KNOW that deep idle doesn't do anything while it is idling??

XDA is turning into playschool.
[Nexus S Android Development] b1337:
^truth
[Nexus S Android Development] :
It's saving considerable power for music. Also, if you download or stream something with the screen off. I've just measured the amps and proven it (apologies to all for my previous test results).

Was it? I was under the impression that it enabled the DEEP IDLE processor state the same way Ezekeel's implementation did. I posted an ARM slideshow pdf about it on my battery thread.

The only issue I notice with DI is that it doesn't shut down the processor when the screen is on. However, the power drawn by the screen is monumentally more than any CPU drain, so that any potential DI savings are negligible if the phone is being used with the screen on. If this is what CPU Idle is supposed to provide, then it isn't worth it.

Me too. DI is a good thing.
[Nexus S Android Development] SA-07:
Sure, go ahead and test. I'll see the results :D
[Nexus S Android Development] nodstuff:
If you listen to music for an hour a day what are the potential battery savings?

The number of people using more than that is pretty small I will bet.

As for cpuidle, isn't it a back port of the whole idle setup from the new kernel sources.

Idle, sleep, deep sleep, all of the states. Not just deep idle.

If they thought that code needed updating then obviously they made it better.

If deep idle is implemented in it then isn't it better than having just deep idle??

I would prefer updated code to manage ALL idle states.
[Nexus S Android Development] caliban2:
No, it's not the truth. People like nodstuff suck just as much as those claiming didle is some magic fix.

It's a lie that deep idle only works when playing music or using GPS/Bluetooth. These are just examples. Maybe you guys should read it up yourself before shooting others down.

Oh, and btw? Battlife is better for me with 16.5 and didle on, compared to 16.0.
[Nexus S Android Development] nodstuff:
The whole point I was making was that deep idle does NOTHING while the phone is siting on your locker at night. NOTHING.

people's keep saying that oh I lost this much last night without deep idle compared to this much with deep idle pointless information as deep idle is a higher state than deep sleep and when the phone is resting at night it is in deep sleep.

Deep idle works, great, that's not a bad thing. People posting **** on xda is a bad thing.

Maybe you should read something before you post.

Oh and btw, I don't care.
[Nexus S Android Development] :
Cool, I'm going to check deep idle savings while I have the meter hooked up too.

For kernel benchmarks and more, see HERE
[Nexus S Android Development] caliban2:
That's okay about deep sleep, we're d'accord on that. but you keep saying didle only works with music, GPS and Bluetooth and therefore it's more or less useless - not true.

As for cpuidle, I'm still trying to find out what it actually does different. From the threads here it looks mostly like people are just a fan of it because it's new...

Oh, and it's okay for you to not care about my battlife - was intended that way. Because this is with my setup. Mine alone. That's what most people forget - every phone is used differently. :)
[Nexus S Android Development] DarkhShadow:
MK can you please read my post on page 267?

Thanks

Sent from my ice cream powered Nexus S
[Nexus S Android Development] SA-07:
What settings?
[Nexus S Android Development] DarkhShadow:
200/1200 clock, standard voltages+25

Happened Friday night as well with completely standard everything

Btw what is suspend_backoff?

Sent from my ice cream powered Nexus S
[Nexus S Android Development] SA-07:
Ok do you have any apps running that could cause this? Maybe change your io scheduler to noop

Even change governor
[Nexus S Android Development] DarkhShadow:
Its not apps, as shown by better battery stats the thing keeping phone awake for 8 hours is under kernel wakelocks, but I will try different io and if that doesn't work will change governor

Sent from my ice cream powered Nexus S
[Nexus S Android Development] sakisds:
Hey mathkid,

the BLD scheduler was announced earlier today, any plans of including it in the next release? It's still marked as experimental but it might perform well.

Edit: I said the same thing twice. Brain crashed for a moment.
[Nexus S Android Development] SA-07:
Oh wow it looks great...

Yeah sure, I'll see if I can include it once the patches are released :)
[Nexus S Android Development] qtwrk:
yo! , MK , your web site still displays 3.0.19 when you are already updated to 3.0.20

and in additional governor , you didn't put weathley, lionheart or something...
[Nexus S Android Development] Shawtux:
Great update! Hopefully it keeps being as great as always.

Being using it for a while now with ng ROM.

Getting like 15 hours with normal usage. Games, web and stuff with 2g and wifi of most of the time.

Lulzactive governor and deadline scheduler.

Nice. Going to try to find better config got battery and performance ratio
[Nexus S Android Development] Imppy:
Is it me or idle stats show on or off stats as 0 in 16.5

I have code name rom
[Nexus S Android Development] R-TEAM:
Hi,

very good battery performance ...... have nearly get the GB up-time .....

Fast and stable too as i see ATM so an nice kernel again ;)

mathkid, have you looked at KSM to implement it ?

(-> http://xdaforums.com/showthread.php?t=1464758 a good explanation and this i use on my TouchPad)

Regards

R-TEAM
[Nexus S Android Development] SA-07:
Thanks! I'll look into it
[Nexus S Android Development] TheLastMirana:
Math lid do u have the deep idle fix for code name rom
[Nexus S Android Development] SA-07:
Grab the fix from my FAQ but androiduser is incorporating the fix as well
[Nexus S Android Development] Icecoldmeat:
When setting liveOC to 110% or higher, phone is rebooting 19 seconds afterwards..
[Nexus S Android Development] DaX05:
From the MK's FAQ; Question #4:

"Why am I getting random reboots?

You probably have it OC'ed too high or your phone can't handle the uv. If you get random reboots, first try raising all voltages. If that doesn't help, then lower the clock speed.

Beamed from my Nexus S
[Nexus S Android Development] KBanause:
Why am I getting different md5 sums on the download page (and not only for the 16.5 cfs kernel)?

When browsing through the download directory ( http://downloadandroidrom.com/file/matr1x/NexusSandNexusS4G ) I can see a md5 sum for every file. But when I click on a file to download it, in the summary right above "Click here to download" there's a completely different one.
[Nexus S Android Development] nexus_junkie:
I found

http://xdaforums.com/showthread.php?p=22477212#post22477212
[Nexus S Android Development] Imppy:
I'm not getting any idle even with patch ...on and off still 0 ...codename rom
[Nexus S Android Development] sperelli:
good to have deep idle back, working fine so far..:p
[Nexus S Android Development] :
Works fine with Pixel ROM. EDIT: Sorry it may be that you need to make sure your phone is doing nothing, then open and close GTalk.
[Nexus S Android Development] nexus_junkie:
Matr1x v16.5, Deep Idle disabled by default. So you must enable with NSTools or init.d script.
[Nexus S Android Development] Imppy:
Done all of the above but still the same...weired
[Nexus S Android Development] :
Tried Pixel ROM?
[Nexus S Android Development] nexus_junkie:
Deep Idle activated when screen off. OFF the screen and ON after a minute. Check it out.
[Nexus S Android Development] DarkhShadow:
No it only does that when playing music or similar things with screen off

Sent from my ice cream powered Nexus S
[Nexus S Android Development] Harbb:
It'll go into di for a second or two not long after you turn the screen off, even if not playing music. Good way to quickly test its working.
[Nexus S Android Development] nexus_junkie:
http://xdaforums.com/showpost.php?p=22477212&postcount=984

That patch perfect!!!
[Nexus S Android Development] geebees90:
Hi everyone,

My question might be irrelevant. But I will appreciate anyone who can help me out with this. I have a Nexus S i9020T that I am using with windmobile in Vancouver Canada. I have a basement suite where my signals aren't very strong and I heard that flashing a good radio would improve the reception. So given my situation, can anyone please advice on what radio would work best for me? Replies will be greatly appreciated.
[Nexus S Android Development] 4I-I:
The best way to know what radio works best is to try them out! Im in south-west germany and kb3 radio's best for me.

Just flash a radio and check upload and download speed of your mobile data with an app of your liking! ;)

sent while eating an ice cream sandwich in the matr1x
[Nexus S Android Development] centroi:
I think deepidle no save battery while phone is screen off, but can appreciate that using phone it drain battery slower

lulzactive - sio in 16.0 (cpuidle 3.2) 8% 7 hours

lulzactive - sio in 16.5 deep idle enabled (working properly) 12% 7 hours

checked with betterbatterystas and no app draining battery, little bit usage in kernel wakelocks, at 200-800 and 99% of time in deep sleep, 1% at 200 mhz

?¿?¿

in my last test of deep idle in 15.5 I cheked that with deep idle enabled or disabled there is not difference, and any battery saving, only while in use I think
[Nexus S Android Development] caliban2:
Since nobody can sit in your basement and test another radio down there, you have to find out yourself. :)

Keep in mind that better reception normally means more power-drain, thus shorter Batt-life. Also in the us there seem to be different radio versions around: capped in speed, but better in specific networks. Dunno if that applies to Canada as well, but make sure you read the radio thread closely. (Iirc, the xx-radios are uncapped)
[Nexus S Android Development] caliban2:
Mathkid, never made it back to you, but my reboot bug is gone with v16.5. :)

Running smooth and stable, battlife is great!

Setup:

16.5 cfs, lazy, didle on, max-freq on, deadline, 100-1000 MHz, bln & touch wake on. Rest is stock.

Think I'll give smartass and sio another try later.
[Nexus S Android Development] :
There might be a small benefit to deadline over cfs when using lazy,

check: https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdDhvTmFUU25vblh4a1NjT2lkMnBRb0E
[Nexus S Android Development] caliban2:
Damn, those spreadsheets have evolved since I checked the last time... :D

Thanks, looks like deadline is the best for lazy AND smartassv2 then... will need to study your tests further. last time in real life use, I got the impression that smartassv2 gave me better battlife in active use (surfing, texting, movie - that kind of activities). But this isn't the scope of all the benchmarks, right?
[Nexus S Android Development] :
I think noop just edges past deadline for smartassV2

Battery life was something that I started studying a short time after doing the governors and schedulers. In the battery tests I've done with the amp meter, and in the overnight tests Harbb has done, it looks like the best battery saving is with conservative.

Still, conservative is too slow for me. I prefer smartassV2. Nothing is going to get much closer to performance as a frequency scaling governor.
[Nexus S Android Development] :
Results for matr1x 16.5 are up!

Please note, in the bfs vs cfs comparison, it looks like bfs offers some cpu benefit, however, it didn't seem to enjoy the vellamo benchmark at all, producing bad gfx scores. This may indicate bfs introduces problems somehow.

For kernel benchmarks and more, see here: http://goo.gl/mpeHI
[Nexus S Android Development] sperelli:
same here...

however math, this version does magics!
[Nexus S Android Development] MaXAiRO:
BLD and BLN

I have BLN Control Pro app and NSTools. If I have both BLD and BLN on BLN works only for missed calls, if I turn BLD off BLN works perfectly both for missed calls and every other app eg. GO SMS Pro. Are you aware of this bug? I don't know if mathkid can do something about, maybe it depends on neldar (BLN dev) or Ezekeel (BLD dev).
[Nexus S Android Development] Imppy:
My deep idle is now working...by reinstalling kernal
[Nexus S Android Development] italia0101:
How do you get top off to work? Only top on is working for me... I'm in stock from with flavors installed
[Nexus S Android Development] moriz1:
I got a reboot today. I was playing music, with Bluetooth active and connected to my car speakerphone. It was triggered when I was I'm the manage apps screen.

400-1300mhz, conservative.
[Nexus S Android Development] :
Hi mk,

I have noticed this behaviour with your kernel that I do not see on others. After I install, it boots up as I would expect. But, if I reboot, then it goes to the Google Logo for a long time, then reboots itself in the normal way (i.e. first Google Logo, then quickly disappears/reappears with the capacitive button backlights, then bootanimation...)

What is the reason for this?
[Nexus S Android Development] derekwilkinson:
i've never seen anyone with this problem before. try reflashing and wiping dalvik-cache

---------- Post added at 02:43 PM ---------- Previous post was at 02:43 PM ----------

use 100-1000 and raise voltages
[Nexus S Android Development] caliban2:
Uh, that's what I was getting with v16. Oo either like you described or it hanged on bootanim -> batt pull. Almost on every reboot, except when I was logging via adb... (of course)

had the impression it's some kind of data corruption in cache or dalvik (because nothing got broken or reset by it).

Is this with v16.5?

So far i didn't get it at all with it, but you make me wonder if it will happen again. ^^
[Nexus S Android Development] italia0101:
I'm on stock ics .. havented undervolted , and I get a lot of reboots ?
[Nexus S Android Development] SA-07:
The kernel is UV by default. Raise voltages
[Nexus S Android Development] italia0101:
I think it was the into voltages ... raised the a tad.. so far so good ...
[Nexus S Android Development] :
Hi mk, did you see my question? People have tried to answer, but I'm not satisfied until I hear it from the horse's mouth.
[Nexus S Android Development] SA-07:
I have not experienced that. Try reflashing the kernel, making sure to wipe dalvik cache.

Did you do a clean install when flashing the rom
[Nexus S Android Development] maniac2403:
I am with Wind Toronto and KI1 works very well for me. No signal drops at all.

Check this thread out for more discussions:

Radios for Nexus S
[Nexus S Android Development] caliban2:
If he really experiences the same as I did with v16, wiping caches and even clean install will not help. Did all that. Also, by simply flashing another kernel the problem was gone. Flash v16 back, so's the bug.

But raising voltages could help... why didn't I think of that earlier? There's a thin range where an uv'ed sys appears stable, yet the CPU produces some garbage -> bad data in files. If this happens in caches, it could explain the extreme slow-downs I got sometimes as well as the boot problems...

Making sense? ^^
[Nexus S Android Development] SA-07:
Yeah my kernel was UV on gingerbread as well and that never happened.
[Nexus S Android Development] italia0101:
OK so I just flashed this kernel coming from speedy 7..

My Bluetooth won't turn on and deep idle top off isn't working , if tried the open camera thing as well for deep idle
[Nexus S Android Development] SA-07:
Bluetooth works fine so it is the rom.

Other q has been addressed in the FAQ
[Nexus S Android Development] italia0101:
I tell you what... that's my bad lol.. I just didn't see it, sorry for blatent stupidity
[Nexus S Android Development] SA-07:
It's no biggie :)
[Nexus S Android Development] caliban2:
Yeah well, gb and ics are two different beasts... ^^

So far I've been on lazy with 16.5 and did about 15 reboots to test. It uses mostly 100 & 1000 MHz, only little use of 2-800.

Smartassv2 (which I was using on v16) scales more evenly, making use of all steps. Switched back to it now, let's see if it happens again.

Edit:

K, it happened. Didn't take long for the system to become sluggish - manual reboot, stuck on bootanim. Battpull, attempt to edit this post - freeze. (This is new)

Another battpull, frozen on bootanim ... wiped dalvik and /cache. Booted up fine.

All I had changed was governor (lazy was fine since release). According to the different use of cpu-steps mentioned previously, I now upped voltages for 200-800 MHz +25. Now I'm waiting. ^^

Edit2:

2 1/2 hours and 2 deliberate reboots later (went fine). Looks like it's been really that, my phone not liking the undervolting on at least one of the 3 freq-steps. (Usage after upping the voltage was the same as before - watching stargate atlantis and surfing the web a bit ^^)