Important to note that he says "...shrinks the target area..." not "prevents the use of those keys", but this isn't the point and is semantics and interpretation so we'll agree to disagree. I could also argue that "krsne..." isn't close to any common words that would be in the dictionary.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Unfortunate iPhone bug...
- Thread starter krsnet
- Start date
- Sort by reaction score
Important to note that he says "...shrinks the target area..." not "prevents the use of those keys", but this isn't the point and is semantics and interpretation so we'll agree to disagree. I could also argue that "krsne..." isn't close to any common words that would be in the dictionary.
As long as your info is legit (no reason to doubt it), I guess it comes down to a screen calibration issue... On my screen and several others, the "shrinks the target area" function actually eliminates the ability to type the keys while your screen still allows the ability to access the button...
Too bad there isn't a published way to recalibrate...
Mine's the same. Under Keyboard settings I have Auto-Caps on, and Enable Caps Lock off.
I wonder if it's maybe a 7-series versus 5-series difference. I heard people talking about how they had different screens with different series.
I have a 5-series. You just dial *3001#12345#* and go to versions. And it's the LCD Panel ID.
I doubt that has anything to do with the on-screen keyboard though.
Are you sure you're not able to get "krsnet" added to your dictionary by creating a "Krsnet Krsnet" contact with nothing else? Make sure it saved it by going to contacts and looking for it.
It comes up as a correction for me when I enter "krsn" after I added that contact.
I'm sure... I have a "krsnet krsnet" contact with no additional info. Even did a sync to make sure it showed up on the Mac without any luck.
Based on a recommendation from someone on another site, I tried to do the official "add to dictionary" function without luck either...
So far, the only thing I've found different is my screen is a "7-series" (7455232). I've played around in that tool for tower signal strength, but I didn't realize it also had an LCD panel ID. I'd be curious to know if the other one's that "work" are 5 or 7 series...
You do have a point there. It's also a little disconcerting that some iPhones seem to be able to "learn" that krsnet is intended, while others apparently can't.
Mine is a "7" series (7455232), and has the same behavior as yours. So maybe it is a "[un]lucky-7" thing.
I have a 7 series screen and 8gig (although i don't think it matters)
(*note i did not add a contact to get it to work)
What i did was open note pad typed "krsnet" 5 times correcting it everytime it gave me "krsney" or "krsner" by using the delete key and manually changing the word. Then i saved the note. Then i deleted the note.
i think by creating a note with the word and saving it helped train my dictionary to recognize the word.
Now when i type "krsnet" in SMS, SAFARI or NOTES it recognizes the word as part of my dictionary. Try it maybe it will work for you.
(*note i did not add a contact to get it to work)
What i did was open note pad typed "krsnet" 5 times correcting it everytime it gave me "krsney" or "krsner" by using the delete key and manually changing the word. Then i saved the note. Then i deleted the note.
i think by creating a note with the word and saving it helped train my dictionary to recognize the word.
Now when i type "krsnet" in SMS, SAFARI or NOTES it recognizes the word as part of my dictionary. Try it maybe it will work for you.
I've already typed and corrected "krsnet" a bazillion times already today in different notes, emails, and web forms...even cleared my "keyboard dictionary" a few times along the way via the "Settings -> General -> Reset" function...none of it worked... BUT...after reading your message I went through the process again.
Some combination of the following finally worked so I can now, finally, after wasting a day of work (luckily work out of a home office...)
* I deleted a contact with the last name "Kramer" (I don't think this was related since it still guessed Kramer later...)
* I reset my keyboard dictionary
* I created a note with many corrected "krsnet". Some I did the "tap" on the word according to the manual, some I just went to the next krsnet... This by itsself did not appear to make a difference.
* I created an e-mail with multiple corrected "krsnet's" and sent the message.
* I went back to Notes and now I can, at long last, successfully type "krsnet"
Not sure which combination of events actually fixed it, but now that I can finally type it, I'm not going back to try to figure it out...
Thanks and glad it wasn't related to the mythical 5-series vs. 7-series discussion (I'm staying out of that thread....)
Bizarre.... even after correcting he word, it will not let me type it.... It's like the 't' isn't there....
that is weird even when you try to drag your finger across the keyboard it will just skips the t. But hey its not like the spell correction function works all the time anyway!
i think it does have something to do with the autocorrect, because I saw the same problem (it did actually try to correct it with kramer at one point, not sure when it stopped.. kind of forgot) and i couldn't type the t. once i corrected and then saved the note and went back and tried typing, it allowed the t just fine.
odd...
odd...
For me, the update did not fix it. No matter how hard I try I can not touch the t after having typed 'krsne'. Strange.
Maybe we'll have to live without beeing able to type 'krsne'
That would be a sad day for the world......
Hunch is they were joking when they said the update "fixed" it. Like I mentioned above, I was finally able to get it going even though I can't explain why doing things I'd already done multiple times finally added the word to the user dictionary.
I still think its a bug (or a bad decision) to completely block a keypress. Reducing the target size is a nice typing feature, but to outright eliminate the possibility to press a key....I hope the algorithm is smart enough to know every possible combination of keypresses and krsnet is the only one they missed...
Anyone in a programming discipline knows as soon as you block a certain path because you can't imagine why a user would ever need to do "that", they have a legitimate need to do "that"....
FIXED in 1.01
Hey, the krsnet bug is fixed in the update--I just tried it in the notepad app, and it seems to be working fine.
The iPhone is now krsnet friendly!
Oops... I see this was mentioned. Well, it fixed the bug for me. Previously, I was duplicating the krsnet bug in notepad. Now I can type it easily.
I'm not joking.
Maybe something else did it, and I just assumed it was the update. Anyway there is some hope for you krsnet, because mine previously did not type krsnet and now it will.
But yeah, this is definitely a bug, not a feature. I can type all kinds of nonsense on my iPhone, and often do.
Hey, the krsnet bug is fixed in the update--I just tried it in the notepad app, and it seems to be working fine.
The iPhone is now krsnet friendly!
Oops... I see this was mentioned. Well, it fixed the bug for me. Previously, I was duplicating the krsnet bug in notepad. Now I can type it easily.
I'm not joking.
Maybe something else did it, and I just assumed it was the update. Anyway there is some hope for you krsnet, because mine previously did not type krsnet and now it will.
But yeah, this is definitely a bug, not a feature. I can type all kinds of nonsense on my iPhone, and often do.
Weird - maybe Apple monitors this website and threw in the "krsnet" fix at the last minute!
Thanks again to all for the help and enjoy typing my screen name... Hopefully they did change the algorithm so that the maximum/minimum target size still allowed those unexpected keypresses...
NOT fixed in 1.01 after all...
Hmm... Now it is not working again. I swear, it did work before. I guess it's possible I was typing ksrnet or something by mistake when it was working for me.
Hmm... Now it is not working again. I swear, it did work before. I guess it's possible I was typing ksrnet or something by mistake when it was working for me.