yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] tupo05:
Stupid question or just a coincidence ? Since using NEAK 1.3 when i use my camera, the rectangle focus turns red (when taking the picture) instead of green. And as a result, the picture is not as clear as it should be. ( Happens on normal scene and text scene).

Camera was working fine under other ROM/Kernel.

Could it be kernel or Rom related ? Right now I'm on CriskeloRom V37 and NEAK 1.3 ( Vr scheduler/conservative governor) with Lionheart tweaks enabled.

thanks in advance.
[Galaxy S II General] urfel:
I just checked on mine, and rectangle turns green while taking a picture (light in the room is dimmed at the moment). Did you try that indoors or outside?
[Galaxy S II General] tupo05:
hummm. thanks for trying. yes I tried both indoor and outdoor. Just wanna make sure it's rom or kernel related ? what rom/kernel are you using ?
[Galaxy S II General] nrk_2k:
This is more than likely an app or rom issue. The red box means the application was unable to focus the camera. This could be due to a number of problems. First thing to check would be that the lens on the camera is clean and free of scratches. If using the stock camera app, try downloading and using another app of marketplace and see if you get the same problem. If other camera apps work fine, then it is an app problem. If all apps have the same issue, first thing to try would be a re-load of the ROM & kernel, if issues still persists, it could be a hardware issue.

Hope this helps you identify the issue.
[Galaxy S II General] tupo05:
Thank you so much. I'll check what you said tomorrow
[Galaxy S II General] alexnative:
i'm using CheckRom and thunderbolt scipt... i'm really like this kernel... but why i maybe the only one here got SoD ?

i've delete cache, dalvik cache...

No UV and governer is Lulzactive....

are there any solution for me ?

or just me ? can't use my lovely SGS2 with this awesome kernel :(
[Galaxy S II General] nrk_2k:
Some people had trouble with the Thunderbolt script on this kernel. I'm pretty sure it was getting looked into, if not already fixed by the Dev. Are you able to try the kernel without the Thunderbolt scripts to see if that is the problem? You may also want to try raising the voltage settings for cpu/gpu up a little bit as the settings in the kernel are close to, but not exactly stock. Also what Frequencies are you using 200-1200 or 100-1200?
[Galaxy S II General] alexnative:
Freq i'm using is 200-1200..

okay i'll try to remove the thunderbolt script to see the result ...

thx mate....
[Galaxy S II General] It_ler:
Results for SpeedMod / Phenomenal / void / N.E.A.K. / Siyah / stock kernels

Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.

For all custom kernels, I was running on Frankenstein XWKL1 ROM (Modem: XXKL1).

For stock kernels, I was running on the corresponding stock ROM.

Always using the Samsung's standard / stock 1650mAh battery.

For void.echo I enabled the UV - nothing else.

For Siyah, as it has many, many configurable settings, I have changed nothing - just default settings.

For N.E.A.K. 1.x (Lulzactive) I tested the default setting with VR schedule and Lulzactive governor – nothing else changed.

For N.E.A.K. 1.2 (Lionheart) I tested SIO schedule, Conservative governor and Lionheart tweaks enabled – rest unchanged defaults.

For N.E.A.K. 1.3 (Lionheart) I tested VR schedule, Conservative governor, Lionheart tweaks and sched_mc enabled – rest unchanged defaults.

Here are my current results:

Benchmarks

Battery stats

Wonderful N.E.A.K 1.3 !

With VR + Lionheart + sched_mc it is still smooth on my phone and has very good battery savings.

I am looking forward to run new versions of this kernel.
[Galaxy S II General] _Garry_:
thx It_ler for the test. my feeling about lionheart/vr+sched_mc were right.

the only problem i see coming, is the fact that void.kernel and neal kernel nearly aim for the same goal. minmalistic kernel but still powerfull in each terms.

will be hard to deside which kernel i will use.

- xda premium - gti9100 - insanity cm57 - Stock Rom Kernel :: lionheart/deadline 100-1200 mhz :: -
[Galaxy S II General] urfel:
I am currently on N.E.A.K. 1.3 with WanamLite 6.7 (killer combo :D)
[Galaxy S II General] rzat:
Hi, do you mind share your lulzactive app settings. Trying to compare different setups.

Many thanks
[Galaxy S II General] _Garry_:
everybody talks about thunderbolt...but what is thunderbolt??? what is it for or better what can it do for the s2??

- xda premium - gti9100 - insanity cm57 - Stock Rom Kernel :: lionheart/deadline 100-1200 mhz :: -
[Galaxy S II General] nrk_2k:
Thunderbolt are some optimisation scripts. I don't use them, so can't tell you exactly what they do, but here is the link to the Thunderbolt Script thread :D

http://xdaforums.com/showthread.php?t=1354709&highlight=thunderbolt

Hope it helps!
[Galaxy S II General] :
basically they give better performance on top of the already given scripts inserted in the kernels that we all use..I am currently using newest version of the scripts and phone seems alot smoother and faster and just overall better performance and stability for the phone....like nrk just given above check on the link of the thread and read the first post and explanation is given better there.:) now each time i flash a kernel i must have the scripts with me.....
[Galaxy S II General] _Garry_:
i have read it, didnt understood it, and dont care....lol

naa, i can see what the dev is aiming for with his script. but i wont use it. my phone runs smooth and stable...except for kernel and there i will wait for neak.

never change a running system ^^

- xda premium - gti9100 - insanity cm57 - Stock Rom Kernel :: lionheart/deadline 100-1200 mhz :: -
[Galaxy S II General] kersey:
Which of the governors is more suited to battery saving - lulzactive or Conservative (with Lionheart tweaks)...can't decide which to use as both are super smooth in this kernel :p
[Galaxy S II General] _Garry_:
as tested from it_ler, lionheart/vr+sched_mc on is better for battery when using stock values.

when you want to undervolt, then you need play around. we cant help you there because each phone is unique and with different roms it even harder.

here is the test

http://xdaforums.com/showthread.php?p=21287854

- xda premium - gti9100 - insanity cm57 - Stock Rom Kernel :: lionheart/deadline 100-1200 mhz :: -
[Galaxy S II General] dancinmilkman:
just flashed 1.3.1, phone wont boot tried everything, reflashed turned on with power button, fix permissions, misssing anything??? on checkrom v4
[Galaxy S II General] AllSeeyinEye:
Just reboot with the power button. Should do the trick

Sent from my GT-I9100
[Galaxy S II General] Didgesteve:
Fix for 1.3.1

This worked for me

http://xdaforums.com/showpost.php?p=21414764&postcount=1138

I have IO/Governor set to SIO/Conservative (with Lionheart tweaks), ARM cpu enabled, and it's running very smooth, no problems at all.

Bit early to say if there is any change to the battery life, but I'll know by tomorrow.

Thanks Simone, great work.
[Galaxy S II General] Didgesteve:
Testing

After a couple of days of testing I have to say that the battery life is amazing. Turning off the wifi when I'm not using it, and disabling google maps and synchronising has pushed the battery life to nearly 4 days (2000ma battery).

Unfortunately there is always a BUT....

the only thing I've noticed is that I can't get a GPS lock when using this kernel. I'll be honest and say I dont know enough about kernel builds to say how it effects the modem. But I've tested it a couple of times.

I'm using Hyperdriod rom, and if I stick with the HDK1.1 or the older UltimateKernel v2.7 the gps locks in 5 seconds, as soon as I flash to NEAK it refuses to lock.

I've tried lots of modems and KI4 is the best for where I live, so I've always wanted to stick with that.

I'd be grateful for any suggestions, as I really want to use NEAK, but no GPS is a problem.

Thanks.
[Galaxy S II General] dubist:
nearly 4 Days with your 2000ma battery ? i have a original 2000ma battery too but i come only 1 to max 2 days .

What did you change UV ?

WHICH SCHEDULER AND GOVERNOR ?
[Galaxy S II General] nrk_2k:
Battery life mainly depends on usage & what you have turned on/off. Undervolting can save you some battery, but we are talking a very small saving. The get a battery life of 4 days, phone usage would have to be pretty low, with things like WiFi, 3G, GPS turned of when not in use, and also stop as many unnecessary processes as possible. :D
[Galaxy S II General] Manitax:
UV is not small battery saving. As the cpu consumes most of the juice (on higher frequencies) uv makes a big difference.

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II General] Myshkinbob:
Since there's a bit of discussion regarding battery life and UV, i thought i'd post my results with neak v1.3.2x testing this weekend, so far as standby goes.

stock rom: XILA2

modem: KI4

Here were the test conditions....

radio

network is t-mobile orange in the UK, i have the phone set to 2G mode and wifi is permanently connected. To give you an idea of the network power drain, the 2G signal tends to vary between -85 and -90dBm, which isn't pefect but it's ok, and my wifi router is on the other side of the house so wifi is a pretty weak -80dBM, around 0-1 bars on the status bar.

sync and push

Accounts and sync are left on default aside from google+ being disabled. The other apps syncing and receiving push messages in standby are: Fancy Widgets on a 30 minute refresh, google talk, and touch messenger (formerly pingchat).

disabled apps

Since it's a stock rom i should mention i disabled a few known offenders for standby drain. AP widget and accuweather are both frozen, along with google maps (replaced with an app called Osmand).

Undervolt

I didn't underclock, governer was lulzactive, frequencies were set to 100Mhz-1200Mhz. I undervolted by -100 to -75mV for most frequency steps. See the attached image for UV details (ymmv).

Result

I left the phone in standby from mid-afternoon to midnight, with the battery around 70%, and during that time it received 5 SMS, 2 gmail pushes, 3 touch/pingchat pushes, and nothing from gtalk. Fancy widget synced the weather etc. I was pretty surprised at the result, losing around 1% every 2 hours. :)

I logged the exact battery % change with an app called Battery Indicator Pro, and the image is attached below.

I'd previously done this same test the day before with the stock XILA2 kernel and lost around 1% an hour, which i thought was pretty decent too. The only differences this time were using neak 1.3.2x and the cpu undervolt. Otherwise same apps, same network, same modem, same phone location, and actually less sms/touch/gmail traffic in the previous test.

I haven't gotten around to testing screen-on battery drain on neak yet, but i did take a baseline with the stock kernel for video playback, 7% an hour with video playback at 50% volume and the screen set 25% brightness, for a standard TV rip (xvid, 624x352, mp3 sound). So at some point this week i'll replay the same hour-long episode with neak.

Hope this proves helpful regarding the battery usage debate. :)

Edit:

conclusions

I didn't really draw my own conclusion from my result and left that open. I don't know enough about the exact changes in the neak kernel to say how much they effect standby battery drain. I also didn't keep a record of the wakes during the tests, suffice to say that the betterbatterystats wakelocks and the android battery graph screen looked similar.

If i had to guess though, i think the uv plays some small part in reducing the drain from standby wake/sleep cycles, but a larger part is probably due to neak allowing use of the 100MHz frequency step, whereas the stock kernel wakes to a minimum 200Mhz at a higher voltage.
[Galaxy S II General] nrk_2k:
Sorry, This is incorrect (for the most part, the CPU only becomes a high consumer of battery when it is under a lot of load, even then the screen still consumes more, CPU @ full load is about 0.6-0.7W, screen at full brightness about 3W). The biggest battery consumers on your phone are the Screen & depending on usage, 3G/LTE, WiFi, & Bluetooth (The components on the device that use a radio signal require a higher current draw to produce the necessary output wattage, main drain will only happen when they are actually in use and sending data). Battery drain is measured in mAh (Milli-Amp-Hour) and since Undervolting has little effect on the current drawn by the CPU, it has little effect on battery drain. The amount of Voltage being used doesn't affect the drain on the battery, the amount of current is what affects battery drain. The thing UV is best at is keeping your CPU cooler, (and it is the fact that it is cooler that saves you battery, as resistance increases with temperature, which in turn increases current draw). The best you could hope for with UV is a few % battery savings over a period of a day. Also, the frequency state at which the CPU is in doesn't affect the current draw until the CPU is under load. If the CPU is in an idle state, it will use very little battery as it is not processing much. As you increase the load on the CPU, current will increase and drain the battery more. This is why higher frequency states consumer more battery, as there is far more information being processed.

Summing that all up, Turning off WiFi, 3G/LTE, Bluetooth & Screen (or dimming the display) will have a much better effect on battery life than UV ever could. Also, killing the number of processes that are consuming CPU time (stopping the CPU from going idle, or as close to) will also have more effect on battery life than UV. Also, underclocking will have more effect than UV as it is reducing the maximum CPU states so that at full load it will use less current. I am not saying in any way that UV wont save you some battery, I am just saying there are many other things you can do that will save you a lot more battery.

Note (for those that don't have much electrical knowledge):

Voltage is not drawn from a battery - it is the potential difference between the positive and negative terminals on the battery. Components in the electrical circuit connected to the battery can use a percentage of this voltage (with 100% being the maximum). This has no effect on battery 'drain'.

Current is drawn from the battery - This is what causes the drain on the battery. Current is only capped to what the batteries capacity is. (a 2000mAh battery can produce 2000mA for an hour before it becomes fully drained, or 4000mA for 30 mins before being fully drained)
[Galaxy S II General] It_ler:
Results for SpeedMod / Phenomenal / void / N.E.A.K. / Siyah / stock kernels

Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.

For all custom kernels, I was running on Frankenstein XILA2 ROM (Modem: XXKL1).

For stock kernels, I was running on the corresponding stock ROM.

Always using the Samsung's standard / stock 1650mAh battery.

For void.echo I enabled the UV - nothing else.

For Siyah, as it has many, many configurable settings, I have changed nothing - just default settings.

For N.E.A.K. 1.3.x (Lulzactive) I tested VR schedule, Lulzactive governor, only enabled sched_mc and the rest unchanged defaults.

For N.E.A.K. 1.3.x (Lionheart) I tested VR schedule, Conservative governor, Lionheart tweaks, sched_mc enabled and the rest unchanged defaults.

Just finished my tests for N.E.A.K. v1.3.2x and added its results.

Here are my current results:

Benchmarks (in Performance governor if available)

Battery stats

N.E.A.K. v1.3.2x performs very good on my XILA2 ROM.

Best thing is not the benchmark scores (which are very good ... even some new high scores), but its stability and that it is very configurable.

I will test N.E.A.K. v1.3.2x with VR/Conservative and Lionheart tweaks enabled, as this had better battery savings on my phone in former versions.

Then I plan to test latest Siyah kernel, because at least Simone201 and me are very curious about this comparison.

Will be back with my results in a few days.
[Galaxy S II General] Manitax:
You are right in some aspect but not all.Here is my proof for my assertion. Read this post and you will think different.

http://www.android-hilfe.de/showthread.php?p=2422412

If you don't understand German here is one picture i took from there that should be understood easily.

The difference of uv 75 mV on 1200mhz Is the amount of juice a white screen consumes with 25% brightness.

And You see that on high frequencies the cpu is the biggest consumer and NOT the screen! Sure on idle you will not feel a big difference but while playing around with the phone or gaming there you will see it.

Cheers.

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II General] nrk_2k:
That was an interesting read, Google translate put it in English for me. I'm not sure if the translation made it not make much sense, but from what I read, all his measurements were taken from the battery terminals. Which makes me query the reliability of his results. As my information was taken from direct from manufacturer specifications of the individual components. If his measurements were taken from the battery and the wattages calculated from those measurements, then the CPU measurements would also include GPU, RAM, cache and onboard memory. As all these components are linked in with the CPU when processessing. A CPU running at idle should consume very very little power as it is not processessing anything, and therefore the internal transistors would not be changing state, and so no need for power consumption. From the diagram above, it appears that dropping the voltage on the CPU is also causing a drop in current draw. This fact alone makes me query the results, as the current shouldn't change that much from a voltage change. As a CPU is essentially an array of transistors, the voltage effects only how fast the transistor changes state. The lower the voltage the slower the transition. None of this should have much effect on current, apart from the reduced heating on conductors. If I could speak German I would talk to the guy directly and see how he did his tests etc, and this might help clear things up for me. As it stands I will have to do some more research as his results completely contradict the manufacturer specifications. Thank you for posting that link. I will look into this and post back what I find out.

Edit: Ok, so after a quick investigation using the phone's built in sensors, I get a much more expected result of the CPU being one of the smallest consumers of battery (until put under heavy load). I will post up results from a clean test after a full charge and normal daily use (for me). This should then give a pretty clear picture as to what can best be done to save on battery :)
[Galaxy S II General] It_ler:
Results for SpeedMod / Phenomenal / void / N.E.A.K. / Siyah / stock kernels

Everything is specific to my phone, my "normal" usage and my home location. Most values are exact results, but some are rounded. I usually have wifi, synch (three email accounts, calendar and news), Google Talk and Skype on.

For all custom kernels, I was running on Frankenstein XILA2 ROM (Modem: XXKL1).

For stock kernels, I was running on the corresponding stock ROM.

Always using the Samsung's standard / stock 1650mAh battery.

For void.echo I enabled the UV - nothing else.

For Siyah, as it has many, many configurable settings, I have changed nothing - just default settings.

For N.E.A.K. 1.3.x (Lulzactive) I tested VR schedule, Lulzactive governor, only enabled sched_mc and the rest unchanged defaults.

For N.E.A.K. 1.3.x (Lionheart) I tested VR schedule, Conservative governor, Lionheart tweaks, sched_mc enabled and the rest unchanged defaults.

Just added my battery test results for N.E.A.K v1.3.2x with Conservative governor and Lionheart tweaks enabled.

Here are my current results:

Benchmarks (in Performance governor if available)

Battery stats

So, my previous statement about N.E.A.K. v1.3.2x remains:

Impressive stable and configurable kernel.

On my phone, there is no significant difference between Lulzactive and Conservative governor with Lionheart tweaks enabled.

Now it is time to test Siyah v2.6.9 ...
[Galaxy S II General] Myshkinbob:
There isn't much a mystery to it. You mention that voltage shouldn't change the current draw very much from the cpu, aside from the lower temperature reducing transistor leakage. Lets forget leakage though, consider how the cpu gets it's power. You're correct that once temperature is disregarded, any change in cpu voltage won't change the cpu's own current requirements, However...

It isn't wired directly to the 3.7v battery, it has it's own power regulation circuitry that steps down the 3.7v from the main battery to the 1.3v or 1.1v or 0.8v as requested for the frequency step in use. Remember from high school that power = current * voltage (P = I * V). So undervolting your cpu works as such:

Lets say at 1200MHz full load the cpu draws 500mA @ 1300mV, that's Power = 0.5 * 1.3 = 0.65 watts. This is the cpu's power requirement, that must be satisfied by the main 3.7v battery via the cpu power circuitry. So what is the drain on the battery from this?

Rearrange P = I * V, we know p is 0.65, and the battery is 3.7v, so I = 0.65 / 3.7 = 0.175 amps. So the cpu is drawing 175mA from the battery. This is slightly naive and assuming perfect efficiency from the cpu power circuit, admittedly, but it works for the explanation.

If you undervolt by 125mV, so the cpu now draws 500mA @ 1175mV, that's 0.5 * 1.175 = 0.59 watts. Immediately you can see that reducing the voltage has reduced the power requirements of the cpu. How does this affect battery drain? Well the drain on the main battery would be 0.59 / 3.7 = 0.158 or 158mA.

You can see that a 10% reduction in cpu voltage will mean a roughly equal reduction in battery drain when the cpu is loaded. So if you game for an hour at full load in this example, then the cpu alone is responsible for 175mAh at stock, or 158mAh undervolted. it's only a 17mAh saving, which is about 1% of battery life on a 1650mAh battery.

So that's how undervolting does in fact does reduce the current drawn on the battery by the cpu. :)

EDIT:

Note this isn't actually how it works for cpu's, the power equation is going to be more complex. Aside from the fact the example guessed at the cpu current draw (500mA), the relationship of voltage to power in a gated transistor cpu isn't as straightforward as P = I * V. If you're curious you can get more realistic information from intel's blogs and posts like http://software.intel.com/en-us/blogs/2009/08/25/why-p-scales-as-cv2f-is-so-obvious-pt-1/ . I'm no expert but i think the short of it is in cpus the relationship of power to voltage is based on the square of the voltage. In other words rather than voltage reduction having a linear effect on battery drain, the battery drain reduction will be greater than the initial voltage reduction.