yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] hospital349:
Simone has kindly asked me to test 2.0.6x. You are not going to be disappointed.

I only flashed a couple of hours ago and improvements are clearly noticeable. I'm using WIN!UV v2.1 settings (unreleased until tests are complete ;)) and I'm getting 1% battery drop with 15 minutes of music (played through phone speaker on high volume), with the screen on. I've browsed using Chrome for 10 minutes, again with only 1% battery drop. Best kernel... EVAAAAAAHHH!!
[Galaxy S II Original Android Development] hospital349:
More on 2.0.6x:

Disbelieving my battery stats...

14 minutes on GTA3 = 2% battery decrease.

UNREAL!!
[Galaxy S II Original Android Development] cammel:
Please try virtual tennis challenge, and tell us how much battery it drains with your settings, it eats my battery really bad every time I play it, and Also it is really an addictive game!! :p

Enviado desde mi GT-I9100 usando Tapatalk 2
[Galaxy S II Original Android Development] omniwolf:
these "amazing" results mean nothing, full discharge then full recharge, and don't test off 100%. test from 99% or lower.
[Galaxy S II Original Android Development] Milkman12:
Hello to everyone!

First of all I have to mention this is my first custom rom I installed on my galaxy S2. It's awesome. A lot better without the TouchWizz and it has a lot of personalization options. I don't think I will ever install an official rom.

The battery drain looks ok, everything works normal, but the touch scroll it's fantastic.

I get some erros: "android.process.acore unfortunately stopped". I've read on this topic http://xdaforums.com/showthread.php?t=1470862 the cause is facebook app but isn't installed. Also, I will recommend you to install a default calendar. I wanted to install myself the calendar from S3 but it gives an error. By the way, which calendar app do you recommend? I found only widgets on the market.

Keep up the good work!
[Galaxy S II Original Android Development] CamoGeko:
^This isn't a ROM dude, its just a kernel.

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Original Android Development] hospital349:
Stats are stats dude. Battery life is battery life. Reality is reality. Theese are my personal experiences. If I can see a difference, then the difference must exist.

I didn't charge before/after flashing. I began testing the new kernel at 89%.

1st cycle, 2nd cycle, 3rd cycle; they make a significant difference to battery life. If I'm getting these results during cycle one, things should only get better from here on out.
[Galaxy S II Original Android Development] omniwolf:
i disagree and believe you're giving false results to people who read your posts. you should do your due dilligence if you want to be a respected member of these forums.

if you don't believe me, do you believe gokhanmoral?

http://xdaforums.com/showpost.php?p=24855128&postcount=3957
[Galaxy S II Original Android Development] sam razzy:
This is true
[Galaxy S II Original Android Development] hospital349:
So you're literally telling me that If I used to experience 5% battery drain playing 15 minutes of GTA3 before (after 4 cycles) and now I'm experiencing 2% drop using the new update within the 1st few hours, that I am misconstruing the truth? It's just my first impressions dude and it is visibly noticeable upon using my device.

I lost 0% battery overnight.

I lost 1% battery listening to music for 15 minutes with the screen on.

I lost 1% battery using Chrome for 10 minutes.

I lost 2% battery playing GTA3 for 15 minutes.

I spent 15 minutes on Youtube and dropped another 2%.

If the percentage drop is minimal, that tells me great battery life is present. (Whether these results are approximate or not.)

Gokhanmoral aimed that post at people complaining about battery drain. I'm not complaining. I'm praising the new update (2.0.6x) - which I am currently testing and I aim to provide users & Simone with info about my

INITIAL EXPERIENCES

of the build. Battery life is included within these experiences. Others include performance & responsiveness. All of which are improved from the get go. Are these false facts also?

I guess the only real way to settle this is to give it a couple of cycles and then provide you with wonderful results. I can assure you, they will be.
[Galaxy S II Original Android Development] omniwolf:
yes.. this is what i'm "literally" telling you. when you change a kernel (that thing that controls all your low level hardware), you need to callibrate your battery to get proper readings. how do you do that? some phones you reset the battery statistics. with the SGS2 you drain and charge once or twice.

ok i think you are getting confused. i'm not saying that on your phone you didn't see the battery % metre go down by 2% or whatever. i'm sure that happened, i believe you. but until you drain and recharge, you cannot trust the battery metre. it's as simple as that.

use your brain :) unless you only sleep for one hour this is a pretty telltale sign that the battery isn't reading properly. if you can leave the phone on for 8 hours a night 3 nights in a row and get 0% battery drain each night i will eat my hat.

see above - you see this on your battery metre, but you cannot trust these readings until you have properly calibrated your battery.

great that you are doing this, but the answer is YES. battery cannot be reliably reported on "initally". performance, responsiveness; sure. battery: no.

yes please! this is all i ask. if you wait a couple of cycles you will give your readers a reliable report. please note (i'm sure you're aware of this already): even if after a couple of cycles your results are still amazing, this doesn't prove your previous testing method to be correct. but if you're attempting to get 0% overnight drain after a couple of cycles, i don't think it's gonna be an issue :)
[Galaxy S II Original Android Development] hospital349:
Understood & thanks for the info. :)
[Galaxy S II Original Android Development] ram3n:
+1 Well said mate. Finally someone with wise words here :D

The only best ultimate killer prove is to let us test ourselves the kernel.

I'm always using my Xtrem UV settings (even more aggressive than ever) which works perfectly with anothers kernels.

Now I wanna give it a try with latest Neak. :p

Come on Simone, just release the Beast on the arena :D

Sent from my S2 monster
[Galaxy S II Original Android Development] Milkman12:
Sorry mates for the wrong post. I know it's a kernel. I hope soon I will come with a feedback.
[Galaxy S II Original Android Development] wolfmenace:
This is the Galaxy SII Specs:

Stand-by	Up to 710 h/29.5 Days (2G) / Up to 610 h/25 Days (3G)

Talk time	Up to 18 h 20 min (2G) / Up to 8 h 40 min (3G)

There is no way on earth I can get these kind of results even with extreme undervolting... :D:D

Just a Theory...........

We know that kernels have no effect on modems , right?

how the heck can someone save more battery by just talking on the phone with different kernels since kernels do not affect modems ? :confused:

Also does the extreme undervolting affects the modems performance/battery drain?

I want to see someone do this test :

Call someone / accept the call / and let your phone on with the line open.....

I wonder in how many hours your phone will die...

Then change the settings to extreme undervolting and try it again and check how many hours you will be able to talk more with Extreme undervolting .....
[Galaxy S II Original Android Development] nrk_2k:
Sorry,

This is also incorrect. Not only do you not need to 'calibrate' your battery in the SGS2, but you CAN NOT 'calibrate' it. The "fuel-gauge" chip is in the battery itself, and by design CAN NOT be calibrated. And because the chip is in the battery itself, pulling the battery etc. will do absolutely nothing to the chip as it is constantly powered by the battery. Even draining the battery until it no longer has enough juice for the phone to turn on (the best way to destroy your battery by the way) the chip will still be powered as it requires very very little power to run. The variations in battery level that you get are due to many things, which can NEVER be properly rectified. The "fuel-gauge" chip only 'guesses' the battery level by comparing its current state with known maximum and minimum values and presenting a 'guess' as to what the current level is (this can vary with current environmental conditions like temperature, humidity etc.). The other issues are to do with the way that the software interprets the information given by the "fuel-gauge" chip. Unless the kernel you flash (or a cleaning script you use) deletes the phones software "fuel-gauge" files, the software side of things should be pretty accurate, otherwise yes it will take a little while and a few cycles for the software battery history to build back up to provide more accurate interpretation of the information passed from the battery. This isn't 'calibration', it is just statistics, the more data to sample from (bigger sample size) the more accurate the result. The hardware "fuel-gauge" is reasonably accurate, but does have some inaccuracies (due to temperature etc.) which is why the software (drivers etc.) are used to 'smooth' the results and provide more accurate information.

As far as for 0% battery drain over 8 hours, I think this is indeed possible. I quite regularly get 1% drain overnight (with 3G data on). So if I can get 1% with it on it would not surprise me if 0% could be obtained with airplane mode on.

Good battery life is simple, turn off anything that draws current for as long as possible. Current draw == battery drain. Spending all this time throwing 'half-baked' ideas around about how to 'calibrate' a battery that cannot be 'calibrated' is not useful. Explaining how to kill applications that cause wakelocks, use profiles to turn off unused hardware while asleep, etc. IS useful. Our fuel-gauge system will ALWAYS have inaccuracies and "issues" that can NEVER be fixed (just like all cars do). Information like CPU Stay-Awake time and Wake-Locks are much more useful information (and a lot more accurate) for preserving battery life. If we spent as much time discussing ideas around these points instead of the silly "mine is bigger than yours" games everyone is playing we would all have awesome battery life, so lets focus on that huh?
[Galaxy S II Original Android Development] hospital349:
I have my data connection set to 'off' whilst my screen is off. It's a AOKP feature. That's why my battery consumption is so low overnight.

---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------

Very useful and great logic.

I agree wholeheartedly.
[Galaxy S II Original Android Development] lionsmatara:
Is new vr comming soon?? :eek::eek:

Oh i cant wait... i cant wait.. :D
[Galaxy S II Original Android Development] omniwolf:
hello.

thanks for your large post about calibration. unfortunately i don't disagree with you on anything you said, but as you started your post with "sorry, that is incorrect", i believe you disagree with mine. maybe you read the word "calibrate" in my post and immediately assumed i was presenting the idea that we had to calibrate our battery (in the traditional sense). this isn't my point. please reread my post, all of your points seem reasonable and valid (at face value, not in relation to my post), but rather tangential.

well i'm jealous :) that extrapolates out to 33 days of idle time with 0 screen on time i suppose. even if you were exagerating by twice as much, that's still over 2 weeks of phone on time. i could only wish for a half of that.

not sure how it relates, but i agree with you.

half baked huh. i guess we'll have to agree to disagree. if you think you can just slap on a new kernel with a changelog as expansive as NEAK's and not let everything settle over a cycle or two, well you're crazy (of course this is only from my point of view, experience, and knowledge. please don't take offence).

and finally, i agree, but again i'm not sure how this is pertinent to our discussion. oh well :)

anyways, thanks for jumping on the bandwagon, i'm done with this discussion.
[Galaxy S II Original Android Development] nrk_2k:
Yes, you are right, I take calibrate at face value, and it is the use of 'calibrate' that I disagree with in your post, not your methodology. As I agree with you in letting things smooth out over a few cycles. Your suggestion of waiting a few cycles for most accurate results is tried and true, not disagreeing with that one. Its the other ideas that I am calling "half-baked" like pulling the battery out. As for the rest of my post, it is aimed at getting people to work together to get the best methods that actually work to get the best battery life, rather than just skirting about how long we have our individual phones lasting. Hope I didn't offend you, yours is one of the few posts I agree with in regards to battery, asides from the use of calibrate that is ;-) (sorry, its a pet hate as its used far too much on these forums.)
[Galaxy S II Original Android Development] edwardeutsch:
The best...the best...the best kernel on CM9!!

Don't stop the party simone!

I'm re-trying and all is smooth!

Tapatalk @ CM9 - NEAK
[Galaxy S II Original Android Development] msquared:
That username.... seems i've already seen it but i don't remember where...:D

+1 awesome kernel,and with a bit of UV gets better
[Galaxy S II Original Android Development] xelra:
So isn't the problem of this discussion just about wiping battery stats?

I'm a user of battery monitor widget and after each flash I just reload stats from bmw history. That way it's immediately accurate.

Never had to let anything "settle" for a few cycles that way.
[Galaxy S II Original Android Development] omniwolf:
funny, it seems your only problem is the idea of pulling the battery out, but you're the only one who has brought this up. i have never suggested this :)

anyways, glad we can agree for the most part :)
[Galaxy S II Original Android Development] Milkman12:
I installed this kernel on a custom rom named Dark Angel through the option flash update .zip in CWM and my phone wasn't booting. In recovery mode I saw some options like changing frequencies, voltages. Does this mean unsecure kernel? I used Odin and download mode an flashed Siyah kernel. Afterwards I saw the option "flash kernel" in CWM. I will try and install it properly today.
[Galaxy S II Original Android Development] bajee11:
Lol you don't use flash update. Zip unless your kernel is named update. Zip. You have to use Flash zip from sd card and choose the kernel file you placed in your internal or external memory.
[Galaxy S II Original Android Development] edwardeutsch:
OT hahaha menegooo! Yes i use sio - ondemand. UV -75 for each step (200-1000)!

Tapatalk @ CM9
[Galaxy S II Original Android Development] nrk_2k:
Haha yeah, I know you didn't bring it up, I was commenting in general, not just replying to your post ;-)

The only reason I have issues with this topic is because I am trained as an electrical engineer, and did a fair bit of research on smart batteries, so kinda an area of expertise for me. And having seen so many mistruths being posted up on xda as if it is the gospel truth and 100% working irritates me as xda is meant to be about improving our phones, where as some of the methods I have seen posted on here do the complete opposite. So my post wasn't so much aimed at correcting you, but trying to correct other misinformation out there on the forums. :-D just trying to do my part to help xda users :-)
[Galaxy S II Original Android Development] Evewon:
Well said! You just fed my brain! "thanks" to you good sir
[Galaxy S II Original Android Development] MaKTaiL:
Hey Simone :)

Any luck on fixing Mobile Odin Support?
[Galaxy S II Original Android Development] :
Simone, I have the N.E.A.K. Configurator Pro app like most of the people on this thread. Just have a question and small request if it's not too hard... Is it possible to have a backup of the UV settings we input into this application? I always wipe my phone and try new roms and I find it a bit tedious to adjust my settings again...

A quick back-up and restore option would be awesome! :D
[Galaxy S II Original Android Development] nrk_2k:
Hi,

I am working on this at the moment :)

In the next update you will be able to save your settings to app storage. With this type of storage you need to remember to back up and restore app data with Titanium Backup as any ROM that wipes data will also wipe your settings ;) I am hoping to maybe have the update ready by next weekend (as I am too busy this weekend with moving house). There will be a couple of new features introduced (with saving settings being one of them). :)
[Galaxy S II Original Android Development] anaweb:
When issued version 2.0.6x ????
[Galaxy S II Original Android Development] :
Thanks! Best Kernel for the S2, hands down!
[Galaxy S II Original Android Development] Mr.Greg:
Is this kernel support MDPI on SAMMY roms?
[Galaxy S II Original Android Development] CamoGeko:
MDPI support is provided by the ROM, not the kernel. ;)

Sent from my 80GB CyanogenMOD 9 + Siyah ICS powered beast. Booya!!
[Galaxy S II Original Android Development] edwardeutsch:
Hey simone! Some news?

Tapatalk @ CM9
[Galaxy S II Original Android Development] simone201:
Yeah, 2.0.6x is ready but as i am also working on the GS3 i don't have much time...:(

Anyway i hope i can release it during this week, to make everyone happy
[Galaxy S II Original Android Development] edwardeutsch:
So...last version for GS2? :(

Tapatalk @ CM9
[Galaxy S II Original Android Development] simone201:
No, don't worry ;)
[Galaxy S II Original Android Development] Mr.Greg:
No mate. I can confirm with Lpd version of sammy rom after changind dpi on 182, phone won't boot, stuck on kernel logo, tested on cf root and abyss, then flashed siyah kernel, on same rom, same dpi, and phone turn on. Also tested Dorimanx kernel and is ok. That's why I'm asking. Thanks for reply, Sir.
[Galaxy S II Original Android Development] lionsmatara:
Bro simone plz dont leave us.. :(we have only sgs2. :(Plz keeping ur devoloping with sgs2:o
[Galaxy S II Original Android Development] edwardeutsch:
Grazie simo!

Tapatalk @ CM9
[Galaxy S II Original Android Development] nguyentramy87:
Waiting for new version, too :D

Love your kernel. You're great ^o^
[Galaxy S II Original Android Development] yeahtyeaht:
s3 is oredered. hope to see ur kernel soon fpr the s3 :D
[Galaxy S II Original Android Development] nrk_2k:
This is not a kernel fault. Kernel has nothing to do with dpi changing. A lot of people have successfully changed dpi on neak without any issue. It likely was something else causing the issue.
[Galaxy S II Original Android Development] fridlack:
Hi

I am new with neak kernel, flashed it over wanam v12 without problems, just buy neak configurator pro from market and i want to set it to get best battery life without losing many performance :P

Here are my setting atm

Kernel Options:

Conservative Gov: Cheked

Lionheart Tweaks: uncheked

Lazy gov: unchecked

sched_mc: checked

AFTR idle mode: uncheked

Ext4 Boost: checked

CPU control

Max: 1000

Min: 100

CPU gov: conservative

I/O: sio

GPU control

Max: 267

Min: 133

Max Voltage: 950

Min Voltage: 850

Voltage Control

1200: 1175

1000: 1075

800: 975

500: 925

200: 850

100: 850

Screen control

Min Gamma: 0

Max Gamma: 24

Min_BL: 50

Misc options

Dyanamic Hotplug

Off: 35

On: 70

Did you recomend to change anything to optmize it?

Thanks for your help and best regards
[Galaxy S II Original Android Development] lionsmatara:
Oopz.. nice..:eek:

Can u play mkv without any problem?

How many hours can u use ur battery?
[Galaxy S II Original Android Development] AllSeeyinEye:
Simone, did you change something in one of the later releases in AFTR idle? Because I always had it turned on on GB without a problem and in the first releases on ICS it didn't give me problems also, but from 2.0.4x and in 2.0.5x it gives random reboots, once or twice a day...

Turned it off right now, but since it's one of the major battery savers, I'd like to turn it back on.

Any ideas or possibly a solution?
[Galaxy S II Original Android Development] simone201:
Nope i have changed nothing about it...turn it off then
[Galaxy S II Original Android Development] AllSeeyinEye:
Tnx for the quick reply. I'll await the 2.0.6x release and will test again :)
[Galaxy S II Original Android Development] fridlack:
Hi

I instaled NEAK this morning, then i cant help you with battery questions until 2-3 days of normal use :)

About the MKV i will try it this night and report the result...

...but, why are you trying to play a 720 video when your screen have less resolution?
[Galaxy S II Original Android Development] lionsmatara:
Hey mate..

Can i knw ur ASV level?
[Galaxy S II Original Android Development] fridlack:
Sorry, I don't know what is asv... If you explain how to check it I will take a look
[Galaxy S II Original Android Development] msquared:
Go in recovery-kernel options-AVS bus frequency
[Galaxy S II Original Android Development] fridlack:
I didnt touch nothing in recovery, then the values are = to default

After read your post i undestand that AFTR idle saves battery, i enabled it and seens my phone is stable, no random reboots, no freezes from 5 hours ago

Than my configuration is now:

Kernel Options:

Conservative Gov: Checked

Lionheart Tweaks: uncheked

Lazy gov: unchecked

sched_mc: checked

AFTR idle mode: checked

Ext4 Boost: checked

CPU control

Max: 1000

Min: 100

CPU gov: conservative

I/O: sio

GPU control

Max: 267

Min: 133

Max Voltage: 950

Min Voltage: 850

Voltage Control

1200: 1175

1000: 1075

800: 975

500: 925

200: 850

100: 850

Screen control

Min Gamma: 0

Max Gamma: 24

Min_BL: 50

Misc options

Dyanamic Hotplug

Off: 35

On: 70

Any recomendation? maybe i must to change the ASV voltages via recovery?
[Galaxy S II Original Android Development] msquared:
Try to rise the avs step by step,standard level is 3 rise it to lvl 4 then 5 until u get to lvl 7 but some devices(like mine) can't keep at higher levels,now i'n at level 4 because on 5,6 and 7 i've freeze...try rising it and see if u can keep an high level ;)
[Galaxy S II Original Android Development] robberknight:
Hi,

I'm running the N.E.A.K-2.0.5x with an original Samsung ROM. The kernel works and battery usage is down from the original kernel. But I have a strange problem:

DNS does not work anymore, unless I configure my wifi with a static ip and wifi is available during boot.

I have tried to find out what is going on and found this: the system properties used for dns are missing when the problem is there:

# getprop | grep dns
[dhcp.wlan0.dns1]: [192.168.3.254]
[dhcp.wlan0.dns2]: []
[dhcp.wlan0.dns3]: []
[dhcp.wlan0.dns4]: []
[net.rmnet0.dns1]: []
[net.rmnet0.dns2]: []

So all the net.dns... entries are missing. When calling (as root) e.g.

setprop net.dns1 192.168.3.254

nothing happens - the property doesn't show up. Only when the property was there at some stage in boot (like booting with wifi on and a static ip), the net.dns properties are there and can be used and changed. It seems like something is hindering the property manager in init to create new properties after a certain stage in boot has been reached. I have already straced init while setting new properties and I can't see a difference between the two kernels. But the property storage is in ram so I just see that the setprop is received.

Does anybody have an idea what could cause this?

Here is some additional info about my rom:

[ro.build.date]: [Tue Apr 3 19:44:49 KST 2012]
[ro.build.description]: [GT-I9100-user 4.0.3 IML74K XWLP7 release-keys]
[ro.build.fingerprint]: [samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XWLP7:user/release-keys]
[ro.build.hidden_ver]: [I9100XWLP7]
[ro.build.host]: [DELL134]

And I'm running my phone with full device encryption - don't know if this is relevant.
[Galaxy S II Original Android Development] lionsmatara:
Where is v 2.0.6? :rolleyes:

Teek teek... im keeping my eyes on this... :confused:

When we can new N.E.A.K monster...:D:D:D