• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Siyah Gingerbread kernel (v2.x)

That's right... pick on us over 35's!
Are we talking Stone here?

To be fair... I had just returned from a Burn's Night.
What you do with those candles you hide under your mattress should not be made public!

:D


What was wrong with CWM in previous Siyahs? Change for the sake of it? Are there any real-world benefits of Hyperdroid over CWM Recovery, or is it just a different front-end UI?
I get a little bit concerned when CWM recovery gets replaced. Does anyone know for sure if existing CWM backups will restore correctly with Hyperdroid and vice versa?
 
What was wrong with CWM in previous Siyahs? Change for the sake of it? Are there any real-world benefits of Hyperdroid over CWM Recovery, or is it just a different front-end UI?
I get a little bit concerned when CWM recovery gets replaced. Does anyone know for sure if existing CWM backups will restore correctly with Hyperdroid and vice versa?

According to the changelog... "this recovery can also mount both internal and external sd. (thank you af974@XDA)".

Allegedly, yes, it can restore CWM backups and visa versa... anybody wanna try?

xda-developers - View Single Post - [KERNEL] SiyahKernel v2.6.11 - "One kernel to rule them all" (SAMMY&AOSP ROMs)

Exactly what I was thinking! Guess there's only one way to find out for sure.... looks like I'll be downloading and flashing .11 after all.

Nice one Slug! :eek:
 
Allegedly, yes, it can restore CWM backups and visa versa... anybody wanna try?

I'm about to.... just finished backing up the current setup and downloading the new kernel release. I'll flash it, reboot a couple of times to make sure everything initialises correctly then backup the new setup. The fun can then commence. ;)

update:
No problems at all. A backup from v2.6.9 restored with v2.6.11, and I then reversed the process back to v2.6.11 without incident. Default backup location is still /sdcard/external_sd, and the option to backup to/restore from internal sdcard remains. I didn't test it but the copies I have stored on /sdcard were certainly recognised and available.

Incidentally, slight changes have also been made to the hotplug loadl and loadh parameters, and the gpu_control stepping in v2.6.11. Default scheduler is still bfq.
 
I have been reading a thread on undervolting on XDA and the writer suggests the following for smooth operation and good battery life.

+ VOLTAGES:

100Mhz - 900mV
200Mhz - 900mV
500Mhz - 950mv
800Mhz - 1000mv
1000Mhz - 1100mV
1200Mhz - 1200mV
1400Mhz - 1300mV

When I look in Siyah voltage settings they are:

100Mhz - 950000mV
200Mhz - 950000mV
500Mhz - 950000mV
800Mhz - 1050000mV
etc...

As you can see, there is an abnormal difference in voltages to what Siyah says it is at and what the writer over at XDA has posted. Has the writer at XDA dropped a few 0's?

Edit, Actually after looking at this, is the Siyah Voltage settings incorrectly displayed?
Edit, Edit - Never mind, I answered my own question. The Siyah display is not in mV's thus you can't use the Voltage built in program to adjust your voltages. (it would take you forever to actually drop the voltage by 50mV) Using Voltage Control app from the app store works well...
 
I have been reading a thread on undervolting on XDA and the writer suggests the following for smooth operation and good battery life.

+ VOLTAGES:

100Mhz - 900mV
200Mhz - 900mV
500Mhz - 950mv
800Mhz - 1000mv
1000Mhz - 1100mV
1200Mhz - 1200mV
1400Mhz - 1300mV

When I look in Siyah voltage settings they are:

100Mhz - 950000mV
200Mhz - 950000mV
500Mhz - 950000mV
800Mhz - 1050000mV
etc...

As you can see, there is an abnormal difference in voltages to what Siyah says it is at and what the writer over at XDA has posted. Has the writer at XDA dropped a few 0's?

Edit, Actually after looking at this, is the Siyah Voltage settings incorrectly displayed?
Edit, Edit - Never mind, I answered my own question. The Siyah display is not in mV's thus you can't use the Voltage built in program to adjust your voltages. (it would take you forever to actually drop the voltage by 50mV) Using Voltage Control app from the app store works well...

950000mV is 950V! No way you'd be churning 950V through your little SGS2! That would probably start to become an electrocution hazard lol.

Siyah is obviously incorrect, but glad you figured it out for yourself (although not in the same way!)
 
I have been reading a thread on undervolting on XDA and the writer suggests the following for smooth operation and good battery life.

+ VOLTAGES:

100Mhz - 900mV
200Mhz - 900mV
500Mhz - 950mv
800Mhz - 1000mv
1000Mhz - 1100mV
1200Mhz - 1200mV
1400Mhz - 1300mV

When I look in Siyah voltage settings they are:

100Mhz - 950000mV
200Mhz - 950000mV
500Mhz - 950000mV
800Mhz - 1050000mV
etc...

As you can see, there is an abnormal difference in voltages to what Siyah says it is at and what the writer over at XDA has posted. Has the writer at XDA dropped a few 0's?

Edit, Actually after looking at this, is the Siyah Voltage settings incorrectly displayed?
Edit, Edit - Never mind, I answered my own question. The Siyah display is not in mV's thus you can't use the Voltage built in program to adjust your voltages. (it would take you forever to actually drop the voltage by 50mV) Using Voltage Control app from the app store works well...

Wow I guess my U/V settings are pretty aggressive... No stability issues however.
 
Actually the giveaway was when I figured out how much 950000mV was. I think the little bugger would be some warm!!

Oh yeah it would be a ball of melted plastic! lol But comparing the settings you got off XDA to my settings, I've gone really aggressive with my U/Ving.
 
anyone using the example init.d scripts gokan has linked to on his xda page?? or people using their own? any recommendations??
 
so what's yer impression of 2.6.11? i installed it, bog standard no tweaks, to be honest, let it sit for a few hours and i could swear i saw battery draining in front of my eyes. prob got paranoid after reading some bloke got the same on xda, plus the pub didn't help.

anyroads, i uninstalled it and went back to 2.6.9 which is rock solid. the new recovery menu *looks nice* tho :)
 
so what's yer impression of 2.6.11? i installed it, bog standard no tweaks, to be honest, let it sit for a few hours and i could swear i saw battery draining in front of my eyes. prob got paranoid after reading some bloke got the same on xda, plus the pub didn't help.
:)

I'm acutally finding the opposite. Unplugged my phone this morning and 8 hours later still at 92%. Best I have ever had.
 
Siyah 2.6.11 is another winner for me, along with the LP6 modem.

After 4 days of use I am getting some of the best battery life ever on this kernel. In fact I'm now down to a 1.5% drain per hour overnight... down from my usual 2%. That's with GPS, Wi-Fi, auto and background sync and widgets firing on all cylinders, 24/7.

Scrolling is very smooth even with my u/c'ing, u/v'ing and changes to GPU.

This is another one in the, "Keeper", column for me. :D

For more information, installation and settings for Siyah 2.6.11, see here:-

http://androidforums.com/galaxy-s2-...0-11-dummies-guide-installation-settings.html




Having said that, I'm now switching to N.E.A.K. 1.3.2 to give that a damn good thrashing! :eek:
 
At what point should the modem be installed? Does it need to be reinstalled with each Siyahkernel upgrade?

Any time you like. The modem and kernel are two separate entities that are not reliant on one another. Upgrading your Siyah kernel does not affect your modem.

Hope this helps. :)
 
After installing 2.6.11 and new modem LP6, I found I could receive a call but when I try to send an SMS, it seems to hang. Is there anything I have to do after installing a new modem?
 
Yes, I ran the kernel cleaning script. The problem seems to have resolved itself. 2 smses did not get through, but now it seems to be fine, so might just have been network problems.
 
I've just noticed something good. The bug stopping things being installed directly from the kitchen is fixed. It could be the new recovery system or it could have been fixed for ages and I'm just not that observant.
 
Back
Top Bottom