yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] msquared:
Did u check in NEAK options in recovery?

Sent from my RootBOX
[Galaxy S II General] superleeds27:
Nope, ill have a look. Cant say ive noticed it before though!
[Galaxy S II General] msquared:
Ok let me know if you find it coz now i'm running thoravukk but asap i'll get back to NEAK ;)

Sent from my RootBOX
[Galaxy S II General] superleeds27:
Not there!
[Galaxy S II General] msquared:
Argh so se have to ask in NEAK thread

Sent from my RootBOX
[Galaxy S II General] hospital349:
Hey man. Thanks for your support!

I don't use juicedefender. I'll be making a list of the things I do use on the 2nd post shortly. It's mainly autostarts and green power that does the trick. Green power disables network data when the screen is off. Autostarts restricts apps from starting up at specific moments, forcing them not to run in the background until you tell them to.

I'll make a note of them and take some screenshots shortly :)
[Galaxy S II General] hospital349:
Hey folks,

You're better off asking Simone about this one... however, I know the team are in the midst of releasing a new app version with tons of features... so the option to adjust vibration intensity might be included.
[Galaxy S II General] superleeds27:
Yeah i pm'd Simone. :)

I noticed you mentioned green power for data? I have an option in SlimICS to diable data when the screen is off, which i might try. Has to help the battery obviously? Could be a nightmare for Beautiful Widgets updating though!
[Galaxy S II General] hospital349:
It has helped my battery life enormously. I'm on CM9, but previous to that I was using various AOKP ROMS that used the same implementation. Cm9 doesn't have this option but Green Power does the same trick.

It does cause issues with apps that require frequent syncing, although I don't sync many items and the ones that I do use have no problems. If you're looking for frequent weather & news updates, etc - it probably won't be an helpful process. However, if you want better battery, then it's a perfect battery saving addition. :)
[Galaxy S II General] superleeds27:
Going to enable it see if it actually works (Not sure if it broke or not, time will tell)
[Galaxy S II General] superleeds27:
Think my 2000Mah battery has seen better days? Using your settings
[Galaxy S II General] sianzb0i:
Neak config pro support so low voltage values for mali 400? Tegrak only does down to 750mV only.

Can config pro really go that low?
[Galaxy S II General] WearTheFoxHat:
Thanks for this post Hospital. After following the CM9 thread and staying with the only approved kernel, I got a bit fed up with 7-8 hrs battery life and decided to take the plunge.

I've gone with your exact settings. There were a few things I wanted to check:

Voltages

800mV (200mhz), 925mV (500mhz), 950mV (800mhz), 1050mV (1000mhz)

It seems to be missing 100mhz and 1200 mhz.

Also should we tick "Set on Boot" ??

Fingers crossed I get some much improved battery times.

Do you also run the other two recommended apps? Autostarts and Green Power?? I tried Juice Defender for a while, but not currently utilising it.
[Galaxy S II General] superleeds27:
Anyone tried this?

Has anyone tried this?

https://play.google.com/store/apps/...r#?t=W251bGwsMSwxLDEwMiwiY29tLmRta2hvLmxibCJd

It basically disabled Data/Wifi when the screen goes off. Re-enables whn it comes back on. Really small footprint too
[Galaxy S II General] msquared:
mmmm i really don't believe in this kind of apps...

But if can try it out and make us know if really make us save more battery than how much it drains...

BTW AOKP roms have this feature in Green Power settings
[Galaxy S II General] superleeds27:
I know what you mean. Yeah, noticed that AOKP Has this, and i thought that if the app from the Market is only like 96Kb, it's surely on par with the AOKP one, right?

I believe the smaller the app, the more effective. This is why Juice Defender fails.
[Galaxy S II General] hospital349:
Wakelocks?
[Galaxy S II General] hospital349:
Hey man.

If you select only 200mhz-1000mhz, those are the only frequencies that'll be used by your device, so it doesn't matter what voltage 100mhz and 1200mhz is set to. It'll ignore those frequencies anyway.

Definitely set all options 'On Boot' as that means they'll start-up automatically if you restart your device.

I use Autostarts and Green Power and highly recommend them. They're battery life savers.

I also 'kill apps by holding down the back button', after I've finished using them. This option can be enabled from Developer Options.

I also uninstall any and all bloatware using titanium back-up, as a lot of the apks that accompany ROMS are unnecessary and can occasionally drain battery (especially Facebook app and Google Talk) - I use Friendcaster instead of Facebook. It's much more battery friendly. :)

I hope this helps.
[Galaxy S II General] LukeNukem:
instead of Green Power is use Internet Commander

dont know if GP supports that too, but IC has an option to periodically sync when the display is off and turn internet off the rest of the time

saves a lot of battery without having to miss sync functionality!

totally gonna give autostarts a try, looks very good :)
[Galaxy S II General] superleeds27:
None at all. I keep a regular check you see.

Ive flashed CM9 and tried new Fluxi. Upto now im on 90% battery, 1 hour 5 mins screen time.

Looks like It could have been a ROM Issue! Ill keep track!
[Galaxy S II General] msquared:
If your 2000 mah battery is new that's normal it needs about 15 full cicles to make it work at 100% ;)
[Galaxy S II General] fridlack:
Hi!

I just set the values and everything is working like a charm

I have a question about the Screen Control section, in my point of view screen is too dark and i want to set my own parametres

It's clear that min and max gamma are about the min and max brightness we have in our screen

But, what is min_BL? what happend if i put 30 for exemple?

Thanks for your work and best regards!
[Galaxy S II General] sianzb0i:
it doesnt really matter cos we dont scale to those frequencies. we limited it to 200mHz to 1000mHz. others wont be affected.

---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------

any confirmations before i purchase? or should i purchase voltage control instead as it is not kernel dependant?

tegrak lowest is 750mV, Voltage control lowest is around 800mV. :(
[Galaxy S II General] hospital349:
Hey.

The lowest voltage adjustment you can make using Config Pro is 800mV, however ASV busfreq adjustments can be made via Recovery, which decreases voltages by -25mV with each level. Safe to say, you can take UV as far as you want using this process and N.E.A.K. Configurator Pro. It's as extreme as you're going to get (if your device supports it that is). :)

Hope this helps.
[Galaxy S II General] hospital349:
If you're looking for something along the lines of stock brightness, I would leave your Screen Control values as Default. I know a lot of people have been having issues with saved values not sticking. It might be a safe bet if you want a brighter screen.
[Galaxy S II General] LukeNukem:
i use these settings for autobrighness tweaks if ur rom supports that

they're for the samsung fascinate but they work great on my s2 too

hope that helps :)
[Galaxy S II General] WearTheFoxHat:
Hey, thanks for the quick reply.

Doh ... makes sense now ... the first setting to restrict CPU "range" to 200-1000Mhz. Cool sorted.

Cool ... had ticked it, and assumed that "set on boot" was the bet way to go.

Brilliant, I'll give them a bash.

Excellent, found it ... will keep that one in mind.

I've got Google Talk disabled, but still use facebook. I'd tried Friendcaster, but as it's not the "official" app, it only allows status' which people have deemed ok to be shared with all devices. It doesn't get all updates.

I guess all the ones that try to keep contact details in sync are worth disabling, or only running when required.

I'm running CM9 too, and rather pleased with that (apart from not having TV out yet!). Although I note that one of the other kernels seem to allow it to work.

Oh it certainly does, thank you very much for your help.

I'm currently 6h since I unplugged, with battery at 76%, and it's following a linear battery depletion. So I'd estimate :

12h - 52%

18h - 28%

24h - 4%

(Totally unscientific of course!)

But still far better than the 12 hours that I'd been suffering!

Edit: One quick question ... when it's on mains charge, and I've been using it such as TuneIn Radio or on a phone call, it seems to be getting hotter than previously. Is this to be expected? Is this because it's running one core up to a higher utilisation before letting the second one have some action?
[Galaxy S II General] hospital349:
Cheers dude. This is great stuff!

Also, this will surely do the trick: LUX

I know how everybody raves on about how great it is. :) Personally, I haven't tried it, but I'm sure it works well.
[Galaxy S II General] hospital349:
I'm glad everything's sorted for you now.

Yeah, you could definitely give it a go. I can't imagine why it's getting so hot unless you have a rogue app running in the background or something. Technically, your phone should be cooler than before as it is now using less energy via UV. However, knock your hotplugging values down 20 each and see how it goes from there. Obviously not as battery friendly but it's worth a try to see if it does solve your issues.

Let me know how it goes. :)
[Galaxy S II General] msquared:
Hey dud just back to ur settings ;)
[Galaxy S II General] hospital349:
Everybody always returns. :victory:
[Galaxy S II General] sianzb0i:
Hi there! Thanks for the reply :)

May i know what does ASV busfreq affect? like what changes are made with each level and where I start (whats the default level)?
[Galaxy S II General] msquared:
An higher level of ASV busfreq means a higher UV on the bus frequencies values,so more battery saver
[Galaxy S II General] hospital349:
My advice is to start on level 3, try it out and then work your way up each level. If you have issues using the next highest level, stop and move back down until you have well balanced UV. To be honest, with the settings implemented on 4.0, I can't imagine anybody making it above level 5. You can only really take UV as far as your device will let you, so it's good practice to use smaller values and commit to trial and error for good testing ethics.
[Galaxy S II General] suta:
my phone is freezing so much using your guide. even increasing all volt by 100. still freezes when playing draw something. Im using based samsung rom- wannalite . can you create another guide for samsung based rom.
[Galaxy S II General] hospital349:
I'm using a Sammy based ROM at the moment, without issues. Try the same 4.0 voltages but change your ASV busfreq level to level 3 and see how that goes.

I'm using Pure ICS 7.5 without any issues.

100% stable and GREAT battery life!

EDIT: Also try WIN!UV Problem Solver on the 1st page of this thread. It has solved many issues in the past.
[Galaxy S II General] suta:
Don't think pure ics is samsung rom, isnt that AKOP rom, anyway did how the UV Problem Solver guide. still the same outcome. think the UV 4 guide is too extreme to samsung rom. the minumum i can get is 875 900 1000 1100 . not sure how the battery life will go though.
[Galaxy S II General] hospital349:
Pure ICS is a Samsung ROM. I'm using the N.E.A.K. 2.0.6x Sammy kernel.

Also remember that each device is an individual device. What works for one device, might not work for another. Also, some ROM's are more UV compatible than others. It's all dependant on the design of the ROM, how light it is, etc.

You should try ASV level 3 before reporting back again. There's really no point writing posts about how your phone freezes if you aren't willing to first of all seek out all possibilities - and even then, it doesn't mean that the settings are bad.

The success rate is high for WIN!UV users. For Sammy and AOKP/AOSP users alike.
[Galaxy S II General] viscocesco:
Try WIN!UV 4.0 on N.E.A.K. 2.0.6 and Omega ICS v15, best battery life I never seen!

Thank you!:victory:
[Galaxy S II General] hospital349:
Happy Sammy user! :D

I'm glad you like it.
[Galaxy S II General] suta:
how did you guys manage to under volt that much? i downloaded pure ics rom, wipped everything, used kernel cleaning script, flash everything. and followed this guide. the phone still freezes. even when switch back to vfs 3 to its default and increase 800 to 825, but still freezes
[Galaxy S II General] SiL3nTKiLL:
hmm interesting..hopefully this can help my bat life quite a bit!
[Galaxy S II General] mario999:
Currently using Resurrection Rom with latest Neak... cant figure the problem out. May try and flash stock.

Thanks
[Galaxy S II General] hospital349:
Is your Wi-Fi effected when you don't UV? - If it does only occur when you UV, then that might be your answer.

For me, N.E.A.K. + HyDroG3N-ICS + my current settings don't cause any Wi-Fi issues. So it might be a combination of all 3: Your ROM, Kernel & UV.
[Galaxy S II General] bajee11:
I'm glad my thread was useful, sometimes I even wonder if people actually use it as a reference :D once again, keep up the good work.

UV shouldn't affect your WiFi. Check if you have all your modules in /lib/modules/ and system/lib/modules/.
[Galaxy S II General] hospital349:
It should. With every slight incremental change that I work on, I squeeze out a little bit more juice. Only 6 months ago before I decided to root, I could only get about 12 hours of battery life. I have now tripled that, with the potential to quadruple in the future. Mind blowing.

I'm so glad independent developers exist. They're phone-savers. ;)
[Galaxy S II General] hospital349:
Cheers buddy. Means a lot.

Yeah, I visit it regularly; I've had it bookmarked on my browser for a while and recently subscribed after realising that I wasn't already. :p

Do you think the WIN!UV settings will translate well with other kernels? - I know you're the kernel master. ;) It'd be interesting to find out, but I'm all flashed out for the time being.
[Galaxy S II General] hospital349:
Cheers bro. Any problems (freezes/reboots) - let me know.
[Galaxy S II General] daz_2000:
Never flashed a kernel before. I've recently installed cm9 and enjoying that so far. But battery life could be better. Only rooted for first time when installing cm9. Sorry to be a noob. But what link do I grab from the neak thread? The zip or tar one and can I flash in recovery without losing data.

I've read up a little on kernels. To confirm my cm9 will remain the same visually etc. The kernel runs in background with the rom?
[Galaxy S II General] hospital349:
Hey.

You want to download the .zip file, locate the file in Clockwork Mod Recovery and flash it. All visual aspects of the ROM will stay the same, nothing to worry about there.

You shouldn't have any problems if you follow those simple instructions. :)
[Galaxy S II General] daz_2000:
Cheers. Will give it a go. Apologies for being thick. But do I want Samsung or asop one?:confused:
[Galaxy S II General] Dunki3:
For CM9 you need v2.0.4x AOSP/AOKP/CM9 Zip
[Galaxy S II General] daz_2000:
sorry for being a pain, I do learn, so wont ask same question again! :)

Do I need to wipe cache and davik cache after flashing neak?
[Galaxy S II General] Dunki3:
Yes, it's recommended.
[Galaxy S II General] daz_2000:
Thanks for the quick reply...here I go!
[Galaxy S II General] daz_2000:
When you say not to use 100. Is there a way to disable? Or should I slide to 800?
[Galaxy S II General] hospital349:
If you set your CPU Frequency to 200mhz-1200mhz, 100mhz will be missed out completely, even if it's visible on the list, it will be ignored.
[Galaxy S II General] :
Hi there, I used your settings for NEAK/CM9. Except the 200Mhz voltage since voltage control wouldn't go lower then 850:

850(200), 925(500), 950(800), 1050(1000), 1175(1200)

Anyway, it worked perfectly for 2 days but then I started to use F1 timing 2012 during the race. Every time after a minute my phone froze. I pulled the battery a few times but the problem was still there, each time after about a minute.

I then resetted the custom voltages and it fixed it again. I still have all the other settings which are working fine.

So I'm pretty new to this and I'm basically asking how to find the problem / tweak it for my setup.

Since the high GPU voltage isn't touched and I'm guessing the f1 app pushed the GPU a lot, I can rule that out. So it must be the 1200Mhz voltage... or the one that is being used when the f1 app is running. Like I said, I'm new to this and guessing here. But to me it looks like I need to find the speed the CPU is running at when the app is active and increase that specific voltage step by step until the phone doesn't freeze anymore right?

Other question, are there any apps or debug settings I can use to figure this out?

TIA.
[Galaxy S II General] Visentinel:
The issue is you can't judge a stable under volt until you have heated the CPU under load. So you actually need to find the lowest stable voltage that also works under loaf for example playing F1 or running your favourite benchmark over and over 4 to 5 times in a row.

A good rule of thumb is if it didn't crash up to 50 Celsius your good to go.
[Galaxy S II General] ksilver89:
Based on my reading in this forum and some simple math calculations, it actually show that undervolting really don't help much on battery life, in fact it is ~2X less significant than underclock. My observation for the past 2 months also proved that the theory is correct.

My UV Settings:

1200 (1150 mV)

1000 (1050 mV)

800 (950 mV)

500 (900 mV)

400 (850 mV)

300 (825 mV)

200 (800 mV)

100 (800 mV)

From my understanding, CPU power consumption only matters during high utilization and data processing, even the clock speed is only part of the influences, and not need to mention the voltage. If you need more battery, you should always tackle the screen brightness, wifi, use 2G, and also rogue apps. For the CPU part, underclock is the one you looking for, instead of undervolting.

just my 2 cent.
[Galaxy S II General] hospital349:
I can't really suggest anything other than what is written in my settings description, as I guess what works for me, might not work for others.

My settings haven't failed me under every situation I have put my device under. Whether it be for playing games, playing music whilst doing other tasks, running apps, using maps, tethering-music-internet (all at once). Fortunately for me, my phone doesn't even heat up to anything above 45 Celsius (which is because of the UV).

The only thing I can imagine it might be is that you have an app that is running in the background that your CPU/GPU isn't agreeing with. This can be resolved by using one of the following apps (which as the capability of disabling apps from independently starting up in the background, unknowingly):

https://play.google.com/store/apps/...vbS5lbHNkb2VyZmVyLmFuZHJvaWQuYXV0b3N0YXJ0cyJd (HIGHLY RECOMMENDED)

or

https://play.google.com/store/apps/...oolbox&feature=nav_result#?t=W251bGwsMSwyLDNd

Either one will cancel out any unwanted app processes from the get-go and this may/may not solve your issue.

EDIT: Also, up your 1200MHZ to 1175mV. I have had a ton of issues with it on 1150mV and wouldn't recommend it.

EDIT 2: Be sure to double check all of my N.E.A.K. Config app settings along with the Lulzactive settings and make certain that they're identical. Even the slightest difference can sporadically change performance.
[Galaxy S II General] hospital349:
How any Roms have you flashed in the past?

How many kernels have you flashed in the past?

The only advice I can give you is, if you've been flashing over and over again throughout the past few months, try a complete full wipe... that's back-up any important stuff on your device and

fully format

your internal memory and external storage. There could be some files from previous Roms/Kernels that haven't been removed after flashing again and are clashing with your current Rom and Kernel.

That's all I can suggest.

I had issues in the past regarding UV and that was the only method that solved everything.

I know it's a pain, but if you're looking to resolve your UV woes, this may work.
[Galaxy S II General] hospital349:
For anyone who might be interested in giving this a try... I upped my ASV busfreq to Level 5 without any issues.

More tasty UV for our bellies, delicious!! :silly:
[Galaxy S II General] sianzb0i:
Thanks guys for the reply. But im kinda interested in what does each level do. For example do each level have a template on CPU,gpu voltages or what changes does each level make to the phone. Cos i wanna understand rather than follow blindly :) . So it would be nice if there was a documention on what it does (sorry if i didnt search hard enough)

BTW im on NEAK GB, not ICS haha. Prior to this thread im alrdy on these voltages and settings. I believe my GPU values can go as low as shown on first post. Hope to save more batt life as my phone's batt life is still not to my standard. :(
[Galaxy S II General] LukeNukem:
tested it know some days and all in all it works good,

but sometimes it freezes when under heavy usage or

when waking up from deep sleep

(use ur settings but just go to a max of 800 hz)

its nothing too annoying, but maybe you can suggest something?

or shall i just go back to busfreq lvl 4? :)
[Galaxy S II General] hospital349:
Back down to level 4, yeah :laugh:

It was worth a try.
[Galaxy S II General] TheStigx:
Should WINUV work right away?

Or do I have to empty my battery and then charge it again, a few times?
[Galaxy S II General] sianzb0i:
UV is undervolting, which is supplying less voltage for the same clock speed than stock. Stock usually sets voltage higher than it minimally needs to achieve stability so it wont freeze. So we are reducing to save juice.

For ur question, you need not empty your battery. Just UV as normal. Probably u wanna monitor from a full charge? Its your choice :)
[Galaxy S II General] TheStigx:
That answered my question perfectly ;) Thanks!

Lets see how it does :P
[Galaxy S II General] WhyLen:
Can you please elaborate the steps of a complete full wipe, internal memory and external storage? Thanks.
[Galaxy S II General] sianzb0i:
Normally for heavy flashers, we use cleaning scripts (clean extra residue data from each kernel) and just wipe dalvik cache thru recovery mode (hold vol up+home+power). Other than dalvik theres also a normal cache parition.
[Galaxy S II General] hospital349:
He's tried all of those methods and more. He is still finding it very difficult to UV without problems which is why I'm recommending the full wipe method. It is uncertain whether the method is completely necessary but might deem valuable to some people having numerous freezing issues whilst undervolting. WIN!UV has worked for around 95% of its users on this thread, so it's better that the 5% try every option before giving up.

Thus, a full wipe.

EDIT: A full wipe previously solved issues I had with freezes and now my device can undervolt perfectly.