Database Users

Need help figuring out problem with Bluetooth Headset

I love having a bluetooth headset with my 8125, but I am frustrated that those who listen on the other end are having a hard time hearing me. At first, I thought that it was the Motorola H700 that I had. So I bought a Plantronics Voyager 510 after reading good reviews. Then I began having same problems with the 510. Volume apparently isn't the problem. Those who hear me state that the words become garbled at times and I am understood only 75% of the time. It's not related to my relative position. I have tried to unpair and pair the devices again. I'm wondering if it is the phone. I'm wondering if the drivers for the device have become corrupted in someway and need to be reloaded. However, I really don't want to hard reset my phone given the amount of time that would take. Anyone have any thoughts to the problem and a potential fix? Thanks.

i too have the same issue with my h700 on my tmo mda. i always thought it was my h700 but i tried it on my girlfriends phone and it was clear. i could hear the music in the background pretty easily. i agree that the problem is with the phone but to what would cause it to do this i have no clue.

I've had the same problem as well.
I believe it has to do with the MDA's bluetooth version. Does anybody know if there is a new version of bluetooth 2.0. I think something along that line would solve the prolems.

If it is a matter of drivers, then I would suspect that more than just a few of us would be complaining about this. I'm wondering if I did something to corrupt the current bluetooth drivers. Is there a way to re-establish the most up to date drivers without a hard reset? Thanks.

I listened to myself to see what others were hearing from my phone. I noticed that with faster speech, the information became more garbled. When I slowed down the speech, the information was less garbled. Which would be responsible for the problem? The headset or the phone? Has anyone tried the Voyager on another phone to experience if the same problem occurred? I don't have another bluetooth phone to try this on. Can anyone else try speaking at different speeds to see if this result can be replicated? Thanks.

Loosing all sound?

Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S

sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have the exact same issue. Very strange and rare. So the occasional reboot fixes it but annoying at times.

sfox said:
Anyone had this yet? Basically after flashing EVERY version of Damages 2.1 roms and Flipz 2.0d, I seem to have this odd issue where I loose all sound input and output. I noticed first when I was using Flipz, but a wipe and flash of DC 2.05 did the same thing. Weirdest part is, that it's fine for a while after a reboot, then suddenly happens and won't work until another reboot. My only thought is for some sort of software conflict or something, but right now my Hero is basically unusable as a phone since noone can hear me and I can't hear them.
Thoughts? Lil Help?
S
Click to expand...
Click to collapse
I have come across the same today on the 2.05 revision. It started this afternoon, since I have had to reboot 5 times. The latest was only about an hour or so apart. When I make calls, I do not hear any sound, no ring tone, not the other person. Also adjusting the ring volume with the volume keys does not make any sounds. Even on my bluetooth headset I do not get any sound. No rings on incoming calls, no speaker phone ... absolutely nothing. This has become a huge issue an I'm going back to my 1.5 image at this point.

Actually, reading through threads about both ROMS, I'd say there are quite a few people starting to encounter this problem...has anyone with this issue gone back to 1.5 to see if it goes away then?
S

just a note, the people on the other end when making a call can't hear anything either but the call does go through. i had to use the g/f BB to call and my buddy thought it was his phone. I'm so mad because I thought this was a done deal but looks like I gotta go back to 1.5

+1 same issue on Fresh 2.0d
When it happened it affected incoming and outgoing calls, earpiece, speakerphone, microphone -- the works. Person on other end could not hear anything either. Fixed with reboot.

me and my coworker both have this issue with our heroes, he couldn't stand it and went back to fresh 1.1 and it went away
I still get the issue once a day, full reboot solves the issue.
I cant seem to pinpoint when it happens, it just happens.
it started with the first fresh 2.0 and then continued with every 2.1 i have tried
i couldn't find a post in this forum relating to a fix for this, unless someone can prove me me wrong and i hope someone does

+1 same issue on Fresh 2.0d and DCv1
Same as others, a reboot will fix it but by that point you just missed a call.
Or if the sound goes out you might miss a few calls from not being able to hear the phone ring.

yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap

Avalaunchmods said:
yes it is a very large issue. im about to run some tests and i will find out what causes it. hopefully i will have a solution tonight for everyone but its going to be hard.
also the issue effects all sound on the phone and pegs the cpu pretty bad. you cant adjust sound lvls or hear anything from either speaker at all.
im afraid the problem will lie in the boot.img with a driver for sound. because dc2.0r2 did have this issue and also has an incomplete boot.img we may have to deal with no trackball. anyways ill report back asap
Click to expand...
Click to collapse
Thanks. You're speaking greek to me as far as the boot.img and all that but if you have an idea of what's going on I'm all ears on fixing it. If there is any sort of info we can provide just let us know.

Im here to help as well, If you need any testers I am willing to do what ever is needed! Anything to fix this problem!

Related?
10chars
http://forum.xda-developers.com/showthread.php?t=657244
Click to expand...
Click to collapse

DroidDhakan said:
Related?
10chars
Click to expand...
Click to collapse
Of course it is,its the fix(hopefully) for it

Answering a Call

Just a quick question for you guys. When I receive a phone call (full signal strength) and slide the slider accross to answer the phone there is a long pause of silence before the call actually connects. Has anyone else run into this situation?
Nexus One running stock Froyo (At&t)

yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.

Old MuckenMire said:
yes I have this issue: I answer and cannot get an answer on the other end but I can hear them saying "hello". After a few seconds we connect and they say they never heard me say anything even though I was saying hello back.
I have two Nexus Ones: one answers calls perfectly and has great sound quality, while the other has this issue you describe, along with low call volume.
I think in my case it may be a hardware issue and I may need to send it in to be looked at. Both running on ATT although the good device is the tmobile version and the problem device is ATT 3G version.
Click to expand...
Click to collapse
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.

Never encountered that issue. The other side hears me immediately as I answer. I guess this is not "across all N1s", unless someone would think my N1 is special in some way (which it isn't, and so are all the other 7 N1s of my friends at work which also happen not to have this problem - and the call quality is great on at least 3 that I checked personally).

Instantly connects on my phone as well, so it's not on all devices at least. I have one of the first batches of T-Mobile N1's btw.

What carrier are you on?

this happens to me too.its so annoying. im on att

Can't find the thread but it was pretty long.

nexusdue said:
You think it is a hardware issue? I thought that it was like that across all N1s?
There was a thread here 1-2 weeks ago about the issue and pretty much EVERYBODY had this problem.
I can't find the thread anymore but it was about the delay between answering a call and the mic becoming active ... which takes 2-5 seconds.
I just noticed the other day that the delay seems to be less if I immediately put the call on speaker.
Click to expand...
Click to collapse
I'm not so sure anymore. I decided since my only choice was to send it in for repair, I might as well one click root and install CM6 and see what happens. So far, I have not had the issue. It's only been three days but that's the longest this device has ever gone without having the "no connect" issue. Also, my low call volume and speaker phone volume issues are now resolved. I now find myself turning the volume down rather than up. I'll update this thread with final verdict on whether this fixes my issue.

This sounds like an att problem not a nrsux one problem

I notice this problem as well. If I wait until the call timer appears on screen before I start to talk the other party doesn't seem to notice.

I'm on T MO and never had this issue. Try the one click root and flash a different ROM. If it doesn't work send it to HTC. I recently sent mine back on a Monday and it was back that Friday.
Sent from my Nexus One

Well my issue has been resolved by switching to CM6. It's been a week now and the issue has not occurred even one time. This was an issue that used to happen to me EVERY DAY, so I am very happy that in my case it turned out to be a software issue.
When I was running 2.1 I hoped 2.2 would fix it and when it didn't I thought for sure it must be hardware. It's so nice to KNOW I can answer the phone if it rings now. Sometimes I would get an important call and I was afraid to answer the damn phone!
Thank you Mr. Cyanogen, whoever you are.

I get this issue once in a while. I think its a software issue. Over time something gets hung up somewhere.

I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?

khaytsus said:
I had a thread like this as well..
http://forum.xda-developers.com/showthread.php?t=691399
For me it still happens randomly, stock 2.1 rom, stock 2.2 rom, Enom's ROM, etc...
Although I have a theory that I haven't tried to prove/disprove yet.. It seems like several times when this has happened I was holding my finger over the second mic on the back, which is naturually where my finger seems to lay when I hold the phone. Anyone else considered this? I'm thinking maybe it's throwing off the microphone trying to do noise cancellation?
Click to expand...
Click to collapse
Definitely not the finger covering the mic. Just tried it with/without and same result.
There was another thread that was at least 3-4 pages of people complaining about it.

Sounds more like a network issue than a hardware issue, IMO

This issue has come up recently for me and it's really annoying. I'm not sure what triggered this problem...
Is anyone else experiencing this issue? Any ideas on how to resolve?
I've got the Rogers/AT&T N1.

6.0.1 Bluetooth issue fix?

Hey guys,
this new android related issue where streaming music via bluetooth is a pain in the ass, as there are only two volume levels (absolutely loud and the opposite) is really annoying.
Is there any statement from google, if and when it'll be fixed or is there even a fix already?
I cannot imagine how sth like this got into a final release...

Stream every single day on a 45 minute commute via GPM and Spotify (Bluetooth to car) and never encountered this... Seems odd. I'll keep an eye out but haven't seen it yet!
Sent from my Nexus 6P using Tapatalk

Delboyd12 said:
Stream every single day on a 45 minute commute via GPM and Spotify (Bluetooth to car) and never encountered this... Seems odd. I'll keep an eye out but haven't seen it yet!
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
is a common issue with 6.0.1 and several bluetooth devices (i have a creative roar box), just search the forums here.

I'm usually ok with blue tooth streaming to my car as well as to my Polaris speaker. No issue with my Huawei watch either that I'm aware of.
(Sent via my mobile device)

I'm having a ton of bluetooth issues with this phone sad as I *love* this phone..
But I listen to podcasts daily (while biking/running./in the car) and it keeps cutting out on me.. like 2-3 times/minute.. that's using the bluetooth in-car, as well as two different bluetooth headsets
BTW phone calls are fine - this is just A2DP bluetooth stereo..
on 6.0.1 stock (rooted)
-mark
Edit - seems worse when I'm near my wifi router; although still having issues w/ wifi off..

I had some issues with bluetooth audio cutting out after the phone had been sitting for a while. I added the media apps (music, youtube) to the not optimized list under battery settings and now it works fine.

stream every day from google music app to my vw golfs system via bluetooth and never cut out once or had any issues. Im stock non rooted 6.0.1

It's a wide issue have a look here https://code.google.com/p/android/i...ry Stars&groupby=&sort=&id=189188#makechanges for the people who are having the issue make a comment and Hit the star so Google understands what's going on as they have it as a low priority

Heinous said:
I had some issues with bluetooth audio cutting out after the phone had been sitting for a while. I added the media apps (music, youtube) to the not optimized list under battery settings and now it works fine.
Click to expand...
Click to collapse
I'm going to try your suggestion here... This is infuriating as I dig the phone so far (mostly).

Grumpy Bob said:
I'm going to try your suggestion here... This is infuriating as I dig the phone so far (mostly).
Click to expand...
Click to collapse
Good luck.

Heinous said:
Good luck.
Click to expand...
Click to collapse
No joy. I did your suggestion in conjunction with a few others and I'm still getting audio hits. Did the following to no avail:
- Uninstalled an app called "gasbuddy" which has been reportedly giving users issues with BT
- Messed with a few settings in Developer Options
- Cleared Cache
Did those listed above plus your suggestion and it still doesn't work properly. The only thing that is (albeit moderately) reliable is to completely unpair, forget device, repair, and update permissions. How frustrating every time I get in the car. Additionally, I've been getting SERIOUS BT phone problems. The caller on the line cannot hear me nearly at all. It's not my car's BT unit either, as I've troubleshooted with other phones. I have to switch to handset speakerphone. I feel like I'm in the 90s again. I'm massively bummed out since I spend a lengthy portion of time in my morning/evening commutes. BT is the one thing I can't do without. What a drag.

Grumpy Bob said:
No joy.
Click to expand...
Click to collapse
Does it work with other Bluetooth devices, or do you have other phones to test in your car? Might be an issue with the car or even something google/hauwei can fix under warranty.

Heinous said:
Does it work with other Bluetooth devices, or do you have other phones to test in your car? Might be an issue with the car or even something google/hauwei can fix under warranty.
Click to expand...
Click to collapse
Thanks for the reply but yeah that's what I meant when I said - "as I've troubleshooted with other phones."...
As to your other point, this is actually my second 6p. I RMA'd one a few weeks back for the same issue - I thought the same thing.
So frustrating. Like nailing jell-o to the wall.

I found what was causing my Bluetooth issues with my Chevy Malibu. The app weather bug was messing with my phone Bluetooth and battery drain. After I deleted the app my Bluetooth works fine and my phone now sleeps with doze correctly...
Sent from my Nexus 6P using XDA Free mobile app

cables2590 said:
I found what was causing my Bluetooth issues with my Chevy Malibu. The app weather bug was messing with my phone Bluetooth and battery drain. After I deleted the app my Bluetooth works fine and my phone now sleeps with doze correctly...
Sent from my Nexus 6P using XDA Free mobile app
Click to expand...
Click to collapse
I was having the same issue, both with BT headphones, BT speaker, and my Android Wear watch. I tried factory resets on both phone and watch, and forgetting all BT connections and re-pairing to no avail. I Factory reset my phone again, and didn't add my Amber Weather Widget back to my home screen and all was well. As soon as I added it...Bt went to hell again. Deleted the app and now I'm having no problems. Not sure why a weather app would cause BT to act up, but it sure did in my case.

Uuuh. This is ultra frustrating. Using my smartphone for business and private stuff, so it has to re reliable. Hearing music is a pain in the ass, really. Doesn´t matter if I connect it to my Bose Soundlink Mini, my Philips NFC/Bluetooth Dongle...interruptions all over the place.
BTW: I don´t have any weather widget installed, so I have absolutely no clue what to try next. Delete all paired devices is a no go, really.
PS: And it´s not only interruptions - music kind of gains speed after those interruptions.

Grumpy Bob said:
No joy. I did your suggestion in conjunction with a few others and I'm still getting audio hits. Did the following to no avail:
- Uninstalled an app called "gasbuddy" which has been reportedly giving users issues with BT
- Messed with a few settings in Developer Options
- Cleared Cache
Did those listed above plus your suggestion and it still doesn't work properly. The only thing that is (albeit moderately) reliable is to completely unpair, forget device, repair, and update permissions. How frustrating every time I get in the car. Additionally, I've been getting SERIOUS BT phone problems. The caller on the line cannot hear me nearly at all. It's not my car's BT unit either, as I've troubleshooted with other phones. I have to switch to handset speakerphone. I feel like I'm in the 90s again. I'm massively bummed out since I spend a lengthy portion of time in my morning/evening commutes. BT is the one thing I can't do without. What a drag.
Click to expand...
Click to collapse
Yep,I have the same exact issue with phone calls, the caller cannot hear me at all and I switch to speaker. This is my second phone and they both did the same thing, connects, fine for a few seconds, then gets muted or something and have to switch to speaker. My notes never did this and it's super making me mad! I'm going to call google and try to return this phone. It's BT totally broken.

I might be giving up on the phone very soon. I'm bummed. I really dig it, but BT is such a HUGE part of my life at this point that it's impossible for me to own a phone that falters in that respect. Ugh. How disappointing.
I even signed up for the new Android N beta testing, hoping that would remedy the situation. Nope.

Can't be heard after some time.

This is very frustrating.
I use my phone for calls between 3-5 hours a day. I've been having this issue where I'll be on a call and after some time (ranges between 2-10 minutes) I can continue to hear people but they can't hear me. I use the Samsung headphones with a built in mic to talk. I'll notice that they can't hear me, I'll unplug the headphones and they still can't hear me. I hit speaker phone and still can't be heard. I end up hanging up and calling back. This happens about 30% of the calls I'm on. I also bought other Samsung headphones and the problem persists. It's also not always with my headset. I've had this muting issue happen while talking directly on the phone.
Here is the kicker. I'm on my 3rd s6 edge+ and I've had the problem with all 3!! My first phone the microphone by the speaker stopped working. My second one started having the same issue with the mic. But all three had the same exacting muting issue.
Anyone else in the same boat? Any suggestions on fixing this?
Thanks

mikeysweet said:
This is very frustrating.
I use my phone for calls between 3-5 hours a day. I've been having this issue where I'll be on a call and after some time (ranges between 2-10 minutes) I can continue to hear people but they can't hear me. I use the Samsung headphones with a built in mic to talk. I'll notice that they can't hear me, I'll unplug the headphones and they still can't hear me. I hit speaker phone and still can't be heard. I end up hanging up and calling back. This happens about 30% of the calls I'm on. I also bought other Samsung headphones and the problem persists. It's also not always with my headset. I've had this muting issue happen while talking directly on the phone.
Here is the kicker. I'm on my 3rd s6 edge+ and I've had the problem with all 3!! My first phone the microphone by the speaker stopped working. My second one started having the same issue with the mic. But all three had the same exacting muting issue.
Anyone else in the same boat? Any suggestions on fixing this?
Thanks
Click to expand...
Click to collapse
Doh. I dont know which firmware/rom/kernel you're running but maybe you should wipe cache/dalvik or clean re-flash.. If already rooted, give a try a custom kernel. Hope you solve it. Thanks.

I have the exact same issue, except my call quality is poor and calls drop a lot as well. Im on my 3rd phone as well. All the issues have followed me on the phone. T mobile told me that I would have to wait for the marshmallow update since its a known issue with the phone and it should correct it. I told them it wasnt a good answer so they are sending me a new sim card to try out and see if that helps. Personally I hope it doesnt so I can get a new device

Konsstantine34 said:
Doh. I dont know which firmware/rom/kernel you're running but maybe you should wipe cache/dalvik or clean re-flash.. If already rooted, give a try a custom kernel. Hope you solve it. Thanks.
Click to expand...
Click to collapse
Oops!
I'm running completely stock, no root/rom/kernel changes at all:
Build# LMY47X.G928AUCU2AOJ1
Android: 5.1.1
Kernel Version: 3.10.61-5921265

bb4ninja said:
I have the exact same issue, except my call quality is poor and calls drop a lot as well. Im on my 3rd phone as well. All the issues have followed me on the phone. T mobile told me that I would have to wait for the marshmallow update since its a known issue with the phone and it should correct it. I told them it wasnt a good answer so they are sending me a new sim card to try out and see if that helps. Personally I hope it doesnt so I can get a new device
Click to expand...
Click to collapse
Ugh. It's going to take forever for Marshmallow to come out. First Samsung needs to rip it apart, then AT&T before it gets to me.
Let me know how the SIM change works for you. That's one thing I've yet to try.

mikeysweet said:
Oops!
I'm running completely stock, no root/rom/kernel changes at all:
Build# LMY47X.G928AUCU2AOJ1
Android: 5.1.1
Kernel Version: 3.10.61-5921265
Click to expand...
Click to collapse
Umm. I see thats AT&T, isnt it? If so, you have got locked bootloader etc, I dont have proper info about it sorry. I prefer you to try something like wipe cache/dalvik etc but it may bricks your phone. So you better ask that in AT&T Forum Good luck.
Edit: I saw your post after posted mine lol. I've simfree g928C btw.