Why the Verizon iPhone won't be any better than the AT&T iPhone (It's not the network)

People across America are excited that Verizon Wireless is getting the iPhone. AT&T has been blamed for network problems that prevent current iPhone owners from being able to do just about anything on their wireless network, like making a phone call. But I'm not so sure Verizon will be all that better, and I blame the iPhone itself.

I seriously think there's a fundamental problem with the iPhone itself, and how it is made.

Let's face it, there's a reason cell phone makers have never built a cell phone with the same type of materials Apple has: reception problems. If you look closely, you'll realize that the majority of people who complain about AT&T's network problems have an iPhone. People with other types of phones don't complain nearly as much about getting dropped, or not being able to place a call altogether.

When it comes to data speeds and connectivity, if you try to complete the same action on an iPhone as with any other smartphone (on the same network), there's a good chance the other phone will finish first. This happened to me the other day. I was with a buddy in downtown LA and went to check traffic on my iPhone with Google Maps. I couldn't get anything to load. (Same with my iPad, by the way.) Absolutely nothing. Zilch. He pulled out his Windows-powered Samsung Focus and Google Maps and traffic loaded instantly.

For this reason, I am skeptical that the iPhone on Verizon will perform significantly better than its AT&T counterpart.

I'm not saying AT&T doesn't have their issues. They do, and they have plenty. But I think Apple's problems are far worse than anyone would like to think.

(This problem extends to other Apple products, as well. Anyone who has used a Mac laptop knows that the range on the internal wireless card is far inferior to other laptop makers due to the metal casing. And yet, somehow, Apple has managed to dodge blame for that as well. While Apple makes "pretty" products, their aesthetics come at a price.)

I base my reasoning on my own hunch and experiences, and no published facts or statistics. I'd be interested in hearing what you think.

Update: Here's more proof.

SPEED TRAP AHEAD - SLOW DOWN

I want to start this post by saying that I'm a fan of cops. I respect them greatly for what they do, and the police in my area are extremely fair and honest in their dealings with people who reciprocate respect. I've been called a snitch before. I've also helped solve a case or two with footage from my outdoor office security cameras.

But when it comes to officers conducting speed traps, especially with cops on motorcycles, I hold a completely different opinion. Catching a speeder who is clearly driving reckless and endangering lives (or those who speed around schools) is one thing, but cops who hide out, waiting for a driver who is slightly over the speed limit is another thing. And that's what's been happening this week in Tustin, a quiet little town in the heart of Orange County.

Yesterday I was driving to my office and received a citation from the "random taxation crew" (don't worry, mom, I wasn't driving any faster than you normally do). I wasn't driving recklessly - I was just doing my normal thing, as most people do (very few people actually drive the speed limit - they're absurdly slow for today's day and age). The only problem was, there weren't many people around, and I was a sitting duck.

In the last 24 hours, I have seen at least 5 people get pulled over by motorcycle cops.

If this were a normal routine - cops nabbing people all the time for speeding - it would be one thing. But they clearly have a campaign going on this week to ticket as many people as they can.

My beef is with the lack of inconsistency. If you're not going to enforce something on a regular basis, don't bother enforcing it at all. Rather than stopping upstanding citizens who are going through their normal routine, why don't you go fight the real crime that happens all the time in the alleyways and dark corners of your jurisdiction?

So to be a "good neighbor," I decided I'd hang a sign warning drivers of the upcoming speed trap.

Who knows how long it will last, but if I can help one honest person avoid a ticket, it will have paid off.

iPhone faux pas

If you use a touchscreen phone, chances are you've sent a text message saying something you didn't intend to say, thanks to the sometimes overly ambitious auto-correct.

Recently I've tweeted some iPhone auto-corrections that I've come across, and some friends have @ replied with ones they've encountered. Here are a few:

psd --> LSD
iOS --> UPS
podcasting --> Piccadilly
awwwwwwww --> seedeater
swimmer --> Weinberg
hahaha --> habanera

But none of these beat the list published by damnyouautocorrect.com in November. Check it out.

The moral of the story is... always double-check your messages before sending, or your recipient might be a little confused.

Have you encountered any strange or memorable auto-corrects? Share them in the comments!

Wanted: English translator for Chinese electronics manufacturers

One of the best parts of buying small electronics straight from China is the joy of trying to understand the product packaging. The words make sense, but they're never in the right order for the English language. It's like they use Google Translate to get their copy into English, rather than hiring an interpreter. 

Here are a few shots off the box of a remote control helicopter I got for Christmas.

And if you haven't seen them yet, last year I posted a few shots from the box for a remote control plane here that I think are even funnier.

With Apple, you have to drink ALL the Kool-Aid, not just half a glass.

Many Mac users talk about how "everything just works." For me, this has never been my experience with any Apple product. Ever. I finally realized why: because I don't do everything their way.

Today I had to get a replacement iPhone from Apple. When I restored the backup of my phone to my new device, I was frustrated to discover none of my apps synced, among a litany of other odds and ends. As it turns out, this was because I didn't have "Sync Apps" checked within iTunes.

Despite the fact that I "backed up" my iPhone, I got screwed because I didn't submit to Apple's entire - and narrow - use case. (Also, Apple failed to explain that a "backup" doesn't actually back everything up.)

So to the rest of you who have a habit of going your own way and not following all the "rules" - or in this case, letting Apple manage everything for you - look out. Because if you don't drink ALL of the Apple Kool-Aid, you too might find yourself in a world of hurt.