yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Peaster111:
Indeed... I agree regarding the cycles. No battery is completely void this. If it was, then I want stock in that company, as they have invented a battery that lasts forever. The eventual cycle degradation must also be balanced with expected cellphone product life. As you said... On average, cell phones are a 2-3 year product cycle. One cannot expect a battery from a two year old phone still have the same capacity it did new. Repeated cycling may be less than optimum, but it is not likely to be an issue given the life expectancy.

Regarding my immune comment... I was referring to memory retention of Li-Ion batteries. Li-Ion batteries don't retain "memory" similar to, for example, NiCad's. NiCad's usually will have a capacity issues due to improper charging (for NiCad), which is pretty common. This will appear to the "user" as capacity loss, which can be rectified by "retraining" the battery. Li-ion have no such issue, so repeated charging is not an issue for that.

To summarize... While all batteries are affected by repeated charges cycles, Li-Ion batteries are not affected by "memory retention" issues affecting "capacity". This leaves us with battery life expectancy (duty cycles) of our Galaxy S phones, which is not likely to be an issue given life expectancy.

Back to our "charge issue"... It appears that exizts has solved one very important part of the equation... the accuracy. The second issue is "restarting" the cycle when the capacity dips below "x" (say about 90%) while plugged into a power cable. This second issue could not be accurately identified or resolved with having resolved the first.
[Captivate Android Development] melvinaury:
In Cognition 5 it's a kernel name Cognition Kernel Beta 2, But I use the Odin (KF1) Gingerbread 2.3.3 and don't have the charging bug.
[Captivate Android Development] holeindalip:
Mine wouldnt charge past 95 until i wiped the battery stats hope that helps somebody
[Captivate Android Development] cyberbandit1998:
I am on 0.4.4.20 charged to 100% and stayed there.Going for 14 hours and still at 40%.
[Captivate Android Development] killer_raj:
when u put ur batt % then u shd put ur usage aswell..coz thats the main thing
[Captivate Android Development] oriveradel:
Alright...doing good on version .20 same usage as everyday..7.5 hours into it and still have 63%...no other problems found...smooth... Mind you that I switched to jjv5 modem that might be helping too..

Tegrak OC 1200...with noop gov
[Captivate Android Development] cyberbandit1998:
Display 44% Calls 3%

System 11% Internet 2%

Cell 11%

OS 4%

GO SMS 4%

Idle 4%

Maps 4%
[Captivate Android Development] cnu4u:
Strange problem to report... Just now I am out of my office and made an attempt to call... Though I got full signal it is not through... I made into airplane mode and after a minute or two, tried to turn back to normal and it didn't let me... Powered off the phone and didn't restart :(

Pulled battery and plugged in back to make it work
[Captivate Android Development] Reynaldinho111:
So i flashed .20 last night and left my phone on while it was charging overnight, for the first time since moving to gb i woke up and unplugged to see my battery at 100%. Existz and crew, you guys are awesome, youre definitely on to something and hopefully we'll see all these gb bugs squashed in the very near future. Thanks guys

sent from my beloved cappy!!
[Captivate Android Development] eep2378:
ok i flahed .20 but when i try to power off my phone to bump charge, it boots up when i plug the charger in??
[Captivate Android Development] LNJ:
I never had the charge bug before but with latest version, I now have to worry about unplugging when fully charged cause if I leave it plugged in, it drains like normal and doesn't charge back up until it is replugged in again!
[Captivate Android Development] eliminat:
With .20 my phone charges then drains, and has also restarted randomly while not in use a couple times. Didn't have these with .18 . Using On-Demand X.
[Captivate Android Development] pikachu01:
Guys here's a real fact:

The battery indicator lies to you when you charge to 100%. When you unplug, it'll show you a number that will be near 100% or even not 100%.

No Android phone in fact, has the ability to recharge after it drops to a certain threshold (from my understanding). Right now you're getting the TRUE battery indicator that is an accurate representation of your battery life.
[Captivate Android Development] existz:
Check your OC/UV.., with 18 down UV was not applying correctly, now it is actually working..so you might have to adjust it..
[Captivate Android Development] rlorange:
@Existz is there an app or terminal emulation command I can use to check actual voltage for each frequently? Tegrak is setting only the 800mhz value in the voltage table which was recently fixed for other voltage apps. If there is a conflict I will use tegrak for oc/UV

For the top frequency only and control freak for the others.

Edit: edit also BOGOMIPS reading in several apps shows 797 at stock settings on 1200talon. Indicating the 800mhz frequency. Stability test app will not scale to 1200. Havn't tried the 1000 version.

**Simply Honey3.9, Talon kernel1.3ghz**
[Captivate Android Development] lowlymarine:
I'm at about 30 hours since last reboot on .20 and regretfully the memory leak still seems to be in full force. The phone is practically unusable at this point. Going to reboot now, just thought I'd pop in first. But it sure sings after a fresh boot with these latest kernels, excellent work, and I'm sure you'll quash the leak sooner or later.

Sent from my Galaxy S
[Captivate Android Development] existz:
Do you think you can test and see which version it started with? I dont have much time to go through all the test to see ATM, but if you could find exactly when it started, it would help me to eliminate it quicker
[Captivate Android Development] iamprayl:
Therse seems to be an issue while on deepsleep. Just now after 6 hours of deepsleep I can't open my phone from deepsleep state. Can someone point me what seems to be the problem. But i dont think its the latest update coz I've gone through all updates but none like these happened to me.

UV Settings before I got these prob:

@1200: -0

@800: -50

@400: -75

@200: -100

@100: -150

Phone: Samsung Captivate

Kernel: TalonDev Kernel 0.4.4.20

ROM: Sensation ROM 2 with

i9000 Bootloader
[Captivate Android Development] rajendra82:
You may be undervolting too much at the 100 and 200 MHz. You did not see a problem before, because the bug prevented from those uV settings to actually be applied.
[Captivate Android Development] hobbs:
Is anyone having trouble with netflix? I can't open up netflix app. It just gives me black screen. It was working fine last week but I don't remember which version of Talon I was on when I used netflix last. I am running Continuum 6.2.1. no OC/UV
[Captivate Android Development] LNJ:
I also noticed that when I don't UV, the phone is more responsive then when I UV and have a saved boot setting.

Anyone else?
[Captivate Android Development] rajendra82:
That is absolutely not true. I have a Nook Color and HTC Status, and both work just fine when left plugged in for an extended period of time. They fully charge battery, then let the charge level drop down to 95% and then charge it back up close to 100% again. Some phones seem to lie about the actual charge level while doing this cycling and keep showing 100% until you unplug, when the finally show the real charge level, somewhere between 95 to 100%, while others tell the actual level, as it drops and rises. No other phone than the Galaxy S on Gingerbread actually let the charge level keep dropping below 95% while still being plugged in. Li Ion batteries have been around a long time, and even the earliest dumb phones know how to charge the battery, and hold it close to 100%, so that the phone will be fully ready to go when you unplug. Even our own phones under Samsung Froyo, CM7, or i897 2.3.3 leaked firmware do not exhibit this buggy behavior of letting the charge drop below 95% while plugged in. It is a bug specific to the i9000 2.3.4 codebase.
[Captivate Android Development] Koizuma:
That might be some phones have different tolerances when it comes to voltages but for instance my UV is:

1200 MHz @ -100mV

800 MHz@ -100mV

400 MHz@ -125mV

200 MHz@ -150mV

100 MHz@ -150mV

And mine runs perfectly happy.

Swyped from my SGH-I897 using XDA App
[Captivate Android Development] topiratiko:
I run 125's all the way down

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] rajendra82:
I agree. Each phone is different. The only way to be sure is to disable all states above the one you want to test, and run stability test for 50 cycles (which can take 12 hours at 100 MHz). If Stability Test can pass at the set undervolting level on each frequency, then your phone can likely handle it in real life situations.
[Captivate Android Development] existz:
Yea, all phones are different.. some can handle 125 on a certain frequency, some can only take 25.., usually to much UV on lower frequencies is what causes sleep death.., also having sleep profiles below 800mhz can also sometimes cause it
[Captivate Android Development] existz:
Nevermind, I figured it out.., started with 0.4.4.16, and i think i know whats causing it
[Captivate Android Development] nh5:
Anyone having problems in the recent talondev im on .20 now, wondering if anyone has issues with the phone waking up for calls. Gotta hit the power button like 3 times before it wakes up. Might be related to the proximity sensor. I also have a UV schedule set.
[Captivate Android Development] existz:
Are you using Ondemand or OndemandX governor?
[Captivate Android Development] rlorange:
Beat me to it!... also it seems tegrak oc ultimate is writing to the UV table but only at 800mhz... I'm assuming that the two anomalies are related.

Edit: also spying on tegrak profile settings I think the ultimate app only actually changes frequency in increments of 5mhz

**Simply Honey3.9, Talon kernel1.3ghz**
[Captivate Android Development] topiratiko:
Prolly on demandx....anyway we can change it from 95 to maybe 82-85 ish?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] pikachu01:
I only know about Droid not charging after having it full. Not sure about other phones (hence, the "to my understanding"). It might be that those phones might be lying to you all the way (Hence, you might really have 50% battery from not charging but battery scales down from 100 to 0 but in actuality it is 50% - 0%). Battery stats is the one responsible for this as.
[Captivate Android Development] existz:
You can try.., reason I say "try" is because in the notes with OndemandX it says it does not support sysfs, BUT even though the sysfs files are not in /sys/devices/system/cpu/cpu0/cpufreq/... , it is in /sys/devices/system/cpu/cpufreq/.., im not sure if it works or not.., but you can try ...

echo "80" > /sys/devices/system/cpu/cpufreq/ondemandx/up_threshold
[Captivate Android Development] nh5:
@existz Forgot to mention earlier running ondemandx. Just did some testing is only happening in ondemandx
[Captivate Android Development] irishvandal:
exists,

everything is rolling fairly well. got a bit of lag under 4.4.20 1200 stock uv using tegrak, ondemandX after 3-4hrs. i am going to point the finger at some apps that were hungry for attention. i have disabled them or flat-out uninstalled them. still in the first 24 though so dont take this other than me throwing pennies out.

btw, where can i place my bootanimation now under 4.4.20? and is it named bootanimation.zip or sanim.zip? or possibly not enabled at all? curious minds want to know. lol. The bootanimation is sanim.zip. Sorry:p, guess it didnt stick the first time.

keep chugging bro, its def in the right directions, batt stats are on point and only had a 1% drop upon disconnect. ondemandX seems to be helping with batt life so far as well. the lag before is my only concren right now and cant not put a finger on it in any direction.

tnx again ahead.

EDIT -

my calls have been spot on. no issues what-so-ever within the first 24hrs.
[Captivate Android Development] Koizuma:
Lucky, I tried running -125 all the way down my phone didn't kilter that to much lol

Swyped from my SGH-I897 using XDA App
[Captivate Android Development] magistrateee:
What Stability Test is this? Is this a certain app?
[Captivate Android Development] existz:
So ive got the BOGOMIPS issue fixed, was due to compiling with O3, so I reverted back to O2, I have no clue about Tegrak, theres no sources so I do not know how it exactly works, nor fix any bugs with it (can only support Voltage Control, Control Freak.etc).., plus fixed a few other small things.. Should have 0.4.4.21 up in the morning sometime.., will also include a 'BETA' version of MemoryFreak for everyone to try out...Which shane87 is working on a few things before making an official release, but we will see how the BETA goes just as a trial run.. Also I might set the up_threshold to 80 with OndemandX to see if it helps any
[Captivate Android Development] rlorange:
You might get source code for tegrak as since it's a kernel module some are pushing for release as it should fall under gpl licence... or something like that. Cool Existz ill stop distracting you now lol!

**Simply Honey3.9, Talon kernel1.3ghz**
[Captivate Android Development] TwinkyOfHope:
I'm also on .20 OndemandX, and I just realized this was happening to me today as well.
[Captivate Android Development] RashaMatt:
With .20 ondemandx, my phone seems laggier, sooner, than .18 did with ondemand.

____________________________________________________________

AT&T Captivate SGS I897, Serendipity VII b.1, TalonDEV 0.4.4.20, KC1
[Captivate Android Development] Rrryan2:
I've been wondering if that might help too. 95 seems like it might be a little too severe, as the phone feels very slow to spin up from wake even when just trying to do some pretty banal things like email etc.

I've also been toying with the idea of disabling the 400MHz or 200MHz step as well to see if it helps smoothness and transition from sleep to in-use profile. They typically only show 1-2% in CPU spy anyway.

Even without trying to answer a call, I've had to hit the power button twice or more sometimes to get the lockscreen (pattern unlock) to come up. I suspect the CPU more than the proximity sensor though, as above.

It's supposed to in a sense. OndemandX is mostly intended to save battery by throttling up the cpu state at slower rates. Keeping the CPU at lower speeds longer saves battery but reduces performance.

I'm also still having problems with an apparent memory leak which sets in after long uptimes, which may be affecting you as well. The good news is that it seems in .20 is seems to be reduced as I've now gone about 30 hours without having to reboot, it's just still not gone. After boot I usually have 246-ish/339 MB in use, which slowly climbs with continued use. At present after 30 hours I'm usually in the 300s-310s when the phone is in use, and "Clear Memory" in Task Manager only gets me down to 297MB in use - with no applications running.

Something is sipping memory and not releasing it, but I don't see any smoking guns in Battery Usage, Running Processes, or Watchdog.

Again however, it seems improved in .20, takes longer to set in and lag isn't as severe or "crashy", and it goes away immediately upon reboot.

I haven't observed the "charge bug" in .20 but I never noticed it before either and my phone seldom sits on the charger at 100% for very long anyway.

UPDATE: Actually, while "Clear Memory" would only get me down to 297MB before, now it gets me down to 282. Without rebooting inbetween. Weird. I'll let it go as long I can stand without rebooting and see what happens.

UPDATE #2: About 5 minutes after I wrote the above, I installed the new Firefox 6 to see if it was finally worth bothering with. Phone locked up on the first page and then did a soft *shutdown* while on the charger. :(
[Captivate Android Development] Peaster111:
Good summary... Now that the accuracy piece of the puzzle is fixed, hopefully this remaining open "charge bug" issue can be fixed.
[Captivate Android Development] rajendra82:
It's a free app in the market.

http://intostudios.com/stability
[Captivate Android Development] eliminat:
I actually don't UV at all. And OC is the standard 1200 MHz. Been using On Demand-X.
[Captivate Android Development] nyydynasty:
i noticed that while running .20, it can (sometimes) take up to 15-20 seconds for the phone to wake up from a sleep state after I press the power button. Probably happens once a day.
[Captivate Android Development] eep2378:
Woke up this morning to sleep death(unplugged). I'll have to adjust my uv settings accordingly. I was -150 on 100, and -125 on 200. I had used these settings on previous vresions of Talon without issue. New improvements require uv adjustment I guess.

Also, after powering phone off completely, plugging in the charger reboots the phone automatically instead of charging while off! Anyone else, seeing this?
[Captivate Android Development] Rrryan2:
Was happening on JVB and other pre-2.3.4 builds before too. When 2.3.4 hit, people initially thought it had finally been fixed...

UV wasn't being properly applied on the most recent Talon test versions, which was fixed for the latest builds. Now that's it's working properly you're seeing the consequences...?

Just tried mine to see. Powered down (with charger already disconnected), connected charger and it went right to the "green battery" screen and then powered down the display like it was supposed to...
[Captivate Android Development] eep2378:
Interesting, I tried to power down last night like 2-3 times and it just rebooted, no "green battery" screen.

yeah I'm using control freak, and I've adjusted my settings(not as aggressive) and all seems good so far. We'll see how the day goes :)
[Captivate Android Development] topiratiko:
Awesome! I remember messing with up thresholds on setcpu when i was having sleepdeath issues...i believe i had mine set at 88 or something like that...going above 92 i would have issues..80 seems like a good number

Curious to see MF although i dont think im gonna mess with it too much ive seen enough ram/lmk/vm swappiness/adj_lvl the past 2 weeks to last a while....but u know how it goes thats what i say now but when its out ill be ALL over it....

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] existz:
0.4.4.21 Public Test

0.4.4.21

Changelog since 0.4.4.20

- introduce MemoryFreak by shane87 (beta)

- fix for sdhci regulator support (upstream)

- improve USB signal quality (AOSP/Samsung)

- revert back to compile with O2 CFLAGS

- some minor cleanups and fixes to cpufreq

- set up_threshold=80 for OndemandX governor

NOTES

Now Talon includes 'MemoryFreak' by Shane87.., this is a 'BETA' version, so treat it as one..Shane87 is working on a few things before its an 'official' release..If you have any bug reports about MemoryFreak, please report to Shane87.., also give a huge kudos to him for creating this app for us.. Theres a 'Help/Tips' button in the app if you need a brief description on what each setting does. The 'Hidden App Min Size' custom slider is only present with 'Talon' settings.. Settings do not take effect until reboot, you can either Save settings, which just saves them to ram.conf ..use this is you do not want to reboot at that exact moment (reboot is needed though for settings to take effect).., or Apply them which saves them followed by a reboot.
[Captivate Android Development] xTRUEx:
what is this memoryfreak that u speak of?
[Captivate Android Development] nyydynasty:
F5

*check the post*

damn

F5

*check the post*

damn

......
[Captivate Android Development] shak0569:
LOL me too!!
[Captivate Android Development] existz:
It is back up ...sorry about that, forgot to change up threshold for ondemandX.., then for some reason 1ghz version was showing 5.64MB, and 1.2ghz was showing 5.63MB.., so had to recompile the 1.2ghz and reupload, now all is good
[Captivate Android Development] nyydynasty:
i'm totally kidding with you :)
[Captivate Android Development] existz:
Its an app that now lets you easily adjust your LMK settings (properly with Talon, instead of how most 'ramhack' scripts and memory apps that just changes the kernel parameters, this actually sets it correctly).., you have 3 different presets, 1) Stock Samsung SGS settings, 2) Stock Nexus S settings., 3) Talon default settings.., as well as having the option to adjust 'Hidden App Min Size' on the Talon preset.., the lower your set it, the more performance you will have, but NOTE that you are sacraficing multitasking.., if you adjust it higher, it allows more apps to be stored in memory, giving more multitasking.. Also you can adjust the ZRAM Size, 0=disabled, Max = the more ZRAM compresses and stores RAM, and swappiness settings, 0=disabled, Max= how often the kernel will swap...
[Captivate Android Development] xTRUEx:
what settings do you recommend/use?
[Captivate Android Development] geokilla:
If Memory Freak settings aren't applied until after a reboot, then temporarily applying the settings without reboot would nullify the changes wouldn't it?
[Captivate Android Development] existz:
Its all up to you.., thats the whole point of the app, so users can fine tune things if they are not happy with the current setup.. I personally use stock Talon settings, they do great for me..But if you dont want as much multitasking then you can tune the hidden app mem size, zram size, swappiness..etc.., if you want more multitasking, same thing goes, you can adjust it the way you want it..but theres nothing wrong with default settings
[Captivate Android Development] existz:
Right, they do not take effect until after reboot...But the point of just saving it, is if you want to go ahead and apply the settings but you do not want to reboot at the moment.., however it will go ahead and write the changes to ram.conf, but they do not take effect till reboot
[Captivate Android Development] nyydynasty:
like anything else, leave it default and see how it performs. No use in adjusting something without knowing the baseline performance.
[Captivate Android Development] topiratiko:
Can someone post what the stock nexus s lmk values are? i dont want to change my custom settings...im just curious.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] geokilla:
So what you're saying is, it's just like the UV/OC changes. They are applied temporarily but gone after reboot unless you press save as boot settings?
[Captivate Android Development] Holmes108:
I don't think so. I think it just allows you to set it up for next boot, even though you aren't ready to reboot right then.
[Captivate Android Development] existz:
No, none of the settings will take effect until you reboot..

Save = it does just that, saves the settings to ram.conf, but are not in effect until you reboot ..use this if you do not want to reboot at that moment

Apply = saves the settings to ram.conf, then prompts to immediately reboot.

If you just want to save the settings but not reboot at the particular moment, just use save ..(settings do not come into effect until a reboot though)...use Apply to immediately save and reboot ..
[Captivate Android Development] daverup:
Thanks!!

Thanks to existz and shane87, Awesome job!

4.4.21 Flashed and running smoothly so far. MemoryFreak runs ok for me, but I'm not adjusting anything yet.

:D
[Captivate Android Development] manny05:
Running pretty smooth so far.

Just can't wait to overclock higher than 1.2

Captivate running dlev's latest rom

Talon kernel/snail

Overclocked and undervolt
[Captivate Android Development] FocuseD83:
@exists wasn't the up_threshold 95 in test 20? Is there a way to edit that setting to revert it back manually? Didn't have any problems with that setting on my phone...

Sent from my Gingerbread Cappy