yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Arkaknio:
I tried to install v8.0 cfs over 2.3.6 an it completely ruined my phone. All was resolved with a CWM restore.

Means this that the kernel isn't compatible with 2.3.6 Gingerbread?
[Nexus S Android Development] SA-07:
No it is compatible. What do you mean by "ruined your phone"
[Nexus S Android Development] Arkaknio:
Flashed again and everything seems to work perfect.

Weird... :S

Enviado desde mi Nexus S usando Tapatalk
[Nexus S Android Development] SA-07:
Haha yeah that was weird. ;)
[Nexus S Android Development] RonnieRuff:
Ruined your phone really? Hate when that happens. :-)

Sent by pure Google goodness. F#*$ Apple | Yes I am a CRACK FLASHER - Math Kid's kernel - Pete's nightly - Zeam launcher
[Nexus S Android Development] joker2wild:
Don't feel bad bro, I have not been able to use any of the matrix series.. every one I have flashed has caused my phone to crash. Try running netarchy or trinity.
[Nexus S Android Development] SA-07:
You do realize it works for him right? And try raising the voltages if you wanna heh
[Nexus S Android Development] RonnieRuff:
Or that new kitchen sink 2.6 cfs

Sent by pure Google goodness. F#*$ Apple | Yes I am a CRACK FLASHER! - Math Kid's kernel - Pete's nightly,2.3.7 - Zeam launcher
[Nexus S Android Development] hansmrtn:
Yes. Finally works without freezing on my ns!
[Nexus S Android Development] SoleOfJohn:
8.0 CFS is just as smooth as 5.5 CFS! Great work man!
[Nexus S Android Development] benrees21:
1 day 16 hours 30 mins on battery and 10% left. Haha this is crazy battery life lol.

Sent from my Nexus S running NSCollab ROM and Mathkid's Supercalifragilisticexpialidocious Kernel!!!
[Nexus S Android Development] psygbert:
but don't drain your batt often. that is not good for li-ion ;)
[Nexus S Android Development] DaX05:
I had trouble with 5.5 a while back but 8.0 cfs is flawless! Dude, great job! Liking that Lazy profile lol.
[Nexus S Android Development] SA-07:
Lolol
[Nexus S Android Development] nazimster:
Wow this is great

Thanks
[Nexus S Android Development] SA-07:
No probs!!
[Nexus S Android Development] benrees21:
Latest NSCollab.42 + 8.0 CFS = Wow!!!

Sent from my Nexus S running NSCollab ROM and Mathkid's Supercalifragilisticexpialidocious Kernel!!!
[Nexus S Android Development] SA-07:
Sweeeet
[Nexus S Android Development] al_madd:
using matrix v8.0

OC to 1.4Ghz...try quadrant test for several times...highest score 4500...after that my nexus rebooted automatically...:p:p
[Nexus S Android Development] SA-07:
Hehe, raise voltage by 20
[Nexus S Android Development] irishrally:
2746 smiley faces

207 "lol"

47 semi useful comments

I counted. PM for spreadsheet.

All in good fun.

EDIT: Crap, you meant 3k posts in this thread. Ah well.
[Nexus S Android Development] SA-07:
Ok.... Thank you for doing that??

Add this one to ur little list

-_-
[Nexus S Android Development] irishrally:
Aw, missed opportunity for what could have been you're funniest "lol" yet.
[Nexus S Android Development] SA-07:
I know, what a shame...
[Nexus S Android Development] saranyan:
Mk, whats the difference between v8 and v8+ with NSCOllab.??
[Nexus S Android Development] SA-07:
Frank and I decided to stick with the current speeds and voltages for the plus version.

The only true difference this time is bln is enabled in the 8.0+
[Nexus S Android Development] saranyan:
Cool, I'll flash once home, College now:(
[Nexus S Android Development] simms22:
---> :D
[Nexus S Android Development] SA-07:
Haha nice! So if you use bln, go ahead and enable it in the bln control pro :D
[Nexus S Android Development] arshad14:
Is there any way to make google wallet run on this kernel? It keeps saying that I don't have sufficient "test-key" privileges. I have it running on my I9020T running on the wind network in Canada which is on the 2.5.6 stock kernel.
[Nexus S Android Development] SA-07:
Try following this:

http://xdaforums.com/showthread.php?t=1286315
[Nexus S Android Development] ChargingPaladin:
Just flashed 8.0 bfs. Screen has a green tint at 25% brightness, just fine at 100%. Did not happen on 7.5 cfs. Anyone else experiencing the same?

Sent from my Nexus S
[Nexus S Android Development] SA-07:
It seems bfs is a bit brighter. Try flashing cfs and see if it persists
[Nexus S Android Development] mike216:
Math genius

thanks MK,great job on 8.0+ love it extremely fast, cant wait to see what kind of battery i get from lazy after wiping my stats tonight

VERY MUCH APPRECIATED ;)
[Nexus S Android Development] ChargingPaladin:
Flashed CFS, colors back to normal. Full disclosure: when flashing BFS the first time something didn't take, had to flash a second time (as mentioned by someone else earlier).

Sent from my Nexus S
[Nexus S Android Development] SA-07:
Yeah :D
[Nexus S Android Development] jeffkhlam:
i wanna try but i have a question, how do i go back to stock kernel if i want to go back? thx.
[Nexus S Android Development] DaX05:
You should of made a backup to your stock rom before making any changes.
[Nexus S Android Development] SA-07:
Yeah, make sure to have that zip on ur sdcard so it is readily available for flashing
[Nexus S Android Development] tempera:
What voltages do you recommend for undervolting?
[Nexus S Android Development] SA-07:
This is undervolted already, don't worry about it
[Nexus S Android Development] jeffkhlam:
no, i dont anna go back to my backup. is there anyway to just flash back the stock kernel? this way i dont need to go back to my old backup after i us it for weeks.
[Nexus S Android Development] SA-07:
Ohh... someone should have it provided somewhere here or on Google. I don't have one but if you Google it you should be able to find it :D
[Nexus S Android Development] tempera:
I undervolted even more, I think -25 across all with setcpu. my phone is runninh fine, will that increase battery life even more?
[Nexus S Android Development] SA-07:
Whoa mine were already uv'ed by 25....

That will increase battery but the stability will be lost

If ur phone can handle it then fine but you might start to get random reboots
[Nexus S Android Development] dario3040:
Make a new backup then?

The only way I know of is to compile it from Samsung's source code.

No reason to go back anyway
[Nexus S Android Development] mike216:
Bow down (I'm bowing )this is the best kernel on batter life without loosing any speed but in fact gaining,ilk give it up this is the sh*%

THANKS,REALLY APPRECIATE IT
[Nexus S Android Development] khartaras:
I'm used to Trinity, which is already crazy fast, but this... It's stupid fast! What's the bus speed?

Also, undervolted by -40, and battery life is insane now.
[Nexus S Android Development] SA-07:
Tbh I kept the bus speed at stock...
[Nexus S Android Development] khartaras:
It's still superfast...

How about a special performance edition 220MHz Matr1x?
[Nexus S Android Development] SA-07:
Maybe once I add ezekeels live oc :D
[Nexus S Android Development] life2monkeys:
Is this safe to flash on rooted stock 2.3.6?
[Nexus S Android Development] SA-07:
Yup :D
[Nexus S Android Development] life2monkeys:
Thank you kindly ^_^
[Nexus S Android Development] SA-07:
No probs!
[Nexus S Android Development] life2monkeys:
May I inquire as to the difference between CFS and BFS? (sorry new Nexus S user here! Coming from an Atrix)
[Nexus S Android Development] SA-07:
Here's a good little answer

http://xdaforums.com/showthread.php?t=808910
[Nexus S Android Development] lolokman:
Will you implement live oc into your kernel?

That sounds great
[Nexus S Android Development] SA-07:
Yeah next update
[Nexus S Android Development] jeffkhlam:
sorry, new to flashing kernel. i just flashed your kernel, how do i set voodoo, cpu and BLN? i guess i need to get setcpu and BLN control from market, but how about voodoo?

thx in advance.
[Nexus S Android Development] SA-07:
Voodoo control from market ;)
[Nexus S Android Development] mike216:
If you have other than 4g then just flash nscollab and you'll have everything you need and its one bad ass rom anyways,its a must
[Nexus S Android Development] jorim.tielemans:
Something to implement?
[Nexus S Android Development] mike216:
Is there any difference between 8.0 and nscollab 8.0+ my guess is 8.0 is slightly undervolted,if that is the case could you please tell me how much more 8.0 is undervolted across the board,thanks MK
[Nexus S Android Development] saranyan:
Only difference is that BLN is turned on in 8.0+. No changes in voltages and frequencies.
[Nexus S Android Development] benrees21:
Ok what is live oc?

Sent from my Nexus S running NSCollab ROM and Mathkid's Supercalifragilisticexpialidocious Kernel!!!
[Nexus S Android Development] bringonblink:
Hey mathkid , i'm back testing your new 8.0 CFS. Got bored of trinity and not being able to custom UV.

Miss meee? :3
[Nexus S Android Development] SA-07:
Lol yeah!

Saran 8.0+ doesn't have bln enabled
[Nexus S Android Development] saranyan:
Lol. Sorry my bad. I thought it was the other way around. :p
[Nexus S Android Development] SA-07:
Heh np
[Nexus S Android Development] dario3040:
Kind of like the governors, just better.
[Nexus S Android Development] bringonblink:
I'm not sure thats quite accurate, from what i understand it allows you to overclock/undertheclock the bus on the phone while the phone is running.

Because the gpu speed is linked to the bus speed, you can get more performance while keeping the cpu speed low (800mhz for example)
[Nexus S Android Development] al_madd:
It is ok I use SetCPU to OC and add voltage(my phone keep reboot when I OC to 1.4)???

Afraid reduce the maximal effect of martix kernel...
[Nexus S Android Development] gouthamsn:
I seem to be having this issue.. I have asked you this before .. could you please explain the logic if possible ..

I have a screen off profile at 200 MHz and set to 900mV.. and nearly 70% of the time CPU is at 100 MHz .. but still my battery seems to be draining out fast 1% for every 10 mins .. I have put off everything except data.. on 3g.. signal is about 45%

any help would be great... thank you...
[Nexus S Android Development] saranyan:
Which governor are you using?
[Nexus S Android Development] gouthamsn:
1300 interactive when above 50% battery ..

and ondemand 1200 for below 35, 1000 for <20 800 for < 10
[Nexus S Android Development] dario3040:
Any source on that?

http://xdaforums.com/showpost.php?p=14529333&postcount=5
[Nexus S Android Development] mike216:
Customize buss speed and frequency
[Nexus S Android Development] Drew474:
where is the links to download the kernel? Am i being stupid?
[Nexus S Android Development] al_madd:
http://www.forums.acsyndicate.net/showthread.php/1466-KERNEL-ACS-*Matr1x*-with-BLN-and-voodoo-v8.0
[Nexus S Android Development] Ezekeel:
What is the point?

These screen-off daemons and profiles work on the assumption that the state of the screen (on or off) can be used as an indicator for the CPU load, i.e. it is assumed that while the screen is off the CPU load will be low. While this is probably true for all CPU activity related to graphics, there are still several processes which are not influenced by the state of the screen and thus for these processes the CPU load will not diminish when the screen is turned off, for example background processes like playing music. And limiting the CPU performance while one or more background processes need the juice does not seem like a smart idea to me. So, instead of using the state of the screen as an indicator - which does not really work well as explained above - why not use a better, more direct indicator for the CPU load: the CPU load itself. And that is exactly what governors are supposed to do. So as long as the governor is doing its job well, messing with that and enforcing additional restrictions based on the screen state does seem more harmful than beneficial to me.
[Nexus S Android Development] SA-07:
I mean you can use profiles and see how it works for you.
[Nexus S Android Development] R-TEAM:
Hi,

i musst disagree here with you ....

The governor should make the phone smoth and fast responding on my input with the lowest cpu usage that is needed for this.(and so the lowest power drain ...) Even the phone can always run at 1000/1000 .....

But if the screen of - i dont interact with the phone !

I dont need smoth scrooling or any other GPU relatet thing.

And i realy dont care if the job a task need is done in 0,1 sec or 1 sec .....

BUt i save many battery power if i set the screen off max freq as low as possible ...

I have an screen off profile from 100-400Mhz - enough to play flawles mp3 music and have an gps navigation recording my position too.

(by 100-200 i haved rare mp3 playback shutters ...)

But with max. 400Mhz - it uses less power as with 800Mhz.

As i sayd - time is not a critical factor by screen off (so its dont harm the same work need at 400Mhz the double time es by 800Mhz).

With 400Mhz the voltages are lower as with 800Mhz - so i save battery power for the same work who i dont care it is take the double time .....

(only if the voltages the SAME - then the power drain is the same for 400 or 800mhz - 800Mhz double freq but half the time for the same work)

[not exactly - as even with the same voltages - the higher clock speed generate higher leakages and additional the gpu is higher clocked waht i dont need by screen off ...]

So "I" think screen off profiles will save power ......

Regards

R-TEAM
[Nexus S Android Development] SA-07:
What governor are you using?
[Nexus S Android Development] Ezekeel:
First, saying that there are no time-critical processes going on while the screen is off is a generalization. You gave a good example yourself with media playback. Other examples might be VoIP calls or heavy use of the mobile broadband for example while listening to internet radio.

Second, your calculations are flawed. If the CPU spends 2 x t seconds on a task when running at half speed it only needs t seconds to finish the job on full speed and the CPU can spend the other t seconds idling. It is called 'race-to-idle'.
[Nexus S Android Development] mike216:
Aren't screen off profiles a bit like tying your hands behind your back isn't the governor (ondemand,lazy)

Letting the cpu throttle as needed
[Nexus S Android Development] dario3040:
Ohhh, you mean the thing all the dual cores fail at doing? :P (Tegra 2.....)
[Nexus S Android Development] SA-07:
Hahahaha :D
[Nexus S Android Development] Ezekeel:
Hmm. And now that I think about that I ask myself if setting a hard limit for the maximum frequency generally is a bad idea. I used to limit the maximum freq to 800MHz and the last days while testing the Live OC mod I did use a maximum freq of 1100MHz. However I did not at all notice a larger battery drain - on the contrary it rather seems to have decreased. I think this can be attributed to the race-to-idle effect explained above.

Going a step further, logic also dictates that overclocking the CPU should on average lead to a decreased battery drain as long as no disproportionate increases in voltage are necessary. Well... that is something I would call counter-intuitive.

Do they? I did not know that. Do you know why that happens?
[Nexus S Android Development] SA-07:
Very weird
[Nexus S Android Development] R-TEAM:
Hi,

you are right IF the voltages from the different CPU speeds the same ....

But it isnt !

If the cpu uses 2 x t seconds at half speed with 800mv and t seconds at full speed with 1100mv ... who need more power ? :)

To be precise :

I use 400Mhz (the max off screen cpu freq) at 1050mV and the non overclock max freq default is 1000Mhz at 1250mV. (have my Nexus already undervoltet...)

So the Mhz/Time calculation will always the same , 0,5 x Mhz = 2 x Time and the other way - BUT the mV are different.And this is the difference in power usage.

@mathkid95

I use 2 governors ...

For default OnDemand an by power saving settings (ScreenOff/LowBatt/Batt To heat..) conservative ...

Regards

R-TEAM
[Nexus S Android Development] SA-07:
R.I.P Steve Jobs :(
[Nexus S Android Development] Ezekeel:
No. You are neglecting that on half the speed it will run twice as long. As long as the power drain at the full speed is not twice the power drain at half speed (which it is not, if you look at the voltages) you will have a lower total battery drain.

Take your own example:

power drain on 400MHz = 1050

power drain on 1000MHz = 1250

power drain while idle = almost nothing, let us say 100

time for task at 400MHz = 10s

total power drain at 400MHz = 1050 x 10s = 10500

total power drain at 1000MHz = 1250 x 4s + 100 x 6s = 5600

Impressive, isn't it.
[Nexus S Android Development] SA-07:
Yes, it certainly is :D
[Nexus S Android Development] R-TEAM:
Hi,

No - you math iss wrong.

You assume the power drain from 400Mhz is the same as from 1000Mhz and only diffs from the mV settings - this is WRONG.

At 400Mhz the signal is running 400 million times through the transitors of the CPU and doing his work with 1050mV per second.. with 1000Mhz it is running 1000 million through ....

So the correct calculation would like :

(and Idle is 100Mhz with 845mV)

400 x 1050 x 10 = 4200000

1000 x 1250 x4 + 100 x 845 x6 = 5507000

THIS come closer to real life .....

PS: in your math you say practicaly it is the best run the phone allways at 1,44Ghz (i have this at max) and the complicatet governors and electronic to step the freq is a waste of time and money .................

Regards

R-TEAM
[Nexus S Android Development] Ezekeel:
First, the power consumption is measured in ampere watt and is the voltage x current. The clock speed does not play into this directly, but only indirectly in the sense that higher clock speeds do need a higher voltage to run stable. So your calculations do not make sense.

Second, the idle state is not equal to the 100MHz frequency state. It is the CPU state used when nothing has to be done and the CPU can essentially power down. Thus the power consumption is not equal to a CPU running some task at 100MHz, it is much much lower. Especially on ARM processors which are made for this. Read this: http://mjg59.livejournal.com/88608.html and http://www.lesswatts.org/projects/applications-power-management/race-to-idle.php

And no, a good governor is not a waste. The reason is that switching to that idle state and back takes some time. If a program is running which needs to repeatedly run some small task at an interval smaller than that time, the CPU cannot switch to the idle state, however the CPU load might be small enough to give room for a decrease of the frequency. So, if we cannot switch to the idle state, at least we do the next best thing and reduce the frequency. That is also the reason why a good governor should jump to the maximum frequency as soon as something has to be done, so the CPU can get back to idle as soon as possible.
[Nexus S Android Development] R-TEAM:
Hi,

First i know the things like ampere/volt/ohm/watts and so one ... i have maked my first job with this 25 years ago ................................

That the clock speed is not "Directly" make more power consumption is clear.

It should only make a simply and understandable formula.

But with your math - the power consumption from 500Mhz and from 1000Mhz is the same if i can run it at the same Volting - and yes - you are right - the volting is ONLY important to make run the CPU stable ...

So you have maked an infinity energy source .......?

Like your math :

500Mhz = 800mV x 10 sec = 8000

1000 Mhz = 800mV x 5 sec + 100 x 5 = 4500

So its doing the same job twice as fast with nearly half the power - WOW

AND i have the same volting for 100 and 200Mhz ... so its doing the double job with less power - AMAZING.

Sorry ---... but you should remember that power come NOT from nothing .... and that power is calculatet Volt x Ampere x TIME !!

And if the cpu doing the same work in only half the time ... from anything musst come the power to doing is faster ,as with the half freq ....

So it looks :

100Mhz

Volt x ampere x time = 1 watts

200Mhz

Volt x (ampere x 2) x (time x 0,5) = 1 watts

But as we have seen and i have always said the volting is with higher freq higher ...(to keep the cpu stable)

400Mhz

(Volt x 1.x) x (ampere x 4) x (time x 0,25) = 1,x watts

With more Mhz the CPU draws more ampere - as the transistors musst be worked more times in the same second.

So THIS is the relevance from Mhz and power drain.

It is correct that in idle its drain not the full power out of the 100Mhz .

But as an rough example it shows nice the real life behavor.

But it takes power too and this come additional to the power drain from the workload.(it is very low in comparsion to the workload - this is right)

So the nexus take by 100 and 200 mhz nearly the same power - but above with every freq step more and more - as the voltages musst be rised....

Regards

R-TEAM
[Nexus S Android Development] Ezekeel:
This seems like a fundamental misunderstanding of how CPUs actually work. CPUs are extremely complicated microelectronic devices and not a steam engine. Just because a CPU performs twice the number of calculations in a second does not necessarily mean that this does need twice the amount of energy for that. And no, this does not violate the laws of thermodynamics, because you are neglecting that the largest amount of energy the CPU consumes is transformed to heat in any case.

The wattage is simply the voltage x current and the current should not change that much.
[Nexus S Android Development] morfic:
Has anyone considered not only clock gating but also the fact that at idle a different amount of transistors will be used than under load?

Things are then far less simplistic to explain.
[Nexus S Android Development] R-TEAM:
Hi,

morfic is here right - if the cpu have different idle states (and not only diff freq states) then less power cunsuming areas of the cpu in usage.

But this dont negate my view ;)

@Ezekeel

Yes - an CPU is an much more complicatet thing than an simply steam engine ...

But your logic have more and more errors .....

If you say the most power from the cpu is generatet in heat then i dont say this is false .... but "I" dont think with higher cpu freq this is going better ..................

This is one of the reasons the voltage musst be higher - the heat generating and the lekage between the gates of the transistors.

The heat is generatet from the electrons that flow trough the cpu circuits.

And with the double amount of freq - the double amount of electrons musst flow - the ampere is a direct value from the voltage and the Electrical resistance of the cpu.(and the Electrical resistance generates the most part of the heat).If you would have a non pulsed power on the cpu it would always the same.But if you pulse the flow from the parts that doing the work with an oscillating quartz - then the amount is direct dependent on the freq.And if you set the double freq - the double ampere is running.(from the more generatet heat and more Electrical resistance becouse the more heat silizium it is even higer then the double - but only a verry small part)

I am not an expert in CPU design and power consuming .......

But if i see not valid refferences who say other statements .....

I am going with the good old -> double work ( ore the same in half time) need double power ......

PS:and sorry - i am native german speaking - and not so familiar with writing complicatet tech things in english ;)

So if you have problems to understand parts from my writing pleas ask - i will then try to clarify them.

Regards

R-TEAM
[Nexus S Android Development] benrees21:
Wow some big noise here. Loving the maths. Hey mathkid still going good on this kernel.

Sent from my Nexus S running NSCollab ROM and Mathkid's Supercalifragilisticexpialidocious Kernel!!!
[Nexus S Android Development] Star Shadow:
Doesn't TWRP recovery allow backup of boot only? That would do the job if so.
[Nexus S Android Development] benrees21:
Mathlid your kernel don't play nice with google wallet. Something about test keys.

Sent from my Nexus S running NSCollab ROM and Mathkid's Supercalifragilisticexpialidocious Kernel!!!
[Nexus S Android Development] DaX05:
Matr1x 8.0 with CM7 # 215 running as smooth as silk on Lazy profile and Google Wallet has been flawless. (Don't have a citi card to add my own.)