This thread can be closed.
I am able to reproduce this situation, but extrangely, my 20 keys keyboard acts as a 16 one (my error, downloaded the wrong cab).
Will update with the right one.
Edit:
Installed the QVGA_CpKbd cab and the bug still exists. This situation happens whilst using abc mode. With T9, a weirder thing happens. Typing for "holy" (4 key press) and hitting backspace, instead of deleting a letter, it changes the word to "gole" (still 4 letters). Same thing happens on the soft keyboard, but the abc "problem" is fully solved.
If you need further information, dont doubt in asking.
As side information, im on great hellonasty´s Mary 6.1 OS 5.2.20753
mignonette said:
Installed the QVGA_CpKbd cab and the bug still exists. This situation happens whilst using abc mode. With T9, a weirder thing happens. Typing for "holy" (4 key press) and hitting backspace, instead of deleting a letter, it changes the word to "gole" (still 4 letters). Same thing happens on the soft keyboard, but the abc "problem" is fully solved.
If you need further information, dont doubt in asking.
As side information, im on great hellonasty´s Mary 6.1 OS 5.2.20753
Click to expand...
Click to collapse
Thanks a lot for testing it.
Now, a list of questions that might seems weird or even deserve an obvious answer, but that are of utmost importance.
1] Your rom is WWE based ?
2] Are you experiencing the issue using the english language ?
3] The T9 english dictionary doesn't have a 'gole' word. Could you launch eT9MyWords from the Programs folder, and check if it has been added as a custom word ? If yes, could you delete it and make the T9 test again ? This doesn't seem to be an hardware issue like the first - it might be unrelated.
4] you say that the backspace issue happens only in ABC mode. Please open the T9 settings and uncheck the "Word Completion in ABC mode" checkbox and the "Spell Correction" one. I don't know if you can set these options even when using the hardware keyboard, but just try. Then, try to see if the backspace issue is still there.
I'm sorry to overwhelm you with questions, but I have just a Kaiser, and I can't reproduce the issues here, first of all because my hardware mapping files are different.
If you can help, your support will be greatly appreciated. If not by the other 'get it and run' users, at least by me and a small good bunch of fellows (who are too timid to post their reports ).
Thanks !!
1] I believe it is, but cant assure it. The rommaker post is this
2]yes, the language was set in english
3]I have seen gole was added to eT9MyWords. Deleting the word, seems T9 works as expected.
4]removing autocomplete in abc mode keeps the disfuntion. Uncheking spell correction and auto-substitution wont solve this issue. Also tried uncheking T9 word completion without success
Ps:
Been trying with all T9 settings checked (spell correction, completion in T9, completion in abc and auto-substitution) and the problem gets fixed. When I tested the first time, spell correction wasnt checked. This makes some changes, as the whole last word keeps "selected", instead of the last word. This could work as a workaround.
Weird thing is that I cant manage to keep T9 mode on. Each time I try to write a new sms, it defaults to abc.
Dont worry if you need more tests, or even installing a debug version (or whatever you would need)
mignonette said:
1] I believe it is, but cant assure it. The rommaker post is this
Click to expand...
Click to collapse
Uhmm... another rom with the Opal EzInput installed. So far all the cooked roms have been using a pre-release version which doesn't include the fix that you can find on my thread. See, basically, HTC manages HW layouts in four different ways, and the settings extracted from the Opal rom are those for phones without keyboards. You can't imagine how many issues are related to this mixed configuration. I don't think this is the case, but only our tests will be able to tell the truth.
3]I have seen gole was added to eT9MyWords. Deleting the word, seems T9 works as expected.
Click to expand...
Click to collapse
Good.
4]removing autocomplete in abc mode keeps the disfuntion. Uncheking spell correction and auto-substitution wont solve this issue. Also tried uncheking T9 word completion without success
Ps:
Been trying with all T9 settings checked (spell correction, completion in T9, completion in abc and auto-substitution) and the problem gets fixed. When I tested the first time, spell correction wasnt checked. This makes some changes, as the whole last word keeps "selected", instead of the last word. This could work as a workaround.
Click to expand...
Click to collapse
Good move, very good move. But the fact is that if you unselect one option - I suppose - the issue reappears.
I can't understand what's happening. Actually, what's the difference between the correct behaviour and this one ?
In ABC mode, does the last letter always gets selected when you type ?
I thought that the letter was reappearing because the ABC autocomplete option or the spell check were trying to correct it.
So, if you write just a bunch of meaningless letters, and then delete the last, does it reappear ?
After these tests, if you have a registry editor, could you try to delete this key, to see if it helps ? You should soft reset, after that.
HKLM/Software/Tegic/eT9/IME/KdbFiles/07FF
It's an empty keyvalue.
Weird thing is that I cant manage to keep T9 mode on. Each time I try to write a new sms, it defaults to abc.
Click to expand...
Click to collapse
We can probably fix this one.
You can change this value:
HKLM/Software/Tegic/eT9/CarrierDefaultTextMode
from 0 to 1. Soft reset after that.
This should give you T9 as default. Do you mean that this should be the default mode, on the Dual ? I've read elsewhere that HTC has made a fix to set ABC as default. Weird.
Dont worry if you need more tests, or even installing a debug version (or whatever you would need)
Click to expand...
Click to collapse
I might ask you to uninstall my cab and delete all the keys used by the application, to be sure to avoid any misconfiguration chance, but this would mean that you would have to hard rest the device to bring them back.
I know that Manila2D users should be prepared to make an hard reset for each build, but it's a bit too 'destructive'. But we might proceed to do it the next time you're going to do it anyway, right ?
The fact is that I'm walking in the dark, and everyone seems interested just in his phone. Quite embarrassing for the whole forum, if it were not for the few users willing to help, like you.
Thanks a lot for your great support.
Well, i have unchecked every setting (spell correction, completion in T9, completion in abc and auto-substitution) and the problem keeps appearing. What I have seen is that you have to press backspace really quick, as the selected letter goes deselected in just a second.
In ABC mode, does the last letter always gets selected when you type ?
Click to expand...
Click to collapse
Thats it, in abc mode, with spell correction unchecked, only the last letter keeps selected. Otherwise, is the last whole word the one selected.
I thought that the letter was reappearing because the ABC autocomplete option or the spell check were trying to correct it.
So, if you write just a bunch of meaningless letters, and then delete the last, does it reappear ?
Click to expand...
Click to collapse
Yes, its certainly the spell checking the step causing the issue.
Have deleted HKLM/Software/Tegic/eT9/IME/KdbFiles/07FF (and also edit HKLM/Software/Tegic/eT9/CarrierDefaultTextMode, thanks for that) and softresetted. Now the problem only can be reproduced when checking Auto-substitution (the other three options unchecked), but still exists.
I will hardreset if you need it (it´s not a big deal), and maybe its a rom-related error, as Manilla is still beta. Maybe I wont be able to do it as quick as changing some reg keys, but will definetly do it.
PS: The CarrierDefaultTextMode hasnt changed the T9-default-behaviour. I´m not sure if HTC wants abc as default, but i believe each user should be able to choose and mantain it. The funny thing is that I don`t use the hard keyboard at all, as I just my Nike to call and get called.
Sorry for my probably frequent engrish
mignonette said:
Well, i have unchecked every setting (spell correction, completion in T9, completion in abc and auto-substitution) and the problem keeps appearing. What I have seen is that you have to press backspace really quick, as the selected letter goes deselected in just a second.
Thats it, in abc mode, with spell correction unchecked, only the last letter keeps selected. Otherwise, is the last whole word the one selected.
Yes, its certainly the spell checking the step causing the issue.
Have deleted HKLM/Software/Tegic/eT9/IME/KdbFiles/07FF (and also edit HKLM/Software/Tegic/eT9/CarrierDefaultTextMode, thanks for that) and softresetted. Now the problem only can be reproduced when checking Auto-substitution (the other three options unchecked), but still exists.
Click to expand...
Click to collapse
You're then saying that deletion of that key actually changes something.
Well, at least I can remove it safely. I though that it was just an error in one of the fixes made by HTC, and it seems I was right. Sadly, this doesn't seem to be enough.
I will hardreset if you need it (it´s not a big deal), and maybe its a rom-related error, as Manilla is still beta. Maybe I wont be able to do it as quick as changing some reg keys, but will definetly do it.
Click to expand...
Click to collapse
No, there's no need to hurry. I've asked to 16keys users to test it, too, and they report the same issue. Chances that everyone is using a wrong rom are low, quite low. But whe you will be ready, we can give it a try...
PS: The CarrierDefaultTextMode hasnt changed the T9-default-behaviour. I´m not sure if HTC wants abc as default, but i believe each user should be able to choose and mantain it.
Click to expand...
Click to collapse
You're right, and this is a bug that we'll try to solve.
It's quite strange that the setting doesn't work, but I'll try with the other users, and I'll let you know as soon as I'll discover something about it.
Your support has been great, there are no words to thank-you. But if you'd like to get something fixed on this package, your request will always get a good psotion in the list.
BJK
Well, whenever you need something to test, dont doubt in pming me
Hi,
installed (on my 16 Key Nike) newest Lily Rom (without Keyboard) and use your cab file. Hardware Keyboard is working
For me it seems the Keyboard has a little lag, but nothing to be worry about.
If you need some further information or some testing, i can do it for you
Thanks for your great work!
//Update:
Your new Version Beta 1.1 seems to work better, or at least i feel so *gg*
vcdwelt said:
Hi,
installed (on my 16 Key Nike) newest Lily Rom (without Keyboard) and use your cab file. Hardware Keyboard is working
For me it seems the Keyboard has a little lag, but nothing to be worry about.
If you need some further information or some testing, i can do it for you
Thanks for your great work!
//Update:
Your new Version Beta 1.1 seems to work better, or at least i feel so *gg*
Click to expand...
Click to collapse
Well, I fear that you're just too kind
Others are reporting the same issue, so something needs to be fixed.
But the registry settings that I've put in the Nike cabs are exactly the ones that come from the stock roms and the keyboard hotfixes from HTC, so it could be a problem related to the fact that HTC is no longer developing for the Nike form factor.
I know that this is better than nothing, but all the time I'm spending on it just for a "better than nothing" is not a good thing...
Anyway, I almost missed your post - could you come back to the official thread ? A least I'll have more time to debug that damned cab...
Thanks,
BJK
settings for xt9 that work with nike hardware keyboard
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\IME]
"CarrierDefaultTextMode"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\Sip\LanguageKeyboardIDMapping]
"0109"="0909"
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Layout Text"="eT9 IME"
"Ime File"="\\windows\\eT9ime.dll"
[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\InputModuleDlls]
"0"="eT9RegInput.dll"
"1"="eT9DisInput.dll"
[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\LdbFiles]
"0109"="ENlbUN_xt9s.ldb"
[HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\IME]
"KeyboadLayout"=dword:00000001
"DefaultInputModule"=dword:00000001
"MdbFile"="HTCMDB.txt"
[HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9]
"ResetDB"=dword:00000000
"DefaultLanguage"=dword:00000109
"XT9SupportMSSip"=dword:00000001
"HTCStyleSelectionList"=dword:00000000
"InstallFolder"="\\Windows"
"AvailableLanguages"="0109"
"MultitapWordCompletion"=dword:00000000
"WordCompletion"=dword:00000001
"AutoSubstitution"=dword:00000001
"AutoAppend"=dword:00000001
"Prediction"=dword:00000000
"SpellCorrectionMode"=dword:00000000
[HKEY_CURRENT_USER\keyboard layout\Preload\1]
@="e0010409"
[HKEY_CLASSES_ROOT\CLSID\{73AB106C-A726-484b-B610-BE3E1CF39821}]
@="XT9"
[HKEY_CURRENT_USER\keyboard layout\Preload]
@="e0010409"
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\KEYBD]
"3PartyIME"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\MASD]
"IME_Engine_Western"="1_5_32294_0"
I would like to see swedish language support. Reason: IMO I think quite a lot of swedes use these devices.
Using BJK's packaged I had two differences to the reg settings above:
[HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9]
"HTCStyleSelectionList" was set to 1
and
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\KEYBD]
"3PartyIME" was set to 1
There are other values in place as his package is for 5 languages.
Regardless of whether these values were set to 1 or 0 the backspace issue as mentioned above always occurs.
FrezoreR said:
I would like to see swedish language support. Reason: IMO I think quite a lot of swedes use these devices.
Click to expand...
Click to collapse
You'll see it, but after the main bugs will be solved.
Swedish is still missing some files that have to be rebuilt from scratch, and obviously the support has to go first to the problems that are affecting all users...
BJK
jerpelea said:
settings for xt9 that work with nike hardware keyboard
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\IME]
"CarrierDefaultTextMode"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\Sip\LanguageKeyboardIDMapping]
"0109"="0909"
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Layouts\e0010409]
"Layout Text"="eT9 IME"
"Ime File"="\\windows\\eT9ime.dll"
[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\InputModuleDlls]
"0"="eT9RegInput.dll"
"1"="eT9DisInput.dll"
[HKEY_LOCAL_MACHINE\Software\Tegic\eT9\LdbFiles]
"0109"="ENlbUN_xt9s.ldb"
[HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9\IME]
"KeyboadLayout"=dword:00000001
"DefaultInputModule"=dword:00000001
"MdbFile"="HTCMDB.txt"
[HKEY_LOCAL_MACHINE\SOFTWARE\Tegic\eT9]
"ResetDB"=dword:00000000
"DefaultLanguage"=dword:00000109
"XT9SupportMSSip"=dword:00000001
"HTCStyleSelectionList"=dword:00000000
"InstallFolder"="\\Windows"
"AvailableLanguages"="0109"
"MultitapWordCompletion"=dword:00000000
"WordCompletion"=dword:00000001
"AutoSubstitution"=dword:00000001
"AutoAppend"=dword:00000001
"Prediction"=dword:00000000
"SpellCorrectionMode"=dword:00000000
[HKEY_CURRENT_USER\keyboard layout\Preload\1]
@="e0010409"
[HKEY_CLASSES_ROOT\CLSID\{73AB106C-A726-484b-B610-BE3E1CF39821}]
@="XT9"
[HKEY_CURRENT_USER\keyboard layout\Preload]
@="e0010409"
[HKEY_LOCAL_MACHINE\HARDWARE\DEVICEMAP\KEYBD]
"3PartyIME"=dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\MASD]
"IME_Engine_Western"="1_5_32294_0"
Click to expand...
Click to collapse
Thanks but... which issue are you talking about ? The Backspace issue, or the T9 not set as default method ? They are the only ones we're talking about, but if you have discovered something else, it would be good to know !
Thanks,
BJK
i have a htc touch pro cdma and in input/setting word completion tab i have * add a space after word enabled... but when i am texting and i pick an auto completion word it places the word in my text but never adds the space... anyone know where in the registry where i can check to make sure its enabled...? driving me crazy
It has me flabbergasted as well: no space, really messed up in the word completion department! And lately, when I use the hard keyboard, the entries I make are invisible. Or when I text, the suggested words are invisible - the box is there, the words are in there, but it "appears" as a blank box. I'm saying they're there, because when I select one and hit enter, it gets typed.
Really irratic!
there has to be a spot in the registry that has a 0 for spacing and it needs to be set to a 1 .... i would think .... but i know the experts on this site would def know more.. can anyone please comment if they have an idea?
I have a Nexus 4 running stock 4.2.1 (rooted) and here is my issue with the gesture typing and predictive text. Anytime I try to use a word that google apparently believes is not appropriate like "****" I have to stop and and type it out. Mind you that spell check does not think it's a misspelled word so there is no option to add it to the User Dictionary. It just will not show up as an option for either predictive text or gesture typing. Obviously these words have somehow been identified in google's stock dictionary so that they are not part of the pool of suggested words - probably along the lines of how the auto-complete of google searches are now censored.
Does anybody have a workaround for this? It's incredibly annoying and I don't like the fact that google is dictating what standard English words can and cannot be part of gesture typing.
One thought I had was that the stock dictionary probably has those words marked with a simple boolean flag, so if somebody knew how to access the dictionary and reset that flag, the problem would be solved. I don't know much about android development but this can't be too hard. If I had the time I'd undertake the project myself.
Any thoughts would be appreciated.
Hey yeah I had the same problem... It's stupid that they blocked swear words... The only thing I figured out to get past it is that if you type in any word that isn't in the dictionary and select to add it you can type in anything you want, before confirming adding the word, including swear words and then you can type them with gesture typing. At least it works on my rooted Verizon galaxy nexus running jb 4.2.1 sorcery v4... Peace...
YourHero11 said:
Hey yeah I had the same problem... It's stupid that they blocked swear words... The only thing I figured out to get past it is that if you type in any word that isn't in the dictionary and select to add it you can type in anything you want, before confirming adding the word, including swear words and then you can type them with gesture typing. At least it works on my rooted Verizon galaxy nexus running jb 4.2.1 sorcery v4... Peace...
Click to expand...
Click to collapse
How do you add words to the dictionary? I'm very Android literate, and have been using Swype for a long time. The problem I have is that sometimes when I press on a word that it suggests, but doesn't recognize, it will give me the option to add it to the dictionary. Other times it will bring a box up above the word with several suggestions. It seems erratic and not very consistent.
wvcadle said:
How do you add words to the dictionary? I'm very Android literate, and have been using Swype for a long time. The problem I have is that sometimes when I press on a word that it suggests, but doesn't recognize, it will give me the option to add it to the dictionary. Other times it will bring a box up above the word with several suggestions. It seems erratic and not very consistent.
Click to expand...
Click to collapse
Settings >> language and input >> Personal dictionary and then add in whatever swears/words you want and it'll work when using the gesture typing. At least it works for me.
Thanks for the reply.
Anyone else having problems since it became a paid app with it lagging a decent amount of time upon opening?
Sent from my Nexus 4 using Tapatalk 2
As title suggests, I updated my phone yesterday. Now, when typing, if I spell something wrong, instead of changing automatically when I press space, it doesnt change the word, even though its highlighted blue. Is this a bug or feature and its very annoying ane may force me to flash back to older version. I cant see any options in the settings menu like before, just new options to sync spelling with facebook and Twitter etc... thanks for help.
Works fine for me
There are no more options anymore in settings for predictive text. You use to be able to edit your own words and specific predictive text data but your cant edit anything now so unsure what to do. Im sure I have read else where others having the same problems?
mine is also doin the same thing. Also noticed it no longer gives you the option to change the full stop to something else without holding
gotta be a bug. why highlight in blue if it no longer has a function anything? This is going to be very annoying.
It's what made me stop using the Samsung keyboard, prediction only seems to work when you use continuous input (swype) but even with that enabled, if you tap out each letter it will not work.
Glad its not just me anyway!
Meh, Android 4.2 keyboard rocks
I like the the way the keyboard behaves now. I can type my words without the auto correcting putting in the wrong words for me inadvertently and not having problems putting in words the the prediction doesn't know about.
I will also confirm that after updating to 4.1.2 stock - the auto-correct/predictive text system in the stock samsung keyboard seems to be no longer functioning correctly.
When typing the words are highlighted in blue however upon hitting space the word isn't corrected
Sango2 said:
I like the the way the keyboard behaves now. I can type my words without the auto correcting putting in the wrong words for me inadvertently and not having problems putting in words the the prediction doesn't know about.
Click to expand...
Click to collapse
+1. That's the main reason I now use Samsung keyboard. If I want it to auto correct I just select on the word.
Sent from my GT-I9300 using xda premium
never bothered with stock Android keyboards or Samsung's effort at "continuous text input" (well I gave it 5 minutes and kicked it into touch).
There is only one keyboard for continuous text input, and why would you want to tap letters individually any way? - its called Swype...its an absolute MUST.
google it, go to website and download swype beta installer
You guys are right, auto correct has been disabled in 4.1.2. I'm really hoping it's re enabled for the next release because I've never been a fan of aftermarket keyboards. I prefer the stock one. I would downgrade to 4.1.1 but I was getting some bugs on that which have been fixed on 4.1.2. Let's all hope it's re enabled for us!
Same problem here and I hate it. I've now switched to SwiftKey because of it.
Matcarroll said:
As title suggests, I updated my phone yesterday. Now, when typing, if I spell something wrong, instead of changing automatically when I press space, it doesnt change the word, even though its highlighted blue. Is this a bug or feature and its very annoying ane may force me to flash back to older version. I cant see any options in the settings menu like before, just new options to sync spelling with facebook and Twitter etc... thanks for help.
Click to expand...
Click to collapse
Same here. VERY ANNOYING! Why change something fundamental on the keyboard in this way? It's awful.
Regardless of what your keyboard preference is, you become accustomed to using it and it's ways until you can almost type blindfolded. Making changes like this just bugs the hell out of me!
Response from Samsung support in 2 hours :good:
I think I'll be trying Swift Key...
Samsung Support said:
Thank you for contacting Samsung.
I am sorry to hear that you do not like the features on the keypad since the latest update and i can understand it is frustrating.
Regarding your query this is a limitation of the new android version your running. However we always look forward to hearing customer feedback and comments.
I've passed your comments on to various departments who will use them to improve the products and services we offer. Thank you for your input.
Click to expand...
Click to collapse
I don't think it's anything to do with Android, Mr. Samsung!
Same problem here.
Please read forum rules before posting
Questions and help topics go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Has there been any update to this or is it still the same? It's so annoying.
larma said:
Same problem here and I hate it. I've now switched to SwiftKey because of it.
Click to expand...
Click to collapse
did switching over fix your problem??
what other keyboards out there can help fix this bug until next patch?