Recently my Mogul keyboard is jacked up. When I try to send a text or email, each key press results in multiple letters being typed. For example, a text message may look like this: cccaaaannn youuuuuuu mmmeettt mmmeeee?
Is this a hardware issue or something else?
More than likely hardware related. Time for a replacement. Also please update your carrier info in your profile so we can help easier.
mine was a memory/software issue. OEM was the worse ROM for it.
I noticed when my memory would get low, I was repeating characters like crazy.
Also I believe you can set the sensitivity of the keypresses in options somewhere. Also if you turn of auto correct or any other keyboard options, it seems to run much smoother, faster and more accurate.
I've gone to a custom ROM and turned off all the options for they keyboard, and I've been months without a double tap issue
Related
hi, not sure where else to ask this but has anyone ever came across the following issue -
whenever im typing a text message the input is only ever a number, even though it shows text on the virtual buttons, this happens with every form of input with the exceptions of using the stylus and full keyboard
it seems to be locked on numbers, i thought it was the shift key but that only seems to make it go to caps but then you press a and the number 2 appears, its driving me nuts and i cant seem to find anyone else having this problem
anyone help please?
cheers
PS
also just noticed whenever you go into input method options the virtual keys change to numbers outright and you cant change it back to text (ie press abc to go back and nothing happens, the abc button is also greyed out)
thanks
stub20000 said:
hi, not sure where else to ask this but has anyone ever came across the following issue -
whenever im typing a text message the input is only ever a number, even though it shows text on the virtual buttons, this happens with every form of input with the exceptions of using the stylus and full keyboard
it seems to be locked on numbers, i thought it was the shift key but that only seems to make it go to caps but then you press a and the number 2 appears, its driving me nuts and i cant seem to find anyone else having this problem
anyone help please?
cheers
PS
also just noticed whenever you go into input method options the virtual keys change to numbers outright and you cant change it back to text (ie press abc to go back and nothing happens, the abc button is also greyed out)
thanks
Click to expand...
Click to collapse
Had a similar problem and using HD Tweak disable T9 Mode for keyboard.
Both HD Tweak & Advanced Config have other very useful tweaks which I recommend. Both attached for your information
Fallen Spartan said:
Had a similar problem and using HD Tweak disable T9 Mode for keyboard.
Both HD Tweak & Advanced Config have other very useful tweaks which I recommend. Both attached for your information
Click to expand...
Click to collapse
hi, i have hd tweak, t9 was disabled, i enabled it, tried typing a message again, there was no input this time, the keys were showing but whenever i pressed them nothing happened, its as if text is completely disabled, i switched off t9 (in hd tweak) and tried it again, once again there were only numbers appearing
help!!
UPDATE
The only modes that DONT work are the phone keypad and compact qwerty, the other modes seem to work ok, unfortunately its the phone keypad i want to use!
As I've also suggested to you elsewhere, try uninstalling HD Tweak entirely - it seems to be the root of these sorts of problems.
I had the same issue. I unistalled HD Tweak and "hey presto!" had myself a working keypad. I suggest you try that same. Cheers.
Hello,
I currently use the phone keypad to type my messages, and sometimes after some words, when I press space it doesnt actually do a space. any ideas on what this could be, its really annoying when I look back and theres loads of words that are stuck together!
Thanks in advance.
Yes, I have a same problem, is there any solution for this?
Anybody help? Its really annoying
glad its not just me, i tryed turning off T9 etc.. but still does it
Yeah here also with a NLD rom. I need to push the spacebar somethings 2 times if I want a space in my text message.
I hope htc will fix it
Same problem here, I thought it was me not pushing it right
did you calibrate your screen?
before I calibrated my screen, I felt I have to skew my taps a bit (maybe its also an illusion with the glass touch screen's thickness when the actual image is behind 1-2 mm of glass) to touch the right keys. after calibration it seems better.
I find what is problem. When a tiny line is under letters, when i push space and then another letter, cursor go back. I don't know how to turn off this option and what is it for. Does anyone have solution? t9 is off in mu case and i use phone keypad.
kajzer223 said:
I find what is problem. When a tiny line is under letters, when i push space and then another letter, cursor go back. I don't know how to turn off this option and what is it for. Does anyone have solution? t9 is off in mu case and i use phone keypad.
Click to expand...
Click to collapse
you are right, the cursor does go back but im not sure how to stop it.
It is driving me insane because it takes me a long time to type a message now
its unusual that more people are not reporting this issue, is it a problem just with our devices, or maybe others are not concerned by this or unaware
Im having the same problem. When I had another ROM installed the keyboard had a bigger spacebar, but I went back to manila 2.1 and now it has the smaller one again...
Isnt there a way to alter the size of the spacebar in manila 2.1?
This is a common issue with XT9.
I suggest trying a different SIP and disabling all other settings other than ABC mode.
Hi. I have been running a couple of modded ROMs and the htc_ime i install on those ROMs is always laggy and somewhat buggy. Is it the same with standard ROM?
One of the bugs i have noticed is that sometimes, when i press space it just goes nuts and creates a period(dot) and just continues to make spaces for a short period. And this has happened on several ROMs.
It's the HTC_IME, not the ROM. the HTC keyboard is designed to put a period and two spaces when / if you hold the keyboard for too long. I haven't looked at the actual code to see how many milliseconds it is, but that is what is happening. Try to tap the space bar quicker and it should be fine.
Thanks for your reply, but thats not whats happening. I press space fast enough. I am aware of the fact that it puts out a dot if you hold it or tap it twice . It does not explain why it continues to make spaces after it makes the dot. It goes totally bananas
Its a setting.
I have a custom rom but im almost certain that the setting is a standard feature.
Its called "Add a space after dot" or equal and you should find it in the settings for input and text.
Good luck.
dicksisfontes said:
I have a custom rom but im almost certain that the setting is a standard feature.
Its called "Add a space after dot" or equal and you should find it in the settings for input and text.
Good luck.
Click to expand...
Click to collapse
I also know this is considered a feature, and I intentionally have it on. HOWEVER, there is often keyboard lag, where you can quickly tap on a key, and the software does not recognize that it was a quick tap and processes it as if you held it down for a longer period. With the space bar, you get the period + spaces. I frequently get the same effect on other keys, yielding numbers, etc instead what I wanted.
The keyboard lag is *awful* and I consider it one of the bigger usability flaws in the mytouch.
majoraccent said:
I also know this is considered a feature, and I intentionally have it on. HOWEVER, there is often keyboard lag, where you can quickly tap on a key, and the software does not recognize that it was a quick tap and processes it as if you held it down for a longer period. With the space bar, you get the period + spaces. I frequently get the same effect on other keys, yielding numbers, etc instead what I wanted.
The keyboard lag is *awful* and I consider it one of the bigger usability flaws in the mytouch.
Click to expand...
Click to collapse
Yeah i get that exact same thing. It is REALLY annoying the !#ยค% out of me
Try using Super D, I get no lag on the key board and its a great 1.6 ROM. Its possible it could be a hardware issue, try going into the dev tools and click pointer location. See whats going on with your touch screen.
phatmanxxl said:
Try using Super D, I get no lag on the key board and its a great 1.6 ROM. Its possible it could be a hardware issue, try going into the dev tools and click pointer location. See whats going on with your touch screen.
Click to expand...
Click to collapse
I am using Super D at the moment . Turning the vibration feedback off helped somewhat, but in landscape mode it is still lagging a lot. Tried pointer location, and the screen seems fine to me
FYI, I switched off the predictive text input option on HTC_IME, which got rid of just about all of the lag. It works very well with haptic feedback now. Unfortunately, there's no spell check or anything, so you may have to pay more attention but it is still preferable I think.
The basic problem seems to be that the mytouch simply doesn't have the processing capability to run close to smoothly with all the advertised features, and we have to selectively disable options to try to get a usable product. It's a shame since android itself is quite nice.
I suppose another solution would be to go into the source for one of the keyboard packages and see if it could be made more efficient, but that may be pointless as soon as better hardware comes out.
I have the TMOUS HD2 and I am having 2 problems and I want to see if anyone else is either experiencing this or if it's just my phone.
On SENSE SMS messages, the keyboard will auto deploy and I will begin to type or Swype and nothing will show, unless I select or highlight the last message and then refocused on the blank area of my current message and then it will show. It's almost as if the screen doesnt redraw the text as I input it. It's VERY annoying.
When I'm in a call, and pull the phone away from my face, the screen will come on, but I can't press or access any button on the dialpad (Eg, Red Endcall or Keypad button) but I am able to press all of the hardware buttons and go to the home screen of Sense and do everything else on the phone. This is really frustrating, because I call my bank and I can't use the touch tone features to access my account or put a caller on hold and do the other features while on a call.
I would just like to know if these are isolated incidents that I'm just experiencing with my HD2, or is there a solution to theses issues. Any help would be GREATLY appreciated. Thanks guys.
Bigcountryed said:
On SENSE SMS messages, the keyboard will auto deploy and I will begin to type or Swype and nothing will show, unless I select or highlight the last message and then refocused on the blank area of my current message and then it will show. It's almost as if the screen doesnt redraw the text as I input it. It's VERY annoying.
Click to expand...
Click to collapse
I think that's just something you have to deal with, I used to get it on the O2UK stock 1.43 ROM after installing the hotfix (I assume it's cooked into the TMOUS ROM). After installing Windows Mobile 6.5.x I haven't come across the issue.
Bigcountryed said:
I have the TMOUS HD2 and I am having 2 problems and I want to see if anyone else is either experiencing this or if it's just my phone.
On SENSE SMS messages, the keyboard will auto deploy and I will begin to type or Swype and nothing will show, unless I select or highlight the last message and then refocused on the blank area of my current message and then it will show. It's almost as if the screen doesnt redraw the text as I input it. It's VERY annoying.
Click to expand...
Click to collapse
This is a known bug that we all have. When you start typing, sense is busy loading all your txts from that contact, and when it has finished loading them it auto focuses on the last text. During that time you cannot see what you are typing, though it is still being typed. When you then select the text input area your typing appears.
The fix is to not have many texts saved.
When I'm in a call, and pull the phone away from my face, the screen will come on, but I can't press or access any button on the dialpad (Eg, Red Endcall or Keypad button) but I am able to press all of the hardware buttons and go to the home screen of Sense and do everything else on the phone. This is really frustrating, because I call my bank and I can't use the touch tone features to access my account or put a caller on hold and do the other features while on a call.
Click to expand...
Click to collapse
you have either bsbtweaks "increase tap time" tweak turned on, or the increase taptime cab from the hints tips thread.
This tweak stops the incall screen from registering presses. Turn it off.
These are both very common, and there must be a few hundred threads asking the same questions.
The BST thing fixed the call problem I was having. And imma try to clean out the sms message to regain speed. Thankyou VERY much Samsamuel and Kalavere! Luv ya like a play cousin!
So I have found the keyboard to be somewhat fraustrating. Not because it is virtual, but because of the software behind it.
First of all, it is rather strange that you cannot set more than one keybaord. Essentially, the device can have two keyboards that you might regularly swap between: the hardware keyboard and the one screen keyboard one might use while in tablet mode. The hardware keyboard uses the autocorrect of the keyboard you have set as your software keyboard. You cannot set seperate keyboard engines for the hardware and software keyboard.
As I said, the autocorrect/engine behind the hardware keyboard is dependant on your choice of software keybaord. However, as far as I can tell, only the defualt TouchPal keyboard provides any autocorrect for the hardware keybaord. The stock android keyboard offers no autocorrect with the hardware keyboard.
On a related note, TouchPal is awful. The autocorrect works pretty badly and is basically very annoying to use. I won't bore you with the details, but things like autocorrecting to a new word when you go back to edit a mistake. This makes it almost unusable.
Also the touch pad is very bad. No two funger scrolling means that again, it is pretty much useless.
I think the Yoga Book is a great device in most respects. Its intersting that all of these problems relate to the software and could potentially be fixed by Lenovo or there may even be fixes out there now.
Has anyone found any solutions to these problems? Thanks, Liam
I completely agree with you and am having the same frustration with the software behind the keyboard. So far the best solution I have found is to use SwiftKey or Swiftkey Beta (not sure which is best yet). With a bit of tweaking you can get decent auto complete and auto correct using both the halo and on screen keyboard. Much better than Touchpal at least. A couple of issues I have found using Swiftkey and halo keyboard: 1) auto complete seems to turn off when resuming from sleep mode (tapping the keyboard button on the top row reactivates it) 2) in WhatsApp Tablet app, after pressing Enter to send a message, the next message gets double words - I. E. Auto correct adds to what you type, doesn't replace it.
I can confirm that switching to SwiftKey makes the hardware keyboard usable! I'm actually using the keyboard to type this now. Naturally, I'm making tons of mistakes but it is catching and correcting almost all of them!
Can confirm that SwiftKey easily switches between physical keyboard and on-screen keyboard when the physical keyboard is toggled on and off.
If anyone is still using the default software keyboard, switch now!!!
Thanks for the tip! This makes a big difference! Have either of you found a way to get auto capitalise to work? The setting is enabled but it doesn't do anythig.
My issue with SwiftKey is that there is no good ways to select a suggested word. You always have to click with your finger on the screen which completely ruins ten finger typing for my.
So I ended up with disabled word correction as it's faster to remove some mistyped words and type again, than to click on the screen.
How do you handle suggestions made by SwiftKey?
faeArai said:
My issue with SwiftKey is that there is no good ways to select a suggested word. You always have to click with your finger on the screen which completely ruins ten finger typing for my.
So I ended up with disabled word correction as it's faster to remove some mistyped words and type again, than to click on the screen.
How do you handle suggestions made by SwiftKey?
Click to expand...
Click to collapse
I have found that SwiftKey enters the main suggested word when I press space. This is good for most of the time, but annoying when:
-I want to select a suggestion that is not the main suggested word (particularly a new word that it doesn't recognise)
-I want to add punctuation directly after the main suggested word (here, because I input the punctuation rather than pressing space, the suggested word is not entered)
I have certainly found using SwiftKey to be the best experience. It's quite a passive autocorrect that doesn't get in the way too much. I got so sick of TouchPal which really gets in your face with its incorrect predictions.
But still there is a lot of room for improvement. It's such a shame that it's terrible software that lets down this keyboard. In particular I don't understand why:
- Some keyboards (like the Google Keyboard) don't offer any correction or prediction when enabled. Does Android maybe treat the Halo keyboard as an external keyboard (which I suppose you wouldn't want predictive features for)?
- Keyboards that do offer prediction don't seem to respond to changes to their settings (I can't get SwiftKey to auto capitalise the first letter of a sentence for example). @thespinner02 mentioned tweaking with SwiftKey settings- I assume they meant for the onscreen keyboard because these settings don't do anything for the Halo keybaord.
I wonder whether there is a keyboard out there in the Play Store that works better with the Yoga Book. I'll try a few and let you guys know if I find one.
I tried several solutions but couldn't find anything good. Hardware keyboards are not that common on Android platform, I guess.
Even using Swiftkey I sometimes get different results depending on the app being used. Auto capitalise is working OK for me, in Word for example.
There are specific options in Swiftkey for Physical Keyboard: in settings, Typing, Voice & Other Input. In Physical keyboard section I have Autocorrect and Auto capitalize on. Everything else off.
thespinner02 said:
Even using Swiftkey I sometimes get different results depending on the app being used. Auto capitalise is working OK for me, in Word for example.
There are specific options in Swiftkey for Physical Keyboard: in settings, Typing, Voice & Other Input. In Physical keyboard section I have Autocorrect and Auto capitalize on. Everything else off.
Click to expand...
Click to collapse
Thanks! I didn't notice that- smart spacing etc makes a massive difference!
Pretty much my only problem with SwiftKey now is that it sometimes creates its own weird textbook instead of typing directly into the text field. But that's not a massive problem.
Also I sometimes accidentally change input method. Maybe I'm using a keyboard shortcut by mistake?
thespinner02 said:
Even using Swiftkey I sometimes get different results depending on the app being used. Auto capitalise is working OK for me, in Word for example.
There are specific options in Swiftkey for Physical Keyboard: in settings, Typing, Voice & Other Input. In Physical keyboard section I have Autocorrect and Auto capitalize on. Everything else off.
Click to expand...
Click to collapse
In settings for hardware keyword I get no harder key found?
Went into Swift settings in onscreen. How to get settings for Halo?
With Yoga Book in laptop mode. Settings / Language & input / SwiftKey Keyboard / Typing / Voice & Other Input
You also need to make sure 'show input method' is not enabled in the keyboard settings/selector popup.
Does anyone else experience a problem with SwiftKey where in some text fields your text goes into a little popup text box at the bottom of the screen as well as the intended text field? And then to get rid of the popup text box you have to tap 'next'. This occurs in the Facebook messenger app for example.
Any way to disable it?
It seems to do this when the text field is small, but other keyboards just expend the text field as you type. The popup text box it creates doesn't expand anyway, so it doesn't offer extra functionality and is just an annoyance.