Flashed stock ICS via Odin (I9100XWLP4), flashed CF-Root v5.4 LP3 via Odin. Then flashed old bootloader and sucessfully used my USB jig to get rid of yellow triangle and reset flash counter. Flashed Siyah 3.0.1 via CWM.
All good so far, but now I must go to bed !!
I'm slightly confused when it comes to the old bootloader. Does it require a different old bootloader for ICS, or will the GB old one do the job?
Device(s): SGSII GT-i9100 Root. Firmware: NEAT ROM LITE LSS. Jelly Bean 4.1.2 Baseband XXMS2 Kernel: Siyah
Carrier: Vodafone
Thanks: 743
Thanked 2,360 Times in 1,627 Posts
Siyah kernel v3.1 beta1 is up!
"Changelog:
touchscreen sensitivity tweaks
sio fifo_batch=1
set default usb mode to mass_storage for MIUI ROMs.
disabled smooth scaling for interactive based governors (lulzactive and interactive)
prevented tick sound after reboots or in download/recovery modes
Dual-booting
For now, you will only have one additional option available in CWM Touch Recovery and that is cloning your primary ROM as secondary.
If you want to have another ROM as secondary ROM, follow these steps:
Make a nandroid backup of your existing ROM
wipe everything and install the other ROM
Boot the ROM and make customizations. Don’t forget to reflash SiyahKernel if the ROM flashes another kernel.
Use CWM Touch Recovery to clone your rom as secondary rom.
Restore nandroid backup
Keep in mind that you will not be able to flash additional CWM packages to the secondary ROM. Therefore, it is important that you have flashed all additional packages and customizations in the third step before you make the clone in the 4th step.
Some notes about dualbooting:
If you do not make any cloning you won’t be prompted to boot the second ROM.
you may need to reflash this kernel after a nandroid restore if your nandroid backup is created with another kernel.
there is no progress bar during the cloning process. it will be implemented later but for now, be patient because the size of data is huge and may take up to 10 minutes to clone.
there are some checks missing. for example if you do not have enough space in your internal sdcard (you need 2.1GB free space) you will not get a warning or error, but dual booting won’t work. remember, this is beta and not all features are implemented yet. In time, other dual-booting options in CWM Touch Recovery will be implemented.
you won’t be able to use mass storage mode for /sdcard in second rom because we have our data and cache partitions on /sdcard. only external sdcard will be mounted if you are using mass_storage mode. mtp should work fine for sdcard.
once again, you won’t be able to flash any CWM flashable zip to second ROM."
I skipped Siyah v3.1 beta 1 because Siyah v3.1 beta 2 is out!!
Changelog (from da site
- fixed high memory usage
- fixed booting Samsung ROMs as the second ROM
- no need to fix CWM Manager backup issue. If you use any action in CWM Manager it will only boot to recovery because CWM Touch Recovery only works for the primary ROM. The commands are created in secondary ROM’s cache partition if you use CWM Manager in the second ROM, therefore they will be ineffective in the recovery mode.
- re-enabled CGROUP_TIMER_SLACK and SCHED_AUTOGROUP
- reapplied ondemandx patch (I forgot to put it back in v3.0 release. it should be the reason of having more battery drain with 3.0 than 3.0rc2)
Looks like I'm back on ondemandx!
Edit1: I still only have the ondemand option, no ondemandx.
Edit2: And Siyah 3.1 beta 3 is right around the corner!
Changelog up to now:
- fixed move2sd problem in CM9 and AO(S|K)P ROMs
- mounted sdcard with utf8 (should fix some chinese or cryllic chars not being displayed correctly)
- I recommend you to use move2sd feature only on the primary rom because there are lots of details which is really hard to explain here.
Edit3: Siyah 3.1 beta 3 is out! lol gokhan's churning them out today!
Device(s): SGSII GT-i9100 Root. Firmware: NEAT ROM LITE LSS. Jelly Bean 4.1.2 Baseband XXMS2 Kernel: Siyah
Carrier: Vodafone
Thanks: 743
Thanked 2,360 Times in 1,627 Posts
Siyah kernel v3.1rc2 is up!
"Changelog:
removed 1600MHz and 100MHz steps
merged with cm9 sources (some patches for at&t version and lots of cleanups/rewrites. thanks to teamhacksung and Entropy512)
updated the build script a little to fix the module loading issues (which is, by the way, the main root of wifi toggling issues)"
* new feature: BLN without Wakelock (BLNWW). Disabled by default. You have to enable it using ExTweaks app.
* default I/O scheduler is set to CFQ.for default profile.
* CIFS is now built-in, no longer a module, to save space
* Superuser.apk, su, CWMManager.apk and ntfs-3g files are moved to the end of the kernel and won’t be decompressed unless they are needed to speed up the boot time.
* samsung recovery binaries and some unnecessary files moved to the end of the kernel image to eliminate unnecessary decompression. those will be decompressed only when you boot into recovery, which will make the booting process faster.
* we are now back to gzip compression after moving unnecessary binaries to payload part.
Last edited by Hawker; April 14th, 2012 at 08:27 AM.
checked all freq and voltage interfaces and found no problem. make sure you remove boot settings and reapply after flashing rc2 or newer because the number of frequency steps has changed. we do not have 8 steps anymore, we have 6 steps. you have to update your init.d scripts or reapply boot settings accordingly. Just in case, I have added parsing 8-step freq settings and discard first and last settings and apply 6 in the middle.
added progress bar to cloning process.
new feature: swap primary and secondary ROMs. It takes about twice the time of a cloning process. This will help you to update your second ROM until I finish flashing zips to second ROM.
updated smooth_scaling defaults to new step level. (smooth_target=1, smooth_offset=2, smooth_step=2)
added available space checks to cloning and swapping ROMs.
updated to linux 3.0.28
BLN: fixed cm9 ROMs having touch lights off after BLN notification
checked all freq and voltage interfaces and found no problem. make sure you remove boot settings and reapply after flashing rc2 or newer because the number of frequency steps has changed. we do not have 8 steps anymore, we have 6 steps. you have to update your init.d scripts or reapply boot settings accordingly. Just in case, I have added parsing 8-step freq settings and discard first and last settings and apply 6 in the middle.
added progress bar to cloning process.
new feature: swap primary and secondary ROMs. It takes about twice the time of a cloning process. This will help you to update your second ROM until I finish flashing zips to second ROM.
updated smooth_scaling defaults to new step level. (smooth_target=1, smooth_offset=2, smooth_step=2)
added available space checks to cloning and swapping ROMs.
updated to linux 3.0.28
BLN: fixed cm9 ROMs having touch lights off after BLN notification
create /sdcard/.nobootlogo if you don’t want to see the boot logo on startup
reverted throttling levels back to stock levels. your device will be cooler on load but this may affect benchmark scores if the temperature is high. run your benchmarks in a fridge
disabled CONFIG_SCHED_AUTOGROUP
fixed underclocking still uses 1200MHz
fixed performance governor always locking to 1200MHz
used GB kernel’s touch sensitivity values which nobody was complaining about…
The part in italics is same as the last changelog of rc4 the last 6 points are the reason for a redownload.
Redownloading..
Last edited by Forbidden 403; April 16th, 2012 at 03:07 AM.
Reason: missed the italics in the modified changelog
The Following User Says Thank You to Forbidden 403 For This Useful Post:
Aah.. and I was just getting settled with my rc4, well downloading again
First Impressions:
Auto brightness is darker than before in low light, still good and clear for viewing.
No lag experienced yet.
Benchmark scores are also good as expected under my current settings.
Let's see how the battery performs overnight.
BTW i noticed that the default scheduler was set to deadline, but the changelog doesn't mention it. Can someone confirm plz. I changed it back to sio.
Last edited by Forbidden 403; April 17th, 2012 at 03:49 AM.
changed “format /emmc” and “format /sdcard” to “format internal sdcard” and “format external sdcard” to prevent confusion. In CWM Recovery, /emmc is internal sdcard and /sdcard is the external.
added back the vibration level setting (thanks to myfluxi for the fix)
fixed ntfs automount for usb sticks. it will be mounted to /mnt/ntfs
Not released yet.
edit: gokhanmoral has edited the post on his site. It's no longer called rc6, its just called 3.1
Last edited by Forbidden 403; April 17th, 2012 at 08:44 AM.
Reason: rc6 renamed to 3.1
Why do I get "no zImage file found" when trying to flash Kernel with CWM Manager.
Siyah-v3.1rc5-CWM.zip downloaded and I can see the zImage file in the zip-file.
Zip-files is placed in internal SD root.
What option do I choose when rebooting into ClockWorkMod recovery to do the same procedure there? Do you think that will work?
Why do I get "no zImage file found" when trying to flash Kernel with CWM Manager.
You are already on a previous Siyah version, CWM Manager by Chainfire uses aspects of a modified CWM recovery in a CF-root kernel. The CWM recovery of Sitah kernels is modified by gokhanmoral according to his needs. It is not fully compatible with CWM Manager.
Somewhere gokhanmoral had mentioned that many actions of CWM Manager will not work and will reboot you to CWM recovery instead.
All you need to do is reboot into recovery (you can do that from the CWM Manager also) and then install the zip file from there. It will work, I had faced the same issue and it worked for me.
The Following User Says Thank You to Forbidden 403 For This Useful Post:
All you need to do is reboot into recovery (you can do that from the CWM Manager also) and then install the zip file from there. It will work, I had faced the same issue and it worked for me.
How do I install it? Like a ROM? Install zip from SD?
How do I install it? Like a ROM? Install zip from SD?
Yeah just flash it like you flash a ROM. Its been a while since I've flashed a siyah kernel with the cwm app so I could be wrong here. But I think if you download the tar instead of the zip it will flash from the app.
__________________
I find the will so hard to find.
Oh well, whatever, nevermind!
The Following User Says Thank You to Shotgun84 For This Useful Post:
How do I install it? Like a ROM? Install zip from SD?
Yes choose install zip from SD (or internal sd depending on where you copied it)
Quote:
Originally Posted by Shotgun84
Yeah just flash it like you flash a ROM. Its been a while since I've flashed a siyah kernel with the cwm app so I could be wrong here. But I think if you download the tar instead of the zip it will flash from the app.
gokhanmoral has changed a lot of the CWM recovery app, adding swipe touch, software buttons, support for dual booting etc.
Hence the recommendation is don't use CWM Manager as it was coded to work with the cf-root kernel.
Use the zip only and flash from the recovery menu.
Nowadays all I use the CWM Manager app is to boot into recovery mode
Yes choose install zip from SD (or internal sd depending on where you copied it)
gokhanmoral has changed a lot of the CWM recovery app, adding swipe touch, software buttons, support for dual booting etc.
Hence the recommendation is don't use CWM Manager as it was coded to work with the cf-root kernel.
Use the zip only and flash from the recovery menu.
Nowadays all I use the CWM Manager app is to boot into recovery mode
Personally I don't even use it for that, I just boot into recovery with the power menu shortcut, I'm not too sure why I still have it on my phone. I only really remember the .tar used to work with the app as I thought it was strange that worked and the cwm zip didn't.
I've never used CWM manager neither.
I always flash via CWM Recovery. I've heard CWM Manager flashes can be unreliable. If you do want to flash when the phone is up and running, use Mobile Odin.
I've never used CWM manager neither.
I always flash via CWM Recovery. I've heard CWM Manager flashes can be unreliable. If you do want to flash when the phone is up and running, use Mobile Odin.
Ah of course how did I forget Mobile Odin. That's a wonderful app too.
It may be just me but I always feel comfortable with Odin on PC and CWM Recovery mode.
@Shotgun82
The power button shortcut is only available on custom roms if I am right.
Since my phone is always on, I always use Mobile Odin. It's awesome
Siyah v3.1 official looks imminent. Changelog (from da site) below:
- changed “format /emmc” and “format /sdcard” to “format internal sdcard” and “format external sdcard” to prevent confusion. In CWM Recovery, /emmc is internal sdcard and /sdcard is the external.
- added back the vibration level setting (thanks to myfluxi for the fix)
- fixed ntfs automount for usb sticks. it will be mounted to /mnt/ntfs
Siyah v3.1 official looks imminent. Changelog (from da site) below:
- changed “format /emmc” and “format /sdcard” to “format internal sdcard” and “format external sdcard” to prevent confusion. In CWM Recovery, /emmc is internal sdcard and /sdcard is the external.
- added back the vibration level setting (thanks to myfluxi for the fix)
- fixed ntfs automount for usb sticks. it will be mounted to /mnt/ntfs
Or...RC6...yes, I mean Siyah v3.1 rc6 is out WITH...one extra change:
- removed blnww temporarily because of the battery drain it causes
No problem Hawker I'll check the thread out and see if I can provide at least some guidance :P
The Following User Says Thank You to Kie For This Useful Post:
Device(s): SGS2,
4.2.1 mcm vsync,
Siyah v5 vsync,
NELP4 modem
Carrier: 3 (for my sins)
Thanks: 16
Thanked 49 Times in 34 Posts
Siyah has been eating my battery for fun, even rc6, im just making the switch over to NEAK can any of you kind people point me to a thread about battery saving settings for this kernel ?
Device(s): SGSII GT-i9100 Root. Firmware: NEAT ROM LITE LSS. Jelly Bean 4.1.2 Baseband XXMS2 Kernel: Siyah
Carrier: Vodafone
Thanks: 743
Thanked 2,360 Times in 1,627 Posts
Quote:
Originally Posted by iT0mm0
Siyah has been eating my battery for fun, even rc6, im just making the switch over to NEAK can any of you kind people point me to a thread about battery saving settings for this kernel ?
TIA
AFAIK there isn't a thread specifically for NEAK 2.X settings yet.
The thread that you could adapt to 2.x is this one:-
Yes one would think an additional change would put it even closer to official v3.1, not further away! Haha gokhan is always keeping us guessing...
I might wait for official v3.1 since it's only minus 1 or 2 changes away
I would recommend atleast going upto rc6 as he has mentioned the wakelocks issue with blnww.
Quote:
Originally Posted by iT0mm0
Siyah has been eating my battery for fun, even rc6, im just making the switch over to NEAK can any of you kind people point me to a thread about battery saving settings for this kernel ?
TIA
Post rc2/rc3 even I am experiencing bad battery life.
Try switching to the battery mode from CWM recovery's kernel specific options menu. That should help.
And it's really too early to comment on battery life of rc6, a kernel needs to settle in before we can really judge battery life.
Will let rc6 settle in for 48 hrs or so before I post about it's performance and battery life (i.e. if gokhanmoral doesn't release another release in the meantime :P )
The Following User Says Thank You to Forbidden 403 For This Useful Post:
Siyah has been eating my battery for fun, even rc6, im just making the switch over to NEAK can any of you kind people point me to a thread about battery saving settings for this kernel ?
Battery is driving me mad also. Did the NEAK kernel improve things, what settings did you use?
I discovered what was eating my battery.
It was Skype and BLN.
With Skype off and BLN disabled I have better battery even on 200-1400 overclocking of cpu.
I just decided to go ahead and urchase, mainly because of the built in profiles it offers. I'm a complete noob at mucking about with these kinds of settings so hopefully the battery/performance/default profiles will give me a flavour of what's possible. Plus helping the devs is always a good thing of course.
Changelog (including the changes from all previous 3.1 beta and rc builds):
USB serial support
USB mouse and keyboard support and fixed crash on unplug (thanks to sztupy for his galaxy s kernel sources and kevinh for the patches)
latest CM9 support
new liblights which supports both Samsung and cm9 ROMs+kernels to prevent problems when users flash stock or speedmod kernels.
re-enabled CGROUP_TIMER_SLACK and SCHED_AUTOGROUP
disabled smooth scaling for interactive based governors (lulzactive and interactive)
Dual-booting
prevented tick sound after reboots or in download/recovery modes
sio fifo_batch=1
adjustable gamma and vibrator levels (thanks to myfluxi)
added gamma and vibrator level adjustments to ExTweaks app
removed 1600MHz and 100MHz steps
merged with cm9 sources (some patches for at&t version and lots of cleanups/rewrites. thanks to teamhacksung and Entropy512)
default I/O scheduler is set to CFQ.for default profile.
CIFS is now built-in, no longer a module, to save space
Superuser.apk, su, CWMManager.apk and ntfs-3g files are moved to the end of the kernel and won’t be decompressed unless they are needed to speed up the boot time.
samsung recovery binaries and some unnecessary files moved to the end of the kernel image to eliminate unnecessary decompression. those will be decompressed only when you boot into recovery, which will make the booting process faster.
Implemented clone primary to secondary, clone secondary to primary and swap primary/secondary ROMs in CWM Recovery
updated to linux 3.0.28
fixed ntfs automount for usb sticks. it will be mounted to /mnt/ntfs
changed “format /emmc” and “format /sdcard” to “format internal sdcard” and “format external sdcard” to prevent confusion. In CWM Recovery, /emmc is internal sdcard and /sdcard is the external.
not released yet
Just hoping that this does not turn into rc7 at the last minute (like with rc6).
So far so good, having installed it alongside the newly-released D4 v7.0. Previous undervolting settings caused a hard lock but I think I've got that sorted by upping the 500MHz voltage slightly. Other than that, no problems.
However, this from the changelog may be worth bearing in mind:
Quote:
changed “format /emmc” and “format /sdcard” to “format internal sdcard” and “format external sdcard” to prevent confusion. In CWM Recovery, /emmc is internal sdcard and /sdcard is the external.
Using D4 these mount points are reversed, with /emmc being the external card and /sdcard the internal storage. It appears to be a general issue with AOSP-based ROMs.
Device(s): SGSII GT-i9100 Root. Firmware: NEAT ROM LITE LSS. Jelly Bean 4.1.2 Baseband XXMS2 Kernel: Siyah
Carrier: Vodafone
Thanks: 743
Thanked 2,360 Times in 1,627 Posts
Siyah kernel v3.1.1 is up!
"Changelog:
applied latest cm9 initramfs changes
if you use cm9 as your second ROM, remember that internal sdcard location is /mnt/sdcard and it is fixed. you should have Settings->Storage->(Press menu)Storage Configuration->Use internal storage TICKED but the internal/external storage order will be reverse if you use cm9 as second ROM.
this kernel may not be compatible with some aokp based roms until they start using new cm9 convention for mount points. in that case use v3.1rc6.
increased min_free_kbytes to 16384 to see if it fixes wifi toggling issues (thanks to wjchen)"
74Likes
RC4 is out...
SiyahKernel v3.1rc4 UPDATED 16 April
