iPhone 4/iOS 4 bluetooth muffled on other end

well thanks Breinders, what i'm going to do is update my 4.1 to 4.2, hopefully it'll fix the bluetooth problem, and if it doesn't i'll just take it to the store, get a brand new one, sell it and get Metro Pcs !! i'm up to my head with this phone man ! and i'm sorry to say this but Apple *****!

Sorry about the delay in replying - been on the road the past two days. You can get the VH110 from Sony's website - www.sonystyle.com - http://www.sonystyle.com/webapp/wcs/stores/servlet/ProductDisplay?catalogId=1055 1&storeId=10151&langId=-1&productId=8198552921666269892&tab=featuresTab

If you have a sony store near you, you can check their inventory online before going there - or order online. I just spent, as noted above, two days on the road with heavy bt use and absolutely zero issues. I definitely get the 30' of range - as I left the phone in the car when getting gas and didn't have the bt disconnect until I was inside the station, at least 30' away. This was NEVER possible with any of the other headsets I've owned. They would disconnect as I walked around the car.

It's definitely not a v1.2 bt standard issue - the VH110 is 2.1, not 1.2. It has to be something else causing the issues and whatever Sony is doing just works. With all the issues I've had with Jabra, Plantronics, BlueAnt and Jawbone, then have the Sony work, it HAS to be something related to what Sony is doing in producing their products.

I didn't do anything else with the phone. No resets, no return and exchange, just connect the headset and it works...the way it's supposed to be.

Not to ruin the Sony-party, but I have a VH300 that DOESN'T work properly. People say I sound muffled and they can barely hear my voice at all. I hear them perfectly.

I think, but can't confirm, that the VH300 is an old discontinued model. I believe that others have had good experiences with their newer models, VH110/410 and a few others. I continue to have perfect service with my VH110, absolutely no connection issues or muffled sounds for the person I'm talking to. This is on an iPhone 4 that completely failed at working with a Jawbone Prime 2, Plantronics Pro, BlueAnt T1 and a Jabra (don't remember which one it was as I was so frustrated, I tossed it).

Hi,

Does anyone have insight to the upcoming iOS 4.3 update? Does it fix anything?

If it doesn't address these incredibly annoying and frustrating BT problems, I'll be taking my iPhone back to the retailer for a refund. Hope I have a better luck with BT on Android then.

--
Schumi

I tried the Sony VH110 that JMacGyver has been raving about and it's no better with my iP4 than my Plantronics Voyager Pro. I still sound like a cyborg and no one can understand me at times - especially once I get 10 feet away or so (but sometimes even when the phone is in my pocket). Same exact issues with 3 different iPhone 4's that I've tried while using them with a Jawbone, Plantronics and now a Sony headset. I don't know if it's an environment issue at my house with my other electronics or what, but I didn't have ANY bluetooth issues in 2 years with my iPhone 3G.

I hope 4.3 fixes this, but I'm not holding my breath. Seems like it's a hardware issue since the problem has been present since the 4.0 software.

Thought I might chime in.

I've tried quite a few BT now with limited success. I have found two however that "work" with my iphone. They are the Plantronics Explorer 395 and the M100. If I get more than a few feet away the problems start, but as long as I keep them on my person I've had few to no complaints.

I'll add that I've never had any problem hearing others, or any other issue with the phone/BT except people saying they can't understand me. These two units solve the problem, for me.

Jkozlow3, did you reset the phone or the BT setting first before using the Sony? It's strange that I went through 3 different headsets and then got perfect service with the Sony. It's remained rock solid and will only disconnect when I'm past 30' and then reconnect when I get back in range. I've also not had any complaints from people saying my voice is muffled as I got regularly with every other headset.

Maybe I got lucky. I would certainly hope they fix whatever is wrong with BT. I would like to be able to use my voyager pro for times when I need sound canceling.

The interesting thing about Apple's BT issue is that some users are able to get good functionality and zero issues from a given headset (like the VH110) on their IP4's running 4.2, and other users try the same headset on their IP4's running 4.2 and get zip.

I'm not a signal or software engineer but that tells me it's not purely a hardware or IOS problem. Likely it's some combination of hardware, IOS and apps. I think there are one or more apps that, when present on an IP4, are creating some kind of IOS-BT conflict within the IP4.

If we could compare the app list of someone that is not having BT issues (like JMacGyver), with someone who has tried an identical BT headset (VH110) and gets lousy performance (like jkozlow3), we'd have a list of apps on the non-performing IP4 that we (or maybe APPLE?!) could evaluate and maybe find one of them that is creating the IOS conflict / degradation.

Just a thought.

This is beyond ridiculous. I, like most you, experienced the muffled BT problem when I got my iPhone 4 at launch. 4.1 "fixed" the muffled problem, but since then I have a problem where my headset and my phone will every so often connect, but not really. The phone lists the headset as an audio source, but will not switch to it. When i issue a voice dialing request from the headset, it registers the button press (confirmation tone 1), and displays the voice dialing prompt on the screen, but does not pick up my voice command on the "ossiliscope", does not produce confirmation tone 2 the headset normally makes, nor does it produce Apple's voice command prompt, the same one you hear when using ear buds for voice commands. Pressing the headset button again does still cancel the voice command request It is a Blue Parrot B250-XT that worked just fine with my 3G. The only remedy is for the headset battery to be low enough that it loses power during a recharge, then it works fine after the recharge. Reboots of both the headset and the phone do not help, nor does forgetting the pairing on both ends.

Is anyone else experiencing this or have any suggestions?

One of the things I've discovered is that the voice command function has some conflicts with other apps - specifically with regard to the volume settings. Try checking where the volume is set with the voice prompt, while not connected to your headset. Hold the home button to get the voice prompt to activate, then quickly use the volume up button to move it to maximum.

I've had the same issue and realized that the reason it wasn't working was the volume was too low or even mute - not because I physically adjusted it down for the voice prompt, but I know I did do so for other apps - which I believe may be effecting the voice prompt.

Thanks for the reply but I believe we are experiencing separate issues. Even if I do speak at or after the visual prompt, the phone doesn't respond and isn't hearing me based on the ociliscope or w/e on screen.

It could be separate issues, for sure. I know that one game app (that I just deleted due to this problem) would cause issues in volume control of the voice prompt. If I turned off the sound in the game, voice control wouldn't work - like you, it would not register my voice on the oscilloscope, and I couldn't hear the voice prompt either.