yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] hospital349:
Admittedly, I'm not very technical minded. I just go with what works best through trial and error over long periods of time; so any feedback and input is welcomed with open arms. The load number from my understanding (via reading XDA threads) is in fact a measurement. The higher that measurement is, the longer it takes for the 2nd core to become active and this is based on the amount of strain that is put on the processors. From 0-100, 90 is pretty high.

I used to use 1200mhz in my previous versions: 1.0, 2.0 & 3.0. I can't really say it helped battery life. If

1200mhz

uses a voltage of

1200mV

and

1000mhz

uses a voltage of

1050mV

, it's probably safe to say that an overall battery cycle will probably benefit from underclocking at 1000mhz.

I have read on a bunch of XDA threads, with folks stating that underclocking is much more battery effective than undervolting... but I like to do things in combination, as it seems to be twice as effective. ;)

I understand exactly what you're saying though. If 1000mhz is the highest frequncy when underclocking, then 2nd core should technically kick in earlier than if 1200mhz was the highest. However, it all boils down to previous experiences, preferences and months of studying battery life using various setting combinations and making notes of each successful cycle. That's pretty much how I work in a nutshell.

I understand the basics of how a kernel operates & its general functions, but each WIN!UV version is based on physical results, trial and error and the study of battery drain over time; hence why I stuck with 'on load: 90' instead of something smaller, and why I have chosen to use 200mhz-1000mhz instead of 100mhz-1200mhz or any other variation. :) I take quite a bit of time out of my life to sit in front of my device and study it as I go about my daily routines. :)

Of course, any user is welcome to test out their own personal setting formations and if proven more battery friendly; I'll most certainly merge my current settings with theirs and credit them for their hard work! :good:

I hope this helps you to understand how I commit to each new version. I try my best to operate objectively when creating, without ruling out any given combination without first of all testing it out. It's a painstaking and monotonous process, but it works and a lot of people (including myself) benefit from it. :D
[Galaxy S II General] sianzb0i:
I totally agree with hospital. For me up till now i still dunno the cpu will scale up one level or activate 2nd core but from my past experiences with a HTC desire, we try to not use max freq. We used too clock till 800mhz (max was 1ghz). It will really save battery life alot. As for dual core, i do not exactly know the CPU values we use is for single core xxx mhz or how does it work. I assume once u activated 2nd core you have to x2 the value. While 1.2ghz is not a very high clock speed, we do not need that much power as power consumption in that state is not practical (clock/batt ratio).

Hope you kind of understand my explaination lol

Sent from my GT-I9100
[Galaxy S II General] Ryther:
I knew you really had to this results with the "trial and error" method, cause i think it's the only way to achieve a REAL result regarding battery!

Well, i'm going to try myself something cause i can undervolt 1200 to 1150! So i'm going 200-1200 with 90 "off" and 99 "on" ;) But if you already tried that i will resign :p

You deserve a medal for your tenacity towards this matter :D

Hi, fellow Desirer ;) I understand that an higher clock consume a lot more, but if the activating the second core pump up the used current by 2, then you have the double the consumption... in the end everything depends on how the phone is used, so 1000 is the best overall user-friendly value!
[Galaxy S II General] sianzb0i:
I dunno how to exactly achieve this, but i would like my CPU to scale to the max freq i personally set before it activates 2nd core, OR it activates 2nd core but cap at prolly 500mhz. Then again in terms of performance the 2 cores option would outrun the single core by just a tiny bit (we wont feel the diff) but consumption-wise single saves alot more. hmm just some thoughts. Hope someone can enlighten me too :)
[Galaxy S II General] hospital349:
I'll be releasing WIN!UV 4½ in a few hours, just committing to some final tests for stability and then I'll unleash the beast. :good: ;)
[Galaxy S II General] sianzb0i:
Sry bro i havent gave you any response yet. I have been busy. I will be doing a nandroid and backups in an hour or so. Then i will flash a stock sammy ICS ROM. Then i will test your settings

Sent from my GT-I9100
[Galaxy S II General] hospital349:
Not to worry! At this rate, you'll be testing them upon its release. :)

Beta testing went well, so I'm looking to push it forward!

People have reported great battery life so far, even during their first cycle.

I can't wait for people to begin posting their results. :good:
[Galaxy S II General] hospital349:
WIN!UV 4½ is now up!

Many thanks to the dedicated beta testers for making the extreme UV process much easier and constantly reporting back! :good:

m4x0r, banok, vladbaca

As you can see, this version is GPU orientated. I've pushed N.E.A.K to it's limits and took every step to bring users the best UV experience possible.

Version 5.0 will be dependant on future N.E.A.K releases and its capability to UV further. I also hope to integrate the Lulzactive app into the next release, as it will add more flexibility and control. :)

I leave for Japan for 4 weeks on Friday, so I will look into taking the next step upon my return.

I'll assist with all issues until I depart. Thereafter, if you could help each other out, that would be great!

Many thanks.

ENJOY!

​
[Galaxy S II General] sianzb0i:
sorry bro! very sorry. i just managed to get my phone up and running and its past midnight here alrdy. I will test with my own settings tmr and maybe we can compare :)
[Galaxy S II General] Ryther:
Yeah! But I have a problem: I cannot go under 700mv in the gpu config!

Edit: just a question: SCHED_MC manage the cores uses and activation, doesn't it conflict with hotplug?

Edit 2: just reflashed everything and forgot to update the app :p
[Galaxy S II General] m4x0r:
Flash the new kernel and update the app. Than it must work.

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II General] Ryther:
Ok, everything is set! Everything works without problems :D !The only difference is that I'm trying without sched_mc ;)
[Galaxy S II General] hospital349:
For anyone initially experiencing problems, please follow this method before reporting an issue:

Boot into Recovery Mode.

N.E.A.K Options> Remove Voltage Control Settings

N.E.A.K Options> Configurator Pro Options > REMOVE EVERYTHING

ROM Tools > Clear init.d folder

Flash Ultimate Kernel Cleaning Script

Flash N.E.A.K 2.1x (AOSP/SAMMY version, respectively)

Wipe Cache

Wipe Dalvik Cache

Fix Permissions

Reboot

Reapply settings and prey to the gods :angel:
[Galaxy S II General] hospital349:
Whatever works best for you :)

I tested both with and without sched_mc + Dynamic Hotplug, extensively. I can confirm that it does in fact make a difference to your battery life. I know they function similarly, but I do recommend using both together. :good:

Sounds good man. :D
[Galaxy S II General] hospital349:
Did you struggle to get the settings to work with sched_mc turned on?

Was the issue fixed after turning it off? :cyclops:
[Galaxy S II General] m4x0r:
4h display and 7h tune in music (Web radio) in background with display off over Bluetooth headset. WLAN, data connection, sync always on and I got 30% left. It's a very good result for me with the first circle :-P

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II General] hospital349:
I'm so glad! The GPU unvervolting-underclock combo really makes a difference, doesn't it? :)

Could you by any chance try something out for me? (Fellow beta tester) ;)

I have changed the following and haven't had issues for the last few hours. I'll update the current version if you experience the same outcome.

Here it is:

Second Core off Threshold: 85

If you experience performance drops, just revert back to the old settings. Otherwise, I'll make the change official. :good:
[Galaxy S II General] vladbaca:
Thank you hospital349 for all your work. It was my pleasure to beta-test for you ;)

I haven't extensively bench-marked the battery life yet, focused more on stability-tests, but here's a glimpse: 2 hours of streaming Youtube videos (with audio on of course) on wi-fi and barely lost 20% of my juice (I am using the 2000mAh extended battery, to be honest; it is remarkable nevertheless; that probably translates to 25% consumption on a regular battery).

This kernel and these settings are the sh*t guys. I enthusiastically recommend you to try them out ;)
[Galaxy S II General] m4x0r:
Sure ;-)

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II General] hospital349:
Thanks bro!

Even with heavy use and stability tests, that's pretty fricken' solid!

I'm impressed.

I think this version SHOULD eventually push this thread up to 5-star status. Let's hope. :fingers-crossed:

It should also make a lot of people very happy. **** just got real. :cool:

Thanks man. I'm grateful! :) - Let me know what you think. There shouldn't be an apparent difference in performance, although it'll just limit the amount of time the 2nd core is used. :good:
[Galaxy S II General] marco.fuce:
I m confused... are you going to release something flashable... or it s a problem for the pay neak's app?
[Galaxy S II General] hospital349:
WIN!UV has never been flashable and as mentioned in my previous post, I wouldn't create a flashable version as it wouldn't be kind to developers who work hard and deserve small incomes from the paid app they provide. If I was to create flashable versions of WIN!UV, it wouldn't give anybody the incentive to buy the paid app. This would make the devs very sad indeed. :crying:

It's recommended that you buy the paid app to apply these settings, unless you know how to edit the scripts and then you can do it manually, although this can be a tedious task.
[Galaxy S II General] m4x0r:
So i tested it and it runs without any problems. Make if officially 8-)

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II General] Ryther:
No, sorry if i made you misunderstand! I had a problem cause the app wasn't updated :p

I've disabled sched_mc because I want to try to use only hotplug and see if I get +battery +performance; this try come from me reading a little about sched_mc and thinking that having two options doing the same job but with different methods give less results than only one option working without conflicts.

Hope you can understand my horrible english :p
[Galaxy S II General] sianzb0i:
bro i do not quite understand what does sched_mc do. I did alot of research but they made little sense. Of all the sense i made, i decided to not turn it on as it will use the 2ns core more actively. plus there a afew states to sched_mc and i dunno which one is implemented on NEAK.

For NEAK PRO i enabled AFTR only. not even EXT4 as i do not have anything running on EXT4, unless our internal is running on EXT4?
[Galaxy S II General] Ryther:
Sched_mc have three state: 0 do nothing, 1 use more the first CPU (battery friendly) and 2 share the load between the cores (performance friendly); this bis why I have doubts regarding the use of both hotplug and sched_mc! If it's 1 then it overlap with hotplug, while if 2 completely nullify hotplug... but I don't have any proof regarding this.

Regarding 4ext: yes,internal run on it;)
[Galaxy S II General] Holgott:
I tried win!UV 4 1/2 and my phone was frozen immediately after applying the gpu voltages. I raised them a bit and now all running fine. Btw I just bought a 2000 mAh battery and to me it's like 100 % more battery life. I think I should be a beta tester for the worst case phones ;-)
[Galaxy S II General] sianzb0i:
Precisely. I do not know which state is implemented or its meant to be auto. So does turning it on save batt for you?

EDIT: i thought internal storage was fat32. Must i do a format to ext4?

Sent from my GT-I9100
[Galaxy S II General] marco.fuce:
Ok...installed configurator pro but seems to not work. Why? Simply don t apply the value. I have superuser and supersu.. in superuser there is only permission for supersu. Tried to fix permission but no fortune... what I can do? Tnx!
[Galaxy S II General] sianzb0i:
my phone is still not very stable so i cant exact measure play with batt life yet.

However i managed to play with your settings and measured performance today :)

GPU performance for normal day to day usage is ok. Games might lag. I tried temple run today. Still running fine but with that kind of performance we could have just bought a cheaper android phone and achieve that performance. I think its underworking the GPU a little (kinda like disrespecting the beast :) ). Gmaps was fine but could feel a little lag, which i personally didnt wish to see. Furthermore in my case, my voltages used we much higher. 160/750 and 133/650. 160mhz cant do 700mhz on my device. i would have occasional to frequent freezes for no reason. it would recover like 20secs later. sometimes it just restarts.

For GPU i guess i will find my sweet spot. I wanna try out 200mhz (not supported by app). hopefully it works well.

btw, could someone explain to me whats all the gamma and BL_min are about. just wish to understand.

---------- Post added at 07:46 PM ---------- Previous post was at 07:39 PM ----------

did you create the init.d folder in /etc/ ?
[Galaxy S II General] marco.fuce:
Edit. Yes I have it. And i can see into it all the files of neak configurator pro. I have uninstalled supersu. Rerooted phone and updated superuser. Now i have just superuser. But neak's setting still not applied!!! Why???
[Galaxy S II General] Ryther:
Two superuser manager apps? You only need one, i think. Usually i go for Superuser and when i have SuperSU in the rom:

I go into it's settings and use the "change superuser app" or something like that

Restart and flash superuser

Reboot and open superuser to check if it's working

Reboot in recovery and fix permissions

Finally reboot and update the superuser binaries

Edit: using neak kernel you can delete SuperSU and reinstall Superuser safely with the option you can find in the "ROM Options" menu in the recovery!

Last but not least wich rom do you use? As suggested by sianzb0i, you may miss the init.d folder.

@sianzb0i: I think we need to check a couple of things:

How the dual core works regarding the voltage. After some tought, I think the voltage of the cpu is the same regardless of the number of cores used, cause, for example, 1600 mv for a 200 mhz clock is a little too much! so we are going to have less battery drain while the cpu works with 2 core at 200mhz than one core at 500!

How sched_mc and hotplug works in the details!

Wich status of sched_mc is used by the kernel, and if it can be added as an option in the control app.

I will try to ask directly to simone201 via PM to fasten the process :p

Regards!
[Galaxy S II General] marco.fuce:
I m using ollo monster rom by neme.... the same of hospital probably. I have init.d folder. Deleted supersu. Fix permission update superuser. Fix permission. But nothing..
[Galaxy S II General] Ryther:
Try this: press "Edit Settings", set your values but don't tick "Set on boot" and press "Apply Settings", then press "Edit Settings" again and set again your values but now tick "Set on boot" and apply.

I've had this litle bug too, but i don't know if your case is the same as mine!

Regards!
[Galaxy S II General] sianzb0i:
Glad to hear from you bro! what you said did make alot of sense too! i nearly bought your idea until i thought of this.

If what you say is true, we might as well setting dual core to ALWAYS ON. afterall when in single or dual core mode it consumes the same amount of power.

This is getting soooo confusing haha
[Galaxy S II General] Ryther:
Well, i'm going to give a try!!! But I don't have the huge experience and "database" as hospital to compare rapidly the effects, but it's worth a try, as you said, to enable hotplug in dual core mode and sched_mc!!!

After reading the data regarding sched_mc, 0 deactivate it, 1 fill more the first core and 2 bias the load between the cores and here linaro say that the choice number 2 it's the one which save battery! But here in the forum ppl say and use choice number 1 to save battery, maybe thinking the use of a single core is less battery hungry than a less clocked dual cores! As you previously said, you save more battery with underclock than undervolt!

EDIT: maybe to improve even more the battery life, we can enable the 100 mhz cpu clock!

EDIT2: also thinking that a single core uses the same power as a dual core is strange :confused: but if the voltage values we set are for single cores, it's strange it go up 2x but if the voltage is for the dual core it's even more stange to have 400 mv for a cpu at 200mhz! I don't know anymore where to hit my head :silly: the only logic conclusion atm is that the voltage is for the CPU and not the cores!
[Galaxy S II General] sianzb0i:
LOL thats where i always get stuck too!

I will not recommend 100mhz as it will scale up and down too often even when its "sleeping". I feel 200mhz is a nice point (Comparing 100mhz vs 200 mhz. Not worth the difference and stability issues, end up it uses more batt to "sense" the load %-tage)

From my understand from my past computer overclocking experiences and abit of reading up, based on intel PC chips, why they introduced dual core is so that overall voltage that is needed to be supplied to chip is lesser, in return less heat produced. And also the higher the clock speed the increase in voltage per every x mhz is increasing. For example, if you need 2V to run 2Ghz single core, to run a 2x1Ghz chip u prolly need 0.7V. If im not wrong thats the rough idea. However in the BIOS we set voltage for the CHIP itself, on our phones its a whole new story (we go by specific CPU speeds). Well back to the big question mark :confused:
[Galaxy S II General] Ryther:
Maybe I've found THE answers!

ICS Kernel explanation

Here you can find the explanation of almost every tunable values!!! And even a formula for the hotplug!!! Intresting reading... gonna test it :D
[Galaxy S II General] tobyp42:
1st day...

Thank you OP!

I have been using NEAK for months but have only just discovered this thread recently.

Applied the settings from your first post last night and then fully charged the phone through the night for testing today...

Battery life appears to have improved slightly, I'm at 66% after 10 hours of light usage. Android OS has taken up 56% of the battery, kept awake time is 2 and a half hours.

Surely this isn't right? I've noticed this problem in the past with prev roms where it has drained the battery super quick so I changed roms. Any advice?
[Galaxy S II General] hospital349:
It sounds like a Rom problem to me. Android OS isn't WIN!UV or N.E.A.K. related. I would recommend doing a

full wipe

and perhaps re-flashing your current Rom. See how it goes from there!
[Galaxy S II General] tobyp42:
Drained the battery last night before leaving it charge again, reset the battery stats in recovery and removed the battery from the phone for 5 minutes before turning it back on...

2 hours later and Android OS is only taking up 4% now :)

Only have 83% battery left because of bloody spotify but looks promising so far!
[Galaxy S II General] sianzb0i:
thats a great find bro!

I do manually edit those files too (after reading the files created by NEAK pro in the init.d folder) but with this i think i will understand it further. I will test it after dinner!

Hey bro! you have a great trip in japan! Lots of stuff and fun awaits you there. Well, i didnt make it in time to be your BETA tester, but i will stay around in your thread. Sorry for the long preach on the PC CPU story. maybe shouldnt have done that :(

but i shall see you in 4 weeks. Have fun!
[Galaxy S II General] g3ckospy:
Was wondering since not all of the followets of this thread can purchase the pro version of the configurator. What are the alternatives for tweaking the gpu and thresholds.. someone could give some inputs it will be of great help to others.
[Galaxy S II General] sianzb0i:
this is your key!

after reading i realised i could have done it on my own.

I will be writing my own scripts based on here and what i learnt from NEAK pro. So actually NEAK pro made me understand all these basics and the website is just a reference. So it was worth getting the app!
[Galaxy S II General] lionsmatara:
Bro hospital,

Any good news about after realese 2.1.1?? :p
[Galaxy S II General] sianzb0i:
dont think he had the chance to flash it before he's gone plus he needs a stable phone when he's overseas :)

saw many people complaining about the batt drain and i flashed 2.0.6 haha
[Galaxy S II General] lionsmatara:
Lol brother,

battery drains on who didn't use UV :eek::rolleyes::D:D:D
[Galaxy S II General] Ryther:
I've tryed to install xxTweaker and I have to say that it works to a some extent! So, out of curiosity, I've played a little with the sched_mc options on neak app and checked the value on xxTweaker but it reported always "disabled", so I've set it through xxTweaker and the value sticks even after a reboot! How can we check if sched_mc is really working?
[Galaxy S II General] ziomek76:
I bought Neak configurator pro, how to get GPU600mV (133MHz), 650mV (160MHz)

min 700 MHz :(
[Galaxy S II General] g3ckospy:
Hi, did you download winuv4? if im not mistaken he gpu setup goes like this.

700mv(133mhz)

850mv(267mhz)

Hope that helps..
[Galaxy S II General] ziomek76:
http://xdaforums.com/showpost.php?p=25942150&postcount=2 :crying:
[Galaxy S II General] g3ckospy:
Do 700 and 750 then, give it a try..
[Galaxy S II General] ziomek76:
No freez . It's ok THX
[Galaxy S II General] Ryther:
Have you set the avs voltage level 4 in the recovery?
[Galaxy S II General] lionsmatara:
you always can cheq ur bus AV setting like this:eek::D

Use root explorer. Go data folder >> neak folder >> open bus_asv_table as a text viewer:p

Now you can see ur current bus asv level :D:D

Cheers... :):D:D:D:D:D
[Galaxy S II General] sianzb0i:
these few days have been trying to UV but for my phone to be stable i had to use higher values than WIN!UV 4 to stablise it on ICS.

Tried it on NEAK and siyah. im on siyah and sensation ROM, just to try out.
[Galaxy S II General] lionsmatara:
hey hey...

Bro Hospital...

Where are you,,,:laugh::laugh:

Please wake up.... wake up :confused::confused::(:crying:

NEAK got new Update..:D:D:D
[Galaxy S II General] Ryther:
He's on vacation ;)
[Galaxy S II General] sianzb0i:
well bro, you could try and help us out and contribute back to the thread by flashing and doing your own testing :)

Be sure to backup thou :)

I will jump right in after i found a good ICS ROM for my phone. My phone doesnt like ICS as i cant go anywhere near those values hospital provided.
[Galaxy S II General] sianzb0i:
i did a quick test on WIN!UV 4.5 voltages values on the latest NEAK 2.1.2x.

Same CPU and GPU values. i havent tweaked the gamma and i used lulzactive governor and different values for hotplug.

CPU values and GPU values are working fine. Ran apps like temple run, let it go into deep sleep and waking it up (1min).

No SODs.Temple run was a little jerky at the beginning of the first round but subsequent rounds were fine.

You guys can try it out!
[Galaxy S II General] :
Awesome..everything set ;)
[Galaxy S II General] lionsmatara:
My choice

160>>650

133>>650

200 >>825

bro just wait NEAK will full update7 sources:D:D:p:good:
[Galaxy S II General] sianzb0i:
oh yah, my 200mHz is at 825mV. CPU values i didnt tweak much. I followed what was used in GB. Except the 800mHz i managed to go to 950mV :)

GPU-wise, i still think NEAK pro should support 200mHz. I will have to script it in init.d when im free. Trying to do a 200 ->267 or 160->200. Im currently going to just start work so lesser time to test and play around :(