Titan 20226 kitchen - Page 3

glintz · #21 (**permalink**) 07-14-2008, 11:46 AM

Here is a reg file with the standard button mappings (if you use the flashlight and voice command like I do

Unzip the file drop it on your phone and run it to add it to your registry.

Glintz

jhamilton · #22 (**permalink**) 07-14-2008, 12:20 PM

Looks like the button mapping problem is the same regardless of which ROM i build. Just tried 19588 and the buttons it has the same problem (worked fine yesterday). Something changed in the titan_drivers maybe?

dthames · #23 (**permalink**) 07-14-2008, 12:22 PM

Its the touchpal that is causing the problem. After reading gurus post I tried switching to touhpal 3.0 and it still caused the same problem. So I took it out altogether and it finally built correctly. Touchpal is definitely the problem.

justpctech · #24 (**permalink**) 07-14-2008, 12:23 PM

Yes button assignment is broken in 20226 and is being investigated now. The reg file that glintz posted will set them to standard button assignments or can be used to edit them to your liking until we get them fixed.

justpctech · #25 (**permalink**) 07-14-2008, 12:25 PM

Quote:

Originally Posted by dthames

Its the touchpal that is causing the problem. After reading gurus post I tried switching to touhpal 3.0 and it still caused the same problem. So I took it out altogether and it finally built correctly. Touchpal is definitely the problem.

Looks like the Diamond skin was culprit- the DSM needs to be zeroed out in the OEM to fix.

jminor · #26 (**permalink**) 07-14-2008, 01:03 PM

will someone kindly explain the difference between this 20226 kitchen, the 19588 kitchen and No2Chem 5067 Kitchen. I think they all run WM 6.1; is the Radio version different? What are the major differences.
Thanks

**colonel** · #27 (**permalink**) 07-14-2008, 01:08 PM

Yes, the dsm for the touchpal diamond skin had a bad UUID in it. You can delete the contents of this dsm safely for now.

If anyone else finds a different error, please explain and post your selections.txt or link it somewhere.

sdsoundguy2007 · #28 (**permalink**) 07-14-2008, 02:13 PM

Jminor it is a different build of the the operating system and drivers from what I can tell that is the major difference it is more up to date.

ViPaDawG · #29 (**permalink**) 07-14-2008, 02:48 PM

does anyone know why contacts with pictures dont sync with Activesync? i haven't encountered this problem with the 20 or so other roms i've flashed, but started happening with 19288 or whatever, and 20226 doesnt work. i deleted the original copies of the contacts from outlook, and created new ones on the phone, and resynced, so it had the new ones I made and that worked (this was on my 192xx rom) and so when i flashed to 20226, the new copies of the contacts didnt sync over. so I want to know why, i added those pictures so I can have them display on HTC Home, so it's dumb to not have my most used contacts not sync over. also what is weird, is that I flashed back to 5067 (which worked), and now they don't sync on that either.

ViPaDawG · #30 (**permalink**) 07-14-2008, 02:55 PM

also, when rebooting, the grey top bar shows up overlapping the Green Windows Mobile Screen, but the spacing is off (so the windows flag is in the top middle of the screen).

also, the today voicemail plugin doesnt work (i.e. select the OEM, but doesnt end up coming out in the cooked ROM).

also, i have to install the Titan KEYFIX in order to make my keys stop showing up as double (hello, how arre youu), so I was wondering if that was going to be fixed?

those are the only issues I saw in this rom, (as well as the activesync one above), but the two major ones that bug me are the AS contacts, and the Grey bar showing up early.

EDIT: I forgot about the random clicks and ticks that I get when using File Explorer or opening any program through the start menu. I dont know how to get rid of those (I checked the screen taps setting, and everything was unchecked, so it's not that, something built into the rom).