Develop Bugs

Letters/keys skipped when typing in WM6 (ONLY in the messaging application)

When I am typing in the messaging application, I find that many of my key presses are ignored, seeming as though I am not able to spell or use proper punctiation, even though I have actually tapped the correct keys.
My messages might look like the following:
"Thaks fo your message. I was nt able to take the call at th time buI will be avaiable after 6pm. Thanks again!"
This is really annoying. It ONLY happens in the messaging application. I can type an entire document in Word without a single problem but I correct numerous mistakes in emails and text messages in order to avoid looking like a moron to recipients of my messages.
Is there anything I can do to correct this problem? I am using the Black Edition ROM right now and thought that this version fixed the problem. I also Experienced it with the LVSW versions and the other before that. I did not experience it in WM5 at all...

pinhead said:
When I am typing in the messaging application, I find that many of my key presses are ignored, seeming as though I am not able to spell or use proper punctiation, even though I have actually tapped the correct keys.
My messages might look like the following:
"Thaks fo your message. I was nt able to take the call at th time buI will be avaiable after 6pm. Thanks again!"
This is really annoying. It ONLY happens in the messaging application. I can type an entire document in Word without a single problem but I correct numerous mistakes in emails and text messages in order to avoid looking like a moron to recipients of my messages.
Is there anything I can do to correct this problem? I am using the Black Edition ROM right now and thought that this version fixed the problem. I also Experienced it with the LVSW versions and the other before that. I did not experience it in WM5 at all...
Click to expand...
Click to collapse
I have the exact error with all the WM6 roms, very very frustrating

I too sometimes get this problem, normally at the start of a text if I start typing quickly. it doesn't happen all the time tho only occasionally. using the lvsw rom at the moment but also had it with the SA WM5 rom

I've got this problem too, but in WM5.

same here on WMXL 0.2

I have noticed this on other WM5 devices but never on the Hermes until now. Is there something that changed in the messaging application that can be changed back to the way it was in WM5...hopefully via a registry edit?

pinhead said:
I have noticed this on other WM5 devices but never on the Hermes until now. Is there something that changed in the messaging application that can be changed back to the way it was in WM5...hopefully via a registry edit?
Click to expand...
Click to collapse
I had this problem but it went away after I selected the option to have word completion only select words after typing six letters. If you have it set to do it after pressing the space bar it seems to cause a delay in typing the text after a key press.

I agree with nmonger, I have alleviated the problem by setting the autocomplete to only suggest after 3 letters (it was set to "a space" before). Also I have made it only suggest 2 words (it was set to 4).

I had this from day 1, it`s just not designed to work that fast...
i hope it`s a driver problem and not keyboard hardware problem.

nmonger said:
I had this problem but it went away after I selected the option to have word completion only select words after typing six letters. If you have it set to do it after pressing the space bar it seems to cause a delay in typing the text after a key press.
Click to expand...
Click to collapse
So far this seems to have solved my problem. Thanks!

I knew it had something to do with the word completion. I set it to suggest 1 word but it keeps suggesting four. I just changed it to after 3 letters and solved my problem. Thank you for pointing that out. Now i don't look drunk when messaging at 11am!

Thank the man above someone else is having this issue as well....trying the word completion trick and seeing what happens.

worked for me - great solutions thanks

BINGO! an obvious solution in hindsight... thanks

cheers for that guys, it was one of those things that had bugged me for a while but not enough for me to look for a fix untill someone else mentioned it.

nmonger said:
I had this problem but it went away after I selected the option to have word completion only select words after typing six letters. If you have it set to do it after pressing the space bar it seems to cause a delay in typing the text after a key press.
Click to expand...
Click to collapse
Worked for me

I was just thinking about how often I had this issue today. I was SURE I was pressing all the keys. I tried turning word completion off and that didn't seem to change anything (strange). I'll give changing it to 6 a try, that makes sense.

I have noticed this problem on the Dash, Blackjack, Universal, and a few other Windows Mobile devices...all WM 5 and newer. This is the first time I have seen a solution. I don't think this worked on any of those devices and that is why I posted. I thought there was going to be a more complicated fix on this phone too!
What really stuns me is the lack of complaining about the skipping issue on other devices, such as those that I mentioned, as I am sure I am not the only one who sees this happening on multiple devices.

I thought it was all down to me being lazy, a bad speller and having thumbs too big for the small keyboard.
Trying the solution and all seems well so far.

thanks a lot, it's working

A-Button Glitch

I've found myself back here on the forums after getting frustrated with the official Windows updates.
There's a really big glitch I've encountered that changes the volume from Normal to Vibrate or vice versa.
It took me years to finally realize why my phone was switching profiles without me changing it.
Whenever I start a new text message and type the letter 'A' too fast as the first letter of the message it changes to Normal/Vibrate. If I slowly start typing the message, the glitch is avoided.
Has anyone else encountered this bizarre problem? I'm still trying to figure out how this could even be possible! Any suggestions from the gurus?

This problem exists on ALL Roms I believe ... I have always had it.
Here is the explanation, as I see it:
The Texting program, in all honesty, sucks. Windows decided to create the TextBox before loading up the history of messages, which meant there was a huge lag. FURTHER: They didn't do these actions on separate threads, which means the lag would occur on one thread.
Now think of it this way: While a program can have different 'threads' to run on, the keyboard, while an input to the program, will get its own thread because it is a system device. So the Keyboard gets its own thread, therefore its own buffer.
What goes on, in the second it takes to load the text message history is this:
1) TextBox appears and is activated to user [and Keyboard]
2) History load starts on same thread as TextBox
3) User types "A"
4) "A" is sent to the foreground window, which is the TextBox
5) The TextBox takes a while to respond, to process the message, therefore the system assumes the key was held down for X seconds.
6) Realizing this is the Hard-coded "change-profile" shortcut, the system then sends a message to the Profile 'manager' (if one exists, but in theory let us say it does) to switch profiles.
7) The TextBox stops lagging since the history is loaded, and it registers that the 'A' key was lifted.
The whole issue has to do with timing and buffers ... all pretty stupid errors on Microsoft's part.
I had wanted to start making a replacement, but alas, I have no time
One day....maybe one day

Brilliant Cyclone! Thanks for the simplified/understandable response.
I didn't realize the quick button to switch profiles is the 'A' button. That's much more understandable.
I just updated my phone to 3v0, but then downdated to 1.22.531.6 because it 3v0 was too buggy.
It cleared all my text messages and I haven't had the A-glitch yet. I'm guessing clearing the text history is the only way to avoid the glitch.
I'm surprised I haven't heard other people talking about this problem. I Googled it, but couldn't find anything.
Very interesting...although, these kind of problems are expected when dealing with Microsoft.

I just had a thought...
How easy would it be to change the "Hard-coded "change-profile" shortcut" to a letter that is never used? Like 'Q'. Or completely remove the change-profile shortcut.
You guys are way over my head when it comes to working with the fundamentals of phones(the registry?) like this. I'd like to learn more, but I must also say....One day....maybe one day!

I don't honestly believe it is possible..."hard coded' means that they programmed it straight into the OS.
Now realize, this is only my theory, I can be 100% incorrect..

The OS can't have any changes made to it? I thought this was possible through something like "regedit" on PC's. Changes to the registry aren't changes to the OS?

zemaoner said:
The OS can't have any changes made to it? I thought this was possible through something like "regedit" on PC's. Changes to the registry aren't changes to the OS?
Click to expand...
Click to collapse
Things in the Registry aren't 'hardcoded' ... when I say 'hardcoded' I mean that when Microsoft employees was in their IDEs developing, they typed in a few lines of code dealing with the A-Key, and then compiled it. We cannot change that, especially since it is part of the ROM.

AOKP Keyboard Bug

I notice it less in 4.0.4, but it's still here. Here's what happens:
Sometimes if I have a thread open, I can either start typing and then all typing will stop, or no typing will start from the get go. What I mean is I tap the keys and nothing shows up in the message box. In build 28 I had this happen only from the get go once in a while, now it also happens sometimes when I'm part way through a message. The only way to fix it is by hitting back to go to the main messaging screen and going back to my thread. If I do this with a partially written message then all the text is erased when I go back. Highly annoying.
Has anyone else experienced this, or know of a fix?

I have problems with this on my SII, but i ran CM9 for a while and I don't remember it happening there so i think it is AOKP specific.

Solution for a laggy/choppy keyboard?

So I'm sure everyone has experienced performance issues when typing stuff on their keyboards. I use Swiftkey 3 and for a long time I thought it was simply performance issues with the keyboard itself, but after testing the stock Samsung keyboard, I get the same performance issues. Basically there is delays while I type, and I've linked it mostly to when the phone is doing some system-intensive task such as using the radios to send a text or receive a text.
The best way to test it is by opening up your SMS app, type up a quick text and send it. While the text is sending (usually takes a few seconds in most cases) start typing another text and you will see a significant drop in performance from your keyboard, and really everything else.
Is there a reason for this? Does it have anything to do with Android's process prioritization? Most importantly, can this be fixed?

[Q] Massive lag for a single contact on stock SMS app

This started happening pretty much immediately since I installed the 4.4.3 update late July, and has just gotten worse.
For a single one of my contacts, the SMS app lags HORRIBLY whenever I am doing anything with said person. It takes about half a minute just to load when I click his name, and the phone keeps completely freezing for up to 10-15 seconds EACH letter I type! It's not just the SMS app itself, but even the keyboard freezes up and is unresponsive. I can keep typing and it will apparently actually record the next 30 or so taps and just blaze through them ... then lag for another half minute or so again. None of the settings (how little there are) have had any effect. Once I click send the message also takes a bit before it appears and starts to send. Any action with this contact open in the SMS app seems to lag my phone like a unusable nightmare.
Since this is the person I tend to text the most, I have been tempted to crush the phone in my hand at this point. It is ONLY happening with them, and ONLY after the 4.4.3 update. It's not consistent either; I was still having this issue earlier today, but right now as I wanted to text him again it was working perfectly lag-free.
I know the first response anyone is going to say is to wipe my phone, but with this being the only issue I have, I really do not want to completely obliterate everything and start over from scratch just to fix one person in my SMS app. On top of that, I want to keep my SMS texting history as well. (Plus I would have no idea if restoring a backup wouldn't also restore the issue).
Has anyone else encountered or heard of anything like this? Or has any ideas of anything OTHER than wiping the phone or my SMS history I can try? Considering the app only pre-loads the last 10 or so messages when you open a contact anyway, I highly doubt it's my history. I am going nuts with this stupid thing.

It is probably something in that message thread.
Deleting all messages from that person will surely fix it, based on what you've said.
You can try wiping the messaging apps cache. Other than that, I think you're stuck.

Second the opinion above. If it's only one message thread doing it, seems likely it's something unique to that thread. Too many messages, pics, etc. I used to use Titanium Backup to save messages between rom flashes, back when I cared about them, so a backup app can save the messages, let you delete the thread and see if it still happens with a blank slate.