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

Siyah Gingerbread kernel (v2.x)

lulzactive is my governor of choice at the moment, with cfq I/O scheduler. It doesn't require a sleep profile as it automatically uses the minimum setting for screen off.

I did remove "performance" folder earlier that I installed a couple of days ago... as per hawkers post.

I've turned the screen off profile off for the time being as I'm out and about and its getting kind of annoying having to my phone on using recovery every time I want to use it. But will give it a test with lulzactive tomorrow. It won't be the performance zip causing the problems as I never had to install it.
 
Could this truly be the, "HOLY GRAIL", of kernels?

I'm going to say no. I've had loads of random freezes, black screens which can be fixed by locking and unlocking my phone, Swype doesn't auto capitalize anymore and when listening to music via Bluetooth there's about 10 second of silence between tracks. If I raise the volts anymore I'm back to stock. I guess nobody will get their hands on the holy grail of kernels as the rabbit will always bite your head off.

Ignore the auto capitalize but, its just kicked in again.
 
Why do I get the feeling that you're going to try and break it? :eek:

Am I that predictable? :D

Success already.... governor, scheduler and CPU voltages are now set at boot via script. Oh, and it doesn't like 1650MHz @ 1.325V - hard lockup as soon as I enabled core1 for a benchmark run.
 
Am I that predictable? :D

Success already.... governor, scheduler and CPU voltages are now set at boot via script. Oh, and it doesn't like 1650MHz @ 1.325V - hard lockup as soon as I enabled core1 for a benchmark run.

Yes... you are Stig.. sorry, Slug!

You are now getting into areas that I will quite willingly let you play with and await your deliberations.

I just figure that if this bad boy works for both Sydney99 and I... it can't be all bad.

Look forward to your u/v figures. :)
 
Not daft at all - see my earlier post. I was watching the 'expected location' all afternoon and it sneaked past me up the blind side unnoticed! :)

You are now getting into areas that I will quite willingly let you play with and await your deliberations.

I've run 1600MHz @ 1.325V countless times - it's my normal stable setting. I was interested to see if 50MHz would make any difference, and got my answer immediately. I'm guessing 1.325 is just inside the tolerance for my cpu, so I'll try 1.375 next time.

p.s. I'm not insane (no really, I'm not!), and have no intention of using such clocks daily. I just want to push the envelope a bit.
 
p.s. I'm not insane (no really, I'm not!), and have no intention of using such clocks daily. I just want to push the envelope a bit.

Its kind of annoying that you had to try. I just broke it without trying.:D I'm starting to know how Syd felt. How did you put up with it for so long Sydney? So I've gone back to the androidmeda tjk kernel for now and (enter explicit rooted here) does it feel smooth. I might have to try again tomorrow as I forgot to run the kernel cleaner first.
 
I did remove "performance" folder earlier that I installed a couple of days ago... as per hawkers post.

The clue was in the post. I'd been using voltage control but recently changed to set CPU but my voltage control boot settings were still in the folder. Deleted them and the browser lag has disappeared. Too early to say about the rest of them but I'm hoping. I've always had that problem, I get most of my best ideas when drunk but I always forget about them.:D Glad I didn't leave this one till the morning.
 
Tonight's best effort.... I got slightly higher and lower with this config, so this is an average.

medium.jpg


CPU: 1696MHz @ 1400mV (vs 1425mV stock. I reckon 1375mv is possible)
Scheduler: vr
Governor: performance (for obvious reasons!)
GPU clock: 267/400MHz (vs 160/267 stock)
GPU voltage: 950/1200mV (vs 950/1000mV stock)
busfreq_static = enabled (stock settings of 0 0 0 0 1 1 2 2)
 
The clue was in the post. I'd been using voltage control but recently changed to set CPU but my voltage control boot settings were still in the folder. Deleted them and the browser lag has disappeared. Too early to say about the rest of them but I'm hoping. I've always had that problem, I get most of my best ideas when drunk but I always forget about them.:D Glad I didn't leave this one till the morning.

:D:D:D

That caught me out the other day which is why I posted this:-

http://androidforums.com/3501091-post209.html

with "Tips for flashing a new kernel".

Drove me nuts until I found the problem.

Glad you're sorted now Shotgun84. :D
 
Then maybe I just need to be drunk to remember something I'd already read.:D I'm really hoping I missed that post as I actually felt clever for a while. Oh well easy come, easy go.

Actually, I'm beginning to believe that it has caught a few people out when flashing backwards and forwards between kernels and I wonder how many times it may have caused me problems.

Whether you read it or not... you still sorted it old boy! :D

Have another drink!
 
Did you throw a bucket of water over it after that benchmark

It's actually nothing to write home about - I've had over 7100 with just a 1600MHz o/c on previous beta releases - so I'm dubious about whether settings were "sticking". I used adb shell to echo the parameters, so that if it all went Pete Tong I wouldn't get locked out.

I now have an idea of the top-end limits, at least. Next is to see how far it will go the other way. "More work required", as my school teachers were fond of telling me. ;)
 
Actually, I'm beginning to believe that it has caught a few people out when flashing backwards and forwards between kernels and I wonder how many times it may have caused me problems.

Whether you read it or not... you still sorted it old boy! :D

Have another drink!

Don't worry about that one mate. I've already had one for you as well;)
 
Thanks. They didn't look too happy but talked them into topping it up. In the end I just had to mention ironass. Damn if you could taste this whiskey :eek:
 
Am I that predictable? :D

Success already.... governor, scheduler and CPU voltages are now set at boot via script. Oh, and it doesn't like 1650MHz @ 1.325V - hard lockup as soon as I enabled core1 for a benchmark run.

Have you written a custom frequency file for SetCPU, Slug...and how are you guys accessing I/O scheduling?

 
Back
Top Bottom