yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] DobermanS:
about b14 and b15 with MIUI...

with galnet ver - 1.10.25 and b14 on incoming call screen goes off and no response for any button ...

b15 with NTD ver (aka stable multilang) also ...

the 2.0 kernel besides FM radio was the most bugless till now
[Galaxy S II Original Android Development] xuxuzao:
man,

do u use script?

wich one?

how do i make it work?

tks
[Galaxy S II Original Android Development] silver2706:
Off topic (Sorry for that) :

Which one is the best CPU management application..??

Plsss...
[Galaxy S II Original Android Development] AndreiLux:
I'm getting bad results with b15. Will post back in half an hour when I finished the testing and comparing between the kernels.
[Galaxy S II Original Android Development] chadouming:
I hads a bug wwith b15, while using performance governor and doing benchmark, it lower the frequencie to 800 Mhz while 1600 is th max freq. Should the b15-2 correct this or it's something completly different ?
[Galaxy S II Original Android Development] gokhanmoral:
are you using b15 or b15-2?
[Galaxy S II Original Android Development] chadouming:
You probabaly have the same problem than me
[Galaxy S II Original Android Development] gokhanmoral:
I have just tested it and same problem with 15-2.

but since it is reproducible I will fix it in the next release...
[Galaxy S II Original Android Development] chadouming:
TY :D

10 chars
[Galaxy S II Original Android Development] AndreiLux:
b15, I'm going to test b15-2 in 5 minutes and post the results in 10 minutes, with screenshots. Basically b15 sleep frequencies are completely ****ed according to CPUSpy. I'm also testing TWD to see if it's my device or kernel.
[Galaxy S II Original Android Development] aamirleo55:
ya now im sure.... its the kernel's bug .... bcoz i tried restoring from Supercore2.0 kernel... its restores.......
[Galaxy S II Original Android Development] :
So far so good, smartass is responsive enough, no locks like there were on rc2. At the moment I am not even bothered to undervolt, just slide to 100mhz and select smartass.

I am running 2.3.5 and didn't even turn fast dormancy off and cleaned all the Samsung crap :).

Thanks for all your efforts.
[Galaxy S II Original Android Development] Muskito87:
brightness was on 80%... screen on time 45min max... just download from market :)

Will try rc3 now!
[Galaxy S II Original Android Development] gokhanmoral:
I confirm that my kernel is working with 2.3.5.

I will rename rc3 to release today. It is stable enough.
[Galaxy S II Original Android Development] :
Thanks for all the hard work, now take some rest :).
[Galaxy S II Original Android Development] tonysac:
I am trying rc3..

I'm with ondemand oc to 1400 from 200 and also uv..the phone is superfast and smooth..(actually still some lag with smartass) but I don't care..now let's see battery drain..I think I'll stay here!

Many thanks to the dev!

Sent from Galaxy!
[Galaxy S II Original Android Development] carcass666:
this is THE best kernel!
[Galaxy S II Original Android Development] :
Jep, phone is superfast with some lag, maybe placebo but smartass was the best for me in rc1. Also 2.3.5 seems to be really fast (maybe placebo again, but my phone never felt so snappy).
[Galaxy S II Original Android Development] Liet Kynes:
I'm on Touch-X Power and I needed a quick info: I'm using Siyah 1.6 and I was wondering which is recommended, on this version and on 1.7, to manage the clocking stuff: do I have to go with setcpu only and ignore daemon controller? Thanks!

p.s. I saw the first post and you say setcpu supported, so I guess I can just leave daemon controller alone.
[Galaxy S II Original Android Development] jdmcivic:
hey. your script works fine on my sgs2. tested on gscript before actually dumping it into the init.d folder. nice work man!! i can say byebye to setcpu..
[Galaxy S II Original Android Development] Zanr Zij:
This kernel on the way to the best. Go on Gokhan :D

Sent from my GT-I9100
[Galaxy S II Original Android Development] yoplaboum:
The best Kernel I have tested !

Great Job
[Galaxy S II Original Android Development] raziel19:
totally agree :D
[Galaxy S II Original Android Development] eybee1970:
nothing to add from my side - just the simple truth :)
[Galaxy S II Original Android Development] kwerdenker:
Thanks for the feedback! :)

Just out of curiosity: did you try to flash a kernel with a different speedstepping (ninph or RAGEmod for instance) while the script is in your init folder? I'm interest if the "adapting" part really works and UV is still applied and stable with a different kernel.
[Galaxy S II Original Android Development] jdmcivic:
not yet bro. i am now inputting scripts to adjust my up_threshold and sampling rate. everything seems to work fine. i will try once i backup my phone. lol
[Galaxy S II Original Android Development] jdmcivic:
so far am getting the best batt life and screen time on this kernel..

screenshots show no batt % cos its at 2% and its blinking. lol

on others i only manage to get 4hrs+ screen time
[Galaxy S II Original Android Development] Grimmy1st:
Hi, first of all: thanks for your hard work!

problems:

still getting freezes with smartass govs (starting app, sometimes on homescreen doing nothing)

+ ondemand gov is not working for me (1.5 and 1.7 RC!), frequency doesn't switch at all (VS amsartassV2), didn't have this problem with other kernels

used kernels: 1.4, 1.5, 1.7 RC1 (trying RC3 later)

using setcpu, but no OC, no UV, no 100 MHz step

used ROMS: Litening 6.1 and Check's DK Gold Edition 3.5, both with freezing (now changing to 4)
[Galaxy S II Original Android Development] kwerdenker:
That's odd. Could you please run the script from my post and show us the results? I'm interested if there is really nothing manipulating the OC or UV values, since some roms include such things in their init-scripts :)
[Galaxy S II Original Android Development] gokhanmoral:
I agree. I have 10 beta testers and none of them has any problems now.previously half of them said that they were having random lockups. they all have removed all kind of tweaking scripts. I am confident that the kernel with stock clock and stock voltages is at least as stable as the stock kernel even with smartass governor.
[Galaxy S II Original Android Development] bgx:
After raise now seems stable! But top is now not 1400 like before now it's 1600?
[Galaxy S II Original Android Development] Bloodloaf:
Phone restarts automatic 2 times in 10 minutes. Back to b14...
[Galaxy S II Original Android Development] Piretia:
b15 and b15v2 are very slow

b14 for me is the best I had in AnTuTu Benchmark am the result of 7621 No. 5
[Galaxy S II Original Android Development] bgx:
Here's the opposite! B15 for me is faster then b14! Now seems stable...
[Galaxy S II Original Android Development] dtekkt:
Still have reboots on b15, I don't want to remove my UV settings because I love them so much... So back to b14 for now
[Galaxy S II Original Android Development] hrzeyni:
b15 stable @ VR3 - faster compared to b14 - sio/ondemand - no OC/UV
[Galaxy S II Original Android Development] nerotix:
@gohkan Any information about this issue? I'm not trying to push you or anything, but since this thread is getting spammed its easy to not read quite and important bug :)

Thanks
[Galaxy S II Original Android Development] Androith:
b15 data gprs/3g not works

Enviado desde mi GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] kokoskokis544:
b14 is faster for me as well...
[Galaxy S II Original Android Development] xeq544:
Same with cm, that bug is fixed since nightly 90 or so.
[Galaxy S II Original Android Development] Molitro:
It's working fine here.
[Galaxy S II Original Android Development] bgx:
No problem here! It works!
[Galaxy S II Original Android Development] the^one123:
Hi!

On b15 my phone sometimes powered off after deep sleep. now i'm testing b15-2 and till now it works fine with old uv settings.

Theone
[Galaxy S II Original Android Development] bundi22:
any soln to choppy touchwiz?
[Galaxy S II Original Android Development] xeq544:
My epeen is now sooo big :)... No perf problems with b15 :)
[Galaxy S II Original Android Development] AndreiLux:
​

Kernels shown in the screen;

-b14 runs on my usual undervolt 850-850-875-975

-b15 will sleep death itself <925mV for 500MHz, have to raise it to 950mV (that's above stock) to wake up, even then without any undervolting on any of the other stages it has issues waking up and takes sometimes 2-3 seconds.

-b15-2 doesn't have the wakeup or voltage issues, but shows the above cpu states too

- all of the above with 100-200 screen-off (i tested it also without so that it doesn't affect stability, it didn't)

-TWD kernel for comparision.... (100-100 screen-off profile, those 4 seconds are probably from me waking it up and before the screenshot), I can't even see what the freq-lock for suspend is for that one... I need to retest this and bombard it with pings.

I reproduced the results several times by flashing between the kernels.
[Galaxy S II Original Android Development] chrisjcks:
Hi, ive never tried this kernel before, is smartassv2 the smoothest/fastest governor?
[Galaxy S II Original Android Development] maxeli:
Which rom r u using??? Oc/uc values?? Uv??
[Galaxy S II Original Android Development] the^one123:
Hi.

Ok with b15-2 there are shutdowns too. Is there a special Frequenz where we have tput up the voltage level ? i remember till b12 or b13 the 200mhz was the problem. Is it the same in b15 or other Frequenzies are wrong:?

Thx theone
[Galaxy S II Original Android Development] jonny68:
No im sticking with version 1.8b as the Kitchen in CheckRom Revolution wont work with latest CWM
[Galaxy S II Original Android Development] terodeg:
i try 2.0 and 2.1 and i like very much your work but CWM 5 is buggy with external sd cad and i cant flash otner zip package and use revolution rom app and in cwm5 dont work back button, please use cmw4 that havent those bug!!!
[Galaxy S II Original Android Development] Orka82:
Strange. Running Revolution and 2.1b15 and i have no problem installing the apps coming from the kitchen app.
[Galaxy S II Original Android Development] olifee:
Working fine here and KitchenApp also still works for me (never realized it was broken at some time ^^). It also worked with the other betas here...

I confirmed I am using CWM 5 and have an external SD.
[Galaxy S II Original Android Development] incubus_fr:
It also happened to me with b14
[Galaxy S II Original Android Development] DobermanS:
tried to reflush back and forwth miui and b14,b15,b15-2 won't wake up on incoming call ....
[Galaxy S II Original Android Development] drziddo:
Question / BLN

No BLN support on beta 14?

Thanks.
[Galaxy S II Original Android Development] CA3iR0:
On CM nightly #95 with Siyah 2.1b15 (and b14) i'm not getting any sound from the notifications (SMS, e-mail, etc). I still didnt confirm but it's possible that the call ring is also muted.

Weird stuff... Everything was working on CM #94.

---------- Post added at 10:52 PM ---------- Previous post was at 10:51 PM ----------

http://xdaforums.com/showpost.php?p=18724341&postcount=7011
[Galaxy S II Original Android Development] nerotix:
Just tested and indeed, phone doesnt wake up on a call.. very odd =o for the rest it seemed to work fine for me tho :)
[Galaxy S II Original Android Development] Orka82:
My phone wakes up on call.

All stock, using SetCPU to switch to smartassv2.
[Galaxy S II Original Android Development] incubus_fr:
Bug in #95, not Siyah related.
[Galaxy S II Original Android Development] spyrale:
b15 report: had 1 SOD soon after first reboot, google maps force close (also cleaned maps cache). back to b14, everything is fine. ondemandx is smoother for me on b14. I'm on revolution 2.7.1, my UV settings are -75 mah on each frequency, OC 1400 mhz. Cheers!
[Galaxy S II Original Android Development] spradling:
My phone locks up after a couple of minutes with the screen off. Going back to b14

Sent from Tapatalk Pro for Android
[Galaxy S II Original Android Development] CA3iR0:
Yep, i did read it just now from here: http://cm-nightlies.appspot.com/?device=galaxys2

CM #96 is almost out :D
[Galaxy S II Original Android Development] incubus_fr:
CM7 #93, Siyah 2.1b14, vr scheduler.
[Galaxy S II Original Android Development] jonny68:
haven't tried 2.1b15 but tried the previous version and anytime i tried to install anything from kitchen it didn't install properly this i believe was due the the latest CWM, others have had this problem too.

---------- Post added at 11:08 PM ---------- Previous post was at 11:06 PM ----------

cannot understand why it isn't working for me as i said previously some people myself included are having trouble with the latest CWM which appears to be conflicting with the kitchen pro but some are not, all very strange!!!
[Galaxy S II Original Android Development] riccardoPolaris:
With smartbench the result is 4395 at default frequency. Very good :-)

CheckRomRevolution--Kernel Siyah 2.1_b15
[Galaxy S II Original Android Development] nerotix:
How do u change the IO? If I change the IO with Voltage Control and I apply changes and reboot, it goes back to sio .. :s
[Galaxy S II Original Android Development] incubus_fr:
I copied a S_volt_scheduler script, edited it and fire it from GScript.
[Galaxy S II Original Android Development] AndreiLux:
Well **** me in a million ways because I've just entered the twilight zone.

I reproduced that weird frequency bug on the last pages I posted several times by switching kernels, the old kernels not having any issues, both b15 repeatedly showing that behavior, all over a period of 1 hour. I managed to finally stop it by disabling the Wifi! The thing is, I reproduced it again by enabling the Wifi again. I set up my laptop to open a hotspot over the W7 wifi miniport and fired up Wireshark to collect packet data, nothing, complete silence in idle, no other traffic than there should be. Now I reboot a dozen times trying to get proper wakelocks and dmesg logs and switching between the laptop hotspot and my router, and the ****ing bug disappears.

I wanted to pin this down on the N7000 wifi drivers and was ready to switch to Speedmod to see if that kernel also does the same since it also uses them... but now it runs fine again on b15-2. It doesn't make any sense to me.
[Galaxy S II Original Android Development] askabaal:
Hy everybody!!!! I have flashed in my galaxy the new Sinyah 2.1 b14 with the new ROM of MIKIMOD----I need a good SET CPU configuration to undervolt my phone. Usually i have 12 hours of battery....I need moreeeee!!! Pleaseeee! Help me!!! Thanks!!!!!
[Galaxy S II Original Android Development] frogman:
phone locked up after a couple of minutes.I was using viewranger apk when screen locked on.Phone also locked on when rebooting. Back to b14 then ill reflash b15 just to be sure.

Rom:Criskelo v27.No changes to Oc/uc or Uv values.
[Galaxy S II Original Android Development] jayquinten510:
Hey Gokhanmoral,

I like the idea of lowering the deep sleep lock frequency, but why lower it to 500mhz rather than something like 200mhz?
[Galaxy S II Original Android Development] nikzDHD:
Each phone differs, try by undervolting by -25, until you get a stable figure.

Try changing governors as well. Ondemandx, Ondemand and Smartass are all good.
[Galaxy S II Original Android Development] chadouming:
Quick question to Gokhanmoral, is the boot logo import still broken ?
[Galaxy S II Original Android Development] AndreiLux:
Going by the testing I've until now it seems that frequency doesn't matter that much as voltage; when entering sleep in L5 (500MHz) it's completely unstable until I raise the voltages close to the 800MHz voltage figure, with the other method by lowering the 800MHz figure to 500MHz first, it seems to work just as fine as with previously in <b14. If you know to do 1+1=2 this would mean that entering/leaving deep sleep is more voltage bound than frequency bound, and the 800MHz or higher states just happen to have mapped enough voltage for that to happen.

The optimal case would be if one could test this further by having high voltages on the lower states, and see if entering sleep works well in those lower frequencies. *if* that theory works, then it would make sense to implement something to enter sleep at something like 200MHz (or even lower) at high voltages (separate from the standard 200MHz voltage); this wouldn't give us the advantage of having lower voltages anymore, but it would still be an improvement over what we had before as that would theoretically cut the power consumption by 4 with the linear scaling on frequency. The device locks its frequency to that state for about 600-800ms every time it wakes up to do anything at all, and we've seen from testing that that's about half the total time for any wakelock in general. Entropy likes to call this "accelerate to wait", and it wastes a lot of power in idle usage.
[Galaxy S II Original Android Development] olifee:
Although this is now going into a direction which is slightly OT, as many users appear to have these problems:

Maybe you can provide some more information, like:

- Does CWM output anything special after the select-in-kitchen-apply-step?

- Does CWM even show up, or does the phone just reboot / boot to 'normal' recovery?

- Did you try fixing permissions (with CWM / some app)?

- Did you do a full wipe before switching to the ROM?

I did not do a full wipe (and was lucky :P), if you also did not do one, make sure you are really starting the NEW kitchen-app (for me, it only used the new one if the old one was removed before flashing the ROM).

In case CWM displays something too fast to read it, try using a webcam / digicam to make a movie ;-).

If we can not fix this in two posts or so, we should take this problem to the CheckRom Revolution Thread (should be better suited, not a strictly kernel-related problem).

After all, Siyah v2.1b13 is in the Kitchen, so the ROM-developers also have tested it (I guess) in their setups and know about CWM 5...
[Galaxy S II Original Android Development] :
First run at 1600 on the updated KI4 based ROM. Beat my previous best on one of the 2.0 beta's by a few points. Haven't tried any 2.1 betas yet; will wait for final release.
[Galaxy S II Original Android Development] fredli888:
I can't wait for v2.1. Fantastic stuff. Want v2.1 want v2.1. Great work !!!!!!
[Galaxy S II Original Android Development] chadouming:
I have a question. If we can lower the lock frequency to 200Mhz, as exemple, wouldn't that increase the time of the wakelock since this freq is less powerful than 500 ? If so, would it still the increased time agains't the lower consumption of these freq.

Edit : To add to the bug in b15 with frequencie, I thing it might be related with your lock to 500 Mhz. After some investigation, i tought it was the Governor which were mixed. Ondemand had me locked to 1600 Mhz, perfomance was acting strange too ( keep me to 800Mhz or 500 after some time. ) But now i thing it's something else. Locked/unlocked the phone with ondemand and the phone seem already using more freq. However the time passed on other freq that 500 Mhz is near nothing. I used my phone a lot to test it and it seem to stuck at 500 Mhz.I then let my phone on the counter, not used and it entered deepsleep correctly.
[Galaxy S II Original Android Development] m00moo:
Installed b15 on MIUI and used the ondemandx and smartass. Both caused deep sleeps and phone failed to respond to incoming calls :(
[Galaxy S II Original Android Development] AndreiLux:
No, well, theoretically no. We'd have to test it to see if it affects resume times. Actually I just checked again to make sure: my suspend and resume times are still the same; 170ms for suspend and around 500ms for resume +-10ms deviation. If it is how Gokhan says and it suspends at 500MHz now, it has no measurable effect on the times, at least for 500MHz.

The wakelock itself isn't being treated yet during that period, basically the CPU does nothing other than getting out of bed.
[Galaxy S II Original Android Development] chadouming:
great, this could lead us to something BIG:D
[Galaxy S II Original Android Development] Androith:
b15 now ok data/gprs with wipe dalvik cache before to install

good work!
[Galaxy S II Original Android Development] pac213:
BLN says "This liblights is not supported." I'm using B14.

Edit:

NVM. Got it working.
[Galaxy S II Original Android Development] Zanr Zij:
2.1b14

Still got problem with usb storage when connecting with computer! Sometimes I have to flash back to CM7 kernel to got it work!

Good battery life! 7h over night airplane mode drain only 2%, close to SpeedMod drain 1% at same time!

Sent from my GT-I9100
[Galaxy S II Original Android Development] Entropy512:
No - some wakelocks are in the "waiting for something to happen" category.

A lot of the time spent in the resume cycle is not spent with the CPU crunching numbers, but with it waiting for something to happen in a peripheral.

If you look at a dmesg, it looks like the last few printk()s of a resume are spaced out in time - and they're all related to modem control. On my device, resume time is always 650 ms or so, and for the last 200+ (need to look again, might not be that long) at least, it's all modem stuff and sometimes mmc controller wakeup - basically, the CPU is sitting there waiting for the modem to wake up.

According to this - http://permalink.gmane.org/gmane.linux.kernel.cpufreq/7439 - it sounds like it's something in the bootloader itself that forces the CPU to 800 MHz, but can't control the voltage.

Similarly, this for Tegra basically says "stop cpufreq in suspend because we lose voltage control when the I2C bus goes down" - http://lists.infradead.org/pipermail/linux-arm-kernel/2011-January/039617.html

So the two possible approaches are:

1) Force voltage to be sufficient to handle 800 MHz in suspend

2) Find hooks in the suspend/resume process right before the MAX8997's I2C bus drops and right after it comes back. Apparently, the suspend/resume hooks in cpufreq.c are too late/early for that.
[Galaxy S II Original Android Development] pac213:
You cannot say a good battery life with airplane mode on and idle overnight. :cool:
[Galaxy S II Original Android Development] silver2706:
Same here..phone went to deep sleep even after auto lock...this could be because of voltage setting...i m trying to restore the default voltage setting n check...
[Galaxy S II Original Android Development] chonshon:
Dear gokhanmoral,

I have one problem need your help.

I use your kernel with setcpu smartassV2 scaling.

But when I close screen and then unlock the screen again,the scaling is changed to ondemand mode automatically.

Do you know what happened?

Thanks.
[Galaxy S II Original Android Development] Denwa:
Since switching to latest beta I have had ti reset wifi several times, some times even needing to reboot. Just me?

I'm starting to wonder if cwm5 has issues with flashing properly? Could explain some random issues people have had with kernels etc.
[Galaxy S II Original Android Development] Nghtmare:
What voltage are you using for 1.69?? And is it stable??
[Galaxy S II Original Android Development] Vulpix:
Can I assume b15 is a bit problematic right now?
[Galaxy S II Original Android Development] rockmaster:
what could it be?
[Galaxy S II Original Android Development] Moskiitto:
I tried b15-2 and had to go back to b13 because of random reboots and battery drain. B13 rocks ;-)

I have not tried b14. Using with cm7
[Galaxy S II Original Android Development] Try4Ce:
With B14 and B15 I have an issue with MIUI. After connecting the USB cable, it shows the usb debugging as usual. But as soon as I unplug it, the USB Debugging message wont go away. Doesnt seem like a big deal tho, but it sometimes is annoying. Anyone else with this problem?
[Galaxy S II Original Android Development] koolshubh:
Hello all,

I am thinking of flashing CM7...

I am currently on Sensation Rom with Siyak kernal v2.0...

But I hve got one ques. Can i flash directly to CM7 with siyah kernal or Do i have to flash codeworks kernal frist...
[Galaxy S II Original Android Development] netchip:
Gokhanmoral, where is the KangBangAOSP repo located? I have already googled for it but I can find nothing.

Sent from my GT-I9100