yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Entropy512:
Actually there's a better fix than increasing AFTR target_residency - check my repo, BE CAREFUL, it doesn't have the level of testing that most of my commits do as I haven't had the time to actually release binaries to the wild. It locks out AFTR when MFC is active.

(GM... I'm fairly certain I did warn you that there appeared to be some issues with that patch...)

It doesn't hit everyone - I had it occur on mildly debloated XWKL1, but had it disappear after doing a TiBu restore. However, disabling AFTR is guaranteed to fix it for those who are affected. In I777-land it seemed to be a small percentage of users (>1000 download of the kernel, only three people reported that issue.)

Only I777 users had the cpuidle patch at that time - Since it was major I wanted to have it "beaten on" more before publicizing it beyond the smaller I777 community, especially when there started to be known issues.

Speaking of not having time - gotta go... GM, I'll try to catch up on your PMs in a day or two, been busy lately. Work is a bit crazy.
[Galaxy S II Original Android Development] omniwolf:
using "init.d" and "on the fly" in a sentence is an oxymoron, init.d scripts are only executed on bootup. so unless you want to reboot your phone every time you want to watch a video and then again when you stop, this makes no sense.

probably your best bet is to get the script manager app and create 2 scripts called:

watchVideo

finishedWatchingVideo

in the watchVideo script, put

echo 2 > /sys/module/cpuidle/parameters/enable_mask

in the finishedWatchingVideo script, put

echo 3 > /sys/module/cpuidle/parameters/enable_mask

then execute them via script manager as required.
[Galaxy S II Original Android Development] msgfromside3:
Hmm you can use terminal and vi to edit and rerun it. You don't have to reboot. Of course you have to be a bit knowledgable and willing to type a lot but nothing to call it oxymoron.
[Galaxy S II Original Android Development] Entropy512:
One thing with scripts, if saved in DOS format they may do weird things. Notepad++ works well for Windows users
[Galaxy S II Original Android Development] pikachu01:
The CRLF is different in unix and DOS format. Save it in unix format and it's fine :)
[Galaxy S II Original Android Development] patwang0311:
Dear gokhanmoral sir,

Not sure if anyone else seeing this issue but BLN seems to be not working for MIUI 2.2.3 using Siyah 2.6.12.

Here is the symptom:

- The BLN app test section LED notification appears to be fine, i.e. that test asking to press power button and the LED lit up fine, reporting all good etc.

- However, when testing with a miss-call, the LED will not work.

- I tried flashing back 2.6.11 and my miss-call test lit up the button LED correctly.

- Flashed 2.6.12 again and BLN failed miss call test, flash 2.6.11, all good again.

Perhaps is something to do with MIUI but I kept the same Pulse notification LED settings all the time - no change. The only change is the kernel. Flash your old kernel and all good, then flash the newer one, call myself, miss-call doesn't lit up the LED, flash old one again and works again.

Just wonder if there is any change in 2.6.12 that may likely causing this behaviour.

Don't worry if it's too hard, 2.6.11 works pretty good for me - just thought I like to use the latest and greatest.

Anyway, thanks again for the great work - this has been my favourite kernel :)
[Galaxy S II Original Android Development] droidphile:
2.6.12 had some CPU idle driver changes which causes one of the deep idle mode: AFTR, to hit soon. This could be the reason. Not sure.
[Galaxy S II Original Android Development] :
2.6.12 no vídeo plata error

hi,

can't play MP4 videos in 2.6.12.

no problems in 2.6.11
[Galaxy S II Original Android Development] pikachu01:
Try reading a few posts before you? Wonder what's preventing people from reading at least two pages back :/
[Galaxy S II Original Android Development] msgfromside3:
They are not here to gain knowledge. Just to ask question and never realize that reading through would show them the way a lot faster. :)
[Galaxy S II Original Android Development] :
i agree your help, i don't have read the thread since a few days

don't burn me for this.

I have not asked for any help, I just report a bug and I'm sure will be fixed in future releases.

Why do you speak of receive / transmit knowledge without looking at my profile and in my opened threads?
[Galaxy S II Original Android Development] gorillaCF:
guys, another quick issue that i faced.

i can connect to my company's wifi, but cant surf. like, no data movement at all. thats on siyah.

so i thought, theres something wrong with the wifi. but when i changed kernel (speedmod), the wifi is working normally.

i'm not sure of what kind of wifi, those technical terms etc, but is this something that is fixed under the wifi changelog for 2.6.12?
[Galaxy S II Original Android Development] omniwolf:
probably a better test is to go back to siyah 2.6.11 and see if that fixes it.
[Galaxy S II Original Android Development] cmd512:
The reports of mp4 playback issues are just strange to me. Just played both mp4's on my external SD... District 9 and Wall-E... with no issues. Could it be a combination of settings causing it?

And yes, I'm still at:

echo "3" > /sys/module/cpuidle/parameters/enable_mask
[Galaxy S II Original Android Development] gorillaCF:
thanks for the quick reply.

i tried 2.6.9, 2.6.11. both doesnt work as well. not sure whats wrong :/

i go back to speedmod, and the wifi works normally again.

edit: anyway not a big issue for me. just thought of highlighting this. maybe the wifi structure for companies are different, just my thought. thanks again omniwolf.
[Galaxy S II Original Android Development] mekhonte:
has anyone noticed slower charging speed in 2.6.12 in contrast to 2.611 or 2.6.9?

in 2.6.12 13% in 30 minutes - screen off all the apps close
[Galaxy S II Original Android Development] omniwolf:
might be worth trying v2.6.6, as in 2.6.6i there were some wifi changes that may have caused your issue.
[Galaxy S II Original Android Development] dosxp:
thanks for your great works.

I find that there are lots of kworker/u:0, kworker/u:1, kworker/u:2 in warelock records when I use Better Battery Stats.

There is no kworker record if I use DarkKnight 2.5.2 .

What can I do ?
[Galaxy S II Original Android Development] dica:
It's the same, 650mA try to control it via voltage control
[Galaxy S II Original Android Development] mekhonte:
I did check every thing is the same. UV + VC everything:confused: there shouldn't be any difference :confused:
[Galaxy S II Original Android Development] rajarshi10:
Best is 2.6.7 in terms of everything till now. Who agrees with me?
[Galaxy S II Original Android Development] XDA mark:
Actually Im very pleased with 2.6.9. Don't want to switch from this one till a very very good one comes out again. So I can't decide between 7 and 9, both fantastic :)
[Galaxy S II Original Android Development] nicolas996:
Hello

I've wifi issue with 2.6.11 and 2.6.12

When i use wifi, it's randomly fastly disconnect/reconnect

I've tried to solved the issue with this thread without success ([Q]Turkbey rom - WiFi problem)

It's seems to be a kernel issue

Anyone with the same?
[Galaxy S II Original Android Development] olifee:
Did you compare the "same" 13 %?

13 % at high percentage (i.e. 80% => 93 %) is supposed to be slower than 13 % at low percentage (i.e. 20 % => 33 %).

It may also be greatly influenced by running background tasks and - at least in the high percentage region - the rollback of the top-off current.

It might also be that the fuel gauge is just a bit off once more ;).
[Galaxy S II Original Android Development] Entropy512:
If this were buried 10 pages back in the thread, this would be a valid excuse. But this issue was discussed in numerous posts on the page before the one you posted on and ON THE SAME DAMN PAGE AS YOUR POST.

Posting about a bug which has been:

Reported AND confirmed/acknowledged by the developer

The kernel developer has posted a temporary workaround for, which is quoted ONE PAGE BACK from your post

Another kernel developer has ALREADY developed a permanent patch for and has pointed gokhanmoral towards ONLY ONE PAGE BACK from your post

is WHINING, pure and simple.

Edit: Oh yeah, GM - I have at least one report that my patch mentioned a page or two back from this guy's post is indeed fixing the issue for those that had it.
[Galaxy S II Original Android Development] baza14:
My wifi stil turns off during deep sleep with 2.6.12.:(
[Galaxy S II Original Android Development] PedroMRP:
Check your wifi sleep policy.
[Galaxy S II Original Android Development] mekhonte:
yep! always keep it between 60% to 90%

It would be great if someone flashes 2.6.9 and compare it with 2.6.12 to how much charges it gets in 30 min
[Galaxy S II Original Android Development] ivangs1:
Hello,

I am using custom ROM on my SGS2 - Cyanogenmod 7.1 (arif-ali daily builds) and recently have installed original 2000mah Samsung kit but it looks like it doesn't identify the correct volume of battery.

I am using CM7.1 kernel i and think that it can't identify 2000mah battery.

Can someone with SiyahKernel 2.6.12 and CM7.1 can confirm that phone correctly recognize the 2000mah battery.
[Galaxy S II Original Android Development] veyka:
I have never had any problems with the official 2000ma battery on cm7 stock or SiyahKernel (back when I was using cm7).

Why do you think its not detecting the capacity, this phone isn't like the hd2 where you need kernel support for extended batterys
[Galaxy S II Original Android Development] baza14:
Yes, It was that, thanks.:)
[Galaxy S II Original Android Development] ivangs1:
Because there was not battery live improvement after installing new 2000mah battery.

Is there a program which can show me the real battery capacity?

P.S. i have wiped battery stats now i will check if this will help.
[Galaxy S II Original Android Development] debay:
Just posted that in the checkrom thread!

Had massive battery drain issues with 2.6.12!

But fortunately it works with 2.6.11! :)

Thanks - great kernel! ;)
[Galaxy S II Original Android Development] legendasboy:
what is the problem with wifi turning off when in sleep? doesnt it saves battery life?
[Galaxy S II Original Android Development] veyka:
You would need some separate hardware to test battery capacity.

And you will see upto 25% improvement, depending on your usage, give it a few days to see the improvement, because again it depends on your usage.
[Galaxy S II Original Android Development] b2rdetor:
any reason to update 2.6.11 to 2.6.12???

all works fine with 2.6.11, but 2.6.12 seems like have many troubles like video problem, wifi...

my wifi isnt lose connection during sleep and phone deep sleep are fine with wifi always enabled with 2.6.11.
[Galaxy S II Original Android Development] pikachu01:
Try it and see :)

You can rollback easily without any harm if you face problems :/
[Galaxy S II Original Android Development] veyka:
RE: wifi issues, pongster noted that some networks where having issues with ECN.

Maybe someone with wifi issues could try:

cat /proc/sys/net/ipv4/tcp_ecn (it seems to be 2 by default?)

Then do:

echo "0" > /proc/sys/net/ipv4/tcp_ecn

This generally happens with older, outdated, or buggy equipment, see here

If it works, go find and thank some of pongsters posts, if it doesn't, just

echo "2" > /proc/sys/net/ipv4/tcp_ecn

to go back to default
[Galaxy S II Original Android Development] veyka:
I had a "screen would not wake up".

Im going to backoff my UV a bit and see if that helps.

I was able to connect to the phone and pull a logcat, but it seems i failed to get kmsg, and for some reason my last_kmsg isn't there? (Yes I rebooted using the power button rather than pulling out the battery).

If it happens again ill try and actually get a kmsg/last_kmsg :/
[Galaxy S II Original Android Development] Lownita:
svnet and svnet_dormancy is my top wakelog and eating my battery... If wifi is turned on, then it is wlan_wake and wlan_rx_wake too. Why is this happening? My carrier supports fast dormancy and it is turned on.
[Galaxy S II Original Android Development] barondebxl:
I agree, 2.6.11 is the best siyah version to date, no need to update it for now . I haven't updated yk 2.6.12 but it seems that people are having issues with it.
[Galaxy S II Original Android Development] a1adin:
I agree, under more or less the same condition,

I find 2.6.7 (and 2.6.6i) is the most battery friendly and has the biggest deep sleep %.
[Galaxy S II Original Android Development] menkromsen:
I'm also using v2.6.7 and have never been happier :-)

Tried almost every release until now, this time I will continue to use 2.6.7 until any major uppgrades.

Batterylife is excellent!!

And the performance and stability also rocks :-)

and I have quite a hefty UV.
[Galaxy S II Original Android Development] NoOneCanHelpMe:
Been using .12 since sunday, no problems at all, wifi/bluetooth work just fine, deep sleep as well. I'm on LA4 with KI3 modem.

The more tests I do the more I realize there some really poorly written apps that make a lot of problems and people start blaming the ROMs and custom kernels! :)
[Galaxy S II Original Android Development] CamoGeko:
So true, it's really sad how many people think it's the kernel's fault for causing bad battery life. When it's actually just a badly coded app that they have downloaded and think it's the best while it's draining their battery without them noticing.

Communicated using an SGS2 droid with XDA premium neurotransmitter while DJ'ing on the Enterprise.
[Galaxy S II Original Android Development] Heroeagle:
despite all of yoU said that the battery life is good ....... I face A huge problem with battery drain in 2.6.12 the battery never stand more than 9 hours In normal Usage small internet using wifi and no more
[Galaxy S II Original Android Development] knights.JayTana:
2.6.12 synergize well with SP-MIUI... Good Batt life, Stable, and Fast...

+1 ... Installing CPUspy or watchdog woudnt hurt them...
[Galaxy S II Original Android Development] Entropy512:
You have an app eating data.

svnet-dormancy = cell data - guaranteed 6 second wakelock per packet regardless of whether the carrier supports FD or not

wlan_rx_wake = incoming wifi traffic

Are you running Skype by any chance?

Wiping battery stats does nothing on ANY android device as far as fuel gauge estimates. Also, no Galaxy S or S II device requires any form of battery calibration.
[Galaxy S II Original Android Development] lsv-1:
@gokhanmoral

Don't get me wrong for what I'm about to say, I'm not going to complain :D, I just wanted to give you some feedback for you to take into account for future releases.

Something that you changed there causes me lag in desktop scrolling (Go Launcher EX).

After a couple of scrolls, there is a weird frame drop and the transition looks slow.

2.6.11 works awesome ;)
[Galaxy S II Original Android Development] BiopsiT:
gokhanmoral

Please make for android 4.0.
[Galaxy S II Original Android Development] droidphile:
Let him finish 'making' for 2.3.4, .5 and .6 !!
[Galaxy S II Original Android Development] Mutalisk:
Come on. Think and read first ;)

When they release sources I'm sure he will.
[Galaxy S II Original Android Development] Mutalisk:
Btw af974 managed to port an ICS-touch-recovery with almost the same layout to GB ;)

Maybe worth a shot :)
[Galaxy S II Original Android Development] Entropy512:
Please learn to search, read, and think before posting.

Have you considered that there might be a reason why there are NO custom kernels for ICS beyond initramfs repacks? Do you really think that every single I9100 and I777 kernel developer is just sitting on their ass ignoring ICS for no reason whatsoever?
[Galaxy S II Original Android Development] poochewer:
Actually I have found 2.4.2 to be even better!
[Galaxy S II Original Android Development] Honusnap:
2.6.12 got strange behavior... got a -30% on my battery yesterday when switching my phone on... ! Switch it off at 54% and wake up at 21%.

Got a SOD the day before yesterday, so switching back to 2.6.7.. best one for me.
[Galaxy S II Original Android Development] The_MutenRoshi:
Im using 2.6.9 and very happy with it! Great battery life, smooth with U. V.!

Sent from my GT-I9100
[Galaxy S II Original Android Development] woodyxxl:
+1 same here...
[Galaxy S II Original Android Development] ercxar:
I just wanted to say in v2.6.12, I will get locked up and reboot when I'm connected to vpn via L2TP in normal states, but in v2.6.11 I hadn't this problem in normal states.

---------- Post added at 02:59 AM ---------- Previous post was at 02:57 AM ----------

+1 for v2.6.9 in terms of battery life!
[Galaxy S II Original Android Development] Vaedryn:
No source no Kernel ,it is so easy.

SGS II Cyanogen Mod Tapatalk
[Galaxy S II Original Android Development] Entropy512:
This has nothing to do with the kernel. Fuel gauge getting confused when rebooting on low battery will happen with any kernel.

This is not strange behavior - this is extremely common and widely documented MAX17042 behavior. It's the small insignificant price we pay for never having to calibrate the fuel gauge - it has ONE corner case where it reports inaccurately and this is it.
[Galaxy S II Original Android Development] gorillaCF:
hi all. just curious on those that mentioned 2.6.9 has good battery life on their devices, are you all UV-ing using geko's config? any SoD encounter so far?
[Galaxy S II Original Android Development] The_MutenRoshi:
Yes, I am!

Sent from my GT-I9100
[Galaxy S II Original Android Development] pikachu01:
You guys should at best follow your own configuration for UVing. A good guide to get the best UV configuration is to follow the undervolting guide in my sig (Android Optimization Tips) - CTRL-F for "undervolt".

This way, you won't have to get an SOD every now and then or worry about hanging when that important call is coming etc.
[Galaxy S II Original Android Development] gorillaCF:
thanks The_MutenRoshi..

@pikachu01, thanks for the great guide, although i'm really not familiar with those sort of configuration stuffs. i'll try several combinations recommended by geko and see how it goes. back to 2.6.9 to see if i will have SoD encounter again.
[Galaxy S II Original Android Development] pikachu01:
It is very easy to configure UVing specific for your phone.

To sum it up, have a video file (RMVB, MKV or some very complexed encoded video), limit frequency to the one you're experimenting (e.g. 200MHz) then start dropping voltage until playing the said video hangs (in software decoding mode). Then increase +25mV to get a stable value.
[Galaxy S II Original Android Development] gorillaCF:
do i have to test for ALL the frequencies in the VC? 100, 200, 500 and on....?

using your example of 200mhz, if the video hangs/lags at 800mV, so the stable value would be 825, or even better at 850?

all these undervolting is referring to the 'Voltages' tab in VC right? not the 'GPU/Charging' tab?
[Galaxy S II Original Android Development] chadouming:
You wanna do this for every freq that you want to undervolt. Also, if you find that a video @ 200mhz is hanging with 800mv, 825 should be stable. But that does not mean that 850 will be better or that 900 will be again better. There is a sweet spot that you want to reach. Samething apply when you overclock. And yes you are right :P
[Galaxy S II Original Android Development] qureyoon:
Limit your Min Max to each frequencies, and do the adjustment.

Min = 200

Max = 200

Min = 500

Max = 500

Min = 800

Max = 800

and so on...

No worries on the low frequencies, it will surely lag. But if it's still running, it's still running :)
[Galaxy S II Original Android Development] pikachu01:
Yup, what qureyoon said is correct. Bear in mind though, disable the remount script (if you're using ThunderBolt!) if you're undervolting. Hanging while having ThunderBolt!'s remount script will increase the likelihood of corruption (though its only corruption in the /data folder). Nothing a "clear data" for the particular app wouldn't solve.
[Galaxy S II Original Android Development] gorillaCF:
thanks for the replies!

edit: @pikachu, i'm not using any scripts.

anyway, now i'm starting to understand the logic of the testing. pls ignore the above 'lost' statement of mine. hahaha!

so its like, min/max i set at 200mhz, then under voltage tab, for the specific frequency level (for this eg, 200mhz), i tweak the mV accordingly based on the video testing method mentioned by pikachu.

then moving on, same steps, same freq for cpu min/max, then tweak the mV voltages accordingly. am i right for this?
[Galaxy S II Original Android Development] lpsi2000:
1. No

2. Yes

LMAO, I could not help myself:D

Pardonez me:p
[Galaxy S II Original Android Development] pikachu01:
Yes, you are correct :)

The remount script caution is just a precaution (just in case) ;)
[Galaxy S II Original Android Development] gorillaCF:
ahh ok. really thankful for the advices u guys provided :)

btw one last thing, hahaha. i cant seem to find any videos of the format u mentioned. MKV...? haha. any samples that you can intro to me for testing :X
[Galaxy S II Original Android Development] kwerdenker:
For undervolting you should change to my newer version of the script. I don't think the old one will work right with newer kernel versions.

Concerning the clocking: since I don't know how that daemon actually works, I can't really say if it doesn't interfere with the settings done with my script. Did you try the scripts without the daemon?
[Galaxy S II Original Android Development] lupu87:
For automatic battery calibration must I connect to a charger when it is discharged, or indifferent? thanks.

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] AndreiLux:
Yes. Use CPU Spy and reset the timers to 0, and immediately turn the screen off. Wait like 5-8 minutes or however long you like to record some statistics, and then check the timers. For me (thanks to android OS bug) it then shows > 1-2 minutes of time at 800MHz. I understand if it wouldn't directly go into deep sleep, but if screen profiles would be working then it would change the governor or actually limit itself to the 500MHz I set up in SetCPU.
[Galaxy S II Original Android Development] gokhanmoral:
to be honest I've never tested if screen-off profiles work for ondemandx and interactivex. but your method is quite appropriate. I will check it.

EDIT: but I have a feeling that this has something to do with "lock the freq. to 800MHz before going into deepsleep" method.
[Galaxy S II Original Android Development] mihapodb:
Ok now I have your newer script, removed OC deamon, but clock is still only 200-1200 MHZ and voltages are default.

And I have updated to RC1 too.
[Galaxy S II Original Android Development] smertj:
Hello. I do not speak English. please help make the script init.d (100-1200MHz) but to attempt to boot through CWM. and here I do not understand http://xdaforums.com/showpost.php?p=17827354&postcount=620

Thank you for your work gokhanmoral

good job, thank you
[Galaxy S II Original Android Development] AndreiLux:
No profile works. I tried pure ondemandx with no manual profiles and it goes up to 800MHz, I tried standard ondemand with manual profiles, still goes up to 800MHz. Use StabilityTest to have load in the background running.
[Galaxy S II Original Android Development] geoalexus:
I flash-ed 1.7.8rc1. No root acces , no su... . How can i make root? I came from a stock ki3.
[Galaxy S II Original Android Development] gokhanmoral:
that is why deep sleep mode is activated by first locking the frequency to 800MHz.

I have modified the sources and made it to lock to 500MHz and I am now testing it.

if it is stable I will release it in rc2.

EDIT: try this on stock kernel: set to 200-500 ondemand and turn the screen off and see if 800mhz is used.
[Galaxy S II Original Android Development] gokhanmoral:
read the changelog. the solution is there...