On my 6th GNEX ...has anyone ever got one that's a Phone?

**bridger2001** · 07-15-2012, 12:08 PM

OK, I'm on my 6th "phone" from Verizon. Yes..the 6th.

I'm a victim of the dreaded Microphone Cut Out Problem (MCOP) and it's killing me. This one I received on Saturday and the FIRST DANG CALL i made on it dropped the mic.

Has anyone gone through this and actually finally received a working phone?

Verizon wants to put me in a Rezound. I played with one yesterday in the store..no offense to rezound owners, but i might as well get a Cricket phone instead..

Is there hope that i will ever get a working phone? Looking for a success story (if it exists).

**ultravisitor** · 07-15-2012, 12:20 PM

Both of mine have been fine. The only reason I got a replacement is because I dropped the one I got on launch day and broke the screen.

**doomtuba** · 07-15-2012, 01:43 PM

Originally Posted by ultravisitor

Both of mine have been fine. The only reason I got a replacement is because I dropped the one I got on launch day and broke the screen.

Same here except it took me a week to drop mine :sly:

Sent from my Galaxy Nexus using Tapatalk 2

**Mimi918** · 07-15-2012, 02:02 PM

I've had mine since December, with no problems.

Sent from my Galaxy Nexus using Xparent Pink Tapatalk 2

**dimsdale** · 07-15-2012, 02:26 PM

OP, are you saying that ALL SIX phones you have been through have the mic cut out problem?

I've been through a whole bunch of VZW refurb GNEXes. (See Verizon Refurb CLNs = GARBAGE) I believe they are garbage.

But all of my GNEX refurbs sucked in slightly different ways. It's hard to imagine six with the same failure.

**trailblazen** · 07-15-2012, 02:33 PM

Originally Posted by dimsdale

OP, are you saying that ALL SIX phones you have been through have the mic cut out problem?

I've been through a whole bunch of VZW refurb GNEXes. (See Verizon Refurb CLNs = GARBAGE) I believe they are garbage.

But all of my GNEX refurbs sucked in slightly different ways. It's hard to imagine six with the same failure.

Thank god they are sending me a brand new one........

**bridger2001** · 07-15-2012, 03:07 PM

Dims..no actually #3 had the radio reboot issue...that was in April before 4.0.4 came out. the other 5 have all had the MCOP. I've tried resetting the device, un-installing all the apps, hours on the phone with tech support...etc..etc...

**woody_105** · 07-15-2012, 03:17 PM

I will be on #5, in the mail getting delivered tomorrow and they all suffered from the mic cut out problem. Some were within minutes of making a phone call and others would take about 10-15 mins then would cut out. #4 was the best by far because it went about 3 weeks with no problems at all then it started squelching, cracking and cut outs.

**bridger2001** · 07-15-2012, 03:41 PM

Dang woody, sounds like we are in the same boat. Very similar experience.

I wish you luck. My verizon rep is balking at giving me a discount on an S3..it's a nice device but still no GNex. i hate to give up, but it's not looking promising.

**EJT** · 07-15-2012, 04:02 PM

Both of mine worked great as phones. The first one went back because when they launched LTE in my area, it couldn't hold radios for more than ten minutes without dropping all signals. Worked fine on CDMA only though. Second one is dead nuts.

**ultravisitor** · 07-15-2012, 04:08 PM

Originally Posted by doomtuba

Same here except it took me a week to drop mine :sly:

Sent from my Galaxy Nexus using Tapatalk 2

I got a good three months out of mine before I dropped it. I've dropped this newer one, too, but luckily there's no damage other than some minor scratches.

**devbo** · 07-15-2012, 10:06 PM

I got my phone back in December and the mic has cut a total of 2 times. Other than that, the phone part of my nexus has been just fine.

**trailblazen** · 07-15-2012, 10:22 PM

Originally Posted by ultravisitor

I got a good three months out of mine before I dropped it. I've dropped this newer one, too, but luckily there's no damage other than some minor scratches.

Originally Posted by doomtuba

Same here except it took me a week to drop mine :sly:

Sent from my Galaxy Nexus using Tapatalk 2

Originally Posted by ultravisitor

Both of mine have been fine. The only reason I got a replacement is because I dropped the one I got on launch day and broke the screen.

Why I will be buying a Otterbox Defender like I do with every phone I get. This will be phone #4 I have bought a defender for and swear by them. My phones have dropped, had fallen from desks, knocked out of holster and not a single scratch on any phone I have owned and used a otter on. They also back their cases too and will replace something if it breaks within the first year.

**rufflez** · 07-15-2012, 11:07 PM

No issues with release day one I have here. Dropped it several times (even stepped on it twice on a treadmill). I was thinking this phone is probably the most durable phone I've ever had... but then again, out of all the phones I've had, I've only broken 1 screen (hero... 1 week before Samsung Epic released which replaced it... still worked).

**CallerHoller** · 07-16-2012, 09:30 AM

Originally Posted by ultravisitor

Both of mine have been fine. The only reason I got a replacement is because I dropped the one I got on launch day and broke the screen.

LOL! Same here. I dropped my first GNex 3 times in the first week. I took it back claiming it rebooted all day. However there wasn't anything wrong with it, other than the cracks in put in it.
After the radio update in IMM30B I've been happy as he'll.

**_JKK_** · 07-16-2012, 09:34 AM

Bought mine launch day, and I haven't had any issues at all... Bought another a few weeks ago, still no issues on that.

Is this a vocal minority, or am I (and people lucky enough to get a device without issues) the exception to the rule?

**mclarryjr** · 07-16-2012, 09:43 AM

I have gone though 5 Gnex since launch and haven't had a microphone problem. 1 had an issue with the radio cutting in and out and the others were just cosmetic issues or bad notification lights.

**only1canoli** · 07-16-2012, 09:44 AM

Still on my first one had it since February

Sent from the great city of Rockford Illinois-not- Gnex

**JET4** · 07-16-2012, 10:24 AM

Mine has been working fine since December when I got it.

**eharty** · 07-16-2012, 10:25 AM

The signal on my GNex is weaker than my wife's Maxx but it usually doesn't create problems. I did swap it out for a new one to see if I could get a stronger radio/antenna and it could not keep a data connection for more that about 30 seconds. I went back to Best Buy and got my original GNex back.

I also have an S3 and surprisingly the signal strength is about the same as the GNex. My last phone was a Samsung Epic 4G on Sprint. It always was a little weak in signal but I assumed it was Sprint...looks like it may be a Samsung thing.

**jgayle10** · 07-16-2012, 10:31 AM

I'm on my second GNex. The first got returned due to not being able to hold the signal while on 4G. Basically, the signal would just dropout and reset while using data or calls. My replacement works perfectly.

**jaguar10301** · 07-16-2012, 10:49 AM

I'm on my 3rd VZW Gnex

First one was perfect, but I stepped on it.

Second one had issues with not recognizing the sim card

3rd one is what i have now, and works great.

**tx_tuff** · 07-16-2012, 11:03 AM

Got mine on launch day and besides a couple dropped calls when new and a few reboots it has been fine. No problem that won't go away, no mic cutting out problem at all. And I use it has a phone and a toy all day long! And some of my days are pretty long including 17 and 20 hour work days.

**jafels** · 07-16-2012, 05:38 PM

Mine and my wifes has kicked **** since launch morning......No data issues, no phone issues....just simply the best phone experience I have ever had.....been lucky I guess.

**MillieD** · 07-16-2012, 08:09 PM

I've had mine since launch day. The only problem was annoyingly low volume on the bluetooth dialer-- almost impossible to hear the "speak now" voice if using bluetooth while driving, and similarly impossible to hear it repeat (usually inaccurately) the name of the person being called. I re-paired it with the bluetooth after receiving 4.0.4. Problem solved.