Introducing XDA:DevCon – A Conference For Developers By Developers
XDA Developers Android and Mobile Development Forum
Forgot your password?
 
Post Reply+
Tip us?
 
sh1nichi
Old
#1  
Junior Member - OP
Thanks Meter 0
Posts: 5
Join Date: Jul 2010
Default Keyboard problem in 6.5

Hi, guys. I am trying to cook my own ROM for wm6.5. The Problem is I can't change the default keyboard to another keyboard input. Editing the reg in [HKEY_CURRENT_USER\ControlPanel\Sip] to another keyboard input make the ROM not bootable. Installing SIPchanger also not solve the problem. Is there any other way to forcefully change the default keyboard input??
 
Farmer Ted
Old
(Last edited by Farmer Ted; 5th July 2010 at 04:42 PM.)
#2  
Senior Member
Thanks Meter 88
Posts: 2,372
Join Date: Nov 2008
You do it by changing the guid in the defaultIM reg key; you also need the clsid for the new sip. Let me say, I had a bitch of a time getting it to work w/ resco keyboard (worked fine w/ fnkbd). The key is to set the defaulIM key during customization, otherwise the rom won't boot. The skin files need to be installed before that key is loaded. With fnkbd, you'd just get an error when the welcomehead appeared (annoying) if the defaultIM was cooked in. But with Resco, you never see your bloody welcomehead. I'm not eve sure that the read letters appear on the splash screen.

I set the defaultIM during customization with a mortscript:

Code:
RegWriteString("HKCU","\ControlPanel\Sip","DefaultIM","{A070BE16-AD56-11D3-BC77-00C06C512035}")
It runs after the skin files are installed (also with a mortscript during customization). Again, it's important that the clsid for the keyboard is cooked in, otherwise the rom will brick when you soft reset it. Once the defaultIM is set, you don't need a sipchanger, and reboots are quick

Edit: it's always a good idea to put in all relevant info if you really want help. What keyboard? What sipchanger? What's your package look like? Did you make it yourself? Did you do it manually, or use a cab-2-oem type tool, which probably crapped everything up? My guess is that you used cab-2-oem, but that there was a setup.dll that installs the clsid for the keyboard, and you didn't get that reg key, so now your package doesn't work. I suspect this because it's weird that sipchange isn't working for you-this is probably because you don't have the clsid (you put the shortcut in Startup, right?). Cab-2-oem type deals are not a reliable method to make packages.
ROM: Retro ROM
Radio: 1.17.25.09
 
Post Reply+
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

report this ad
Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Go to top of page...