Motorola Q: Equine Excrement

Comments

I promised to update this, so here are the various problems I encountered over the past week or so:

- 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.
This one is great: instead of ringing today, my phone decided to crash and restart. Yay! It rang for about a tenth of a second, then was so polite as to say "Good Bye" and restarted itself.

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.
The Motorola Q: Constantly Amazing Me with New Ways to Suck.

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.
And now, after the battery dies literally 15 minutes after I see the indicator with 2 bars, the phone refuses to charge or turn on even if I plug it in.... unless I also remove and replace the battery.

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.
Just spent the last 20 minutes trying to get the phone to...

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.
This one is novel...

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...
Maybe this one is a little nitpicky, but the Q's call history apparently only goes back two months, and this parameter cannot be altered by any menu item. (I imagine you can hack the registry or something, but I'm disinclined to put too much effort into a phone that I intend to use for the minimum remaining obligated period.)

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.
Not that anybody every reads or comments on this blog anymore, but before someone repsonds to the above by saying I can just get a copy of my phone bill or subpoena the phone company records, I want to say that yes, I know that. And to stand in trial, of course, you have to have the official records, not some dump of call history from your phone.

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.
Up until this weekend, most of the problems I've had with the Q fall into the "Extremely Inconvenient" or "Extremely Frustrating" category. I didn't think it would come to this, but I came across one that falls squarely into the "Safety of Life Compromised" category.

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.
[this is good]
You have describe my Q perfectly.

Post a comment

Already a Vox member? Sign in