yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] #illidan:
Yes! There is a problem with extweaks & that specific setting. It doesn't stick no matter what you do. GM will probably fix it in the next version but in the mean time put these lines in a script & run it using script manager which you can find on the market. Remember to run the script with root (the skull & cross bones icon).

#!/system/bin/sh

echo "1" > /sys/devices/system/cpu/cpufreq/pegasusq/max_cpu_lock;

Anyway if it's battery life your looking for I think there is sufficient proof out there that 2 cores are better than one but it's your choice.

I also can't seem to get the backlight to stay off. It was working properly before but after a full wipe & all the appropriate settings configured to switch off the backlight, it has no effect & they are always on.

No problems here.

There maybe an app that keeps requesting root access again & again & the superuser app maybe be configured to deny su rights to the app. Whenever an app requests su permissions the screen switches on. Check the superuser logs.
[Galaxy S II Original Android Development] viscocesco:
Some here, battery life was better with 3.3.3d version.

V3.4 eat more battery.
[Galaxy S II Original Android Development] fr3d0x:
Agreed,going back to 3.3.3d
[Galaxy S II Original Android Development] :
3.4 is draining so much to revert to 3.3.3d? Come on, stop trying to beat other's guy battery life, just plug into the charger when you get home, stop trying to get more than 1 day of battery life.

So maybe it's really linux .37, I don't think u6 it's the problem.
[Galaxy S II Original Android Development] stevehkim:
This is with newest siyah. Screen brightness at about 65-70%. I did charge for about 10 mins but that was just to grab something from my sd card to my laptop. Ondemand 200-1300 cpu and thunderbolt scripts.

Thanks GK! Rock solid and awesome battery!

Ported VK w/ bad ass Jkay.

Siyah synthetics and K-tuned for maximum performance.
[Galaxy S II Original Android Development] thomsch:
Maybe it's just me but I experience the best baterry life with 3.4. Keep testing..
[Galaxy S II Original Android Development] nihilista:
Battery life is very good here, too, but i'm on stock xwlp7. Seen no other problems so far...
[Galaxy S II Original Android Development] aceian:
I'm getting great battery life on slim ics with v3.3.3d...

the 3.4 version caused some random freezes with the same exTweaks config..so had to revert..

But the 3.3.3d is great ...stable and good battery life..

5 hours+ of onscreen time always
[Galaxy S II Original Android Development] digkong:
With 3.3.3d and cm9 rc2.. am having amazing battery life 4-41/2 hours of screen on time.. and amazing stability(have some extreme uvs applied to both CPU and gpu) along with great smoothness.:D:eek:

And the best thing my phone doesn't become a hot pan anymore.. before it used even for normal usage.
[Galaxy S II Original Android Development] vitoski:
Yesterday I fully wiped my phone and installed CM9 (nightly 07.17.2012). The backlight control built-in ROM worked perfect (1 second timeout). Then on stock and pure CM9 I installed Siyah Kernel v3.4, restarted the phone and confirmed that even if exTweaks option for led timeout was disabled, built-in CM9 control of backlight stopped working properly.

What's more is that led fadeout in exTweaks did not work as well. No matter if I had it enabled or disabled the led was breathing.

Judging from my test it looks like installing Siyah on CM9 somehow have impact on built-in CM9 led control feature and disabling fadeout (breathing) effect for backlight.
[Galaxy S II Original Android Development] samsungmario:
I flashed the latest cm9 07-19 nightly and siyah 3.4. To make the led work, here is what I did: first went to system settings > advanced > sensors > enable keys backlight . You have to check and then uncheck this to reset cm9. Then after unchecking I exit system settings and went to extweaks. In extweaks > BLN > led_timeout (i select 1.5 secs) and I check led_fadeout. You can also check and uncheck again to make sure it sets. Then save settings and exit extweaks. Now the LED will light up only if you touch the softkeys for 1.5 secs. It worked here and I hope it will work on your phone. Cheers.
[Galaxy S II Original Android Development] vitoski:
Thx for the answer.

Indeed if I do what you said, BLN works partially according to exTweaks settings. I have set up the same timeout as you (to 1,5 sec) and it works. But fadeout (breathing effect) is still there no matter if I enabled, disable, repeat the procedure again. I prefer not to have fadeout effect, but somehow cannot disable it:(

I thought that disabling LED timeout in exTweaks (according to its tip) would bring back the built-in CM9 control and I would be able to set up timeout there (1 second). However as I said disabling exTweaks does not give me that result and in fact it causes the control panel to work improperly - no matter what timeout I set up in CM9 control settings the backlight stay enabled until I turn off the screen, so it looks like the timeout is not applied.

EDIT:

I just checked files in the following path:

/sys/class/misc/notification/

and led_fadout has value 0, which may suggest that it should light up and light down immediately without fadeout effect. Unfortunately somehow it doesn't. The led fadeout is present.

I tried to changing values and saving file, but no joy. What's strange is that led_fadein works (if I set it to 1) and stops (if I set it to 0), but led_fadeout does not seem to work, no matter what value I set up.

EDIT 2:

Just final thought.

I read in the discussion thread that someone had problem with BLN and flashing Ultimate Kernell Cleaning Script helped. So I gave it a try, flashed Kernel Cleaning Script, then Siyah 3.3.3d and re-setup the settings in exTweaks. However it did not work as well.
[Galaxy S II Original Android Development] johnbeetee:
Confirmed! It's small bug in the profiles ( missing one line in which to store the set value)

the actions are performed OK though:

setting single-core only and applying does switch to single mode (it only doesn't reflect in extweaks - it keeps showing dual-core mode)

going back to extweaks and toggling the setting (single->dual and apply) will turn dual-mode back on

just look at the feedback pop-up when applying....
[Galaxy S II Original Android Development] Lownita:
Is it right that gpu stay counts are at 0s for 1 and 2 at default?
[Galaxy S II Original Android Development] cdaarif:
At 1st u clean ur old kernel by kernel cleaning script by cwm, link hear: http://xdaforums.com/showthread.php?t=1363738

then flash 3.4 by cwm/odien, then go to Extweaks, tick✔ (general fair sleep, BNL, I/o schedule-sio, deep sleep) For know battery life download CPU spay from Google play.

100% agreed with u. I charged 100% & I don't use my phone for sleeping 5hrs 41min 40 sec. Now I lost 19% battery ( 1200mhz-3%, 500-1%, 200mhrz-75%, deep ideal-18%) all data from cpu spay. So deep sleep don't work perfectly.

I also use devil kernel 3.x.x for sgs, based on teamhacksung's kernel, with updated Linux base to 3.1.10. Everything work in this kernel. Miss it for sgs2.

Sorry for my bad English
[Galaxy S II Original Android Development] johnbeetee:
have been testing 3.4 for over a good day now....and all seems OK

If any more drain is taking place, the only indication I have is that it would be in the order of magnitude of no more than 5% extra ( but probably less than that ; this period of measuring is too short to make an acuurate statement)

So I think you guys are experiencing something else that is causing such noticable higher drains....

but there's also no real drawback/problem in going back to 3.3.3.d......3.4 and 3.3.3.d are more or less the same, apart from the source/linux updates (mostly minor inpurity fixes/updates)...
[Galaxy S II Original Android Development] lyndonguti:
not agree in paranoidandroid the battery life is insane without any undervolt! look here my post

http://xdaforums.com/showthread.php?p=29050432
[Galaxy S II Original Android Development] lyndonguti:
happends to me too...but when i try to reflash rom and kernel with full wipe ...all the problems solved! no more wake ups expected
[Galaxy S II Original Android Development] robertobsc:
A doubt: by "eats more battery" means eats more battery at screen on or battery drain at screen off?

Here with stock xwlpg there's almost no battery drain.

But with screen on I had also the feeling that battery was going down a little faster. About 5-10 minutes less of screen on / 10% of battery.

I also checked the commits from Linux sources. There were mostly bugs fixed, but the updates are so complex.. Who knows if a correction may really need more processing then more battery.
[Galaxy S II Original Android Development] quijote1:
Thanks a lot for the great suggestions. I checked the superuser log and saw that the main process demanding attention was the Advanced Slim Settings. About the only thing that I have toggled there was the Power Savings option. I switched that off and now we will see. But 3.4 was better even before I made that change. Thanks again.

EDIT: That change made the difference. The phone has had 71% deep sleep since I did it. I'm liking 3.4....

Slim ICS 4.2

Siyah 3.4

XXLPX
[Galaxy S II Original Android Development] d3l1:
Nothing has changed concerning battery life. The kernel is online for a day now and aleady people are crying about worse battery life.

First, after flashing the kernel it is still recommended to reboot the phone at least once if not twice.

Second, it still takes 2-3 complete battery cycles to make any assumptions about battery life.

I for one flashed the kernel shortly before recharging my phone over night and guess what, so far the battery life is better then 3.3.3d. That can/may change over time for the better or the worse, but it's still too early to make any assumptions.

Of course you used your phone constantly and did already go through at least 2 charging cycles, then assumptions can be taken seriously.

Before that, any battery comments are worthless. Same as crash reports without a last_kmsg. :)
[Galaxy S II Original Android Development] johnbeetee:
I really don't think the bugfixes will introduce more processing in that (extreme) extent (some even the opposite, because they eliminate some inefficiecies that could have occured before). And nothing has changed with respect to the screen behaviour ; I think if any, it's more the fuelgauge chip still calibrating itself after a new flash (after a couple of hours it's reasonably stabilized, but fully calibrated only after a few full cycles)....which is why it's important to fully charge after a new kernel and discharge a far as possible (at least 'til 10%) and cycle again.....
[Galaxy S II Original Android Development] bonanza123:
hey,

i now flashed siyah 3.4 and in extweaks i tried the BLN test and it works. But if i have a missed whatsapp message i dont see any BLN (and yes i selected in the settings a color, e.g. white or blue)

how to get BLN for whats app and missed sms and calls?

thx in advance for your help!
[Galaxy S II Original Android Development] Hawkeye1103:
Any idea anybody why do I get random freezes and reboots? Cleared cache and dalvik after install. Same under volt as before -50mv.

Thanks

Ps: reseted the extweaker settings in CWM and set them the same. Maybe it helps:p
[Galaxy S II Original Android Development] aceian:
Happened to me....

It may be simply because cpu can't handle that much of uv...

I'm currently using the same –50uv and gpu uv with 100–1000 mhz...

But have changed cfs to Samsung defaults in extweaks and everything is great...

Not even a hitch till now
[Galaxy S II Original Android Development] noscentsbrad:
First cycle and very impressed best kernel ive used to date (:

Thanks for the brilliant kernel
[Galaxy S II Original Android Development] SPBoss:
Hey gokhan i love your kernel and have been using it from day one but fluxxi had a new sweep 2 wake feature which is awesome. Is it possible if you could port this feature? (Dont wanna leave siyah its so smooth!)
[Galaxy S II Original Android Development] noscentsbrad:
My 1st battery cycle on stock battery (: pretty pleased probably not the best tho
[Galaxy S II Original Android Development] GalaxyGusta:
Is there a way to make the device consume less battery when screen is on? I it eats 1% per 3-5 minutes
[Galaxy S II Original Android Development] aceian:
probably

undervolt and underclock...

use conservative governer
[Galaxy S II Original Android Development] GalaxyGusta:
Thanks I'm going to try and see

Any other ideas for that?
[Galaxy S II Original Android Development] stoyanow:
Hi, I am comming from Galaxy S plus. So to set up this kernel which programs is good to use ? Also one stupid question where are this extra tweaks and how to enable BLN .. :( Sorry again :)
[Galaxy S II Original Android Development] aceian:
extweaks supports this kernel...

you can apply all tweaks including bln stuff from the extweaks app itself

https://play.google.com/store/apps/...SwxLDEsImNvbS5kYXJla3hhbi5leHR3ZWFrcy5hcHAiXQ..
[Galaxy S II Original Android Development] MistahBungle:
OK. Think about this for a moment. By your numbers, that's 300 (5 hrs) to 500 (8+hrs) minutes of screen on time. At the low end, that's not too shabby. At the high end, that's very very good. So, if we take the midpoint, 400 minutes is a bit under 7 hrs of screen on. Again, that's really good.

I don't see what the problem is ?
[Galaxy S II Original Android Development] stoyanow:
Hi aceian,

Thank you for the quick answer. But I have problems .. :( my phonesticks after reboot ! :( The settings that I changed was I/O, min freq, enabled BLN ... :(

EDIT: Is it possible undervoltin -100mV to be the problem of sticking ? I am using stock Russian 4.0.4 firmware . Also which ROM do you recommend ? I know the best ROM is the one which everybody preffer for himself but just an advice :P
[Galaxy S II Original Android Development] Josuhu:
Go to CWM and reset ExTweaks. That should save you :)

UV might have caused your problem.
[Galaxy S II Original Android Development] stoyanow:
Ok. I reinstalled the kernel, reset the extweaks but what was that sticks :( It is better to know what was the problem but not only the solution. Thank you :)

---------- Post added at 06:35 PM ---------- Previous post was at 06:30 PM ----------

Something more. I cannot turn on Bluetooth :(
[Galaxy S II Original Android Development] Kadhim7:
Can anyone explaing to me how to use this kernel to get less battery drain ?

I'm using Whatsapp and toutube only and some small games

I want explaing by pictures please
[Galaxy S II Original Android Development] GalaxyGusta:
In real life I'm actually getting 3 hours of screen on time than the device is under 15% battery
[Galaxy S II Original Android Development] bervin:
There are a number of parameters that must be adhered to. Firstly what is your screen brightness and also what is the standby time with your 3hrs of screen on time? Honestly 3hrs isn't too shabby
[Galaxy S II Original Android Development] yahyoh:
delete fb and battery life will be better its damn app when using it always cpu will run @1.2 wtf and use 3 services in ram :rolleyes:

use frindcaster and will forgot about **** app from ****ty fb developer :o
[Galaxy S II Original Android Development] Josuhu:
Under volting -100mV you said ? That caused your booting problem.
[Galaxy S II Original Android Development] GalaxyGusta:
my screen brightness is all the time on automatic with CM9

and my standby time is beetween 5hours of intence use to 18-19 sometimes 20

it all depends on how constantly im using it becuse when it sleeps its wasting only 2-5% per 7 hours
[Galaxy S II Original Android Development] stoyanow:
I also think this was the problem. And maybe because I use it with stock firmware.:confused:
[Galaxy S II Original Android Development] Many40:
Josuhu is right. Undervolting in Siyah lower than -50mV gives in most cases instability on 500 MHz. For me it's impossible to have stable config with voltage lower than 950mV on 500 MHz. I would recommend you to use more flexible tool (eg. Voltage Control) to check different undervolting on each frequency of your scalling range which would give you a best stable config fitting to your phone. UV option in ExTweaks force us to undervolt the same on all frequencies what is not optimal solution (eg I can undervolt more on 200 MHz or 1000MHz than on 500MHz). Regards
[Galaxy S II Original Android Development] baza14:
Rock stable 900 mV on 500 MHz.

Sent from my GT-I9100 powered by CM9
[Galaxy S II Original Android Development] Many40:
Lucky guy. But seems you are in minority. If think it is very individual issue and dependant on particular phone's hardware.
[Galaxy S II Original Android Development] future1803:
It works on 4.0.4, except for de camera, it take photos and videos but i can't see anything when i open the app, i can see only what I've captured, can you pleas fix it ??? Thanks !!
[Galaxy S II Original Android Development] SPBoss:
Guys i just done my brothers phone on custom rom and the lockscreen is htc sense 4.0 ui with awesome weather animations.

is there any way to flash like a modded lockscreen so i can have that feature?
[Galaxy S II Original Android Development] Tungstwenty:
You can use this temporary fix until GM is able to update the kernel.
[Galaxy S II Original Android Development] noscentsbrad:
Nit sire if you mean fb uses 3 services in ram or to be enable 3 services in ram. What do u mean? :p
[Galaxy S II Original Android Development] yahyoh:
when u use fb u will find one service in ram and 1 or 2 cached service for it + its use cpu like hell + drain a lot of battery

thats my opinion :o
[Galaxy S II Original Android Development] noscentsbrad:
Thanks for fixing my confusion

And I realised it drained battery but its a good app :p
[Galaxy S II Original Android Development] bensonwang:
Fresh new, does this support 4.0.3 ics? With juicydefender cpu speed adjust?
[Galaxy S II Original Android Development] bandroid842:
Hey! Latest version says it was only tested on AOSP, unlike the previous ones. Has anyone tried it on MIUI?
[Galaxy S II Original Android Development] yahyoh:
try friendcaster and u will never look back :D
[Galaxy S II Original Android Development] #illidan:
People talking about battery life & other things which are not even remotely related to development in this thread should know that this isn't the place for it. There is a dedicated discussion thread for it so please do make use it & avoid turning the development thread into a mess. It will help GM to find genuine bugs reports much easily without him having to go through the unnecessary clutter.

My bad! I didn't check the customconfig.xml file to see what was the issue. Checked it now & you're right.

Blutooth doesn't work for now. GM need a source drop from Samsung to get the necessary stuff for it to work.
[Galaxy S II Original Android Development] Kristion:
I've experienced a complete shut down of the phone a day after installing 3.3.3d. I'm on odexed stock LPG with Jkaymod, what could be the cause? When I went to bed it had smth like 28% and when I woke up it was completely shut down, I couldn't start it until I've plugged the charger. The battery wasn't depleted because when I booted up the phone it showed me aprox 40% ( I've left the phone to charge a little bit while it was turned off). I haven't done any UV or changes, it's on the pegasusq governer. On previous versions of Siyah I've experienced random freezes, this one seems stable apart from the nasty thing that happend recently :). I don't understand why I experience issues only on Siyah, if I use CF-Root or CM9 with stock kernel everything is ok. I only want an explanation or what's the possible cause of this issues, I'm not whining.
[Galaxy S II Original Android Development] Josuhu:
Hmmm. My friend had a lot of sudden deads even with a full battery. The reason was a dirty USB port. He could see a big battery drop in his battery options from that time. Otherwise my Siyah 3.3.3d has been flawless and the best kernel ever for me. Have not even wanted to try 3.3.4 yet ;)

EDIT: Complete dead a day after installing! This might also be because the phone acts crazy always after flashing a new kernel, no surprises that it might do something like that shortly after :)

EDIT: And last but not least. Do you use Superuser ? Might wanna change it to the SuperSU. This gave a huge performance and a battery boost to many of us. Dont know why or how, but I had this tip from some thread and it freaking works! Amen. Cowabunga dude.
[Galaxy S II Original Android Development] gokhanmoral:
3.4.1 is up.

merged tungstwenty's changes for bluetooth.

all credits goes to him as I have just compiled and uploaded the kernel this time :)
[Galaxy S II Original Android Development] vitoski:
@gokhanmoral could you please have a look on the led fadeout that doesn't work well (cannot be disabled) on CM9 (dunno if that it's relevant or not).

Wysyłane z mojego GT-I9100 za pomocą Tapatalk 2
[Galaxy S II Original Android Development] timberwolf60:
I don't think superSU so superior. I never had problems on superuser.

Send via my GT I9100 using Tapatalk2, 1st ROM RR 2.6 and 2nd ROM Paranoid V1.6a. Siyah kernel 3.4.1
[Galaxy S II Original Android Development] Krendelrus:
this is so awesome, bluetooth is now working with LPM sammy 4.0.4 rom!) thumbs up for both of you - gokhanmoral and tungstwenty, you're geniuses
[Galaxy S II Original Android Development] WhoIsJohnGalt1979:
would u be kind enough to check if data wipe works in recovery?:fingers-crossed:(tongue in cheek)
[Galaxy S II Original Android Development] Krendelrus:
I'll leave it for you to check, but assuming it's Siyah it's good
[Galaxy S II Original Android Development] timberwolf60:
You tested it, please report up to lpm thread. Thank.

Send via my GT I9100 using Tapatalk2, 1st ROM RR 2.4, and 2nd ROM Paranoid V1.6a. Siyah kernel 3.4.
[Galaxy S II Original Android Development] Tungstwenty:
Turns out that even though hardcore's patches didn't have a direct fix for BT to work on I9100, I looked a bit more and tried the N7000 drivers (with more recent sources from Samsung) on our device and it now works :cool:
[Galaxy S II Original Android Development] Tungstwenty:
For the camera the kernel isn't yet updated (the N7000 drivers are not applicable) but you can find a fix here: http://xdaforums.com/showthread.php?t=1772931
[Galaxy S II Original Android Development] Krendelrus:
Thanks a lot for the fix, Tungstwenty

p.s.it's good that S2 and Note have almost the same hardware :) in your face, Samsung
[Galaxy S II Original Android Development] kairi_zeroblade:
oh dear..your almost there.. :D

yup did saw the fix on your thread..but i'm still patient to wait for things to be prepped thru the kernel.. i am still tweaking and modifying the base XWLPM.. :D
[Galaxy S II Original Android Development] republicano:
+1

i would like to modify cpu thresholds too

Question

does the second core turn on in screen off state?

when frequency does the second core turn on when screen on state?

thanks

sorry i should of posted this in the discussion
[Galaxy S II Original Android Development] Krendelrus:
I don't know if it does, but I'm using 2nd Core app by tegrak to turn off second core manually
[Galaxy S II Original Android Development] Many40:
To modify governor's tunables currently you have a few possibilities, eg init.d script or SetCPU app. To have clearer view on the topic I recommend you do familiarize yourself with very instructive posts of droidphille (first two links in the 3rd post here). It's quite time-consuming but very usefull :) Regards
[Galaxy S II Original Android Development] giajp:
with new update in 3.4.1 we're now safe from the bricks found with the 4.0.4?
[Galaxy S II Original Android Development] kairi_zeroblade:
its the 1st thing GM does..to make sure we don't get FUBAR'd..so YES we are safe from the EMMC Bug with his Kernel..(or should i say always safe..)
[Galaxy S II Original Android Development] Hannibal226:
Anyone else cannot download??

CHEERS
[Galaxy S II Original Android Development] giajp:
+1, so now, we can try the checkrom v7, for example