yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] zetret:
Is this kernel Isorec compatible?

I flashed "Siyah-s2-v6.0b5 Kernel +Recovery" on the i9100...

If you know if this is isorec TWRP compatible, please let me know.

P.S: If you know how to install the TWRP image from any other means other than ADB, please let me know too.

Thanks.
[Galaxy S II Original Android Development] ssanjy:
This is a very old kernel whereas IsoRec is a new concept...I guess you didn't read the original thread of IsoRec... Anyways if you are on stock then unofficial dorimanx build by chhapil and GreekDragon recent build is compatible for IsoRec.... Also you can easily flash the image file once you are on TWRP....
[Galaxy S II Original Android Development] zetret:
Hi

Thanks for your reply. However, for a new person like me, it is very difficult to understand the isoRec first thread... This is what I learned from your message;

a) Go install unofficial dorimanx build by chhapil and GreekDragon

- Now, would this automatically install TWRP? OR would I have to go to CWM and flash the isorec-TWRP again?

From your last line, "Also you can easily flash the image file once you are on TWRP" - I am a bit confused. Are you saying that I must install IsoRec-TWRP and then update TWRP again by flashing the new image from there?

Please clarify. Thanks.

(What is not clear is HOW is the Recovery partition related to the Android system Kernel?)
[Galaxy S II Original Android Development] C.Z.O:
Hi everyone

I am flashed siyah kernel finel versions in my stock jb rom. Everything working well but I connect my charger my phone wont charging any one know to fix this issue

My current kernel is dorimanx kernel by GreekDragon working without problems
[Galaxy S II Original Android Development] :
I don't remember any problems like that on siyah, but that was a few years ago....

Why would you want siyah? It is really old and out-dated. You would be better off with dorimanx, or even apolo.
[Galaxy S II Original Android Development] C.Z.O:
Thanks for your reply and can I use apolo kernel with stock JB rom
[Galaxy S II Original Android Development] :
Yes, just get the right version (branch 4.x). Read up in pedestre's thread here

chhapil also developed apolo kernel a little bit. It's here
[Galaxy S II Original Android Development] C.Z.O:
Hi can you explain about this versions
[Galaxy S II Original Android Development] dinos3:
Does anyone have a mirror for Siyah-s2-v6.0b5-CWM.zip?

I have problems with dev-host...
[Galaxy S II Original Android Development] RudeboyXL:
I wish Siyah was still in development. It was the best most stable kernel I ever experienced, never found anything close to it these days with modern ROMS. used to have button light brightness match display brightness, button lights for notifications, dual booting ROMs, kernel level gesture support etc etc and the fine tuning of the gov/IO settings gokhanmaral tweaked, made the kernel lighting fast and stable beyond compare. Everything was just working as it should. Meanwhile most kernels now and then cant even keep my button lights on permanently when set to.
[Galaxy S II Original Android Development] jotapdiez:
Thanks for your work.

I have CM14.1. This kernel will works with that version?

If not, based on your experience and personal recommendation and just as a ROM recommendation, should I move to cm10?
[Galaxy S II Original Android Development] mraxido:
Bug report

With beta 7 the twitter app stoped sending me push notificationes and the facebook app dont let me select my notificationes. Any ideas?
[Galaxy S II Original Android Development] gokhanmoral:
I will try to fix the scaling problem first.

needless to say, the plan is always to fix everything... but it may not be practical.

I don't think about releasing rc1 with this SOD problem.

fixing MTP is not a challenge for now.. there is already a workaround for it which is to release two different kernels.

don't expect any updates while we have this problem...
[Galaxy S II Original Android Development] gokhanmoral:
yes. my idea is that it has nothing to do with the kernel. :)
[Galaxy S II Original Android Development] bala_gamer:
Do you think its kernel related? Wow!!!
[Galaxy S II Original Android Development] omgitsniklas:
btw, 4.0.4 sources are out!

https://groups.google.com/forum/m/?f...ng/YoBlTfntDvo
[Galaxy S II Original Android Development] stanmarx:
No I did not.

Thanks for the answer :)
[Galaxy S II Original Android Development] :
Dumb question alert!!

Fire retardant suit mode ON

To enable bln on cm9 with beta 7 do I need bln pro app, or is there something to enable it already in cm itself? Some posts are giving me troubles understanding this...

Thank you :)

Sent from my SGS2 - Powered by CM9
[Galaxy S II Original Android Development] omgitsniklas:
bln isn supported in siyah beta 7 i think! when u read changelog of siyah beta 3 rc1 u see that he will enable it in this new version!
[Galaxy S II Original Android Development] suchevent:
try this and see if it works. worked for me (i'm on hydrog3n-ics, though).
[Galaxy S II Original Android Development] Entropy512:
Useful for the CM team, not so much for kernel people.

No clue why it's better for you - I can tell you without a doubt that on my device, proper operation of cpuidle has a significant effect on battery life.

For example, when at home on wifi, if I set up a permanent wakelock inhibiting deep sleep:

With the Tab 7 Plus cpuidle code, drain was slightly less than 1.5%/hour (measured over 10 hours)

With the original cpuidle code, drain was 2%/hour when wakelocked

I'll try with CPU1 locked on in a day or two

The stock hotplugging heuristics kind of suck (at least they did on Gingerbread, allowing plug-in at 500 MHz for example), so if you didn't try to fix the hotplugging logic, forcing both CPUs on might have helped things.
[Galaxy S II Original Android Development] TecQuality:
Just a Q for the CM9 users: what are your feelings with this kernel?
[Galaxy S II Original Android Development] Vaedryn:
Very good, as it is known by Gokhan
[Galaxy S II Original Android Development] Ogy77:
Nice,very fast,very stable,like always from Gokhan:D
[Galaxy S II Original Android Development] :
Never used latest cm kernel so no way to compare for me, but as of now I'd say great, taken that cm is still experimental and syiah still beta ;) once both will evolve to gb level will surely be a big "wow" :) I still find it too battery thirsty though, even if I set up carefully voltage control and extweaks...

Btw: who wins if there are conflicting settings between cm, VC and extweaks? I still have to find a precise answer...

Sent from my SGS2 - Powered by CM9
[Galaxy S II Original Android Development] TecQuality:
Sounds good. Some days ago i noticed that Gokhan is using a nightly, right now he switched or not?
[Galaxy S II Original Android Development] :
Thanks a lot guys, my question was slightly different: do I need to buy bln pro or is the same function already present in cm9?

:)

Sent from my SGS2 - Powered by CM9
[Galaxy S II Original Android Development] Qwerty__-:
hi! :)

is there any thread where i can found people settings of voltage control app for profile and underclock/overclock ?

thx !
[Galaxy S II Original Android Development] StaxTheDeath:
Voodoo Louder

Is anyone here using the Voodoo Louder App?!

Does the Siyah-ISC-Kernel support it at the moment?!
[Galaxy S II Original Android Development] rauschkugl:
the extweaks settings are applied very early on boot and get overwritten by the voltage control settings. they are set much later. don't know about the implemented cm stuff.
[Galaxy S II Original Android Development] SimboXXX:
You need the bln app, but can be the free version.
[Galaxy S II Original Android Development] sreg:
yes, all beta version...
[Galaxy S II Original Android Development] oblivianz:
I am, it works.
[Galaxy S II Original Android Development] jontoo:
Yes I'm using and it works OK
[Galaxy S II Original Android Development] blair287:
is the menu button and back button lights fixed in rc0?
[Galaxy S II Original Android Development] aceofclubs:
been trying out my GB settings based on geks magicconfig and not having any usage issues yet.

LP3 and siyah beta7.

Here is his thread for gingerbread.

http://xdaforums.com/showthread.php?t=1466017
[Galaxy S II Original Android Development] pulser_g2:
I think this is old news, but my tests show underclocking while CPU is high speed will cause a freeze...

It could be related to hotplug, as I have disabled second core when this tries to apply...

But basically, the currently active clock speed seems to matter... If it's high, freeze... If it's low, it seems fine...
[Galaxy S II Original Android Development] franciscofranco:
Can you keep me posted on your results? Im kind of curious. =)

Im free for theorycrafting and technical discusion anytime, it would be fun to help the sgs2 kernel folks since its such a highly famous device.
[Galaxy S II Original Android Development] franciscofranco:
Welcome to the highly unstable world of hotplugging. Dual core mode only and that will be fixed.
[Galaxy S II Original Android Development] pulser_g2:
Yup makes sense...

I will just manually apply the overclock since I can see current speed when enabling..
[Galaxy S II Original Android Development] Entropy512:
That's what we've been discussing for the past few pages. :)

Sure, will do. :)

I wouldn't be so sure. I haven't yet tested complete removal of the hotplugging code in defconfig (I'm testing some CM9 patches for gerrit review at the moment), but if I use /sys/module/stand_hotplug/parameters/lock to lock the CPU in or out, the crash still happens.

I'll probably hop back over to Touchwiz this weekend and really take a closer look. The next three evenings are going to be busy. :)

Interesting thing to note: In addition to the existing hotplugging code, there are 2-3 alternate hotplugging algorithms that can be chosen in defconfig. I haven't messed with them yet as there are bigger fish to fry! :)

<Ninpo> ok
<Ninpo> sounds like
<Ninpo> it's ignoring the request to drop from 1200
<Ninpo> BUT
<Ninpo> buses change
<Ninpo> which is fine
<Ninpo> most freqs iirc are the same between 1200 and 1000
<Ninpo> and power
<Entropy512> https://github.com/Entropy512/kernel_galaxys2_ics/tree/entropy_kernel_main
<Ninpo> 800 is different though
<Ninpo> **** changes
<Ninpo> so the non cpu freqs are changing and aaaaaaaaaaa crash
<Ninpo> find out why cpu speed isn't changing, that fixes the problem
<Entropy512> I haven't tried seeing what happens if I try to do something like setting a limit of 1000 and dropping down
<Entropy512> or 800 and dropping
<Entropy512> hmm one sec
<Entropy512> I think pulser said dropping down to 1200 on an overclock kernel did it too
<Entropy512> hmm good observation there
<Entropy512> If I lock to 800
<Entropy512> load up
<Entropy512> and drop to 200
<Entropy512> no prob
<Entropy512> 1000->500 dies

Edit: Did a "drain when wakelocked" test - 6% in 1h52m, so a bit over 3%/hour. Will try with hotplugging in a normal state in a bit.
[Galaxy S II Original Android Development] hirak99:
Just installed Siyah kernel beta 7 - using this for the first time ever - I think it rocks :)
[Galaxy S II Original Android Development] myfluxi:
Frequency does change and does not hang, setcpu reports wrong, sysfs reads correct.

It's the step from 1000 down, I can be sure because I have 100 MHz steps in my kernel.
[Galaxy S II Original Android Development] zekurosu:
try here

http://xdaforums.com/showthread.php?t=1557844
[Galaxy S II Original Android Development] hirak99:
The charge current setting says it's risky for USB Ports to increase it to 650mA. What is the kind of risk? Will it be on the laptop, or does the phone also run any risk?

---------- Post added at 08:53 AM ---------- Previous post was at 08:48 AM ----------

Does the Siyah kernel have lower battery usage at default settings?
[Galaxy S II Original Android Development] loopism:
Host (ie: PC) USB ports are only rated to supply 500mA
[Galaxy S II Original Android Development] bajee11:
HyDrOG3N-ICS + Siyah v3.0 Beta 7

Best battery life so far.
[Galaxy S II Original Android Development] franciscofranco:
But what is that "lock" you're talking about? A mutex_lock? Offlining cpu1? Why would one want to "lock" the cpu during runtime?

This isn't making much sense to me and the more I think about this the more I want to buy this device to research this problem.

Sorry for hijacking the thread, it seemed like a nice place to discuss this crash since it's kernel related.
[Galaxy S II Original Android Development] MistahBungle:
b7 is fantastic other than not being able to use MTP with CM9 (none of the apps which claim to enable it work for me), so I've gone back to b6 where MTP works. Am sticking with SiyahV3b6 for now until the CM9 team improve their kernel beyond what I can do with Siyah b6 or until we get another Siyah build with MTP working on CM9 again. Whichever comes first basically.
[Galaxy S II Original Android Development] joseph.alukka:
I'm running Stock ICS LPQ. I guess BLN will work on CM9 from RC1 onwards according to Gokhan's website next release description.
[Galaxy S II Original Android Development] DROIDRACER:
Performance/Deep sleep

just a couple pic's been using b7 since it was released and think its by far the best so far (for me that is)
[Galaxy S II Original Android Development] Qwerty__-:
i got this one, but i dont found any settings :/

thx, btw

thx, i try here
[Galaxy S II Original Android Development] Entropy512:
/sys/module/stand_hotplug/parameters/lock

It has a slightly different path in Gingerbread, but I'm surprised you are unaware of this.

Setting this to 1 will lock the hotplugging configuration to the current state - e.g. if both cores are online and you set this to 1, both cores will stay online.

If you set it to 1 when the second core is offline, it will stay offline no matter what.

It does so by disabling all of the logic which determines when cpu_up() and cpu_down() get called.

https://github.com/Entropy512/kerne...ter/arch/arm/mach-exynos/stand-hotplug.c#L198 - see the user_lock variable

Don't think there's much need to buy the device other than possibly the fact we're a bit ahead in receiving ICS - other than that it's nearly identical at the kernel level.

https://github.com/Entropy512/linux...master/arch/arm/mach-s5pv310/pm-hotplug.c#L97 - The lock functionality exists in Gingerbread kernels, but the path will be slightly different than above.
[Galaxy S II Original Android Development] vivmar:
help

please,someone can help me with this issue?

i have tryed siyah with different rom,like cm9-wanam or hydrogen and in all cases,when i install this kernel i'll start with same issue,my phone randomly when i use it or when i put on screen,will be "freezed" (remain stuck) and i have to pull out battery....

in a lot of cases,this happens to me when i start phone at lockscreen,i try to unlock it and will be stuck...

with same rom,if i change kernel...no more issue

any idea? (i have stock siyah settings,so no oc,no uv..ecc....)
[Galaxy S II Original Android Development] joseph.alukka:
Older pc's have a self resetting thermal fuse on the USB hub controller to trip when the slave draws more than 500mA which no devices back then used to do. Newer MB's have 1000mA fuses to support the newer portable HDD's and power hungry USB devices. No risk in trying 650mA for USB, if your MB doesnt support, the phone will stop charging suddenly until you disconnect/reconnect.

@Gokhan

That gives me a question, can the charge current for S2 be increased to 800-900mA from the kernel? Even if not permenently, temporarily such that phone can be charged quicly while travelling and all? My old Nokia 5800 charged at 850mA from AC charger and filled the empty 1350mA battery in 1.5hrs. S2 takes nearly 4 hrs to fill up from empty and 800mA could save maybe an hour on the total charge time. Or is it preset by the charge controller chip?
[Galaxy S II Original Android Development] gokhanmoral:
no, no need to sorry. I am very happy that you two are discussing here.

I am also still working on the same problem. changed the code a bit and put lots of printk()s

the cpu can scale when the policy->max is higher but it doesn't scale down if it is lower than the current limit.

I am just searching which part of the code causes that.

it may not be a dvfs lock, maybe a mutex prevent that, or anything else, maybe it's a race condition.. I still have no idea because I searched all max_support_idx, policy->max, even ->max and limit keywords and read the code line by one...

and it happens only on load.

I will try to debug more now...
[Galaxy S II Original Android Development] t2k269:
If I set the hotplug policy to second core always on by ExTweak. The phone become unstable, stuck or may be freezed. No OC/LV applied.
[Galaxy S II Original Android Development] Delacor:
+1

But I read some pages ago that it is controlled by a Chip and not Kernel related, but IF gok can do that, we have the most Fu*king Crazy superawesomeness Kernel Ever!!! But I think S2 users must live with 450-650 (which person charge a smartphone with 450mah?) SAMSUNG U NO CHARGING?

Send from my SII ;)
[Galaxy S II Original Android Development] Entropy512:
Not true - there is risk running 650 mA from USB without the ability to determine that the motherboard supports higher currents because some motherboards or hubs have rudimentary overcurrent protection and may get damaged. It's pretty rare nowadays - but as an example my monitor's USB ports are blown due to a Chinese "pirate special" GPS that would draw more than 500 mA from USB host ports. 1A support on USB ports is part of newer standards, and drawing more than 500 mA under any circumstances requires the host (or charger) notifying the device of the ability to deliver more than 500 mA. Shorting D+ and D- together by the charger is one such method (for dumb chargers) - but there are now methods (USB 3.0, non-standard USB 2.0 extensions) for signaling high-current USB host support too, but the GS2 doesn't support any of these methods. The only devices I know of that currently do are tablets - iPad (nonstandard USB 2.0 extensions, meaning Apple hosts only), Transformer Prime (USB 3.0), probably a few other newer tablets and maybe some newer phones.

I'm fairly certain the DVFS locks aren't the problem, because it seems to only happen when setting a policy maximum 1 GHz when current frequency is 1.2 (rare but does sometimes happen - this seems to only occur in race conditions where the frequency rises to 1.2 just as the policy drops to 1), <=800 MHz when current frequency is 1.2 (guaranteed). <= 500 MHz when current is 1.0. Setting 200 MHz when current frequency is 800 seems safe.

I'm positive I've seen sysfs reporting 1.2 GHz when the maximum is 1.0 before. (Will test tomorrow morning, running a drain test now, I just happened to wake up briefly and am going back to sleep as soon as I submit this post)

In addition when I instrumented exynos_set_target, policy->cur was reporting 1.2 GHz speed every time it was entered. This weekend I'm going to check policy->cur on exit.
[Galaxy S II Original Android Development] veyka:
It is defo hardware related, there was talk of a second chip, but this is a long way in the future if at all.
[Galaxy S II Original Android Development] rlorange:
yes it can I posted a script here pulled from the GB siyah thread. Max is 950mah works great with my 1000ma USB charger
[Galaxy S II Original Android Development] planetf1:
I've had this with stock kernels before. I can't remember which builds, but pretty certain as recent as LPQ/LP7.

Very rare for me - probably in the order of once every 2 weeks over last 6 weeks or so.
[Galaxy S II Original Android Development] rauschkugl:
No it can't. Your script is useless. It's a hardware limitation of the phone that you cannot workaround with a script.
[Galaxy S II Original Android Development] II_DiE_4:
I have a question for this.. My charger, the original that came with the phone, says output 0,7A.

Even if the scripts works above 650mA, it would be useless right?
[Galaxy S II Original Android Development] MistahBungle:
Yep. That's exactly right.
[Galaxy S II Original Android Development] joseph.alukka:
The 3-4 intel and Amd MB's i have used have this piece of info mentioned under USB headers. They were all standard motherboards from 2004-2009 and have the specs mentioned as 500mA Thermal Fuse enabled in the manual. And I have tried overiding with a load greater using leds and without digital negotiation (without touching D+ & D-), the load simply shuts down after a second or two, if I disconnect and reconnect, fuse resets and same happens. There is no risk at all in trying to pull more than the rated current as long as it has a branded southbridge chipset from Intel or AMD ( I donno abt nvidia Chipsets), they simply shut down. If you have a chinese chipset based pci usb card, it might blow out, but I have never experienced it on any MB's. I had rewired 2 usb ports long back on a 2005 mB just for my portable HDD to work by simply driving the +Vcc from the SMPS 5V, its not protected I know, but that was only what I could do then. however on my motherboards after 2007, they have native charging port support for 500mA+ without digital negotiation and so every thing runs fine. Apple stuffs use the same digital negotiation of measuring D+=D-=2V or something near to sense for charge, have never heard of a short between the D+ and D- though, that will just blow off the hub controller of most MB's. And as you said, rudimentary overcurrent protection is what works, it will just shut the device down, wont blow it at all. Thats for the USB host side, we'll use a dedicated constant current 800mA SMPS charger, so no USB hub issues. But for the S2 support, is what I dont know about. If a 5yr old Nokia 5800 can charge at 800mA, why cant the S2? This is what I need to confirm. 5800 used a current regulator chip and no matter even if I provide 8VDC, it would charge fine. Yesterday tried S2 on a USB 1000mA charger and the phone was throttling at 648mA which I dont know what was bottlenecking it. I could be wrong with all this, but this is what my experience tells me.

---------- Post added at 04:10 PM ---------- Previous post was at 04:06 PM ----------

Can you link it please :)
[Galaxy S II Original Android Development] Happy_Jack:
BS. Anyway the idea is to short the data connections the device sees, not the host PC. What would be the point in that? I made myself a little converter that does this from a cheapo (and otherwise pointless) "USB socket saver". Using this my SGS2 draws around 640mA instead of 450mA from my (1A capable) PC or my Chinese battery/USB charger.

From http://en.wikipedia.org/wiki/USB - "A portable device can recognize the type of USB port from the way the D+ and D- pins are connected. For example, on a dedicated charging port, the D+ and D- pins are shorted.".
[Galaxy S II Original Android Development] TecQuality:
guys i need a tip: can i use VC in synergy with ExT? maybe i'm wrong but these apps do the same things or not?
[Galaxy S II Original Android Development] hirak99:
I have moved to stock XWLP3 and Siyah at once, so I don't know if Siyah is causing this or the new ROM. I see the battery is getting used faster, and lot of the battery is used by the Android OS primarily.

Is this to be expected? What is the expectation from Siyah running at default values, is it supposed to take more, less, or equal amount of power to run compared to stock?