Hello,
As i posted earlier FlyKernel-08 does work with MCR r5.
Unfortunately there are visual issues.
Spiky/jumpy/laggy screen when some process is using the CPU. What does it mean? Open your dialer, click an entry to dial, wait 2 seconds, reject the call, go to home screen and try to scroll left/right (launcher pro + sense observable). The home app either scrolls in a jumpy/laggy way or even misses a swipe, and that effect lasts at least 5-6 seconds. Seems like pinning the CPU to 576MHz solid (min and max freqs) reduces the issue, but doesn't eliminate it.
It's most irritating when the Android bootup itself - just after the launcher has started. Usually apps like htc email, gmail, facebook download and process data on boot and during that time the phone is really unusable with this kernel and MCR r5 - it lags/spikes that much. At least not for the first 2-3 minutes after the launcher/lock screen has started.
The problem is not present (means jumpiness is times less) on stock rooted kernel, nor Teknologist 2.0b, nor FlyKernel-04 or even stock VR12.
Unfortunately FlyKernel-04, just like VR-12, has issues with the framework which usually leads to system_server process restart time-to-time (2-8 hours). If you haven't seen it - it's like your phone restarts without showing the initial HERO logo - only the animation. Meanwhile you can be on ssh session to the phone while the Android virtual machine boots. For the linux backend the phone has never restarted
Anyway the second issue is quite weird and definately not a blocker. When the phone boots, just before it powers the launcher and the lock screen app, for few seconds the whole phone goes black (screen off) and also during that time the dropbear server closes my ssh session. It's either a module issue or related to the networking - the dropbear process itself never gets controlled (started/stopped) by the Android frontend.