Has anyone experenced issues using the 'phonepad' text entry method that's listed with Transcriber?
I just had someone try the new 318 rom, and it loads down the phone and won't let you change it back - and doesn't seem to do anything.
I hadn't ever noticed before, let alone tried it...
More details:
New release of 318, using the attached black keyboard .mui.
Looks like that black keyboard is part of a larger package. Here's the installation cab for it, and it also fixes the phone pad issue. Thanks deviusdragger!
Do you also have the cab for only the black keyboard?
TheWizzard2203 said:
Do you also have the cab for only the black keyboard?
Click to expand...
Click to collapse
I don't...
but if you decide to try and build one, the .mui works by itself (ie it is the black keyboard) - but if you want to use the 'phone pad' entry method, you need the 'dark Phone Pad' cab.
thnx
thnx mattk_r for the phone pad CAB...
Related
Hi, I need some help here:
I have tried extracting tapres.dll from several WM6 releases.
However, they never seem to be correctly rebuild after dumping the ROMs.
Does anyone know a way to get hold of a Working tapres.dll (from WM6 !!!) ?
I have tried dumping rom's with itsme tools (viewimgfsf, rebuild module etc..), but the resources from the file are VERY strange..
I need this file because I am writing a new program to build dailerskins, But I want to resize the dailerbuttons.
Solved:
Raceit pointed me to the resource file:
tapres.dll.0409.mui
This one needs to be edited!!
Am working on it.
Thanks Raceit !!!
The problem now is in how to make WM6 to use the new tapres2.dll (and MUI file)
edit
Had to write a new dll, but succeeded:
http://forum.xda-developers.com/showthread.php?t=297530
I got this with viewimgfs.exe as well so I'm not sure it will be of any help to you. This is from the Orwells ROM.
Thanks, too bad I got the same results:
There are no dialogs to be edited..
So it's not (yet) possible to have a big button dailer.
I understand this is about the dialer, but for some reason my WM6 dialer wokrs fine, i can change the background and button graphics, however when i am prompted to enter my SIM pin code the number pad has the nasty white background and pink buttons etc... (as if there is no skin).
What .dll controls the dialpad and sim pin pad?! Could i be missing some graphics files?!?
mrvanx said:
I understand this is about the dialer, but for some reason my WM6 dialer wokrs fine, i can change the background and button graphics, however when i am prompted to enter my SIM pin code the number pad has the nasty white background and pink buttons etc... (as if there is no skin).
What .dll controls the dialpad and sim pin pad?! Could i be missing some graphics files?!?
Click to expand...
Click to collapse
Been a while since I messed with sim-pin pad..
Out of memory I believe that:
The background is created by cmdpad_land.gif cmdpad_port.gif (and square, but this is not used on wizard).
And the buttons are the NmBtnDn_Land.bmp and other nmbtb**etc** bmps.
[ for convenience I attached those ]
thanks sir, i added the graphics to the \windows folder but still no joy (im running on the hermes btw). could my .dll that refers to it have been corrupted?!
mrvanx said:
thanks sir, i added the graphics to the \windows folder but still no joy (im running on the hermes btw). could my .dll that refers to it have been corrupted?!
Click to expand...
Click to collapse
It sounds like an image problem. I'd uninstall any dialer skin you have running to get the default stuff back if you can. If that doesn't work try this. It's the same as the-equinoxe posted, but there are a few more files. (No offense the-equinoxe) Just trying to help. This should get all the dialer buttons and images back to normal.
LOL! i REALLY appreciate the help people but still no luck! :s could i have corrupted a .dll or registry value when the ROM was cooked?
Raceit said:
It sounds like an image problem. I'd uninstall any dialer skin you have running to get the default stuff back if you can. If that doesn't work try this. It's the same as the-equinoxe posted, but there are a few more files. (No offense the-equinoxe) Just trying to help. This should get all the dialer buttons and images back to normal.
Click to expand...
Click to collapse
None taken
I only posted the pin-pad images (out of memory, didn't find my notes), and left the dailerpad images out.
LOL! i REALLY appreciate the help people but still no luck! :s could i have corrupted a .dll or registry value when the ROM was cooked?
Click to expand...
Click to collapse
Could be, what changes have you performed while cooking the ROM?
Did you edit the grafics for the dailerpad while cooking of afterwards?
mrvanx said:
I understand this is about the dialer, but for some reason my WM6 dialer wokrs fine, i can change the background and button graphics, however when i am prompted to enter my SIM pin code the number pad has the nasty white background and pink buttons etc... (as if there is no skin).
What .dll controls the dialpad and sim pin pad?! Could i be missing some graphics files?!?
Click to expand...
Click to collapse
I've got same problem. I think that's a sort of TMobile skin and not a file missing problem.
All began after i installed http://forum.xda-developers.com/attachment.php?attachmentid=34670&d=1172649654
SpH1nX said:
I've got same problem. I think that's a sort of TMobile skin and not a file missing problem.
All began after i installed http://forum.xda-developers.com/attachment.php?attachmentid=34670&d=1172649654
Click to expand...
Click to collapse
The file you refer to is the smart dialer, and installing it without a skin gives the same result as my sim-pin pad has. but LOL yer it does look like a T-mobile skin. Just install a skin and it will work ok.
the-equinoxe said:
None taken
I only posted the pin-pad images (out of memory, didn't find my notes), and left the dailerpad images out.
Could be, what changes have you performed while cooking the ROM?
Did you edit the grafics for the dailerpad while cooking of afterwards?
Click to expand...
Click to collapse
Well the first ROM worked fine, the black WM6 dialer and pin-pad looked the same, by copying the files from this post into the windows folder the colours and graphics for both the dialer and pin-pad were changed?!? (as desired)
But after the ROM change the pin-pad is white with no buttons. adding the files again to windows only changes the dialer. :s
AFAIK nothing has been done to the dialer skin, however it may have been changed by accident!? Which is why Im wondering which .dlls and reg values effect these?!
SOLVED
Raceit pointed me to the resource file:
tapres.dll.0409.mui
This one needs to be edited!!
Thanks Raceit !!!
Could you explain how to fix that skinning problem?
SpH1nX said:
Could you explain how to fix that skinning problem?
Click to expand...
Click to collapse
I am testing/working on it @ this moment..
All looks promissing but please be patient, don't want to rush out a release.
Only difference with the eten/paulyA skins is you edit another file, some regkeys are differrent, and the smartdail is build into the same resource.
Will build a test-skin (based on the Eten-grey Light I build for WM5), and do some test.
I will also build my findings in the WM6 dailerskin-builder program I am working on.
This one is still in the early development fase, and not all screens have been skinned.
Status:
-editing NEW resource Had to write my own dll, Done
-Dailer portrait Done
-Dailer landscape Done
-Call in progress portrait In progress
-Call in progress landscape In progress
-Button templates In progress
This program will be WM6 WWE QVGA only, but I will probably add some other languages once those are released.
Attached:
-a screenshot from the skinbuilder (although I am thinking to change the layout, because the troubles I have with switching to landscape and control-placement)..
Clicking on the screen will let you select the background picture
You can choose the buttonset (here used "test" ) with the dropdown menu.
You can change the transparancy of the buttonset with the slider.
And build a cab by clicking a button..
Sorry i didn't wanna bother you. I'll wait. Absolutely no probs...
Still having troubles applying the new tapres.dll
Replacing the XIP based tapres.dll crashes the dailer..
Then I tried to use the tapres.dll (plus MUI) as skin
So I renamed the dll and Mui to tapres2
and edited the registry:
[HKEY_CURRENT_USER\ControlPanel\Phone]
"IcoFil"="tapres2.dll"
[HKEY_LOCAL_MACHINE\Security\Phone\Skin]
"Enabled"=dword:00000001
"ext"="tapres2.dll"
[HKEY_LOCAL_MACHINE\ControlPanel\Phone]
"RESDLL"="tapres2.dll"
To no avail, still the old tapres.dll takes over
What am I missing??
EDIT:
OK I had to build a new dll.
Started from scratch, but now I have Big Buttons and Smartdailing Working
New thread is here
http://forum.xda-developers.com/showthread.php?t=297530
Classic Reading.
I think MrVanx would also like to see this one back someday.
I even remember myself finding out that there needed to be a phcanXXXETC.dll and a specific registry key to get a skinned unluck screen.
I'm closing the thread, but will never remove this.
I've updated the Tilt keyboard fix to address the apparent issue with the Smartdialer keys also being incorrectly mapped when flashing a non AT&T ROM onto the Tilt. This will also fix the FN character issues being incorrectly mapped too.
This was tested on a Tilt flashed with the (current) HTC ROM and worked perfectly.
Install -> Soft Reset
Enjoy!
IMPORTANT:
Some people have reported that this cab didn't fix their Smartdialer issue. It's important that you uninstall the older cab that was posted here (if you even installed it), then soft reset. Then install the new one and soft reset one more time. That should do it.
Do not unzip/decompress this .cab file on your desktop and move the files over to your device. It won't work. You need to copy the .cab (as is) onto your device and tap to install.
Great job thx.
Thanks!
This is great! Any tips on how to accomplish the reverse...if someone say, wanted to put the Tilt ROM on their Kaiser?
roameo said:
This is great! Any tips on how to accomplish the reverse...if someone say, wanted to put the Tilt ROM on their Kaiser?
Click to expand...
Click to collapse
Remove the registry key and soft-reset.
Code:
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\KEYBD]
"CWSLayout"=dword:00000001
roameo said:
This is great! Any tips on how to accomplish the reverse...if someone say, wanted to put the Tilt ROM on their Kaiser?
Click to expand...
Click to collapse
You "should" be able to just navigate to:
HKLM\HARDWARE\DEVICEMAP\KEYBD and delete CWSLayout, then soft-reset.
EDIT: Dang, Pof beat me to it.
Awesome. Thanks guys!
gret work
i got the tilt at 12 today and took it home and startedripping it apart, I put the htc rom on with msvc 1.6, live search, the nice battery icon and the home plug-in customizer, thats it, on my hermes i needed so maney things to make it function, i like the tilt now that the keyboard is fixed.
damn i can not edit the title, well crap
Excellent Work
TaurusBullba said:
This was created by myself and sirsycho. This will fix the FN character issues when flashing a non-ATT carrier ROM on the Tilt.
Install -> Soft Reset
Enjoy!
Click to expand...
Click to collapse
What exactly does it do?
Thanks,
g
gregross said:
What exactly does it do?
Thanks,
g
Click to expand...
Click to collapse
When you flash the HTC ROM (or any non-ATT ROM) onto the ATT Tilt, some of the alternate (FN) characters on the keyboard are mapped incorrectly. This fixes that.
TaurusBullba said:
When you flash the HTC ROM (or any non-ATT ROM) onto the ATT Tilt, some of the alternate (FN) characters on the keyboard are mapped incorrectly. This fixes that.
Click to expand...
Click to collapse
oh ok - thanks. Is that a registry update?
Was curious becuase i couldn't find and "...\qwerty" entries in the registry.
gregross said:
oh ok - thanks. Is that a registry update?
Was curious becuase i couldn't find and "...\qwerty" entries in the registry.
Click to expand...
Click to collapse
It is a registry entry. I was originally looking for the same "qwerty" entry (like in the 8525), but instead the following was the culprit:
Code:
[HKLM\HARDWARE\DEVICEMAP\KEYBD]
create - CWSLayout - value (1)
TaurusBullba said:
It is a registry entry. I was originally looking for the same "qwerty" entry (like in the 8525), but instead the following was the culprit:
Code:
[HKLM\HARDWARE\DEVICEMAP\KEYBD]
create - CWSLayout - value (1)
Click to expand...
Click to collapse
ahhh - i have a feeling there will be many registry differences from 8525 to 8925....
Thanks for the knowledge
reitjam said:
i got the tilt at 12 today and took it home and startedripping it apart, I put the htc rom on with msvc 1.6, live search, the nice battery icon and the home plug-in customizer, thats it, on my hermes i needed so maney things to make it function, i like the tilt now that the keyboard is fixed.
damn i can not edit the title, well crap
Click to expand...
Click to collapse
which HTC rom did you put on it? Got a link to it? I think it's time to de-ATT mine.
robroth said:
which HTC rom did you put on it? Got a link to it? I think it's time to de-ATT mine.
Click to expand...
Click to collapse
Not hard to find, it's stickied in this forum.
TaurusBullba said:
Not hard to find, it's stickied in this forum.
Click to expand...
Click to collapse
Already downloaded that one, but I just wanted to make sure that's the one to use on the 8925. Better safe than sorry with something so new .
Keyboard fix
How do I install this?It keeps showing up as a xml file that opens the web browser
bigthingspoppin215 said:
How do I install this?It keeps showing up as a xml file that opens the web browser
Click to expand...
Click to collapse
You're trying to install it from your computer, don't. Move it over to your phone using activesync then tap to install.
bigthingspoppin215 said:
How do I install this?It keeps showing up as a xml file that opens the web browser
Click to expand...
Click to collapse
its a cab file, try right clicking and save/as. stick it on your PPC and then run the cab. it worked fine here.
I have a bit of an issue when on phone mode. This fixes the FN issue, but doesn't fix the caps issue when on the phone mode. I'm trying to search for a name and the W is a Q, T is a V, there is no S, D is a F, and so on...
I am using Schap's WM6 Pro 4.22 and I have installed the cabs for the keyboard and dialer and restarted, however it is still coming up as the big black keyboard, and the black dialer. When I select "keyboard" in the options it does not show anything, I then realized that the TOUCH keyboard was the only one that is working. I have a Tilt btw.
Hope this made sense.
Same problem here..
Can anyone explain..
I have never get it work either. It just disappear after installation. But it is a critical so I let it slide.
1 The attached keyboard works fine with me.
2 black dialer- have a look here http://forum.xda-developers.com/showpost.php?p=1725991&postcount=17
grizzlymint said:
I am using Schap's WM6 Pro 4.22 and I have installed the cabs for the keyboard and dialer and restarted, however it is still coming up as the big black keyboard, and the black dialer. When I select "keyboard" in the options it does not show anything, I then realized that the TOUCH keyboard was the only one that is working. I have a Tilt btw.
Hope this made sense.
Click to expand...
Click to collapse
Shouldn't you be directing the specific problem at the original thread ??
http://forum.xda-developers.com/showthread.php?t=350700
~~~~~
UnicornKaz said:
Shouldn't you be directing the specific problem at the original thread ??
http://forum.xda-developers.com/showthread.php?t=350700
~~~~~
Click to expand...
Click to collapse
Probably........
taiseer999 said:
1 The attached keyboard works fine with me.
Click to expand...
Click to collapse
This has worked fine for me too, but I found that if I uninstall the M&M TOuch Wait Cursor, I lose the gray keyboard too. Something is being changed in the wait cursor cab file that also is effecting teh keyboard. go figure...
does anyone have a for sure working cab. I've searched and tried a few different ones w/ this new ROM i'm using (TAEL)...and all the cabs i've tried seem to fudge something up. for the most part, none of them have the numbers in the right spot Fn+any number gives me symbols instead of the numbers. So far i've tried one called 'HTC Fuze Keyboard fix' and 'TP2FUZE KB', and another called 'Shlomki Fuze Keyboard in TouchPro ROM'
EZinput 2 does not play nice with the Fuze keyboard lay out, his new rom corrects the issue along with many other bugs and from what TAEL says it should be out some time tomorrow.
Fraid i cant be 100% sure - but i think http://blownfuze.org has the cab (mines not a fuze so never bothered downloading the cab to check!)
well...i'm not running ez input...but i'm running finger keyboard 2.1. I never had any problems w/ my tilt using that app. Hopefully thats not it, i'm gonna try this cab one more time from blownfuze.
if i'm installing these cabs, it wouldn't matter if the keyboard was changed under the advanced config utility would it? Because regardless of whether it was on AT&T/Cingular/English/Custom...installing the cab would make the reg edit right?
you dont have to be using EzInput but its installed on the device and thats where the conflict is, The EzInput changes the key mapping for all hardwere keyboard keys.
dah wellz, i just switched back to nrg genesis rom. no biggie. thanx for the help anyways guys
I built a clean kitchen using sense 2.5 and noticed that the Fn-J produces a / instead of a colon. Is there an easy way to fix this mapping?
http://forum.xda-developers.com/showthread.php?t=727406
I have a Us Cellular TP2 and I have the same "problem"... but found that the secondary function of the buttons of the J & N are jsut switched.. There are a few other secondary fuctions that are switched around too.. I wish they had a cab or mod to use our keyboard.. I am using the newest Energy rom...
Talamar said:
I built a clean kitchen using sense 2.5 and noticed that the Fn-J produces a / instead of a colon. Is there an easy way to fix this mapping?
Click to expand...
Click to collapse
http://thewingster.com/Documents/Sprint Keyboard Fix.cab
It's a cab from thewingster.com. Also see the ppcgeeks post for more info...
http://forum.ppcgeeks.com/showthread.php?p=1346281&highlight=Sprint#Fix.cab#post1346281
I can confirm... the US Cellular keyboard lay out is identical to the Sprint one.. I installed the above cab and now my keys are accurate... Thanks again....
kiint,
I tried what you suggested on the other thread but I'm missing the second key and value (the one under SOFTWARE), should I add that or did something not get loaded in the kitchen right?