I own a Motorola phone that is constantly thwarting my texting efforts. My phone is endowed with a interpretive text function that is supposed to help it learn what I am most likely trying to say. But apparently my phone is a little squeamish, because, when typing "butt", my phone will first offer me "butv", followed by "but8". (At this point you might be wondering why I'm talking about butts so often. Consider these possible text sentences -
- Hey, you have something on your butt.
- Nice butt.
- I have a butt.)
Finally, on the third try it will produce "butt". Oddly enough, the second I throw an "F" afterwards, my phone immediately and accurately predicts that I want to call someone a buttface.
What drives me the craziest, is that butv and but8 are not words. I want to know what phone programmer sat down to program my phone and thought, "In the occassion that someone dials 2-8-8-8, I assume they are having a discussion about butv's."
- Hey, there are butv's all over the place.
- Quit goofing around with that butv.
- Have you considered some of these butv's?
But the trouble doesn't end there. Whenever I try to say "Hey", my phone quickly picks up on the fact that I very well might be trying to say "Hew". And if not Hew, then I am most definitely talking about a "Hex". I am glad Motorolla is catering to the needs of ax-murderes, gardners, and magicians.
When I try to talk about a taco, my phone realizes that I'm probably trying to communicate my feelings about tabo... which is a Philippino alternative to toilet paper. All of this from a phone that can perfectly interpret when I want to say "Nintendo64". (Something Bridger shared with me about his phone years ago, but I hadn't experienced until now.)
This needs to stop. Whoever the ax-murdering, gardner, magician, philippino, Nintendo 64 enthusiast who is programming these phones is, he needs to be stopped.