yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] larsrya8:
If you keep charging it after full charge it stops charging, and begins discharging as though it wasn't on the charger. It will drop until 90% and then maintains a charge at or around 90%.

I don't understand why this "issue" keeps coming up over and over again. It was sort of an problem when AOSP kernels couldn't charge quickly, but now that is fixed (and I'm so grateful :) ). Constantly discharging and recharging the battery to keep it close to 100% is very bad for Lithium based batteries, so the current behavior is correct.

Bump charging (aka, the battery charges when turned off immediately after reporting full while turned on) is probably because of the load placed on the battery when the phone is on. The phone seems to report charge status based on voltage, and load lowers voltage, so when the phone is on it reports that it's full a little earlier because it's not sure how much of a voltage drop the current load is placing on the battery. And once again, continuing to charge a fully-charged Lithium based battery is bad, so the current behavior is correct.
[Droid Incredible Android Development] godsmacked4653:
I usually charge my phone overnight, so I'm used to only having about 90% battery every day, which isn't that big of a deal. But this morning, on the #19 kernel, when I unplugged my phone, it dropped to 20% in about fifteen minutes. I hadn't done anything different with it, so that was pretty odd. (and a little scary.)

Hands down the most severe battery drop I've ever seen.
[Droid Incredible Android Development] khanam:
If you want to truly test kernels, you got to keep the rom exactly the same - I would recommend that people flash 16, 17, 18, 19 on aosp roms (cm61rc2, miui1211, UD2.4, Ruby), and do not set up anything at all except their google account and test it. At least we will see consistent results. Right now people run various services in their setups that eat up too much power and it makes them think its the kernel. Could be other things too people! Think of this as a control experiment.
[Droid Incredible Android Development] larsrya8:
You'll need to buy everyone a femtocell then, too.
[Droid Incredible Android Development] v941726:
with li-ion batteries it's safe to bump charge at 40% in fact its good for it. I think that's more of a phone issue
[Droid Incredible Android Development] v941726:
thats why you fully charge it while it's off, then wipe the battery stats before turning it back on
[Droid Incredible Android Development] v941726:
[RiQUOTE=khanam;9798207]If you want to truly test kernels, you got to keep the rom exactly the same - I would recommend that people flash 16, 17, 18, 19 on aosp roms (cm61rc2, miui1211, UD2.4, Ruby), and do not set up anything at all except their google account and test it. At least we will see consistent results. Right now people run various services in their setups that eat up too much power and it makes them think its the kernel. Could be other things too people! Think of this as a control experiment.[/QUOTE]

I have been trying to say this. We all use them differently, the dev made the spreadsheet to factor all that in. Either way, it's the best kernel for the
[Droid Incredible Android Development] papi92:
Everytime we charge? That sounds wrong. You shouldn't have to keep it off then wipe stats
[Droid Incredible Android Development] upther:
I'm at just over 16 hours since I unplugged and my seidio 1750 is around 29%. I use my phone in the car a lot to listen to music and the DSP Manager in CM6 chews the battery up pretty good. When I turn the DSP off, the battery is pretty damn solid while listening to music.
[Droid Incredible Android Development] LeoD:
Ahhh! ok finally! never heard or knew that. thanks for that info ;)
[Droid Incredible Android Development] v941726:
no not everytime you charge. This comes from HTC known issue. Turn phone off. Charge to green light. May take a awhile. Unplug. Plug in wait for green again. Continue til green comes on quick. Pull battery. Boot into recovery. Wupe battery stats. Reboot
[Droid Incredible Android Development] pcguy09:
#18 worked well with me for a while on CM 6.1 RC 2 , but the today I was having terrible battery life. I'm trying #19 now on the new CM 6.1 stable and we'll see how it works. #17 had great bat life. I don't bump charge much, and I charge during the day a lot. I'm hoping I have good luck w/ #19. I run 2 widgets (beautiful small home widgets and brightness toggle) and Under running services I only have google framework and android keyboard. I don't play games much at all (actually none) but I use tweetdeck all day long for work and play.
[Droid Incredible Android Development] invisiblek:
ok guys, heres another one to test out, #20, reverts 19's change, enables 128mhz (you have to go set it though, 245 is still the default min) and a couple minor tweaks to some lower freq voltages (undervolt a little more)

i would like some people, who are willing to test, enable 128mhz, either with setcpu or os monitor (i also would like these testers to not overclock, use setcpu profiles or anything else weird. only change your min freq for this testing) and report if we have any problems coming back from sleep, or anything strange happening and lower frequencies. if we are stable at 128mhz and these voltages, they should help our battery life some more

keep in mind, this is still a testing kernel, if it gives you problems, go back to one that was more stable for you

Download

Mirror

enjoy!
[Droid Incredible Android Development] shoman24v:
I'll give 20 a whirl.
[Droid Incredible Android Development] trombone dixie:
I love the work you're doing on these kernels.
[Droid Incredible Android Development] Grooby97:
testing #20.
[Droid Incredible Android Development] slorange:
Configured as requested with setcpu. Really doing well so far. 2 hours on, moderate use, 96% battery.

EDIT: the above post cost me 2%!

EDIT2 now it 's just dumping battery. Lost 5% in the last 15 minutes.
[Droid Incredible Android Development] DS36:
I will give you real feed back aube end of the day.....as apposed to the usual whining you usually get

Also you guys should check out the new cpu boost app from conap it a really nice alternative to set cpu

Located in themes and apps
[Droid Incredible Android Development] mattxander12:
I used to have little drain in the 100-90 range when on CM6.1RC2 plus #17. Now I'm on 6.1 stable with #20 (yes...setcpu'd to,min 128) and have dropped 10% in 40 mins.

Just my subjective input.
[Droid Incredible Android Development] slorange:
20 doesn't appear to actually scale down to 128, even when you set.it with setcpu.
[Droid Incredible Android Development] chemical1der:
thanks invisiblek. i just flashed #20 and will report back at the end of the day.

quick question(s): when i set the min freq to 128 SetCpu immediately changed the governator to Powersave, which made the phone hella laggy. i changed it back to smartass and everything was fine. did others experiencing this? is it just me? do other CPU monitoring apps do this same thing? DS36, did this happen with cpu boost?

TIA
[Droid Incredible Android Development] dccoh:
I believe you have to set a governor other than Smartass for it to scale to 128 (like interactive or convervative).

I loaded up #20 this morning. My battery at the time was at 14% (yea i know, im nuts). I have used setcpu to select Interactive as a governor (since you havent set smartass to be able to go below 245 as of yet it seems). And I have a screen off profile set for 128-245 (would you rather i set it mix-max of 128?)

I sent 2 messages and made 2 short calls, and 2 1/2 hours later im down 2%.

Let me know any other configurations you would like to test #20 :)

dc
[Droid Incredible Android Development] dccoh:
As per this page http://www.pokedev.com/setcpu/

Setting the governor to Powersave "It will keep the CPU running at the "min" set value at all times".

So its quite possible, based on your minimum, that you took your phone from a 998mhz phone to a 128mhz phone for a short while while powersave was selected :)
[Droid Incredible Android Development] mattxander12:
Actually appears that none of the governors can touch 128 mhz...at least for me

Edit: nvm...had to reset the min freq in setcpu...was showing 245 even tho it was set to 128. I can confirm however that the smartass gov wont scale below 245.
[Droid Incredible Android Development] dabomb697:
I'm running stock right now. What would happen if I flashed this kernal
[Droid Incredible Android Development] chemical1der:
thanks dccoh! that makes sense. i'm now running at 128min-998max in smartass and everything is gravy. i'll report battery stats later.
[Droid Incredible Android Development] SomeGuyDude:
128 is too low anyway. The ONLY time it works is screen off. If the governor drops to 128 while you're actually doing anything you'll lag and stutter like mad.
[Droid Incredible Android Development] DS36:
thats very strange everything seem to be working just fine for me.

i at the time of writing this am listening to a podcast on powersave gov. on purpose just to test the 128 clock speed. nothing skips and no lag
[Droid Incredible Android Development] dccoh:
Smartass isnt configured yet to go below 128 min, no matter what you tell setcpu to do. (watch setcpu and you can see it never goes below 245 when smartass is set)

I would use another governor such as interactive or conservative (id love to see ondemand added again) in order to test the 128 min.

Another user stated that 128 is too low period. While this may be true for some handsets (not all handsets seem to be the same), some operate just fine with a minimum of 128.

I can set mine to 128 min no problem, and while listening to music and watching setcpu, i have seen the cpu hit 128 rarely, since it seems to bounce all around. But when it does hit 128, i have no lagging or whatever. Same thing for when my phone is asleep, I dont seem to have any problems waking up from 128 (although sometimes I do set my screen off to 128-245, but have not seen any benefit, again ymmv).
[Droid Incredible Android Development] Grooby97:
I think with further UV, 1152000 is no longer stable (per adb logcat). I seems to noticed errors with DalvikVM when I have max speed of 1.152Ghz. Downgrade a notch to 1.113Ghz and the errors went away.
[Droid Incredible Android Development] chemical1der:
i just checked and you're right, smartass never went below 245. i've switched to interactive and so far i haven't experienced any lag. thanks again, dccoh. more anon.
[Droid Incredible Android Development] DS36:
Know what fellas maybe we should rethink smart-ass all together

smart-ass is based off off interactive gov. with a bulit in sleep profile

but im starting to think everyones screen needs are different

so im thinking we get rid of smart-ass and return ondemand and let set cpu handle screen off.

i like interactive its save battery over ondemand

but i LOVE powersave on screen-off
[Droid Incredible Android Development] Ty07allstar:
I'll give those settings a try.
[Droid Incredible Android Development] whewstoosae:
I'm sorry but I disagree entirely. My phone is running the best it's ever had. Best battery and performance I've ever experienced. Everyone's use differs but I don't think my phone can do any better than it is with this governor. Thanks invisiblek for making it fun to use my phone again.

Sent from my MIUI Incredible.
[Droid Incredible Android Development] mrchambo:
+1 whewstoosae...

jc
[Droid Incredible Android Development] tdiman:
I disagree as well.

I've been running #16 since it came out. Why 16? This was the last kernel released before intensive work started on the bump charging non-issue, which I'm not a fan of trying to solve as 1) it is good for the battery and 2) reports of "solutions" are inconsistent and 3) it seems to add more instability than stability.

Battery life is excellent, stability is second to none. I switched over from nightlies to 6.1 stable recently and am happy with combination.
[Droid Incredible Android Development] dccoh:
Hopefully...

Hopefully Invisiblek can tweak smartass to have a screen off min-max of 128 sometime in the future :)
[Droid Incredible Android Development] khanam:
that is a very good point... cant argue with that. radio would be different for everybody - however at least people will be able to compare 16 to 20 for themselves in the same radio/rom combo.
[Droid Incredible Android Development] :
+10000.....My phone has been really stable with this kernel (16/18) and battery life has been the best I've had since I bought the phone back in the summer. Now I don't even have to worry about carrying around my charger!!! :)

I don't mind the screen of min set to 128, but setting the screen off max to 128 I think it's too much. Lock screen is already a bit laggy (with all kernels) as it is. IMG setting the max that low will make the phone's wakup time longer. "If it's not broken, don't try to fix it" :D
[Droid Incredible Android Development] mikeymop:
@IV

Can you put the spreadsheet link in the main post where it's easy to find? I'd love to contribute to it, I think you'll get more participants if you put it in the main post asking for 'feedback to improved the kernel'
[Droid Incredible Android Development] shoman24v:
With #20 I'm sitting at 14 hrs of up time and I'm at 45%. Mind you I took it off the charger before I went to bed. Slept for about 7 hrs. #20 seem good. I kept the default min speed. 128 or what ever it is is too low. Laggy.

Sent from my Droid Incredible
[Droid Incredible Android Development] apockoffork:
Just wanted to chime in with my anecdotal evidence.

I used 19 for about a day including a full charge, discharge and then overnight charge cycle. When I took it off the charger it quickly dropped 38%. My battery stats blamed voice calls and display mostly but I think it was just because I happened to use my phone in that way for the hour it took to discharge 38%. I'm now back to 18 for the time being as I can't really test out kernals on my phone today.

On another note I haven't posted on this thread yet and just wanted to thank invisibleK and everyone who has been helping out with making this kernel. Really cool stuff and it does work great. The idle power usage is quite astounding compared to my old sense days.
[Droid Incredible Android Development] egeorgia:
20 has been just as good as 17. Have it set at interactive with a min of 128. Went about 3 hours at 6% discharge total.

sent from my Incredible using Tapa Talk
[Droid Incredible Android Development] smtom:
+1. #16, for my device and preferences, is the best kernel of an exceedingly good batch. Thanks again invisiblek....
[Droid Incredible Android Development] bradm23:
I agree with this 100%. I tried 16,17,18, and 19 and for some reason I keep going back to #16.

I asked this question a few times in some other posts but didn't get any answers. Does the stock 6.1 stable kernel have smartass governor? Also is this kernel off the latest HTC source? I love invisblek's kernels and will prob be switching to them again soon, but for now the stock Kernel has been rock solid.
[Droid Incredible Android Development] NickB95:
anyone got a link for a desire version of this? I really want to try cyanogen or miui but will miss gpu+...
[Droid Incredible Android Development] RegnierD:
Find the forum with Incredikernel in the title in the Development section.
[Droid Incredible Android Development] shoman24v:
I think I got about 18hrs or so today, maybe a little more. Phone died in the middle of a phone call.

I use my phone heavily, and have a 1500mAh battery (HTC). When I'm at work my screen brightness is always set to the lowest setting too.
[Droid Incredible Android Development] v941726:
I started with a 17. I keep going back to it. but guys, k would like us to test the new ones to get the best for all our world's. so let's help him!
[Droid Incredible Android Development] v941726:
so. k. with 20 I didn't get the quick battery drop. have the low set to receive 128, but it doesn't seem to ever hit it oops. Just checked Android system info. @128 it has spent 14+%. at 998 it has spent about 49% of its time (cpu of course) with about 10 other frequency's in between taking up the other 35%. sounds good to me. but i want to know what you think.

k. do you want me to send the log from ASI?

btw. my display uses up 67% of the battery no matter what i do. I keep it at 25% brightness
[Droid Incredible Android Development] rick311:
2 days 6 hours 33 minutes 7 seconds.

kernel 19, nightly 174. stock battery.

i charged it til it turned green and unplugged it. turned phone off and charged it some more til it turned green and unplugged it. turned it on, plugged it back in to see if the light would turn green. it did, so i unplugged, turned it off and charged again til it turned green and unplugged it.

booted into recovery, wiped batt stats and went with it.

charging now to see how tomorrow will be. *crosses fingers*
[Droid Incredible Android Development] Ty07allstar:
Is anybody having issues with wifi staying connected?
[Droid Incredible Android Development] ghostrida:
+2 still on #16. I see no reason to switch since its been so good. I was @ 55% after 24 hours.
[Droid Incredible Android Development] ghostrida:
No wifi issues here. Been solid.
[Droid Incredible Android Development] whewstoosae:
After maybe an hour of my phone sleeping, I can wake it and see that it's neither connected to mobile data or wifi. It's always done that to me though on AOSP roms.

Sent from my MIUI Incredible.
[Droid Incredible Android Development] upther:
Listening to music seems to be the biggest drain on the battery for me. I turned the DSP Manager off but I'll still lose about 4-7% over a 10 minute span. I've been using Winamp and maybe that's the culprit. I'll try going through a day with Meridian and see how that goes.
[Droid Incredible Android Development] v941726:
How do you attach a file here anyway?
[Droid Incredible Android Development] baram:
you people talking about using 16 because it didn't do the bump charge realize 18 was a revert to 16 meaning it also didn't have 17s bump charge "fix" and only was different in that it altered the screen on profile right?
[Droid Incredible Android Development] dccoh:
I hope this doesnt come off as a stupid question, but do you have the option turned off in the wifi advanced settings for wifi to stay on even when the screen is off?

I was on a older rom before (not sure if it was cm) and got mad that my wifi would shut off, then i realized that my wifi sleep policy was set to turn off with the screen.

dc
[Droid Incredible Android Development] NickB95:
I tried that yesterday, ty said it wont work :(

Thx anyway
[Droid Incredible Android Development] whewstoosae:
It's not a dumb question because I too got mad when I realized that the option was kind of hidden in those settings, but I have it set to "Never" for the sleep option in the advanced settings.

Sent from my MIUI Incredible.
[Droid Incredible Android Development] v941726:
how do you get your display to use such little battery. my brightness is set at 25% and is kind of dim. i always use 60+% no matter what
[Droid Incredible Android Development] rick311:
I'm not sure what i have it set at. It's definitely not auto brightness and i have a *****in wallpaper that's mostly black. i wonder if that has anything to do with it? how do i check the % of my screen brightness.
[Droid Incredible Android Development] RaptorMD:
While I am not new to flashing ROM's I am new to installing a different kernel. I have been testing out CM6.1 final on the DInc, and wanted to give this kernel a go as well.

Since I have CM6.1 Stable on do I just boot into recovery and install the kernel from the SD card in .zip format as well? Also since I have a stock build saved in recovery on the SDcard if I restored will the kernel get restored as well?
[Droid Incredible Android Development] Zomb!e:
Yep. Just boot into recovery and flash it. It's not a bad idea to wipe the dalvick cache though. A lot of people (including myself) recommend it.

If you restore your stock build you have backed up it will restore the kernel you were using when you backed up. I'm assuming it's the stock kernel.
[Droid Incredible Android Development] alphahere:
Another unless data point, but here goes. Using kernel #18

Using CM 6.1 and I have installed superpower (battery saver). With moderate use mainly email, text, wifi (I don't use 3g because data is too expensive) and a few phone calls it has been 24 hours with no charge. I am currently at 50% battery life remaining. Amazing to me.

I keep sync and wifi on from 7am until 11pm.

Before CM 6.1 and kernel #18, the best I got with stock kernel and stock sense was 12-14 hours. Sometimes I had to even charge up during the day and I was not even doing anything on the phone!

Note this is from a so called bump charge and not from a battery drain and recharge. I do not use setcpu.

Thanks a lot.

PS: I have never tried the stock CM 6.1 kernel.
[Droid Incredible Android Development] upther:
As much as I love the super fast charging on these kernels, I had to switch back to the stock CM 6.1 stable kernel. Not sure if it's just me but these kernels just don't seem to hold up well when playing music. I've tried Winamp, Meridian, and the stock player and all three lead to some pretty quick battery drain. Could the Smartass governor be the issue?
[Droid Incredible Android Development] mattxander12:
Try using 6.1 stable with 17 and the MIUI music app (there's an apk floating around). I haven't noticed significant drops with that setup.
[Droid Incredible Android Development] upther:
Does the MIUI music app scrobble to Last.FM? That's my only requirement with a music player. #17 seemed to the best for me out of the 17-20 group.
[Droid Incredible Android Development] v941726:
i have an app called adjust brightness. you can put in whatever you like. at 25% its kind of dark. easily adjustable though
[Droid Incredible Android Development] fp99:
I use My Settings app to set screen brightness at 25%.

invisiblek - I was using google gps driving home from work today and took a call on speakerphone for 15mins. When I for off the phone it was warm and temp was 111F. It fell back to 89F after 5 mins. I've never had this happen before. Any ideas on what could have caused it (kernel related)? No setcpu, no overclocking, no profiles. Battery was at 37%. Thank you.
[Droid Incredible Android Development] invisiblek:
i did some digging, and 111F doesnt seem to be that uncommon on this phone, when you are really working it. from what im reading that shouldnt be an issue

http://androidforums.com/incredible.../96716-high-battery-temperature-question.html
[Droid Incredible Android Development] fp99:
thanks for the info. I've never seen my temp go up that high before when using the gps and speaker phone so I was just wondering if you knew if it was kernel related or actually ROM related. Plus it's been nice and chilly here in NJ for the last few days so there's no chance of overheating I believe...lol.

EDIT: I also have not gotten any reboots due to rom, kernel, or high temps.
[Droid Incredible Android Development] ufvj217:
damn

what rom?
[Droid Incredible Android Development] ufvj217:
so, are we supposed to NOT use setcpu profiles? i currently am, getting pretty decent battery life. Invisblek, what do you suggest? im running #18 now, about to give 19 a try.
[Droid Incredible Android Development] v941726:
Jeez. I'm lucky if i get 6 hours. Sucks. If i need to talk a lot its even less
[Droid Incredible Android Development] dccoh:
His post said "nightly 174" so that would be cm (cyanogen mod), nightly build 174.

You should be able to find that specific build here: http://mirror.teamdouche.net/?device=inc&type=nightly