Is anyone else having issues with the bluetooth connectivity with their HTC Inspire? It pairs with my car with no issues. The bluetooth drops in and out. It says bluetooth headset connected... then 1 minute later it says bluetooth headset disconnected... and so on.
The car doesn't recognize that it is gone so the sound stops on the speakers in the car but the phone doesn't switch the source to the phone. I have to switch it manually to get back to my call.
Anyhow, I see a lot of articles on google where people are complaining about this but I have been unable to find any resolution. Has anyone here had this issue and resolved it?
Any advice would be greatly appreciated.
Same is happening with mine. I paired my inspire with the car and it connects. But if I use it no connection or doesn't dial. When I receive a call and disconnect, my car will stop the connection but the phone stays on.
I might be restoring to stock to see if it's just an inspire thing or bug with different ROM's
zerocalories said:
Same is happening with mine. I paired my inspire with the car and it connects. But if I use it no connection or doesn't dial. When I receive a call and disconnect, my car will stop the connection but the phone stays on.
I might be restoring to stock to see if it's just an inspire thing or bug with different ROM's
Click to expand...
Click to collapse
I am using my phone stock and was thinking about rooting it if it would fix it. I am new to Droid phones so I have not read enough to be comfortable with rooting quite yet...
Have you found any solution to this issue? I've just bought a BT headphone (Plantronics 903+), and as a I put it in my left pocket (where it is supposed to be placed since the headphone antenna in the left side), connection dropping starts and never stop happening. The movement seems to stress the connection quality and it gets really annoying, I can't listen to music without having this chopped streaming all the time.
I thought to post this question here since this is the only post I found about the same issue, but I will put a specific one about Plantronics and Inspire if I can't come out with a solution. I'm really very disappointed now with the headset, the phone or I don't really know which one is the guilty one.
Thanks in advance
it will not work. since after rooting, my phone cannot pair with my Garmin GPS, but it did with the stock rom.
greatzt said:
it will not work. since after rooting, my phone cannot pair with my Garmin GPS, but it did with the stock rom.
Click to expand...
Click to collapse
I still have the stock rom
Ok so this question has been issued 3 times on XDA already, and some more on the net. However, noone, on the entire world, seems to have an idea on what to start with.
Why can't my phone act as a headset (bluetooth)?
An Android phone (but could be another OS) has BT drivers, speaker, microphone... all it needs! I undderstand phones are usually designed to be used with a BT headset rather than as a BT headset, but i see many situation where that could be handy:
- two phones (all calls taken from one)
- calling through computer, but handling the phone
- same through tablet
Now, here on XDA there are all kind of skilled hardcore devs. Why nobody ever got the Android BT driver and apps to turn the phone into a headset? Whyyyyy?
Thanks for reading
because they all bought in-ear bluetooth kits and couldn't be bothered.
Why not just buy a logitech 930 and roam the house? Probably a bit better on the head and if you are friend with Beyonce like me, great to hear in 7.1.
Lol, i wonder why every single thread asking this question always gets the same answer: "why not buy a headset?"
Although i understand what you are meaning, this does not answer the original question
Can someone please answer the actual question with technical details or is this subject cursed for life to getting no answer/off topic answers?
Roam the house? Bluetooth has a very short range.
If someone made android headphones that streamed PC stuff over wireless you'd have a far longer range and much better audio quality.
i really need that.... (why not just buy "BT", very meaningless since you are not understand our situation)
For me, HTC Flyer (tablet) x 1, HTC ChaCha x 1, I have hundreds of BT headsets, but dont you think:
1. extermly trouble every day charging for 3 items?
2. to bring 7" tablet, one cellphone and a bt headset more?
3. *** MAJOR PROBLEM*** i have 1 SIM card only (network and phone), with two mobile... if i can put the SIM into Flyer and pick up the phone from ChaCha that will be wonderful.
Kind of like the above poster I have an Android phone with a no data plan, but I have a galaxy tablet with a tablet data plan
So it is an very troublesome to yell at the tab to talk on Skype or Dell voice or other voip.
It would be very good if I can use my phone to act as the headset
I do not want to hang a Bluetooth headset on my ear
So...anyone has any idea?
Hi,
there is a solution you can use the samsung galaxy player 3.6 device with android 2.3.6.
It is a multimedia player not a smartphone but it has the BT profile so you can use it also as a headset for your phone or tablet and it works really great.
It can be a nice add-on for a tablet or an oversized telephone.
joexda75 said:
Hi,
there is a solution you can use the samsung galaxy player 3.6 device with android 2.3.6.
It is a multimedia player not a smartphone but it has the BT profile so you can use it also as a headset for your phone or tablet and it works really great.
It can be a nice add-on for a tablet or an oversized telephone.
Click to expand...
Click to collapse
Anyway this could be ripped out of a ROM for that device and made to work on others?
darn what a dissapointment to notify that it will not work.
I wanted to keep my work phone and private phone sepparated but picking up all calls with my private phone while no one knows my private number seems so great...
any news on this??
Hi all,
Just wanted to put this out there to see if anyone else had experienced this. Using SGS2 skyrocket - stock 2.3.5 UCKK1 (rooted) and then updated UCLA3 everything (rooted) - When on a phone call after sometimes 1 minute and then other times 5 minutes my microphone stops working and the other person cannot hear me. I can hear them fine, but they cannot hear me.
Wired headphones work without an issue, but the internal mic seems to have an issue with my phone. a work around I read for the non LTE SGS2 works where you hit the speakerphone button and then they can hear you again and if you turn it off it buys you another 5 minutes or so on mic.
So frustrated with this that I am doing an exchange today on the phone.
Just wanted to see if anyone else had experienced and if there was a know n problem with the phone? Google and XDA returned very little.
Thanks!
MB
Hey I too also have this issue, I had a temporary fix which lasts longer than turning on the speaker but it's still temporary, I have the skyrocket on Rogers and I called them in about it, apparently it has something to do with the network, they did some reset and told me to restart my phone and it worked for about a week or so, hope this helps, if anyone has a fix to this please reply
I read another case like this awhile back, try searching it up. i believe it was rma'd though
I have a very similar problem, I go "in and out" a lot. The problem is the noise canceling mic on the top of the phone by the headset input, I left myself voice mail on my home phone and while talking moved my finger gently over the tiny microphone hole and that causes me to go in and out.
For most turning of Noise Suppression in settings will work, for me it does nothing as if it is perma on lol except on ICS where it actually turns off (dont ask me I have no idea why)
I am wondering if any of you fellow Verizonites would be willing to help me test this out, as I have already asked my friend with the AT&T version if his does this, and it does not:
When connected to the aux in (very common on cars and stereos nowadays, you know, so you can listen to music off your phones and iPods and MP3 players, etc.) I now have the SAME incredibly aggravating problem I could never resolve with my Fascinate. As usual, I have my bluetooth connected to take the call. When I answer the call, I hear NOTHING over my bluetooth unless I disconnect the audio cable out of the headphone jack!!! This is a huge safety hazard, as it takes your hands and eyes off the road, requiring you to disconnect a cable every time you get a call!!
I called Verizon and complained about this with my Fascinate to no avail. I never had this issue with my Droid X, HTC Eris, or my Galaxy Nexus, another dual core Snapdragon based Verizon LTE phone made by Samsung.
Not to mention the SGS III is laggier and less responsive than my Nexus, although not as bad once you disable S Voice (S is for stupid, by the way, at least in my opinion ... I can't get it to work worth a darn!! Could be that I'm the stupid one, but I've certainly given it a lot of effort in a very quiet environment.)
This is horrible because the screen is incredible, and the battery life far outpaces every other smartphone I've ever had by a ridiculous margin, so PLEASE, fellow Verizon SGSIII friends, help me out if you can!! I don't want to have to return this phone, but reasons to do so are stacking up.
If there's no fix for the audio cable thing, that is a definite deal breaker, and enough to make the phone "defective" in my opinion. That is such a blatant safety hazard. I do NOT want a "Fascinate 2". The other issues pale in comparison to the audio cable issue.
Here is a video of the AT&T version NOT having this glaring safety and functionality issue:
http://www.youtube.com/watch?v=A37p4fF-h-k
This is a glaring safety issue you are right. I planned to have bluetooth on my ear to take calls but have the phone plugged in for music on my car speakers.
The other thing is I bought a Samsung HM7000 thinking it would work with the SAMSUNG S III. Pff. I guess FreeSync App doesn't support the S III yet. I will definitely express to Verizon/Samsung why I have to return this headset if this isn't solved in a few weeks. I will contact Verizon on this.
So this doesn't affect other US Galaxy S III units only Verizon? That's so weird but it also suggests it's an easy fix.
I tested it with Bose Bluetooth earpiece and that works, somewhat. If you have the Aux plugged in and get a call, the phone picks up your voice from the Bluetooth and plays the other guys voice through the Aux. Unplugging the Aux mid-call will route the other guys voice back to the Bluetooth. In both cases both me and my friend could hear each other.
There is a problem though. When the Aux is plugged in, with Bluetooth our not, the call quality will drop significantly. It will sound as if you're in a horrible signal area and will cut out every other second or so making it impossible to carry on a conversation. Funny thing is as soon as I unplug the Aux the call is back to normal and we can hear each other just perfect. It's as if with Aux the noise cancellation kicks in and starts cancelling out everything, including your and the other guys voice, lol. Not sure if that's just my phone or SGS3 in general. I actually intentionally used this "glitch" to avoid taking to annoying person. Just tell them "I'm in a bad area and can't talk" and plug in the aux mid-call and they will stop bugging you as soon as they hear the voice glitch up
My bluetooth headset works fine with the audio out through the "dock" connector.
macdroid01 said:
This is a glaring safety issue you are right. I planned to have bluetooth on my ear to take calls but have the phone plugged in for music on my car speakers.
The other thing is I bought a Samsung HM7000 thinking it would work with the SAMSUNG S III. Pff. I guess FreeSync App doesn't support the S III yet. I will definitely express to Verizon/Samsung why I have to return this headset if this isn't solved in a few weeks. I will contact Verizon on this.
So this doesn't affect other US Galaxy S III units only Verizon? That's so weird but it also suggests it's an easy fix.
Click to expand...
Click to collapse
Same here
Using bluetooth in a 2009 infiniti, AUX jack prevents proper bluetooth calling or receiving. I had come to rely on this in my other phones (HTC).
same here too
I upgraded from a fascinate to a s3 and have the same problem on both phones. It is really annoying and I'd love to find a fix for it.
adsbar said:
Using bluetooth in a 2009 infiniti, AUX jack prevents proper bluetooth calling or receiving. I had come to rely on this in my other phones (HTC).
Click to expand...
Click to collapse
I think I am having the same problem with the Bluetooth in my 2010 G37. It seems like if u connect via Bluetooth for media audio, I can't get calls and vice versa. Plus when I connect to media audio and try and switch back to just phone, it doesn't auto connect when I get in the car.
My Rezound didn't seem to have any of these issues.
Sent from my SCH-I535 using xda app-developers app
This was the case with my 1st generation galaxy s epic 4g. Looks like Samsung still hasn't recognized this as an issue. The smart developers here ultimately fixed this on my epic but my s3 is still suffering from this... Btw I'm on synergy. I would love for someone smarter than me to figure this out. Please, please....
Sent from my SCH-I535 using Tapatalk 2
sinman02 said:
This was the case with my 1st generation galaxy s epic 4g. Looks like Samsung still hasn't recognized this as an issue. The smart developers here ultimately fixed this on my epic but my s3 is still suffering from this... Btw I'm on synergy. I would love for someone smarter than me to figure this out. Please, please....
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I don't know who to blame, Samsung or Verizon. I have the Samsung Galaxy Nexus and it does NOT have this issue. Never had that issue, with stock or custom ROMs. A good friend has the SIII on AT&T and it also does NOT have this issue, as the video above demonstrates. He also owns the Galaxy SII, which also does not have this issue. I used to rock a Droid X. At least my Droid X did not have this issue, although I have read reports of other Droid X owners' phones having this problem. My old HTC Eris also didn't have this issue. But, as mentioned above, my Fascinate does have this issue.
It's horrible. I have messaged Samsung, and they have responded that they are looking into it. It's the same response they gave me several weeks ago when I first posted on the support page on Facebook about this issue. I have also called and complained, after which their support tech said she wasn't yet fully trained on the SGS III yet, and they had a special number for me to call, which of course wasn't open at the time.
If a dev can figure this out, he can at least count on a donation from me.
I am sick of this ... I decided to keep this phone despite this issue, because of all the other goodness it brings to the table (especially battery life!! Wow!!) But this is still a horrible issue.
SirKronan said:
I don't know who to blame, Samsung or Verizon. I have the Samsung Galaxy Nexus and it does NOT have this issue. Never had that issue, with stock or custom ROMs. A good friend has the SIII on AT&T and it also does NOT have this issue, as the video above demonstrates. He also owns the Galaxy SII, which also does not have this issue. I used to rock a Droid X. At least my Droid X did not have this issue, although I have read reports of other Droid X owners' phones having this problem. My old HTC Eris also didn't have this issue. But, as mentioned above, my Fascinate does have this issue.
It's horrible. I have messaged Samsung, and they have responded that they are looking into it. It's the same response they gave me several weeks ago when I first posted on the support page on Facebook about this issue. I have also called and complained, after which their support tech said she wasn't yet fully trained on the SGS III yet, and they had a special number for me to call, which of course wasn't open at the time.
If a dev can figure this out, he can at least count on a donation from me.
I am sick of this ... I decided to keep this phone despite this issue, because of all the other goodness it brings to the table (especially battery life!! Wow!!) But this is still a horrible issue.
Click to expand...
Click to collapse
I have the same problem - my 2008 Tundra does not have A2DP for audio streaming, but does have BT for phone calls (and works great). On my previous Droid2, I could use the AUX jack for music and the BT for calls no problem. Now, with the S3, if I hook up AUX for music and BT for calls, then when a call comes in the phone keeps the audio out going to the AUX jack while my truck switches to BT for sound. Therefor, I can't hear the other person (but they can hear me) unless I unplug the audio jack.
From what I've found on the net, it seems it's something in the bluetooth settings/drivers in how Samsung has them implemented on the phone, which is not the same as how they are implemented in the Motos and HTCs. I was unaware that other carrier versions and/or certain other Samsung phones (S2, Nexus) did not have this problem.
For now, I've solved it by getting my hands on a car dock for the ATT Infuse 4G, which has the "dock" mode built into the USB connector with both power and audio output. I dock my S3 into this dock and changed the settings to output audio out the dock. Then I plug my AUX cable into the dock and it works like I expected it to from the start.
CIPuyleart said:
I have the same problem - my 2008 Tundra does not have A2DP for audio streaming, but does have BT for phone calls (and works great). On my previous Droid2, I could use the AUX jack for music and the BT for calls no problem. Now, with the S3, if I hook up AUX for music and BT for calls, then when a call comes in the phone keeps the audio out going to the AUX jack while my truck switches to BT for sound. Therefor, I can't hear the other person (but they can hear me) unless I unplug the audio jack.
From what I've found on the net, it seems it's something in the bluetooth settings/drivers in how Samsung has them implemented on the phone, which is not the same as how they are implemented in the Motos and HTCs. I was unaware that other carrier versions and/or certain other Samsung phones (S2, Nexus) did not have this problem.
For now, I've solved it by getting my hands on a car dock for the ATT Infuse 4G, which has the "dock" mode built into the USB connector with both power and audio output. I dock my S3 into this dock and changed the settings to output audio out the dock. Then I plug my AUX cable into the dock and it works like I expected it to from the start.
Click to expand...
Click to collapse
Does the S3 fit into the dock ok? Any stability problems? And you get proper 3.5 inch output for your car's input, plus your bluetooth call works? I have the same kind of deck in my Freestyle. Installed it myself. It does bluetooth for calls but not A2DP. Thanks for your responses so far! I am willing to buy a dock if it works like that. I would just appreciate any reassurance you could give me that it will work out ok ...
but that's a really nice idea that i didn't consider. I would really like to get this thing working and willing to apply any dev fix. what's interesting is that skype calls work fine, yet regular phone calls do not i'll give this doc a try.
Ok, I have the dock now, and wanted to update everyone on this. Audio quality is good, better than bluetooth, but an ever so slight downgrade from just plugging straight into the headphone with an audio cable, but it's certainly good enough.
The one thing that is annoying enough to prevent me from using it is that there is an audible click between each song. I haven't a clue how to get rid of this!! ARGHH!!! I haven't tested the dock with video or pandora output to see if the clicks persist, but as of right now, it's a bit annoying on a long trip. Otherwise, this would work really nicely, and is a pretty cheap fix for $18, not to mention getting a fully functional windshield/dash mount to use your phone as a GPS with.
Hoping my new ROM I installed might solve the audio issue. It has a custom kernel, and possibly improved car dock compatibility. We shall see...
Hello everyone!
I just upgraded to the SIII from my Droid 4 and am having this same issue. Does anyone have a fix? It seems silly to have to buy additional items to get it to work when it worked fine on other phones.
I like the stock ROM, but will flash if necessary to get this to work, as its very distracting while driving.
misterpat1975 said:
Hello everyone!
I just upgraded to the SIII from my Droid 4 and am having this same issue. Does anyone have a fix? It seems silly to have to buy additional items to get it to work when it worked fine on other phones.
I like the stock ROM, but will flash if necessary to get this to work, as its very distracting while driving.
Click to expand...
Click to collapse
SoundAbout Pro is an app that will override Samsung's stupidity when it comes to BT/AuxJack audio routing. Well worth the price of admission.