yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] samir5421:
So how's the test with kmobs' kernel?
[Nexus One Android Development] wildmonks:
I posted my results here in this post.

The code tweak he made to improve battery life was probably made elsewhere.

BTW: If the other battery life tweak he made was related to wfi_rate (this tweak helped improve battery life for pershoot), then IR and I have already determined that this tweak has no observable effect when used with AVS.
[Nexus One Android Development] wildmonks:
Update:

-Minor changes since kernel date 062610:

-Added commits relating to the cpu scheduler from IR's repository:

-Tweaked code to allow smoother interaction between AVS and SVS.

2.6.34_AVS-800mV_CFS_1113Mhz_070110.zip

2.6.34_AVS-925mV_CFS_1113Mhz_070110.zip

2.6.34_AVS-800mV_BFS_1113Mhz_070110.zip

2.6.34_AVS-925mV_BFS_1113Mhz_070110.zip

(No audio boost versions, for those that don't like the increased volume during calls.)

2.6.34_AVS-800mV_CFS_1113MHz_NoAudBoost_070110.zip

2.6.34_AVS-925mV_CFS_1113MHz_NoAudBoost_070110.zip

2.6.34_AVS-800mV_BFS_1113MHz_NoAudBoost_070110.zip

2.6.34_AVS-925mV_BFS_1113MHz_NoAudBoost_070110.zip
[Nexus One Android Development] Domskibus:
Just an easy question:

What are the differents bewtween "CFS" and "BFS"?

2.6.34_AVS-800mV_CFS_1113Mhz_070110.zip

2.6.34_AVS-925mV_CFS_1113Mhz_070110.zip

2.6.34_AVS-800mV_BFS_1113Mhz_070110.zip

2.6.34_AVS-925mV_BFS_1113Mhz_070110.zip
[Nexus One Android Development] stage3turbo:
Domskibus

Member RinTinTigger posted links about CFS & BFS on the second page of this thread.

As I am a new user it will not allow me to paste links directly into this thread.

Hope this helps..

p
[Nexus One Android Development] THATTON:
This "easy question" has been answered 583 times in at least two different threads. It's an easy answer when you use the search function. ;)
[Nexus One Android Development] wildmonks:
I updated the 1st post with a short questions and answers section. Hopefully this will help those who are new to the Nexus xda forums. :)
[Nexus One Android Development] mtw4991:
Before you search for that, search for the meaning of facepalm, roflmao:rolleyes:
[Nexus One Android Development] jjss75:
N1 w/ Kang 0.9 sp2** ←oops sorry wrong ROM. CORRECT ONE IS cm6.0.0-alpha1

At first I tried BFS 925 but messed my phone up.

I've dont multitasking straight for like 6hours with the 2.6.34_AVS-925mV_CFS_1113Mhz_070110.zip

Worked amazing even without using ATK most of the time.

No stress switching constantly from QuickDesk together with ADW, Quickoffice Folder Organizer, Gallery, File Viewers all opened.

Tried listening to Pandora while working, using Browser with no ATK, got a little slow but TOTALLY bearable.

FCs throughout the 6hrs was just one from a twitter app and that was it.

Can't believe how far android phones have come, Phew, iPhone's far behind..

zipping the minor update now.
[Nexus One Android Development] boesky:
Have you tried the 800 mv versions? Tried the 070110 800 mV one, and it messed up my accelerometer.
[Nexus One Android Development] LordPhong:
Are you guys/gals all testing this on frf91?
[Nexus One Android Development] SimFox3:
Thank you so much for making a BFS and CFS NO Audio Boost kernel. I'm going to try both and report back my findings. Thanks.
[Nexus One Android Development] wildmonks:
No problem. I didn't want to forever limit the choices of the no audio boost users out there. :)
[Nexus One Android Development] wildmonks:
Was a bit bored today so I went ahead and compiled .35 overclock versions from IR's github.

The one thing I noticed was an improvement in 3D gaming. In Neocore, I have never seen it benchmark over 30fps, until now. :)

Everything else seems to be about the same as the .34 kernels, including Linpack/Quadrant scores, battery drain, and its running nice and stable on cm6.

2.6.35-rc3 kernels (considered a work-in-progress, personally tested on cm6.0.0-alpha1):

-First release, based on IR's source

2.6.35-rc3_AVS-800mV_CFS_1113Mhz_070310.zip

2.6.35-rc3_AVS-925mV_CFS_1113Mhz_070310.zip

2.6.35-rc3_AVS-800mV_BFS_1113Mhz_070310.zip

2.6.35-rc3_AVS-925mV_BFS_1113Mhz_070310.zip

No Audio Boost versions can be found here.
[Nexus One Android Development] jjss75:
no i havent tried those.

now that uve mentioned that i dont think ill even try it haha

which one are u using now?

flashed the minor update n been having problems. a tad bit slower, batt is juiced out quick..

man, it's so hard finding the best combination.
[Nexus One Android Development] xda890:
Have to agree, I can finally choose a ROM without checking if the ROM uses the stock kernel or not... Thx! :D

BTJ
[Nexus One Android Development] wildmonks:
If battery life is you #1 priority and you haven't done so already, you might want to limit the max MHz to something under 1113MHz (like 1075MHz). In order for me to keep it stable @ 1113MHz, I had to revert to using SVS so you won't gain any powersaving benefits from AVS when the cpu hits 1113.

Also if your feeling adventurous, you can try out 2.6.35-rc3 925mV CFS. I've been using it for over a day now without any problems on cm6-alpha1, otherwise stick with 062610 925mV CFS.

The 070110 versions is mainly just an update to match with IR's changes. Personally, I haven't notice any difference between 062610 and 070110.
[Nexus One Android Development] wildmonks:
Ah, your welcome :). Funny, after going back and forth between audio boost and no boost when testing out the kernels, I noticed there is some audio distortion in calls. Not enough to bother me personally but I do see where you guys are coming from in preferring no audio boost.
[Nexus One Android Development] damanrico:
I'm a happy no audio boost user as well. The new 35 kernel seems to work great. Been running it for a few hours now, and it seems to act just like the 34 kernel. Since I don't 3D game at all, I guess I won't see any difference.
[Nexus One Android Development] THATTON:
@Wildmonks- you are doing a spectacular job with these kernels bro! Keep it up. I continue to be amazed! I have always used IntersectRaven's kernels for battery life and Pershoot's for performance and recently battery life as well. Now, I have yours that are a perfect combo of both! Plus, I like the BFS for how I use my phone. You are doing a great job my friend! I look forward to future releases from you. I wish I had the time to compile my own but my wife already hates my computer and phone enough as it is! LOL! So, I will leave it up to you and reap the benefits. ;)
[Nexus One Android Development] wildmonks:
Thank you Thatton! I gotta say, before coming here, I've been with the iPhone for 3 years and had to put up with it's close restrictive and unpleasant environment. But now, since getting the nexus one and coming here, it's just been phenomenal and amazing to be in a supportive and wonderful open source community. I too am looking forward to being here with the great coders/developers and the awesome users here in this forum. :D
[Nexus One Android Development] smedentsev:
2.6.35 branch report

Just to report on the .35 kernel branch. Running 2.6.35-rc3_AVS-800mV_BFS_1113Mhz_070310 for almost a day now with RoDrIgUeZsTyLe@FroYo [v3.2] r21 ROM [FRF91] - absolutely stable for me. Excellent job. You rock! :cool:
[Nexus One Android Development] tecknight:
Thank you Wildmonks

I have been using your kernels now thru several of Paul@Modaco's releases. I have found your kernels to be extremely stable while remaining fast and best of all, using a fraction of the power my previous kernels were using !! Thank you so much for your excellent work !!
[Nexus One Android Development] damanrico:
nvm delete
[Nexus One Android Development] mrmarshall428:
Wildmonks, I'm coming from Pershoot's kernel and was wondering what setcpu settings you are using and governor? I'm looking to reap the benefits of your kernel, just wondering what settings to use. Thanks in advance! Reading alot of good stuff about your kernels keep up the good work!
[Nexus One Android Development] wildmonks:
I'm constantly trying to find the right settings that fits my needs, so this varies for me. Right now I'm using the following, for normal everyday use, that gives me a quick UI experience with good standby/sleep battery life.

Main:

ondemand, min=245, max=998

Profile (only using 1 at the moment):

Screen Off:

conservative min=245, max=998
[Nexus One Android Development] SimFox3:
The .35-rc3 925mv CFS No Audio boost is working perfectly, unsurpringsly

sigh, i'm kinda wishing that you screw up the next build or so. it's getting really boring having perfect builds. As the Joker put it, "Sometimes you need to introduce some anarchy..."; then things will get realll interesting :D
[Nexus One Android Development] wildmonks:
LoL! Well, I kinda like it when there's no issues ;)

Actually, I have been working via private messages with a couple people that have unique issues, so it's not totally perfect for everyone :rolleyes:
[Nexus One Android Development] waylo:
My first results... amazing

I've been trying to get the most out of my Nexus battery life and my efforts up until now have not been too promising.

After hearing about this kernel on a separate thread, I decided to give it a try. I installed the 800mv BFS 7/1/10 kernel 2.6.34 yesterday. I'm running CM 5.0.8. SetCPU with 998 max, 245 min when awake and ~500max/245 min when screen is off.

It looks like I'm lucky and my Nexus is functioning pretty well with only 800mv. No radio issues so far.

So here's a photo of juiceplotter since this AM. Of course, it's not easy to quantitate how much I used the phone (after plugging it into the USB to attempt a screenshot, all the usage stats reset), but this really is remarkably better than before! The slope of the battery discharge really is amazing compared to before! ~20% battery discharge after 7 hours. I'd estimate that I probably had 2x the battery discharge on 5.0.6, thought slightly better than that on 5.0.8 (which I believe is pershoot's kernel).

I REALLY wish I had a battery graph from before the kernel change to demonstrate the difference (the data seems to disappear after a while, but it was scrollable yesterday).

So obviously, a big thanks Wildmonks for doing this.

EDIT: If someone has a better way of getting screenshots (app anyone?), I'd appreciate the info. Tried the android SDK but couldn't get it running.
[Nexus One Android Development] xykj:
2.6.35-rc4

kernel updated again 2.6.35-rc4

http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.35-rc4
[Nexus One Android Development] mortzz:
Been running it for a little while now, nice and stable. Keep up the good work!
[Nexus One Android Development] THATTON:
That is pretty cool news! I'm sure Pershoot, kmobs, IntersectRaven and Wildmonks will be all over this one!
[Nexus One Android Development] wildmonks:
Very nice results! Too bad I can't use the 800mV...

I use an app called ShootMe. After you run it and put it in the background, you just have to shake your phone to take a screenshot.

Cool, but I was kinda hoping to do some PS3 gaming, guess I won't be.. :rolleyes:
[Nexus One Android Development] THATTON:
Nothin' like some good ol' fashioned DEDICATION!!! Thank you Wildmonks!
[Nexus One Android Development] wildmonks:
Haha, np :p
[Nexus One Android Development] SimFox3:
Wildmonks,

I've been running the 800mv cfs no audio boost for a few Hours without any problems (i think), but what kind of failures did you experience with the 800mv? Were they subtle?
[Nexus One Android Development] wildmonks:
In certain areas like around my workplace, my phone would constently start switching between EDGE and 3G (AT&T network). This results in rapid battery drain for me. When I'm at home, I don't experience this problem.

I've seen other reports that when they use 800mV, their camera would not function properly or they can't turn on their screen from standby/sleep. All of these I would attribute to too little voltage being feed into the phone.
[Nexus One Android Development] wildmonks:
Update:

-Changes since kernel date 070310:

-Updated with IR's latest commits (2010-07-04 & 2010-07-05)

2.6.35-rc4_AVS-800mV_CFS_1113Mhz_070510.zip

2.6.35-rc4_AVS-925mV_CFS_1113Mhz_070510.zip

2.6.35-rc4_AVS-800mV_BFS_1113Mhz_070510.zip

2.6.35-rc4_AVS-925mV_BFS_1113Mhz_070510.zip

No Audio Boost versions can be found here.

Thank IR for an awesome job updating his github to rc4 so quickly. :)

Initial testing show no difference in performace. Will have to see about stability and battery life...
[Nexus One Android Development] THATTON:
Already downloaded and testing... :)
[Nexus One Android Development] damanrico:
wildmonks, why do you set the max to 998? Does it have something to do with AVS/SYS? If so, does it save that much battery to set the max lower than 1113?
[Nexus One Android Development] wildmonks:
I find that, when the cpu is at 998mhz or 1036mhz, AVS feeds the phone 925mV and usually doesn't have to bump the voltage unless the cpu needs it.

Note: Not only mhz but also temperature plays a big role in whether how much voltage is feed into the cpu by the AVS

From a AVS/SVS coding perspective, you will save more battery power if you set your max at 1075mhz or lower. At those speeds AVS will always be in use. Its only at 1113mhz that SVS is used.
[Nexus One Android Development] damanrico:
Interesting. Do you think you can give a rough estimate of how much battery will be saved, or is that impossible to say?

Knowing a rough estimate helps me determine if I should set my max cpu to something like 1036 instead of 1113. If it's a small difference, I can live with a little less battery life.
[Nexus One Android Development] wildmonks:
Reporting my overnight battery drain with the .35-rc4 kernel and it seems to still be pretty good. Been getting lots of -mA numbers under -10mA which usually translates to 1%/hr or better battery drain.

You can see my log entry for battery drain here.

Note, I unintentionally "bump" (steps 1-3) my battery which is why after 7 hours, its still at 100%.
[Nexus One Android Development] wildmonks:
I can't say how much you will save as that will depend on your usage pattern and how often you hit 1113mhz. Using ondemand will make you hit 1113mhz almost all the time when the phone is in use. Using conservative will make you hit not hit 1113mhz much less often.

But its not like 1113mhz = super battery drain. Your phone can be on idle but you set your min and max at 1113mhz and battery drain can still be less then if it was 1113mhz and not idle.

Battery drain can be a mysterious thing (haha), so many factors play into it. But I can say I get less battery drain when I lower the mhz.
[Nexus One Android Development] big_adventure:
Just loaded up the 705 925 BFS .35rc4 kernel -

998 - Ondemand is the only configuration

FRF91 - rooted, deodexed, TBW

No special "prep" for benchmarks:

Turning 41-ish in Linpack

Turning 990-1030 in BenchmarkPi (5 runs)

Neocore @ 29.5 Edit: 2nd try pulled 30.0

Quadrant @ 1661 ! That's the best I've seen in Quadrant.

Lovely work.
[Nexus One Android Development] harmohn:
hehe...then you'll like to know i managed to get 1771 on CM6a1 running the 925 BFS kernel :)
[Nexus One Android Development] there_are_four_lights:
[ROM] FRF91 Stock, Deodexed, rooted, busybox, battery %, TB alert/wake/unlock

705 800mV CVS .35rc4 kernel, 1113 - Ondemand

Linpack - 42

BenchmarkPi - 997

Neocore - 31.1

Quadrant - 1663

705 925mV CVS .35rc4 kernel, 1113 - Ondemand

Linpack - mostly 42-44, highest = 45.111

BenchmarkPi - mostly 950-100, lowest 909 (is lower better?)

Neocore - 31.2

Quadrant - 1672
[Nexus One Android Development] jjss75:
wildmonks.... pure genius. A day passed, did exactly what u told me n diff in batt was drastic. was my bday yesterday felt like this was a gift. So into it dun wanna change anymore.

well as of this moment I pretty much trust ur decision so ill go on the next trip n try out what u said. thnx so much for ur work, and the supporting advice to all of us.
[Nexus One Android Development] wildmonks:
Nice! Well happy belated birthday! And glad it worked out for yah :D
[Nexus One Android Development] wildmonks:
Actually this is pretty impressive if you capped your max speed to 998mhz :eek:
[Nexus One Android Development] big_adventure:
I admit, I was pretty happy, and it was (and is) indeed capped out at 998. Froyo with Launcher Pro is already so fast and so smooth that I just don't see the reason to overclock anymore (and I was OC'd for months before Froyo).

As an aside, I love showing off to my iPhone carrying friends just how much better Froyo/N1 is at, well, anything except games. That's the one place that Android is still lacking. Many of the best games are either crappy ports or pale imitations of iNonsense. Oh well, we're getting there, and I've got my iPad to show off there, and eveything else is just sooooo much better on Android now: text handling, widgets, background downloads and updates, notifications and speed are just untouchable. Even the wholly desirable iPhone 4 is just much, much slower to get things done on.
[Nexus One Android Development] big_adventure:
OK, so I just stepped up to 1113 for tests:

BenchmarkPI - 914-967 (10 tests - my best ever is 910 with FRF50 and a 1113 2.6.34 non-AVS kernel)

Linpack - 41.6 to 42.9 (10 tests with one aberrant 30.6 thrown out)

Neocore - 29.9, 30.1 and 30.0 (3 runs) - not exactly linear scaling (I got 30.0 at 998 this afternoon), but consistent!...

Quadrant - 1666 and 1662 (2 runs - talk about consistent!)

So basically, on my phone, with the BFS kernel, there is almost no "benchmarkable" advantage in going OC.

Just to re-check, I set it back to 998:

BenchmarkPI - 969-1031 (5 tests)

Linpack - 38.302 to 39.664 (5 tests)

Neocore - 29.7 and 29.9 (2 runs)

Quadrant - 1672 and 1652 (2 runs - 1672 is faster than I got OC'd)

And for fun, here is Sunspider at both speeds, plus some other systems:

998: 5607.6ms

1113: 5703.4ms (yep, slower...) (so here's a second run: 5712.2 - still slower!)

iPad (3G 32GB, on WiFi, iPhone OS 3.2): 10415.8ms

iPhone 3GS (iOS4): (first run failed) (second run: 13967.8ms - Apple should be embarrassed)

MacBook Air SSD, 1.86Ghz, Chrome 5.0.375.99, OSX 10.6: 520.0ms

MacBook Air, Firefox 3.6.6, OSX 10.6: 1317.6ms

MacBook Air, Safari 5 (6533.16), OSX 10.6: 433.4ms

MacBook Air, Opera 10.60, OSX 10.6: 532.6ms

MacBook Air, Firefox 4.0 Beta, OSK 10.6: 950.8ms

So again, except for pure CPU activities, I don't see a real reason to OC these days.

Thanks Wildmonks (from my kids - you have saved me time compiling that I can spend with them)
[Nexus One Android Development] AllanJacques:
A quick question, if I use this kernel and do not want to OC, is there a way?

I mean, I would like to use it withou OC...
[Nexus One Android Development] carlost24:
Is there any way of removing a kernel that's already installed
[Nexus One Android Development] SimFox3:
Don't install SetCPU. The internal scheduler will cap the speed at 998Mhz =)

EDIT: Private PM from the Monk himselfffff, WOOT =)

If you uninstalled SetCPU and restart the phone, it will default to ondemand but the min and max is set to 245/998. So its a requirement to have SetCPU to use the 1113 speed. Although you can set your settings in SetCPU and then uninstall it. The setting will be retained until you restart the phone.
[Nexus One Android Development] wildmonks:
Yup, what SF3 said, or rather what I said :p

You can usually flash a new kernel on top of the current one without any problems. If your goal is to go back to stock, that will be a bit harder if you didn't make a nandroid backup to go back to.

Note, if your flashing between different kernels, like between .34 and .35 or between different compiled kernels, like between IR, pershoot, or mine, your module directory will start to accumulate excess modules from previous kernels. There's no straight forward way to clear this directory because it's system protected. I have made an update.zip type file for a user (i forgot who...) to flash that will clear this directory so that user can then make a clean kernel flash. You can find this file here. Remember, this will clear everything in the module directory including the wifi driver so you will have to flash a kernel to get wifi working. (It isn't a requirement to wipe this module directory but it is kind of a waste).
[Nexus One Android Development] waylo:
I had read somewhere that flashing the boot.img from a "stock" CM firmware would also revert to the original kernel? Is that not correct?

Maybe this is just a lesson that everyone should do a nandroid backup before doing any major ROM altering!
[Nexus One Android Development] waylo:
Found the app. Thanks so much. Had heard about this but forgot the name. So much better than attempting to run the android SDK with USB-debugging for a mere screenshot.
[Nexus One Android Development] fitsnugly:
Holy ****, I just banged out a 1727 in quadrant with this kernel :eek::D:eek:
[Nexus One Android Development] AllanJacques:
thanks a lot!!!
[Nexus One Android Development] LordPhong:
I ran into two problems so fast with stock frf91 and the .35 800/925mhz kernel w/o audio mod.

1) after a day the 800mhz kernel completely killed my radio. I had to change the kernel to make it work again.

2) in less than a day I've gotten two sleep of deaths (SOD) with the 925mhz kernel.

Sorry if I'm repeating what someone has already said. I'm on my N1 and there is no search in thread function.
[Nexus One Android Development] zizoty:
I'm getting a lot of touch screen problem in rc4 compared to rc3.
[Nexus One Android Development] mtw4991:
@wildmonks this kernel is extremely fast with every benchmark I've ran plus I've recalibrated my batt according to the batt thread and it is almost PERFECT...11.5 hours into the kernel and still at 74%. batt left....ducking amazing!!!!! Cm 6_A1...oc to 1075

edit: forgot to say its your 0705_925_bfs kernel
[Nexus One Android Development] wildmonks:
There are bound to be some bugs with the .35 kernels since its still a work-in-progress. It can take months before a kernel version is considered stable. I do see that a lot of updates have been made to the .35 source since 070510 but unfortunately I don't have time to compile and release an update today. I'll try to do it tomorrow.

Thanks for the report though. Its good to know (or is it?) that these kernels aren't perfect :p.

So please everyone, make a nandroid backup before kernel flashing.
[Nexus One Android Development] wildmonks:
I think you've become the master at recalibrating batteries :D. One of these days, I'll have the patience to properly recalibrate my battery...
[Nexus One Android Development] mtw4991:
I don't know about the master thing lol but at 20 hrs now and still have 55% left...amazing!
[Nexus One Android Development] mrmarshall428:
Edit: iT'S 2.6.35 rc4, i figured it out sorry for stupid question! What setcpu settings and govenor are you using if any?

Was that using 2.6.34 or 2.6.35 rc4?
[Nexus One Android Development] mtw4991:
2.6.35-rc4_925-BFS left on 1036/245 ondemand, only sleep profile set 245/245-no other profiles used. advanced sampling rate=40000, up threshold=85. I'm now at 23.5 hrs and 41% left with fairly decent usage the last 3 hours, btw.
[Nexus One Android Development] mrmarshall428:
Wow! That's incredible! I'm going to try those settings and see what i get, thanks so much for info! I have 2 more questions is sleep profile on demand or conservative? Do you clear the battery stats on final step of bump charging, I'm in the process of doing that now?
[Nexus One Android Development] mtw4991:
sleep profile is ondemand also...never really used conservative mode.

Yes, I cleared battery stats on the final step then put it back on charger for 30 mins and it maxed out. fyi, 24.5 hrs and 38% left with steady usage for the last couple of hours= 2.77% per hour with 6 hrs overnight sleep. It's impressive, imho.