After returning from the Verizon store in December, 2011, I turned on and started setting up my Galaxy Nexus! Oh, nice phone...
Upon turning it on and setting up the e-mail that is required, I am notified of an update. I had been told 4.0.2 would be out and ready to go when I got home...
After the update and the set-up process was finished, I added apps (I moved from an AT&T Captivate-whose GPS, I must add, never really worked...).
I made some calls, and I noticed what I called a microphone issue. Namely, after about a minute on the call, I'd hear the other party say, "Are you still there? Hello?! Hello? He must have ..." click.
I called back a client this happened to, and the client stated, "I heard a series of short beeps, garbled audio, and then nothing." I could hear everything they were saying, but they could not hear me--so I assumed it was a microphone issue.
I went on-line (isn't that what we do these days?) to see if others were reporting "the issue." I found several links on several sites (See summary of them http://2-sidedcoin.blogspot.com/2012/06/galaxy-nexus-issue.html). No known solution.
Some of the issues reported were from GSM variants of the phone. Although, I feel as if the CDMA version is affected more than the GSM version. Perhaps this is an error as I focus on Verizon-my provider.
I called Verizon... You know the story from there. They sent me three other Galaxy Nexus phones, and all 3 had the issue. I ended up buying another phone (at a reduced rate) so I could talk to clients-it is hard enough starting a business in this economy...
I kept the Nexus because Verizon stated a fix was forthcoming (this was end of January). February, March, April, ... Finally, the 4.0.4 update arrived in June, and I applied the update! The issue remained.
Steps I've taken to identify the issue:
1. Removed all apps not sent with original phone (I call this stock V Android for GNexus);
2. Enable wi-fi, BT off, LTE/CDMA set as networks, and issue occurs;
3. Disable wi-fi & BT, use LTE/CDMA... issue occurs;
4. Disable wi-fi & BT, use 3G (CDMA) only... issue occurs;
5. Boot into safe-mode and repeat 1 - 4... issue occurs.
After all those steps, Verizon agrees to replace it with a phone of my choosing. I am nervous about a Samsung (the SGSIII) since my Captivate's GPS never really worked and because my Nexus can't be used to make calls.
I call Samsung support and get a trouble ticket and send the phone to Texas for "repair." I get the phone back (2 weeks later) stating they "replaced component" (without stating which component was replaced). Samsung states they "hooked it up" and found a "dropped call issue." I never complained about a "dropped call issue," but perhaps that is what they call my issue...
I boot up, and I am hopeful it is fixed. I notice I have a "scratchy" audio out of the phone's speaker. Great, an issue I did not have when I sent the phone in to Samsung for repair... Furthermore, the issue occurred on the first phone call lasting over 2 or 3 minutes (with a client, no less). I call back, apologize, and let him know I'll call from a land-line as soon as possible...
I call Verizon back. They are willing to let me have a new phone, great. I call Samsung to let them know their "repair" didn't fix the issue. The Manager I spoke with was polite, but all he could offer was for me to send the phone back so that he could "replace the whole motherboard." I'd be out of a phone, and I can't get a new phone from Verizon if I send in my Nexus for review.
What did I ask for?
I asked Samsung to send a technician to North Carolina, and I stated I'd lend him/her my phone. Let him/her stay here for two weeks so that he/she can get enough data to report back to Samsung.
What have people said? Basically, I have heard the following 6 potential causes:
1. DTMF tones;
2. Communication via reverse channels with LTE;
3. VIA chip;
4. Microphone malfunction;
5. Network (Verizon) or left-over tech from Alltel or other acquisition;
6. Android software issue; &
7. SIM card.
Of the above, I don't think it is a SIM card. I've used my SIM card in a DROID Razr MAXX, and I've never had the issue happen when I'm using my MAXX. Therefore, not a SIM issue.
How am I supposed to find out what is the cause? I tried to use OpenSignal, but I only have 1 tower near my house, an LTE tower that always seems to have a strong signal. Happens when I'm at home.
What could I "dump?" What logs do I have that would be useful? Why isn't Samsung or Verizon asking for them?
Where I sit today...
I am tired. I am trying hard to get Verizon, Google, and Samsung to step up and spend a small amount of cash to get techs in the field. This really is the only way they are going to solve this issue.
I am not sure I want a Samsung phone, so I may just hold my "credit" open so I can get a free phone when Verizon comes out with a new device I want... If, If they come out with a device I want...
The SGSIII seems nice, but the bootloader is locked-the Nexus is open-what I bought it for, and I don't feel as if I should be penalized when I didn't cause the problem with the phone, network, or software...
People have complained to the FCC, to various Attornies General, and to I think everyone should read their Verizon Contract where you waived the right to class-action status…
Where are you? What provider do you use? Still have the issue? Has your issue ever been solved? Did it go away while you were in one of those states where the issue happens less (not NC, MN, CO, or CA)?
How can such a small population of affected users get appropriate relief without a lawsuit? I'm asking Google, Samsung, and Verizon to step up, be responsible corporations, and deal with an issue that is making them all look horrible to those affected.
1. A "Google-experience" device = Galaxy Nexus;
2. A Samsung Galaxy Nexus phone; &
3. A Verizon phone sold with their service.
How are 1 - 3 looking anything but bad? If this is a "Google-experience," give me Apple or Microsoft. If this is Samsung, give me Nokia. If this is Verizon, give me another provider...
Out of the three, Verizon, at least, is offering me a new phone and, perhaps, a car dock to make up for the money I spent on the Google-experience Samsung-made Verizon-sold & Verizon Branded Galaxy Nexus. Out of the three, only Verizon is stepping up to the plate to try and make me, the customer, happy.
Samsung at least tried to fix it, and they are willing to try again. It could be the problem is NOT hardware related, but I think Samsung should send a tech here to find out. How else will Samsung know with any certainty?
Google? Where is Google? Silent. Shame on them. A Google-experience. Right... Eric Schmidt would be proud...
Summary...
I've got to decide whether to send it back to Samsung for a "complete overhaul" which, basically, means a new motherboard. What to do about a new phone or hold the credit for a phone that may be introduced later.
Choices, choices....
