Sweet work - amazing that you're managing to work around your previous frustrations with this project!

abra cadabra - camera will work one day :)

the rest is your own abra cadabra magic to get a 300% decrease (or is it 200%? I can never think clearly in percentage math) in your boot time!!

So are we getting to the point where the only significant issue is the camera instability?

Cuz what your .35 kernel brings to the table it simply outstanding :)

faster boot confirmed go riemer go !
boot is indeed faster but now it takes age to wake up from lockscreen
doesn't even wake up now, had to restore

Originally Posted by keyra74

faster boot confirmed go riemer go !
boot is indeed faster but now it takes age to wake up from lockscreen
doesn't even wake up now, had to restore

I switched back to the completefair-sceduler(CFS), instead of the brain****-sceduler(BFS) in earlier builds.
When finally booted up, there is quite a high load generated by everything. I guess BFS put some extra cpu cycles into the GUI elements making the phone appearing more responsive. However the load is solved way quicker in the CFS one.

Still, I agree the first boot is kinda a long trip when the whole phone is fired up in CFS. I think this is due the fact SD-card IO operations take too long, do you have a lot of apps on the sd-card? (apps2sd, by script of froyo-style?).
Hope to tackle this problem in the future, so we can continue with CFS.

However when all fired up, CFS works better for me. With BFS I sometimes had the problem it didn't gave some CPU cycles to SetCPU, which in turn would increase the CPUfreq when I turn on the screen. So with BFS I couldn't unlock sometimes... :P

@dkelley, camera is currently one of the main issues aye. Still some more speed is always welcome, but the whole kernel is coming along quite good actually :)

yeah i have a bunch of apps installed with app2sd

Originally Posted by keyra74

yeah i have a bunch of apps installed with app2sd

I'll see what I can do

Originally Posted by riemervdzee

I switched back to the completefair-sceduler(CFS), instead of the brain****-sceduler(BFS) in earlier builds.
When finally booted up, there is quite a high load generated by everything. I guess BFS put some extra cpu cycles into the GUI elements making the phone appearing more responsive. However the load is solved way quicker in the CFS one.

Still, I agree the first boot is kinda a long trip when the whole phone is fired up in CFS. I think this is due the fact SD-card IO operations take too long, do you have a lot of apps on the sd-card? (apps2sd, by script of froyo-style?).
Hope to tackle this problem in the future, so we can continue with CFS.

However when all fired up, CFS works better for me. With BFS I sometimes had the problem it didn't gave some CPU cycles to SetCPU, which in turn would increase the CPUfreq when I turn on the screen. So with BFS I couldn't unlock sometimes... :P

@dkelley, camera is currently one of the main issues aye. Still some more speed is always welcome, but the whole kernel is coming along quite good actually :)

In the hero's BoardConfig.mk file, there is a definition as BOARD_USES_ECLAIR_LIBCAMERA := true
Shall we remove this definition to use froyo camara jni when compiling the rom ?

Originally Posted by sotux

In the hero's BoardConfig.mk file, there is a definition as BOARD_USES_ECLAIR_LIBCAMERA := true
Shall we remove this definition to use froyo camara jni when compiling the rom ?

I'm afraid that will break support with the closed-source HTC camera control library. Also the camera works with one picture at a time now (after picture, reboot hehe), so I guess it just needs a few kicks in the nuts to get it working
No need to switch bases/interfaces like you propose.

Originally Posted by riemervdzee

(...) the camera works with one picture at a time now (after picture, reboot hehe), so I guess it just needs a few kicks in the nuts to get it working (...)

Dunno if it helps, but this was the same first problem that came with making the camera work on Gingerbread until SteelBytes fixed the camera fully. One shot then the camera stoped working.

Originally Posted by Ciprilik

Dunno if it helps, but this was the same first problem that came with making the camera work on Gingerbread until SteelBytes fixed the camera fully. One shot then the camera stoped working.

I think I'm getting very close, I was able to take 6 pictures this morning. Then I tried to reopen the cam a few times and at the third time it went poof...
Gonna try it again a few times today.

I also noticed there is some wake-up problems when clocking too low. I prefer to have a screen off profile with 176-264 ondemand gov. Then it wakes up quite quickly. Other governors perform poorly though..

Originally Posted by riemervdzee

I think I'm getting very close, I was able to take 6 pictures this morning. Then I tried to reopen the cam a few times and at the third time it went poof...
Gonna try it again a few times today.

I also noticed there is some wake-up problems when clocking too low. I prefer to have a screen off profile with 176-264 ondemand gov. Then it wakes up quite quickly. Other governors perform poorly though..

With this kernel we can have working camera in Sense 2.2 roms like ChocolateFroyo ?