yashsingh1/xdaforums huggingface dataset:
[Droid Incredible Android Development] gmichaelow:
ms79723,

I think you should give a fair warning to everyone about how trickle charging and this charging method will affect their battery life. By that, I mean how long-term. The duration that the battery will be useful for.

Li-ion batteries (the kind in our phones) don't like extremes. They don't like it too hot, nor too cold. Likewise they don't like to be discharged too much, or charged too much either.

Discharging too much can cause the entire battery to simply stop accepting recharges, instantly broken battery.

Charging too much will wear out the battery and reduce the lifespan to a few months.

Many are probably saying "But he's not OVER-charging our batterys past 4.2v, so it's safe, right?" Well, yes. It's safe in that the battery won't explode on you.

But the trickle charging keeps the phone at, or near 100%. Remember how Li-ion's don't like extremes? This is one of them. 100% charge, 4.2v is on the very edge of how much the battery can handle. Staying there too long will do the same as staying at 0% too long---the battery will stop accepting a charge. However, on the top end, 100%, the battery doesn't outright die. It simply drops in capacity. Your 1300mah will become 1200, and then 1100, and then 1000, and on and on.

I'm not bashing the kernel in any way, I just think users should have a fair warning. I mean, if you're gonna get a new phone in a few months anyways, then go for it.

This is actually a good workaround for the bump charge issue. All I'm saying is that the users should know that the bump charge issue exists for a reason. HTC deliberately drops the charge to ~90% for a reason, and that's to protect our batteries.
[Droid Incredible Android Development] sneaky_zekey:
Im willing to take the risk

Bump
[Droid Incredible Android Development] ufvj217:
me too.

like i said a couple pages back, ive had my incredible since the release date. in about 1.5yrs or less, when im available to upgrade, we all know you will use the upgrade, especially by then there should be even better android phones, and 4g at that. im sure this wont affect the battery in the time i have left using the phone, so personally it doesnt bother me. whoever i sell the phone to (unless i keep as a spare) can deal with getting a new battery if needed :)
[Droid Incredible Android Development] Homan13PSU:
Been running this for two days now. VERY impressed with the battery results. Having a couple app issues though. AppBrain and PureMessenger crash when you try to open, or place it on a screen. Also getting a lot of Launcher crashes.
[Droid Incredible Android Development] mrchambo:
23+ hours and at 77%. Running MIUI 12.24, v2 kernel...light to moderate usage, predominantly SMS and Calls, some surfing, ESPN etc.

I'm impressed.

jc
[Droid Incredible Android Development] chicojd:
Interesting strangeness with my 2150mAh battery. Charged overnight, never got over 99% and after 5minutes was down to 93%. Installed Battery Monitor and didn't see anything unusual. Ran a backup while plugged in. When the phone rebooted, I was at 17%. Charging slowly now. After 2 hours, charged to 42%. Hoping this fixed my issue.
[Droid Incredible Android Development] keith.mcintyre26:
Dud you wipe battery stats in recovery? This has been the ticket for me.
[Droid Incredible Android Development] infamousxsniper:
Can someone help me? I installed v2 on my MiUI 12.24 and every time I try and install and use the v2 it makes my touch screen unresponsive. Is anyone else having this problem and is there a way to fix?
[Droid Incredible Android Development] Crackmaggot:
Loaded up V2 before I went to bed last night. Grabbed it this morning and drove into town. After 40 minutes of not using it, the battery was at 62%. Didn't have the time to figure out what happened. Just reflashed Invisiblek's #28. Using OMGB6.
[Droid Incredible Android Development] Atlas.rouge:
I will bet an imaginary dollar that you didn't wipe cache/dalvik well enough. Happens to me sometimes too lol. 2x through is usually good enough.

Sent from my HTC Incredible running MIUI 12.24
[Droid Incredible Android Development] SomeGuyDude:
Um. Computers aren't like car windows. It's not like you need to keep wiping it to make it cleaner and cleaner.
[Droid Incredible Android Development] infamousxsniper:
Were you referring to me? If you were then this is what I have done with it...

Wiped, wiped cache, wiped dalvik, flashed MiUi 12.24, rebooted, went back to recovery, wiped dalvik again, and then flashed v2. When I rebooted my touch screen would not move. I can swipe down and hold the power button and it will show me the menu on that. It's just my touch screen is not responding to my soft touch... Can anyone help me?
[Droid Incredible Android Development] GMK83:
It's not like you're wiping your ass. Once you format the partition the data is gone.
[Droid Incredible Android Development] seanzer:
You never know what you'll read next in these forums.. lool
[Droid Incredible Android Development] stopxstart:
After a few battery cycles, I'm getting some pretty ridiculous improvement in battery life.

Just had a 38 hr charge with the 1750 battery. With moderate use. With heavy use I'm getting about 24. Very impressed.
[Droid Incredible Android Development] Atlas.rouge:
Radio? I'm running the same set as you and am pulling about 12-16 hours moderate use, which is fine for me but I'd like to max out my battery time. Thanks!

Sent from my HTC Incredible running MIUI 12.24
[Droid Incredible Android Development] chaosbringer:
For some reason, multi-touch is not registering more than 2 points.

I have Cyanogen 6.1 + this kernel v2...

Anything i have to modify that i didnt realize?
[Droid Incredible Android Development] superchilpil:
Hate to but in

But i believe one dev has proven that wiping cache doesn't make a difference. I don't do it unless I'm using a different rom

Not different kernels
[Droid Incredible Android Development] superchilpil:
Some dincs including mine don't register more that two, I've got a amoled screen and the newer touch screen capable of ten touches yet I only get two with any rom I try
[Droid Incredible Android Development] chaosbringer:
Hmmm, i have two dincs, one amoled one slcd both rooted. Im going to try the other one to see whats going on... I also remember trying it with skyraider but it also did not work...

It has to be an issue with the drivers/software, i dont see how the screen has anything to do with how many inputs it accepts.
[Droid Incredible Android Development] stopxstart:
The newest EVO one.
[Droid Incredible Android Development] seanzer:
It just happens that there are at least 3 different touchscreens in the dinc..
[Droid Incredible Android Development] csseale:
http://www.ziggy471.com/2011/01/02/overcharging-batteries/

This is the whole point and problem....I appreciate the effort but at what cost.
[Droid Incredible Android Development] vandeec5:
My results.

I took the screen shot when it went down to 2% left of battery.

I noticed when the battery charges to 100%, I rebooted and it went down to 46% So I had to recharge again.
[Droid Incredible Android Development] larsrya8:
Are you running a Sense ROM?

While I would never run this kernel in it's current state, it appears that several are. What worries me more is that ms79723 hasn't pulled either link yet, even though it has been confirmed that charging is broken. What else may be broken? What unknown damage could v1 and v2 be causing? The new method of 'more frequent bump charges' (which I think is a better idea) was to be released six days ago, yet nothing.

I know the thread title has "[TESTING]" in it, but battery life is like crack to these guys so disclaimers can only do so much. Pull the links to v1 and v2 and explain why (so Dropbox mirrors don't pop up everywhere).
[Droid Incredible Android Development] keith.mcintyre26:
Can't. This is an AOSP kernel.
[Droid Incredible Android Development] larsrya8:
And yet, that sure looks like Sense in the screenshot. See how the Display battery usage is being reported as unbelievably low? Classic Sense. So is the presence of "Awake Time", which AOSP doesn't have. His/her posting history seems to imply that it's Redemtive rEVOlution, which claims that it is "based on the newest official Incredible OTA 3.26.605.1 and the newest EVO OTA 3.30.651.2". So... they're running an AOSP kernel on a Sense ROM?

That's not to imply that the source of the battery drop issue stems from that, of course.
[Droid Incredible Android Development] vandeec5:
Yep, I am running a Sense Rom. Redemptive Revolution 1.8. Baseband Version: 2.15.00.09.01.

Awesome battery life :)
[Droid Incredible Android Development] csseale:
Its not for sense roms only for aosp roms so you should probably revert. While yes it may seem to be working there is almost a certainty its not doing so properly.
[Droid Incredible Android Development] sneaky_zekey:
As I stated in earlier post. I understand the risk of using this kernel. Im willing to take the risk. No one is making anyone use this kernel. I say bring on the updates. More power to the OP. Its also risky to overclock our phone but everyone does it. Lol
[Droid Incredible Android Development] byrong:
True: I fully support everyone's right to make their own decision. No harm in helping them be informed in that decision: hence my agreement with the suggestion that disclaimers be added to the OP.
[Droid Incredible Android Development] kenny21:
Whatever decision you guys make is great but let me tell you from my experience about this modded kernel. I have a evo and have been using this from the first day it came out and its awesome. You wouldn't believe the difference it makes getting a full charge on your battery. I started on the sense version and got about 20 hours moderate usage. I just installed the miui rom with the aosp version of this kernel and got 23 hours with 40% charge left so in my opinion this one of the best mods you can get for your incredible. With each update you'll see it get better. And like its been repeated before but sure this a risk but so is rooting, installing custom roms, and overclocking our phones. But without experimenting and testing the limits of our phones we might as well stick to stock roms and kernels cause thats what the manufacturer has provided for us. Thats what xda and various other sites are about is developing and improving our phones. Just my opinion
[Droid Incredible Android Development] fortesquieu:
Yea, you are right. I've been using it, it really squeezes out more juice!
[Droid Incredible Android Development] shoman24v:
OCing can't cause the battery to explode. If anything the increased voltage to accept the clock speed will fry the phones CPU. If anything really it will cause it to not boot or have stability issues.

I don't see the benefit of OCing other than getting nine billion in quadrant.

Sent from my Sprint Galaxy Tab
[Droid Incredible Android Development] joelcableguy:
U have a link for the "sense version"?:)
[Droid Incredible Android Development] subzero2000:
Availability of Sense kernel source with Trickle Charge modification

I have made available a github repository forked from Chad0989's incredikernel (which is a Sense kernel) with the modifications to htc_battery.c in it.

The URL for it is https :// github.com/sleavitt/incredikernel

I cleaned up those modifications for readability using "diff -NuBw" to disregard the whitespace that was introduced by copy and pasting the code from gedit. The source of the diff was htc_battery.c from the original HTC source (incrediblec-MR3-2.6.32-g9a2fc16).

I am merely making the repo available for anyone interested in it. I will NOT be distributing ANY binary kernels built from this source, but anyone who wants to do so is welcome to. I am currently not running a kernel built from this source, so I have no idea if it works or not.

ms79723, if you get an opportunity, I would appreciate it if you could peruse the commit that makes the necessary changes (https :// github.com/sleavitt/incredikernel/commit/40ec49c5f3bcda9df7945d3c6c4dffb6cfaa6049), and make sure I did not introduce any regressions by cleaning up your code. I have been over it several times, and don't think I did, but a second set of eyes on it would be greatly appreciated. Thanks.

P.S. Had to make changes to the URLs as evidently I don't have enough posts yet to allow me to post URLs in my replies.
[Droid Incredible Android Development] stopxstart:
Just got this with this kernal with the 1750 battery and moderate to heavy use.
[Droid Incredible Android Development] macaulee:
After using this for a couple weeks I can say that I love it. Super fast and recharge times are awesome
[Droid Incredible Android Development] lakeyece:
I'm still waiting on an answer to if this can be modded and used on virtuous 3.2. I pmed the op and it has gotten me no answers. He didn't even seem like he knew what he was talking about. He said this kernel would work on virtuous.
[Droid Incredible Android Development] OlympusGod:
Ive been using this for about two weeks. The first week I had stellar battery life, about 4 hours extra. Now. My phones been on for 2 hours, and its at 55 percent. I listened to maybe half an hour of music, and that's it. The display has taken up 60% of the power, even though its been on maybe 2 minutes. Has this happened to anyone else, and are there any fixes?
[Droid Incredible Android Development] bensl84:
I would say reflash the kernel after wiping cache and dav, just my thoughts. cause that happened to me before and it did the trick
[Droid Incredible Android Development] lakeyece:
this works with cm7 nightlies?
[Droid Incredible Android Development] vinmod:
No
[Droid Incredible Android Development] FatGuyWithWifi:
if it does trickle charging am i to assume this is an sbc?
[Droid Incredible Android Development] SynisterWolf:
lol yep. SBC aka Superior Battery Charging? :D
[Droid Incredible Android Development] HyperTension:
Holy dead thread resurrection... :-)
[Droid Incredible Android Development] Kiboe:
is this still safe to use?
[Droid Incredible Android Development] countryfolk07:
I've used SBC kernels. Never had any issues other than the charge is slower.

Sent from my ADR6300
[Droid Incredible Android Development] foopy:
Dumb question - removed.
[Droid Incredible Android Development] egobuster1:
How's performance
[Droid Incredible Android Development] ms79723:
I haven't committed the changes yet, I forked it then left the house.

As soon as I get home I'll answer all questions.
[Droid Incredible Android Development] Atlas.rouge:
This kernel is doing even less overheating than Cayniarb's kernel, which is nice. About to deplete battery to 0 and recharge, will reassess in the morning.
[Droid Incredible Android Development] ms79723:
You can use USB to charge. What I recommend: When flashing this kernel, do not have your phone plugged up to USB. Does that do anything wrong? No...not necessarily. From my experience with the Evo, when I had my phone hooked up to the comp and flashed the kernel, I would have to unplug my phone from USB and then plug it back in to start up the charging. Idk why it does that...just a heads up.
[Droid Incredible Android Development] ms79723:
Shouldnt overheat. Temperature decreases over long periods of charging. So your phone should be pretty cold when you pick it up in the morning (well mine is, but I'm an Evo user so...idk how much that applies here haha. Just my two cents.)
[Droid Incredible Android Development] nikon_rh50:
Does this have Multi-touch?
[Droid Incredible Android Development] ms79723:
Should have everything that Invisiblek's latest kernel has. Only thing different is the charging aspect.
[Droid Incredible Android Development] ms79723:
Wait...have you been on 97% for the last 20 mins? Or the drop from 100% to 97% took 20mins?
[Droid Incredible Android Development] shoman24v:
looks to me he's been on 97% for the last 20 Mins...
[Droid Incredible Android Development] Atlas.rouge:
Ok, I have a problem. In trying to force my phone's battery down to zero, I decided to run a stress test. I also decided to put my kernel settings on maximum (1.2GHz) and run it with the Performance gov (so running 1.2 GHz constantly). I managed to achieve my first boot-loop.

Now, with that in mind, can I flash a previous backup to get rid of this? Or am I close to screwed? I am in CWM recovery but would rather not touch anything until I know I'm good to go (I feel like I'm looping because I set the kernel too high).
[Droid Incredible Android Development] ms79723:
Yeah, you set the OC too high probably. I think you can just wipe dalvik and then go into setCPU and turn the OC down when your phone boots up. And why are you taking your battery to 0? You dont need to do that. Just gotta stick it on the charger. Dont need to wipe battery stats either.
[Droid Incredible Android Development] Atlas.rouge:
Ok thanks! Just did all of that and am trying it now (I'll need to QUICKLY log into SetCPU and shut off the high-ass (pardon my language) 1.2 GHz speed or it will likely bootloop on me again. Good to know it's fixable...I didn't do something stupid like flash a bad radio lol.

Edit: Boot is running normal so far...I reflashed Evervolv a13 after doing Dalvik/batt stats, so it's gonna take a few minutes to get going. Will move like lightning when I see the soft keys light up lol...
[Droid Incredible Android Development] ms79723:
Now I'm assuming that works because I did that once and wiping dalvik was how I fixed it. If that doesnt work, tell me and I'll OC and we'll figure this out.
[Droid Incredible Android Development] mikesincredible:
when I unplugged it, it was at 97% ..usually after about 10 mins of use i was down to about 90%....i dont bump charge, i charge and leave it as is, but so far all around great kernel
[Droid Incredible Android Development] Atlas.rouge:
hot keys just lit up.

Sh*****t...couldn't get into the app fast enough...the damn profile activated at 1.2 GHz and kicked me out. I'm going back into Recovery, going to wipe User Data, much as I don't want to...it probably needs to be done.

And the reason I think that will work is because it will (hopefully) clear my SetCPU settings, which will in turn allow me access back to my system. Then all I do is reload my apps from a BackupPro save. Did one two days ago lol, not much has changed since then.
[Droid Incredible Android Development] shoman24v:
Usually when I OC I never let them stick on boot. Did you do this?
[Droid Incredible Android Development] Atlas.rouge:
Yes...probably a stupid thing to do. Will make sure I don't do that in the future. Booting back up now with wipe of user data, data & dalvik done.

Edit: It worked. Now I just need to reload all of my apps, I will probably load SetCPU directly from the market, where I can control the data that it starts spewing. Thanks for all of the help shoman and ms79723!
[Droid Incredible Android Development] ms79723:
Thats weird...so you charged to 100% and when you took it off the charger it was at 97%? Thats not supposed to happen.

Can you do me a favor? Can you download the app "battery monitor widget" and charge to 100% and tell me if you see any -mA's once you reach 100%. Make sure you set your update interval to 50 seconds.
[Droid Incredible Android Development] mikeymop:
I wish I got here quick enough for you, with AOSP theres a SAFE MODE boot that will only run GAPPS at boot. If you check the general discussion section there was post about it (i believe it was volume + UP during the boot animation
[Droid Incredible Android Development] mikesincredible:
On the gb rom the battery don't show 100%..just fully green when its done and the green light...when I unplugged it, it was at 97%. I will download the widget and update u tomorrow ..so far its been stable, responsive..that signal issue was just bad location in my house
[Droid Incredible Android Development] mikesincredible:
Did u want me to run it at normal clock speed? Right now I'm oc to 1.13
[Droid Incredible Android Development] ms79723:
ohhhhhhhhhhhhhhhhhh yeah! That's right! I find that odd, but at the same time, I like it. That makes me feel a little better haha.
[Droid Incredible Android Development] xShin:
I'm running Sense and am currently having beautiful results with Chad's Kernel, so I am unable to try out this fix for now. That being said, I just wanted to extend my thanks for your generosity in helping people with phones that you don't even have/use. Thanks!!
[Droid Incredible Android Development] xjbhxx:
I tried installing with ultimate droid 2.5, screen was unresponsive. Installing with Cm 6.1 now.
[Droid Incredible Android Development] RLKirk:
Sorry to ask again but will a sense version be available?
[Droid Incredible Android Development] xjbhxx:
Same thing with CM 6.1. Hmm.
[Droid Incredible Android Development] ms79723:
OC shouldnt matter. Because overnight when your phone is idle, it'll be at the minimum frequency

If I can get this to work on AOSP then I'm pretty sure the devs that work on Sense kernels will add it.
[Droid Incredible Android Development] RLKirk:
Ok thanks

_10char
[Droid Incredible Android Development] mikesincredible:
woot xmas eve!
[Droid Incredible Android Development] ms79723:
SHIAT! Is that 807mA positive or negative?
[Droid Incredible Android Development] ms79723:
If you're using Battery Monitor Widget...what is your voltage next to that 807mA?
[Droid Incredible Android Development] mikesincredible:
ive had only one 807mA and the voltage was 4247mv
[Droid Incredible Android Development] mikesincredible:
its positive.
[Droid Incredible Android Development] papi92:
I've gotten 576+ on charger and -554 on charger.
[Droid Incredible Android Development] ms79723:
What would you say your avg voltage is?
[Droid Incredible Android Development] ms79723:
Do you have anything below 4200 past 100% And how many readings do you have that are above 4235?
[Droid Incredible Android Development] ms79723:
What is your voltage looking like on the charger?
[Droid Incredible Android Development] papi92:
4195
[Droid Incredible Android Development] ms79723:
Do you see anything underneath 4195? In the 4100 range?

And are you actively using your phone right now?
[Droid Incredible Android Development] papi92:
Yes very active. And nothing below 4195 my top is 4199
[Droid Incredible Android Development] ms79723:
And all positive -mA's? That's good. Are the mA's increasing or decreasing? Like, are you going from high number -> 0 or 0 -> high number?
[Droid Incredible Android Development] papi92:
I have had a couple negative ma's. And my chart is wild lol
[Droid Incredible Android Development] mikesincredible:
about 4190...

everything is below 4200 past 100% 4190 high, 4158 is the lowest @ 99%.....i have some readings above 4235 but this was during charging at 81% the mv got lower as the %s increased
[Droid Incredible Android Development] ms79723:
What do you mean?