Google Voice Won't Work With Bluetooth Headset After Jelly Bean

[Missquote2]

I am SO frustrated. I had no idea I was installing the Jelly Bean update when I updated the software on my phone. Note to Verizon Communications team: PLEASE do a better job of communicating significant software updates. I would not have installed Jelly Bean. I learned long ago to stick with factory OS on my phones.

Since the update, I noticed that I could no longer dictate texts and emails. Also, my call recording app no longer worked. I switched to Swype and it would work for a few minutes and then stop.  I could still use my bluetooth headset to make calls and S voice worked (although, like others here, I noticed that it's now worse--it doesn't recognize any contact names I request anymore). After trolling Android forums I found that the problem is with the bluetooth headset. You can still dictate when the phone's bluetooth is on, but when a device is connected, all bets are off.

I almost did a factory reset, but then I read that a hard reset will not restore ICS, nor did it resolve this bluetooth Google Voice issue for the few people who tried it already. In fact, resetting caused more problems (eg., more battery drain and removal of Adobe Flash, etc.).

Does anyone know how I can go back to ICS? Bluetooth and Google Voice are the two features I value most in my phones. This is a NIGHTMARE.

[Ann154]

No, you can't go back to ICS officially. Any thing else would involve voiding the phone warranty.

[Missquote2]

Well, then it would be helpful if JB 4.2.1 be pushed out to Verizon Galaxy S3 users as soon as possible. I understand that this update addresses the Google Voice issues. That would be refreshing.

As for the phone warranty....In my view, this phone is now broken, so I'd like it replaced with another phone that allows me to use the two features that allow me to conduct business efficiently (bluetooth and dictating correspondence). This bug is a deal breaker for me. I'm close to breaking my contract with Verizon and getting a Motorola phone from another carrier. Frankly, my patience with Verizon's market leader arrogance is wearing thin.

[jimpreis]

The issues with JB 4.1.x on VZW SGSIII so far are...

- Google Music is broken.  After playing one or two songs the device fails to recognize the end of a song and just plays silent forever.  The only fix at this time is to stop the process or restart the phone.

- Headphone jack will intermittently and randomly stop audio out via the headphone jack and return it to phone speaker out

- Voice input in (whether it's dictation, Google Now or anything else that's supposed to be listening) is broken with BlueTooth enabled.  At the very time you would most likely want to use dictation or voice input, it's broken because you're likely pairing with your car's BT

How does this stuff get out???

Is it tested AT ALL???

[rcschnoor]

1 - Google Music works just fine on my VZW SCSIII with JB

2 - haven't used a headphone jack so I can't say.

3 - works fine with my BT.

[jimpreis]

rcschnoor -

The Bluetooth/Voice Search/Dictation issue is a valid issue for the OP, a valid issue for me and oh yeah, the hundreds of other people affected by the, "Google Voice Search stuck on "Initializing" bug filed here on the Google Android Project page.  Here is yet another reference to the same issue from Android Central.

The "Google Music freezing after Jelly Bean Update on Galaxy S3" is also a valid and documented bug located here also on the Google Android Project page.

So I ask, how does sharing with these people that do have these issues, and are affected by them, that you are not experiencing these issues help in any way?  Isn't that the whole purpose of a community forum to help others?

[rcschnoor]

It may not help the OP, BUT if no one records input of instances without these problems, someone could very easily deduce that ALL Galaxy SIII handsets on VZW are having these problems and this is just not the case.

I'm sorry if you didn't want me to let people know if/when you do upgrade your VZW GSIII handset to JB, it has a good(probably a great) chance of working just fine after the update.

Edit: If only posts are shared describing the problems, then some would most likely think that ALL of these handsets are experiencing these problems and this is just NOT the case. Sorry if you don't want this information to get out.

[Missquote2]

That's nice. Sounds like your primary concern, rc, is not tarnishing the marketing momentum of this device. I understand...I've been a marketing professional for more tha 20 years, so I understand it's important to put out these fires as efficiently as possible. But as JimPreis points out, the JB update problem with Google Voice and Music has been documented by HUNDREDS of people on the top Android forums. And this is not an aesthetics issue, JB has cripped functionality of our phones. I feel like I just bought a new Ferrari and someone from the dealership came to my garage overnight and, without my permission, replaced the tires with more expensive tires that don't fit.

My question for Verizon: 1. Is the 4.2.1 update going to be pushed out to Galaxy SIII phones soon? Feedback on the forums seems to indicate that 4.2 addresses these issues. This seems like the most logical solution..

2. If not, is Verizon prepared to allow those of us who have lost functionality of our phones to JB to replace our handsets?

I'm not a statistician....I don't know how many have this problem, all I know is that on December 20, I had a fully functioning phone, and on December 21st. I did not. And, like many Verizon GS III customers with this problem, I am not happy.

[rcschnoor]

Sorry to disappoint you, mi, but that is not my primary concern.

As people who have problems tend to voice their displeasure more vociferously than those who are happy with the update, the fact that HUNDREDS of people on the top Android forums would seem to point to the fact that a very small percentage of updates actually have these problems. out of the MILLIONS of SGIII phones which have been upgraded. THAT is my primary concern.

If someone considering the SGIII as a purchase decides against this phone in favor of a phone which in their mind is a lesser phone only to see the vast majority of SGIII users on the street happily using their SGIII phones without a problem, they will only come back on these forums YELLING how Verizon had TRICKED them into settling for a phone they did not want instead of the SGIII.

Yes, there are those out there who are having problems with the update, but there are most likely many more who are quite happy with the update.  Call it "not tarnishing the marketing momentum" , "putting out these fires", etc... but I tend to to call it exactly what it is. I don't have any of the problems with the update listed on this thread. Failing to point this out only leads to the FALSE impression that if you have a SGIII and get it updated, you will be sorry. This is just NOT THE CASE.

[jimpreis]

At the top of this page there are links to "More like this".  They include different posts about the same problem...

"Voice dialer useless after Jelly Bean update"

"Jelly Bean update completely killed true hands free voice dialing"

"Bluetooth problems after Jelly Bean update"

THAT'S ON THIS SITE.

Then add the HUNDREDS of other citations of the same problem on the official Android bug registry maintained by Google.

Then add the many reports of the same issues at Android central.

If you're asserting that these issues are isolated, that, my friend, is JUST NOT THE CASE.

And what I call it is perspective from many, many paying customers.

[rcschnoor]

Nowhere have I ever said these issues were isolated. All I have said is people who are unhappy with something are more vociferous than those who are happy with the same thing. Take it however you would like. Read into it whatever you would like. It is nothing more than what it is. There are instances of GSIIIs which DO NOT have these problems, but maybe you would like these to stop.

[jimpreis]

What is wrong with you?!?!?

This is where WE'RE SUPPOSED TO COME FOR COMMUNITY SUPPORT FOR ISSUES.

Or maybe you'd just like to not help others by parroting, "I don't have this problem."

[rcschnoor]

Nothing wrong here. Getting an idea as to the extent of the problems is almost as important as what problems exist and the cause of the problems, or even why not all units have the same(or any) problems. I assume pushing a fix which causes additional(or different) problems is not what anyone is looking to accomplish.

After all, the last update wasn't so successful according to all those reporting the current crop of problems. I assume you wouldn't want the next update to be just as successful.

[Missquote2]

I am very happy for the customers who had a flawless update. But for those of us who shelled out good money for this phone last summer and were very happy with it before JB crippled it, this is a serious issue. I had been singing SGSIII's praises to anyone who would listen...I even persuaded several AT&T iPhone customers to make the switch to Verizon's SGSIII. Whether 100 or 100,000 people have this problem is irreleveant. If a software update damages important functions on a once working phone, the carrier should remedy the situation: Either inform affected customers of a reasonable timeframe for providing a software update to fix the damage, or offer to replace the phones (in this case, SGIIIs with ICS would be acceptable). As for pushing out "fixes" that cause more problems....well, that's where testing comes in, right???? At least it should.

Why not let the customer decide if they want to hose their phone's operating system? I am a firm believer in keeping the factory OS, because of the high potential for bugs with updates.  I DID NOT want Jelly Bean. I would have refused it. I was not given a choice.

In any event, I am very disappointed in Verizon's shoulder shrugging customer service response to this problem.  And I feel it's only fair to warn Verizon customers who value full bluetooth functionality: Buyer beware. Period.

[jrsatx]

I called Verizon and the rep said that he hadnt heard of the issue and that i needed to go to mazda to get my bluetooth updated.... I told him it had nothing to do with my bluetooth because that worked just fine up until the JB update. I called Samsung, they are aware of the issue and have a patch in the works to be released anywhere from 2 weeks to 1 month. Now verizon is aware of it....

[Missquote2]

Thanks for posting this update. I had called Samsung after Verizon's customer service rep professed ignorance about the problem. Samsung thanked me for the feedback. I'm glad to see that they are doing something about it. Hopefully, Verizon won't sit on the patch.

[gregoryggg]

I have the same problem with my plantronics headset.  I have to turn off the headset to get the voice to text to work reliably.  Kind of defeats the purpose of hands free in the car.  Turn on the headset to answer calls, turn off the headset to voice to text.   VERY FRUSTRATING.  I've already swapped out the SIM card and did a factory reset.  No difference.

[jimpreis]

The final answer is this.  It's broken and no one is going to fix it.  You can continue to read my rant, but it won't change anything.

Verizon's aware of it and they refer you to Samsung.  When I called Samsung they said this.  "It's broken.  The defect takes away functionality that you had.  We're aware of that.  We have no plans to fix it."  That is precisely what they told me yesterday.  And the joy of that was they first told me to do a factory reset of my phone which I wasted an hour of my life doing for nothing.

So the premier Google Application, Now, on the halo Samsung phone, SGS3,  obtained through the purported best carrier, Verizon, is broken when BlueTooth is enabled and all three are aware of it and there are no plans to do anything about it.

[jimpreis]

The Jellybean 4.1.2 update appears to have fixed the Bluetooth Issue.  It was pushed to my phone yesterday.

And so here we are a scant 9 days after BOTH Verizon and Samsung confirmed no fix was in the works and no ETA was given despite extremely pointed questions about exactly that and there's a fix that started going out on 3/7.

You guys can't even get fixing a horrible mistake right.

Complete and utter failure to communicate internally, externally and never once did I feel like a single person I spoke to was considering the issue from the customer's perspective.

[SBMongoos]

I thought it was fixed to with 4.1.2. Had to install the latest Google Search (2/13) update as well. This on this past Saturday it no longer works again. I use this a lot and especially in my car that's a stick shift. Sux!!  I swear there is always some issue with these phones. Owning an Android is like owning a Windows PC in regards to issues, updates, fixes. LOL.

I've noticed Verizon's support is not what it used to be. Especially tier 2.

[blueline17]

I second this. I thought, and hoped GREATLY, that 4.1.2 fixed it. Nope. Same garbage. No voice entry can be used while bluetooth is connected (other than actually speaking on the phone)--things like Google Now will simply fail. Interestingly, the initial "Google" command to cause Now to "listen" does work, but it never gets past "initializing" as described above.

This trash continues even after 4.1.2.

I like how it was said by jimpreis above: "So the premier Google Application, Now, on the halo Samsung phone, SGS3,  obtained through the purported best carrier, Verizon, is broken when BlueTooth is enabled and all three are aware of it and there are no plans to do anything about it."

Absolutely correct.