yashsingh1/xdaforums huggingface dataset:
[Fascinate Android Development] zeroxg4:
Yeah im on the stock sd card and am running voodoo of course. I don't even have quadrant as I only use linpack. Its weird because I used to get those high scores before with the version of otb that came before this (before reloaded) but it was not as stable. In terms or real word performance though, my phone has never been snappier than it is with the newest iteration of this kernel. Im just curious as to why a benchmark such as linpack would not reflect it.
[Fascinate Android Development] saps:
That score just means you are at 1ghz, if using this kernel make sure you enable the higher states
[Fascinate Android Development] zeroxg4:
Of course, all of the states I wanted to use were checked when I got that result.
[Fascinate Android Development] stephenj37826:
Did you up the maximum clock speed
[Fascinate Android Development] saps:
Yeah if you truly are at 1.3 Ghz your linpack will be around 18, it can't not be
[Fascinate Android Development] zeroxg4:
*facepalm*

wow. can't believe I overlooked that :o
[Fascinate Android Development] stephenj37826:
How is it doing now ?
[Fascinate Android Development] neyenlives:
My battery life with the before mentioned settings was drinking battery like a hood rat drinks cool-aid in the summer in Atlanta. I checked stats and it showed 100Mhz as being 60% used with trailing up to 1300Mhz being only like 3%.....so it wasn't like something in the background was running off. 6:30am to 12noon and it was down to like 15% at which time I put it on charge. No music, no calls, a few texts, few web pages browsed, maybe three hours on wifi the rest on 3G. Two email accounts set to instant notification and screen set to autobright. Normal use for me is this way but also listening to music several hours a day and I can go about 12 to 16 hours with default clocks and -50mV on all steps.

Its fun to overclock and bench but I need all day battery and to be honest I played with this at overclocked settings last night and only benchmarks were faster. It still texted, called, emailed and surfed the same speed so no use in giving up battery to say it runs 1300Mhz.
[Fascinate Android Development] nemesis2all:
When you change settings you need to give battery time to re calibrate. If you don't give phone a chance to do that then you will never realize the benefits of uv.
[Fascinate Android Development] saps:
Yes like the master says, often times its the second charge cycle when you begin to see the gains from a uv. Equally, true this phone is darn fast at even an 800Mhz top step. However as aforementioned, the real battery saving do come when screen is off and phone is asleep. Under use even the difference between 800mhz and 1.3 ghz is not as great.
[Fascinate Android Development] neyenlives:
i realize that....but it was already well cycled in.....are you saying by simply extending the available frequencies somehow changed battery calibration because i could see it is i had changed voltage values and tweaked a bunch of stuff but all i did was add 1200 and 1300 frequencies and set limit to 1300 and set them the same as the others at -50mV

im not saying i dont believe it but it seems unlikely to me that even after doing so that i would get better battery performance running 1300Mhz max vs. stock settings. That was kinda my point, that there's no real world use benefit to running it at 1300Mhz 24/7 and I wasn't lacking speed to begin with so....im trying to focus on keeping clocks as low and lower voltage as much as i can and not impact performance, thus extending battery life
[Fascinate Android Development] scarmon25:
+1 to that. The first day or so after I flashed this kernel my Batt was horrible. Now I get a full day easily out of my phone. With it OC'd to 1200Mhz and Moderate use.
[Fascinate Android Development] nemesis2all:
Im just saying that when changes volts battery may drain like crazy. Adding another step that has different voltage is changing the volts as well. So I'm not sure if what you were seeing was due to that or just extra speed from oc, but you saying you were not spending hardly any time at 1300 leads me to believe battery needed to re calibrate. A quick fix I do to get that process starting faster is after I save my settings that I want to keep as boot settings I will power off phone and pull battery for atleast 30 seconds and then reboot.
[Fascinate Android Development] beray5:
There are 2 power conserving strategies, Eclair mode and Froyo mode, you still are in the Eclair strategic modality. HERE's the answer given to me.

"There is two approaches to handling the processor that people/developers go down (at least as far as this discussion concerns). The first involves the idea of keeping the processor at the lowest power consumption as often as possible. Underclocking is often used as a way to accomplish this, and really conservative usage of the higher power states.

Some smart people got to thinking about this and thought of a much better way to address the problem. If you are doing a processor intensive process, underclocking only makes the process take longer. Wouldn't it be better to get the process done as quick as possible, so that the phone could return to a lower sleep state sooner? As it turns out, this usually ends up in, not only a more efficient power using device, but also a faster user experience. Gone are the days of slowing down your device to a crawl in order to save some battery life."

Simplified answer in the universal language - MATH

Power usage = Fast processing over short period of time (Froyo) = Slow processing over longer period of time (Eclair).
[Fascinate Android Development] luke949:
after many lockups with -50 from 100-1000mhz on CFQ or BFQ scheduler, I just about gave up. But I tried out the NOOP scheduler and it seems to be working pretty well so far. i will update after a few days of usage.
[Fascinate Android Development] AuroEdge:
I want to caution those who undervolt that you need to also investigate your I/O situation. You're significantly increasing your probability of data corruption.
[Fascinate Android Development] Skrazz:
please explain.
[Fascinate Android Development] neyenlives:
I appreciate the insight. Just wanted to update to say after charging it back I changed settings back to where I had them originally, no battery calibrations or so on and now even with heavy use I might have burned 15% in four hours. Back to where it was.
[Fascinate Android Development] neyenlives:
Flash memory is susceptible to low power environments. Or more so the memory controller....things can get corrupt between read/write cycles if there's not enough power to sustain the memory while it is in a volitile state.
[Fascinate Android Development] Daswolven:
I second the recalibration. Before I did, it was draining crazy fast. One full cycle after and I've been sering about 20% more time for my normal usage.
[Fascinate Android Development] suppliesidejesus:
I think the main question is why does the different I/O schedulers increase the risk of data corruption when undervolted, not why undervolting can risk data corruption.

My own question would be does undervolting the CPU also undervolt the NAND and RAM?
[Fascinate Android Development] beray5:
Definitely should be never, it made no technical/economical sense. NAND and RAM power usage is distributive, lowering voltage is not going to save much except leakage power which is so little already.

Exceptions could be made only for very high performance devices which had already been pushed to their limit which would show noticeable power savings.
[Fascinate Android Development] dablitzkrieg:
How are you guys seeing what voltage is being used the most?
[Fascinate Android Development] scarmon25:
Just out of curiosity. What would be some of the "symptoms" of data corruption. Freezing, stalling out or would there be some more specific signs.
[Fascinate Android Development] beray5:
Reboot, forced closed, lost home screen widgets, etc...
[Fascinate Android Development] scarmon25:
Good to know. Thanks for the info.
[Fascinate Android Development] luke949:
@dablitzkrieg I use android system info from market
[Fascinate Android Development] dablitzkrieg:
Thank you

Sent with my 3rd leg
[Fascinate Android Development] miah009:
I haven't seen anything about this anywhere.. but when flashing this Kernel, shouldn't it have changed what's listed under the kernel info in my settings, "about phone" page?

It definitely feels like things have changed for the better, with this kernel, but for whatever reason it still shows what it read at bloated stock ed01. 2.6.32.9

-sorry if this has been answered previously.
[Fascinate Android Development] scarmon25:
Mine had never changed under settings. I believe it is because they are all built off that source so that's why it always shows the same version. If you use the app cpu spy. It will show you the actual kernel info including version and so forth.
[Fascinate Android Development] CrucialBT:
That's normal. The kernel version will likely never change from that until a gingerbread kernel/rom is released. The only thing that changes from kernel to kernel is the "tag" from the compiler usually something like "someone@somedomain" which you'll need either a terminal emulator or some type of system info application to see.
[Fascinate Android Development] miah009:
this is what I was looking for, or at least felt like was missing. I work with a few people with rooted captivates, and vibrants, and all their custom Kernels show the creators tag's underneath.
[Fascinate Android Development] GoBruins:
Just a curious question... What are the negatives of over clocking? Lower battery? Increased temp?
[Fascinate Android Development] stephenj37826:
Well an overclock to say 1200 set at say 1250 mv would give you increased performance with in my opinion better battery life without much extra heat. Theory is if the cpu can get done computing faster then it can return to a lower state quicker. Also at those settings I don't believe it would be pulling much more power than stock 1ghz and would in theory get done with a certain task 20% faster leading to better battery life.
[Fascinate Android Development] johndolle01:
Anybody able to get 1500 or 1600 speeds I would like to know your settings. My fascinate does fine at 1400 with a slight uv but when I try 1500 it might work for a few minutes and then locks up.
[Fascinate Android Development] stephenj37826:
I run 1500 @ -125 (1375 mv) I'm still on 1.2 but there should be a 1.4 release today as it is in the new comm rom
[Fascinate Android Development] beray5:
Here you go, I pulled it from the comrom.
[Fascinate Android Development] saps:
Any info change log wise regarding 1.4?

I ask in part because 1.2 is more stable for me than 1.3. Won't move to 1.4 without just cause
[Fascinate Android Development] beray5:
There are too many changes, I can't follow them all down with 20 minutes of reading. You can read them here -> https://github.com/nemesis2all

But besides others nemesis2all did change the voltage settings, for myself its for the better, 1500MHz seems much better already for the last 10 working minutes trying out.

1600MHz actually working briefly, that's the first time for me.
[Fascinate Android Development] johndolle01:
Thanks is that with ISO scheduler
[Fascinate Android Development] stephenj37826:
Actually cfq
[Fascinate Android Development] PeterGunz:
I was on it for a few minutes, only thing I remember at default the scheduler is sio and he removed (unchecked) the 600 step.

I think that was it, but it was at 2-3am and I was half asleep. No clue on the voltages.
[Fascinate Android Development] ezas:
We got to go over this again.

Too many people are talking about longer battery life.

While you may very well have 'seen' more battery life, You saw what seemed like better battery life because now your phone knows what's full and what empty is. As time goes on it 'learns' your usage patterns and gets better at guestimatting how much battery life you have left. These combine to make it appear you are getting longer battery life.

Now the nuts and bolts:

You can't increase the capacity of a Li-Ion battery pack. Period. And they don't develop memory and can't be 'conditioned' by cycling them. From this site on Batteries: http://batteryuniversity.com/learn/article/the_high_power_lithium_ion

"Lithium-ion does not have memory problems like nickel-cadmium batteries. No deep discharges are needed for conditioning."​

And from this site: http://www.techrepublic.com/blog/helpdesk/the-care-and-feeding-of-li-ion-batteries/124

"The gauge that measures the remaining power in your laptop is based on circuitry integrated into the battery that approximates the effectiveness of the battery’s chemical compounds. Over time, a discrepancy can develop between the capacity that the internal circuitry expects the battery to have and what the battery can actually provide. Letting your computer run down to zero every month or so can recalibrate the battery’s circuitry, and keep your computer’s estimates of its remaining life accurate."​

When you fully charge the stock battery on a Fascy and use something like Spare Parts to see the voltage you will see about 4200mV. After you calibrate it and do a full charge cycle it will STILL say 4200mV. You have not increased its capacity.

And of course calibrating a battery does not affect how your phone's battery discharges. If process X use Y amount of (m)Volts, X is still going to use Y amount of (m)Volts after calibration, all else being equal.

So, same size tank, same MPG, but a fuel gauge that is more accurate and better at predicting when you will be on empty.

If you are curious to learn more about what type of things battery stats can do take a look at Battery Diviner in the Market.

I hope this help clear up what calibrating the battery does and doesn't do.
[Fascinate Android Development] AuroEdge:
I'm glad somebody finally broke this down because God knows I wasn't going to. It's fine to clear your stats when you flash a new ROM to avoid calibration creep. That is it and nothing more
[Fascinate Android Development] ezas:
I was really curious about the whole 'battery stats' thing so I've been trying to find out more and came across this tech sheet for a Texas Instruments Fuel Gauge microcontroller. Now I have ZERO idea about the hardware or algorithm used in our phones, but this give some idea of what is possible. Its from 2009 so it's fairly recent and at the bottom is says:

APPLICATIONS

Smart Phones

PDAs

Digital Still and Video Cameras

Here is the feature list:

Microcontroller Peripheral Provides:

Accurate Battery Fuel Gauging

Internal Temperature Sensor for System Temperature Reporting

Battery Low Interrupt Warning

Battery Insertion Indicator

96 Bytes of Non-Volatile Scratch-Pad FLASH

Battery Fuel Gauge Based on Patented Impedance Track Technology

Models the Battery Discharge Curve for Accurate Time-to-Empty Predictions

Automatically Adjusts for Battery Aging, Battery Self-Discharge, and Temperature/Rate Inefficiencies

Low-Value Sense Resistor (10 mΩ or Less)

Orig page: http://focus.ti.com/docs/prod/folders/print/bq27500-v130.html

Now back to our regularly scheduled kernel thread
[Fascinate Android Development] scarmon25:
Just curious. About the voodoo lagfix. And please know I'm in no way complaining. On the project voodoo website I see that thd GSM galaxy devices are all using the 5.5 lagfix. When I look in the voodoo app it shows ext 4. This has probably been answered but I couldn't find it. What is keeping us from geting the v5 and honestly is there any difference? I love what nem and all the other devs have done. Just trying to understand how that whole deal works.

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Fascinate Android Development] MattRussNC:
I was under the impression that "conditioning" for these phones was relating to the bstat file and not the battery. I thought to condition one must charge to 100% wipe the stats and in order to properly rebuild the file (not the battery) discharge it completely followed by complete recharge. Had heard that this was for rebuilding the file. While called conditioning the battery, never heard anyone actually mean the battery itself, just easier then saying the battery stat file.

Now then again this could also be a myth as far as what it takes to get a accurate file.
[Fascinate Android Development] akellar:
Pretty sure ext4 is the file system not the version.
[Fascinate Android Development] scarmon25:
Ah. Gotcha

Rockin Hienz 57 w/ Ultimate Honeycomb and OTB Voodoo
[Fascinate Android Development] beray5:
Battery calibration is solely for determining full charging capacity, not for discharge (discharge is linear to voltage reading, voltage reading is definitely not linear and nearly useless for charging).

http://xdaforums.com/showpost.php?p=12150257&postcount=40
[Fascinate Android Development] MattRussNC:
My only point was that even though the phrase "condition the battery" is often used in this context, nobody implies or means the battery itself. While the lipo battery may be consistent the phones knowledge of it may need reseting from time to time and thus it was simple to use the phrase condition the battery without implying any changes to the battery itself. Unfortunately i do not really understand how the battery stat file works exactly but i do know it requires reseting from time to time after kernel or rom changes. And doing so while having no effect on the battery can dramatically alter the devices run time.

Perhaps the battery shouldn't be mentioned but i dont really think anybody is believing that the battery's capacity is changing by "conditioning" but i may be wrong. That term just seemed good enough for the process of wiping the stats and at full and letting the phone discharge to calibrate the phone not the battery.
[Fascinate Android Development] beray5:
The battery calibration/conditioning does change the capacity, uncalibrated the default maximum charge is ~85% (normalized default 100% charge), requiring multiple charge cycles to achieve actual 100% capacity.

85% of actual capacity while indicated as 100% charge would make the battery dies faster.
[Fascinate Android Development] ezas:
Thanks for those clarifications. I tried to research to make sure that what I was writing was correct but I never say any mention of the li-ions being limited to 85% before calibration.

I read the article you linked to here: http://powerelectronics.com/mag/50122.pdf

I also found this: http://www.inspired-energy.com/standard_products/Recalibration Notes.pdf which was also a good read.

and this: http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries

And this: http://docs.google.com/viewer?url=h...tandard_products/Smart Battery User Notes.pdf

And a few other sites with semi technical information and I cannot find anything about this 85% initial charge and what its purpose is.

Can you explain or point me towards more info on it?
[Fascinate Android Development] beray5:
Its purpose in battery calibration is to avoid blowing up the phone and accounting for a predetermined scope of battery quality variance. Typically +/- 1dB charge level variance, +/- 1dB depletion level variance, and +/- 1dB intermediate level variance.

Sum total of 3dB variance, the EE equivalent of Standard Deviation.
[Fascinate Android Development] ezas:
Ok that gave me a hazy idea. So it's kind of like a margin of error until the 'gas gauge' circuit starts monitoring the actual charging stats?

Question: If on my first charge to 'full' I pulled up a monitoring app it would read ~3570mV?

I appreciate your effort and patience to explain this stuff in this and other threads. I know it's been helpful to me make some sense about all the anecdotal posts about the battery life getting better after a few cycles.
[Fascinate Android Development] beray5:
Use your battery to some random charge level less than 50%, boot into CWM and clear battery stats. Default battery calibration table will be loaded when you boot back into Android, charge up to 100% and expect the battery longevity to be shorten by ~15% of actual capacity.

If your known idle power usage is 1% per HR then expect loss of ~15 idle hours of power usage.

If your battery happened to be extra great, expect as much as 30% (full 3dB margin) loss of actual capacity. If your battery happened to be bottom barrel quality, your battery status would essentially already be calibrated.
[Fascinate Android Development] allcity187:
This might be a noob question but what is the schedule option in the voltage app for?
[Fascinate Android Development] beray5:
In typical Distributed Processing designs, you typically have simultaneous multiple data streams moving from simultaneous multiple different sources to simultaneous multiple different destinations.

There's sound data streaming to speakers, there's animated visual data streaming to the display, there's GPS satellite streaming data being acquired, etc...

All these I/O data streams required scheduling with I/O schedulers.
[Fascinate Android Development] allcity187:
So what is the best scheduler to use?
[Fascinate Android Development] beray5:
Currently the best would have to be CFQ as BFQ is yet fully implemented, but nemesis2all is just about finishing up with full BFQ implementation.
[Fascinate Android Development] allcity187:
So what's the difference between cfq and bfq?
[Fascinate Android Development] allcity187:
Well I just google io schedulers I found a lot of information. So what schedulers is everyone using?
[Fascinate Android Development] beray5:
They are described here -> http://xdaforums.com/showpost.php?p=13209379&postcount=247
[Fascinate Android Development] AtropineNa:
Voodoo can flash over voodoo without disabling voodoo and whatnot right?

I'm running 1.1 OTB and was just wondering if I need to flash the latest kernel after disabling voodoo, flash latest version and then reenabling voodoo...
[Fascinate Android Development] scarmon25:
Voodoo over voodoo is good. Ive never had issue doing that.

Tap-a-Talked.
[Fascinate Android Development] cvs0115:
Yup... You can do it... Wipe your caches...
[Fascinate Android Development] GoBruins:
Just wanted to share my experience with the awesome kernel

Ran OTB 1.4 for a while, but kept getting freezes (not really FCs), then I switched back to OTB 1.2 and been stable since (I've been running the same voltage settings for both kernels)

Basically, and not sure why, but OTB 1.2 is more stable for my phone/settings than 1.4.
[Fascinate Android Development] saps:
Same here 1.2 is the most stable for me with an OC. I think its due to slightly higher voltage
[Fascinate Android Development] dnoyeb:
Anyone running this on ed03? Went back to stock to get the latest radio and am very impressed in the battery life... Going to try running a simple debloated / debinged one and need a kernel.
[Fascinate Android Development] beray5:
It is better because better CPU voltage regulator required less droop voltage compensation and 1.2 had the least compensation, start here -> http://xdaforums.com/showthread.php?t=1011626&page=60

And follow through with nemesis2all post #592
[Fascinate Android Development] exzacklyright:
Tried 1.2 since people were saying it's more stable but now it won't let me into voltage control.Says kernel is not compatible

Sent from E.T.
[Fascinate Android Development] CHANGiism:
nemesis uploaded v1.5 of this kernel to his git. Can someone build it and upload it for all of us please?
[Fascinate Android Development] dnoyeb:
running version 1.2 on top of a straight ED03 OTA updated phone... was getting unreal battery on the base and its staying strong with 1.2 installed on it as well. Just de-bloating it myself after rooting and putting this kernel on it...

running like a champ at about 4.4% battery per hour with moderate usage and exchange email.
[Fascinate Android Development] navenedrob:
I'm building it now. After a while, I will post a link to it here.

EDIT: Download v1.5 here: http://www.multiupload.com/IXRT5GXDP0
[Fascinate Android Development] vlucchetti:
Anything new/special we need to know?
[Fascinate Android Development] kidserious:
Do you know if someone is doing the same for his GB cm7 version?