yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] olifee:
The 'decent' results should be decent in benchmarks only, your high readahead-values will make random accesses to sdcard much slower, especially for a card with class < 10.

If you do not have random accesses, but only copy large files (such as movies) to and from your card, you are good with the high values ;).

If you want to benchmark a real-life scenario, you might use iozone or fio.

---------- Post added at 11:43 PM ---------- Previous post was at 11:36 PM ----------

I don't have those problems with 2.6.8 in gallery app, although I am also using QuickPic most of the time.

Did you find a result for your card corruption? If not, and in case it happens again, it might either be related to the loop-problem in 2.6.7 or your card might be broken (like my 32 GB class 10 card was). To check the latter, try h2testw (on Windows) or F3 (on Linux / guess also MacOS, Solaris or others).
[Galaxy S II Original Android Development] manyakurt:
I have lots of freezing. Sometimes, phone cant wake up, screen isnt shown just black screen. Three times I remember in a day, just flashed 2.6.8 yesterday morning.

MIUI @ 500-1400 performance.
[Galaxy S II Original Android Development] gokhanmoral:
another late night changes...

in v2.6.9:

I added Entropy512's changes to sec_battery driver to show battery charging current and changed it a little bit to map the adc readings to real charging current miliamps (mapping is done in an unscientific way but it works). you will be able to see how fast your device is being charged and also why those 100%s are not the same. I am now at 100% and my device is still being charged for half an hour with 300mA.

so, as I have already said many times, those "oh my god, I lost only 1% in 10 hours" statements are just useless crap.

and also I replaced the adbd in initramfs to fix MyPhoneExplorer phone keypad not functioning problem.

I reverted back some changes (cpu alignment and slqb) and used old-good toolchain (2009q3).

lastly, I added tegrak's home key double click fix. (thanks to Tegrak)

I will test it for a day and then release.
[Galaxy S II Original Android Development] PedroMRP:
Why revert slqb?
[Galaxy S II Original Android Development] olifee:
That's actually pretty cool, really looking forward to it :).

To those now crying "awww, crap, why doz my batter not draw full current anymore, fix it now!":

As far as I understood, Lithium-batteries are normally charged with constant current up to a certain voltage, and then with constant voltage, so the drawn current goes down.

That also conforms with everything I saw on the phone up to now: Percentage rises really fast up to some value, then, charging becomes slower, and even after 100 % is reached, it still takes some time until it really is 'full'. You can also see this when you look at the battery voltage over time.

People who built models of cars, ships etc. will also know fast chargers for Lithium batteries which keep the current-loading phase active some time longer to reach 'real' 100 % faster. Those chargers, however, normally check temperature of the battery to stop charging when it becomes hot (our phone also does that I think, though I never experienced it myself) and the lifetime of the battery should be reduced.

After all, Lithium batteries live longest if they are neither fully charged nor fully depleted and do not become too warm. For laptop batteries, it is often recommended to only fill them up to 100 % if you really need it, and otherwise charge them to 60-70 % and stop there. Worst thing is depleting them, so if you love your phone / battery, never do that ;).
[Galaxy S II Original Android Development] gokhanmoral:
just to be safe. I think slub is simpler and I don't see any noticeable performance and/or battery advantage of slqb. honestly, I am at the same distance to those two and I am open to suggestions about reading and/or benchmarks about those. I believe most kernel developers choose slqb just to make a difference and I could not find any good benchmark suggesting that slqb is just better.
[Galaxy S II Original Android Development] PedroMRP:
Between those two I don't know my experience with slab and slqb, slqb wins in terms of battery life and that is my main goal.

But if you say that slqb and slub are equals then its all good.
[Galaxy S II Original Android Development] AndreiLux:
Before anybody starts whining about how I'm not using my phone: I've been home most of the week and had no reason to.

This really makes me wonder how accurate the battery reading is, or how bugged the software must be. There's clearly something wrong going on starting at about 40% lifetime and goes ape**** at 80% where I turn Wifi back on. Usage then flat-lines for a good 20 hours, and the end again drops drastically. About 1 hour screen on and about total 3 hours of radio playback.

Makes you wonder. In my opinion, there's much wrong going on in terms of power management.
[Galaxy S II Original Android Development] omniwolf:
the bit where it drops heavily to 85% lifetime seems a bit suspicious, exactly 85% (you can tell because it changes colour exactly when it flatens out)? why? maybe trying to recalibrate ?
[Galaxy S II Original Android Development] mariosraptor:
No problem whatsoever with 2.6.8. A lil bit of undervolting for cpu and gpu. I get a day easily with most of the day wifi on.

3g on and sync on. Also bluetooth on all day. Paired with an itech bluetooth headset
[Galaxy S II Original Android Development] gokhanmoral:
6 days??

you must be living by a base station :)
[Galaxy S II Original Android Development] CamoGeko:
No wonder it's going ape****, you got tonnes of wakelocks right there. If I'm reading it right that is lol

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
[Galaxy S II Original Android Development] :
Really freaking loving this kernel.:)

Anyone wants my settings feel free to message me ;)
[Galaxy S II Original Android Development] AndreiLux:
I check the phone from time to time, and saw that it was draining stupidly without me doing anything, so I re-enabled Wifi to look if it would change something, and it did; but only for a while before things got bad again.

-75dBm 15 asu signal, nothing spectacular. I seriously think I'd be able to idle it to about 10 days if I figured out what the heck is eating up power like that.

Forget the bar graph in the battery stats for wake time on extended periods, the graph rounds up any wakelock to 1 pixel, and if you have a large time period the granularity gets too small for it to be properly represented. That and the graph itself is bugged sometimes showing its awake when it isn't. If I went by the graph then it would mean I have around 4 days of awake time, sorry but my phone isn't that awesome. (Real time was 4.5h)

That's the thing. I don't know *which* wakelocks. It wasn't wifi related wakelocks, those were <15minutes summed up. I had 1h15m of deleted_wakelocks at a count of 42000, and svnet locks summed up at about 2 hours. 22 and 15 min of alarm_rtc and alarm wakelocks respectively. The huge drop at the 80% mark may be due to the rising svnet, as that was the only extended period without Wifi on, but I have no idea from where it comes from. Application wakelocks were fine other than a justified 42min from Trillian keeping the C2DM connection alive. It's stupid as I cannot possibly trace it, you'd have to check the phone's dmesg log every hour to see if something unwanted is happening, and then that by itself is like Schroedinger's cat and may skew any observation.
[Galaxy S II Original Android Development] Honusnap:
Hi all,

Seen that on your last 2.6.9 :

"Set topoff current in battery driver to 100mA (stock value is 200mA) to ensure that the battery is fully charged before the charger circuit stops charging. Your 100% level will be a bit higher than before."

For what i know, it is not a good move to "overcharge" a Li-Polymer battery... partial charge are better than full charge. It is also better to charge your phone when it is off... no load on the phone means no drain on the battery, this will ensure that the correct voltage is reached.

---------- Post added at 11:45 AM ---------- Previous post was at 11:42 AM ----------

Betterbatterystats to know where the wake-lock come from.

Which radio/Modem are you using ..?
[Galaxy S II Original Android Development] gokhanmoral:
It is not overcharge actually. The charging voltage will be the same but it will feed that voltage a little longer.
[Galaxy S II Original Android Development] b2rdetor:
it isnt overcharging. its a charge with constant voltage and 100 must be better than 200 (batery will charged better - may be 10%) but charge time will encreased.

---------- Post added at 12:12 PM ---------- Previous post was at 12:10 PM ----------

my phone reboots twice since i installed 2.6.8... but 2.6.7 was much stable.

thinks that need to test cpu voltages (may be too low)
[Galaxy S II Original Android Development] Rampler:
@Gokhanmoral

special thanks for that (in 2.6.9):

reverted the adbd in initramfs to fix MyPhoneExplorer phone keypad not functioning

:):):)
[Galaxy S II Original Android Development] gokhanmoral:
v2.6.9 is up in my blog.

install CurrentWidget :)
[Galaxy S II Original Android Development] CamoGeko:
Time to flash. Happy dayz :D

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
[Galaxy S II Original Android Development] coolfire:
Awesome! Will you be trying with your same setup as well?

Sent from my SGSII
[Galaxy S II Original Android Development] droidphile:
I have my AC current set to 750 via script (just for fun) and CW shows 643mA.

So all clear about "either 450 or 650" story!!
[Galaxy S II Original Android Development] coolfire:
Wow, awesome! Finally CurrentWidget works! :D

Sent from my SGSII
[Galaxy S II Original Android Development] rauschkugl:
It works just when you charge your device.

Sent from my GT-I9100
[Galaxy S II Original Android Development] gokhanmoral:
and more importantly it will help you identify the cables&charger with bad quality.

some cables cannot hold that much of current (although it is not too much) while charging your phone.
[Galaxy S II Original Android Development] CamoGeko:
Already running 2.6.9.on my config mate. :D

Have noticed ondemand is slightly smoother, thanks for the tweaks gokhan.

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
[Galaxy S II Original Android Development] gokhanmoral:
it doesn't work when the phone is discharging.

I doubt our device has that information. we can read temperature, voltage level but not discharge current while the device is discharging.

or maybe there is a way that I don't know.

I checked all adc channels and could not find anything usual.
[Galaxy S II Original Android Development] :
Just out of curiosity is anyone here have the lulzactive app running ok for them?
[Galaxy S II Original Android Development] Cygnuss:
2.6.9 flashed great work congrats on your super Kernel! [[]]
[Galaxy S II Original Android Development] eybee1970:
tested 1.7.8beta4...got best smartbench with 1200mhz ever (no GPU-OC!) :D:
[Galaxy S II Original Android Development] GDT:
Is it right flashing with CWM or I need to flash through odin?
[Galaxy S II Original Android Development] SweSarah:
Deep sleep works perfect here.
[Galaxy S II Original Android Development] Orka82:
Same here.

Not when connected to the charger of course. :)
[Galaxy S II Original Android Development] :
Testing new combination and phone is really fast as hell, just have to see about battery life see attacment + SQLite Boost courtesy of LeoMar. Perfect so far :)
[Galaxy S II Original Android Development] jsompis:
Did you use smartass and 100-1200?
[Galaxy S II Original Android Development] gokhanmoral:
This is great news. if your phone is working fine I am sure that every others will work just as well :)
[Galaxy S II Original Android Development] Orka82:
Yes. Smartassv2 100 - 1200.

Using 1.7.8 and latest beta4.
[Galaxy S II Original Android Development] tolis626:
So,unless my phone was working more than fine with beta3,installing with CWM app is no problem at all.SD is mounting,reboots/freezes are gone,I had never faced a problem with superuser...All's fine! :D
[Galaxy S II Original Android Development] lenny12:
I have only 3500 with this Kernel.:confused:
[Galaxy S II Original Android Development] gokhanmoral:
guys, I need bug reports or else I will have to make a release candidate tomorrow :)

any comment on the battery life?

I received a feedback that the battery life of v1.4 was better than the latest beta3.

I think it may be related with the lack of root support for init.d scripts.

I will not release any new versions until I receive a serious bug report to see the battery performance of the latest beta.
[Galaxy S II Original Android Development] prydoxs:
i want to flash the kernel but do i have to play with the setting of GPU clock and voltage? can i use the kernel as it is?
[Galaxy S II Original Android Development] :
Yep, give us a day at least, but I think battery is fine until Samsung release 2.3.5 sources as ki3 kernel has great battery life.
[Galaxy S II Original Android Development] AndreiLux:
But this was on beta1. It ran just fine for me. Just flashed beta4 and checking it again. Hard to check battery life properly when flashing twice a day :p
[Galaxy S II Original Android Development] gokhanmoral:
And any feedback on android os usage?
[Galaxy S II Original Android Development] AndreiLux:
Did you change anything in the drivers? Because, I don't know if it's because of the kernel, newest ATT sources, or KI3 modem, but ever since for example the events/0 process will *not* eat any more CPU time like before. Before it would eat as much CPU as suspend when it bugs out. Now it's only like using 20s time for a whole day. The problem is that the suspend process still is bugging out at sometimes up to 1.5h time when it's bad.

Here it bugs out at around 50% mark until I reboot the phone later on. suspend process gained around 30m CPU time in BetterBatteryStats in that period and Android OS went from 30% to 75%. I didn't use the phone, and the bug triggered when I just check the time and battery (it became a stupid obsession to check for the Android OS bug) in the middle of the night.

I don't remember what kernel that screenshot was on, but it was from 2 nights ago. Will report back at the end of the day for beta4.
[Galaxy S II Original Android Development] Orka82:
You don't need to play with any settings if you don't want to.

The kernel works fine as is.
[Galaxy S II Original Android Development] :
Just removed it from charger, was charged up to 95% so you can not see much, but here is screen shot anyway.
[Galaxy S II Original Android Development] ebliss:
Just a question, I have a script in init.d which has

echo "1600000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

however, after booting, the scaling_max_freq remains as 1200000. If I run the script manually, the scaling_max_freq will be changed to 1600000.

Any ideas?
[Galaxy S II Original Android Development] GDT:
I'm on beta 4 now, just removed o/c daemon scripts and flashed superdaemon 3.0 again, cleaned cache and dalvik cache and rebooted. Now I'm using setcpu and stability test to check if it stays at 1.4Ghz. It starts so but then switch to 1.2Ghz while testing. Why?

By the way I'm definitively wrong with o/c daemon. Maybe I'm using and incorrect script or wrong daemon controller app settings?
[Galaxy S II Original Android Development] gokhanmoral:
works for me. you have to select lulzactive governor before using the app.

and since lulzactive governor is not the default governor of this kernel you have to select it with init scripts if you want lulzactive app to set your values on boot.
[Galaxy S II Original Android Development] droidphile:
Yes, i was thinking of the same.

Good news for benchmark freaks...You can now benchmark your charger too... (Even the power socket may be) :)
[Galaxy S II Original Android Development] Vaedryn:
With 2.6.9 for best battery is ondemand the best ? With 2.6.7 it was the best for me, 2.6.9 the same?

SGS II Cyanogen Mod Tapatalk
[Galaxy S II Original Android Development] Rampler:
I have understood that we have three frequency steps for GPU. Right ?

In VC I can adjust only two values. Are this values the low and high ?

Where i can find the explanation for this ?
[Galaxy S II Original Android Development] PedroMRP:
gokhanmoral nice work with currentwidget!

screen on: 638mA

screen off: 640mA (the value that appears the instant that I turn on the screen and then it drop to 638mA)
[Galaxy S II Original Android Development] :
Thank you Gokhan now i know were i was going wrong then. I need to set it up first as default through init and then set my values on the app...Thanks..Now how does someone go about changing it through init then:o

Thanks again with your super kernel by the way
[Galaxy S II Original Android Development] droidphile:
The values in VC are step 1 and step 2. To fiddle around with step 3, (which is 300 by default), use init.d scripts.

Read the third post here under Siyah Specific Tweaks for more info.
[Galaxy S II Original Android Development] XDA mark:
A friend of mine liked how my phone looks (ICS theme, Jkay tweaks) and how good it performs (rom kernel). So yesterday I turned his phone into mine in an hour or two. Rooted, backed up his apps, installed my ROM and all kinds of stuff. I also flashed Siyah 2.6.7 for him.

Now I want to continue helping him because he wouldn't be able to solve things by himself yet. I told him to instal CPU Spy and tell me what it says. What bothered me is that he has 11,5 hours of 200MHz and 7 of deep sleep. I always have more deepsleep time then 200MHz and I suspect his device has wakelocks.

Now since I never had any major problems with wakelocks I have no idea how to search for them. Could anybody tell me what the best (or the most easy) way is to find out what is causing wakelocks? Tnx
[Galaxy S II Original Android Development] :
BetterBatteryStats. Look under partial wakelocks first to see what app causes the phone to stay awake. Then follow the necessary steps to either freeze the app or better yet just unistall it:)
[Galaxy S II Original Android Development] CamoGeko:
Search on XDA for betterbatterystats app, that's the easiest way to find what's causing wakelocks.

Edit: Beaten by Suarez7, the queue jumper.

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
[Galaxy S II Original Android Development] Honusnap:
Yes i know that, just saying that overcharging is not good. I would just like to know what is the advantage of using 100mA as Top-Off instead of 200mA.... when using top off charge, the full voltage as already been reached !

Or perhaps we are not talking of the same "top off" ... :)

How it works : (for what i know)

1 - The charger gave a constant CURRENT charge to the battery till it reached its full charge voltage (something like 4.1v/4.2v). Currrent regulation phased end.

2 - After reaching this peak, we are entering voltage regulation phase. The battery is gaved a constant VOLTAGE current till this current go under 3% or 4% under the rated current

3 - IF the voltage reached IS UNDER 4.05v THEN a TOP-OFF charge is triggered, this is not for every charge !

=> Don't know in details how the top-off works for Li-Ion/Polymer, in the case on Ni-Cd, the top-off charge was an alternative charging +200mA, 0mA, 200mA let's say every 30sec (example as i do not know the real interval)

http://www.maxim-ic.com/app-notes/index.mvp/id/3607

It's about USB charging but there's some good infos.

Ps : 100mA is not a voltage ... Ampere is an unit of intensity
[Galaxy S II Original Android Development] coolfire:
I'll be switching over to ondemand once I flash 2.6.9, mate! :)

well I guess that's good enough, for us to identify during charging, because batterymonitorwidget doesn't truly reflect correct values during charging. I read a long time ago that all Sammy devices do not have capability like HTC and Motorola ones, to report true discharging values.

Sent from my SGSII
[Galaxy S II Original Android Development] zoule HCo:
This kernel give me a very good impression at the first boot..

Its light and better than 2.6.8.. I'm using bfg+ondemand governor..

I'm with this kernel since 2.6.7.. Thank you..
[Galaxy S II Original Android Development] gokhanmoral:
all things you say are right.

there are two charging methods: constant current and constant voltage.

the topoff current is only meaningful when you are in constant voltage phase.

and it will try to supply that constant voltage (4.15V in our case) to the battery until the charging current goes below the topoff current.

it will take several minutes more to stop the charging process.

if you keep your phone connected to the charger, you will notice that it activates the charging periodically.

so, once you disconnect your phone, you will have just a little more juice in it.

I did not increase that 4.15 limit, and that is overcharging.

this one is not dangerous and the lowest limit is set to 50mA in the battery charging driver.

you may argue about it decreasing the battery life. it may. but if one care about the battery life 1-) he/she should not charge the phone to 100% and 2-) should reconsider next time about buying a $600 phone and spend $40 in two years instead of three.
[Galaxy S II Original Android Development] rauschkugl:
I don't think he has problems. Are you sure he didn't charge his device after clearing the stats of cpuspy? Because while charging the phone won't go to deepsleep but stick to the lowest frequency when the screen is off.

Sent from my GT-I9100
[Galaxy S II Original Android Development] :
@ Gokhan. sorry for this question. how can i edit in the init scripts to make lulzactive as the default governor to be able to make the app working please? i already save it on voltage control and save my settings and set on boot... that works fine.. but when i go ahead and try the app and put my settings in it fails miserably..:( it is not a big deal but i just like to use the app to tweak the governor about and see what difference it makes...if you are busy no worries it is ok if you can not reply..Thanks again
[Galaxy S II Original Android Development] Cygnuss:
Since i have 2 batteries i use a external samsung charger to have one always ready to go, guess i will not benefit from this new tweak.
[Galaxy S II Original Android Development] gokhanmoral:
use voltage control app. it is the easiest way.

I guess it will set the default governor to lulzactive before lulzactive app kicks in and sets the lulzactive parameters.

if not, just edit the script that voltage control app generated and remove sleep statement from the script.

EDIT: sorry I was in a hurry and did not read the whole post before answering.

edit the script in /system/etc/init.d and remove the sleep part.

if it still doesn't work then you'll have to wait. since xan has put sleep in the script I will remove the sleep before the init.d script execution and you'll be able to set the default governor to lulzactive before lulzactiveapp is launched.
[Galaxy S II Original Android Development] jermitano:
quick question...im currently using siyah 2.6.2 with hawkers script...id like to jump ships and test the last release...can i just wipe cache and wipe dalvik and flash away with the new kernel or do i have to flash first a cleaning script? and if i do, can i please ask for a link of a cleaning script which works well with siyah...thanks guys
[Galaxy S II Original Android Development] ct85msi:
I`ll stick to 2.6.8, I want to maintain my battery as long as I can.

You only gain for the moment more juice in the battery, but you loose that capacity in one or two years...maybe less. I think 200 mAh topoff is the right approach between the maximum charge and the life of the battery that can maintain that charge.

I think this move to set topoff to 100 mAh is wrong and you`ll loose many users migrating to other kernel.

This is just my opinion, I don`t want to offend your great work.