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

Siyah 2.1 beta 13 actually works

Just in case any ones interested. I have tried 13 and 14 (gave 15 a miss as there still seem to be a few bugs) and out of the 2 I'd say beta 13 its the best option. 13 seems to have better battery and 14 suffered from quite a bit off lag and caused my phone to freeze a couple of times.
 
Shotgun84 said:
Just in case any ones interested. I have tried 13 and 14 (gave 15 a miss as there still seem to be a few bugs) and out of the 2 I'd say beta 13 its the best option. 13 seems to have better battery and 14 suffered from quite a bit off lag and caused my phone to freeze a couple of times.
Click to expand...


Beta 13 says that it gets rid of AOS usage... is this the same for 14 because i flashed beta 14 and i still have the AOS usage and tbh battery life isnt that excellent... i'm using:-

SmartassV2 Scaling
Screen off profile 200 - 500 with Conservative governer
 
If I read the governor descriptions correctly, there is no need to have a screen off profile for smartassV2, it already uses the very minimum required amount of CPU power while the screen is off, perhaps I misread but that discussion was in the Siyah kernel thread at one point in the last few days.
 
It all depends on how each handset is used. I run a 200/500/conservative screen-off profile too, for slightly better endurance. It does make the CPU slightly slower to respond though, which could be an issue depending on apps used.
 
There is also a significant debate on xda regarding whether kernels with lower AOS usage actually fixed the AOS bug or just stuffed the usage into another category thus not really reducing battery drain at all, I believe gokhanmoral removed the fixes from Siyah 2.1 (b12/b13?) in one of the betas so the AOS usage returned but nobody noticed a significant increase in battery drain at least from the discussion in the kernel thread, so the conclusion of the moment was that the patches are simply hiding it in a different category rather than completely fixing it.
 
Siyah kernel v2.1 rc2 is now up! :D

Changelog

"re-enabled auto rooting
automatic efs backup removed temporarily
auto-creation of /sdcard/clockworkmod/.salted_hash to fix problems with CWM5.X (thanks to olifee@xda)
some usb fixes (again, thanks to olifee@xda). this should fix usb keyboard & mouse problems but I could not test as I am still waiting for my OTG cable.
interactive governor removed
lulzactive (thanks to tegrak) and smartass governors enabled and set lulzactive as default.
some more performance optimizations (most of them are from beta14 which seems to be the best beta in terms of performance)
added BFQ-v2-r1 io/scheduler back. some people think that it is the best for HD video recording. it doesn’t hurt to have one more i/o scheduler anyway"
 
Wakey! Wakey! boys and girls... Siyah kernel 2.1 rc3 is up. :D

"fixed bluetooth sleep problem
fixed usb detection problems
re-enabled deepsleep entering @500MHz
read-only info about the cpu class
removed ARM_ERRATA_753970"
 
ok installed siyah rc3 with checkrom rev 1.0. Everything seems fine but was initerested to know why CWM says current kernal:unknown. Is that literally because its a beta release or what?
 
Hi can someone point me in the direction of this rom please, i am so sick of watching my battery disappear before my eyes.
 
Does setcpu or Tekrak work for anyone? Both dont seem to work for me at least. :( Cant overclock

Ignore that. Only Tegrak seems to not work . Then again I always did prefer setcpu.
 
Rudedawg said:
initerested to know why CWM says current kernal:unknown.
Click to expand...

I suspect that it's due to the same vagaries of the GS2 that have caused problems with ROM Manager, as CWM is based heavily on that app's code. ROM Manager also never identifies the kernel correctly but rather insists that the one installed is 4.0.1.5, the most recent available via the app.

No problems to report with rc3 today, btw. Battery has drained more than I would have expected but I'm using the new default lulzactive governor. I'll compare tomorrow with smartassv2.
 
Rudedawg said:
Does setcpu or Tekrak work for anyone? Both dont seem to work for me at least. :( Cant overclock

Ignore that. Only Tegrak seems to not work . Then again I always did prefer setcpu.
Click to expand...

I don't think you're supposed to use tegrak anyway as the siyah kernel its based on a stock samsung kernel.
 
You must log in or register to reply here.
Back
Top Bottom