What is it with cell phones anyway. It's primary function, while I admit is not a function I do that frequently compared to other things, it can't do all that well. I mean calls but I don't mean hard to hear connections and dropped calls. Those are problems too however just the mechanism of placing the call...
First off - never make a fucking phone dialing app that is incapable of accepted a paste of a phone number!!! You'd think that'd be a no brainer but way too many phone dialers do not allow paste. So you find a number in a web page or an email or you put it in a file - whatever. You select the phone number and you go to the phone app and want to paste it in. There's no paste. Stupid phone!
Secondly you would think that a phone application would be, oh, I don't know.... RESPONSIVE PERHAPS. Many play back those button tones we all know and love. But most phones can't keep up with even the slowest of typists. How hard is this to sense the button was pushed and immediately (I mean right away, with out hesitation - IMMEDITATELY!!! - did I say immediately?) play the fucking tone and be ready for the next button push. Come on folks, this is not rocket science nor is this a lot of work that the phone needs to do in order to accomplish this minor fucking miracle - yet on both Windows Mobile based phones and now my Android based phone this constantly happens. Is it hardware related? Again, how much hardware is needed?!? My old land line never seemed to have an issue accomplishing this task - why can't my $$$ phone do it?!? Write the damn phone app in assembler and make it (and the tones for that matter) memory resident so you have no excuses WRT speed! Really is this too much to ask?!?
And another thing about phones - why is it that the most common things I do require push and hold in order to work. Not just phones, sometimes accessories. For example, my Bluetooth headset of choice (Sony Ericson HBH-980) has a recessed power button and you must hold for a few seconds to turn on. Now I understand the concept of requiring such a delay to distinguish between a real turn on/off event and an inadvertent one but trust me you would not be inadvertently hitting this power button.
And why is it that I must always wrestle with Bluetooth to get it to work right. My BT headset can handle both "Media audio" (from the media player) and "Phone audio" from say and incoming all. Why the distinction? I don't care. Just call it audio. You don't know how many time I try to connect my BT headset and only the phone audio gets connected. No media audio. So I try to connect again. No go. Try powering off the BT headset and back on. Nope. Try turning off BT on the phone and back on No go. Then the phone hangs. Bluetooth is the only thing that seems to have the power to hang my phone, requiring me to open the case and yank the battery in order to reboot!
And then when listening to Bluetooth often I'll get gaps of silence, especially when starting a new song or podcast, as if it needs to buffer stuff or whatever. It's real annoying. Why is Bluetooth so hard, flunky and trouble ridden?!?
First off - never make a fucking phone dialing app that is incapable of accepted a paste of a phone number!!! You'd think that'd be a no brainer but way too many phone dialers do not allow paste. So you find a number in a web page or an email or you put it in a file - whatever. You select the phone number and you go to the phone app and want to paste it in. There's no paste. Stupid phone!
Secondly you would think that a phone application would be, oh, I don't know.... RESPONSIVE PERHAPS. Many play back those button tones we all know and love. But most phones can't keep up with even the slowest of typists. How hard is this to sense the button was pushed and immediately (I mean right away, with out hesitation - IMMEDITATELY!!! - did I say immediately?) play the fucking tone and be ready for the next button push. Come on folks, this is not rocket science nor is this a lot of work that the phone needs to do in order to accomplish this minor fucking miracle - yet on both Windows Mobile based phones and now my Android based phone this constantly happens. Is it hardware related? Again, how much hardware is needed?!? My old land line never seemed to have an issue accomplishing this task - why can't my $$$ phone do it?!? Write the damn phone app in assembler and make it (and the tones for that matter) memory resident so you have no excuses WRT speed! Really is this too much to ask?!?
And another thing about phones - why is it that the most common things I do require push and hold in order to work. Not just phones, sometimes accessories. For example, my Bluetooth headset of choice (Sony Ericson HBH-980) has a recessed power button and you must hold for a few seconds to turn on. Now I understand the concept of requiring such a delay to distinguish between a real turn on/off event and an inadvertent one but trust me you would not be inadvertently hitting this power button.
And why is it that I must always wrestle with Bluetooth to get it to work right. My BT headset can handle both "Media audio" (from the media player) and "Phone audio" from say and incoming all. Why the distinction? I don't care. Just call it audio. You don't know how many time I try to connect my BT headset and only the phone audio gets connected. No media audio. So I try to connect again. No go. Try powering off the BT headset and back on. Nope. Try turning off BT on the phone and back on No go. Then the phone hangs. Bluetooth is the only thing that seems to have the power to hang my phone, requiring me to open the case and yank the battery in order to reboot!
And then when listening to Bluetooth often I'll get gaps of silence, especially when starting a new song or podcast, as if it needs to buffer stuff or whatever. It's real annoying. Why is Bluetooth so hard, flunky and trouble ridden?!?
No comments:
Post a Comment