yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] ciprigeorgiu:
I don't see any difference in battery life but I can see an increase in signal strenght between s2 and s4 drivers. and It's quite considerable. So after all S4 driver are better.
[Galaxy S II General] pedestre:
I agree, signal seems to be stronger and wifi is more estable with new drivers and with S2 drivers sometimes there was a strange battery drain and with this new drivers it never happened to me.

If everything is normal (not strange battery drain), I can't see any difference in battery life either
[Galaxy S II General] It_ler:
So, it's not a "magical" wifi driver, but it doesn't make things worse :fingers-crossed:

BTW, I have to repeat my night use battery for Apolo v4.7 light, as I had some corrupt files on my internal sd card which caused 57m of MediaScanning and an "unusually" high battery loss.

Corrupted files are fixed now and I have already checked that MediaScanner only runs for less than 1m on my phone after rebooting.

Now preparing battery tests again.
[Galaxy S II General] pedestre:
jajajja, no , I guess there are no magical drivers of nothing, but I think these drivers improve wifi conections on several users (at least they have told me that)
[Galaxy S II General] It_ler:
Apolo v4.7:

First result on AnTuTu directly after wifi short test: Apolo v4.7 (XWLSS NeatROM Lite v4.7): 8959

Will repeat the benchmark after next battery test.
[Galaxy S II General] It_ler:
Apolo v4.7:

Moderate battery life in night use.

Apolo v4.7 light (XWLSS NeatROM Lite v4.7): Battery loss of 0,59% per hour, Awake: 1,5%

It's a little bit worse than on v4.6, but still ok.

I am running Apolo kernel v4.7 light with light voltages and completely default settings.

Here are some screenshots:
[Galaxy S II General] It_ler:
Apolo v4.7:

Fantastic battery life in mixed usage.

Apolo v4.7 light (XWLSS NeatROM Lite v4.7): Battery loss of 1,18% per hour, Wifi: 10,4%, Awake: 11,7%, Screen: 10,3% => loss*(1-screen): 1,06%

It's nearly the same as on best run with v4.6. Amazing !

With light version and no manual changes.

EDIT: Second result on AnTuTu: Apolo v4.7 (XWLSS NeatROM Lite v4.7): 9778

Here are some screenshots:
[Galaxy S II General] ciprigeorgiu:
is ondemand and cfq the default in this kernel?
[Galaxy S II General] It_ler:
Yes, it is. And I haven't changed it on v4.7 yet.
[Galaxy S II General] It_ler:
Re-test Apolo v4.7:

Excellent battery life in night use on second (long) run in "night" use.

Apolo v4.7 light (XWLSS NeatROM Lite v4.7): Battery loss of 0,43% per hour, Awake: 1,9%

It was a long (about 18 hours) standby test to verify its battery life when phone is idle/sleeping.

So it was the same battery test as always in night use, but only for a longer period of time - usually my night use battery tests run about 12 hours.

Still on completely kernel defaults - and on light version.

BTW, third run on AnTuTu: Apolo v4.7 (XWLSS NeatROM Lite v4.7): 9940

Here are some screenshots:
[Galaxy S II General] It_ler:
Re-test Apolo v4.7:

Slightly worse battery life on second run in mixed usage.

Apolo v4.7 light (XWLSS NeatROM Lite v4.7): Battery loss of 1,25% per hour, Wifi: 10,2%, Awake: 11,8%, Screen: 10,1% => loss*(1-screen): 1,12%

But this is still a very good battery life and confirms the battery fantastic battery test results on my phone with light usage.

Here are some screenshots:
[Galaxy S II General] cripubu:
Hello Itler! After all this Apolo enthusiasm (seems we landed on the moon again) could you test latest Phil¨s??? Thank you :D
[Galaxy S II General] cnjax:
Why keep testing philz only thing which changes is the recovery?

GT-I9100 powered by

NeatRom Lite 4.7

Apollo 4.7 v1

JB Reloaded + MYLR blue theme
[Galaxy S II General] Many40:
Maybe It_ler would add to his thread another type of tests: CWM recoveries battery tests (how much battery is drained by different CWM recoveries while phone is in recovery mode ;):D
[Galaxy S II General] mr_zuff:
But it's not fair!

Most of us use TWRP recovery when on Apolo kernel... how can you compare battery life on CWM with TWRP??? No way!!! :D :P
[Galaxy S II General] Many40:
Why not ? We compare different kernels' versions and types so why we can't do the same for recoveries :D
[Galaxy S II General] mr_zuff:
Hat's off master! :D

But I wonder... how much screen on will CWM reach? On a heavy usage I mean :P

It_ler, now it's your turn! :D
[Galaxy S II General] It_ler:
Recovery battery tests :laugh:

Back to topic :cool:

I will for sure test latest PhilZ kernel, but as it was already said, PhilZ is stock kernel.

So this will always be a kind of verification of my previous stock/PhilZ kernel tests.

Maybe I will check XWLSW ... then latest PhilZ kernel will surely be my first choice.
[Galaxy S II General] cripubu:
yes cnjax, you´re right. got it myself reading the changelog :silly: but anyhow, i have better results with philz than with apolo 4.7 ...
[Galaxy S II General] It_ler:
Re-retest Apolo v4.7:

Even slightly better battery life on third run in night use.

Apolo v4.7 light (XWLSS NeatROM Lite v4.7): Battery loss of 0,36% per hour, Awake: 2,1%

This was a normal night with about 8,5 hours.

So the excellent battery life in previous "long" standby was not caused by the long time ... this kernel has fantastic battery life on my phone when idle.

Here is a screenshot of BBS with the times (Other stats):
[Galaxy S II General] bobdoblo:
I have basically the same on Apolo as Philz and i have gotten my best ever on Philz.

That is on Light version, so same voltages as Philz.

Regular and Extreme my phone isnvt stable like It_lers.

Btw It_ler what CPU group is your phone?

Mine is 2

★NeatROM★ Mods ********************* Battery Tips
[Galaxy S II General] Many40:
Bob, my is in group 2 too :confused: but I can UV quite deep and even extreme Apolo settings are not so extreme for me :eek::confused:

This works stable in my phone:

200MHz (825mV), 500MHz (950mV), 800 MHz (975mV), 1000 MHz (1075mV), 1200MHz (1150mV)
[Galaxy S II General] It_ler:
I will check my CPU group as soon as I flash Dorimanx kernel.

Yet, I don't know about my actual CPU group :confused: (Hope that it's not group 1 :eek:)
[Galaxy S II General] bobdoblo:
To be honest, i haven't really tried regular Apolo :o i tried extreme. I just assumed it wouldn't because i'm group 2 and my phone only OC to 1.4Ghz, it lasts less than a minute at best on 1.5Ghz and 1.6Ghz is just a no go.

I will flash Apolo and try your voltages:thumbup:

How much can you overclock?

But group2 must be good really because we get great battery life:thumbup::)

★NeatROM★ Mods ********************* Battery Tips
[Galaxy S II General] Many40:
TBH my phone is fast enough for my daily use even for some HD games being UC to 1000MHz (what is more battery friendly) so never had a need to try OC/OV. So, simply I have no idea :)
[Galaxy S II General] bobdoblo:
Yeah, i just wanted to know to see if it is all down to this CPU group thing or if there is anything else that affects it.

If these groups are true then you should only be able to do 1.4 too.

Would there be any benefit of overvolting 200mhz - 1.2Ghz?

What is ESD btw?

★NeatROM★ Mods ********************* Battery Tips
[Galaxy S II General] Many40:
No, OV might be needed while OC to keep phone stable. But generally they can cause more harm then benefit IMO.

Edit: ESD is for sure outside his toilet, otherwise he would be posting :D
[Galaxy S II General] genothomas:
From where now the CPU group came? What's is actually? :confused:
[Galaxy S II General] Many40:
From Dorimanx (latest) kernel. You can check it from Dorimanx STweaks app. Theoretically higher group -> your phone is able to stand deeper UV

(posible groups: 1-5).
[Galaxy S II General] bobdoblo:
Just tried Many, everything was going fine, swiping homescreens fast for about 30 secs then i opened camera and got black screen and reboot.

I put it on Pegasusq+sio too because that's what you use.

So it looks like its not just the CPU group:cool:

★NeatROM★ Mods ********************* Battery Tips
[Galaxy S II General] Many40:
I don't use 1200MHz so not sure about 1150 mV setting (it's set in my phone but not used) so might unstable on my phone too.

Please increase it to 1175 or 1200, try again and report pls.
[Galaxy S II General] bobdoblo:
Hmmm... All seems fine:)

On it now, tried scrolling, tried camera, tapatalk, still here............ Still here....... :thumbup:

Edit, still here:D

Very surprised my phone can handle that much UV:eek:

Edit2, Thats lower than Apolo Extreme v2:eek: apart from 1.2Ghz step.

Thats why it didn't handle it before when i tried because 1.2 is too low, maybe same problem for It_ler?

★NeatROM★ Mods ********************* Battery Tips
[Galaxy S II General] Many40:
That's gteat but a litle to early to celebrate - keep monitoring.

Btw My advice is - never use predefined UV settings because every phone's hardware is different and behaves differently on each frequency. So by testing/ trials find your own custom UV settings which will work stable on your phone.

Ps if you experience freeze again increase voltage for 200MHz to 850mV
[Galaxy S II General] bobdoblo:
Dropped 1.2Ghz down to 1175mv and all seems well, been watching it hit 1.2Ghz on

2nd Core (Can shut off core only on Siyah, Many) app and no problem so far....

Edit, Browser killed it! Back to 1200mv:thumbup:

Edit 2, Now 3 hours later and still good:thumbup:

★NeatROM★ Mods ********************* Battery Tips
[Galaxy S II General] It_ler:
Just tried this UV (even with sio/pegasuq), but I had SODs very soon.
[Galaxy S II General] It_ler:
Re-re-retest Apolo v4.7:

Again a very good battery life in night use.

Apolo v4.7 light (XWLSS NeatROM Lite v4.7): Battery loss of 0,40% per hour, Awake: 2,3%

I think I have to stop testing this kernel now.

Even without any UV, I get this excellent battery life on my phone with my light usage.

I will keep a nandroid backup of this system on my phone.

Maybe it's time to test latest Dorimanx now?!

Here is a screenshot of BBS (Other stats):
[Galaxy S II General] It_ler:
Dorimanx v8.28:

Ok, now I have flashed Dorimanx v8.28 kernel on my XWLSS NeatROM Lite v4.7.

It says that I have voltage group 1.

Wifi toggle doesn't work on my phone. Can't turn on wifi :crying:

Bluetooth, GPS, etc. works fine.

Camera, video recording, Gallery and FM radio works fine too, but live thumbnails in video player are all black again.

Will abort this kernel test, as I really need wifi on my phone.
[Galaxy S II General] Many40:
Group one? :eek: What a pity - that's really bad. TRB is on Group 3 :(
[Galaxy S II General] bobdoblo:
I

I really don't understand where Dorimanx is going with his kernel?

He adds more and more stuff that hardly anyone will end up using but the basic things are still broken months later!

I know people like the option of tweaking but its gone too far and he is neglecting the basic fundamentals of things just working.

Fix the default things you expect of a kernel before adding more stuff!

The irony of it all is more and more people are using stock because they offer the best balance of stability, performance and battery.

The most popular ROM & kernel are:

NeatROM - Basically stock Sammy ROM

Philz - Basically stock Sammy kernel

What happened to the days of the fantastic 5.92 version?

Group 1 It_ler:cool:

Is that how it works, the lower the number the worse the chip?

★NeatROM★ Mods ********************* Battery Tips
[Galaxy S II General] It_ler:
Partly agree ... I always prefer easy steps: Flash and enjoy !

Group 1 needs overvolting on some CPU frequency steps ... Dorimanx said.

I know that since JB times, my phone is very "sensible" about UV.

But in GB and ICS times, I could run Phenomenal Extreme kernel without any issues.

But on JB, every undervolted kernel (Apolo, HiroX, etc.) leads to SODs on my phone.

So I will keep stock voltages ... and I have very good battery life when idle and in my light usage too.

No need for me to "cry" that I have a CPU of voltage group 1.
[Galaxy S II General] It_ler:
PhilZ v5.06.1:

I just flashed PhilZ kernel v5.06.1 on my XWLSS NeatROM Lite v4.7.

It is very stable and very smooth on my phone.

Everything works fine.

First result on AnTuTu: PhilZ v5.06.1 (XWLSS NeatROM Lite v4.7): 9626

Now preparing battery tests.
[Galaxy S II General] kadivarz:
i think you shouldn't test every version of dorimanx kernel

u only test the stable release as it counts as a basic ref..

for example the last release u should be testing or puttin its result is 8.14

i dunno if am right but thats wat i do i only install the version that he says its

stable otherwise its gonna be hard to catch up with the releases
[Galaxy S II General] It_ler:
PhilZ v5.06.1:

Moderate battery life in night use.

PhilZ v5.06.1 (XWLSS NeatROM Lite v4.7): Battery loss of 0,62% per hour, Awake: 1,6%

Very good deep sleep ratio, but battery life was not so good IMO.

I am sure that with a better settling down of the battery stats chip (on a second or third run), the battery life will be a little bit better.

Here is a screenshot the BBS (Other stats):
[Galaxy S II General] It_ler:
PhilZ v5.06.1:

Good battery life in mixed usage.

PhilZ v5.06.1 (XWLSS NeatROM Lite v4.7): Battery loss of 1,38% per hour, Wifi: 10,4%, Awake: 12,0%, Screen: 10,4% => loss*(1-screen): 1,24%

It's nearly the same as for "stock" NeatROM Lite v4.7.

So everything is "stable" on my phone :fingers-crossed:

Here are some screenshots:
[Galaxy S II General] It_ler:
Apolo v4.7:

After being a little bit disappointed with stock/PhilZ kernel, I tried Apolo v4.7 regular kernel.

And it runs stable ... with light CPU voltages.

So I will test this kernel version ... just to see the difference between light and regular version on my phone with my apps/settings/usage/ etc.

Everything seems to work fine so far :fingers-crossed:
[Galaxy S II General] Droodroid:
I made a switch to 4.2.2, Mackay ROM on Wed this week after having been on Neatrom with different kernels for over a year.

In my opinion its much smoother overall. Battery life has been similar so not much in it.

I think we are all so obsessed with finding the best ROM/kernel that we sometimes just need a change to feel like we've found something better :)

Anyway I just thought I'd put it out there, right now I could swear that cm10 with some tweaks by Mackay, is faster, smoother and more efficient than 4.1.2 in stock or Neat form.

As the Americans like saying YMMV.

Keep smiling
[Galaxy S II General] bobdoblo:
:confused:

If your using lite voltages then it will be the same as lite version wouldn't it?

★NeatROM★ Mods ********************* Battery Tips
[Galaxy S II General] It_ler:
Probably not.

There are different ARM, Bus and GPU voltages in light and regular (and extreme) kernel versions.

From kernel thread OP:

- Light (stock voltages)

- Regular (-50mV in ARM, internals)

...

Regular and extreme has -50mv UV in GPU (others UV like bus, memory, video controller too). Light has stock voltages in GPU​

So even after setting light CPU voltages, there are still different voltages in regular version.
[Galaxy S II General] cripubu:
so why is Dori uploading versions that HE KNOWS they are unstable???:cyclops:

---------- Post added at 09:13 PM ---------- Previous post was at 09:03 PM ----------

Hi It_ler! Allow one question pls. I have been with Apolo 4.7 for the last three days. Strange enough my phone gets hot when I am in internet. And once it´s hot it won´t cool untill I turn it off. I´m now on Sched. sio and gov. zzmoove with max freq. 1000. Doesn´t heat anymore, but performancewise :eek: What are the values you are on. I also have light use of phone.
[Galaxy S II General] It_ler:
1. Beta tests. xda is a good platform for devs to have a big test user base. In OP, you can read which version is test/beta test or stable version.

2. On Apolo light, I had light voltages and changed nothing in kernel settings => default scheduler + governor, max CPU freq. = 1200 MHz, everything stock/default.

Now on regular version, I set CPU voltages to light too. Rest is still on kernel defaults.
[Galaxy S II General] It_ler:
Apolo v4.7:

Moderate battery life in night use.

Apolo v4.7 regular (XWLSS NeatROM Lite v4.7): Battery loss of 0,55% per hour, Awake: 2,2%

It's nearly the same battery life as for v4.6 light, but worse than for v4.7 light on my phone.

Maybe I have to give it another try ... to settle down properly.

EDIT:

Added some screenshots:
[Galaxy S II General] It_ler:
Apolo v4.7:

Very good battery life in mixed use.

Apolo v4.7 regular (XWLSS NeatROM Lite v4.7): Battery loss of 1,27% per hour, Wifi: 10,2%, Awake: 12,2%, Screen: 10,0% => loss*(1-screen): 1,14%

But it's worse than on light version.

I'll repeat the battery test, just to see if the battery life for regular version are better on a second battery cycle.

Here are some screenshots:
[Galaxy S II General] GoldGanja:
Hi all, I would like to share my best result with the S2 so far... I've changed rom, now with miui 3.5.31 and latest PhilZ kernel.

I've frozen just 3 app (Screenshot ), greenify others a blocked autostartup of some others like Maps.
[Galaxy S II General] It_ler:
Re-test Apolo v4.7:

Nearly the same battery life on second run in night use.

Apolo v4.7 regular (XWLSS NeatROM Lite v4.7): Battery loss of 0,55% per hour, Awake: 1,7%

This time the deep sleep ratio was a little bit better.

If the battery life in mixed usage is not better, then I will check new XWLSW NeatROM Lite v4.8 ... for new base ROM.

But let's finish my current test for Apolo v4.7 regular first.

EDIT:

Added some screenshots:
[Galaxy S II General] It_ler:
Re-test Apolo v4.7:

Nearly the same battery life in mixed usage on second run.

Apolo v4.7 regular (XWLSS NeatROM Lite v4.7): Battery loss of 1,26% per hour, Wifi: 10,1%, Awake: 11,5%, Screen: 10,0% => loss*(1-screen): 1,13%

It's still a little bit worse than for light version on my phone.

Maybe regular version is already running on the "edge" of my phone's limits.

Here are some screenshots:
[Galaxy S II General] marcusmt:
It_ler

Neat Rom 4.8 LSW , its new testing ROM?
[Galaxy S II General] It_ler:
I just flashed XWLSW NeatROM Lite v4.8.

It's very stable and very smooth on my phone.

Everything seems to work fine so far.

I only had some issues to switch to MTP mode ... like bobdoblo.

After some changes and reboots, now it works how I want.

It's too early to say if this will become my new base ROM, but it looks promising.

EDIT:

First result in AnTuTu: NeatROM XWLSW: 9437
[Galaxy S II General] oskarpp3:
I think you mean xwlsw ! :good:
[Galaxy S II General] It_ler:
Yes, you are right.

Typo corrected now :o
[Galaxy S II General] It_ler:
XWLSW NeatROM Lite v4.8:

Moderate battery life in night use.

NeatROM XWLSW: Battery loss of 0,58% per hour, Awake: 1,8%

It's in the "normal" range of last NeatROM Lite versions on my phone.

Now i am checking its battery life in mixed usage. If this fine too, this will become my new base ROM for further kernel tests.

EDIT:

Added some screenshots:
[Galaxy S II General] bombaybadboy:
Hey guys can I ask if you remember what version of philz came with neatrom lite 4.7?
[Galaxy S II General] mr_zuff:
Philz v5.00.4 ;)
[Galaxy S II General] It_ler:
Just have a look here for detailed information about XWLSS NeatROM Lite v4.7.

Everything is in NeatROM thread ... you only have to find it ;)
[Galaxy S II General] marcusmt:
My firts night use on Apolo V2
[Galaxy S II General] It_ler:
XWLSW NeatROM Lite v4.8:

Good battery life in mixed usage.

NeatROM XWLSW: Battery loss of 1,32% per hour, Wifi: 10,2%, Awake: 11,7%, Screen: 10,1% => loss*(1-screen): 1,19%

Nearly the same as for v4.7.

So there are nearly no differences between XWLSS and XWLSW battery wise on my phone.

I think I will prepare moving to a new base ROM.

BTW, second run on AnTuTu: 9357 (so no update for first post).

EDIT:

Added some screenshots:
[Galaxy S II General] It_ler:
PhilZ v5.06.6:

Just a teaser for my upcoming battery tests with PhilZ-touch kernel v5.06.6 on XWLSW NeatROM Lite v4.8.

It was in Airplane mode during the night (about 8h 45m with 99,7% deep sleep ratio) and on a fully charged battery (100%) ... so nothing special IMO:
[Galaxy S II General] It_ler:
PhilZ v5.06.6:

Will do my battery tests next week. Need a "free" weekend.

BTW, first result on AnTuTu: PhilZ v5.06.6 (XWLSW NeatROM Lite v4.8): 9834
[Galaxy S II General] egps2:
Hi guys on NeatROM Lite 4.8 with included PhilZ kernel and UC/UV settings as shown in sig I get around 2 hours and twenty minutes screen on time from 50% battery which is good for me but nowhere close to what some are posting for Apolo!

Ps screen shot won't attatch sorry! I'll try and add it later.

Sent from my GT-I9100

EDIT: I use Tegrak Ultimate to UV/UC on stock roms and kernels but it's a paid app
[Galaxy S II General] bobdoblo:
:confused: You can't UC or UV Philz kernel!

★NeatROM★ Mods *********** Battery Tips
[Galaxy S II General] parag1dubey:
+100 :confused::confused::confused:

---------- Post added at 12:44 PM ---------- Previous post was at 12:43 PM ----------

+100 :confused::confused::confused:
[Galaxy S II General] Vivek_Neel:
Am very much eager to know about how did you do uc/UV in philz kernel?.:confused:
[Galaxy S II General] egps2:
Hey guys you usually can't but I use an app called Tegrak Overclock (see sig) which I purchased over a year ago and it still works well on JB. It is a paid app though so it's not for everyone but it was great for people like me who only used to use custom kernels for voltage control and this is the only one that works on stock samsung kernels provided they're rooted. It also let's you adjust clock speed and voltage for the two GPU steps which I sometimes do when I know I need the extra juice and won't be playing any games.

Here's the link for anyone who has some spare cash and wants this feature:

https://play.google.com/store/apps/details?id=com.tegrak.overclock.ultimate

Some people report licence issues and a failure to work properly on JB but at least for me personally it works well and always has. From what I remember the free version does not allow UV but it does allow OC if that's all you were interested in.

EDIT: To anyone wondering I can't be 100% sure it works but I am 95% sure because when stress testing the cpu it produces much less heat; it only get's a little but warm where as before it would get uncomfortably hot.
[Galaxy S II General] parag1dubey:
[MENTION=4638454]egps2[/MENTION] AFAIK, if a kernel itself doesn't support underclocking and undervolting, i don't think a third party app can change voltages

.... Please check again..
[Galaxy S II General] egps2:
Thanks for sharing your concern but I heard about this by knowledgeable developers back in GB days and for me at least it seemed to work fine since then and even now. This is a quote from [MENTION=3484113]tegrak[/MENTION] who made the app: "My app does not need custom kernel. In addition no reboot, can change at runtime. This is a big differrence from another apps."

Is anyone else using Tegrak Ultimate to back me up on this? I know there is definitely a big reduction in heat output while getting the same benchmark scores so it definitely feels like it's working for me and if it somehow reduces heat without UV or reducing performance then I'm still happy. If I set the voltages very low the phone becomes unstable and crashes if I UV irresponsibly low so this again suggests it works and I doubt Tegrak coded it to crash the phone to make it seem legit!

EDIT: This APP only works on certain Samsung devices like the S2 and is not like other apps that work on a number of devices by communicating with supported kernels.

If you search you'll fine many people UVing successfully on Tegrak: http://xdaforums.com/showthread.php?t=1289644

I'm not saying anyone should buy it (I think dev has stopped anyway) but it seems to work for lots of us :)

EDIT 2: Official mention on XDA website: http://www.xda-developers.com/android/tegrak-updated-for-all-galaxy-note-ii-and-10-1-devices/

Edit 3: from an XDA moderator
[Galaxy S II General] Many40:
[MENTION=4638454]egps2[/MENTION]

Hi, that's something new for me as well.

Btw Did you check just in case by other (non tegrak) CPU monitoring/tweaking tools like CPU adjuster or CPU spy, if the voltages are really changed?