yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] najaboy:
Apparently your reading comprehension and critical thinking skills aren't quite up to par.
[Droid Incredible Android Development] xFlawless11x:
He never stated that he was getting an Incredible. I'm just glad he's willing to develope for others benefit.

He's put out some awesome kernels for the Inc, and I have no problem donating for whatever he chooses to buy.

-Flawless
[Droid Incredible Android Development] jlss:
I think it's easy to overlook the basics when evaluating battery life. Let's use my experience today.

I was off-charger for 10 hours. Of those 10, 8 were spent with the phone asleep while I was in training. My awake time is 3:22, only because I was checking mail after my laptop died.

I just plugged in with only 53% remaining. Which is far, far below where I typically run, and with less than 1/2 the awake time of today.

So what happened? Cell standby. I was in a conference room with terrible cell reception which, in turn, chewed up my battery. Tomorrow I'll turn on WiFi for comparison.

King's kernels are terrific - they're by far the best I've used - but neither king nor I can boost VZW's signal in an interior conference room. Before you bash the kernels (not saying most are), take a look at what's using your battery. Therein will likely lie the answer.
[Droid Incredible Android Development] clambert11:
What is the real benefit of wiping the battery stats?

Sorry to sound so ignorant, but when it comes to this thread I have only been glancing through posts and I'm only somewhat knowledgeable.

I am however getting ready to flash BFS #4 on my phone. I get clearing the dalvik cache, but is wiping the battery stats necessary? What is this going to actually help? I don't recall (and I could be wrong) ever seeing anything by King stating that this needed to be done.

I'm just wondering what exactly it's going to help if the life of the battery it is reporting is already somewhat accurate.

I'm not planning on OC the CPU, so at this time I'm planning on running without Set CPU. Is that a mistake? It looks like several have been fine with that.
[Droid Incredible Android Development] jlss:
The theory (I've yet to see proof, but I haven't read every post in every thread in every forum) is that the way to max your battery is charge, with your DINC on, till green. Then boot into recovery and wipe battery stats. Then let the battery charge with the phone off until green again. Theory further goes that it takes several total drain/total charge cycles to maximize this. I can buy into the first part of the theory, but not the latter. We know that lithium ion batteries don't have a memory. This isn't like nickel metal hydride where draining was beneficial. That said, LiIon batteries do limit the voltage they'll accept on charge. I believe that is in the neighborhood of 4. I'm sure someone will correct me if I'm wrong.

As for flashing the kernel for the first time, I wipe dalvik and cache partition, then flash the kernel, then charge. Hope that's somewhat helpful.
[Droid Incredible Android Development] jlss:
+1000. Who cares what he's doing with donations? I'd guess that 95% of those who are using king's kernels haven't donated a dime. And that's okay. You're not obligated to. I see it like tipping a waiter/waitress. If I get a good experience, I boost my tip. So I donate to ROM and kernel devs. But that's me. Totally an individual choice.

Beyond that, it's pretty damn telling that since king started cranking out his exceptional kernels, activity with hydra's kernels seems to have stopped (hydra's were fine, imo.) So you've got a dev here, king, who WITHOUT his own DINC is willing to spend his time (which could be used doing other things, since time is a finite commodity) not just putting out *a* kernel, but 4 thus far PLUS others for AOSP. Carry on king. You're kicking a$$.
[Droid Incredible Android Development] eniamg02:
Last comment since I don't wanna flood thread..insult my comprehension level?idiotic.

It wasn't intended too bash anyone my comment was a little rash, didn't mean it to be that way so I apologize.Simply stating my opinion.
[Droid Incredible Android Development] oldman_58:
Not only is King building excellent Kernels he also looked at a dump file I sent, it is not often you find someone willing to put themselves out for strangers.

Yes , I donated, King and many other DEV'S have donated so much of their personal time, it's the least I could do.

Hats off King, thanks for all the hard work....
[Droid Incredible Android Development] elborak:
Coincidence. ejhart had already announced that he no longer had time to develop hydra kernels before king's kernels appeared.

Praise king if you like, but don't invent drama where none exists.
[Droid Incredible Android Development] bast525:
I ugh.... I have tried BFS numbers 2, 3, and 4, but keep having the same issue.... every time the phone goes past about 40 hours of up time without a reboot, it will randomly start to act VERY sluggish. When I opened system panel to see what was up, the CPU was pegged at nearly 100% load and full speed. At first I thought this was an issue with Setcpu, as opening Setcpu while this was happening would always make things go back to normal ( for a brief time). This same issue has happened on BFS #'s 2, 3 and 4.

So, I tried running with Setcpu completely uninstalled, but after 44 hours of uptime, the problem started again..... randomly starts slowing down really bad, open system panel, CPU is pegged. I NEVER had this problem with Hydra..... I've run my phone for over a week without a reboot on Hydra just fine.

No offense, I am not trying to bash, I REALLY LIKE the overall performance and benefits of Kings kernel, it really does do what it says it does, but will take stability over performance any day of the week. For those of you who don't mind rebooting every day or two, this kernel is awesome, but I'm going back to Hydra for now.
[Droid Incredible Android Development] Hand76:
Wow you read my mind just coming to post the same thing. After 24+ hours of not resetting my phone it starts to act sluggish with all of Kings Kernals.

I think a lot of people reset their phones offten so they may have not noticed this yet but I don't know what else to do.

Bast have you noticed this happening at any particullar time? Like after coming out of sleep?
[Droid Incredible Android Development] Lexus One:
I want to upgrade to BFS #4. I understand how to flash the code. But I'm not real clear on what I need to do initially to prepare. Is there a procedure posted somewhere that explains this in detail? Do I need to to a backup and restore? Do I need to do a wipe...and if so, what?
[Droid Incredible Android Development] seanzer:
I noticed the Android system process seems to use more CPU after installing BFS #4, but I thought it might have just been because the recent launcher pro update..
[Droid Incredible Android Development] jasonb1985:
System is also way above normal here as well with bfs4. Battery life seems fine though. Wonder whats up.
[Droid Incredible Android Development] Dat108Kat:
i definately have sluggish responce when coming out of sleep:(
[Droid Incredible Android Development] wakeboard143:
Always backup first, then wipe dalvick under advanced, then flash the kernel by applying zip from sd.
[Droid Incredible Android Development] wakeboard143:
I am currently at 35 hours uptime and having no sluggish qualities whatsoever running Virtuous 2.6 and BFS 4.
[Droid Incredible Android Development] Hand76:
Keep going see what happens.

I am on the same deodexed version of froyo and right around 1 1/2 days time of the phone being on it will start acting up and nothing seems to fix it besides a reboot. This has happened to me on multiple govenors and usually when coming out of sleep.

BTW it has happened even after I removed my sleep profile from SetCPU.
[Droid Incredible Android Development] wakeboard143:
Ya I'll keep it going to see what happens. I'm not sure if I have let it go this long without rebooting though so time will tell...
[Droid Incredible Android Development] androidsteve:
40.815 mflops

Sent from my ADR6300
[Droid Incredible Android Development] sdorn77:
I am currently on BFS#4, Virtuous 2.6 rom. Uptime is currently over 70 hours with awake time of almost 30 hours. CPU is idling at around 5% and phone is running perfectly. I've been using 3G hotspot for the past 5 hours or so straight and phone is cool and running smooth. This kernel is awesome.

I also consistently get as high or higher quadrant scores on my phone (over 1500) without SetCPU installed at all as I do when I install it and overclock my phone. I prefer to just leave it uninstalled and let the phone handle the CPU. There is no real need to OC these phones anyway.
[Droid Incredible Android Development] adamant13247:
So these King Kernels are the best, but how are you dinc users maximizing your battery time more than I seem to be? what kind of system maintenance apps are you using? Are you still trying to use advanced app killer (even though it seems to not work with froyo), Autokiller (which is what I use), or just the good old Android OS?
[Droid Incredible Android Development] chillmeow:
Are you using a 3500mAh battery? I cannot get my phone over 24 hours, and my awake time is only 6 hours. I have this kernel and Virtuous 2.6 with 1500mAh battery from bidallies. I do not have SetCPU either, and the quadrant score is around 1300. I have no idea how you get those number.

Plus I have a quick battery drain problem from 100% down to 85-90% without running anything.

Maybe you can give us some tips, please?
[Droid Incredible Android Development] bast525:
It always starts having issues after about 40 hours. Like five times in a row it did this. And just to make sure it wasn't some app I used system panel to stop ALL running programs. Nothing would work except either a) opening Setcpu (sometimes I would have to do this 2-3 times), or b) reboot.

When it starts having the issue, it does tend to do it when bringing the phone out of sleep after its been asleep for a while, but sometimes it will do it just sitting with the screen on (Ebuddy keeps the screen awake). It still runs good overall just randomly will start to go very slowwwwwwww.
[Droid Incredible Android Development] sdorn77:
I am using the 3500 mAh battery. I have my phone plugged in right now too but my uptime and awake counters are still running. Are they supposed to reset when you charge the phone? Maybe they will reset when I unplug it? My point was that I was not having the sluggishness issues the other poster described when my phone hasn't been rebooted in the past day or so. My phone hasn't been rebooted in over 3 days with no issues at all.

Don't know what to say about the quadrant scores. It hits over 1500 most times I run it with a dip here or there into the 1400s. I suppose that happens when some process runs in the background while the test is running.
[Droid Incredible Android Development] yzdirtrider13:
I've always used SetCPU, so I couldn't say if there's a difference.

Not usually, but other kernels never did this.
[Droid Incredible Android Development] chillmeow:
I didn't bump charge it tonight, but battery drained to 95% in 10 mins after I unplug the AC cord. This is so weird. I'll try to wipe the battery status again after I charge to 100%.
[Droid Incredible Android Development] melophat:
uptime and awake counters reset when you reboot, not every time you charge. :D
[Droid Incredible Android Development] brentslim:
This is my battery for just when i was at work using bfs #4..Sad.

This is from friday Using kernel bfs #2

I'm using the factory battery and Juice defender and thats it.
[Droid Incredible Android Development] oldman_58:
Something was keeping the phone awake your up-time and awake time only differ about an hour, check and make sure WiFi is set to sleep, and Signal access can make a big difference, the phone will search constantly for signal if you are on a low reception area.
[Droid Incredible Android Development] brentslim:
No i just use it that much at work, i have a lot of sitting around time..lol
[Droid Incredible Android Development] Lexus One:
Thanks. Will wiping the dalvik destroy all of my settings and configuration? IOW will doing a backup just be for a safety precaution, or because I will need to do an apk and data restore after the wipe?
[Droid Incredible Android Development] mschifman@aol.com:
Battery issued caused by Facebook

Many of you will be surprised to learn that the latest Facebook update will drain your battery fast. Regardless of which kernel you use, if you uninstall Facebook 1.3.2 to the stock one, you battery will not drain as fast. The results are dramatic and very noticeable.

By the way, I learned about this reading the forums. I barely ever use Facebook, and dont use the widget, and set my sync settings for Facebook to sync once a day. There were my settings BEFORE I discovered that it was draining my battery after upgrading to FB 1.3.2. After reverting back to the stock version, battery life improved a bunch.

Try it. You will be shocked at the difference.
[Droid Incredible Android Development] jermaine151:
When facebook 1.3.2 is first installed, it starts a service that drains the battery. Go into settings-->Applications-->Running Services and stop it. Reboot after that and you won't have a battery drain issue. I've been using it for a month without issue.
[Droid Incredible Android Development] upther:
The battery drain issue was in Facebook 1.3.1. It is supposed to be fixed in 1.3.2 and I haven't seen any signifigant battery loss. It also doesn't show up anywhere near the top of the list under my partial wake usage in Spare Parts.
[Droid Incredible Android Development] wakeboard143:
No wiping dalvik wont erase any settings or apps. Backup is in case of boot loops which are always possible when flashing a kernel.
[Droid Incredible Android Development] mgrassi99:
Slight instability

So I used BFS #4 all weekend (with Virtous 2.6), and had outstanding battery life...22 hours with moderate usage (Facebook, SMS, a few calls, some searches, etc). However, I found 2 issues: I had a couple random reboots, and my Bluetooth pairing was a little wonky. I reverted to the Virtuous Custom kernel, and all is better.

I don't know about the BT problem, but I would attribute the random reboots to being undervolted (and no, I'm not overclocked). Is there a way to get all the goodies from this kernel, without the UV?
[Droid Incredible Android Development] chillmeow:
I charged to 100% and wipe the battery stats while the AC cord is still on. I fall asleep last night, and today I woke up with the battery charged only to 86% and the phone is hot!

I have no idea what is going on right now :( :confused:
[Droid Incredible Android Development] douger1957:
+1. I've usually gotta swipe twice to get the phone unlocked.
[Droid Incredible Android Development] jasonb1985:
same here. i usually don't use a lock screen, but when i do it is always slow to unlock. i usually have to swipe twice to unlock it.
[Droid Incredible Android Development] upther:
Are you using SetCPU? If so what is your sleep profile set at?
[Droid Incredible Android Development] seanzer:
Don't have this issue anymore... I had it when I was using conservative governor or a screen off profile..
[Droid Incredible Android Development] Lexus One:
Thanks...... ;)
[Droid Incredible Android Development] hawkye:
Definitely backup before applying! I usually do but I didn't loading BFS#3. I tried going back to BFS#2 and sure enough got in a boot loop. So I had to resort back to a really old backup.
[Droid Incredible Android Development] hawkye:
Change your SetCPU profile to OnDemand. I used to have Powersave and experienced the same issue.
[Droid Incredible Android Development] dragonsamus:
I have bfs 4 installed but I'm not using set cpu. Is that bad? Also I've noticed my data keeps turning off. Is that a battery saving feature? Thanks in advance.
[Droid Incredible Android Development] Odin2347:
this kernel works well for a few hours and then grinds to a halt
[Droid Incredible Android Development] cmo220:
I just passed 40 hours of up time on my stock battery. So far the performance isn't any worse than when I start it up. I usually charge with it turned off so I won't get to see if performance gets worse in a few hours since my battery is under 10% now. This kernel seems great to me and can't wait to get paid so I can send a donation.

I can't get the awake time I see a lot of people posting but still, having 40 hours without charging is a lot better than I ever got with anything else.
[Droid Incredible Android Development] muaddib20:
Forty hours on stock 1300 ? That can't be right I barely get eight if I'm lucky.....

Sr 3.1 BFS# 4 radio 2.15
[Droid Incredible Android Development] wakeboard143:
Not 40 hours on a charge but 40 hours without a reboot. There has been some debate about the kernel becoming unstable around 30 hours up.
[Droid Incredible Android Development] Colomonster:
I too run bfs #4 without set CPU and with sometimes... #3 only runs at 245mhz when run without set CPU and #4 works just like the old #2 or #1 you will see improved speed and battle lire without setcpu I currently am not over clocking but have a screen off profile st at 245 min 384 max and no lag whatsoever do now get set CPU and turn it all the way up to 1:19 in both slots or you will be unhappy.
[Droid Incredible Android Development] mp3sum:
Any chance the next version will play nice with wireless tether pre releases?
[Droid Incredible Android Development] seanzer:
Wireless tether pre9 works for me.. I'm on BFS #4..
[Droid Incredible Android Development] jasonb1985:
same here. tethered right now. :-)
[Droid Incredible Android Development] yzdirtrider13:
8?! I could usually get 24 if 8 of that was the phone sleeping while I slept. Around 12 with heavy usage.
[Droid Incredible Android Development] rfarrah:
Details? ROM, Kernal, Radio, Battery?
[Droid Incredible Android Development] Div033:
I've been having issues with this kernal with a lot of uptime as previously mentioned. It was up for close to 30 hours and it started grinding up and slowing down. I have a hunch that for some reason its locking itself to 245mhz. I could be wrong though.

I could temporarily fix it by killing setcpu and rerunning it. However the problem would resurface after another hour, forcing me to repeat process.

I remember reading that using the set cpu widget can cause this, so I removed it from my homescreen... same problems. I turned off my task killer, removed the set cpu widget and have rebooted now. I will report back if I still have issues in another 30 hours-ish.

BFS#4

SkyRaider Vanilla 3.0 RC2
[Droid Incredible Android Development] syn87:
My phone reached 115 degrees with this kernel... the charging voltage was only around 3.7. I also randomly reboot with this rom... not oc'ed. anyone else reaching those temps?
[Droid Incredible Android Development] alexdeluxe:
I've been having great battery with #4, Skyraider 3.1 RC3. Stock battery too.

Current phone stats right now:

67% left

9:30 hours of up time

1:40 hours of awake time
[Droid Incredible Android Development] rfarrah:
FWIW, if you have Set CPU to "run at boot", I don't think removing the widget from your desktop will keep it from running.
[Droid Incredible Android Development] Nom Prophet:
#4 ftw! Battery lasts so much longer than #1. Thanks King!
[Droid Incredible Android Development] jlss:
Coincidence that you failed to quote my post, wherein I stated (as I have throughout these forums), that hydra's kernels were perfectly great as well? I'm not the one creating drama. Simply giving credit where due: both to ejhart and to king. Have a nice day.
[Droid Incredible Android Development] xwera43:
I've noticed a lot of lagging when typing, the keyboard (stock) really lags. I've tried it with SetCPU at 1GHz, 1.13GHz & 1.15GHz and with the governor set to On Demand as well as a couple others (it's not installed now & I've forgotten what they are). I don't have this issue with the stock kernel. Currently running Virtuous 2.7, no additional theme.

Suggestions please. ;)

TIA

X
[Droid Incredible Android Development] adrynalyne:
Quoting would just further cement the evidence.

Thats a backhanded way of creating drama. Intentional or not, its not what you say, but how ya say it...
[Droid Incredible Android Development] mp3sum:
Round 40 hours she crawls forcing a reboot.
[Droid Incredible Android Development] blakeem:
I had the same (or very similar) issue, it would run (very) slow and seem like it's running at 245mhz but for me opening set-cpu would fix it (would speed up as soon as it says it got root privileges) and then it would have issues again about one or two hours later. For me it wasn't only after 30 hours and would still do it after resetting the phone but was somewhat random.

I re-installed the kernel after I upgraded to Virtuous 2.7 and it seems the issue went away so if the widget removal doesn't work (I never used the widget) a rom and/or kernel re-install may fix it, so far this seems to have worked for me.
[Droid Incredible Android Development] xwera43:
I think it may be a bad install/upgrade to Virtuous 2.7 because the problem is not there with a fresh Redemption 2.0 install. It's also more of a lack of haptic feedback than sluggishness.

X
[Droid Incredible Android Development] fortesquieu:
I installed BFS#4 onto Virtuous 2.7 last night, for the whole day my reception has been showing 0-2 bars.
[Droid Incredible Android Development] muaddib20:
24:53 uptime equals crawling then reboot into boot loop until hard reset
[Droid Incredible Android Development] cmo220:
A few pages back when I mentioned 40 hours up time on the stock battery...that was up time and on a single charge. It was pretty light usage, maybe only 4 awake, but it was all on a single charge. I only made it to 41 before it died but I don't think I noticed much drop in performance.

I installed a new ROM last night which put the stock kernel back on and I decided to try it out a few days. Right now on stock kernel I'm at 12:51 up time, 2:28 awake, and 6% battery. BFS4 did much better.
[Droid Incredible Android Development] kingklick:
the kernel has NOTHING to do with your reception.......
[Droid Incredible Android Development] fortesquieu:
That's what I thought. :D

It was just an observation from me, not trying to confuse anyone. Thanks for your amazing kernels!
[Droid Incredible Android Development] Hand76:
King can you please comment on alot of us getting sluggish performance and having to reboot after the phone is on for 30-40 hours?
[Droid Incredible Android Development] crashdogy:
Hu, I thought it was my Rom or theme i was running maybe not.
[Droid Incredible Android Development] SLOflatlander:
i have the laggy lockscreen problem, and get hard locks every few days, im running 1113mhz interactive with 420mhz screen off profile (and i have for several weeks since these kernels came out). and i dont know how the hell you guys get so much battery time! i always seem to last the whole day, but thats with never more than 2 hours up time. (and its always cutting it close). i think it may be because i never have more than 2 bars even though i live in a generally good singal strength area
[Droid Incredible Android Development] iowabowtech:
I've recently had the sluggish thing also. Slows to the point it feels like a windows machine with a really bad trojan. Been running King for a long time and only had it since I switched to On Demand. Went back to Conservative and so far at least, no probs. Could be a fluke idk.

I'm not necessarily blaming the kernel. Interesting though that others are having similar issues. Also, I haven't paid any attention to the uptime to make any correlations there.
[Droid Incredible Android Development] ToyTank:
I'm just glad to make it 40 hours consistently without random reboot.

KK #4 and SR3.0RC3 Vanilla gave me the best battery(HTC 1500) life I ever had.

Check out screenies! :D

3hrs Wifi Audio Streaming

3hrs 3G Audio Streaming

2hrs listening to Audible

1Hr Voice Calls

30+ Min GPS w/ audio streaming

30+ Min Web browsing

50+ Text

20+ email

Thank You King! Awesome!:D