Hello everyone,
First some background...every phone I've had up until this year has worked perfectly fine with my Eclipse Navigation Head Unit (Eclipse AVN726E) via Bluetooth. Can make and receive calls no problem.
However, this year I purchased the Galaxy S3 and I had a huge issue. The phone can make a call and the person can receive it, however, I hear nothing on my end. I can't hear the ringing, or the person answering the phone. Needless to say, this makes the bluetooth impossible to use in the car. The Galaxy Nexus worked perfectly fine, but now the Nexus 4 is exhibiting the same issues the Galaxy S3 did.
Clearly, it's an issue with the newer Bluetooth versions (firmware maybe), so is there anyway to program the phone to use older (more compatible) firmware for the bluetooth stack? Again, the Galaxy Nexus worked perfectly, but the new phones this year seem to all have the same issue.
Hopefully someone else has had this issue with their built in navigation or bluetooth head units. Ugh, so frustrating.
TIA.
I have the same issue with my 06 BMW 330i, factory head unit, with a twist.
I have a normal conversation for 5 minutes or so, then their audio goes away. They can hear me fine, but I cannot hear them.
I'm interested in a solution to this as well, as my Nexus S worked perfectly before the Nexus 4.
Yeah, it's not looking good w/ the solution.
Totally sucks that newer phone hardware is incompatible with head units that were manufactured prior to like 2010...at least that's what it seems like right now. Eclipse, my head unit manufacturer is less than responsive as well, so I'm not getting anything from that end.
I was hoping there was a way to downgrade the bluetooth firmware on the phone or something to make it compatible, but I don't even know if that's possible.
Nothing you can do most likely
Sent from my Nexus 4 using Tapatalk 2
surferdude73 said:
I have the same issue with my 06 BMW 330i, factory head unit, with a twist.
I have a normal conversation for 5 minutes or so, then their audio goes away. They can hear me fine, but I cannot hear them.
I'm interested in a solution to this as well, as my Nexus S worked perfectly before the Nexus 4.
Click to expand...
Click to collapse
Have you gotten the Android 4.2.1 update yet? It looks like there's some Bluetooth stuff in there.
Acuity said:
Have you gotten the Android 4.2.1 update yet? It looks like there's some Bluetooth stuff in there.
Click to expand...
Click to collapse
Yeah, I updated before the audio dropping issue.
Strangely enough, I have since made 3 calls through BT at 10, 15 and 25 minutes respectively with no issues. I'll continue to monitor.
Well, I have found my issue (and it's unsolvable so far). My car simply isn't compatible with any phones with the Qualcomm S4 Pro processor. I tested a few other phones. Droid DNA (S4), Galaxy S3 (S4), Nexus 4 (S4)...none of them work.
HTC One X+, Galaxy Nexus...both work fine. X+ uses Tegra 3 and GNex uses OMAP. So yeah...clearly it's an issue with the S4 processor and chipset getting audio from my phone to my head unit.
I can make calls, receive calls, everything, but no audio is transferred at all...I can't even hear the phone ringing. It's a shame too...because all of the best phones use S4s now. Grrrr.
Want to add this thread. i have had the same exact issue OP mentioned with Sprint variant Galaxy S3 and stereo Eclipse AVN726e.
Was so disappointed that i Installed customer CM10 at the time which wasn't even stable yet but did not solve problem. Gave up the last couple of months.CM10.1.0 Release is on the phone now and today to my surprise after pairing my phone back up to my AVN726e I was able to hear the voice of other party on the phone when it accidentally connected when I was on the phone and started my vehicle.
So for OP and others alike see if CM10.1 is the answer for you as well now.
Related
In case anyone was curious, A2DP really doesnt sound any better between these builds. I'm starting to give up hope, maybe it's just my phone. The sound quality difference is night and day between my Vibrant and the myTouch 3G I have. I've tried on both my Kenwood head unit in my car and a pair of bluetooth headphones so I'm certain it's not the device I'm pairing with.
Ugh, just needed to vent, thanks.
pardon my ignorance, but i keep reading about A2DP and I finally want to find out what it is.
What is it?!?! thanks!!
A2DP is a bluetooth connection profile that supports high quality stereo audio. In the Vibrant's case however it is far from high quality. I was finally able to try another Vibrant today and it sounds just the same so now I know it's not just my phone. Some songs actually pass as decent bust most have a scratchy sound in the background and just lack overall depth. It really sounds like the bitrate is set too low on the Vibrant. Sabotage by the Bestie Boys for example has constant background noise/distortion that is not present when listening with wired headphones.
I've been digging around and swapping files around with the Korean Rom that has a supposed fix but I haven't made any progress.
One of the reasons I'd really like the Vibrant to sound better is because my Head Unit in my car supports A2DP. I have an app on my Vibrant called Tasker set to automatically fire up Pandora when a bluetooth connection is detected. So basically I can start my car and have my phone automatically start playing Pandora through my stereo, I can even advance songs with my dash controls. The audio quality can make it difficult to enjoy, My wife's myTouch3g on the other hand sounds superb on this same setup.
thanks for the response. i don't have a bluetooth set so that's probably why i haven't noticed this.
It really gets me down that my GPS, Compass, and A2DP are all broken on this phone. I'm gonna try and hold out for another month on a fix. If they released it in Korea hopefully they will release it here. Maybe I can talk Eugene or another dev to look into it
Audio quality is one of those subjective things and I really think a casual listener might not notice the problem but once you do you can't ignore it.
Strange, my BT sounds great streaming music through A2DP. I'm just on the stock Eclair build and streaming music through a Sony BT receiver, MW600. It's not an audiophile solution, but pushing music through some high-end IEMs sound perfectly fine for mobile listening. Maybe your hardware is bad?
I've tried two different Vibrant's on my car stereo and a pair of Bluetooth headphones and the results are the same. Again my wife's mytouch3g works perfect on both devices, maybe I should trade her phones . I've also tried an iPhone4 with excellent results.
Someone has actually opened a bug report with google on this very issue so I know I'm not alone in what I'm hearing:
http://code.google.com/p/android/issues/detail?id=9888
There was also an update for the Korean version of the Galaxy S that improved A2DP quality. This confirms that there is probably an issue that has not been addressed with our phones, since there have been no updates for Tmo customers.
http://phandroid.com/2010/07/14/korean-galaxy-s-receives-update-version-dg07-samsung-expects-to-sell-10-million-worldwide/
chadti99 said:
I've tried two different Vibrant's on my car stereo and a pair of Bluetooth headphones and the results are the same. Again my wife's mytouch3g works perfect on both devices, maybe I should trade her phones . I've also tried an iPhone4 with excellent results.
Someone has actually opened a bug report with google on this very issue so I know I'm not alone in what I'm hearing:
http://code.google.com/p/android/issues/detail?id=9888
There was also an update for the Korean version of the Galaxy S that improved A2DP quality. This confirms that there is probably an issue that has not been addressed with our phones, since there have been no updates for Tmo customers.
http://phandroid.com/2010/07/14/korean-galaxy-s-receives-update-version-dg07-samsung-expects-to-sell-10-million-worldwide/
Click to expand...
Click to collapse
Honestly, the quality of sound threw my A2DP is better than threw my headphone jack
jz9833 said:
Honestly, the quality of sound threw my A2DP is better than threw my headphone jack
Click to expand...
Click to collapse
Hi jz9833, what bluetooth device are you pairing your Vibrant with? Also what firmware, music app, file format are you using?
Have you considered going back to the stock ROM?
BT on mine is virtually identical to the headphone jack output. With Ety ER4p I can detect a little bit of digital hiss, but it's not really noticeable in a mobile environment.
Kubernetes said:
Have you considered going back to the stock ROM?
BT on mine is virtually identical to the headphone jack output. With Ety ER4p I can detect a little bit of digital hiss, but it's not really noticeable in a mobile environment.
Click to expand...
Click to collapse
Just today I tried a friends brand new out of the box Vibrant and I could still hear distortion/crackling at high frequencies. I then paired my headphones to my other friends iPhone4 just seconds after testing the new Vibrant and guess what, no distortion.
Man, I don't know what to say to you. My Vibrant sounds better out of BT than my iPod does out of its headphone jack. What BT headset are you using? For some strange reason they may just not get along. I've got a Sony MW600 and it's fantastic.
chadti99 said:
I've tried two different Vibrant's on my car stereo and a pair of Bluetooth headphones and the results are the same. Again my wife's mytouch3g works perfect on both devices, maybe I should trade her phones . I've also tried an iPhone4 with excellent results.
Someone has actually opened a bug report with google on this very issue so I know I'm not alone in what I'm hearing:
http://code.google.com/p/android/issues/detail?id=9888
There was also an update for the Korean version of the Galaxy S that improved A2DP quality. This confirms that there is probably an issue that has not been addressed with our phones, since there have been no updates for Tmo customers.
http://phandroid.com/2010/07/14/kor...samsung-expects-to-sell-10-million-worldwide/
Click to expand...
Click to collapse
There is no word on if this fixed it or not and according to your link this has nothing to do with Samsung.
Look, if you don't know that Samsung has acknowledged GPS by now, has already fixed the compass in the JI4 series you mentioned in this thread, you should just jump over to Android 2.2 and it's problems.. sounds like you won't be getting a fix either way according to your own links
chadti99 said:
Hi jz9833, what bluetooth device are you pairing your Vibrant with? Also what firmware, music app, file format are you using?
Click to expand...
Click to collapse
I am on stock vibrant, using the stock music/video app, playing mp3s, mp4s, avis, all going to my Sony MW600s.
heygrl said:
There is no word on if this fixed it or not and according to your link this has nothing to do with Samsung.
Look, if you don't know that Samsung has acknowledged GPS by now, has already fixed the compass in the JI4 series you mentioned in this thread, you should just jump over to Android 2.2 and it's problems.. sounds like you won't be getting a fix either way according to your own links
Click to expand...
Click to collapse
The first link confirms that other Android devices are having the same issue. Again my wife's myTouch3G doesn't suffer from the problem so I think it could be a simple bit rate setting that some manufacturers are overlooking.
The second link confirms that there is an A2DP problem on the Samsung Galaxy S and a fix exists.
chadti99 said:
The first link confirms that other Android devices are having the same issue. Again my wife's myTouch3G doesn't suffer from the problem so I think it could be a simple bit rate setting that some manufacturers are overlooking.
The second link confirms that there is an A2DP problem on the Samsung Galaxy S and a fix exists.
Click to expand...
Click to collapse
No it doesn't. You don't know if the "fix" is not a "fix". The myTouch 3G has Android 1.6 stock and if she hasn't changed it, it's still running Android 1.6.
heygrl said:
No it doesn't. You don't know if the "fix" is not a "fix". The myTouch 3G has Android 1.6 stock and if she hasn't changed it, it's still running Android 1.6.
Click to expand...
Click to collapse
I'm not sure what point you are trying to make, I still hear the distortion on a bone stock Vibrant. The reason I tried these beta builds was because I was hoping that Samsung would have incorporated the A2DP update. And yes the mytouch3g is running Android 1.6.
What does "You don't know if the "fix" is not a "fix"" mean? I think the fact that Samsung released an update for the Korean Galaxy S that improves A2DP quality pretty much sums it up, there was a problem and they fixed it.
This reminds me of the Oscar Rogers skit on SNL, "Sombeody needs to look at this mess and fix it!", lol.
chadti99 said:
I'm not sure what point you are trying to make, I still hear the distortion on a bone stock Vibrant. The reason I tried these beta builds was because I was hoping that Samsung would have incorporated the A2DP update. And yes the mytouch3g is running Android 1.6.
What does "You don't know if the "fix" is not a "fix"" mean? I think the fact that Samsung released an update for the Korean Galaxy S that improves A2DP quality pretty much sums it up, there was a problem and they fixed it.
This reminds me of the Oscar Rogers skit on SNL, "Sombeody needs to look at this mess and fix it!", lol.
Click to expand...
Click to collapse
Have you heard the purported fix on your phone? Have you seen what other people have said about it? No and no.
heygrl said:
Have you heard the purported fix on your phone? Have you seen what other people have said about it? No and no.
Click to expand...
Click to collapse
This is true, I have no idea what the A2DP fix does besides doing what Samsung claims it does, improve A2DP playback quality, which is exactly what I want. What is your point again?
Bluetooth audio still sounds poor on the new JI5 build. I've tried on three different Vibrants and three different bluetooth audio devices and have had others hear exactly what I hear. My wife's exact words, "Your phone sounds like a radio broadcast and my phone sounds like a CD."
I spoke to Samsung and they acknowledged there was a problem and said it was due to my devices not being Bluetooth 3.0 compatible. To my knowledge you can't even buy headphones that support 3.0 yet. I really wish they could fix this, I really like the phone overall.
I wanted to get some community feedback on the Bluetooth drivers for this phone.
I've noticed several times that my jawbone icon will "cut out" for 5 to 10 seconds periodically. Doesn't seem to happen at any consistent interval with no consistent trigger. I've tested the same headset with a nexus s, and a blackberry bold 9300. It works fine with the other 2 phones.
I've also seen my Nexus 4 exhibit the same behavior with my car stereo, a clarion CX 501. It acts like it's buffering a song, no audio, but it definitely isn't my network connection because it's doing it with local content and the song doesn't actually pick up where it left off, it clearly just keeps playing on the phone with no Bluetooth output.
It's probably worth noting that it doesn't actually lose the Bluetooth connection, it just stops transmitting out of nowhere. It still stays paired and connected.
Also mostly unrelated... It doesn't seem to hold a Wi-Fi connection very well when Bluetooth is active.
Anyone else seeing similar behavior?
Sent from my Nexus 4 using Tapatalk 2
snowmanwithahat said:
I wanted to get some community feedback on the Bluetooth drivers for this phone.
I've noticed several times that my jawbone icon will "cut out" for 5 to 10 seconds periodically. Doesn't seem to happen at any consistent interval with no consistent trigger. I've tested the same headset with a nexus s, and a blackberry bold 9300. It works fine with the other 2 phones.
I've also seen my Nexus 4 exhibit the same behavior with my car stereo, a clarion CX 501. It acts like it's buffering a song, no audio, but it definitely isn't my network connection because it's doing it with local content and the song doesn't actually pick up where it left off, it clearly just keeps playing on the phone with no Bluetooth output.
It's probably worth noting that it doesn't actually lose the Bluetooth connection, it just stops transmitting out of nowhere. It still stays paired and connected.
Also mostly unrelated... It doesn't seem to hold a Wi-Fi connection very well when Bluetooth is active.
Anyone else seeing similar behavior?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
works quite well for me on Stock. Are you using a custom ROM?
No issues here. CM 10.1 with Franco's kernel. Never had issues stock either. Using through Microsoft Sync in my car.
Sent from my Nexus 4
I'm 100% stock. Wondering if it's related to hardware at all. I figured it was software based on the symptoms but if no one else can reproduce it I might start to pursue an RMA
Sent from my Nexus 4 using Tapatalk 2
This device has better Bluetooth than stock gs3 and note 3 drivers. It always skips on Bluetooth while playing music with Samsung devices. While in this device, its flawless!
Sent from my Nexus 4 using xda premium
I currently use a LG-HBS700 bluetooth headphones with the N4 and so far, it's been working great, I've noticed its not so much the bluetooth thats the problem, but certain podcast apps that have trouble responding to the bluetooth controls on my headphones. So far, connection has been really good, I used to get occasional dropped connections with these earphones when connected to my iPhone, but no such issues with the Nexus 4.
expertzero1 said:
This device has better Bluetooth than stock gs3 and note 3 drivers. It always skips on Bluetooth while playing music with Samsung devices. While in this device, its flawless!
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
That's really interesting. Your experience was the opposite of mine. My nexus s was really great with Bluetooth.
I find it interesting that this was moved to the Q&A section... Just because I asked for impressions and people answered doesn't really mean it's a Q&A thread. Hopefully it'll still get enough traffic here to get accurate impressions.
Sent from my Nexus 4 using Tapatalk 2
Stock, but rooted and unlocked. BT at first was not stable. Had to pair and unpair all my devices for it to stick. Only had to do that once and from that point bt have been stable. Using Parrot Neo Minikit speakerphone, also my jabra pro 9470 at work, and using the HTC Stereo clip to stream wirelessly via aux port. No issue now.
kpjimmy said:
Stock, but rooted and unlocked. BT at first was not stable. Had to pair and unpair all my devices for it to stick. Only had to do that once and from that point bt have been stable. Using Parrot Neo Minikit speakerphone, also my jabra pro 9470 at work, and using the HTC Stereo clip to stream wirelessly via aux port. No issue now.
Click to expand...
Click to collapse
Thanks, I'll give it a shot after repairing
Sent from my Nexus 4 using Tapatalk 2
http://code.google.com/p/android/issues/detail?id=39633
http://code.google.com/p/android/issues/detail?id=39632
Catchpen said:
http://code.google.com/p/android/issues/detail?id=39633
http://code.google.com/p/android/issues/detail?id=39632
Click to expand...
Click to collapse
Thanks for digging those up! That's awesome. Hopefully there will be something in 4.2.2 that corrects this issue. You really brought some hope to me for this phone. Honestly bluetooth was the biggest complaint I had... I can live with the non SAMOLED screen and mediocre battery life... but the bluetooth has been driving me nuts!
code.google.com
^^
lol
Hi all,
Got my nexus 4 last week - very impressed with it (then again (as my username says) i came from Sony X10/Arc land so a big improvement was easy!)
Having problems using handsfree on the phone - i'm using my existing handsfree cabled (3 bands on connector).
If i plug in the headset before making a call and dial someone, the call instantly ends and goes to google now
If i make the call and then plug in the headset, the quality is genuinely terrible.
Anyone else have any experience with this? Call quality without handsfree is genuinely perfect...
Ta in advance.
I am also unable to use my sony headset with n4 and was searching for problem.
whenever I connect it opens googles now and sound quality is clear only if I keep the button pressed on my headset. Can you check if the same case?
I am finding someone with same situation. I want to know if this is problem with sony n4 match up?
Hi Ksavai,
Thanks for the response. I don't have the headset with me now but will check later...
I also have a sony headset (MH-500) so maybe should test with another. Would like to know that no one else has this problem though before i spend money on another brand/model!
ksavai said:
I am also unable to use my sony headset with n4 and was searching for problem.
whenever I connect it opens googles now and sound quality is clear only if I keep the button pressed on my headset. Can you check if the same case?
I am finding someone with same situation. I want to know if this is problem with sony n4 match up?
Click to expand...
Click to collapse
Checked my phone tonight.
With the sony mh-500 headset, i now get volume through the earphones ok but the audio level is very low; when i press the handsfree button the audio level increases dramatically.
Really is a crazy problem!
irl_x10_user said:
Hi Ksavai,
Thanks for the response. I don't have the headset with me now but will check later...
I also have a sony headset (MH-500) so maybe should test with another. Would like to know that no one else has this problem though before i spend money on another brand/model!
Click to expand...
Click to collapse
Samsung headsfree have same problem.
Do anyone knows which one works?
Sent from my Nexus 4 using Tapatalk 2
Hey,
Is this just a problem for some users? I would imagine that it would be a much more reported problem if it was the case with every phone. Or maybe everyone else is a blue-tooth-er
ksavai said:
Samsung headsfree have same problem.
Do anyone knows which one works?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
There are only us 2 makes me think that way too hopefully not
Sent from my Nexus 4 using Tapatalk 2
I am having the same problem with samsung handsfree. Actually I tried two sets. One had this issue and the other one just didnt work.
Is there a list of tested handsfree headsets?
After lots of searching I found out headset prior to 2011 won't work as it was different standard now it is updated standard. (I forgot the name but if you are interested I can look that up for you)
Newer galaxy s2 onwards or 2012 and later will work.
Newer one comes with grey or white circles on on pin while older ones have black.
Sent from my Nexus 4 using Tapatalk 2
ksavai said:
After lots of searching I found out headset prior to 2011 won't work as it was different standard now it is updated standard. (I forgot the name but if you are interested I can look that up for you)
Newer galaxy s2 onwards or 2012 and later will work.
Newer one comes with grey or white circles on on pin while older ones have black.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I 've read about a ctia standard, but none of the products in eshops says whether they are compliant or not. There are also headsets with green circles in the pin...
I guess I should look for sony and iPhone compatible headsets.
2012 Sony line up was compatible
Sent from my Nexus 4 using Tapatalk 2
I was having the same issue and I found this: https://code.google.com/p/android/issues/detail?id=41860 I've used three different headsets: Samsung, Skullcandy, iPod headphones (newer model and the low mic problem persists throughout all of them).
This is the first Android device I've ever had that has not exhibited Android's classic Bluetooth stuttering/cutout issue. I'm coming from a Note 4 that was on 5.0.1, and previously had S4, S3, HTC One M8, HTC One XL, S2, Atrix, Atrix 2, and this is a first. I've heard that maybe Google finally fixed the issue on 5.1.1, but either way, the annoying Bluetooth milliseconds cutout is gone.
If you say you didn't have the issue, you simply do not use Bluetooth or never listened at any length to render an observation. I commute 2 hours a day, at minimum, and podcasts and music would have this issue prior to the Note5. This was in multiple cars, multiple Bluetooth speakers. I'm happy to report that the issue is gone. You can bet that I will be investigating any software updates in the future to see if they reintroduce the classic bug, but I'm pleased.
Anyone else notice this has been fixed?
PS - the Note 4 community found a slight fix for this issue when II had that phone. If the screen remained on, the audio would not cut out. An FYI to Note 4 people.
cfn87 said:
This is the first Android device I've ever had that has not exhibited Android's classic Bluetooth stuttering/cutout issue. I'm coming from a Note 4 that was on 5.0.1, and previously had S4, S3, HTC One M8, HTC One XL, S2, Atrix, Atrix 2, and this is a first. I've heard that maybe Google finally fixed the issue on 5.1.1, but either way, the annoying Bluetooth milliseconds cutout is gone.
If you say you didn't have the issue, you simply do not use Bluetooth or never listened at any length to render an observation. I commute 2 hours a day, at minimum, and podcasts and music would have this issue prior to the Note5. This was in multiple cars, multiple Bluetooth speakers. I'm happy to report that the issue is gone. You can bet that I will be investigating any software updates in the future to see if they reintroduce the classic bug, but I'm pleased.
Anyone else notice this has been fixed?
PS - the Note 4 community found a slight fix for this issue when II had that phone. If the screen remained on, the audio would not cut out. An FYI to Note 4 people.
Click to expand...
Click to collapse
I had a nightmare with my note 4 and it's bluetooth, it was awful.
I got a Note 5 and bluetooth was absolutely awful, I had to return it and got a new one and all is good. Very good bluetooth
Having bluetooth issues with my Note 5 and an my Chevy Equinox. The phone works perfectly with all my other bluetooth devices though. I think its the car but my wife's iPhone works perfectly with the car. Who knows.
I have a thread in the Troubleshooting sub-forum looking for help with my BT.
See here.
Any ideas would be greatly appreciated!
Also - OP - what carrier are you with?
I have a nexus 6 and thinking about getting a note 5 but I have never had any issues with Bluetooth on my nexus
About every 20 minutes mine chooses to disconnect from my bluetooth speaker.
I haven't had a single issue with BT yet in my car or with my speaker at home. I use both daily.
Bluetooth on this phone (A2DP streaming specifically) is fantastic. I have had problems with horrible sounding overly compressed bluetooth audio streaming in my car (old head unit, no Apt-x or anything supported) since Android switched bluetooth engines after version 4.1. All the nexus devices (I've had a few) apparently only support SBC streaming, so this leads to the horrible sounding audio with some receivers, I presume. I just returned a Nexus 6 because of this very issue. I couldn't tolerate it in the car, music sounded like garbage. This was an issue with the Note 4 when I bought it last year as well. I don't know what Samsung did on the Note 5, but BT audio sounds pretty damn good again. I'm so glad, because nobody seems to care about this issue so I had almost lost hope. Props to Samsung for improving it.
Thats great news! I was to the point of wanting to beat my Note 2 with a hammer after every bike ride with my Bluetooth headphones! - Every time I would turn my head they would cut out. I'm looking forward to trying with my new Note 5 on my ride tomorrow.
I have read a few post on bad call quality with the 6P and for me it is a killer since I talk about 2500 min per month. My issue people still say I sound muffled...
- Have a rooted 6P using Pure Nexus
- Running EX kernel
- Performed the build.prop tweak many have posted about cancel noise cancellation
- Recently Google sent me a replacement phone but still same issues with it. Same complaint
- I am with Verizon
- Have great LTE connection full bars
- Use a BT 95% time Bose Bt2 and I bought a new Plantronic BT high-end headset and same issue
- v6.0.1_r10 and build MMB29T
I have come to conclusion that it is not the phone anymore think it is an issue with Google. Just looking see if others have the same and or found a real solution....although I don't think this is really one...??..??
best sound quality Ive ever had in a phone.
LTE means nothing when it comes to voice (unless it's a data call). So full bars doesnt mean anything...
Perhaps it's all that tinkering you did to the device. I would suggest not messing with the stock device and using it as they intended, then complain.
I noticed some issues with Bluetooth headsets between the three I use but the device alone no complaints
Sent from my Nexus 6P using Tapatalk