yashsingh1/xdaforums huggingface dataset:
[Nexus S General] :
I tested Deep Idle in Mathkid95's kernel aswell as Ezekeel's, and got the same result for both. Perhaps Deep Idle used to work in Gingerbread, but apparently this is no longer the case. Other possible explanations include:

1) Placebo effect

2) Ezekeel measured wrong

morfic has suggested that the best way to confirm would be to charge overnight, and bump charge the following morning, then run music (I would absolutely insist with all volume muted and all radios off and not touch the phone for a couple of days). Uses whatever logs to find out when it crapped out. Then repeat with the addidtion of Deep Idle. I won't personally be running this test, I'm confident in my findings.
[Nexus S General] tchaari:
Bedalus, I think that Ezekeel's tests have been done without background music play as you did in your tests. Maybe deep idle is more efficient when you do nothing with your phone...
[Nexus S General] :
Don't perpetuate this myth! When the phone is doing nothing, the processor is in deep sleep. This is a step lower than deep idle:

Deep sleep

Deep idle - Ezekeel

Idle

That is the hierarchy of low power states. Deep idle was possible, but not implemented in any kernel until Ezekeel discovered some existing code (for a different device, author still unknown) and adapted it.

If it ever worked, it is apparently broken now.

For kernel benchmarks and more, see here: http://goo.gl/mpeHI
[Nexus S General] tchaari:
Ok thank you bedalus. So Ezekeel's deep idle is between the deep sleep and the idle states in android. Hum, it is a little bit clearer for me now but I am still confused between cpu idle (backport from 3.2) and deep idle. I am wondering if they are at the same state level. I am also wondering if eugenee's didle is at the same level as the Ezekeel's one... I think I should have some more reading on this :)

Thanks again bedalus ;)
[Nexus S General] italia0101:
so is matrix the best for battery life?
[Nexus S General] :
Matr1x according to my measurements uses less power compared to other kernels.
[Nexus S General] deani77:
I try to use Antutu Benchmark (Free) but before completed bench-marking process it suddenly stop the process.

Any idea why it happened?
[Nexus S General] simms22:
clear the apps data and try again.
[Nexus S General] :
Right, I'm hooking up the whole battery thing again tonight, and if anyone can think of any tests I missed then let me know asap! This is DEFINITELY the last time I will be doing this! (Too freaking scary!)

I'll be testing:

-The new CPU idle (with music on) - can't believe I missed that the first time, using Air Kernel 2.7

-Processor drain (music on) at all the frequencies up to 1200 but this time with the screen off.

I'll also supply a circuit diagram for anyone who PMs me (I'm not making something like that publicly available because I think it might be a bit irresponsible!) If you're thinking this is something you'd like to try, you'll need an analogue multimeter or pure ammeter because a digital one will be difficult to read with constantly changing amps. Also, a battery caddy for 3 AA batteries (I'm using rechargable ones because the volts are a bit less, 3*1.35=4.05 - close enough to the spec 3.7) and plenty of crocodile clips, and some wire, and of course, a xylophone to hold the battery and two cups of tea to hold the wire down onto the battery contacts. If you're thinking of soldering something onto your battery, DON'T - you may accidentally make a short circuit that will be difficult to undo, and cause the battery to explode. Plus the heat of the soldering iron certainly won't do it any good. And don't solder anything onto your phone contacts, just carefully twist a few strands of copper wire around them, so they can be easily removed. REMEMBER I ADVISE THAT NO ONE SHOULD ATTEMPT THIS.

[Q] Why do I need 3 AA batteries when I have the samsung battery?

[A] My multimeter inserts a 600 ohm resistor into the circuit and works out the amps by measuring the voltage drop across it. Running a parallel battery to the phone will prevent it crashing when the voltage supply isn't sufficient for things like screen on+cpu max frequency+sdcard IO... This parallel supply should run directly to the phone, not through the multimeter. It can be disconnected when the screen is off, and will not harm the phone (although it may harm your samsung battery). Remember to reattach it before powering on your screen, or it is likely your phone will crash. I would advise to start with fully recharged batteries, and not connect the USB charger.

[Q] Won't the amps read half of what is actually being drawn?

[A] Yes, but you'll get the correct reading if you unhook the parallel battery.

[Q] Might I also be able to do that when the screen is on?

[A] Yes, but I recommend that you do that with everything possible powered off, wifi, 3G... etc... screen brightness minimum. Set your screen timeout to never, so that you have control over it with the power button. Always reconnect your parallel battery before changing from screen on to screen off, and visa versa. (Due to large power spike)

[Q] I want to try this. Should I?

[A] No, no-one should try this.
[Nexus S General] Icecoldmeat:
I really appreciate all the work you are doing! I see you like it, because if you didnt you wouldnt do all this stuff. Keep up the nice work!

Sent from my Gummy Nexus with some help of Tapatalk.
[Nexus S General] :
Cheers, yes, I'm enjoying it.

I'll just add that Eugene suggested I check the power drain difference between 56 FPS and 65 FPS.

Anyone got any other ideas?
[Nexus S General] aLNG:
heavy task?
[Nexus S General] benoit2600:
I really like your work ! it's so useful for me ! thank you bedalus !
[Nexus S General] :
Yep - I tried running nenamark, but my setup can't handle the amps. Phone dies. We'll never know that one. I guess it's academic really, I think people know that using their phone is the number one battery killer :D
[Nexus S General] deani77:
Still failed to complete the bench marking... it stop after open gl test... small android skating around.

Sent from my CM9 Nexus S
[Nexus S General] :
UPDATE: More battery tests done!

SUMMARY

CPU Idle backport from 3.2 tested. Saves no power.

Deep Idle in ICS retested, saves no power.

+ with screen off max frequency set to on, uses more power.

Deep Idle in GB tested, saves no power.

+ with screen off max frequency set to on, uses more power.

56 fps vs 65 fps. 56 fps saves power.
[Nexus S General] steve.garon:
Exactly the results I was expecting...
[Nexus S General] Harbb:
Thanks for the results bedalus, great work.
[Nexus S General] :
Great article on the difficulties of accurate metering (thanks aLNG):

http://low-powerwireless.com/blog/d...t-schemes-for-battery-powered-devices-part-1/

In the article I believe DUT stands for Device Under Test

The implication is that DMM [Digital Multi Meter] voltage drop readings (to measure amps) take hundreds of milliseconds, a will miss instantaneous battery savings above this time window. However, I am using an analogue meter, the the needle responds to all current. Due to the mass of the needle, there is inertia to overcome, which provides a form of averaging.

Quote from the article:

"a GSM cell phone can have current pulses of 2 amperes that last approximately 500μs while the power amplifier is on and transmitting, and then drop back down to the milliampere level for the remainder of the 4.5 ms GSM cycle."

500μs is 0.5ms, so is 1 tenth of the 5ms GSM cycle. 2 amps at 1/10th of 5ms = average of 200 mA

In my spreadsheet, the reading I get with 3G on compared to off is 0.03 mA

However, the article is talking about broadcasting a signal, where my 3G was idle. I will run the test again but broadcast over 3G to confirm.

EDIT: Done ^^^ will post results asap. Found link to great article of SOC (State of Charge) http://www.mpoweruk.com/soc.htm

EDIT: spreadsheet updated. GSM broadcasting uses at least 170 mA - see row 36. I think this is a nice proof that the analogue multimeter beats the digital multimeter hands down for dynamic amps (i.e. changes happening below the millisecond level.)
[Nexus S General] MaXAiRO:
Bedalus, congratulations and keep up the good work! Have you tested IO schedulers? I would like to know which scheduler is the best for copying files from PC to phone. With sio it takes about 1 hour to copy 3GB, which seems really strange.
[Nexus S General] :
I haven't done any large file copy tests, just regular io. The best scheduler to use seems to depend on the governor you use. Check my study to find out which is best.

For kernel benchmarks and more, see here: http://goo.gl/mpeHI
[Nexus S General] :
UPDATE: Air Kernel 2.7 added!

UPDATE: SG-NS-ICS 31st Jan (Best Colour) added!

UPDATE: Battery Test #2 Setup Video #2 see OP
[Nexus S General] Harbb:
Can't wait to have a look. BTW, the second video says it's private and can't view it.

edit: works fine now, cheers :)
[Nexus S General] :
Oops, will set permissions.
[Nexus S General] tchaari:
About CPU IDLE, it is just another (more recent) implementation of the 4 CPU states. Saving power highly depends on how it was implemented (back ported) for the Nexus S ;) Maybe tweaking it can save more power. This is what I found on it :

http://www.mjmwired.net/kernel/Documentation/cpuidle/sysfs.txt

What do you think about it?

PS1: It seems that you have done further interesting battery tests since last night Bedalus. Nice second viedo ;)

PS2: After your study, it seems that GB is draining more power than ICS. I don't know how ICS eats more battery than GB on my phone :confused:
[Nexus S General] :
Yeah, I tested 3G broadcast, and got a result of 170 mA drain. Almost exactly what was predicted in the article shared by aLNG: http://low-powerwireless.com/blog/d...t-schemes-for-battery-powered-devices-part-1/

Also, read this: Read this: http://www.mpoweruk.com/soc.htm

I don't think we'll be saving more power. Things are now about as good as they are going to get.

And I need someone to confirm this link is working please: https://plus.google.com/photos/102685556297003041834/albums/5704563778358045361
[Nexus S General] nodstuff:
So it's as i thought, deep idle is ineffective, pity because the theory is sound.

at first I thought it was because google had implemented similar code in the 3.x kernel for ICS but seeing that the results are the same on GB that obviously isn't the case.

I wonder how ezekeel got the results he got in his thread about deep idle, maybe it is over an extended period of time that the effects are really seen. maybe the cpu and other hardware has a minimum "on" time before deep-idle truly sets in because ezekeel tested it over 10hrs and got huge power savings.

The only way is to replicate his tests but obviously you aren't going to leave your phone on that setup overnight, and i wouldn't ask you to either as i wouldn't do it.

if anyone wants to charge their phone to full and play a song on repeat for say 10 hours like ezekeel did and put their phone in airplane mode with deep idle on and again the following night with deep idle off and compare the results at the end it may be something but the results wouldn't be perfect as the test isn't perfect, but still it would be a rough indicator.

i would do it but i can't put my phone down for more than 10 mins! :D

Great work with all this bedalus, you are a martyr for the cause!
[Nexus S General] tchaari:
Yes it works Dave ;)
[Nexus S General] :
I need still need someone to confirm this link is working please: https://plus.google.com/photos/102685556297003041834/albums/5704563778358045361

For kernel benchmarks and more, see here: http://goo.gl/mpeHI
[Nexus S General] :
Great thanks tchaari!

For kernel benchmarks and more, see here: http://goo.gl/mpeHI
[Nexus S General] nodstuff:
Working! And added! :D

Edit: Should've reloaded the page before i posted!
[Nexus S General] tchaari:
You are welcome but the content is a little bit scary for our phones :D
[Nexus S General] :
It's a solid theory, and you can see it in action in the 3G broadcast test. If you read the article aLNG posted, there is a reference to how 0.5 ms uses a huge 2 amps, then spends the rest of of the 5 ms GSM cycle using 0 amps. This powering down over the cycle reduces the average to 200 ma. This is what Deep Idle was supposed to achieve, but with the processor.

I don't think Ezekeel's tests were accurate. Read the article I posted on SOC, it shows just how hard it is to measure charge correctly. Battery monitor widget cannot be trusted! Also, Ezekeel does not specify whether he played the same song on a loop, or had the volume on mute.

Sort of, but the test needs to be better. We could try just two runs, one with Screen Off Max Frequency [SOMF] ON and one with it OFF.

Setup must be identical (apart from SOMF). Install battery monitor widget, set history update rate to 10 minutes (not particularly to monitor the battery, but just to act as a timer). Set to run without widget. Turn off all radios, turn off sync, turn off location services, put in airplane mode. Turn off any of Ezekeel's mods excepting (Deep Idle of course). Set up your music app to play the same song on a loop. Make sure all volumes are down. Phone must be in mute. Morfic told me that to avoid the problem of the battery not reporting itself properly you can begin both tests with the same charging procedure: charge while off overnight. In the morning bump charge for exactly one hour. Disconnect, boot, start music immediately. Power button to screen off. Leave phone for 48 hours (should be enough time to auto power off).

After the first test, check the history from battery monitor widget to see how long the phone was on for.

Repeat again but with SOMF set to on.

I may find the time to try this, but then again, I believe my results are correct, so perhaps there is not much point.
[Nexus S General] :
UPDATE: Circuit diagram of test now linked within the battery benchmark spreadsheet. I've decided to share it publicly as I've now set up and run this test three separate times, with no major problems. So I've reclassified it from utterly reckless, to merely dangerously stupid. Do not under any circumstances try this with your own phone! You have been warned!
[Nexus S General] :
I hope my childlike "teacher style" diagram frightens people away. No-one under any circumstances should try it unless they want to risk their phone never working again. (Secretly I hope someone does successfully try it) <<< No one should read that, it's secret.
[Nexus S General] fergie716:
I have the same thing with sio and smartassv2 gov. I change the IO scheduler to deadline and the gov to ondemand when I transfer big files. Seems to work better for that task. Then I just go back to smartassv2 and sio lol

Great thread. Wanna read some of this stuff when I get back home
[Nexus S General] MaXAiRO:
Thanks, I 'll try this combination right now to copy about 4-5GB. I hope it ll give better transfer speed. :p
[Nexus S General] :
UPDATE: Air Kernel 2.8 added!
[Nexus S General] :
UPDATE: Air kernel 2.9 added!

UPDATE: Matr1x 16.0 added!

UPDATE: All Free RAM scores now redone (free before test begins)

-Note, I had to correct Franco and Thalamus, I'd killed all tasks the last time I measured theirs. This time, it's just a measure after a normal boot into my testing setup, after the system has settled. Same procedure for all kernels from now on. Consistency!
[Nexus S General] android_nexus:
http://xdaforums.com/showthread.php?t=1427352

SG updated, 05-02-2012
[Nexus S General] :
Oh, yes, I've done that one, but just forgot to

UPDATE: SG-NS-ICS 5th Feb '12 56 fps version
[Nexus S General] :
UPDATE: Morfic's TEUV with BLN and BLD benchmarked!
[Nexus S General] mobile_pc:
Peter Alfonso's Kernel 08 FEB (flashable boot.img and kernel-related system files from 08 FEB ROM)

Please test it later :)
[Nexus S General] :
Nearly finished with the ROMs. Will have time for a couple of kernels. Thanks for the link!
[Nexus S General] :
UPDATE: morfic's T132 with BLN/BLD

UPDATE: r_data' Air Kernel 3.0

UPDATE: Peter Alfonso 3.0.8+ (Feb. 8th build)

UPDATE: Ezekeel's GlaDOS 2.10 CFS

UPDATE: Ezekeel's GlaDOS 2.10 BFS

Looks like BFS harms performance. Feedback please!
[Nexus S General] tchaari:
In your benchmarks, we can't see if the kernel update is improving the score when compared with the last version. Can you please keep the best score (for example, between brackets with the corresponding version number) in front of the latest version scores.
[Nexus S General] :
Yeah, I kept all the old scores so i might be able to produce this.
[Nexus S General] :
UPDATE: "Best Ever" scores now visible.

Please remember: A small difference in scores may due to test variability.

The average overall variability for a kernel is 2% up or down. Although it is very unlikely for normally distributed data, it is theoretically possible that the same kernel could produce two overall average results that are 4% apart (i.e. the difference between its worst possible, and best possible overall average score).
[Nexus S General] androidphone2012:
@bedalus

work hard without a pause? :) thx
[Nexus S General] :
I'm one of those people who can't switch off.
[Nexus S General] :
UPDATE: Cyanogenmod kernel added! (Thanks mobile_pc)

UPDATE: Matr1x BFS and CFS v16.5 tested

When comparing BFS and CFS please note, BFS seems to perform well, but suffers in the graphics tests only in the Vellamo app. Having never experienced any problems with this app before, this makes me wonder if there is some problem introduced by BFS.
[Nexus S General] tchaari:
Just a small suggestion bedalus: can you please add which version number of each kernel had the best average score? (between brackets in front of each best average score for example).
[Nexus S General] :
The best scoring kernel info is already right underneath.

EDIT: I've just noticed that the ridiculously complicated averaging system I can't cope when I add new kernels, so the previous best scores all took a little dip. Just corrected them now. Will have to keep an eye on that.
[Nexus S General] tchaari:
thanks bedalus. Sorry, I have not seen the details of the best scores rows. I suggested a much simpler thing but you've already done more as usual :D

Thanks again :)
[Nexus S General] aLNG:
I heard that quadrant got update.
[Nexus S General] :
Simms22 tells me the same, I haven't looked yet. It might be worth a little project to see if the scores come out differently. I'm only using the 2D and 3D scores at the moment, because they have very little variance.
[Nexus S General] nexusphone:
Thanks to bedalus' REF, NS forum works better. :)
[Nexus S General] benoit2600:
There is a new version of matr1x kernel (v.17), can you benchmark it please ?

I really love your work ! :)
[Nexus S General] :
np, and thanks!

UPDATE: Mat1x v17.0 added. Beats its personal best!
[Nexus S General] mobile_pc:
@bedalus

CM9 v3.0 default kernel

http://xdaforums.com/showthread.php?t=1399035
[Nexus S General] :
That is above and beyond excellent service! Thanks very much! Will bench this one after I'm done with r_data's latest update.
[Nexus S General] :
UPDATE: Air Kernel 3.1
[Nexus S General] :
UPDATE: Cyanogenmod V3 kernel - Thanks mobile_pc!
[Nexus S General] flibblesan:
Missing deep idle from the Air 3.1 table.
[Nexus S General] :
Oh yes, I'll add that in now. Thanks!
[Nexus S General] glennkaonang:
Bedalus, does the I/O score have an impact on performance?

I saw people mentioned something about the latest Air Kernel having poorer performance than the previous version, and you said that it's due to the lower I/O score.

I thought I/O score is for data transfer only.
[Nexus S General] :
To be honest I'm surprised anyone noticed anything. It was about a 25% drop in IO. That would bring the overall score down by a sixteenth (if I'm remembering the data correctly.) It might cause a little bit of a slow down, perhaps. The OS and apps all require access to data stored on the drive at times.
[Nexus S General] glennkaonang:
I see. Perhaps it's because I don't play games nor do any CPU intensive tasks that I don't see performance slowdowns using the latest Air Kernel.
[Nexus S General] :
UPDATE: morfic TEUV with BLN BLD voodoo sound

UPDATE: morfic T11 with BLN BLD voodoo sound

CM9 KSM versions available too. (I use anykernel versions.)
[Nexus S General] bluelyd:
I always start my day with reading & checking your posts. And always thanks to you in mind. Your works - benchmarks - lead this forum to right side, I think. Thank you very much.:D

Please keep go on this work, but also take care of your health. Nice work and excellent effort. Thank you.:thumbup:
[Nexus S General] glennkaonang:
New update on Air Kernel is out, version 3.2 http://xdaforums.com/showthread.php?t=1469842

Could you go hands-on with it, bedalus?

I'm curious to know whether this new version brings back the I/O high score :D
[Nexus S General] :
Thanks for the tip. I'll look at it asap.

kernels ; battery ; ROM ; gov/sched
[Nexus S General] :
UPDATE: Air Kernel 3.2 benched!
[Nexus S General] bluelyd:
Thank you, bedalus.:)
[Nexus S General] mobile_pc:
Peter Alfonso default kernel 16 FEB

known issue : http://xdaforums.com/showthread.php?p=22872945#post22872945
[Nexus S General] glennkaonang:
Bedalus, Air Kernel 3.2 has CIFS module cooked in.

Might want to add it in the feature table.
[Nexus S General] :
Okay, thanks Glenn!

kernels ; battery ; ROM ; gov/sched
[Nexus S General] :
UPDATE: Peter Alfonso 16th Feb kernel (with reboot issue) benched!

Thanks to mobile_pc!
[Nexus S General] :
UPDATE: morfic's T12 benchmarked!

T12 does not have an overclocked bus/GPU unlike all of morfic's other kernels.
[Nexus S General] mobile_pc:
CM9 v3.3 (v3.4) default kernel by KalimochoAz

Updated kernel 3.0.22

...
[Nexus S General] :
This one may have to wait until tomorrow. I'm running a little experiment on my phone right now...
[Nexus S General] glennkaonang:
Could it be a new benchmark thread, bedalus? :P

Looking forward to your new idea.
[Nexus S General] atlantis.mu:
excellent! many thanks! keep up the good work :)
[Nexus S General] simms22:
@bedalus..

these two kernels need testing, they are cm9 ramdisk kernels. also, you were added to the op in the trinity thread :D

T144-HoneyBadgerB http://goo.gl/LCTvo

T11-HoneyBadger http://goo.gl/JUdQV
[Nexus S General] :
UPDATE: T11-HoneyBadger benched! Results are up!

T144 makes my phone cry digital tears which I wipe up with microfibre handkerchief (i.e. Unable to boot this one.)
[Nexus S General] simms22:
poor phone.. :(
[Nexus S General] Steviemac12:
Bernchmark sheets

Bedalus,

I really appreciate your work, it makes navigating the top kernels, much easier and better to evaluate.

If it is no trouble, could you put a date on your sheets, so we know when it was updated? Sometimes I end up on your sheets from many different threads.

Just a thought.

I do love your detail and methodology.

St3vi3
[Nexus S General] atlantis.mu:
removed, stupid post
[Nexus S General] :
Good idea, I'll start putting dates on the kernels and I'll put a recent changelog (with dates) on the sheet.

kernels ; battery ; ROM ; gov/sched
[Nexus S General] :
UPDATE: Cyanogenmod V3.3 kernel benched!

Thanks mobile_pc
[Nexus S General] :
UPDATE: Air Kernel 3.3 benched!
[Nexus S General] glennkaonang:
Looks like once again the score decreases, especially the I/O.

Anyway, what kernel are you using for daily use, bedalus?

I'm curious to know.

Thanks.