Help [VZW] Have a Nexus? Having one-way audio issues? Tell us where you are

[quickaudi]

I can't say I've had the one-way calling issue, but I have had an issue when talking to voicemails (twice) where the system couldn't hear me, even if I yelled.

I know this is supposed to be a software issue, but maybe it's hardware in some cases?

 

[Demache]

I can't say I've had the one-way calling issue, but I have had an issue when talking to voicemails (twice) where the system couldn't hear me, even if I yelled.

I know this is supposed to be a software issue, but maybe it's hardware in some cases?

That's what makes this bug tricky. There doesn't seem to be a rhyme or reason to it. It just....happens. Sort of like the silent call issue on the Eris (similar issue, completely random, you couldn't talk to OR hear anyone). In the same way, some people have constant issues, others have none. Its only ever happened to me once, and I was out of state in a "remote" area [with 4G ]. Its never happened locally though.

 

[OfTheDamned]

My replacement came in the mail today and will be going back to Verizon on Monday. While it didn't appear to have the silent call issue it did have a bad habit of completely dropping connection of any kind about 33 times today. 4 of which happened in a Verizon store.

I spoke with 4 techs and made them aware of this thread. Each told me they would take a look as they are very interested in the problem.

 

[jkc120]

My replacement came in the mail today and will be going back to Verizon on Monday. While it didn't appear to have the silent call issue it did have a bad habit of completely dropping connection of any kind about 33 times today. 4 of which happened in a Verizon store.

I spoke with 4 techs and made them aware of this thread. Each told me they would take a look as they are very interested in the problem.

Yeah you got one with bad hardware.

If I knew for sure the SGSIII would get AOKP/AOSP, I'd probably pre-order one now to replace the nexus. This mid-call muting thing is annoying as hell to me, and I rarely use the phone. I can't even imagine relying on it for an emergency or a business use...

 

[OfTheDamned]

Yeah you got one with bad hardware.

If I knew for sure the SGSIII would get AOKP/AOSP, I'd probably pre-order one now to replace the nexus. This mid-call muting thing is annoying as hell to me, and I rarely use the phone. I can't even imagine relying on it for an emergency or a business use...

I'm not willing to pay anything for another phone or lose my update at this point. The phone is under warranty I expect to get one that works right or a free upgrade to one that will.

 

[Blue218]

I got off of the phone with verizon technical support today.....the lady told me that she would put in a work order to have the local towers checked. She agreed that the problem(one way mic) did not seem to be hardware and was probably network/tower. She advised me to dial ###send after any call that gets the one way mute....so they can track the call and see where it hits possible problems. I am not holding my breath but this is the farthest that I have gotten with verizon even making any attempt to resolve an issue. (PS: the tech I talked to had no idea about tired data so I pointed her to articles about the verizon CFO "spilling the beans" Verizon CFO: Unlimited Data Plans Going Away, All Users Pushed Onto Shared Data

 

[jkc120]

So I made 3 calls today all from my house:

- call #1: 49 minutes, NO issues at all
- call #2: 30 seconds, went mute almost immediately
- call #3: again, immediate muting

I tried dialing ###<send>, but it just says "your call cannot be completed as dialed". Is that normal? Or am I dialing it wrong somehow?

What's interesting is my wife on her VZW iPhone 4 had a similar issue right around the same time. Hers was an outbound call, too, and it happened early in the call as well. hmm...

So freaking annoying. The next time I'm in a Costco, I'm going to ask about whether they will honor a late return because this is ridiculous.

 

[Demache]

So I made 3 calls today all from my house:

- call #1: 49 minutes, NO issues at all
- call #2: 30 seconds, went mute almost immediately
- call #3: again, immediate muting

I tried dialing ###<send>, but it just says "your call cannot be completed as dialed". Is that normal? Or am I dialing it wrong somehow?

What's interesting is my wife on her VZW iPhone 4 had a similar issue right around the same time. Hers was an outbound call, too, and it happened early in the call as well. hmm...

So freaking annoying. The next time I'm in a Costco, I'm going to ask about whether they will honor a late return because this is ridiculous.

So her iPhone had exhibited very similar behavior? Very interesting. Makes me wonder if it IS a network issue, but the Nexus has a hard time correcting it (which is an issue in and of itself nontheless, but still).

 

[jkc120]

So her iPhone had exhibited very similar behavior? Very interesting. Makes me wonder if it IS a network issue, but the Nexus has a hard time correcting it (which is an issue in and of itself nontheless, but still).

Sounded like it. I was telling her what I was doing on the computer and she goes "oh, that just happened to me I think. My Dad couldn't hear me. I had to call him back.".

I think it's something with the towers, but the Nexus seems more susceptible to it for some reason. I wish Verizon would official acknowledge this problem instead of dismissing it as as phone or sim card or software issue. *sigh*

 

[jkc120]

I asked my wife if this has happened a lot for her. She said this was the first time that she can remember.

So I'm chalking it up to coincidence or again some sort of tower/nexus interaction that the nexus.

Since the international sgsIII is already rooted, if the Verizon bootloader is not locked down (and the root method works for the VZW one), I will probably see if TouchWiz bothers me as much as Sense does and consider running a rooted sgsIII w/Nova Luancher in place of the Nexus.

 

[brhermon]

Hey everyone, I've been following along with similar issues, though I'm still trying to make heads or tails of it. FWIW I live North of Dayton, OH. We don't officially have 4g coverage here, but in the last 2 or so weeks it's been popping up. Looks as if they're preparing for it at least.
Unfortunately I haven't found a resolution but I've done a crap load of research. For anyone that's interested, You might want to check it out. It might help or at least bring the problem to more people's attention.

http://androidforums.com/samsung-galaxy-nexus/567387-audio-headphone-jack-problems.html

 

[Blue218]

I called verizon again and again the lady (different one) put in a work order to check the towers and logged the calls that I marked (###send) 3 one way mute calls today.....not including the call I was on to verizon lady that went mute......she's "supposed" to call me on Friday. We'll see.

 

[Boldy]

I was getting my hopes up after not experiencing the issue for several days (although I don't make many calls). Then today my phone went mute on three calls in a row. Each time it occurred within a few minutes. Still thinking about getting it replaced with a Razr Maxx. There are several things I don't like about the Maxx, but at least it works as a phone.

One thing I just realized, I never had the muting issue while at my house (in Denver, CO). It is always when I'm away from my WiFi.

 

[Copacetic]

Another NC person here. South east corner, since launch day, on my second nexus, very frustrating.

 

[OfTheDamned]

Ok, I just finished a call with a Verizon tech. This is the same tech I have been talking to the whole time and he actually called me.

So he asked me a week ago to do the whole ### send thing with each call that has the muted audio issue. He explained that the call will not go through, but that they use it to flag the calls on my call log. Then they can go back and see the call I had issues with. They can look at the tower I'm on, the duration of the call, the connection quality, etc. and evaluate the call overall.

So after a week of me doing this, in various places and to various people, they are doing a trouble ticket to come out and check the network in my area. They are going to be looking at all the towers and the overall network stability. He recognized that my calls were made as far south as Colorado Springs and as far north as Cheyenne, WY, but stated that they were going to focus on just my area for now. If they determine that it is the network and not just the way my phone or phone number is communicating with it then they will start to go through other areas of Colorado. After this test (should be 3 to 5 days) he said he would get back with me to go over everything.

We did discuss the fact that I've had 3 different Nexus phones with this issue. We also discussed that the bluetooth headsets that I have with 2.0 and 3.0 did bypass the issue, but that the newest headset with bluetooth 4.0 tech does not.

Lastly, he explained that if they could not resolve the issue they would offer to move me into another phone of my choosing.

I encourage anyone that is having this issue to call Verizon tech support and let them know what is going on. If you've called a few times with no real results, keep trying. There are Verizon employees that are really looking to help and want to resolve this problem. At the very least they can be made aware of the overall problem. At the best they can get it resolved so that we can all enjoy our phones that much more. It can only help everyone that much more if they see that the issue is specific to states or regions too.

 

[Blue218]

VZW supposedly checked the towers in my area (Santa Fe, NM) around my house....I'm equidistant from 3 towers so my phone switches between them......so sometimes I get a real crummy signal....they offered to sell me a refurb network extender cheap and I took them up on it. The VZW tech also admitted that it is a network/software issue. I also learned that the VZW 4G towers around here are not the "latest/greatest" like they have in Phoenix (the regional headquarters) so maybe the older 4G towers are part of this issue.

 

[OfTheDamned]

We have a friend spending the night tonight and she uses an iPhone on At&t. Apparently, she has the exact same problem with her phone here in Colorado.

We started talking with some local friends that have the problem. The only thing that any of us have in common is that all of our accounts originated in another state. Anybody else with the issue move from another state?

 

[Boldy]

We have a friend spending the night tonight and she uses an iPhone on At&t. Apparently, she has the exact same problem with her phone here in Colorado.

We started talking with some local friends that have the problem. The only thing that any of us have in common is that all of our accounts originated in another state. Anybody else with the issue move from another state?

Not me. I have the muting issue in Colorado, but I haven't moved from another state since opening my account.

 

[dwilliam16]

The VZW tech also admitted that it is a network/software issue. I also learned that the VZW 4G towers around here are not the "latest/greatest" like they have in Phoenix (the regional headquarters) so maybe the older 4G towers are part of this issue.

One thing I noticed after seeing that survey map is that it corresponds pretty closely to the places that Verizon is upgrading 4G and also areas that were notorious problem areas with Alltel - especially North Carolina. Maybe Verizon has been having issues with the old equipment that worked fine utill the 4G upgrades (why change it if it works?) but now can't handle the new signal hand-offs and differences in network traffic. I could be wrong, but having lived here and remembering similar issues with Alltel in certain areas, this seems very plausable to me.

I really think that if someone did an in depth check, they would find a correlation between the old Alltel problem areas (inherited by Verizon) and the new one-way audio issue. With Alltel in NC, we had this issue where a handoff between towers wouldn't complete correctly and there would be several seconds of dead air for one person. It would recover, but otherwise was the same issue - one person wouldn't be heard for several seconds and the call would either drop or a pop was heard and it would continue normally. Granted, Alltel was 2G at best (don't remember if they even got 3G before buy out), but the basic network to tower connections probably haven't been changed much.

 

[Lucky Armpit]

I remember the Alltel days. It was a great company and I remember NOT being happy when Verizon bought Alltel. I've been with them since they were 360 Communications. First 360, then Alltel, then Verizon.

I really hope the Nexus folks get this worked out, I really do. I couldn't stand it anymore (been 6+ months) so I've switched to a Razr Maxx. It has it's shortcomings, but they are far outweighed by the fact that I can once again make phone calls without the constant worry of the one-way audio issue. I'm moving my files off the Nexus as I type this and I'll be sending it back in a few days. I got a nastygram from Verizon, asking for the Nexus back so I can't delay it much more. Wife told me I'll be on the hook for the money if we get charged so I need to send it back ASAP.

 

[Member 838958]

Another Northern Colorado person here.....I've assumed it's a tower issue all along. I did originate my Verizon account in another state but we've been here three and a half years (and changed our phone #). I'm not sure if you know Fort Collins very well but there is a Front Range Village shopping center. We are within a couple miles of that. Consistently around -100 to -120 db. When I am in that center I barely have a signal and can only get 3G (and not that great either). The funny thing is there is a MyVerizon store in that center (which probably has a network extender but geez it can't be good for business to have no signal for customers, lol).

When I go further south into the Loveland area my signal is much better (-75db but only 3G). When I'm closer to downtown Fort Collins my signal and 4G are MUCH better.

Getting a network extender is a thought but this morning I had to call my wife while driving to work and the first time it dropped and the second time she said my voice mail was garbled, which I knew it was since the ringing was going in and out.

At some point I will hit that Verizon store and see if they know of any new towers coming to the area, I think it's needed bad.

 

[OfTheDamned]

I really think that if someone did an in depth check, they would find a correlation between the old Alltel problem areas (inherited by Verizon) and the new one-way audio issue. With Alltel in NC, we had this issue where a handoff between towers wouldn't complete correctly and there would be several seconds of dead air for one person. It would recover, but otherwise was the same issue - one person wouldn't be heard for several seconds and the call would either drop or a pop was heard and it would continue normally. Granted, Alltel was 2G at best (don't remember if they even got 3G before buy out), but the basic network to tower connections probably haven't been changed much.

I just went through the markets acquired by both Verizon and At&t from Alltel. I can see were NC and a few other areas used to be Alltel markets. However, in Northern Colorado and Northern California I don't see where Alltel ever had any coverage for Verizon to take over.

 

[OfTheDamned]

Well, my Razr Maxx is being sent out in a few days. I'll get about a week to test it out and then my baby has to be returned. Sad day, but I have to be able to make a phone call.

 

[jkc120]

Well, I read that one of the AOKP devs will be getting a VZW SGS3. And Roman himself said he'll likely be getting one.

That pretty much seals it for me. If the VZW SGS3's radio performs like I hope it will, I'm selling the Nexus and getting the SGS3 (full retail to keep my unlimited data).

 

[Lucky Armpit]

Well, my Razr Maxx is being sent out in a few days. I'll get about a week to test it out and then my baby has to be returned. Sad day, but I have to be able to make a phone call.

That's what did it for me. I had no other choice.