I called Verizon and asked about this issue. Apparently it is a known issue. As usual, they had no idea when a fix will be o
I told the tier 2 tech support guy that the problem is a serious driving safety issue, he agreed with me. His suprevisor said that I had the
option of
exchanging my 11-month-old Galaxy Nexus for a brand new Samsung Galaxy S3. He put notes in my account
for this offer. He said all I had to do was to visit a Verizon corporate-owned/operated store and they'll give me a new GS3.
Hmmmm..... not sure if I want to do that. Do I really want to give up my Galaxy with Jelly Bean for a VZW GS3 with outdated
ICS software?
Verizon seems to prefer to exchange phones to shut up complaining customers.This has already happened to me once.
When my VZW Samsusung Fascinate was still on Froyo, it had many software problems which Verizon could fix.
(Gingerbread was the solution, but you know how long it took Verizon to push that out) Anyway, I was offered a free
exchange from my old banged-up Fascinate to a new VZW Samsung Droid Charge. I did accept their offer and
received a new Droid Charge as promised. Now I don't know if I want to go down the same road and exchange my
Galaxy Nexus for a new Galaxy S3. Perhaps I should wait a couple more weeks and see if they'll upgrad the offer
to a Galaxy Note 2.
Sheesh... why can't Verizon, Samsung, and Google come up with a fix for this "simple" bluetooth headphone problem?
(P.S. being the bonehead that I am, I did not notice this thread before starting another one asking the same question... sorry)