[Q] POLL: Verizon Galaxy Nexus In-Call Microphone Issue - Location Map

cguella · May 9, 2012

Prefer to Jinx Myself

Since these updates no muted mic issue (Update happened again a few times no fix here):

Verizon Galaxy Nexus (Since available)
AOKP 4.0.4 Milestone 5 (Over a week now)
Flashed new radios FC05 (Two days)
Charlotte, NC

cguella · May 10, 2012

What could It Be ????

to summarize:
- Not 4G - since it happens on 3g
- Not headphone routing issue - happened with the switcher widget in place
- Not Wifi/3g/4g switching - happened with 3g only
- Not provisioning - VZW reprovisioned my device 2x
- Not hardware from China or Korea - Both have had the issue
- Not root/stock issue - Both seem to get it
- Not radio version issue - so far all radio flashes have not fixed it
- Not 4.0.2 4.0.4 issue - it has happened to both custom ROM or stock
What else is there? Fundamental hardware defect? Software defect?

ohumad · May 18, 2012

I too have had this problem, located in St. Paul, MN. Its happened less than 5 times I would guess, still really annoying. All calls took place around St. Paul. Running stock Galaxy Nexus from VZW with LTE switched off.

loraque · May 24, 2012

ohumad said:
I too have had this problem, located in St. Paul, MN. Its happened less than 5 times I would guess, still really annoying. All calls took place around St. Paul. Running stock Galaxy Nexus from VZW with LTE switched off.

I just got called from the wife, who reported this problem. St Paul also. It would certainly seem that the region DOES have something to do with it... the spread on the votes is not much of a spread- Focus of issues in MN and NC does not make sense on pop distribution. I did try disabling her Voice Privacy setting in the dialer as another thread said this mitigated it. It also does seem that it is either a software issue, or some problem perhaps with the local networks in some areas?

How can there be so many votes for MN and not for CA or NY for example? Having a hard time with that being coincidence.

We are using the new radios and CM9.

matt30 · May 24, 2012

loraque said:
How can there be so many votes for MN and not for CA or NY for example? Having a hard time with that being coincidence.

We are using the new radios and CM9.

It's probably a problem with the way the poll is set up. A bunch of people live in St. Paul but not many people live in Sacramento or Albany - the capital of CA and NY.

bangdrum · May 25, 2012

I'm in Sacramento, and I have this happen every day.

Sent from my Galaxy Nexus using Tapatalk 2

adjuster11 · May 29, 2012

Not giving me the warm fuzzies.

I recently dumped stock 4.0.2 and went with AOKP build 37, with imm76 radios. I'm still getting this one way audio issue. Just disabled NFC, and 4G, to see if that might work.

I hope someone finds an answer, but cguella appears to be way ahead of me in his search.

cguella said:
to summarize:
- Not 4G - since it happens on 3g
- Not headphone routing issue - happened with the switcher widget in place
- Not Wifi/3g/4g switching - happened with 3g only
- Not provisioning - VZW reprovisioned my device 2x
- Not hardware from China or Korea - Both have had the issue
- Not root/stock issue - Both seem to get it
- Not radio version issue - so far all radio flashes have not fixed it
- Not 4.0.2 4.0.4 issue - it has happened to both custom ROM or stock
What else is there? Fundamental hardware defect? Software defect?

pchoi94 · May 29, 2012

Hi folks,

Just wanted to report back that I traveled to Houston for a week on a business trip and did not have the issue happen once. I also had full bars on 3G most of the time (there wasn't any 4G where I was staying, which was way north of Houston actually).

Got back home to Denver (Boulder area) where I have around 2 bars and the issue has happened a couple of times so far. Would be interesting to see how much reception affects this as well.

People might assume that 2 bars is "good enough" but maybe with the radios on the Gnex (compared to Motorola, for example), it just doesn't cut the mustard?

On a side note, I also noticed that my battery lasted twice as long, which is expected. My radio signal was around -75dmn in Houston, whereas it is around -105dmn in Denver area.

hmm, I may set up another poll to track the issue per signal strength...

adjuster11 · May 29, 2012

I'm wondering if it's region related, since I'm in Lakewood, just on the West side of Denver. The only place I travel is in state, so I don't get to find out if it "works" somewhere else.

Good point though!

jkc120 · Jun 7, 2012

I really think this is regional.

I think I'm going to contact the California State Attorney General and FTC about this. Verizon continues to deflect and wants to replace devices, when it's been clearly shown people's replacements have the same problem.

Maybe if enough of us complain to the FTC and our local state AG we'll get some response from them...

---------- Post added at 11:39 AM ---------- Previous post was at 11:37 AM ----------

pchoi94 said:
hmm, I may set up another poll to track the issue per signal strength...

I've had it happen at my work's parking lot with full 4G bars @ like -75 dBm and perfect 3G service as well. I don't think it's (entirely) signal related.

Dan76 · Jun 7, 2012

Even after 4.0.4? My experience after the update has been incredibly better... although it's only been six days.

Manos Lijeros · Jun 7, 2012

regional

It may be regional... I do see the poll shows 22% in NC affected, low 10s in Colorado and California, and in between in Minn.

Bob Egan suggested there may be some issue with the reverse channel communication. I am working on this via twitter (I've tweeted to 30 Internet luminaries (Bob Egan, Google Execs, Verizon CIO & PR staff, writers, etc...).

Verizon Support is all over me know... The last thing they asked me to do (since I have the 4.0.4 update) was to run it in safe mode to see if the issue happens in Safe Mode. Bottom line... The issue is still here in safe mode.

I am updating my issue and my quest to solve this issue at 2-sidedcoin.blogspot.com. I tweet under ManosLijeros, and I'm active over the last three days (that is where this issue is located).

Dan76 · Jun 7, 2012

Manos Lijeros said:
It may be regional... I do see the poll shows 22% in NC affected, low 10s in Colorado and California, and in between in Minn.

Bob Egan suggested there may be some issue with the reverse channel communication. I am working on this via twitter (I've tweeted to 30 Internet luminaries (Bob Egan, Google Execs, Verizon CIO & PR staff, writers, etc...).

Verizon Support is all over me know... The last thing they asked me to do (since I have the 4.0.4 update) was to run it in safe mode to see if the issue happens in Safe Mode. Bottom line... The issue is still here in safe mode.

I am updating my issue and my quest to solve this issue at 2-sidedcoin.blogspot.com. I tweet under ManosLijeros, and I'm active over the last three days (that is where this issue is located).

It's most certainly regional. If you've seen these other threads:

Poor Quality Control
4.0.4 Update
Mic cutting out problem

You'll see that many of us have a theory is that the Galaxy Nexus will lose outgoing audio (or crackle, pop, whatever) on many VZW LTE towers in certain areas of the US, likely due to poor or old tower technology. Or possibly due to the companies that did contract work on certain towers.

Obviously those towers work, it's just an incompatibility of those towers with the specific radio in the Galaxy Nexus (which is unique among all verizon phones).

Jep0 · Jun 9, 2012

Samsung Charge has same issue

I just replaced my Samsung Charge (after 3 Charge replacements) with the Galaxy Nexus through Verizon. The Charge has the exact same issue as the Nexus with mic-drop. I have experienced this for quite a while now. It starts once in a while on long calls then becomes more frequent with shortest call time around 2 minutes.

I have had this Nexus for almost a week now and it's doing the same thing. I went to the Verizon store, and of course they were very suprised to here about this issue. Lol. they did say it might be bad towers in the area. I live in Reno, NV. This never happened with my Samsung Omnia or Omnia II. The only true fix that I have seen out of this is someone switching over to a Razr Maxx. I would rather not do that if I don't have to.

Does anyone know if the Charge and the Nexus share the same radio?

shadowstewie · Jun 10, 2012

I live in Orange County, California.

My girlfriend and I both have the VZW GNex, both on AOKP Milestone 5, switching between Franco and Lean Kernel, with the 4.0.4 official radios flashed.

We hear a scratching/robotic noise when the other person talks on the phone. Its happened to us talking to each other as well as us talking to other people. It happens randomly.

Any ideas?

Sent from my Galaxy Nexus using XDA

jkc120 · Jun 14, 2012

Jep0 said:
I just replaced my Samsung Charge (after 3 Charge replacements) with the Galaxy Nexus through Verizon. The Charge has the exact same issue as the Nexus with mic-drop. I have experienced this for quite a while now. It starts once in a while on long calls then becomes more frequent with shortest call time around 2 minutes.

I have had this Nexus for almost a week now and it's doing the same thing. I went to the Verizon store, and of course they were very suprised to here about this issue. Lol. they did say it might be bad towers in the area. I live in Reno, NV. This never happened with my Samsung Omnia or Omnia II. The only true fix that I have seen out of this is someone switching over to a Razr Maxx. I would rather not do that if I don't have to.

Does anyone know if the Charge and the Nexus share the same radio?

I'm not certain, but I think they are both VIA (for 3G/1x) but the Nexus has a newer version of it...

cucamelsmd15 · Jun 26, 2012

I voted North Carolina. My wife and I both have this issue.

pchoi94 · Jun 26, 2012

shadowstewie said:
I live in Orange County, California.

My girlfriend and I both have the VZW GNex, both on AOKP Milestone 5, switching between Franco and Lean Kernel, with the 4.0.4 official radios flashed.

We hear a scratching/robotic noise when the other person talks on the phone. Its happened to us talking to each other as well as us talking to other people. It happens randomly.

Any ideas?

Sent from my Galaxy Nexus using XDA

i think that's a different issue that the one this thread is about, but to answer your question that just happens from time to time, probably just a bad connection... how often does it happen?

pchoi94 · Jun 26, 2012

wanted to chime in again here, I'm the OP of this thread:

I live in Colorado, where I've had the issue a lot, but for the past 3 or 4 weeks i've been staying with family in the Los Angeles area in California, also visiting friends and family in Orange County: Irvine, Huntington Beach, Palos Verdes, La Palma, etc.

We also drove cross country from Colorado to California for this trip.

Anyway, the entire time I've been here (and for the entire road trip on the way here) I have not had the issue once. Not a single time. It was happening to me about 1/4 to 1/3 of the time back home in Colorado.

I've used the phone in areas with excellent coverage, as well as marginal coverage, and I never had the issue on this trip. But I'm sure when I get back home to CO I will have it happen again. I also travel for work, have been to several other states, i.e Houston area in Texas, Seattle area in Washington, and never had the issue, but whenever I got back home to CO it would start happening again.

Just more info...

JFMFT · Jun 28, 2012

I live in NC and me and my boyfriend both have trouble with the mic cutting out on our GNex's. We're replacing them with GS3's as soon as the phones we pre-ordered ship out to us.

We've had the mic cutting out issue since we got the GNex on launch day last fall/winter. We spent some time in Ohio last December and never had the issue once. I have tried every single radio combination on both phones, nearly every ROM/ROM revision, and just about every tweak/setting possible and we continue to have problems here.

Just lending additional credibility to the theory that it's the towers and the specific radio in the Galaxy Nexus. Too bad, it's an amazing phone otherwise, but the poor radio and its susceptibility to losing outbound audio on certain towers (especially in my area) makes the phone completely useless to me.

[Q] POLL: Verizon Galaxy Nexus In-Call Microphone Issue - Location Map

Vote for your state ONLY IF you have this issue and you live in the state's capital

Alabama

Alaska

Arizona

Arkansas

California

Colorado

Connecticut

Delaware

Florida

Georgia

Hawaii

Idaho

Illinois

Indiana

Iowa

Kansas

Kentucky

Louisiana

Maine

Maryland

Massachusetts

Michigan

Minnesota

Mississippi

Missouri

Montana

Nebraska

Nevada

New Hampshire

New Jersey

New Mexico

New York

North Carolina

North Dakota

Ohio

Oklahoma

Oregon

Pennsylvania

Rhode Island

South Carolina

South Dakota

Tennessee

Texas

Utah

Vermont

Virginia

Washington

West Virginia

Wisconsin

Wyoming

Member

Member

New member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member

New member

Senior Member

New member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts