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

Siyah kernel - Dummies Guide

Since my phone is always on, I always use Mobile Odin. It's awesome :D

Siyah v3.1 official looks imminent. Changelog (from da site) below:

- changed
 
Forbidden 403 said:
Damn, that extra change log reverted it back to rc6 :(

Anyways already downloading :p
Click to expand...

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 :D
 
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
 
Kie said:
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 :D
Click to expand...

I would recommend atleast going upto rc6 as he has mentioned the wakelocks issue with blnww.


iT0mm0 said:
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
Click to expand...

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 )
 
iT0mm0 said:
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 ?
Click to expand...

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.
 
Ummm... the built in profiles of battery/default/performance are freely available in the Kernel specific tweaks section of CWM Recovery. :p
 
SiyahKernel v3.1 is imminent

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).
 
He had removed the 1600mhz option around the rc1 phase only. It was causing bootloops and freezes on quite a few phones. So he limited OC to 1400mhz.
 
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:

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.
Click to expand...

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.
 
  • Like
Reactions: Kie
Siyah kernel v3.1.1 is up! :D

"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)"
 
You must log in or register to reply here.
Back
Top Bottom