[Galaxy S II General] hospital349:
Hey guys, I've been reading your posts and this is my response to pretty much everything:

As I mentioned previously, I'm not technically minded when it comes to kernels, my knowledge is limited although I have spent the past 2 months constantly arranging and rearranging voltages, clocks and other such features & settings. Tweaking everything to as close to perfection as possible, using result after result after result to form the best combination. Nothing is at random, trust me. I wouldn't have selected Dynamic Hotplug if I didn't think it was of value. Same goes for sched_mc. Same goes for combining the two and using them as a duo. I have read many posts regarding Dynamic Hotplug and sched_mc and never really got my head around it all that much. It's kind of ignorant but at the same time, I appreciate physical results and testing rather than taking somebody else's word for something that might only be one interpretation of an idea. It's all a little unclear from my perspective. Even gokhanmoral contributed to several conversations about the subject and still it appeared to be inconclusive. I really don't think the subject is worth puzzling ourselves over. :)

Dynamic Hotplug exists for a reason and its creator designed it to aid folks who couldn't choose between better battery but a lesser & limited performance (1-core) OR a consistently outstanding performance (2-cores). Dynamic Hotplug eliminates those woes by giving us automated control over the cores. The cores themselves have much to do with our potential battery life... otherwise, why would Dynamic Hotplug exist to begin with? Why not give us just the one option out of the three? Why not just get rid of the core-control options altogether and leave your device set to 2-cores all the time? - because it makes a difference and that's why the option is there for us.

Now, I have no idea how the cores switch between single and dual and how they correspond and work together, although as stated before... the 'load on' and 'load off' settings are there for our benefit. They're a measurement (1-99), respectively giving us the choice to control when we want that 2nd core to kick in. That's all we need to know. There is no magic or godly way to choose the perfect moment as to when it actually does kick in, it just depends on the ongoing and ever-changing environment as we perform our tasks, use our apps and play our games. It does it all for us, so we don't have to.

For us, we have a choice of frequencies from 100mhz all the way up to 1200mhz, there are a limited amount of frequencies to select, so it's not as if we have a large amount of options thrown at us. I choose 200mhz instead of 100mhz as the lowest frequency because 100mhz's voltage can't go any lower than 200mhz's voltage. I've tried. 100mhz @ 775mV freezes after a while. (You're all wecome to try it) - However, I find that 100mhz is a piss poor base frequency... I prefer 200mhz as I've noticed that performance is more solid overall.

All that your device is doing is moving up another frequency step when the going gets tough. When a load is too heavy, it is forced up to the next step, then the next and so on. That's why it's absolutely pointless to have settings at: 800mV (100mhz), 800mV (200mhz). Their voltages are the same so they're technically consuming the same amount of battery. It's literally a waste of time unless you find you can get 100mhz at a lower voltage, but even then, you'll find that your device is forced to move up a frequency much sooner because there aren't many moments that you'll find that your device can run a task using that frequency without really straining, thus you'll find it steps up to 200mhz anyway. :cyclops:

All in all, I try not to get weighed down by all the technicalities. I know they exist and I know there are folks that really know their stuff and could run ring around me... but I do have experience with this. I study CPU Spy religiously as a go about my testing. I study battery life religiously, during and after cycles 1, 2, 3, 4, 5... I'm constantly making note of how much battery is consumed over time using restrictive and objective actions, whereby I reiterate tasks over and over again using various setting formations. I do all that I can to find the best solution to a problem, whilst finding the strongest outcome for battery life and performance alike.

These are the settings that I use for my device. I have experienced nearly 8 hours on screen time with almost 2 days on battery. It's doubtful that I'm doing this wrong and although I know there's always going to be room for improvement, I really don't care about what I can't do, instead I enjoy concentrating on what I can do (using 'logic' rather than technical knowledge). I'm never going to please everybody and people use their devices in different ways.

As always, WIN!UV is to be used as a guide to great battery life. Feel free to create and share alternate versions and show use your battery cycle screenshots! :D - I'm REALLY glad you're all spending quality time sharing your ideas about cores, clocking, voltages, kernels, etc. I'm happy the thread is being used and it isn't at all off-topic. It's all relative.

Thanks for those that have taken such a huge interest in the thread! I leave early morning for Japan for 4 weeks, so I probably won't be around during this time. Please help one and other and share your current knowledge. The beta testers probably know as much about the latest version than I do, so I'm sure they'll be happy to give out advice if you ask nicely. :good:

I usually check my posts for spelling & grammar mistakes, but in this instance, I think I'll pass. :laugh:

I hope that all your batteries live long & prosper.

Speak to you all when I get back. :highfive: