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

Siyah Gingerbread kernel (v2.x)

Performance is as good as ever. I cant really say how the battery performs while being used yet as I've only just got up. But I charged it up before I went to sleep, woke up 9 1/2hrs later and was still on 100%.

And lulzavtive seems smoother than it was last night. Maybe it was due to tired eyes.
 
Default for this is ondemand/sio 200/1000

I've put the settings to lulzactive/sio 100/1000.

On golauncher, the smoothness of the menus is MUCH better when max is set to 1000 compared to 800.
For those on 800 max, try setting it to 1000 to see how it compares for you.
 
I only just installed 2.6.4 lol. Thanks for your help Slug. Looks like there are problems with 2.6.5 and Thunderbolt! so won't upgrade till pikachu fixes Thunderbolt! for 2.6.5

One problem I had was that CWM would not mount /sdcard. Anyone come across this? How do I fix this?

I copied over the Thunderbolt! scripts to bolt_scripts on the sdcard manually and went into a terminal. I did "su" and "chmod -R 777 bolt_scripts". Hopefully that has worked. I'm not sure how to tell.

I would be happier if I can resolve the mounting issue in CWM, which can see my sdcard just fine (as I flash kernels from it - "choose zip from internal sdcard" works) but just not mount it under /sdcard.

I added pikachu's Lulzactive settings (described here) to the S98bolt_siyah script.
 
early signs on battery seem very good. phone on 4hrs, some texts, some internet, emails, 30mins music, 5% battery gone. loohing very nice so far.

defo smoother than NEAK for me too.
 

Thanks, checked it out. Uninstalled a few apps I don't really need like 3G watchdog and Android Task Manager. I am on CM7 (nightly 115) so most bloatware has been removed.

Nothing really changed on my phone application-wise since the previous 3 kernels, but the drainage issue of about 10% an hour happens on some of them, probably some sort of sorcery :D

Also, can someone please check out if Skyvi works on your phone, I am just wondering if the kernel itself would have anything to do with it not working on mine "Unable to recognize voice".
 
Thanks, checked it out. Uninstalled a few apps I don't really need like 3G watchdog and Android Task Manager. I am on CM7 (nightly 115) so most bloatware has been removed.

Nothing really changed on my phone application-wise since the previous 3 kernels, but the drainage issue of about 10% an hour happens on some of them, probably some sort of sorcery :D

Also, can someone please check out if Skyvi works on your phone, I am just wondering if the kernel itself would have anything to do with it not working on mine "Unable to recognize voice".

Gosh! That was quick leondb. :D

When you go to Settings > Applications > Running services... do you see Wi-Fi sharing or Wi-Fi sharing manager?
 
Gosh! That was quick leondb. :D

When you go to Settings > Applications > Running services... do you see Wi-Fi sharing or Wi-Fi sharing manager?

No; luckily CM7 left those out on stock they were killing my battery; so glad those are gone. Checked again, nothing funny running, the regular stuff I installed, nothing new.

9h45m and 36% remaining isn't that bad I guess... However, I get 16 to 18 hours usually. Maybe its the 36C weather we are having today :eek: hehe.

Perhaps it will go better with the next kernel, or I will just revert.
 
Looks like there are problems with 2.6.5 and Thunderbolt! so won't upgrade till pikachu fixes Thunderbolt! for 2.6.5

I couldn't get a clear picture of exactly what the "problems" were, so simply whacked v2.6.5 on to see what happened. So far I've seen no noticeable issues, except for a reported error in the syntax of the screenstate_scaling script when I checked it with Script Manager.

I copied over the Thunderbolt! scripts to bolt_scripts on the sdcard manually and went into a terminal. I did "su" and "chmod -R 777 bolt_scripts". Hopefully that has worked. I'm not sure how to tell.
I don't think you can set those permissions on an SD card as the file system won't allow it. The scripts in bolt_scripts are either examples to replace those in init.d or meant to be run manually, so I don't believe it's necessary to change the permissions.

I would be happier if I can resolve the mounting issue in CWM, which can see my sdcard just fine (as I flash kernels from it - "choose zip from internal sdcard" works) but just not mount it under /sdcard.
Are you presuming that it's not mounting because bolt_scripts is copied to the external card? If so then that's down to how the GS2 presents the mount point - mine is the same. I can "mount /sdcard" in CWM Recovery but flashing Thunderbolt! results in the bolt_script folder appearing on /sdcard/external_sd.
 
No; luckily CM7 left those out on stock they were killing my battery; so glad those are gone. Checked again, nothing funny running, the regular stuff I installed, nothing new.

9h45m and 36% remaining isn't that bad I guess... However, I get 16 to 18 hours usually. Maybe its the 36C weather we are having today :eek: hehe.

Perhaps it will go better with the next kernel, or I will just revert.

36C or slightly better battery. mmmm, know what i'd rather have ;)
 
I don't think you can set those permissions on an SD card as the file system won't allow it. The scripts in bolt_scripts are either examples to replace those in init.d or meant to be run manually, so I don't believe it's necessary to change the permissions.
Ok cool. I did wonder about that as when I looked in a file manager the permissions did not appear to have taken effect.

Are you presuming that it's not mounting because bolt_scripts is copied to the external card? If so then that's down to how the GS2 presents the mount point - mine is the same. I can "mount /sdcard" in CWM Recovery but flashing Thunderbolt! results in the bolt_script folder appearing on /sdcard/external_sd.
When I choose "mount /sdcard" in CWM, it says "unable to mount /sdcard", despite being able to install kernel zips from the sdcard via "choose zip from internal sdcard"
 
When I choose "mount /sdcard" in CWM, it says "unable to mount /sdcard", despite being able to install kernel zips from the sdcard via "choose zip from internal sdcard"

I had no such problems with v2.6.4, and I've just checked to ensure that it works as it should with v2.6.5 also.... it does. Tried reflashing the kernel?

Actually, I wonder if maybe running "Fix permissions" from the Advanced menu in CWM Recovery wouldn't be a good idea? Try that, then "reboot recovery" and see if /sdcard will now mount. If it's still a no-go then try reflashing the kernel. I take it you've no issues accessing files on the internal storage?
 
I don't think that Siyah 2.6.5 is going to do it for me I'm afraid. :(

Running with lulzactive + v(r). 100 -> 800MHz. Stock voltage. No tweaks or scripts.

12 hours on battery and I'm down to 30% already.

On 2.6.2 I was getting around 27 hours on a charge consistently.
 
I don't think that Siyah 2.6.5 is going to do it for me I'm afraid. :(

Running with lulzactive + v(r). 100 -> 800MHz. Stock voltage. No tweaks or scripts.

12 hours on battery and I'm down to 30% already.

On 2.6.2 I was getting around 27 hours on a charge consistently.

I know you love your lulzactive app, but ondemandx has been awesome on battery for me, even compared to 2.6.2, but I know im abnormal!
 
I know you love your lulzactive app, but ondemandx has been awesome on battery for me, even compared to 2.6.2

I used lulzactive + v(r) as a comparison to the N.E.A.K. kernel set-up I had. Like everyone else I guess, I'm after the best performance and battery combo. You do tend to find that certain kernels favour certain governors. I'll give ondemandx a go now.

I know im abnormal!

I'm saving that statement for posterity Syd. :D

EDIT

Cheers Syd!

ondemandx is a big improvement over lulzactive. :)
 
I don't think that Siyah 2.6.5 is going to do it for me I'm afraid. :(

Running with lulzactive + v(r). 100 -> 800MHz. Stock voltage. No tweaks or scripts.

12 hours on battery and I'm down to 30% already.

On 2.6.2 I was getting around 27 hours on a charge consistently.

True story! You are not alone.

Also going to give ondemandx a go now then.
 
There's something weird occurring with the lulzactive governor on certain configurations. Some users are reporting high battery drain, lag, freezes and crashes while others (myself included) have no issues.

A changelog for v2.6.6 is already up:


  • fixed the problem which is causing device turn on by itself when it is connected to a charger. (it was related with lulzactive changes in v2.6.5)
  • some more lulzactive changes
  • smoother “mr bones” playback in youtube
    icon_smile.gif
  • removed brazilianwax, interactivex, savagedzen and intellidemand governors.
  • fixed a nasty bug in interactive governor.
 
Cheers Slug!

I thought it was just me losing the plot with lulzactive in my post #965.

Don't feel quite so stupid now. :rolleyes:
 
Oh well, so much for my idea of an early(ish) night... only reason I'm still awake now is that the Virtuous devs released a third ICS beta for the DZ and I wanted to get it flashed before crashing.

Changelog (in addition to the above) is interesting:

  • default governor is set to lulzactive
  • default i/o scheduler is SIO
  • XZ compression (this is not a feature but an explanation for smaller kernel size. I am sorry that I had to give up LZO because it gives me >8MB kernel image which exceeds the available kernel partition size)
  • (Possible)Tegrak overclock app support. although you may customize all the features with scripts, some existing tegrak overclock app customers may prefer to use it.
 
Good morning Slug!

Kernels are getting to be like buses... none for awhile and then two come along, right after each other!

Am still playing with the new N.E.A.K. v1.3 kernel which is looking very good for me so far.

However... I am easily tempted by v2.6.6... :rolleyes:
 
Back
Top Bottom