I have a jabra bt530 and i cant for the life of me figure out whats going on with it. I previously had the samsung moment and actually i went thru 3 of those. Everyone complained about me breaking up with my bluetooth so ofcourse im thinking my bluetooth is crap. I paired it with my work nextel phone, everyone said i was very clear and no problems. Then the evo came out. Same problems as before. I dont know what to think. Im clueless as to the problem. Anyone else have problems with their android phones and bluetooths?
Related
Ever since the Sprint 2.2 update, my audio via Bluetooth cuts out. The person on the other end can still hear me, but I cannot hear them.
It comes and goes. I've tried un-pairing and re-pairing, but it doesn't seem to have helped. I'm using the original Jawbone ear piece.
I haven't seen anyone else complain about this.
I've had this issues with other ROMs. Then I told Cyanogen and he patched it imeediately, and the fix went into effect in the nightly, then RC1.
Seriously though, sounds like either an issue with your headset, your particular EVO, or you can just thank HTC for their proprietary PoS BT stack. Sorry mate. :/
Well, if no one else has the same issue, then it's just my EVO.
I can't even pair my jawbone since I flashed a 2.2 ROM. I did notice while talking to a fellow Evo user that their headset sounded like crap with the OTA. I don't think you are alone.
ive never had an issue bluetooth pairing my g2 to anything up until today. My dad just bought a handsfree bluetooth kit for his car from walmart i believe and asked me to hook his g2 (stock, rooted) to the bluetooth unit and his g2 didnt even see it. I then tried my g2 (cyanogenmod 7 latest nightly) and it didnt see it either. Just out of sheer curiousity i tried his old motorola razor and bam, found it and instantly hooked to it. Im kinda bummed our "smart phones" wouldnt but the one dumb or "challenged" phone would. anybody know why? or how to fix, or even an app to help get around this issue? thanks for any help.
sent from something they thought nasa built
veritasaequita said:
ive never had an issue bluetooth pairing my g2 to anything up until today. My dad just bought a handsfree bluetooth kit for his car from walmart i believe and asked me to hook his g2 (stock, rooted) to the bluetooth unit and his g2 didnt even see it. I then tried my g2 (cyanogenmod 7 latest nightly) and it didnt see it either. Just out of sheer curiousity i tried his old motorola razor and bam, found it and instantly hooked to it. Im kinda bummed our "smart phones" wouldnt but the one dumb or "challenged" phone would. anybody know why? or how to fix, or even an app to help get around this issue? thanks for any help.
sent from something they thought nasa built
Click to expand...
Click to collapse
Did you set your phone as discoverable in the bluetooth settings?
Sent from my HTC Vision using XDA App
yes, it was set as discoverable
sent from something they thought nasa built
I can't seem to find any mention of this anywhere else, and I have looked. My wife and I both have E4GT and are both experiencing this issue everyday and we both have different Bluetooth headsets.
We will walk away from our phones far enough that our headsets disconnect. Once we close enough, sometimes they connect back up, but most of the time, we have to shut off the Bluetooth radio in the phone and turn it back on before it will connect again. Once in a while we are right next to the phone and it will disconnect for no reason at all.
My wife has a cheaper Rocketfish headset and I have a more expensive Jawbone.
Anyone else having this problem?
both our phones are rooted and we're both running Caulkins rom. She is running an older 2.8.0 and I am sporting 2.8.1. I have asked this in his rom thread, but twice have gotten no responses. I can't find anywhere if there is a Bluetooth radio driver update like with modems.
Did this happen while you were on stock?
Sent from my SPH-D710 using XDA App
davidc23 said:
Did this happen while you were on stock?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
HAHA, I knew someone would ask that!
To be honest with you, we got these phones and two hours later, I had them rooted and flashed, so I couldn't say. I've been rooting and flashing roms since we had our first Droid 1 phones and I just can't seem to leave well enough alone.
I have the same issue with a Jawbone Era.
Has happened on stock roms as well as Caulk's and UnNamed.
What happens with my Era is that it will just stop working. Phone will show that it is still paired, but I get no audio to the device. The only way to fix it is to turn off the Era headset, and turn off bluetooth on the phone. Then turn BT back on, followed by the headset.
It's a real PITA. I got this headset after reading several reviews on the webs saying that it was a great unit.
It is, when it works. Unfortunately this happens at least once a day.
I am looking for a solution as well, and I was even thinking of getting a different headset but after reading that it's happening with completely different headsets makes me think that won't solve anything.
I'll try to report back if I find anything.
One other note, the Jawbone Companion app also is very flaky. Most of the time it will not detect the Era headset even when the phone is connected and it's working fine. This too happens on both stock and custom roms.
Bluetooth
Make sure your phone is set to always discoverable and when you get back in range of your phone try hitting the call/end button on your bluetooth, this should help it re-connect without having to restart the program in your phone.
I have been running into this exact situation with my brand new Plantronics Voyager Pro HD, and I was about to return it to the store today, but then I saw this posting, so maybe it is NOT the BT headset afterall. Next time it happens I will give those instructions a shot...
Does making your phone "always discoverable" have any bearing on the battery life or anything? Thanks!
jb8301 said:
I have been running into this exact situation with my brand new Plantronics Voyager Pro HD, and I was about to return it to the store today, but then I saw this posting, so maybe it is NOT the BT headset afterall. Next time it happens I will give those instructions a shot...
Does making your phone "always discoverable" have any bearing on the battery life or anything? Thanks!
Click to expand...
Click to collapse
I'm seeing a pattern here. It appears from what I'm reading, that it does not matter what Bluetooth headset you have or what rom you're running, it's happening to a few people. Makes me think it's the phone or Gingerbread itself that's the issue. Maybe when ICS is ready to be a daily driver, it'll change.
In one respect it makes me feel better as my wife and I don't have to replace our headsets!!
I am not comfortable in leaving our phone "discoverable" as this opens our phones to possible unwanted access from unscrupulous people.
hello world,
its been a while since i've been on xda for forgive my lack of knowledge and bare with me:fingers-crossed:.
i've had a G2 since its release, rooted it to the 2.6.35.10-virtuous [email protected] #15(adroid version 2.3.3) and never looked back. This thing has been running flawlessly despite numerous drops from my hands(they dont build 'em like this anymore).
Last month I updated my radio to 26.13.04.19_M build and have been enjoying the batterylife.
Alas, just yesterday i've noticed that no one can hear me on the other end of a call, although i can hear them just fine. After tinkering with it i realized it was indeed my microphone and my ribbon was indeed torn. i replaced it myself promptly and still didnt work, took it apart again, and put it back together incase i forgot something. Everything else works fine so u can imagine my dismay(i can do everything but make phone calls )
The microphone still has issues and can barely hear me when im screaming at it, but even then ppl on the other end hear a faint voice.
so i ask u fellow "Vision" owners, what can i do to fix this?
(im also aware that 3 other members have experienced a similar dilema, 2 of which are recent, but no remedy has been brought about)
http://forum.xda-developers.com/showthread.php?t=1763276
http://forum.xda-developers.com/showthread.php?t=1530502
http://forum.xda-developers.com/showthread.php?t=1190380
-for one who actually had the patience to read through the whole thing, i award u an invisible cookie
I got same issue ,too
Dose anybody know how to fix this issue
no one has any ideas?
Has anyone else experienced this, ive reset, formatted, factory reflashed and im not the only one having this problem.
I wish i was smart enough to see why wifi works like crap unless i turn bluetooth on, 5ghz or 2.4ghz channel doesnt matter.
Google engineers obviously cant fix this, its been going on for over a year, have any of you had a chance to log or see what is going on?
Do you guys think this is a hardware defect that google is keeping hush hush, im guessing the bluetooth and wifi are on the same piece of hardware.
I shall not be buying a Pixel 2 as people are already experiencing this on their new ones are well.