[Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot] hanseric:
Ok so I'm trying to trace down what might be happening here.

Ive got a LG Tone Pro 750 BT headset which I totally love for the most part (epic battery time for one thing). Bought it about a month ago.

About a week ago, maybe two, something weird starts happening. I'll get a call, pick it up and no sound. Caller may or may not hear me, but if they do, it appears to be garbled (I've done a poor job of asking callers if they could hear me and inquiring about that part of the experience so not very good feedback there).

Since I'd had the BT headset for a couple weeks already, I don't even consider there could be a problemo there. So I take the SG4 to Sprint and have a tech check it out.

He comes out to see me (never happens).

Asks me if I have the LG Tone Pro headset. He then proceeds to tell me that he has the same problem on his LG (!) phone with that headset (although it's a later model than my Tone Pro 750...next one up from that model).

He says that the only way he has been able to fix it is by unpairing and re-pairing the headset. Says he has to do it every other day or so.

That was early last week.

So for the next day or two, I go without the headset being re-paired. All is well with the three or four calls I get.

I pair the headset but don't get any calls. I do listen to some podcasts and that is fine (but was never a problem so no change there).

The next day (this morning) I get a call. Problem is back. I try turning off BT making calls and that doesn't fix it. Have to restart the phone.

So I do and I can now make and receive calls. However, BT is off.

It sure looks like this is a problem with the headset.

But I also noticed a preponderance of SG4 owners complaining about a somewhat similar issue where the mic would suddenly turn off on their phone, mid call. Seems WIFI signals would somehow interfere with it (I tried turning off WIFI though and that didn't fix it).

Is there anything else I can do to diagnose this better and maybe get to the bottom of it?

What could be happening here? Is this the headset not playing well with the OS? Is there a way to tell?

Why would this start happening off a sudden two weeks after I'd been using it heavily with no problems?

Also, I'm trying to find more instances of this issue online but it's tough one to Google.

(As a side note, LG doesn't seem to be a very good company when it comes to customer service. I saw several instances on Android Central where their customers reported issues with the headset and then were told their posting violated the TOS of the forum. WTF is up with that? Have they not realized there is ths thing called the Internet? Do they think people won't eventually catch on? :eek:)

I'm seriously considering returning this thing, but the truth is, I really want to keep it if I can get it to work. Probably a pipe dream though, now that I've written all this out. lol

I'm even considering rooting my SG4 and throwing another ROM on to see if that fixes it. That's how much I like the headset.

Happy to receive any feedback from fellow forum members. Thanks in advance.

PS: Just realized I haven't really tried just unpairing and re-pairing more than once so I'm going to test that some more over next few days meanwhile...