yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] elborak:
Okay, this is just getting screwy.

Looking at the kernel source for BFS #5, the fixes from HTC from their latest kernel drop (which king incorporated starting with #4) are gone again.

When #4 came out, I noticed that AVS was missing and asked repeatedly in this thread why it was removed. King ignored the question. Then suddenly with #5, weeks later, it's "I've found the problem with AVS in #4!" No kidding! The "problem" was that the code wasn't in the source tree!

And now with #5 you've reverted the HTC fixes that you incorporated into #4. The very changes we had to beat you over the head repeatedly to get you to acknowledge that they existed at all.

I think I'm giving up.
[Droid Incredible Android Development] DroidHam:
So why don't you start releasing kernels?
[Droid Incredible Android Development] smtom:
Help me understand - there's stuff in #5 that was supposed to be in #4, was pulled from #4, and is now in #5?

For my simple brain, the good stuff is in #5 that was supposed to be in #4?
[Droid Incredible Android Development] elborak:
After #3 was released, we asked king if he would consider updating to the newest source from HTC as the basis for his kernels, as he was using an older drop with missing fixes. He claimed there was no newer source. We pointed out that their was, and after some convincing, he acknowledged that there was and adopted that for #4.

However in #4, AVS was dropped without notice. I asked why, several times, and was ignored or overlooked.

Now in #5 he's restored AVS but dropped the fixes from the newer HTC code.

Decide for yourself what's most important.
[Droid Incredible Android Development] smtom:
Thank you for the context, that's helpful.

So, is/are there 'old' versions of #4 floating around that are based on the updated HTC drop, and if so, do/did they perform well? And can we get them?

Asking not to be contrarian, rather to learn and see if the older version of #4 with the more recent basis (HTC drop) are better than the current #5, which, if I understand correctly, doesn't use the most current HTC drop.

Thanks for you input! I'm learning a ton - literally, and implied from what's not directly stated. :)
[Droid Incredible Android Development] adamant13247:
Well #5 seems to be working exceptionally well...what's missing in the fixes for the newer HTC source code?
[Droid Incredible Android Development] roborob1969:
My battery life so far, 65% battery left after 3 hours of continuous use.

SetCPU, uninstalled

No Task Killers installed

Battery bump charge + reset

Quadrant Score" 1,250

RunKeeper (w/GPS On and full screen brightness) for about 20 minutes

Surfing and syncing (4 GMail accounts, Twitter)

I've only used the stock kernel (with SetCPU - No OC) before #5 and so far it seems to have about the same battery life. Should I be getting better life on a 1750 mAh battery, or does this seem about right?

DINC w/Seidio Innocell 1750 mAh Battery

Rom: Skyraider 3.0 vanilla RC 3

Kernel: KiNgxKernel BFS #5

Radio: 2.15.00.09.11

S-OFF Unrevoked forever

LauncherProPlus v0.7.9.0
[Droid Incredible Android Development] elborak:
I'd rather not post a kernel source diff. The differences are the ones noted by King in his changelog for #4:

These are now missing in #5.
[Droid Incredible Android Development] Div033:
By my standards that seems about right. The 1750 is actually a 1500 which is only 15% more capacity than our stock 1300. So around 7-8 hours of continuous use sounds about right.

I have a question for you though as I had an issue with this kernel and am curious if its related to skyraider... In your battery usage, how far ahead is the android system? Its normal for it to be high but like 70-80% isn't normal.

Sent from my Droid Incredible running SkyRaider Vanilla 3.0
[Droid Incredible Android Development] smtom:
Thank you sir. I learned something way important today.

Appreciate your kind input!
[Droid Incredible Android Development] roborob1969:
Thanks for the great info about the battery and reassurance on expected life.

My Android System is at 51% right now...which is actually a lot better than stock, which was at about 80%.
[Droid Incredible Android Development] roby6298:
Tried Re-flashing the BFS #5 kernel. I must be one of those unlucky sonofaguns. After around 21 hours of uptime and 2 hours of google maps on navigation mode (plugged in to cig lighter) (constant screen on) I notice that my navigation is getting choppy.

I check system panel. I notice the phone is super hot and the CPU load and MHZ is pegged.

I LOVE the performance of this kernel. Its effing blazing fast. But somthing is causing the system to go beserk on high uptimes.
[Droid Incredible Android Development] jlss:
Sounds like a memory leak or, most likely, an app misbehaving. You can do a titanium backup and add them back one by one manually until you find the problem, or go to settings/battery/see what's using the battery. If you're lucky you'll find your answer there.
[Droid Incredible Android Development] roby6298:
I checked system panel. None of the apps listed are taking up any significant cpu time. meanwhile the "user" is taking up 98 percent system resources. Odd...

Gonna flash another kernel see if the problem persists.
[Droid Incredible Android Development] oldman_58:
Newer is not necessarily better, my phone seems to run much longer and and faster on #5 kernel.

From a cursory view of the 2 Kernel packages

#5 has 2 more modules:

ext4

jbd2

zimage has the only discernible size difference .1mb

File dates differ #4 are all Sep 10 #5 Sep24

contents of the files may differ significantly without size changes.

If you don't mind me asking, What, in your opinion, is missing that is of vital importance?

Thanks in advance.
[Droid Incredible Android Development] REYES702:
Welp, I would say this is good for constantly having "WIFI" or "Mobile Data Connection" connected. I did a nice bump charge and let it rock and roll til it shut itself down. I played NESOID, SNESOID, surfed the web using Dolphin Browser, synced weather, GMail, twitter and I used ChompSMS as well as run Launcher Pro Plus.

Using a RED 1300 stock HTC battery.

SR 3.2 RC3

SetCPU O/C'd to 1075mhz, turned off all profiles.

"Set on boot" to "Interactive" scaling.

Quadrant ranges from 1249 to high 1500s

Benchmark is 320ms to 360ms in SetCPU.

This screenshot was at 1% right before it died;
[Droid Incredible Android Development] elborak:
Never said anything was missing of "vital importance". Of course nothing added to #5 is of "vital importance" either.

HTC made multiple fixes between the two kernel source drops. The one king is using in #5 is from one of the earlier 2.2 leaks. Differences between that and the final 2.2 kernel are fixes to ptrace, the DMA code, the SD card driver, low memory handler, USB mass storage buffer counts, and the USB controller driver.

Again, it's up to you whether the loss of these fixes is sufficient to dissuade you from moving to #5. I'm not trying to discourage anyone, just inform them. What I'd really like is for King to restore the fixes. I'm 99% sure he didn't drop them on purpose, but simply screwed up the merging of his branches.

Of couse he ignored me when I repeatedly asked why AVS was dropped from #4, so he may well ignore me again. All I can do is try.
[Droid Incredible Android Development] kingklick:
who said havs was dropped in #4....

AND who said the updated code is not in #5.....

???

You are confusing the crap out of everyone
[Droid Incredible Android Development] oldman_58:
You can use other kernels if this one does not fill your needs, From my, perspective and looks like a majority here on the forum agree, #5 is an improvement over #4.

Just my 2 cents
[Droid Incredible Android Development] smtom:
Agree. I've tried to break #5, can't. Thus far, it's stable, fast, and way improved my battery life. I'm yet to encounter previously endured lag or f/c that I did in #4.
[Droid Incredible Android Development] jumperalex:
Running #5, SetCPU not installed, 60 hours and I woke up to a HOT and SLOW phone. Reboot fixed the problem and now I'm putting Hydra back ... again [sigh]
[Droid Incredible Android Development] Masterpiece Finishes:
My battery started dropping super fast after installing #5. I did not wipe anything before install. Should I wipe dalvik?
[Droid Incredible Android Development] gmichaelow:
Yes. Are you OCed?
[Droid Incredible Android Development] Masterpiece Finishes:
I wasn't when I tested it yesterday. With #3 & #4 I would only lose 10-15% in my first 3 hours of work listening to mp3's . I lost about 25% in the same amount of time with # 5.
[Droid Incredible Android Development] elborak:
King,

I am. And I'm basing this on your github repository.

I've downloaded your source from github. The updated code from the latest HTC kernel is not in the kernel source. So unless you're posting kernels compiled from a different souce tree than your github repository, kernel #5 doesn't have the updated code.

Just like when we had to argue with you that there was a new kernel drop from HTC (which you vehemently denied existed), did you actually look to see if you'd dropped the fixes, or did you just assume you must be right and I must be wrong?

Let's make this simple. Look at drivers/staging/android/lowmemorykiller.c. Is there a definition of dump_deathpending? If not, you have the old kernel source.
[Droid Incredible Android Development] ejdavis72:
60 hours!

So you're complaining about 60 hours?!?!? If I get a day and a half out of mine I'm LUCKY! Even if I had to reset my phone at 48 hours it would be SOOOOO much better than what I'm getting now. Dude, seriously.
[Droid Incredible Android Development] csseale:
To be honest...maybe they don't matter, and if the kernel works flawlessly then fixes are irrelevant. If I bought a car and installed a new radio and then the next month that car came out with an updated radio to get hd stations but my radio already did that why would I rebuy the car just to install my radio again....I am no dev. At all I just trust the ones that are and so far this kernel is superior to htcs kernel so even if they were left out or not it doesn't matter. And if your so good at pulling kernels apart y not make Ur own instead of telling someone what they should do with theirs.

Cory

"Results may vary."
[Droid Incredible Android Development] jumperalex:
[sigh] no I'm complaining about getting only 60 hours of UPTIME, not battery time before a reboot is needed.

My phone was plugged in overnight and that is what I woke up to. I should have suspected something was up. When I went to bed the battery was much lower than I would have thought it should be given that it was plugged in at my desk for a while, then unplugged for about an hour while I puttered around the house before going to bed. My guess is, the "troubles" started before I went to bed and started to suck the battery down in that hour. I then woke up to a very hot and very slow phone.

For what it is worth I did seem to be getting great (but only anecdotally) battery life for the preceding two days. Though honestly I can't say for sure it is any better than what I get out of Hydra undervolt [shrug].
[Droid Incredible Android Development] zeke1988:
did you reset the awake time, reboot, before testing? because awake time will keep stacking day by day.
[Droid Incredible Android Development] jumperalex:
Where would a person looking to get their hands on this new stock kernel go to get it? And is the Hydra Undervolt based on that kernel?
[Droid Incredible Android Development] ardax:
1. Install a stock Froyo ROM. :p

2. ejhart hasn't updated his kernels, and has already announced that he's not going to. If you want an undervolted kernel from the newest source, it's King's or adrynalyne's.
[Droid Incredible Android Development] Staticaxe:
Flashed KK#5 last night with SR Vanilla 3.2, and took OFF SetCPU based on reading some posts here. Have to say I am a bit disappointed in the battery life today. Seems like it was much better with BFS #1.

Going to throw SetCPU back on the way I had it and give #5 some more time, but may be going back to #1!
[Droid Incredible Android Development] adamant13247:
Not going to lie bub, but I love this #5 kernel more than any other kernel and I don't care if he compiled a bunch of different modules from hundreds of different source codes, it rocks!
[Droid Incredible Android Development] jumperalex:
I'm trying to avoid flashing the entire ROM. Or am I able to do that without clearing everything and losing all my settings. I have TiBU but honestly haven't used it to recover things like my Sense setup (I HATE having to redo all my icons etc)

I found Virtuouses stock Kernel ... from all I can tell I can use that right?

Is Adrynalyne's compatible with the stock ROM? Honestly I just haven't found any of the ROM's to be compelling. I guess I just like the stock Sense UI and removed the apps I didn't like on my own [shrug]

This is of course getting OT ... sorry about that. Perhaps PM me so we don't hijack King's thread.

King, thanks for all your work here, I will keep checking back as new versions come out. But I just seem to always be running into slowdown issues even when not using setcpu or frankly doing anything "special". I'm really quite a boring user in that regard yet I still have uptime problems [shrug]
[Droid Incredible Android Development] REYES702:
It resets everytime you reboot. I liked to charge my phone while it's off because I feel it's most efficient that way. So once green I bump charge anywhere from 6-10 times and turn it on and never plug it in to recharge or anything. So far I have done this twice and gotten around the same up/awake time. I think my uptime was a little more but my awake time was a little less last time. Today is my third and final test before I decide if I am going to keep this kernal or reflash my #4 with my SetCPU settings. As it stands right now the way I use my phone has changed since I used to use #2 and #4 wasn't doing that great. #5 seems to be stable, with decent battery life. I plan to buy the Verizon 2150 extended battery in the near future and I hope to get 1.5-2days of uptime with double the awake time. Then I would be set!

So far on the 3rd and final test I am at 1:48 uptime and 25:30 awake time and battery is at 91%

Just another clarification that my Quandrant scores have been pretty consistent too. I just did one and it was 1369.
[Droid Incredible Android Development] kingklick:
LOL

don't look at my master branch and try telling me my code is off -.-

I have 5 branches of code on my github for the inc, and I haven't heard you say anything about which branch you are even speaking of....

EDIT: just triple checked my code per your request, and that definition IS in there. So like I said before, #5 has the latest code in it..........
[Droid Incredible Android Development] Dmtalon:
Had to reboot my phone this morning... system was 100% CPU and the phone was unusable on #5 :-( Last night I was at 22h 'uptime' and like 9' awake time when I went to bed, this morning it happened around 9:30am so, FAR short of 20h awake unless something happened last night when I went to bed.
[Droid Incredible Android Development] elborak:
If I've misrepresented you, you have my apology.

Which branch are you using to build the BFS/HAVS kernel?
[Droid Incredible Android Development] SLOflatlander:
yes huge for me. im running 1113 max on aiccucs rom. i think profiles in set cpu really help with this as well
[Droid Incredible Android Development] Omniel:
Yea there is a difference, better than hydra for me.
[Droid Incredible Android Development] jredecop:
Ok I'm a little confused. I downloaded over clock widget so do I NEED this to make the kernel over clock or does this just let me see what the speed is?
[Droid Incredible Android Development] Berzerker7:
Would it be possible to make a 25mv overvolt version of #2? My phone is not completely stable at 1.19 with stock voltage, 25mv overvolt would definitely help.
[Droid Incredible Android Development] seanzer:
I suggest you read more about this kernel.. I don't think its at stock voltages..
[Droid Incredible Android Development] Berzerker7:
There's nothing that suggests this does not run at stock voltages. No undervoltes, no overvolts. What makes you think that?
[Droid Incredible Android Development] kingklick:
He knows how to read a changelog ;)
[Droid Incredible Android Development] Reddog80p:
The thread title says "[OC],[UV]"...
[Droid Incredible Android Development] Berzerker7:
Well there's your problem. Why would you undervolt the kernel while overclocking it past where most phones max out on clock support?
[Droid Incredible Android Development] androidmylife:
market issue

I am having a problem loading the market place. It keeps giving me a server error when trying to load app listing.
[Droid Incredible Android Development] kingklick:
/sigh

The oc'ed frequencies are not undervolted
[Droid Incredible Android Development] Berzerker7:
Many phones still aren't very stable on OC frequencies with stock voltage. That's why I suggested something like a 25 mV OV.
[Droid Incredible Android Development] Reddog80p:
Yeah me too. Thats the only thing I did not try.
[Droid Incredible Android Development] s197:
delete (10 char)
[Droid Incredible Android Development] Berzerker7:
http://hydrakernel.cz.cc/

Overclocked kernels #2 and #4 have a 25mv overvolt option. Adds much needed stability to phones that don't do well overclocked on stock voltage. Also, like king said, overclocked frequencies even without the overvolt are not undervolted.
[Droid Incredible Android Development] wakeboard143:
Having Market connection issues as well on kernel #2.
[Droid Incredible Android Development] Berzerker7:
Add me to that list, as well.
[Droid Incredible Android Development] Muerte_X:
#2 seems pretty stable up to 1113Mhz for me. I can do 1152, but it'll eventually freeze or reboot. 1190 won't last very long at all. That's ok though, I'm happy with 1113 or even the stock voltage.

I noticed the conservative governor using setCPU doesn't work right. It'll just stick at whatever clock speed the cpu was at while you selected it. When the phone boots it's stuck at 998Mhz, I can actually turn the max all the way up to 1190 and nothing will change. If i watch the "Time in state" under the info tab in Setcpu, this confirms it.

On demand seems to work fine, Time in state shows time in all the various clock speeds. Powersave just bottoms out the clock speed at the min setting, which I guess it's supposed to do. I'm using the most current version of SetCPU (2.0.2)
[Droid Incredible Android Development] s197:
I understand what you're asking for, I don't really know why some phones need the overvolt and some don't. I could run the hydra 1.15ghz with no overvolt with zero problems.

But isn't the objective of this kernel to improve the battery life? To me, the overclock is just gravy. If it's unstable at 1.9, scale it back to 1.15 or whatever works for you.
[Droid Incredible Android Development] androidmylife:
it doesnt seem to be the kernel. I reverted back to stock kernel and I am still having problem connecting to market place. seems like an issue. Can non rooted DI try to access their market place and see what happens?
[Droid Incredible Android Development] setexascustoms:
Well my experience with #5 has all been good. I've tried Hydra and a couple King's previous kernels, and I think I'll be on #5 until something new and exciting comes out. Thanks King.
[Droid Incredible Android Development] wrightrocket:
Anyone having any luck trying to get bootaudio.mp3 or VZW_bootaudio.mp3 to work? I tried using both file names in /system/customize/resource without success.
[Droid Incredible Android Development] mikesincredible:
Try android_audio.mp3 or VZW_Droid.mp3

If that still dont work, put the above file in /system/media
[Droid Incredible Android Development] kingklick:
Haha not a problem man was just almost confused myself for a second.

I am working off my test branch and havs-bfs branch

those who follow my evolution work already know but I have patched us up to. 32.17 ! :)
[Droid Incredible Android Development] northernlights:
Working great - thanks so much for the hard work!
[Droid Incredible Android Development] elborak:
Thanks for the info. I have to tell you, though, I'm still confused.

The lowmemorykiller.c file update contains a couple of strings with the text "deathpending" added. After unpacking the zImage and decompressing, these strings are clearly visible in the stock Froyo kernel image, as well as Adrynalyne's redemption kernels. They're missing from yours.

Any idea why?
[Droid Incredible Android Development] ncwildcat:
King

Is the #3 kernal the final CFS kernal you plan on doing? I am a big HAVS fan, but I think that CFS is better than BFS for multitasking. The BFS benchmarks are great, but multitasking is the bread and butter of android, imho.

Thanks for the great work!

Sent from my personal space
[Droid Incredible Android Development] kingklick:
not really too sure or concerned at this point.

perhaps I left it out accidentally in the final product, pre-compile?

"If it ain't broken, why fix it"

:)
[Droid Incredible Android Development] adamant13247:
Y

Amen! lol My battery life rocks but it seems that the most battery is eaten by my 3g web browsing, I hardly get more than 4 hrs of awake time on my 1500 htc battery when I periodically use the internet...any idea why?
[Droid Incredible Android Development] staticx57:
How is the signal in your area?
[Droid Incredible Android Development] Hand76:
Well at about 60 hours up time (on number 5) my cpu jumped to 100% and the phone was sluggish again till I went in to setcpu and exited out.

Might uninstall setcpu to see if that fixes the problem but sucks I can't control when i want to o/c.
[Droid Incredible Android Development] muaddib20:
@ hand

What Rom are you using ?
[Droid Incredible Android Development] adamant13247:
Signal's always good in my area so I don't think it's that. I should just be gettin more awake time! :/
[Droid Incredible Android Development] kingklick:
New kernel cfs coming.

Pulling code from my evolution, its getting awesome feedback :)

Stay tuned
[Droid Incredible Android Development] xtmo22x:
Ok I'm running the uncommon sense rom and I tried to flash a Hydra overclock and kings #5 kernel but it said installation aborted for both in recovery. Any idea why?
[Droid Incredible Android Development] ogkhaze:
What's the difference between "BFS" and "CFS" ?

:P
[Droid Incredible Android Development] ncwildcat:
Hells yea!! Thanks king looking forward to it!

Sent from my personal space
[Droid Incredible Android Development] jbh00jh:
Did you wipe Dalvik Cache and Battery stats ? ? :)
[Droid Incredible Android Development] smtom:
Couple other ideas - before flashing, see if you can look at/bring up @ the kernel(s) in Astro or another file manager - not open them, just see if Astro recognizes them. If you cannot, they may be corrupted and likely need to be d/l again. I raise that only in that both failed.

Also, you may try wiping cache partition as well. Let us know what works, and whether this still fails.
[Droid Incredible Android Development] xtmo22x:
Ok ill be doing this shortly....
[Droid Incredible Android Development] Killa200:
Not sure if i have missed something within the 180 pages of posts about this kernel, but it is giving me fits. Ever since i have loaded this the phone is taking 3x longer to boot, and bogs down to the point to where you think it has locked up in random intervals.

I'm running:

Android 2.2 (8.1 fix)

Baseband: 2.15.00.07.28

Kernel: KingKernel BFS #3

Rom: Aiccucs 2.2 Lite Version 4.2

Have SetCPU configured never to throttle speeds due to this, and also cleared normal cache and Dalvik cache, with no success at fixing the issue.
[Droid Incredible Android Development] jbh00jh:
I had some of the same problems with #3 , upgraded to #5 and all the problems went away. :)
[Droid Incredible Android Development] Killa200:
Shall try real quick, as i really like this kernel's featureset
[Droid Incredible Android Development] michaelnhf:
#3 had a different stock scheduler which is y it probably is giving u issues u can check set CPU.