yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] Panda Fuzz:
I also ran into another issue with this kernel and the Camera. All of a sudden the Camera just stopped working. Reboots would not fix it. I had to completely power down, then power back up to get it to work again.

EDIT: Forgot to mention that for whatever reason power control was unable to turn on and off the wifi. It would just hang.
[Droid Incredible Android Development] ToyTank:
Do you use an app that reports battery voltage? Use Battery Snap(or pull battery test w/ voltmeter) or something similar.. ~4.2V is 100% ~3.5V is 0% FOR OUR PHONE.
[Droid Incredible Android Development] execute_method:
No, I don't use an app for it, I was going by the Notification bar and BattStat. The point I was trying to make is that while I did not get out my meter and check the voltage, there was no way that the battery was 1%, because when I flashed back to the nandroid I did before the kernel update, it was again close to where it had left off. As a matter of fact, I just put it on the charger @ 10% remaining.

^ I may have misinterpreted you reply.

I'll check out that Battery Snap app. Thanks.
[Droid Incredible Android Development] execute_method:
Wow, battery snap is pretty sweet.

Sent from my "girlfriend"... According to my wife.
[Droid Incredible Android Development] DarkMattr:
lol!!
[Droid Incredible Android Development] bhazard451:
I think this kernel is either undervolted a little too much causing slowdown, or there is something up with the BFS330 patch. I had to revert back to #1 as well.
[Droid Incredible Android Development] s197:
If I had to guess, it would be the latter. Undervolting too much doesn't account for the very bad battery life.
[Droid Incredible Android Development] kingklick:
all of this makes me realize it is time for a CFS kernel with all the new code :)

bear with me, you will have it soon
[Droid Incredible Android Development] gmichaelow:
Yay yay yay! CFS seems to be a little less "wonky" with the scheduling.

Hmm, perhaps them lowered charging temps you promised as well? :D

My phone charging + me using is HOT HOT HOT. Like 112 F or higher to the point where I can't even handle my phone at all while it's charging.
[Droid Incredible Android Development] Ty07allstar:
Just tried out the #2 kernel and I too had a reboot within two hours of flashing with wifi on and the charger plugged in. Reverted back to #1 for now.
[Droid Incredible Android Development] s197:
Thanks for the update! Any chance wireless tether might work with the new CFS kernel?
[Droid Incredible Android Development] kingklick:
tethering has been said to work. You just need the right app :)
[Droid Incredible Android Development] s197:
For the AOSP kernels? I've yet to hear anyone say it's working for them...

I can get it to work on all the other kernel's (adrynalyne, koush, stock) so I don't think it's the app.
[Droid Incredible Android Development] ejdavis72:
I haven't ran into any of these issues everyone is talking about at all. My camera works just fine, no battery drain, no random reboots, WIFI works just fine. I'm using Token

Cricket Incredible Rom and everything works just fine with this kernel.
[Droid Incredible Android Development] iflip:
Any reports if this working with miui rom??
[Droid Incredible Android Development] rynosaur:
It works pretty well with MIUI, yes.
[Droid Incredible Android Development] whewstoosae:
+1
[Droid Incredible Android Development] GMK83:
This is true with everyone else's kernel. But yours. Tethering is not working.
[Droid Incredible Android Development] killer2239:
Did a quick search and didnt really find what i was wanting. Do you need to install setcpu to handle any of the clocking or whatever, or will the kernel do everything for you without setcpu?
[Droid Incredible Android Development] GMK83:
Kernel will not overclock for you. It's set to the default 998 out of the box
[Droid Incredible Android Development] ardax:
^^^ What GMK83 said. Just don't create any profiles.
[Droid Incredible Android Development] andrew53517:
Why? I though profiles helped save battery life?

Droid Incredible Rooted!
[Droid Incredible Android Development] baram:
e: didn't read and my issue seems to be a common one with v2 of the kernel.
[Droid Incredible Android Development] ardax:
Because changing the min/max clocks (and maybe the CPU governor) interferes with HAVS, according to kingxclick.
[Droid Incredible Android Development] Ianxcom:
So far i get better benchmarks with #1 and it just seems more smooth. Thats not saying this one is bad, it just seems performance is better on the first kernel.

Now as far as battery life goes ill have to report back.
[Droid Incredible Android Development] killer2239:
I installed #2 on the nightly 9/29 cm and my battery life went to ****. Dropping like crazy. Just installed #1 but im in the process of recharging the battery back up to see if its better. Iv been using a new nightly every couple days with great life overall. Need to use a kernel with vpn support so i installed #2 and disappointed with battery. hope #1 is better.
[Droid Incredible Android Development] andrew53517:
Gotcha. So delete my profiles but keep my max and min on the front so I can still overclock? Or just don't use it at all?

Droid Incredible Rooted!
[Droid Incredible Android Development] ardax:
Exactly. If you want to overclock or change governors, do that.
[Droid Incredible Android Development] andrew53517:
Okay thanks! Doing that now.. hopefully that helps with the poor battery life I was getting.

Droid Incredible Rooted!
[Droid Incredible Android Development] Ty07allstar:
King, will you be updating #2 or will you go straight to #3? Also will you be making a CFS kernel too? Keep up the great work! :)
[Droid Incredible Android Development] kingklick:
Update coming very soon

CFS

:D
[Droid Incredible Android Development] Ianxcom:
Im VERY interested to see how this one preforms.

About 3 weeks ago it was all the rage to flash the BFS kernel. Maybe cuz it was new or whatever but it seemed to do very well.

Im curious what would be the advantage of going back to CFS using this new source?
[Droid Incredible Android Development] kingklick:
You will see my friend :)

I patched up your guys kernel to 2.6.32.21

:D
[Droid Incredible Android Development] kingklick:
new kernel is live!

read changelog
[Droid Incredible Android Development] DroidHam:
Can I use this with Redemption ROM? Whats the diff between #5 im using now?
[Droid Incredible Android Development] DroidHam:
Flashed this over #5 using RedemptionRom and it killed my battery =\

Flashed back to 5...
[Droid Incredible Android Development] dnoyeb:
This is for aosp rom's bud.
[Droid Incredible Android Development] DroidHam:
ah ok, maybe thats why :)
[Droid Incredible Android Development] Ty07allstar:
Did you update #2 or is the CFS the only new one? Will give it a try. Thanks!
[Droid Incredible Android Development] Asterdroid:
CFS is the new one. I'm seeing improved battery life so far. Performance is not as good, according to Quadrant, but I don't see a decrease. Happy with it so far even though my quadrant-peen shrank.
[Droid Incredible Android Development] Ty07allstar:
I just flashed the CFS. I wonder why the performance has dropped significantly with these two new kernels?
[Droid Incredible Android Development] luniz7:
Where is the new one?
[Droid Incredible Android Development] Ty07allstar:
In the OP. It doesn't seem that the quad scores are that bad. I got 1500 with no oc which isn't too bad.
[Droid Incredible Android Development] ncwildcat:
I think that the BFS kernals give a higher quadrant score, due to the way they process. CFS is better for multitasking from what I understand, so although the quadrant may be lower the overall performance should be better. I may be wrong here, but that is the way I understand the schedueling

Sent from my personal space
[Droid Incredible Android Development] larsrya8:
And better for stability. There's a reason Cyanogen moved away from BFS last year.

I wonder how long it'll take before HAVS is removed from this kernel... it's already interfering with SetCPU. The HAVS "benefits" sound like they should be read to me by a snake-oil salesman. :p
[Droid Incredible Android Development] ToyTank:
My limited read on Wikipedia suggests BFS has less overhead compared to CFS, which uses a complex algorithm.

They must have moved away from it pretty quickly. BFS was created august 2009 according to Wikipedia.

I am an idiot and do not understand this stuff, still a good read:confused:.
[Droid Incredible Android Development] s197:
Anyone test to see if wireless tether is working with the new kernel?
[Droid Incredible Android Development] Ianxcom:
First runs with CFS at 998: 1355 1482

First runs with CFS at 1113: 1635 1607

Not bad, feels just as smooth with great benchmarks. Battery life will be the dealbreaker for me when i test it out.
[Droid Incredible Android Development] Ty07allstar:
Does not work.
[Droid Incredible Android Development] larsrya8:
Doesn't matter if it's simple, it starves background processes which can lead to instability.

It appears they did move away quickly. Tweet from early September 2009 that it was added, bug report from mid-September 2009, and a tweet from October 2009 that it was being removed.
[Droid Incredible Android Development] Dat108Kat:
I am running MIUI and was wondering if the new CFS kernel will work for it? This Rom is AOSP so I'm guessing it should. Please let me know
[Droid Incredible Android Development] Ianxcom:
Yes it works just fine
[Droid Incredible Android Development] whewstoosae:
Not working for me. Built-in or the tether app.
[Droid Incredible Android Development] neotericpiguy:
Have you used the wifi tether 2.0.2? I have wifi tether working with CFS#1. I start up wifi tether from the phone, iwlist eth1 and make sure it is broadcasting and connect to it in ad-hoc mode and dhcpcd usually spits some junk at me and tells me i'm connected. Right now, ipchicken.com is telling me that I have a .vzw.com ip so I'm sure i'm not connected to my home WAN.

I think 2.0.2 is from the market and it worked for both BFS#2 and CFS #1. Someone please confirm because I'm pretty sure I'm not tripping balls.
[Droid Incredible Android Development] kingklick:
I am not sure but that sounds right

I know FOR A FACT tethering works, you just need the correct app

:D
[Droid Incredible Android Development] larsrya8:
So, you're marking the "Built-in Android tethering doesn't work with your kernel" bug as WontFix? ;)
[Droid Incredible Android Development] Ang3lmack:
Instructions, create android.tether folder on root of sd card and drop this file into it http://www.mediafire.com/?nh7spjjb46fzfww then install this version of wifi tether http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_2.apk , I take no credit for the fix, just copied from another thread

Incredible
[Droid Incredible Android Development] kingklick:
placed this quote in the OP

Thank you very much
[Droid Incredible Android Development] Ang3lmack:
And it should work with any of your kernels

Incredible
[Droid Incredible Android Development] baram:
got an issue. running the latest cm nightly #95, s-off and all that jazz. using the new cfs kernel and the #1 if i try overclocking above 1.113ghz it causes my phone to be super unstable. the last couple times i tried clocking to 1.15ghz it cause my phone to run into a boot loop. any idea what would be causing this?
[Droid Incredible Android Development] slorange:
I keep getting 'download unsuccessful'
[Droid Incredible Android Development] Ang3lmack:
Does it say because it isn't compatible or something similar? If so do about:debug go to settings, uastring and set to desktop

Incredible
[Droid Incredible Android Development] julesism:
for me, setcpu does not play nice with the new CFS kernel. I have the main profile set to conservative with a max of 998 and a min of 245 but the clock speed gets stuck only when the profile changes, for example I plug in which changes the profile. I uninstalled setcpu and reinstalled and re-did the profiles but it got stuck again. I roll back to BFS #1 and things are happy. I can plug and unplug and the profile\speeds change and behave.

I'm running CM 6 build #95 with setcpu 2.0.2 back on BFS #1 for now.

FYI - the wireless tether fix posted earlier works on the old kernel
[Droid Incredible Android Development] slorange:
If I press the message in the notification bar it does say something about 'not supported on your device' so you're probably on the right track. That said, I have no idea how to do what you advised.:-\
[Droid Incredible Android Development] Ang3lmack:
Go to browser in address type in about:debug click menu go to settings go to the bottom click uastring then press desktop

Incredible
[Droid Incredible Android Development] kingklick:
Do not get the infatuation with set cpu :confused::confused::confused:

there are so many other good apps, such as overclock widget. MUCH better and simple
[Droid Incredible Android Development] whewstoosae:
My only infatuation is with the profiles I guess. Other than that it's a great app in general.
[Droid Incredible Android Development] julesism:
no infatuation... i just wanted to know if anyone else was having simular problems with setcpu and the new kernel so i provided as much info as possible. i have no interest in overclocking.
[Droid Incredible Android Development] ncwildcat:
What is the consenus on these kernals with respect to batt life? I am searching for great batt life. Running stock ruby kernal I run very smooth but batt is not so good. Adrynalyne's battery AOSP kernel seems a bit laggy. I would think a CFS kernal would be the best on battery, but I could be wrong

Sent from my personal space
[Droid Incredible Android Development] HurricaneStiz:
I experienced TERRIBLE battery life with this kernel. I went back to the alternate CM6 kernel and battery went back to normal.
[Droid Incredible Android Development] shoman24v:
Kernel 2 is still broken. Sucks battery life like no other. Would recommend it to be taken off again.
[Droid Incredible Android Development] Ianxcom:
CFS kernel OC to 1.113 no profiles minimal bump charge of 15-20 min on 1500 mah battery.

Uptime 13:30 hrs with 30% left. I was at work with NO service, which is known to hurt battery life. Granted it was minimal usage with occational texting and some xda app, Usually i get 8-10 hrs at work before my phone dies.

Tomorrow night i will try it with screen off profile and see if there is a difference.
[Droid Incredible Android Development] ncwildcat:
I also experienced this. Tried CFS also and just killed my battery. Went to Koush Inc-Test2, battery life better again.
[Droid Incredible Android Development] execute_method:
I'm now using cfs 1, with overclock widget. I couldn't get 1152 stable with setcpu. So far it's stable using overclock widget.

Sent from my "girlfriend"... According to my wife.
[Droid Incredible Android Development] slorange:
Thanks!!!!
[Droid Incredible Android Development] raptir:
I love the performance boost of these kernels, but they all really hurt my battery life. Maybe I'll switch back to one of these if I ever get an extended battery.
[Droid Incredible Android Development] execute_method:
Well got a reboot on 1152, so back to 1113

Sent from my "girlfriend"... According to my wife.
[Droid Incredible Android Development] blakeem:
I have been using #2 on ShadowRom and I've noticed with your kernel the browser sometimes hangs. Maybe ads redirecting to localhost is the issue? I disabled the built in ad block and still had the issue so maybe not. I have been using engadget.com home page as a test because it does it every time. It hangs and gives me that message to wait, force close, etc. I wait and the page will come up eventually but it takes a long time and everything else is frozen.

I have tested this with all the different clock speeds and scaling settings and I only have the issue after installing your kernel. I haven't been able to repeat this issue with the stock kernel.

Your kernel is much faster so this is a bummer. It's not a big deal but I figured you would be the one that might know an easy fix.
[Droid Incredible Android Development] Ianxcom:
This time i tested the kernel with the screenoff profile and a full bump charge, which was abpout 5-10 mins more than the first test. The same situation and usage applies.

20:50 hrs with 34% left

Color me impressed.
[Droid Incredible Android Development] Archangel:
I hate to sound ungrateful but someone has to be able to say that # whatever kernel is better then # whatever kernel,,,these have been out for a while. Now i know that they all can be different for each user, but there has to be a general consensus on battery life and stability one one vice another????
[Droid Incredible Android Development] ncwildcat:
I can say for certain that every king kernal I have personally run (aosp branch) has has bad battery lift. BFS# 1 had the best of the 3, but they were all bad.

Sent from my personal space
[Droid Incredible Android Development] Archangel:
Thank you for some insight!!!
[Droid Incredible Android Development] ktownhero:
King,

I don't wanna use an app for wireless tether, I wanna use the cm6 built in AP mode. This way I can rest assured I wont end up with some crazy bill from Verizon.
[Droid Incredible Android Development] kingklick:
it's 'insight' but not fair news

there have been PLENTY of users reporting excellent battery life with my kernels

Its that new leaked radio scewing everything up....

Make your own decision :)
[Droid Incredible Android Development] kingklick:
thank you very much for this :D
[Droid Incredible Android Development] ncwildcat:
I am not knocking you king. I got great batt life out of BFS# 1 when I ran sense roms. I am not running the leak radio either. I have been trying lots of different combos recently. If you don't have an incredible then how do you test? It looks like there are plenty who agree with me on the board. I would love for your kernels to get better batt life, they are overclockable and run nicely. I just need more than 5 hours out of my device

Sent from my personal space
[Droid Incredible Android Development] nfiniti9:
Well so far I have to say excellent work on the new CFS #1. I have gotten the best battery life I have ever gotten from any rom/kernel combo.\

Running AOSP CFS #1, CM6 #96, 7.28 radio
[Droid Incredible Android Development] Ty07allstar:
What is your screen on time? Looks like you hardly even used your phone.
[Droid Incredible Android Development] ncwildcat:
Since I am off work today, I am going to run CFS#1 and see how it goes. I like the overall feel of the kernel, just want to get some decent batt life out of it. For this test today, I uninstalled setcpu. I went into GEM settings (running Ruby 1.1.1) and turned on the conservative profile. Min = 245, Max = 1113

Running the 2.15..7.28 radio (froyo released, not leaked). Will report back results this evening. Also, I have the 1750 Seido Battery
[Droid Incredible Android Development] nfiniti9:
Just over 3 hours. It's definitely not a heavy day for me but still I wouldn't normally be above 20-30 at that point.
[Droid Incredible Android Development] ncwildcat:
So I ran from 100% to 35% in 5 hours. Heavier than normal usage, but not by a lot. Turned phone off, did a full charge with 2 bumps, and let it try again. At 28% now. This kernal is very quick, no lag I can see, but the battery just does not like it. Maybe the fixes king talked about in his tweet will help

Sent from my personal space
[Droid Incredible Android Development] whewstoosae:
Are you guys wiping dalvik on each kernel install? I usually do but lately when I'm in recovery it says something like "can't mount e:\...file exists" after selecting wipe dalvik. It gives that error, but after I select the option it states that the wipe was successful. Anyone experiencing the same thing?
[Droid Incredible Android Development] ruggar:
Yes I am. No clue if the wipe actually is succeeds or not.
[Droid Incredible Android Development] whewstoosae:
Glad I'm not the only one. Is this good or bad?
[Droid Incredible Android Development] blakeem:
An update about my issues before. I switched to the CFS kernel on shadowrom and this seems to run great so far without the strange hanging issue.

There might be something conflicting in the BFS kernel that makes shadowrom not play nice. I haven't had any of these issues when trying the kernel on ruby or CM.
[Droid Incredible Android Development] jtcarnes:
Yup, noticed it yesterday when I switched kernels. I reflashed ClockworkMod and still have the issue. The message reads "E:Can't mount /dev/block/mmcblk1p2 (File exists)". Then I tell it to wipe and it says it did, but it takes NO time at all.
[Droid Incredible Android Development] whewstoosae:
I asked koush about it on twitter.

ClockworkMod: @whewstoosae That's fine. It's a benign error.
[Droid Incredible Android Development] Ty07allstar:
Any progress on the CFS kernel King?
[Droid Incredible Android Development] Pons:
Generally means improper formatting of the SD card. Try formatting it with the alternate recovery, with SD-ext being 512mb, swap of about 32, and the rest as FAT32. Cleared up the error for me.
[Droid Incredible Android Development] Ty07allstar:
What is the purpose of setting up an SD-ext and a swap?
[Droid Incredible Android Development] Pons:
I'm not an expert on this, so someone correct me if I'm wrong. SD-ext is for apps2sd and swap is something similar to a pagefile for Linux.
[Droid Incredible Android Development] larsrya8:
My understanding is that the dalvik cache lives in /cache. The "delay" that you notice when wiping /data and /cache is because those partitions must be mounted first.

If you have already wiped /cache, recovery will try to mount it (again) to wipe it, but since it's already mounted you'll get the error. It will then erase it, but it's already been erased.

You can "tell if it worked" because the phone will take longer to boot as it rebuilds the dalvik cache.

So yeah, it's a benign error.
[Droid Incredible Android Development] setexascustoms:
Thanks for the explaination, I've been curious about this as well.
[Droid Incredible Android Development] Pons:
That doesn't add up to me. I've tried that scenario with my properly formatted SD card and no errors. I'm not arguing that it's benign, just the details. Mainly because I'm bored. I'd do some research on it, but I'm also tipsy and I don't trust myself in that regard.

Edit: Alright, some more details since I can think clearly again. I've tried both of these scenarios with SD with only FAT32, and one with an additional SD-ext partition. Reboot into recovery, make sure everything is mounted, clear dalvik. Reboot phone into ROM, back to recovery, make sure everything is unmounted, clear davlik. Both times I get an error with the pure FAT32, and not with the other. From research, (and according to this http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/ ) the popular consensus is that spot act as a pointer for apps2sd which uses SD-ext partition. The error seems to be that file doesn't exist (I've also looked for it manually via adb sell and ES File Explorer) when you skip partitioning. When partitioned, I can find that file easily with ES.
[Droid Incredible Android Development] AndrewGL:
king- do you think we could get MD5 sums for the kernels?

Thanks for all the hard work! :)
[Droid Incredible Android Development] ZonicTH:
Hey, thanks for the kernals. While I haven't gotten better battery life (infact, it's a bit worse :P), I've gotten a stable overclock on MIUI, so thank you.

I was just wondering if you could include the five point multitouch like on your Evo kernals.
[Droid Incredible Android Development] whewstoosae:
Do you use Set CPU? I get great battery life with the CFS kernel and a screen off profile. Definitely helps.
[Droid Incredible Android Development] ZonicTH:
No, what's your average battery life per day? (With bump charge?)

I'm at 40-50% after 8 hours on Koush's test kernal, usually at 20 when on this one.