Develop Bugs

Slow Android 2.1

I've been experimenting with the Sense 2.1 VGA build of XDAndroid and after compiling it and copying it over I see that Android itself runs very sluggishly on my RAPH110.
Im using a 4GB HC Class 4 card.
Are there any ways that I can actually speed this thing up?
Ive used ATK and thats about it. Im out of ideas here.
Also: 1) Is there anyway to fix the backlight issue when coming out of sleep mode? (It stays at minimum brightness)
2) Is there anyway to transfer winmo contacts to XD?

howeasy said:
I've been experimenting with the Sense 2.1 VGA build of XDAndroid and after compiling it and copying it over I see that Android itself runs very sluggishly on my RAPH110.
Im using a 4GB HC Class 4 card.
Click to expand...
Click to collapse
AFAIK There's no XDAndroid build with HTC Sense in it. There's this but it's not part of the XDAndroid project, has fewer users and is (in my experience) updated less frequently. Click the banner in my sig to go to the XDAndroid thread - there's a new Eclair 2.1 build out which I'm yet to try. If that's slow, try the 2.0.1 build, which has none of the backlight issues you've mentioned. It shouldn't be slow, but if it is to you then it's just because you're used to Windows Mobile running very quickly on the device, and there's no way to get Android going that smoothly just yet.

You could try overclocking but it should be pretty speedy already. Is this your first build of Android? Have you deleted data.img and let it remake it. Try formatting your sd card.

ben_duder said:
AFAIK There's no XDAndroid build with HTC Sense in it. There's this but it's not part of the XDAndroid project, has fewer users and is (in my experience) updated less frequently. Click the banner in my sig to go to the XDAndroid thread - there's a new Eclair 2.1 build out which I'm yet to try. If that's slow, try the 2.0.1 build, which has none of the backlight issues you've mentioned. It shouldn't be slow, but if it is to you then it's just because you're used to Windows Mobile running very quickly on the device, and there's no way to get Android going that smoothly just yet.
Click to expand...
Click to collapse
That is indeed the build i'm currently using.
The official XDAndroid build of 2.1 would give me the endless fireworks screen even and updated zImage.
If there's a version that will work on my Fuze then please link me to it as I have been unable to track it down.
But regardless, I've been working on trying to get it to run faster, Ive had moderate luck using ATK but thats about it.
Im baffled as to why its running this slow.
Also, using the 2.0.1 build caused the phone not to send SMS messages, hence the reason I came looking for a new build and came across the Sense one.

Did you use the Fuze startup text instead of Raphael? Did you leave it long enough? On first boot my Raph100 takes about five minutes to start, but it's only about one minute after that.
Here's proof (if you want it) that it's normal for it to take ages to load on first boot.

ben_duder said:
Did you use the Fuze startup text instead of Raphael? Did you leave it long enough? On first boot my Raph100 takes about five minutes to start, but it's only about one minute after that.
Click to expand...
Click to collapse
Indeed I did. It simply played the Nexus one boot animation for a while, froze for around 5 seconds, and then went back and played the nexus one animation from the beginning.
The sense build im using works in all aspects other than the fact I would prefer the normal Android layout, I want it to run smoothly, and I want a more constantly updated version.
I used the Fuze startup text with and without the overclocking script thrown in.
I'd be more than willing to go at it again if its worth the shot.

I really recommend having another go: XDAndroid is exactly what you're looking for with regards to the lack of Sense and the frequent updates. There's no hardware-related reason why it shouldn't work on your Fuze, so delete everything from the build that's already on there, get the right startup.txt and give it a go

Thanks for the positive reinforcement!
If you could possibly directly link me to the 2.1 build you'd personally recommend that would be appreciated.
Ive been trying a build for the RAPH800 that was linked to in your sig and its giving me to the same problem I described earlier.
I have the RAPH110, as you know, but the RAPH800 build was the closest thing I could track down.

Eh? Don't use the 800 unless your phone is CDMA. Just download the 2.1 bundle for the normal Raphael, the link is just under the changelog. I'm giving it a go right now and I'm currently waiting for it to boot, I'll tell you if I have any problems.

ben_duder said:
Eh? Don't use the 800 unless your phone is CDMA. Just download the 2.1 bundle for the normal Raphael, the link is just under the changelog. I'm giving it a go right now and I'm currently waiting for it to boot, I'll tell you if I have any problems.
Click to expand...
Click to collapse
Oopsy! I had a hard time tracking that down.
Im using the one labeled "03.05.10 | 2.1 builds". Is that correct?
It also says it already has the lastest zImage that should work so do I need to go update that?
I swear, if there was a super mega +rep button i'd press it.
You're what support forums are all about <3
(3:42PM: Just calibrated touch screen)

Yep, that's the one I'm trying. I've had some experience with the 2.0.1 but I've never actually used this build before, so it's possible there's something missing that I don't know about.
Haha thanks, although there are much nicer and more knowledgeable people on here than me

Well you're the one putting forth the effort to help a guy in need, so I truly do appreciate it.
I'm still getting the constant Nexus one boot animation sadly enough.
Maybe I'll go test out the 2.0.1 build and see if I can get that one to work, but like I said earlier, I had SMS issues with that one.
EDIT: I was able to get the 2.0.1 build working with SMS after zImage and etc..
Going to test sound and whatnot now and come back with another edit to verify.
I would still like the 2.1 build though but this might have to suffice.

Okay, I've just been messing with the 2.1 build and couldn't get it working either. I checked my startup.txt and noticed that set mtype was on the same line as set ram size, so I'm deleting my data.img and trying again.
Edit: It worked! No more boot animation

ben_duder said:
Okay, I've just been messing with the 2.1 build and couldn't get it working either. I checked my startup.txt and noticed that set mtype was on the same line as set ram size, so I'm deleting my data.img and trying again.
Edit: It worked! No more boot animation
Click to expand...
Click to collapse
AWESOME!
Mind uploading whatever it is you did and tell me what I have to do to get the same result?
Sorry, Im still pretty new to this whole thing.

I won't upload it, but just check your startup.txt and there should be two lines of text that look like they should be separated. Press return just before the second, save it and delete your data.img file. Then run HaRET again and it should work fine.

You have to try this build - it's brilliant.

Well I suppose I'll have to give that a shot.
I found and edited the lines and also threw in the overclocking script.
After deleting the data.img Im giving it one last shot now.
If that doesnt seem to work then I'll just deal with the 2.0.1 build until I find a way to get this to work.
EDIT: anddddd, no such luck.
Guess I'm left to stick with 2.0.1 for now, it was running pretty fast as well.
So if anyone reading this gets 2.1 working please feel free to post.
Is there a way to get Android on the phone itself rather than SD? I'd love to ditch Winmo and save some battery life here.

Shame... I can't understand how it's not working now. All I did was edit the startup.txt, delete my data.img and try again, then wait for ages while everything loaded. If you're not sure if you've edited your startup right you can try using the one that works for you with 2.0.1.
As for not having to use the SD, that would require NAND flashing, which has some way to go before we can use it on our Touch Pros to replace Windows Mobile. There's a thread about it here. There are dual-booting and light WM ROMs designed for XDAndroid users, however.

In case you don't believe me
Sent from my AOSP on XDANDROID MSM using the XDA mobile application powered by Tapatalk

Did you happen to update the zImage or anything or did you just copy and paste and throw in the startup?

Best Android

Hi All,
Been looking around, (ive tried android on my kaiser once), and just wondered what is the best (most stable) android for kaiser, as a lot of them seem to have a lot under "not working"?
Thanks,
Tom,

Kinda hard to answer, since no one Android build has anything working 100%.
Myn’s Warm Donut will get you most of your stuff working, but there's still a lot of bugs.
Incubus26Jc's Super Eclair is pretty good, but you lose out on Camera and Bluetooth. Less bugs then Donut, but more stable IMO.

Although Polyrhythmic hasn't updated his 2.1D for a while, I still think it's the best of the eclairs. For Donut, Myn's is really the only game in town.
Eclair is still struggling with non-working camera, but GPS , WiFi, and BT are working reasonably well, if you are prepared to invest some time into hunting out the best combination of nbh and build.
Donut is reasonably complete, I have had Myns working with WiFi, GPS and Camera, or GPS, BT and Camera, but never managed all working at once, it is the most feature-complete and arguably the most stable build of all.
Given that we have only had Android on our kaisers since the end of last year, I still think that all the devs have done a remarkable job, and development continues.
Compared to the start of the year, when all that was possible was running from SD, with battery life measured in minutes, no wifi, gps, bt or camera, I think what we have now is a complete OS, it's been my everyday phone OS now for months, and once you get into a few good habits, it's stable and smooth, with decent battery life.

Thanks for replies guys,
I have installed Myn’s Warm Donut, but it seems the graphics are a bit weird, they seem like they are the wrong bit depth or something, not quite sure how to describe it.
Any help on this please?
Thanks,
Tom

XCougar said:
Thanks for replies guys,
I have installed Myn’s Warm Donut, but it seems the graphics are a bit weird, they seem like they are the wrong bit depth or something, not quite sure how to describe it.
Any help on this please?
Thanks,
Tom
Click to expand...
Click to collapse
Q: I installed Android but now everything is blurry.
A: It's due to wrong resolution. Kaiser phones have panel for 230x320 but you're probably using 320x480 build. Here is a post by user tatnai where he explains this situation for Vogue devices (it goes same for Kaiser).
Android FAQ: http://forum.xda-developers.com/showthread.php?t=683644
Click to expand...
Click to collapse
Myn's Warm Donut is basically a scaled down version of 320x480 resolution to fit 230x320 panels, with 110 density, hence the blurriness.
One build with native 230x320 I like is vilord's Tattoo Sense, but there is a camera and BT audio not working problem in that build - hopefully incubus26jc's next release will fix this.

milanche said:
Myn's Warm Donut is basically a scaled down version of 320x480 resolution to fit 230x320 panels, with 110 density, hence the blurriness.
One build with native 230x320 I like is vilord's Tattoo Sense, but there is a camera and BT audio not working problem in that build - hopefully incubus26jc's next release will fix this.
Click to expand...
Click to collapse
vilord's Tattoo Sense sounds pretty good, and it has rosie which I'd love to see working stable. I think I'll try this on the weekend, but just wanted to know, has anyone tried this? is it stable and/or fast? Its for the touch, but as far as I've seen, vogue builds work for kaiser... would this work too?

milanche said:
Myn's Warm Donut is basically a scaled down version of 320x480 resolution to fit 230x320 panels, with 110 density, hence the blurriness.
One build with native 230x320 I like is vilord's Tattoo Sense, but there is a camera and BT audio not working problem in that build - hopefully incubus26jc's next release will fix this.
Click to expand...
Click to collapse
Hi, thanks for reply, not that I don't believe you, but its not so much blurryness, there are pink and green bits everywhere? Or is this what your describing?
Thanks again,

Oh thats because you´ve choosed a wrong paneltype. Kaiser was built with 3 different Panels so you have to choose the right one. Look at the second sticky thread.

xPreSiDenT said:
vilord's Tattoo Sense sounds pretty good, and it has rosie which I'd love to see working stable. I think I'll try this on the weekend, but just wanted to know, has anyone tried this? is it stable and/or fast? Its for the touch, but as far as I've seen, vogue builds work for kaiser... would this work too?
Click to expand...
Click to collapse
I've tried it and believe it's the best Android build so far, despite BT and Camera problem (which we should be able to fix as it is Donut 1.6 Android).
For Kaiser you should use kallt_kaffe's update to get Wifi working and it also fixes Rosie and Market.

Thanks for info.
Ok please dont flame me, ive looked around and I used to flash windows mobile all the time, but I really dont understand these nbh files.
What are they, what do they do, why are there different ones e.g voguimg.nbh and kaisimg.nbh and polimg.nbh
Thanks for your patience with me

XCougar said:
Thanks for info.
Ok please dont flame me, ive looked around and I used to flash windows mobile all the time, but I really dont understand these nbh files.
What are they, what do they do, why are there different ones e.g voguimg.nbh and kaisimg.nbh and polimg.nbh
Thanks for your patience with me
Click to expand...
Click to collapse
VOGUIMG is for Vogue devices, POLAIMG is for Polaris devices and KAISIMG is for Kaiser. Think of them as some sort of bootloaders for Android. You flash the NBH, boot to the install console, install Android from SD to NAND/SD/EXT2 and boot Android. Also you have to choose the correct panel to avoid screen problems you're having. The only way to see which panel are you using on Kaiser is to test all three of them and see which one doesn't cause you screen problems.
To test which panel you're using you should first make an SD install with Haret, there you have the option to specifiy panel type in the config file default.txt and can change this before every boot. With NAND this is hard-coded into NBH file. Later you can flash to NAND if you decide to stick with Android.
Please go thru this Q/A topic, it should help you get the answers to most of newbie-type questions.

I´m not a developer and especially on android i´m a noob but i think the NBH contains all what is going to be flashed into nand. In case of WiMo it´s the whole Operating system, somtimes with radio too. In case of android the NBH contains the Kernel only. The kernel is designed for your device with all the drivers you need (touchscreen, wifi, BT, GPS, etc.). so kernels from other devices may not work becaus of other hardware specs. in worst case it may brick your device. I read alot before i flashed my kaiser an kallt_kaffe´s kernel seems to be the best for now. Nearly all funktions are available. Only the Camera have a bug, but i think it only takes only a little time to fix this too.
I use kallt_kaffe´s kernel and Myn´s Warm Donut RLS5 and i´m totally happy with it. Fingerfriendly (you´ll never need your stylus again except for reset ^^), and much more responsive then the fastest WiMo ROMs.
You only have to modify the nbh for your panel type. But you only can do trial & error to find out which type you have.
So... happy flashing.

Thanks everyone for your help, I have the tattoo sense rom on my phone now, my phone uses panel2 type of kaiser nbh.
I now understand the nbh better.
As im more then likely going to upgrade to a newer android rom when more stable ones come out, can anyone recommend a android application that will allow me to backup my txts, emails, contacts, and settings, etc.
Thanks all

[Q] Can I run Froyo on my HTC Kasier?

Can I Run it using Haret?
I dont wanna install it.

Absolutely!!!!
I have been playing with Froyo on my Kaiser for weeks and loving it...I've always flashed to Nand, not worrying to much about putting winmo back on the device (but believe me, you won't want to) Just search this forum, there are excellent devs and tutorials on running Android from SD using Haret and flashing via Hardspl....Ive tried many ROM's and can recommend Icubus' Super Froyo RLS12 and Milanches Cyanogen mod 6 for Kaiser RLS4....
Id start here:
http://forum.xda-developers.com/showthread.php?t=680518
Then check out these two links:
http://forum.xda-developers.com/showthread.php?t=712310
http://forum.xda-developers.com/showthread.php?t=732040
XDA is truly the cutting edge for Mobile phone development....You have come to the right place...
All the credit goes to the genius of the many devs on this forum....

Does the camera,GPS and blutooth work?
Does the camera,GPS and blutooth work?

yes it works

Yes you most certainly can I am running CyanogemMod6 on mine quite happily, everything seems to work just fine. Enjoy.

Leona, got 1 question here, i've been a loyal dzo's fresh froyo, so far my favourite distro less hiccup no restart, but still the camera doesn't improve much, dark picture, how is camera on cyanogenmod6 doing? in terms of picture quality and brightness.
Thanks.
Kaiser 130 (panel 2)
radio/spl: 1.71* / 3.34
Dzo's fresh froyo 26-07 (Nand)

akmalxxx said:
Leona, got 1 question here, i've been a loyal dzo's fresh froyo, so far my favourite distro less hiccup no restart, but still the camera doesn't improve much, dark picture, how is camera on cyanogenmod6 doing? in terms of picture quality and brightness.
Thanks.
Kaiser 130 (panel 2)
radio/spl: 1.71* / 3.34
Dzo's fresh froyo 26-07 (Nand)
Click to expand...
Click to collapse
Hi Akmalxxx, I am possibly not the best person to ask that, since my sight isn't great, all I can tell you is that the camera works, seems the same as other builds I have tried.
Now as I understand it, cyanogenmod6 uses the same zImage as Fresh, (dzo's latest 26-07-10) so I would assume/expect that the camera would be the same?

oh i totally forgot about the kernel, thanks for the clarification, guess i should wait for new kernels.

Sorry, this video cannot be played

Alright, guys. I've been searching for an answer to this problem for about 2 weeks now and I can't find a great answer.
I converted my AT&T Tilt to Android successfully and I've been trying out a series of different ROMs to find the one that works the best for me. Currently, I am running 2.6.32_VOGUIMG-320-FROYO-01-16-11.NBH from l1q1d with barebones 5.1. However, I have tryied Incubus's Super Froyo, Myn's Warm Donut, etc. I've been very happy with most of the builds; however, I have problems playing video in every single release of Android that I have tried. This includes through Android's included movie player, Meridian, and the youtube app. I am using panel type 2 when I reconfigure the kernal using atools. I don't know if this is the correct panel type, as I don't know how to figure out which one I have. I don't know if this makes a difference for video.
Does anyone have any suggestions about how I could get video working in Android on my phone? It's the last missing link in getting my phone to work the way I want. Thanks.

Seriously. No one else has experienced this problem? I've literally spent hours searching XDA trying to find a solution.

Youtube works on mine... tell you what. Flash the nbh with panel type 1.
Even if you get screen artifacts, or other issues, try the video. If you can play, then you've isolated the problem to the panel type. If not... oh well.
I'll try meridian and see what i get.

Just out of curiosity, I tried flashing it with all three different panel types; same results. I have overclocked to 520 mhz; would this cause any problems? Every other program seems to work fine. I'm honestly baffled.

Via Atools or RogueTools ?

Via atools. Thanks.

Do not OC via Atools. Might not have nothing to do with it, but RogueTools seems MUCH more stable. Just and advice

Removing the overclocking from atools has not made any difference. Thanks for the suggestion, though.

Same problem. I managed to play some videos with poor quality, so maybe this is a performance related problem.

Looks like it's back to WM for me. The lack of video is a dealbreaker for me. Sorry that you're having the same issue, sloikas. Windows plays everything I've thrown at it.

Back to the dark ages on our kaisers lol? What may be affecting your video playback is the radio rom. It actually contains a little more than the radio and in my experience can affect playback of videos. Also if your trying to stream over edge, good luck with that. Over wifi I have next to no issues with Barebones 4.55, overclocked to 575 mhz and on wifi.

Thanks for the reply. Just out of curiosity, I tried three different radios: 1.70.18.02, 1.70.19.09, and 1.71.09.01. Same results with each of them. I don't have a data connection with my phone, so I am only using wifi. I have also tried to play MP4's on my SD card.

Video is supposed to be working. How exactly do you have it set up atm?

erickrause01 said:
Alright, guys. I've been searching for an answer to this problem for about 2 weeks now and I can't find a great answer.
I converted my AT&T Tilt to Android successfully and I've been trying out a series of different ROMs to find the one that works the best for me. Currently, I am running 2.6.32_VOGUIMG-320-FROYO-01-16-11.NBH from l1q1d with barebones 5.1. However, I have tryied Incubus's Super Froyo, Myn's Warm Donut, etc. I've been very happy with most of the builds; however, I have problems playing video in every single release of Android that I have tried. This includes through Android's included movie player, Meridian, and the youtube app. I am using panel type 2 when I reconfigure the kernal using atools. I don't know if this is the correct panel type, as I don't know how to figure out which one I have. I don't know if this makes a difference for video.
Does anyone have any suggestions about how I could get video working in Android on my phone? It's the last missing link in getting my phone to work the way I want. Thanks.
Click to expand...
Click to collapse
use KAISIMG, And mind that you need a corresponding kernel. Atools is creating problems for me in editing the kernels. I suggest you try a stock kernel with respective build. (FROYO kernel for FROYO, Eclair kernel for Eclair and Donut's for Donut). So far, Meridian is the best media player for me and I am using it on Donut (Warbyte's or Myn's ? your choice).
To check which panel type is nice and good is to check your SCREEN's colours. Are they perfect? is Touchscreen working good? and is brightness set good. First thing you notice after flashing wrong panel type is colours. Deformed Colours, usually u see each pixel as showing rainbows.
Flash a KAISIMG kernel I say and do not play with them on Atools / iHex or what so ever.
For instance try this,
http://phobos-lab.net/android/Warbyte Donut RLS04.zip
kernel is included and panel type is set to 1, Device keyboard is set to HTC Kaiser default. I say use iHex to edit the nbh for your suited panel type/keyboard.
Installing Data on SD Card can cause browsers to malfunction and almost Force Close on anything. Try installing on NAND (both SYS and DATA)

erickrause01 said:
Alright, guys. I've been searching for an answer to this problem for about 2 weeks now and I can't find a great answer.
I converted my AT&T Tilt to Android successfully and I've been trying out a series of different ROMs to find the one that works the best for me. Currently, I am running 2.6.32_VOGUIMG-320-FROYO-01-16-11.NBH from l1q1d with barebones 5.1. However, I have tryied Incubus's Super Froyo, Myn's Warm Donut, etc. I've been very happy with most of the builds; however, I have problems playing video in every single release of Android that I have tried. This includes through Android's included movie player, Meridian, and the youtube app. I am using panel type 2 when I reconfigure the kernal using atools. I don't know if this is the correct panel type, as I don't know how to figure out which one I have. I don't know if this makes a difference for video.
Does anyone have any suggestions about how I could get video working in Android on my phone? It's the last missing link in getting my phone to work the way I want. Thanks.
Click to expand...
Click to collapse
To play video, convert your clips/video to mp4 and use yxplayer to play them. This was the only working solution for video issues for me. Now I can play any video as long as it's in mp4 format and i'm using yxplayer to play it.
About youtube...are you on WIFI or mobile net? Youtube on wifi defaults to HQ video which our kaisers cannot play for some reason. Solution use 3G/H or if you're on wifi .......when the clip is loading click a HQ icon on the screen it should be in the right upper corner on the screen(depending on youtube app. version) that should load LQ/MQ version which plays fine on kaiser.

Thanks so much to dark_prince. His instructions worked perfectly for me. I now have a perfectly working (for me) Android phone. Awesome! Thanks to all that tried to assist.

Was just curious as to what build you were using. It basically sounded like he said to use a vanilla build with atools edit'd for whatever build you are going to use. I hate Donut just due to how old and slow it is. I do not think the build you are using matters, it sounds like you had a kernel configuration problem if it is now working.

erickrause01 said:
Thanks so much to dark_prince. His instructions worked perfectly for me. I now have a perfectly working (for me) Android phone. Awesome! Thanks to all that tried to assist.
Click to expand...
Click to collapse
I am glad that I was of to good use for humanity.
Cheers mate
aceoyame said:
Was just curious as to what build you were using. It basically sounded like he said to use a vanilla build with atools edit'd for whatever build you are going to use. I hate Donut just due to how old and slow it is. I do not think the build you are using matters, it sounds like you had a kernel configuration problem if it is now working.
Click to expand...
Click to collapse
for OLD I might agree. But for SLOW I wont ever. Donut is far far far far far far better than those eclairs or froyos out there. Particularly when my battery lasts for a day on Eclair / Froyo, it lasts for almost 48 hours crisp while using Donut. So please sir...

Well its like I said before, it is really the kernel that is making battery last longer. My barebones with a proper .32 kernel (Still waiting for clemsyn's .32 to be committed to git) and stock speeds is plenty fast and gets almost equal battery with more features and apps. I of course could overclock it but that drops battery to around a day which is more than adequate.

video doesn't work for me either....
I have VOGUIMG-320-FROYO-01-16-11 changed to kaiser and to panel 2 with atools... CM 6.1 barebones build both sys and data on nand... and is working really fine ( is the only one i've tried... )
already installed meridian and rockplayerbass the best i could get was with rockplayerbass with software render but the image was very ver slow... =(
erickrause01 , did you installed only kernel or entire build that dark_prince advised? and did you changed panel? what is the difference to change panel with atools and ihex? ( dunno how to use it ;P but if necessary will learn...
If only the kernel is needed to be changed, if i install new kernel do my installed build be ok or the process is re-installing kernel and then build again? i'm still with this doubt...
I would like to stay with this build because almost everything is running fine... little by little i'm getting my android to "perfection" hehe although some apps aren't working i'm finding solutions for almost everything.. video and camera is not one of that .. yet ;P
sorry for the bad english ;P
edit: when installing kernel i've changed name to KAISIMG
edit2: build is Scoot CyanogenMod 6.1 RLS5.5 not barebones....

[Q] Display Artifacts

After searching the forums and installing different kernel versions and quite a few froyo roms, I have found android to run very well on my kaiser. One thing really bugs me though and would prevent me from using this as a day to day OS: All over the place there seem to be artifacts, pixels that do not belong there. It really does break the overall look and feel of the system. Does anyone have an solution for this?
Yes i did search, it might be that my phrases arent correct. I just cant seem to find an existing solution for this. It has to be a display module problem, since it happens on every single rom I tested.
Thanks in advance

Sounds like you have selected the wrong panel type in the kernel.
Kaiser's were shipped with 3 different panels over the production time, you will need to play around and see whether yours works best set as 1,2,3 with atools.

Since i dont have a linux pc available right now, i opted for a kernel that was already set to panel 2. Would be really cool if the community could upload version for all 3 types. Thanks for the pointer. I might just create 3 kernels and upload them to share.

you don't have to run a linux pc to use atools to edit kernels
http://forum.xda-developers.com/showthread.php?t=783514

Yeah i havent had time to test it, I have 2 linux machines running at home. Although this line kinda made me not test it under windows:
"If you are a stupid windows user you can't use it so don't ask!"
Thanks a bunch dude

You're reading into that too much! I would assume that since you figured out how to get Android on your Kaiser you aren't stupid. There are different kinds of windows users, stupid ones, smart ones, etc.
I'm also going to assume that because you also use linux you probably aren't the stupid windows user. I use atools on windows and it works great. Try a different LCD type, it should fix your issues (although I still get some weird artifacts with both type 2 and 3 on some kernels and type 1 never works).

Okay I managed to get the problem sorted out using atools and selecting Panel 3. Now I have a booting 2.6.32 kernel, no artifacts. Rom seems a little sluggish, but I am sure if i fiddle with the kernel enough, it should show some speed improvements. Thanks for the help guys, makes me remember why I loved this place and my htc's so much