[Samsung Galaxy SL i9003] Erahgon:
Feedback - Tested the Hillbeast version of BCK:

So, I had the "opportunity" to revert from CM9 to stock ('twas time for a clean flash), so I decided to make it worth our while to test out how Linaro compares on this device and how the kernel works.

I tried the XXLE4 value pack Stock ROM, and after a few minutes, it was apparent that it was too laggy to be a good baseline. I proceeded again by flash over it (directly after H-mod BCK, no latona.pit this time) with XXKPU, which I had a good experience with the last time.

Flash path for clarity:

NOTE: I am coming from CM9 Alpha 7.

Latona.pit -> XXKPE (all files) -> XXLE4 -> Hillbeast BCK -> XXKPU -> Clean Cache, Wipe Data -> TEST -> BCK -> Clean Cache, Wipe Dalvik -> TEST -> Hillbeast BCK -> Clean Cache, Wipe Dalvik -> TEST.

PDA and PHONE are "I9003XXKPU", CSC is "I9003SERKPU".

Build Info: "Wed Feb 22 13:50:49 KST 2012"

NOTE: During these tests I was on Airplane mode, with Wifi enabled. These tests are taken STOCK, ODEXed ROM, without EXT4 conversion. Tested twice on each benchmark 'cause I had no time left and decided to keep the focus on CPU and GPU rather than on I/O speeds (hope I am right in this assumption). Hence I'm going to show the results of the second test only (and also I'm just that lazy... *sigh*).

System Pages (These are going to be the order for the following images as well):

Stock | BCK | H-BCK

1) Boot-up time from on-vibrate to lockscreen (fastest to slowest, non-scientific - so no msec count, not first boot after flash):

BCK 13 (~39 sec) < Stock (~40 sec) < H-BCK (~47 sec).

2) Here are the Quadrant Benchmarks (free edition):

3) Here are the AnTuTu Benchmarks (free edition):

4) Here are the CF-Bench Results (free edition):

Observations:

1) An odd thing I noticed is that when I booted up after flashing the H-BCK over XXLE4, All the command line displayed was "Android_" and nothing else.

Maybe you compiled H-BCK wrt XXLE4? After I flashed it over XXKPU, with and without clearing the cache, there was all sorts of messages displayed.

2) I actually had a slightly more complex way of flashing. Everytime I flashed a new kernel, I would let it boot, shut it down again, go into CWM, clear the above mentioned data, go into download mode, reflash the same kernel, and finally let it boot.

3) Shutdown and restart took longer on XXKPU than on XXLE4 oddly enough. This could be due to the kernel messages and errors.

4) The H-BCK kernel seems pretty stable on XXKPU.

5) As we can see, the results are better than stock (all except Quadrant... which I don't trust much anymore). However between BCK and H-BCK, there were don't seem to be any significant differences which errors cannot account for. More research is needed.

I'm gonna keep this device profile (XXKPU with bench tools and any other requested tools) as a CWM backup on my phone for easy switching so I can continue testing. So tell me if you need a few mass feasibility testers (note that my device is almost a year-and-a-half old, and been extensively used).

I will follow up with a test on XXLE4 after I get some sleep (Yes, those timestamps on the screenshots are in AM).

Hope this helped in some way.

Cheeers!