yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
Honestly, i would use either Voltage Control or Control Freak to set OC/UV if your only going to OC up to 1.2gz, since the OC/UV code in the kernel was wrote for them.., and apps like Tegrak and SetCPU use total different methods.., both work, but for best compatibility i recommend using VC or Control Freak since the code was wrote for them (if your using the OC built in the kernel..aka 1.2ghz).., Also I recommend to only use 1 or the other, if you have mutliple apps that control the same thing (and in this situation applying it differently) it can cause issues..

As you can see with the latest UV bug, both apps (VC/Control Freak versus SetCPU/Tegrak) they all do the same thing but SetCPU/Tegrak applies it differently, so they were not effected by the earlier bug, since they do not use the frequency_voltage_table file..
[Captivate Android Development] RTBee:
Heard it from the man... case closed! ;-)
[Captivate Android Development] existz:
0.4.4.20 Public Test

0.4.4.20

Changelog since 0.4.4.19

- added few ZRAM upstream fixes

- possible 'charge bug' fix from AOSP upstream

NOTE

Its to early to tell if this 100% fixes the problem yet, so if you guys can test this for the 'charge bug' id really appreciate it..(where after charging to 100% it drops to 95-below when pulling off of the charger)..Again, im not sure if it fixes it, but its an attempt to..
[Captivate Android Development] topiratiko:
First. Thanks existz

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] iXNyNe:
I actually make use of setcpu's profiles feature, so unless there is an actual compatibility issue with using it ill stick to it :) but regardless its good to know this information
[Captivate Android Development] Thunder22:
Does 0.4.4.20 have memory freak? how do we get to it
[Captivate Android Development] existz:
No, it will be released soon..., didnt plan on putting another update out today but I wanted to test the charge bug fix, but its still in private testing, wont be to much longer
[Captivate Android Development] mrhaley30705:
Will MF work with aosp roms, or just samsung roms.
[Captivate Android Development] existz:
Will only work with Talon (for samsung roms) as it is setup to use kodos' ram.conf file, you adjust the values in the app and apply, then it will write those settings to ram.conf
[Captivate Android Development] existz:
Dont want to bring false hope to you guys, but for the last 3-4 hours ive been setting at 100% charged, and every hour ive tested it by unplugging from the charger...and its setting at 100% ..before it would always drop to atleast 99-98, never would it stay at 100%, and never after setting at 100% for 3-4hrs...So we might be on to something here.. which its still way to early to tell, but so far its showing an improvement..fingers crossed
[Captivate Android Development] daverup:
I don't think it's false hope, I think you fixed it.

There is a different behavior of the battery percent indicator. Before this fix, if it charged to 100%, it would beep and both the full notification and percent indicator would indicate 100%.

My calibration is a little off I think, so when reached full charge, the notification says 100%, and the percent indicator showed 98%. I ran it for a while still connected, then unplugged. The percent indicator remained at 98%. Then I plugged it back in and the notification quickly showed 100%, and the percent indicator showed 98%, then 99%. Unplugged again, no change.

So, it's probably topping off the charge after the 100% notification. This is different than the previous behavior with the charge bug.
[Captivate Android Development] sinichi21:
Oh my same here it stays on 100% after 2 hours of leaving it on the charger same with charging it off stays 100% after booting lets cross our finger hopefully will try it before going to bed to leave it on the charger :D
[Captivate Android Development] sinichi21:
hmm maybe your calibration is off it just happen that i just finish calibrating my phone yesterday and fix came out mine shows the 100 percent on both
[Captivate Android Development] topiratiko:
Ya know what existz...if this pans out....you get to claim the first FULLY stable custom gb kernel. Fixing wifi AND charge bug. Your a beast quite simply.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] b-eock:
Can this be used to work on the KF1 leaked Gingerbread build for the Captivate?

Sent from my plain KF1 Gingerbread Captivate using the XDA Premium App.
[Captivate Android Development] sinichi21:
+10 Indeed existz is really the beast what would we do with out him :cool:
[Captivate Android Development] existz:
No, only works for i9000 gingerbread (jvp/jvq/jvr..etc)
[Captivate Android Development] Rrryan2:
No, since my initial flirtations with topiratiko's LMK settings I've left the stock Talon settings alone. I haven't noticed the problem as much lately, but then again for various reasons (like updating to .18,.19,.20 etc.) I haven't really gone much more than 10-12 hours without rebooting either.

I'll try to see if I can go a day without rebooting and see what happpens.
[Captivate Android Development] eliminat:
If existz lets you....
[Captivate Android Development] topiratiko:
L.O.L

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Rrryan2:
Heh. Well, if something new drops I guess I'll just have to find the willpower to hold off flashing and continue waiting for the greater good. :D
[Captivate Android Development] watsa:
Ok no 9.2 till everyone tests this. So no reboots from my side :D
[Captivate Android Development] irishvandal:
lol, you would say that. i am so wanting to drop DC. missing my Talon claws.
[Captivate Android Development] existz:
0.4.4 is getting close to release, im still wanting to get the memory leak squashed and add Memory Freak in the official..., so what i might do is make the next release a 'stable' RC1 release.. IMO 0.4.4.x is getting very close to that point, alot of bugs fixed and a few new features added.., its possible i will have MemoryFreak in the RC1, but still need some time on the memory leak issue.
[Captivate Android Development] manny05:
How about overclocking? When are we getting that feature back? After all the bugs are fixed or?

Captivate running dlev's latest rom

Talon kernel/snail

Overclocked and undervolt
[Captivate Android Development] existz:
Not sure yet.., I really dont want to go back to all-in-one OC like before, its way to unstable..., it seems to be best to leave it the same number frequencies as stock.., but if I just replace 1ghz/1.2ghz step with 1.3/1.4..etc..,the cpu will have to be alot more stable than it was before, since theres no other frequencies there to keep load off the cpu... So for those that could do 1.44 stable before, they might not be able to do it then.. BUT honestly, Tegrak OC gives about the best option when it comes to this.., it replaces the top freq like it should be, while giving alot more control over adjusting arm/internal voltages.., more than I can give you guys.. Heres a post by Lukiqq, which he stated it pretty spot on about why its best keeping the number of freqs the same as stock, theres alot of things that are based on the number of freqs as stock..

Theres alot of DVFS settings through out the source, for different drivers..(like USB, BT/WIFI, power management..etc), I would have to locate and fix each one, which would be a pain in the ass..But i do plan on making my own OC module at some point, it will probably take me awhile to get it finished..hell, even started.., But as of right now, I will probably only keep 1ghz and 1.2ghz versions (plus its less versions i have to compile and upload :P)

I remember with froyo there was alot of talk about non-oc kernels and oc kernels (all-in-one OC) not being the same, even if no OC was applied.., this is true.., if you have the step disabled and 1ghz max, an all in one oc kernel (....800-1000-1200-1300) set to 1ghz max, is alot different than a non-oc kernel.., this is because of the DVFS settings.. if something was set to L3, stock that would be 200mhz, on an all-in-one oc kernel, say up to 1.3ghz, that would be 800mhz, thats a big jump when something is suppose to be running at 200mhz, when its running at 800mhz..
[Captivate Android Development] RashaMatt:
It will easily if you're running Mobile AP - and mine will discharge all the way down to zero if I don't intervene. Every time.

EDIT : Actually not *every* time, but every time that it does drop, it will continue to drop all the way to zero if the charger is not removed and reapplied. I'm about to test .20 to see if that fixes it, but it will take me at least 24 hours to be certain.

_________________________________________

AT&T Captivate, Serendipity VII b1, TalonDEV 0.4.4.18, KC1
[Captivate Android Development] existz:
Yea, but running Mobile AP is not just setting there doing nothing :P.., Mobile AP is a battery hog.., i think what they was talking about was it just literally setting there doing absolutley nothing...Mobile AP draws alot of battery
[Captivate Android Development] irishvandal:
hell with it,

okay existz, i cant stand it. i got 4.4.20 stock and 1200 prepped and ready. its been almost an hour and shown about as much restraint as possible. lol. i have got to come home now.

one q, kf1 bl and 4.4.20 haven't shown any compatibility issues have they? heading to bed and rollin xda mobile till i pass out.
[Captivate Android Development] existz:
Nope, im using KF1 bootloaders myself, no issues
[Captivate Android Development] irishvandal:
cheesy-breezy. i am onboard again. i got till monday to play with the phone, so i can throw some beta dayz ur wayz. tnx for the quick reply as always.

flashin in my sleep. lol. gn brotha.
[Captivate Android Development] rlorange:
I agree with Existz for using tegrak oc.

Free version you can go to 1.3ghz and use voltage control or control freak to UV all frequencies. This is what I used until I got the paid version.

Tegrak paid version go all the way to 1.6ghz but at Existz mentioned jumping all the way back to 800mhz may mean previous very Oc are no longer as stable.

Tegrak ultimate allows CPU changes in 4mhz increments and UV/OV in 1mv incrememts so finer control. And internal voltage control not just core voltage. So far at 1.344ghz and ONLY 1320mv but showing slight UV stability issues ie right on the limit.

My biggest worry and the reason I won't use the apply boot option is that tegrak doesn't use the same voltage tables and init.d script so no way clear bad settings in recovery.

**Simply Honey3.9, Talon kernel1.3ghz**
[Captivate Android Development] TwinkyOfHope:
I've had the "charge bug" every single day for what seems like forever. I just charged to 100%, pulled out the charger and it stayed.

Feels awesome. Hopefully all goes well with the kernel. Thank you existz!
[Captivate Android Development] pikachu01:
After studying the code, I can conclude that the battery now shows the "truth".

I used a USB charger to charge my phone. After the 100% notification popped up, I left it there for another hour or two. I checked back and the battery was 96%. I unplugged it and it stayed 96%.

My conversation with existz on IRC:

Code snippet

On another note, official XXJVR is out on Switzerland.
[Captivate Android Development] Drew489:
Feel like a dummy but I can't remember and can't find the answer...do we have to disable lagfix before flash?
[Captivate Android Development] Wdustin1:
For flashing just the kernel, no.
[Captivate Android Development] pikachu01:
Never had to disable lagfix to flash. You can try not disabling lagfix and flashing. Be sure to have a nandroid backup :)
[Captivate Android Development] fuloplori:
Voltage settings r sticking fine on t19 and 20 over here (using vc) also charge stays @100 upon unplug right after prompting full (i9000 bootloaders)
[Captivate Android Development] RashaMatt:
I can confirm that in .20 the battery display (percent charge) is now accurate - good work there.

However, the bug remains that (at least sometimes) after reaching full charge and still plugged into the charger, my battery just discharges all the way down... it never resumes charging when reaching 95% (or wherever it's supposed to kick back in). I'm looking at 71% right now, and still falling. At least it's accurate now so I don't have to use the battery status screen to see what's actually going on.

In my battery status screen, "battery status" field is still "full" (at 72%!) instead of "charging", though everything else (voltage, percent, etc) looks correct.

So if someone can find the code responsible for toggling charging back on after the battery falls below the lower "full" threshold, there's a bug in there somewhere. Good luck...

P.S. That code is ridiculous... weren't exceptions invented so we wouln't have to write like that any more?

_________________________________________________________________

AT&T Captivate SGS I897, Serendipity VII b.1, TalonDEV 0.4.4.20, KC1
[Captivate Android Development] VFO:
I am experiencing something odd on 4.4.20. For the first time since running Gingerbread I woke up without the phone saying 100% and then un-plugging to 88%. Great work existz! So far running very smooth on the latest test. One thing that through me off however was when charging, the phone reaches 100% and then stops charging. This is visible using BattStat and you can actually see that once it gets to 100% it goes from displaying "charging" to "percent". This differs greatly from previous Kernels where as long as it was plugged in to the charger it displayed "charging" even if it was dis-charging. This behavior shows a profound change in the way the battery is handled with the latest code changes.
[Captivate Android Development] killer_raj:
watsa told me abt this and i just flashed to test...

bug is still there.

i flashed it before 6 hours...and that time my battery was around 30%...then after plugging it in i went off to sleep..

so i m on apex..and my battery % mod is on...

so once i noticed when i woke up just to check my phone..that my batt percent was showin 97% and there was battery full indicator was showing 100%

i didnt take out the plug..and slept again...

now when i woke up my phone batt indicator was showing 90% and batt full indicator was also there...

now i replugged the charer..and now its takin charge again..and reached 98% and got the 100% full indicator flashin..

now i m givin it bump charge for 100%

so the conclusion is..that same bug is still there..

but there is an improvement...that atleast now it shows the real status of the batt % without unplugging...

baby step.... :)...hoping to get it permanently solved

EDIT : now after few tries of bump charge..both the indicators r 100% and after unplugging also batt status showing 100%...just like any other kernal...
[Captivate Android Development] pikachu01:
Guys, the reason that it stops charging anymore is to prevent overcharging. True, there should be a code that should restart charging once it goes under that threshold, but what number should it be to satisfy everyone?

And remember, this affects ALL android devices and it's not a bug.
[Captivate Android Development] Peaster111:
My vote would be 90%. The 95 to 100% range is basically full and in the topic tolerance of the battery... so we give it another 5% to discharge that would put you at 90%. I would expect most would be OK with a charge in the 90's. I doubt the same would be true for the 80's.
[Captivate Android Development] daverup:
Another thought,

What if the charging code has the ability to detect bad calibration and disable the top off charging if the calibration error exceeds some preset tolerance.
[Captivate Android Development] pikachu01:
It takes around 20mins to charge from 90 to 100. In the time we would sleep, we would've already done 5-6 times of charging. That is 5-6x of unecessary charging that we made.

Edit: Oh, there's no code to do that yet, and we're not even sure if it is possible with the Android power framework. And this is how it has been since Android was made.
[Captivate Android Development] rajendra82:
The charge bug is still there, sad to say. I have three android devices, all running different flavors of Gingerbread, and the "bug" is unique to the Captivate (and other Galaxy S phones). All the other devices show less than 100% shortly after disconnecting from the charger. Only Captivate keeps discharging past 95%. I know that there is logic to let the charge level drop from 100% to 95% before starting to apply current again to charge back up, as this protects the battery. The bug is in the applying current back part still not being reliable.

I do see an effect of the new code change. Before the current version, the indicator while the phone was plugged up, and in a discharging after a momentary full charge state, would say 100%, only to drop immediately to the real charge level upon unplugging. Now the indicator shows the real charge level, so this morning, my phone was plugged in overnight, and had a charge level of 68%. This could be a sign of progress, if the code that reapplies the charge would just recognize this, and kick in.
[Captivate Android Development] Peaster111:
I wouldn't worry too much about the extra charge cycles. Lithium Ion batteries are immune to repeated charging.

... I forgot to mention my phone accurately displayed the battery level this morning... Unfortunately it said 88%. I was able to disconnect and reconnect the charger for about 20-30 minutes... ended at 96%.
[Captivate Android Development] carey:
Flashed .20

Plugged phone in over night

Unplugged... 80%

I am seriously thinking it is time to stop fighting with this phone and gingerbread. You devs have done quite a lot, but it seems like you've been chasing your tails the last several versions.

I came, I saw... I left confused
[Captivate Android Development] mrhaley30705:
Thomas Edison made almost 2000attempts at making a lightbulb before he found the one that worked. Existz had only made a couple hundred at the charge bug. Be patient.
[Captivate Android Development] Peaster111:
Awesome analogy! Very true. The effort on this kernel is amazing. It is very close to a RC candidate. If you want to be reminded how far its come, flash an early 4.4.x. version
[Captivate Android Development] rajendra82:
Lithium Ion batteries are not immune to repeated charging cycles. They are rated for 500 full Depth of Discharge (DoD) cycles, at which point, they typically reach 70% of their original rated capacity. They also do better with less DoD than 100%. They will typically last 1500 cycles at 50% DoD, 2500 cycles at 25% DoD, and 4700 cycles at 10% DoD.

As a result of the charging bug, there is going to be a faster loss of battery capacity, because each DoD cycle is deeper than it would have been if the software was functioning correctly. You are not likely to feel the effect of this during the 2-3 year useful life of the phone, but it is a less efficient use of battery.
[Captivate Android Development] IDoMy0wnRacing:
I had the phone plugged in last night and the phone had charged to 100% by 11:00 P.M. So I left it plugged in when I went to sleep until I got up in the morning at 5:30 A.M. and the phone had stopped charging but the battery indicator was reading 89% before I unplugged it. I had to unplug and plug it back in to get it to recharge to 100% for the day.

At least it didn't read 100% and unplug to 89%. It read 89% before unplugging. Also, It seems that the phone doesn't discharge at an accelerated rate while plugged in after it stops charging.
[Captivate Android Development] Jep56:
I can sure as hell deal with being at 95% with these ROMS, then to have 100% and deal with the stock BS!

Thanks to all DEV's for their work!
[Captivate Android Development] killer_raj:
yes...there is a saying..

to get something u hav to sacrifice somethin else...

its just depends on us that what r we ready to compromise...

so if we need modification..then who cares so much abt changin the batt in 1 year...as it is people r changing the phone almost every year...
[Captivate Android Development] IDoMy0wnRacing:
I wouldn't say that the charge bug is fixed. But it is much better. After being plugged in for 6 hours after reaching 100%, the phone was reading 89% before I unplugged it, and continued to read 89% when I unplugged it.

The phone doesn't discharge at an accelerated rate any longer if it is left plugged in past 100%. That I didn't like. For example if the phone is charged to 100% and I left it plugged in for a few hours it would read 100% and unplug to 69%. This part of the charge bug in my opinion has been corrected.
[Captivate Android Development] Darryl Henley:
I hate to be that guy, but, I have never had the charge bug with talon and .20 is working great.
[Captivate Android Development] cnu4u:
Things like "stop charging after 100%"are made for safety precautions. Not sure if we need to care about 5-10% when we have remaining 90-95% to use....

Main thing we might need to care about at least for now is memory leakage and our support to team to find it...
[Captivate Android Development] olo567:
I consider myself very lucky. I've never unplugged my phone and had the indicator at less than 96% with any ROM/kernel.

Great job on all aspects of the kernel existz, hopefully you can solve the issue for everyone else!
[Captivate Android Development] melvinaury:
I was using Congnition 5 2.3.3 and on the ROM if you let the phone charging at night in the morning it indicata 100% and if you disconnect it continue to show 100%.

It's there's a way to see the code of the ROM for the charging module and applied it to the Kernel? I was just thinking like a crazy man. Any thoughts.
[Captivate Android Development] Wdustin1:
It is weird how some phones do it and some don't. My wifes phone is a 1010 ans mine is a 1007 she has never had the charging bug yet I have it on my phone about every other day.
[Captivate Android Development] pikachu01:
What kernel is in Cognition?
[Captivate Android Development] rajendra82:
I have a build 1007 as well, and it can go a week or two without having the charge bug, and then all of sudden for a couple of days drop below 95% while on the charger.
[Captivate Android Development] rajendra82:
Cognition has an older TalonDEV kernel in it.

Edit:

Sorry. I was thinking of Continuum. The latest Cognition is a totally different kernel, based off the i897 UCKF1 leaked binary with a a modified initramfs. May be in a future Samsung release for i9000, whatever they fixed during that build will be added, and the charging bug will go away.
[Captivate Android Development] topiratiko:
The reason this is so weird is because its INTERMITENT. The fix/problem is there. It just has to be found. Existz is there any reason to think ditchin the infuze charge source and goin back to cappy/i9000 would help? prolly not lol

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] shopealope:
I updated to 0.4.4.20 last night and my phone wont charge past 97, otherwise it works great. I run continuum 6.1 on my phone.

Sent from my Beast-Associated Captivate
[Captivate Android Development] nappent:
I updated to .20 last night as well. I'm running continuum 6.2 beta. Phone was charging all last night but was powered off. Unplugged the phone and powered it on to see it showing 99% this morning. So far charge bug seems gone for me. I will try again with it powered on and charge to see if I get the same results.