Just installed wym's warm eclair on my old Kaiser

Cool, thanks for your consideration. Should not have just addressed that request to Dark, my apologies

Dark is a very prominent member, the place wouldn't be the same without his help, though at the same time, it takes a viable effort from everyone to keep things running smooth an together around here so it's a group thing as always.

I think the gang is a go for this, just give us a day or so to put it together.



WR

@ Keithyv:
So I went ahead and switched to the Polymod 2.1 Eclair build - Sweet looking UI, very smooth, and Marketplace works perfect now   Rogue Tools overclocking my Tilt to 500mhz was helpful too.
(Still running off SD through HaRET)

Only remaining issues:
- Physical keyboard symbols are a little off - think this is fixable by editing default.txt script to indicate Tilt vs Kaiser - but not a big deal to me
- Camera is DOA, won't launch at all :-(
- BT is also DOA, but haven't tried the BT fix zImage yet
- Rogue Apps overclocking does not seem to survive restart.
- GPS cannot get fix - although to be fair I only gave it 5 minutes to try from cold start and, let's face it, the Tilt's GPS has always been retarded.
- Biggest Issue: Sleep/suspend still crashes to a LINUX console screen and phone freezes. DPI was set to 120 on install of the build.  UPDATE: Fixed by editing the pm.sleep command in the default.txt to suspend apps, screen off & wait for interrupt instead of the original suspend device command.

RC

Thanks for asking keithyv. Well, it's been interesting:

I went ahead and flashed the PolyMod 2.1d Eclair build to the phone to really give it a good try, replacing WinMo completely - MUCH smoother, faster and more stable after that than running off SD through HaRET.

- Got the camera to at least take 640x480 pics with no autofocus - good enough for snapping a pic of a license plate in case of an accident, etc.

- Got keyboard mapping set to "ATT_tilt" finally, instead of "HTC_kaiser" and physical keyboard was perfect.

- Bluetooth never did get sorted out - after using the latest Eclair kernel and image for Kaiser, I could enable it, pair with my headset, then all sound and mic would be killed - even after disconnecting the headset, turning off bluetooth and even removing the pairing - until I soft reset the phone.  

- GPS actually worked surprisingly well once I gave it TEN minutes to lock in the signal the first time. After that, would lock back in next time within 30-45 seconds (acceptable for a Tilt) and tracked very well.

Unfortunately, I made the mistake of letting someone else play with it - my fiancee is considering a Motorola Backflip to replace her Pantech that hates my eXpo, and wanted to try out Android first, so I let her have it for the weekend once it was as stable as I could get it. She installed "Farm Frenzy Lite" (one of those Diner Dash type games I guess) and it killed Android. Flat out killed it dead. Hard reset even, and still couldn't load the Linux kernel past about 3 seconds (loading system img) before it crashes to a white screen. Will have to re-flash the ROM via USB or  SD card (can still get tri-color bootloader screen at least).

Was fun while it lasted. Friggin' crapware game.  

RC

EDIT: Realized I never actually answered your question keithyv - I was liking Android enough that I went ahead and used my upgrade with AT&T and got the Samsung Captivate. Loving it so far. With the Expo and the Captivate, I feel like I'm dual-wielding the best WinMo and Android have to offer.  Like a .45 on one hip, and a 10mm on the other 

The only thing I would consider upgrading my expo for is a true multitouch screen.

Android I could take or leave.

Mind you the new samsung galaxy variants look like nice phones. The HTC Desire also looks like a decent product.

Not sure if I am going to switch to WP 7 when it comes out... I guess Ill wait and see what happens after its release.

That's sweet. It's an interesting device, would love to have a screen like that.

Has installing marketplace apps on the SD card ever worked on any android ROM? ANY FIX??? if so which ones?

which android kernel are people using? what is the significant difference of each? im using "kaisimg-panel2-320-tilt-froyo-26-07-10.nbh" is this recommended?

i had problems with the battery not charging properly and staying at 15% and then randomly freezing and restarting. ANY FIX???

wHAT Is Maps (brut)? I get a virus alert with wireless tether? how do i get original launcher? how do i get rogue tools to work (overclock), screen calibration does not work? barcode scanner does not work? Video playback seems glitchy. is there a fix for camera button?

What is the most solid, fast, reliable and stable android ROM out there for the Att Tilt in the southern california area?

im still using hardSPL 3.29 i cant get 3.34 to install properly...

Indeed Guy, that's a lot to throw out here - most of those question will have been asked and answered over on XDA - look under HTC Kaiser/Tilt forum, then Android Development sub-forum, then hunt down some FroYo threads.

As far as the kernel goes, that's the right panel type and resolution, so you're good there - whether that particular kernel works best on the Tilt specifically? Again, that's something to search out on XDA. Newest does not always equal most stable. FroYo is being problematic so far even for devices that were designed to use it, so porting to a Tilt? You're gonna see issues - that's just a given.

NO one - to my knowledge at least - has gotten the Tilt camera to do better than a 640x480 snapshot with Android - autofocus doesn't work and so naturally barcode scanning is not likely to work either. It just can't properly access the hardware controls.

Battery percentage being accurate has been an ongoing issue with all Android builds brought over to the Kaiser/Tilt. Different builds have had better success than others. Only one I found to be consistently accurate (+/- 5%) is the Polymod builds (search for it).

Um, Google Maps.
Probably your firewall. Can't help you there.
Original to what build? Way too vague a question.
Find it on Market and email the developer for help
Likely has to do with the build you're using
Again, likely due to build issues, maybe kernel
Maybe I'm missing something here, but what the heck does your geographical location have to do with anything??
search for KaiserUnlocker.

Hope that helps start you on your way to some of the basics.

Seriously though, do some reading and searching before posting questions like that on XDA - they'll flame you for those kind of vague questions and not at least posting what you've tried so far. Like, are you installing to the device, or running it off the SD? Etc. 

Just a friendly heads-up. 

RC