Motorola Q: Equine Excrement
A little over a year ago, I underwent an utterly hellish process to stay loyal to Sprint and get a Motorola Q. One day, I may document this on the blog, but not today. I have all the e-mails saved, and the memory of the multitudes of phone calls with incompetent, undertrained, ineffective "customer" "service" "agents" will be forever seared into my memory... I imagine that if I ever get Alzheimer's and forget my own name I will still remember the pain that this process caused.
You would think that enduring that kind of pain would net something worthy of the process. Unfortunately, after a long year of continued frustration and just astonished, flabbergasted bewilderment, I now find it necessary to document all the ills of this phone. I don't know if these problems are Motorola's fault, Sprint's fault, or Microsoft's fault, but frankly, I don't give a damn. The phone is the technological equivalent of equine excrement, and every day it surprises me in some new way. 90% of the stress in my day comes from traffic, but the remaining 10% comes from my having to use the Motorola Q.
- First off, the hardware... about the only good thing I can say about this phone is that it is built fairly solidly. I've dropped it a couple of times and it's held up well. Plus, the sexy black rubberized-for-your-pleasure finish is not only aesthetically pleasing but also functions to assist in grip.
- There is a set of maladies which I would like to characterize as "poor battery life," but that doesn't even begin to tell the story. In fact, it's kind of misleading, because on a brand new battery, it was acceptable. That is to say, on a full charge when the battery and phone were brand new, I could go an entire day with a little surfing, a little talking on the phone, and some SMS messages without having to worry too much. Unfortunately, within 6 months, the battery life began to drop noticeably. I am a fucking battery hound, period. I am so anal about my batteries that I have a spreadsheet to track the charge that goes into each and every NiMH battery that I own (I have a special charger that lets me cycle each battery fully on every charge and track the energy put into every individual cell). So don't tell me about how to properly take care of batteries. My last phone, a Samsung Palm device, was still holding charge on its battery at a level indistinguishable from brand new 3 years later. On the Q now, if I make it through a whole day without getting a low battery warning, I go and buy a lottery ticket because it's my fucking lucky day.
- What's even more frustrating is that the phone will literally turn itself off as if the battery died for no reason whatsoever, randomly. I can be sitting there with 3 bars (out of 4) on the batt indicator, and five minutes later, I look at my phone, and it's fucking taking a personal day. When I power it back on, it comes up with a random number of bars. Sometimes, it's 3 like before it turned itself off, sometimes it gives me a low battery warning with 0 bars. What a piece of junk. I'd pick up a spare battery, but I refuse to give Motorola more money for a defective product.
- The "flash" on the camera must be short for "flashlight" because it is not a "flash" in the photographic sense of the word.
- Software-wise, it's just unbelievably buggy. They couldn't even get something as fundamental as dialing right. When you're on the "home" screen and press a number, it is supposed to put you into dialing mode. The numbers you press show up at the top, and simultaneously, it brings up possible matches for the letters underneath out of your address book. This is pretty standard for any mobile phone since, oh, I dunno... 1990? But no, not on the Q. Right now, as I type this rant, if I hit any number or letter from the "home" screen, what do I get? My fucking calendar.
- Also, there is an entire friggin' qwerty keyboard on this phone. You'd think you'd be able to dial 1-800-MOTO-SUX but no. You have to translate the letters yourself and then dial the numbers. How hard would it have been to include some "letter dialing" mode? I mean, I don't even need it to be automatic. I'd be fine with having to press alt- or shift- or whatever. But no. Nothing.
- Don't even get me started on IE.
- ActiveSync is neither active nor does it sync. It is a royal pain in the ass to use, and frankly I doubt that 99% of people who don't have professional IT support have ever sync'd their Q's to their Windows machine. And if you want to sync over Bluetooth, you might as well hit any number or letter on your Q to bring up your calendar so you can cancel your appointments for the next three days because that's how long it'll take you to figure that shit out.
I'll continue to post the misadventures I have with this phone, which I am convinced must be standard issue in Purgatory. After all, I am locked into this contractually for another year thanks to the orifices which are the telcos. But as long as I have to put up with this crap I might as well get my word in edgewise on it.
Comments
- More often than not (probably 80% of the time) it takes several button presses to wake the phone up from "sleep." ie. just to get to the "unlock" screen if it was locked before. Of course, combined with the already documented defect of the darn thing turning itself off for no reason, this leads to several moments of "god fucking damnit the fucking phone turned itself off again" before, suddenly, it decides to actually wake up.
- The power button has gone AWOL all too often. Sometimes, it won't turn off even if I command it. Pressing and holding doesn't help either. I have to actually remove the battery. Sometimes, it won't turn on! So far, hard resetting it by taking the battery out solves the problem. Related to this, even when the power button works, it usually takes several presses and holds before the phone realizes that I'm trying to tell it something. Either that or it actually responds to voice commands where "fucking piece of shit!" means "on/off."
- Today, it got stuck in all caps mode for no reason, and no matter what I pressed in terms of shift/alt keys, it would not get out of all caps. Yay.
- Relatedly, perhaps, backspace stopped working for no reason as well. Yay.
Let me say again: I don't care what fancy frills are on the phone if it cannot be relied upon as a PHONE. This thing is useless.
Using the video "function" will crash the phone so hard that you have to remove the battery to restart it. Not on a one-off type thing, but with a fairly regular repeatability. Awesome.
When I am done with this phone, I am not going to donate it to a serviceman or to Cuba or to some other cause. I wouldn't wish this phone upon George W. Bush himself. When I am done with this phone, I am going to get my new HD camcorder out and I am going to document its destruction by excessive prejudice. And then I am going to submit the video to the nominating committee of the Nobel Peace Prize because I feel like I will have done as much for world peace by destroying this diabolical phone as disarming ten nuclear warheads.
TURN ON.
Went to bed last night with 4 bars of battery (out of 4, remember). Turned the phone OFF. Not turned the radio off, not sleep mode... OFF. As in "Good Bye."
Woke up this morning. Dead. Wouldn't turn on.
Now the great thing about this phone is that Motorola decided that they wanted to force you into buying their special accessories, so the phone will not charge the battery if you plug it into any other power source other than a Motorola-approved charger or via USB to a computer that the Q can communicate with. How do I know this? From experience, my friend. This is not documented anywhere in the scant literature I received with the phone from Sprint, nor was it disclosed by any Sprint employee. I mean, c'mon, these morons couldn't even subtract 100 from 200, what do you expect?
Anyway, the gist is that you cannot plug this phone into the USB port of a Mac and even have it *charge*. I mean, I could almost understand a Windows Mobile device not wanting to play nice in terms of syncing with a Mac. But charging!? What the fuck, you assholes.
Now how did this cause my phone to not even turn on this morning for 20 minutes? I am not sure, but here's my theory: because the battery was so completely dead, there wasn't even enough power left in the battery to power whatever circuitry/firmware/software that allows the phone to decide whether whatever you have plugged into it is a "legit" charge-able USB power source (as defined above). So the phone wouldn't even charge when I plugged it in.
I removed the battery and tried to just power on the phone while it was plugged into the USB port of my laptop here at work. No dice. Don't ask me why.
After a while, I somehow managed to get the thing to start charging the battery. I can't remember exactly what combination of tricks I had to pull to achieve this, but the gist of it is that I tricked the phone into letting me charge the battery for a few minutes, which was enough to get it to power on. But here's the thing! I couldn't even get it to power on while it was charging. I had to let it charge, then unplug it, power it on, wait 'til it got to the home screen, and THEN plug it back in to resume charging normally.
Suffice it to say I am never, ever, buying another Motorola product again. I am probably also never buying a Microsoft Windows Mobile device ever again too. And other than this blog, I have made it abundantly clear to anybody who asks what I think of this phone. Not only that, but I actively wish ill will upon those who brought this phone into existence.
I let the battery die yesterday night out of neglect (didn't really feel like I needed to take any calls on Father's Day). So this morning, I brought it into work and plugged it into my computer via USB as I have done in the past many times. Somewhat to my surprise, the phone started to charge the battery.
Knowing the history, I waited for a few minutes before turning on the actual phone so as to not unduly strain the delicate balance of power within this prissy little brat of a phone. When I finally did turn on the power, I was surprised by two things: 1) the phone turned on, and 2) not only did it turn on, but it did so on the first try.
Now I'm thinking, "holy shit I'd better get on a plane for Vegas RIGHT NOW."
Fortunately for my wallet, the phone almost immediately rescinded this thought. Within a few moments, all USB devices attached to my computer stopped working. The phone was still charging, but my keyboard and mouse were dead. And ActiveSync no longer recognized the phone as being attached (of course it was in the middle of a sync).
The good news is that a restart solved this problem. The bad news, of course, is that not only does this phone stink, it's contagious. Anything you plug into it is liable to fail, explode, and burn in flames. You couldn't design a better WMD...
By comparison, my old Samsung had a call history that, as far as I could tell, was limited only by the size of storage available. I had that phone for three years, and on the day I stopped using it, I could still browse all the way back to the very first phone call I'd made on it.
When is this ever useful you might ask yourself? Well, most of the time it probably isn't. But say you're involved in a legal case and you need to establish some facts around when phone calls were made, by whom, and to whom. Suddenly this "useless" feature could worth quite a bit.
Alas, the Q disappoints yet again.
That being said, having that dump acts as a starting point in research and is nonetheless helpful. The point is, the Q doesn't even have that.
I have mentioned before how unreliable this device is as a PHONE. At various times, I have been unable to dial numbers, dial letters, the thing has crashed while answering an incoming call, etc... but this weekend, while I was stuck 15 miles from civilization with a dead car battery, the Q gave me quite a scare.
Having returned from a climb in the mountains, my party found our car to be dead. Having smartly turned off the Q so that it wouldn't waste battery during the climb, I now powered it on and proceeded to attempt to call a friend for help. Instead of making the call, the phone replied, "The Operation Failed." The only option was to click "OK." Subsequent attempts to other numbers resulted in the same error message.
First of all, let me say that IT IS NOT "OK" when my phone cannot make phone calls. So don't make me press a button that implies my consent to this failure. Fuck. You.
The story has a fortunate outcome: I was able to reach my friend after restarting the phone, but before he even had to come out, other hikers happened to come by and aided us.
However, I can't help but think what the consequences would be if I needed to make an emergency call to 911 and the phone failed like this. What if someone was having a stroke or heart attack? Waiting for the piece of junk to reboot costs at least a minute or two... time which, I'm sure you know, is quite precious in these situations.
This phone is downright unsafe.