yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] gorillaCF:
oh this happens even without wifi? ok thats really strange.

anyway, i tried another method mentioned by another user few posts back, use cleaning script, clear OC/UV settings, wipe cache/dalvik, and reflashed 2.6.11.

seems like its still the same drainage of 2% per hr even until now. i'm really lost to as to why is the drain, cause from BBS cant seem to notice any significant wakelocks, and also within the battery graph also shows no sign of constant wakes.

maybe its just my phone wanting to screw me up haha.

edit: maybe i should give 2.6.9 a try. i jumped to 2.6.11 from 2.6.7 haha.
[Galaxy S II Original Android Development] fransarj:
anyone having problems with thunderbolt 2.4 and siyah 2.6.11?
[Galaxy S II Original Android Development] omniwolf:
OK thanks for checking it out. the kmsg buffer will still be recorded to after the SOD occurs but before the phone is rebooted though, right? there was probably a minute's gap between when i discovered the phone was experiencing an SOD and when i rebooted it
[Galaxy S II Original Android Development] pikachu01:
Remove 02modules/05module/90ram-tweaks/98mounts/99complete. They'll conflict with ThunderBolt! scripts.

What problems are yo having? :)
[Galaxy S II Original Android Development] fransarj:
Nothing really as i haven't flash it yet. I was reading a couple of pages back that people were having problems with screenstate scaling. :)

Now that you're here, just run me through the steps here... just flash your script in CWM, that's it? No need to clear davlik and cache? :)

i have

s70zipalign

s98darkyrommarket

s99complete

in my init.d folder. should i remove s99complete as per your post above?
[Galaxy S II Original Android Development] pikachu01:
Nope. I've asked the people who were having problems with screenstate_scaling to PM me and let me troubleshoot. No PMs at all so far :/

Yup. Just CWM and install. No need to wipe anything.
[Galaxy S II Original Android Development] Entropy512:
I thought you said it was happening for you without wifi?

As I said - When I have the issue, it's almost always when connected to my home wifi. I've seen it maybe once (and I'm not even sure if that was the issue) when not on wifi.

You are correct - this doesn't show in BBS, it doesn't show in battery usage, it doesn't show in CPUSpy deep sleep percentages. As far as I can tell, something (I don't know what) is not being shut off properly when the device goes into deep sleep. This causes drain to go up to 2%/hour or so when in deep sleep - normally in airplane mode (No background syncs to wake the device), deep sleep drain is well below 0.5%/hour.

For me, this seemed to happen when I patched my own kernel from the I777 source base to I9100 update3. If it's specific to Siyah 2.6.11 for you - that gives me a hint where to look for my problems. :)

Edit: Ideally, if you ever have a situation like the following:

Charge phone to 100%

Leave phone overnight

When you wake up, there is normal drain for a few hours, then this issue starts

It would be VERY useful if, when you wake up, you estimate from the battery screen about when during the night it started, and pull a dmesg from the phone.

No - when a device SoDs, it's crashed so badly that even the kernel's reboot-on-panic timer isn't able to reboot the device. It's 100% frozen.
[Galaxy S II Original Android Development] pikachu01:
Oops. Just saw that you edited your post with init.d scripts. Delete them before flashing ThunderBolt!.
[Galaxy S II Original Android Development] gorillaCF:
ah yes, i have the problem without wifi. misunderstood your statement previously. anyway, i tried to hook on wifi and leave it there for about 3 hrs, wow the drain is about 4-5% per hr.

i think i have to agree with you, something is not right when the phone goes to sleep.

i'm on 2.6.9 now, and for the past 3 hrs, drained 1%. seems like the problem lies in 2.6.11. i shall try disabling 3g when i go to sleep at night, to see if theres any improvements.

thanks for your help bro.

i tried charging 100% and leaving it overnight. shows drainage, but at a certain point of %, the battery holds. eg, i have 90% after waking up, and further draining to 75% after 2 hours of normal usage.

from this point, my battery will lose about 1%? or sometimes 2% over a few hours of usage. until a few hours later (i didnt really notice already at this point), starts draining more frequently again.

is this normal? if this is normal, probably the 2% drain overnight is common :/

and whats the dmesg? haha sorry, newbie here.
[Galaxy S II Original Android Development] omniwolf:
oh really? when i have my SODs, i can still press the power + home button (as if i'm taking a screenshot), and the phone will make the screenshot noise. Is this not an SOD?

also if i jam on the volume buttons they'll often make a vol up sound.
[Galaxy S II Original Android Development] fransarj:
too late! ok il just delete the scripts then reflash yours. :)
[Galaxy S II Original Android Development] rauschkugl:
i had this problem all the time. After a full charge i had a drain of 2mA and afteran hour it raised to more than 20mA without receiving a message or something. No wakelocks and phone still shows that it's in deepsleep. Only way to get back to 2mA standby drain was a full charge. But with 2.6.11 this got better for me. Now i'm sometimes able to get back to this small drain without recharging. But not for al long time...

Sent from my GT-I9100
[Galaxy S II Original Android Development] airjoe:
Hi, this is a very great kernel. Appericated your hard work!

Is it possible to support 2-way call recording patch in next version? Thank you!!
[Galaxy S II Original Android Development] :
After putting the kernel through its paces we have the following. 35hrs and 5hrs screen on time. Performance amazing battery excellent what more can i ask for. Might be due to my solid configuration..lol
[Galaxy S II Original Android Development] olifee:
This sounds like it is caused by the drain-estimate of the app you are using.

There is no way to measure the drain in mA directly (at least, nobody found it yet ;) ), we only have a method to measure the pulled charging current when plugged in. So all apps showing you the 'drain' in mA have to estimate it using voltage / 'battery percentage'.

The last change (top-off current reduced to 100 mA) fills up the battery a bit more, so when using the phone, it should stay at 100% / higher voltage some time longer. I guess the app you are using interprets this as 'lower drain'.
[Galaxy S II Original Android Development] werziluk:
By far the best Kernel on Android but recent versions have upset me lol

Been using this since the the first ever version and it is the best overall kernel by far.

With the latest version though I am having an issue with brightness, funnily enough I am now getting even more battery life but at the expense of a very very dark screen and also when taking camera images even if its light and I for testing purposes put the flash on too the picture comes out dark.

Now obviously with auto brightness turned off and brightness set up high I do not get any issues but I did not have this problem on all other previous versions?
[Galaxy S II Original Android Development] rauschkugl:
No, this also happened when the topoff current wasn't set to 100. It was even worse in earlier versions of siyah. I know that there's no app to measuere the current directly on our phone because current widget doesn't work but you also can also see it in the percentage now when i'm sometimes able to get it when not fully charged. it falls much slower when it showed 2mA then when it showed 20 or up to 40. Both times without turning the display on inbetween or receiving a message or email or something. So i don't think that this is just wrong reading of the app (battery monitor widget) or has something to do with the charging level of the battery. Maybe it has some influence but i think that there is something else which really drains the battery. Also has no wakelocks that were weird.

Sent from my GT-I9100
[Galaxy S II Original Android Development] :
i never tried this but have you tried using the jkay mods to adjust the brightness profiles?
[Galaxy S II Original Android Development] werziluk:
Hey Suarez, Yeah I have and even the brightest profile is much duller than previous versions. Im re installing previous versions to work out exactly when it happened.

I know The version with Sensation Rom 2.0 works much better (2.5.2+ I think).
[Galaxy S II Original Android Development] :
alright mate. or just set the brightness yourself an untick in settings the auto adjuster in display settings
[Galaxy S II Original Android Development] kilian7th:
Thanks for your answer, have tried my friend google but don't find the source or the procedure to install redpill Recovery with an older version of Siyah (2.6.9) and if it's compatible with miui rom, could you post me the link ?

I found a hyperdroid kernel with redpill recovery but not only the redpill recovery ...

Thanks and best regards ...
[Galaxy S II Original Android Development] gokhanmoral:
try beta5.

it has some fixes for those unexpected reboots.
[Galaxy S II Original Android Development] poch_1421:
i found a bug from v1.7.7 :)

my pc and fone couldn't detect my memory card.

i flashed back to 1.7.4, my mem card was detected again.

sorry if someone already posted this
[Galaxy S II Original Android Development] ebliss:
Hi,

the script in init.d to set the scaling_max_freq doesn't work. In the same script, the scaling_min_freq and scaling_governor are set and both values are updated. Not sure why.
[Galaxy S II Original Android Development] fish80:
Hi gokhan,

I tried for a while 1.7.8beta4 with LeoMar 2.7.1 and think it's the best couple ever... Rock solid for me, solid as Samsung should sell SGS2.

This morning switched to 1.7.8beta5 and my phone didn't wake up from deep sleep, locked :-(

Switched back to 1.7.8beta4.

My 2 cents...
[Galaxy S II Original Android Development] gokhanmoral:
I don't have any problem with setting scaling_max_freq with beta5.

I am using stock rom now to test.

I even moved init scripts to the end to make sure that they run after all other scripts are done.

maybe you have something else which sets it to other value...
[Galaxy S II Original Android Development] gokhanmoral:
that may be a coincidence because there is nothing to make new beta less stable.

if you are using UV try to increase voltages.
[Galaxy S II Original Android Development] gokhanmoral:
I am attaching the scripts that I use.

it is CWM flashable. I am attaching it as an example because it can make your phone unstable as it has undervolting script with values for my device.

scaling max frequency works well. I've just tested it with leomar rom as well.
[Galaxy S II Original Android Development] ebliss:
I had another device freeze when I scroll up and down on titanium backup.
[Galaxy S II Original Android Development] Skyline92:
Hello Guys :)

How can I change the I/O scheduler?! :)

Thanx 4 helping me :D
[Galaxy S II Original Android Development] darkflyer1983:
back again to GPU OC

Hello there,

If I understand well, there could be only two states for GPU (default are "100 and 267MHZ"). any way to change it so that we could have three states:

*100MHZ for idle phone

*267MHZ for UI, browser and applications with moderate GPU needs

*400MHZ (OC) for applications with heavy GPU needs

I guess we should have in this case a governor or at least a daemon to control GPU clock.

thank you in advance for your replies.
[Galaxy S II Original Android Development] chadouming:
We can't change that.
[Galaxy S II Original Android Development] gokhanmoral:
since there are only two states, the logic is very simple.

if there is high GPU demand, use high freq.

also there are some codes in the driver such as "if the user is playing 1080p content, lock to the higher frequency".

I did not change anything in that logic.

if you want to lock to higher freq always, you can set both of them the 267 or higher.

of you can lower it if you dont need that much gpu power to save battery.
[Galaxy S II Original Android Development] gokhanmoral:
I could reproduce this...

the script works but max freq is set to 1200MHz again.

I still don't know the reason but I'll fix it :)
[Galaxy S II Original Android Development] Dark_Lord0122:
I got the android OS bug mine is 80%

SmartassV2 100-1400 leomar 2.7.1 KI3 ( beta4 )
[Galaxy S II Original Android Development] Dark_Lord0122:
SetCPU or no-frills

it has been answered lots of times. read the thread.
[Galaxy S II Original Android Development] gtizon:
The old version of SU solved my problems with this whole setcpu and root permisions issue. I think its 2363. Its the simplest method. Flash rom flash, flash SU, then flash the kernel.

Sent From

GALAXY S2

VR 3.0 on Siyah Kernel V1.7.7
[Galaxy S II Original Android Development] jdmcivic:
same here. max freq seems to be locked at 1200mhz. other scripts work fine.

btw am getting great battery use and deep sleep drain.
[Galaxy S II Original Android Development] kwerdenker:
Are you all using my script? Than it's really odd because I'm running it with beta5 just this moment and scaling_max_frequency is set correctly. Did you by any chance change anything in the script? Especially the chmod line after the scaling_max_frequency echo?
[Galaxy S II Original Android Development] gokhanmoral:
no, I haven't changed it.

but even if I set the permissions to read-only somehow the freq changes back to 1200.

I launch setcpu as soon as the system starts and I see that the freq is 800mhz

when the media scanner starts the freq is set to 1200mhz.

it is really weird because I have nothing else running as startup script.

and I do not receive any superuser notifications.
[Galaxy S II Original Android Development] Entropy512:
That's not consistent with any SoD I've encountered. For example, when this happens are you able to ADB in?

Where are you getting these drain estimates from? Did you build a dummy battery with a current sensor?

Any app that claims to be showing you drain numbers is pulling that information out of its ass... There is no known way for any app to properly measure drain current on these devices, only charging current.

Without a current sensor for the battery the best you can do is percentage per hour lost, and even that isn't too accurate, it's only good for comparing unusually high drains (2%/hour without any wakelocks or wakeups) to normal ones (<1%/hour, closer to 0.5%/hour).

It seems like quite a few people are having the "high deep sleep current" issue. This may be common to all I9100 update3 kernels. In my case, it seems to only happen (with 1-2 rare exceptions) when connected to my home wifi. Turning off wifi will stop the drain for me.
[Galaxy S II Original Android Development] kjshah:
hello guys..

i am having a problem in customizing the charge_current file..

i open it through root explorer and change the AC to 750>save and exit.. when i open the file again to check it has reverted back to 650..

whats the problem..? im running the latest version of siyah
[Galaxy S II Original Android Development] stevehkim:
no point in changing it. our phones only see 2 currents. 650 and 450 for usb. 650 being wall charge.
[Galaxy S II Original Android Development] tolis626:
Guys,first stupid question from me after a while(Not that I don't ask stupid questions,but I don't usually ask questions-Yeah,I feel proud to be part of the endangered species called those-that-search-in-XDA).

By modifying min_bl in brightness_curve,do we modify the lowest backlight possible,or just how low automatic brightness goes?Because I was hoping for the first,but am observing it must be the second...

Thanks in advance! :)

PS:I think I'll be switching to ICS for a while.Gingerbread with Siyah(For me any Siyah after a beta version of 2.2) is too f*cking stable to be fun.And I'm still overclocking. :D
[Galaxy S II Original Android Development] wurzelsepp3:
I was thinking the same. I have Siyah 2.6.11 together with Hyperdroid running for over a week now and haven't had a single reboot or lag, I haven't even had a force close in spite of heavy undervolting.

Battery life is also better then ever. :D

---> It is getting boring, time to test something less stable
[Galaxy S II Original Android Development] incubus_fr:
Switch to Cyanogen and play with Monkey ;)
[Galaxy S II Original Android Development] Entropy512:
Gokhan really needs to completely remove that interface since it does nothing... (And never can - charging turns out to be handled by a different chip with three fixed current limits - 90, 400, and 650 mA.)
[Galaxy S II Original Android Development] kjshah:
Ok thanks for explaining!!

KJS
[Galaxy S II Original Android Development] XDA mark:
Sorry if this is to offtopic:

Since a few hours whatsapp has been acting very strange for me. This morning I reflashed Siyah .11 hoping to do something good (battery seemed to drain a little to fast, performance was not perfect, etc). But like I said, since a few hours I am unable to send a picture using whatsapp. The screen just turns black and after a few seconds I return to the homescreen (it crashes). Sometimes it even crashed when I just tried to open the app.

Anybody else having these kind of problems with the app? I am pretty sure it's something kernel related since I see no sign of other people having the same issues today. The phone in general feels slower then it should be. Other apps seem to work though (email, phone, sms, browser, twitter, etc)

What can I do to "refresh/clean up" my phone? I tried to wipe cache/dalvik and reflash, but that hasn't helped. I read something about a Samsung Kernel Cleaner or something, maybe do that?

Sorry if this is a 'lil bit to much offtopic.

Further more Im using 200-1200MHz, BFQ +Ondemand, very little UV (has never been a problem). I installed an update for Voodoo Louder also this morning, but can't see how that would cause these things.
[Galaxy S II Original Android Development] tolis626:
I know I'm not helping and I'm sorry for going off-topic,but does the updated Louder app work for you?It crashes after it requests su permissions here...
[Galaxy S II Original Android Development] XDA mark:
It works for me. No problems at all with Voodoo Louder itself after updating to the newest version today.

Edit: ok, I deleted Whatsapp and reinstalled. At least it's working again, even though I would have prefered not to reinstal the app.
[Galaxy S II Original Android Development] gokhanmoral:
I am still very busy and I could not read the thread for a day.

today, I did not use wifi (completely off) and had great battery life. entropy512 is right, we have some problem with either wifi driver or something related.

and entropy512: I did not remove the charge current interface completely not to break the compatibility with voltage control app. I will remove it as soon as I get the xml&scripts based dynamic-ui config part working. I will ask xan to remove the charge current control part. I am thinking about a button which will "increase usb charge current until you unplug" with a warning about not to use it on computers but to use it with car chargers which are detected as usb port.
[Galaxy S II Original Android Development] AndreiLux:
Btw, just a heads-up, running 2.6.12 for two days now and that Wifi wakelock freeze didn't occur anymore, at least not yet.
[Galaxy S II Original Android Development] gokhanmoral:
well.. that is both good and bad.. since I could not checkin those changes to any of my repository (neither to hg or svn) I don't know which one you are using now and the latest .12 on my device has those wakelock freezes :)

I think reverting some changes back to i777 sources (my old v1.8) helped which means Entropy512 is right again :)
[Galaxy S II Original Android Development] fransarj:
question,

is it safe for me to OC the GPU from 267 to 400 (via voltage control)? has anyone done it?
[Galaxy S II Original Android Development] droidphile:
You nasty 'compiler'!! (or tester?) :D
[Galaxy S II Original Android Development] AndreiLux:
update3 sources plus whitelist filter.
[Galaxy S II Original Android Development] chadouming:
The answer is in this thread, have fun.
[Galaxy S II Original Android Development] dannyc93:
Hi how do i enter these codes into the phone...bit of a noob here :P

BTW you moved to ICS beta yet?
[Galaxy S II Original Android Development] Simba501:
http://xdaforums.com/showpost.php?p=21860684&postcount=17964
[Galaxy S II Original Android Development] dannyc93:
Thaks allot mate, i get the feeling you get asked that allot haha :P

Sorry a bit unsure what i rename the file to

"rename it (remove file extension from the end), and set the permissions to 755"

Thanks again!
[Galaxy S II Original Android Development] Simba501:
Doesn't matter; as long as there is no extension on the end.
[Galaxy S II Original Android Development] Dennys_Santos:
Hey, Gokhanmoral.

Do not leave the "troll" knzo undermine the development of optimal kernel.

Please keep up the good work, go back to provide new updates.

Thanks dude.
[Galaxy S II Original Android Development] kasica-76:
Do siyah 2.6.11 is better than 2.6.7 ?
[Galaxy S II Original Android Development] poochewer:
Originally Posted by tolis626

PS:I think I'll be switching to ICS for a while.Gingerbread with Siyah(For me any Siyah after a beta version of 2.2) is too f*cking stable to be fun.And I'm still overclocking.

Ah fellas, have you tried hitting your phone with a sledge hammer?

It's never boring after that!!!!! :o:p
[Galaxy S II Original Android Development] rauschkugl:
Yeah i know the apps are crap but as i said the high and low stanby currents go hand in hand with 1% in 2 hours and 2% per hour. Independent from wifi, gps or blutooth. Also no wakelocks other than normal. It's not kernel dependent for me but got a little bit better with the newest siyah. Didn't really test old kernels that base on update 2 though.

Sent from my GT-I9100
[Galaxy S II Original Android Development] Entropy512:
One thing to note: The specific problem I have been having (which it seems a few such as rauschkugl) have also reported) is:

Drain at 2% or so an hour, despite:

Deep sleep at a very high percentage (97%+)

No wakelocks held

No significant time at the suspend lock frequency

For me, this started happening when I patched the s5pv310-specific parts of arch/arm and components dependent on it up to update3. Wifi got patched about ten days before that without causing problems for me - however, most of those ten days were spent traveling and visiting family so there's a possibility that the different environment and usage patterns hid the problem. I haven't had a chance to revert to a build from in between (I9100 update3 wifi driver, I777 for "exynos core components") to see if they are affected.

What's frustrating is that it's intermittent - for example, it didn't happen at all last night. Other times it happens immediately on boot.

I think a few other people were having problems with wlan_rx wakelocks and frequent wakeups, which is a completely different one.

On another strange note (I need to figure out if it was update3 or the cpuidle backport that did this, I haven't run wakelock tests in a while...), I just got nailed by the StartingAlertService wakelock and only lost around 1.25-1.5%/hour. Normally that's 4-4.5%/hour.

One other interesting thing: In the I9100 update3 sources, there is an early suspend/late resume (screen off/on) handler in the bcm4330 driver, however it never seems to get called. Weird.

Going to be plenty of things to poke at this weekend...
[Galaxy S II Original Android Development] eladnava:
Hi,

I have been using Siyah Kernel and upgrade almost every new version. In previous versions Siyah Kernel would make my phone randomly shut down in my pocket, when I would take it out during the day I would notice that it just went off suddenly.

Now with v2.6.11 it happened already 3 times in the same day.

Is this kernel unstable? I did not overclock, underclock, or do anything unstable to the phone. My phone actually started once in Safe Mode when I started it. I do not have SetCPU or anything like that. I am using Litening ROM (v2.3.4 Android).

Thanks!