Monday, February 18, 2013

A Report Card on the Google Nexus 4 Phone

The new Nexus 4 phone from Google went on sale mid-November last year. It is made by LG and sold by Google, and is presently running, of course, the latest Android - 4.2.2 Jellybean.

We received the first of what eventually became a series of four Nexus 4's on December 13 last year. We figured some of you readers might be interested an actual user's experience with the phone, as compared to the often rather breathless "Oohs, and Aahs," that a few of the professional reviewers have been publishing about the N4. You might also want to take note of who pays for advertisement on some of those reviewer sites, btw. Just sayin'.

So, after having had three months to fully explore the phone, we thought we'd give Google a report card on the Nexus 4. We divided the report card into the following categories:

  1. E-commerce purchasing experience,
  2. customer support, and
  3. product quality.

E-commerce Experience, Grade: D-

These days we have big-time professional E-commerce retailers like and around against which to compare Google for an online buying experience. As it turns out, Google fell flat on its face. When the phone first went up for sale on November 12, Google's servers crashed within minutes, and stayed down for most of the day. The phone apparently sold out within minutes, but potential buyers didn't know this until later that day because the servers could not handle the load of people trying to buy the phone.

Then, on December 17 when a fresh batch of phones became available for sale again, the same thing happened again! If I were Google, I'd be real embarrassed about that. Google: take a lesson from Amazon on how to host a scalable E-commerce infrastructure. We were torn between D- and F+, but eventually decided to give points for at least trying.

Customer Support, Grade: F

Here's were it gets a bit ugly. It seems like there were a few known issues with the Nexus 4 and with the Android 4.2.1 distribution that came with the phone. It also seems that the Google Nexus 4 developers were fully aware of these issues at the time the phone went up for sale. Or became so immediately after it went up for sale because that's when people started complaining.  

So, this is why we ended up calling Google's Device Customer Support number (1-855-836-3987) about an hour after receiving that first phone. The first thing we did after unpacking it and letting it connect to the home office wifi was to do an update from Android 4.2 to 4.2.1. Next, we paired it with a  Plantronics bluetooth headset, fired up Skype, and attempted to make a Skype VoIP call. 

Oops. Immediately, the phone's wifi died, and the wifi icon disappeared. And the phone locked up, requiring a hard reset. Wifi seemed to work fine. Unless you tried to use bluetooth. Bluetooth killed wifi, every time.

So we called Google's Device Support number, and were told, "There are no known problems with the Nexus 4, it sounds like a hardware problem; we'll be happy to replace if for you."

So we replaced it.

And the replacement phone had the same problem.

Then, we noticed that when we blanked the screen, the phone would disconnect itself from its wifi connection and would no longer respond to push notifications. This in spite of having the "Keep Wifi On" set to "always". When we'd turn the screen back on the wifi icon would be grey and then turn blue again after the phone reconnected to my wifi access point.

Another call to Google's Device Support Team. Was again told "No, there are no known issues with the Nexus 4." We let them send another replacement.

In the meantime, we searched the Google code forums where the Google developers hang out, and found several bug report threads devoted to the specific bluetooth wifi-killing issue and the wifi suspend issue, both dating back to November 20, 2012.

Clearly, Google had known about both of these problems for quite some time. 

By now we were curious to see if the Google Device Support team would tell us yet one more time "There are no known problems with the Nexus 4." So we called them. And they did.

We decided to have them send a third replacement. Because by now, one of the Google developers had identified the cause the wifi screenblank dropout behavior - a buggy Qualcomm wifi driver. Plus, a number of other wifi bugs had been identified in Android 4.2.1 which the Google Android developers promised to have fixed in 4.2.2. We figured we'd install the 4.2.2 update to see if they fixed the Nexus 4 problems.  

The problem is, 4.2.2 didn't come out in a very timely fashion. So on day 15, the last day for returning the phone to the vendor, we called to RMA our third Nexus 4.  

And then 4.2.2 came out. So we ordered a fourth Nexus 4. We are nothing if not tenacious.

And guess what? The same buggy Qualcomm wifi driver was in 4.2.2, and bluetooth still kills wifi. And other customers are now complaining the the Google Device Support Team is still telling them that there are no known problems with the Nexus 4.

So, we took our fourth Nexus 4, rooted it and installed the latest Cyanogenmod image, recovery-clockwork-touch-, and then installed this patch to the Qualcomm driver init file. The patch helps, but does not totally fix the wifi screen blank suspend problem. Bluetooth still kills wifi though.

I always wanted to root a phone anyway.  

The grade for customer support therefore is a big, fat F. Either for being dishonest, or for being completely incompetent. Whichever.

Product Quality, Grade: C

The HSPA+ 4G data service is nice, seems to work as it should with T-Mobile. We usually get download speeds of 3 - 7 Mbps and uploads of 0.7 - 3 Mbps in Santa Fe, NM were there is decent T-Mobile 4G coverage.

The camera is nice.

Battery life is on the short side, maybe 6 - 8 hours if the phone is used sparingly.

The wifi and bluetooth components are a shambles.


Google does not know how to do retail. The online buying experience was a disaster.  Google's customer support is either completely dishonest, or hopelessly incompetent. The Google code forums provide very little feedback to the thousands of bug reports about the Nexus 4. 

When bug reports are made via the Google code forums, progress can be measured by glacial standards. Relative eons pass with no feedback, and little progress. Bug reports about critical features of the Nexus 4 went for weeks before even being acknowledged, and once acknowledged, estimates of time to fix were never given.

Google effectively does not have a working customer support system.

The Nexus 4 looks great on paper. The reality is somewhat different, and at the rate Google is progressing (actually, we can't even tell if they are progressing) someone else will come out with a newer, better working product. 

Our advice: wait for that.



  1. What's surprising is that there is no press whatsoever on the shortcomings on basic stuff like WiFi and Bluetooth in Engadget or gizmo do for example, when iPhone gets press for an item so subjective as a screen leak..


  2. I've noticed this lack of press about the Nexus 4's shortcomings as well. It is possible, I suppose, that Google is pressuring high-visibility news sites, like Slashdot, CDNet, ZDNet, etc. to not publish articles critical of the Nexus 4.

    1. Now, if that's true, That's pure evil.

  3. Hey, don't take my word for it. Buy one & see for yourself!

  4. Some of the Google fanbois over at Android Central Forums are taking exception to my "C" grade for the Nexus 4 Product Quality category. Well, when/if Google ever figures out how to get wifi working, and working *with* bluetooth on top of that, I'll reconsider. But not until then.

    1. Welt my friend you have to be smarter than the phone and from your whole article it seems you donteven posses a grade school education if you cant seem to get it going.

      Oh and PS stop writing comments yourself under anonymous to make it look like you actually have any readers over here.

      Troll on.....

    2. I never post anonymously, my Google fanboi friend.


  5. Ladies & gentlemen, the contribution left by Mr. Anonymous above at 8:20 is a good representative example of the level of technical expertise and maturity that one finds over on the Android Central Forums.

    Think high school, and you're in the neighborhood regarding the level of social development you can expect to find hanging out there.


  6. Wow and you think you are being mature by name calling and commenting more on your own article than your readers??

    Google's ecom capabilities are clearly terrible, but very few people myself included have had this so called Bluetooth issue.

  7. Well George, the concept of "maturity" is a relative one. For example, the apparent level of maturity over on Android Central is, on a scale of

    infant --> child --> teenager --> young adult --> mature adult --> senior citizen

    hovering somewhere between "child" and "young adult".

    Not very mature, in other words.

    Out here in the Things Linux blogosphere, you have to be capable of interacting with your peers at "young adult" and above maturity levels in order to be allowed to play.

    So, now to directly address your comment:

    1) "Wow and you think you are being mature by name calling and commenting more on your own article than your readers??"

    - Missing punctuation. Missing comma after the opening "Wow".
    - Incorrect punctuation: extra, superfluous "?" at the end of the sentence.
    - Incorrect math. The answer is "No. There are more comments from others on the referenced forum thread than from myself."

    2) Second sentence: incorrect premise. That fact that you have not experienced the particular bluetooth issue in question does not mean that it does not exist.

    Summary: not a bad first attempt to interact at a "young adult" or above level of maturity, but it could use a little work.

    Grade: C+, mainly for effort. rather than depth and accuracy of content.

  8. Alright, based on your butt hurt response, I think we're done here. I will say this though:

    Screw being a "young adult". You are a wanker. It goes to show that your argument is a joke when the only thing you can do is attack someone's grammar in the comments section.

    This blog is lame, you are lame, and if you think you are operating at superior maturity level to everyone else by your ridiculous arguments, you are delusional.

  9. Somehow, the lack of maturity in your response does not surprise me.

    Have a nice day.

  10. Just bought a brand new Nexus 4 after reading * rave * reviews, upgraded to 4.2.2 and yep, won't find my trusty blueant headset. Swapped off an iphone 'cos curious about Android and annoyed with some of the Apple limitations, but this feels like a 50' drop in quality straight up. Bit anxious if its a known bug since Nov 2012 and we're now in April 2013. Worse given there is no handsfree in the box - kinda blackmark #2 in about 3 hours so far.

  11. No arguments here, Dean. Google dropped the ball on this one.