Database Info

Raphael hardware keys, remapping?

Has anyone come up with working solution for mapping hw keys?
I found this thread on Diamond, but no help:
http://forum.xda-developers.com/showthread.php?t=398280

I am using AEKMap to enable both latin/cyrillic input on my TP's hw keyboard. You may google it and give it a try.

There is no need for additional software, just follow this post and you'll get the answer. Worked for me.

Try AE Button Plus.
B.

I think you did not quite follow me here.
I dont mean to change layout of QWERTY, but hw-keys like "Back" and "Home" at front panel of TP.
This is becaus I find home and back quite useless and would much more prefer to have ALT+TAB (change program) and close program (REALLY close them, not leave running background as back seems to randomly do).

Taajuus said:
I think you did not quite follow me here.
I dont mean to change layout of QWERTY, but hw-keys like "Back" and "Home" at front panel of TP.
This is becaus I find home and back quite useless and would much more prefer to have ALT+TAB (change program) and close program (REALLY close them, not leave running background as back seems to randomly do).
Click to expand...
Click to collapse
And that is EXACTLY what i also want to know....
The total lack of hardware-keys on this device is already disturbing enough, but being locked out of the option to remap any of them is truely horrid...
Anyone know of any reg-hacks maybe?

I've got Spb PocketPlus 4 installed btw, and it's got a button mapping function as well...
But when i go into the buttons map, some weird black icons appear with no name attached to it. Can anyone make anything of this? As you can see i've been able to map one thing only: the Spb close-button-contex-menu, which allows me to switch task KW-buttons only....
But this is not enough for me, i need ALT-TAB aswell and off course a VoiceCommand button.
And regrettably the Rapael doesn't have that many HW keys to start with...

I want also to use Home/Back buttons for different purposes,but I didn;t found a solution yet.

Gotten a step closer to what i really need over this weekend:
In the button dialogue (with extra generated buttons by Spb PP+4) there was only one other button that had a name...
So i tried this one and go figure: it seems to be the " <= " (or 'back') button. In the dialogue it's called the OK button. I've got it set to the close contaxt menu now, and mapped Voicecommand to long-pressed answer key...
So far, this setup is to my satisfaction, and after two months of use this phone finaly behaves completely the way i want it to...

Hi, guys.
See my post here:
http://forum.xda-developers.com/showthread.php?p=2743845#post2743845
Hope this helps!
Cheers.

helped realy much !!! big thx for that nice instructions

You're very welcome, tk_berlin.
You be sure to let me know if anything in there doesn't make sense or you need any help with it.
Cheers from Canada!

ah cool to see a reply that fast ,)
hmm u got any further with finding out how to set the home button and the backwards button ?
Since the other htc user ,) wrote
In the button dialogue (with extra generated buttons by Spb PP+4) there was only one other button that had a name...
So i tried this one and go figure: it seems to be the " <= " (or 'back') button. In the dialogue it's called the OK button. I've got it set to the close contaxt menu now, and mapped Voicecommand to long-pressed answer key...
so it works with SPB PocketPlus ?
there must be a way to get it work wit the other tool

ah cool to see a reply that fast ,)
Click to expand...
Click to collapse
Lol. I was on my machine all morning and had XDA open in one of my tabs.
Yes, you can map practically any button in AEBPlus no problem.
hmm u got any further with finding out how to set the home button and the backwards button ?
Click to expand...
Click to collapse
AEBP will also *learn* any keys it doesn't have. So you could use the "Add Button" option, press your Home key, and away you go.
The way I have it set up, holding down the phone key will activate voice command (default behavior).
But remember, assigning commands to the Home or OK buttons (that "Back" button is actually an "OK" button) doesn't unmap what they normally do so you will always go home first and then it will perform <x>-function that you assign.
Personally, I don't like to program the Home or OK buttons because I find that they are "trickier" to press. What I mean is, if you tap the OK button near it's center or close to the left, it doesn't register a press. If you tap it sort of with the long part of your thumb (which is more natural when holding the device in one hand), it registers it. I've tried this with two TP's now and the button behaved the same way on both. Due to this, I find it unreliable to map anything to it.
In any case, as I mentioned earlier, the Volume buttons, Phone and End keys will be unmapped once you attach AEBP to them but the others will not.
Oh -- I forgot to mention, you can map the directional pad as well if that is your thing.
so it works with SPB PocketPlus ?
there must be a way to get it work wit the other tool
Click to expand...
Click to collapse
It does work, but it sends an OK command first.
I wrote a little utility for hard-coded buttons such as these for another Pocket PC I had (an ASUS P527) called "DoNothing.exe" but we can't apply that work-around here. What I would do is replace the EXEs of apps the hardware keys called with my DoNothing.exe, but in the case of the TP, we definitely don't want to replace START.EXE (which I believe to be the likely EXE (haven't tested this)).
If I find a way to map those buttons reliably, I will let you know, tk_Berlin. So far tho, I've been quite pleased with just using the four buttons I mentioned. The more I use this device and the more I ponder my decision to stay with TFL3D instead of the normal WM interface, the more I realize that I don't need half the add-ons I used to use prior to having TF3D. I am accustomed to very, very, very *heavily* customizing my device, but the setup I have now works great and I really haven't lost nething from my old WM world. In fact, prolly gained a few CPU cycles and memory to boot.
I don't miss the Today Screen at all!!! Now that I think about it, I never really looked at it.
Cya!

Word Correction / Auto Correct Fix

I posted this in the other Auto Correct thread (found here). That thread got so long that it was requested that I start a new thread with this info so it is easier to find this fix and how to do it.
I have a FUZE and mainly ONLY use the actual physical keyboard and not the onscreen keyboard. The fact you can not set up normal Auto Word Correction words was driving me crazy. So through a lot of people a fix was found. Credit goes to a lot of people who suggested different things (like Bugsykoosh), and then I put a few different programs/tweaks together and it works very well.
Here is how you do it.
1) Disabled T9 completely by installing the cab found at http://forum.xda-developers.com/showpost.php?p=2914474&postcount=8 . After installing the T9 button will no longer work.
2) Change your onscreen keyboard to "keyboard" as the default. You will no longer be able to use the QWERTY keyboard, but that was fine for me since I mainly use the actual keyboard. For this to work you MUST switch your on screen default keyboard to "keyboard" or install the Happy Tapping keyboard.
3) Install DictMgr for Windows Mobile that can be found at http://mobile-sg.com/software/?p=DictMgr&platform=ppc . It is FREE. This program is the key to making this work.
4) Only parts of DictMgr works with our version of Windows Mobile. After installing open up the program and launch the Word Corrector part of the program. It looks exactly like the traditional word replacement entry screen you see on your PC. SEE ATTACHED PICTURE.
5) Add the words you want to auto correct and hit save. It requires a soft reboot.
10) After the reset try to type something using the actual keyboard and you will see the word correct work the way it is supposed to.
I am VERY positive right now about this working so far.
Some other Feedback/Notes:
1) I use MyMobiler so when connected to my PC I can view my phone screen on my desktop. This makes entering all the auto correct words I want MUCH easier since I can use my normal keyboard.
2) I entered as MANY as I could at one time because a soft reset is required each time you save the file.
3) I have started entering all the basic ones like
i --> I
monday --> Monday
mon --> Monday
tuesday --> Tuesday
tues ---> Tuesday
(and all the rest of the days)
jan --> January
feb --> February
(and all the rest of the months)
4) on the onscreen keyboard I did go to the Touch Input Setting and check all options. See attached image.
5) I also went to the Options-->Word Completion Tab and checked "Enable Auto Correct. See attached image.
Everyone, this SEEMS to be a real EASY fix for this issue I am happy to report.

There is a solution to still use the Full QWERTY Keyboard. The complete text is located here: http://www.fuzemobility.com/?p=1527
After disabling T9 you must toggle the T9-ABC button back on. To do it press the button then hit the ABC123 button and keep going until it stick. If that fails go into landscape mode and try toggling. Once you get it to change it will stay that way. The one downside is it only works for odd numbers so it works on the first, third and fifth letter you enter and on the second letter no autocompletion appears on screen. The autocorrection (ex spell check) still occurs either way that.
Thanks TVDinner -that was fun

sweet! This issue now has 2 solutions. I love when a plan comes together!!!

So with this fix can I still use the physical keyboard/Full QWERTY soft keyboard/Phone Keypad like normal?

NeroDan said:
So with this fix can I still use the physical keyboard/Full QWERTY soft keyboard/Phone Keypad like normal?
Click to expand...
Click to collapse
Hi NeroDan;
With bugsykoosh's fix you can still use the on screen Qwerty keyboard.
With my fix you have to choose the onscreen "keyboard" option, or install the happy tapping onscreen keyboard. You can not use the qwerty keyboard with the fix I described.
If you do not use the onscreen keyboard then either fix will work fine.

Remove T9 black bar!!!

Hey fellow XDA-ers.
I hope that in this thread we can unite in finding a solution for the annoying t9 input mehod, without breaking the hardware keyboard.
What's the problem:
I want to get rid of the annoying black t9 input and autocomplete bar, and use the standard WM6.1 version.
What anoys me the most is when you type an address for sending text, you start by typing first name of for instance friends who share a first name, but have different last names, , as soon as you hit space for the lastname, the person with the first name that's on top of the list gets selected..ARG
I also hate the lag it introduces.
So getting rid of the black ezinput part of the keyboard.
This can be done by replacing the eT9 values in your registry at the layout to COMP (et9IME replace by compIME and so on) and this works for soft keyboard.
However, this "fix" breaks some stuff in your hardware keyboard (the SYM key for instance stops working, also you cannot get the euro sign or the pund sign by pressing fn E or fn W)
I of course want the best of both worlds, and especially miss the sym button for getting a "\" whilst typing in shortcuts
So, I have tried so much, but haven't found a solution yet.
Does anybody know how to get this "best of both worlds" option?

Does opening up the on-screen keyboard and hitting the T9 --> ABC switch help?

nope
It doesn't use autocomplete then when typing text, but you still get the black bar at the bottom whilst entering an address, and the space-issue (filling in word after space) is introduced.
I just want the behaviour as when eT9 replaced by comp (ei. you get a couple of suggestion in your screen in light grey boxes, in stead of on bottom bar in black) but with FULL use of my hardware keyboard.
I want to do this without installing all kinds of secondary software that slows my device down, but want to solve it at the root.
Hope I am explaining the problem clearly
But thanks for the reply..
Maybe we can figure it out..

known problem
I've done the t9 compIME registry change and to me, is a must. That black bar was SO annoying and decreased effectiveness.
I have noticed the hardware keyboard does get screwy after doing this.
Using Da_G's roms, he has solved most of the problems in some of his earlier roms. I think the only problem I have currently is a non-working "cent" sign (FN+_). I'll test this again after I flash to his latest Rom.
I think he solves this by implementing SOME of the t9 files. I'll follow up with more accurate results.

player911 said:
I've done the t9 compIME registry change and to me, is a must. That black bar was SO annoying and decreased effectiveness.
I have noticed the hardware keyboard does get screwy after doing this.
Using Da_G's roms, he has solved most of the problems in some of his earlier roms. I think the only problem I have currently is a non-working "cent" sign (FN+_). I'll test this again after I flash to his latest Rom.
I think he solves this by implementing SOME of the t9 files. I'll follow up with more accurate results.
Click to expand...
Click to collapse
If that's the case, making a cab, or posting the necesary files to replace would be ideal.
Does your SYM key work?
sounds like a very good start

I had this same annoying error
I managed to get it to go away by
sliding out the keyboard
whilst pressing the green FN button hit the spacebar.
This brings up a small menu, select
ABC and bingo, its sorted.
Steveb

akky66 said:
I had this same annoying error
I managed to get it to go away by
sliding out the keyboard
whilst pressing the green FN button hit the spacebar.
This brings up a small menu, select
ABC and bingo, its sorted.
Steveb
Click to expand...
Click to collapse
Tnx for your input Steve.
I allready have that set up, but as you will find, it does not get rid of the black bar during txt msgs to field input, if you know what I mean.
It also gives lag on the hardware keyboard input comapred to the comp ide input method, which I find anoying.
What I really want is just the old wm input and auto complete feature without breaking my keyboard.
but as said before, thanks for the input.
This way we can narrow it down and hopefully make the problem easier to understand.
Ta...

tried editing sym files
Tried editing and replacing the txt files in windows directory,
eT9.Raphael.0409.kmap.txt and eT9DeadKeys.txt and renamint the et9 to comp, no luck.
Anybody any suggestions?

akky66 said:
I had this same annoying error
I managed to get it to go away by
sliding out the keyboard
whilst pressing the green FN button hit the spacebar.
This brings up a small menu, select
ABC and bingo, its sorted.
Steveb
Click to expand...
Click to collapse
I did that and the black bar is gone! No more annoying auto-capitalizing and duplicated words! Thanks a lot!

Not quite
Smaniac said:
I did that and the black bar is gone! No more annoying auto-capitalizing and duplicated words! Thanks a lot!
Click to expand...
Click to collapse
It get's rid of the black bar whilst typing a text, however whilst typing an adress in the to field, you will notice that you still get a black bar and proposed name in the bottom of your screen.
This is actually eT9 still running, and slowing down your input, trust me on this
The "old" way, you'd get the proposed names next to your to field, in a light grey box, and you could scroll through them and use the space bar without getting it to autocomplete.

I normally type the first few letters of the persons name, and then use the left and right arrow keys to gp through the matching contacts. That does the trick for me

indeed
GaZ said:
I normally type the first few letters of the persons name, and then use the left and right arrow keys to gp through the matching contacts. That does the trick for me
Click to expand...
Click to collapse
It does the trick and it is how I use it now.
It's just not the solution I am looking for.
I'm a bit wierd in that way, if I see it poping up, I know it's there and it just annoys me...
Don't you just love the way things were before
But thanks for the tip.

No luck here yet
I haven't had any luck yet, anybody else?
This issue is really starting to bug me

Any luck yet with removing the T9 Black bar? I am having this problem as well.

Me too!
i want the old way with the little grey box, it was so much better. It gave a number of people when you typed in a user name for sms and it also gave better autocomplete options.

Solve for all us
Try attached CAB guys from our famous Russian PDA professional. It's remove this bar completely.

yes it worked for me on Touch HD perfectly

Works
Igoran said:
Try attached CAB guys from our famous Russian PDA professional. It's remove this bar completely.
Click to expand...
Click to collapse
TY it completely rocks on Touch HD.

Does this just disable T9 on the hardware keyboard? AND, when entering a contact into sms or email you get the grey list like before?
What about T9 for soft keypad/boards? How does it function now?
I stumbled upon your thread while searching for "disable t9 hardware keyboard".
I have the same problem on my Kaiser... Installed ezinput keypad/board and now have that 'damn' black bar. I'm getting used to it like 'GaZ' but dont really like it...
<<<UPDATE: Only selected abc over t9. Black bar still there.>>>>

use different sip
im not sure if this help but wasnt this issue introduced with the diamond sip set? maybe using different sips might get rid of it. or maybe replacing the new eT9 and using the old wm6 t9 instead in wm6.1 roms. just a thought

[Q] Multi-language keyboard auto-switching bug?

Hi everyone
I first dismissed this error as another manifestation of the N1's touch screen drawbacks; but since I owned the Nexus S, the same error reappears, and it’s driving me nuts:
All signs point to the fault being caused by the Gingerbread keyboard. This is how you reproduce it:
1) Use more than one keyboard layout / input language
2) Type anything, switch to the first symbols keyboard
3) Hit any key from the symbols keyboard, and afterwards, directly the space bar
4) The keyboard switches back to letter mode, all good up to now
5) Hit the symbols button again
6) The input language automagically changes to the adjacent one, the keyboard switches back to ABC mode
Suffice to say, this is quite an annoyance. There’s a workaround, though: this doesn’t happen if you hit the ABC key before hitting space, but that’s not how I expect my keyboard to work.
Is anyone else able to reproduce this issue, and if yes, does anyone know how to fix this? Unfortunately, extensive research throughout last week didn’t bring back any usable results.
Thanks for your help!

thenoo said:
Is anyone else able to reproduce this issue, and if yes, does anyone know how to fix this? Unfortunately, extensive research throughout last week didn’t bring back any usable results.
Thanks for your help!
Click to expand...
Click to collapse
Hey!
this happens also on my Nexus S...really disappointing (
I played around in the Keyboard settings but couldn't find a way to fix this (unless you remove multiple languages....but that's not the point :S).

[Q] BT keyboard woes

Hello world,
(I really hope this is the correct section)
I recently bought an Oyama OY661 for use with my Android tablet and was disappointed to find out none of the special keys (shift, ctrl, alt) worked with it. Using a key test app I noticed that while for my fullsize USB keyboard it showed e.g. meta_shift_on|meta_shift_left_on along with 'a' when pressing shift-a, obviously, for the bt keyboard it just showed the letter, while showing the shift code when pressed alone (so I knew the keys themselves were working, just not combining them). Without giving it any second thought I returned it as incompatible and got a Rapoo E6300 instead, as I saw it had all-around great reviews.
I now regret that decision. The keyboard is the same size as the onscreen one, but with all the keys crammed together, it's actually even more uncomfortable go use. The battery is built-in, meaning you have to get a new keyboard when it dies out, and the auto-sleep is too agressive, having to reconnect more often than not when e.g. browsing and reading a forum.
Seeing how I actally preffer writing this post using the onscreen keyboard of my 4" phone than using the E6300, I'll return this one as well today. So my question is: Should I get the OY661 back? I've tried every "confirmed working fix" (disable chrome after uninstalling updates, set everything to 'default' in lang&input, force everything to 'English (US)' in lang&input etc) but none worked for me. But now I'm thinking maybe this can be fixed by modifying the keyboard layout&map files? Or is this a driver/hw specific issue and I'm better off looking for another keyboard? (I'm looking for something cheap to use with a $200 tablet. So a $100 keyboard that works with my computer, tablet & dog will not do, as anything designed primarily for the desktop compromises on the mobility usage and vice-versa - take the multimedia vs Fn keys; plus, I don't have a dog.)