Discussion in 'Android Devices' started by ironass, Mar 20, 2012.
Siyah kernel v3.2rc1 is up!
At last! Felt like a lifetime
RC1 is looking good. I flashed it this morning after zeroing-out my VC/ExTweaks settings. It's running fine with my previous undervolt settings @ 200-1200MHz (using the default 18-step freq_table). No problems to report as yet.
Siyah kernel 3.2rc2 is up!
disabled ESCAN_RESULT_PATCH in wifi driver
auto-reset extweaks profiles if customconfig.xml is changed
default i/o scheduler is set to sio for all profiles
increased brightness level for battery profile
undervolted gpu steps by 50mV in default profile"
I've just updated to 3.2rc2 & now my wifi wont turn on. Have been back into recovery & cleared cache & dalvik, but still the same.
Is there anything I should try next?
what ROM are you using?
I'm on D4 Rom version 10
restore /system/lib/modules from the original rom
3.2 is up
(just cant get the staff these days ironass)
Cheers, but how would I go about doing that
copy the rom
open the copy in 7zip
delete everything apart from META-INF and system
go into system
delete everything apart from lib
go into lib
delete everything apart from modules
Crikey! That caught me out. :ahhhhh:
removed nandroid backup from/restore to 2ndROM. There is a problem which I have just noticed and it will take some time to fix that. Use swap&backup until I fix it.
default lower cpu step is set to 100MHz
your extweaks settings will be automatically reset after flashing this version
used Linaro toolchain 4.7 (2012.04) which let me use gzip without exceeding 8MB"
Does it matter if I change the file name, so I can easily identify it on my phone?
You can call it whatever you want mate
Cheers. I tried it as listed & it got stuck at the siyah boot screen logo when I rebooted. Reinstalled the full ROM & problem is solved.
All good here with v3.2.
Not mine - my customised ExTweaks profile remained active after flashing.
mis post... got excited about change log for 3.2.1.
Was it the thought of having Gok's cat as your boot logo?
V3.2.1 is up! SiyahKernel for SGS2 | "One kernel to rule them all"
removed ntfs-3g from the payload part to make the kernel smaller (I want to enable LZO instead of GZIP). if you want ntfs-3g you can find it here
Blimey, this will be the third kernel change in 24hrs.... slow down, Gok!
Siyah kernel 3.2.2 is up!
added support for Boot-to-Gecko (b2g) (thanks to pulser)
slightly modified panel gamma set to have smoother transition for low-level lights and this will also help a little with the battery life when the screen is on.
removed LCD panel undervolting to prevent grayish tint with low brightness
enabled SCHED_AUTOGROUP once again
Has anyone else been having wifi issues (i.e. it refusing to turn on at all) with Siyah? I've been having this issue intermittently with quite a few of the releases, with some not having the problem but others are. I haven't really been scientific in monitoring it tbh, as it took me a long time to realise that it was a kernel issue (I had thought before it had occured because I had only cleared cache and dalvik when upgrading to a newer version of a ROM, not done a full wipe) but i'm 99% sure it's Siyah doing it now. I switched to N.E.A.K. and haven't had any problems since.
My most recent occurence was when I switched ROMS from D4 to Hydrogen the other day. Hydrogen doesn't come bundled with Siyah so I flashed v3.2 and immediately after rebooting my wifi stopped working, which is the point I realised Siyah must have something to do with it. I'm no expert on these things though. I really like Siyah otherwise though so i'd be hoping to be able to switch back to it once this has been cleared up.
I've been having some issues too. Hawker gave me the instructions shown above, but this didn't work for me. Might work for you though...
Thanks for that ooberandy. I'm kinda relieved i'm not the only one having wifi issues with Siyah, although Hawker's solution seems sort of cumbersome to me (although kudos for figuring it out Hawker!). I might just stay away from it until a definitive fix is reported.
The problem is not with the rom or kernel, it is due to kernel cleaners, hence the update to gs2wiper.
Ah thanks for that Hawker - I had been using an old version of you Blitzer script which was obviously causing all the problems. Cheers!
Looks I should keep a closer eye on some of the threads for these things