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

Siyah Gingerbread kernel (v2.x)

ironass said:
Somebody get a bucket of water to throw over Slug!
Click to expand...

Nah, I'm over her now. Back in the day though I was a sucker for a trim figure swathed in Nomex. Two of them in a fire-breathing beast like the A1 was like Xmas!


I'm feeling the same way about smartassv2 with sio at the moment.
Click to expand...
It's only been 5h 45m so far but it looks very good. Time to break something.... let's see how it copes with a min of 100MHz. ;)

edit: "not well" is the answer. All was fine for a while, but eventually it wouldn't resume from sleep and needed a battery pull to restart. Ho hum! :D

edit#2: I've benched all available schedulers with AnTuTu against my default config e.g. 200/1200MHz, smartassv2, custom voltages. I changed the scheduler in my bootscript and rebooted each time, making no other changes; all the usual services ran as normal so as to keep the tests as representative of 'real-life' as possible. Only a single run was made with each scheduler but I still reckon the results are worthwhile.

SIO showed a small but definite advantage over VR in the CPU and database IO tests. Over all six tests the other scores hardly varied so I'm confident that the difference is a genuine one. The relevant scores were (scheduler: cpu int/cpu fp/db io):

sio 1648/1278/375
vr: 1647/1272/365
bfq: 1630/1278/360
cfq: 1642/1276/300
deadline: 1612/1224/340
noop: 1622/1258/235
 
Slug said:
SIO showed a small but definite advantage over VR in the CPU and database IO tests. Over all six tests the other scores hardly varied so I'm confident that the difference is a genuine one. The relevant scores were (scheduler: cpu int/cpu fp/db io):

sio 1648/1278/375
vr: 1647/1272/365
bfq: 1630/1278/360
cfq: 1642/1276/300
deadline: 1612/1224/340
noop: 1622/1258/235
Click to expand...

Very interesting!

After my very unscientific "gut" testing yesterday, I found that sio just had the edge over vr for me on the CheckROM 3.1.1.

Early results are that I'm getting a very good battery life on my, "average use" scale, with no spurious wakelocks and coma like deep sleep.

Also the Dynamic hotplug setting is working well in 2nd Core.

I'm left wondering now just how much more tweaking can be done by gokhanmoral on this kernel.
 
glad i haven't done my usual "tinker and see what happens" before understanding it then! although i suppose if i was to play with this bit of voltage control and messed things up, it would reset to original settings on reboot..........
 
If all else fails you could, before tinklering, select Voltage Control > GPU & Charging > Menu > Recovery instructions and place a, "vcremoveboot-CWM.zip" on your SD card as a precaution and, "get out of jail" card.
 
ironass said:
Very interesting!
Click to expand...

Dunno if it actually proves anything though. My results for RAM, graphics etc were consistent enough for any scheduler influence to be disregarded, so I propose that, with smartassv2, sio offers the best performance benefit. Whether that applies to other governors under similar conditions remains to be seen.

Sydney99 said:
does anyone alter the gpu control settings??
Click to expand...

I've experimented a bit. 400MHz required max voltage (1.2V), and setting the min/max to 400/400 resulted in screen freezes during the AnTuTu tests. I was able to cancel the test okay but it didn't like that setting. That's been my limit so far; I haven't looked at how the GPU reacts to undervolting yet.

I will also need to review my CPU settings before doing any more serious testing. Tried a couple of 1696MHz 'suicide runs' last night and both resulted in lockups and a seriously warm CPU. Something appears to have changed between 2.2RC3 and 2.2i as 1696@1400mV was stable previously. I don't want to futz with anything else until I've got the processor itself nailed.
 
2.2p now up. P for performance apparently. Downloading now.......

change log says same as 2.2i except tweak to conservative and on demand, so pointless unless you're using either of these I suppose
 
Well, I've installed it but can't see any real difference, for me, in performance.

2.2i (revised) was, for me, as smooth and snappy as this "p" version. Am using smartassv2 with sio, stock voltage and no profiles.

For my needs I would rather go for the "i" version and conserve battery as "p" does not appear to be as battery friendly.

Nice to have the choice though. :D

Will leave it on for awhile to see how much battery it uses.

Just re-read your post Sydney99. I suppose Conservative and ondemand are better but as I don't use them anyway it doesn't matter. Might as well leave it on now and see what happens with my preferred governor and scheduler.
 
Ah come on, I just got 2.2i yesterday! What's with the sudden affection for letters now? Obviously I'll pick the battery life over performance, since I don't notice a difference.

I like how they said 2.2i is supposed to have better battery :P
 
Performance didn't seem any better on p and I was losing 1% of battery every minute of browsing so back to i.
 
2.3 is now up.

changelog:

Changed auto-brightness levels again. this time, you’ll have lower brightness than stock in low-light conditions but maximum brightness level will be the same.
fixed auto-rooting problem
reverted back to old workqueue implementation
reverted memory allocator to SLAB
enabled cleancache
 
No wakelocks last night so that's looking good. But my battery took a bit of a dive when my reception cut out so I'm hoping that was a one off. Will keep it on for another day to see if the same happens tonight.
 
hawker said:
what problems did you have with v2.3 butty?
I've not had opportunity to go through it with a fine tooth comb as yet, but it seems very good for me so far.
Click to expand...

Sorry, I should have explained further.

2.3 was very jerky on my Launcher Pro 3D App Drawer using all governors and schedulers. Certainly, for me, not as smooth as 2.2i or p. Battery usage seemed to be about the same though. 2.2i is as smooth as silk. :D
 
ironass said:
Sorry, I should have explained further.

2.3 was very jerky on my Launcher Pro 3D App Drawer using all governors and schedulers. Certainly, for me, not as smooth as 2.2i or p. Battery usage seemed to be about the same though. 2.2i is as smooth as silk. :D
Click to expand...

No need to apologize old fruit! :)

It seems ok in that respect for me. Seems smooth on both TW4.5 and GoLauncher. I'm using conservative "out-of-the-box" currently, with no other tweaks or profiles whatsoever.

I will however put 2.2i back on and do more testing...
 
You must log in or register to reply here.
Back
Top Bottom