Related
Yesterdaty I updated to WM6.5 and now try to get everything working again. Somehow my TP2 won't pair with my bluetooth carkit anymore. With WM6.1 this was no problem. The phone still pairs perfectly with my computer (also bluetooth connection) so I think the bluetooth connection is ok.
When parining to my carkit it finds the device, then I have to enter a password on the TP2, and after that it just sais "pairing connection failed", and it will not work. I am sure the password is not changed since yesterday. I tried it several times. I do not know what to do anymore. Could this be a setting somewhere? I get the feeling my password is not send properly but have no idea.
Meanwhile I tried pairing my carkit with another phone and no problems there. So my conclusion is: something has changed with bluetooth, updating to WM6.5 which makes it now impossible to pair my TP2 with my carkit.
Is there maybe a programm for the TP2 which give me more controll over bluetooth (like maybe go to an older standard)?
I have exactly the same problem as you
good to hear I am not the only one. Hope someone will come up with a solution for this.
I did nor observed any issues when pairing my TP2 after reflashing to WM6.5
There is another issue however - I can not hear any voice until it is charging.
Unplugging of the charger fixes this issue immediately. Horrible...
Seems, HTC guys are saving money on testing by using us as Beta Customers.
Would a custom ROM be a solution for us?
I updated to the "energy 6.5.1 rom" and guess what..............
The same problem. The rom is very nice, but my TP2 still won't pair with my BT carkit which is very big problem for me.
Is there maybe a way to downgrade just the BT part of a rom to WM6.1. I read on different forums there is something that is called a BT stack. Could this be the problem?
I have a ton of problems with bluetooth pairing now. However, I don't know whether it's the fault of 6.5 or the Tilt 2. Here is what I am experiencing...
- On car deck or headphones, the skip buttons don't do anything
- on car deck or headphones, I have to disconnect Stereo Audio and then reconnect to actually get sound. It NEVER works when it auto connects.
- Music will do a brief skip when you shut the screen off
- Stupid message about volume control every time it connects (resolved by switching to custom rom)
- SMS or any kind of alert tone now turns music way down so that the tone is the only thing you hear. Which is super awesome when I'm driving my drunk friends around and they are singing along to a song when suddenly it mutes so everyone can hear my incoming text message.
Not a single one of these issues existed when I had my Fuze.
Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM
orb3000 said:
Same here
My bt headset (sony hbh ds970) and simply does not find the pairing...
I asume is a problem related to energy´s ROM
Click to expand...
Click to collapse
No I do not think so, because I used the official WM6.5 with the same problem. Does someone know a way around this issue. I strongly believe that if only I could pair I have some options to work with it (in 6.1 it worked like a charm). If I only could pair without having to send the passkey it would be great step forward. I presume with sending the passkey, the bluetooth of the TP2 sends out other "rubbish" that confuses my carkit.
My problem is solved and guess what, it had nothing to do with my TP2. The problem was my carkit. It has a maximum number of bluetooth devices (5) it can pair to and the last one (the WM6.1 version of my phone) had been reached. So a hard reset on the bluetooth carkit and the problem was solved.
Well, at least I now know how to flash a rom to my phone and I think I learned more about the phone reading through all the forums. Thanks all for thinking with me on this problem!
Does anyone else still have this problem?? I have removed all the devices from my car and continue to have the same pairing error just after entering the passcode. Stock Spint ROM worked great, but multiple 6.5 upgrades don"t pair..............suggestions/ideas??????
bluetooth settings, advanced, enable beam data exchange,check the box
Interesting.....I actually found a fix. Instead of pairing the phone with the car, I paired the car with the phone. I didn't even know that this was possible, but it did the trick!
Hi,
I have a bluetooth phone in my car, when I first connected the HTC Desire HD up, it had no problems, it paired and everything looked fine... around 10 minutes later, I noticed the bluetooth had simply disconnected from the car but was still running on the phone. I tried to reconnect it up to the car but it wouldn't, I then turned it off, and turned it back on.. it struggled to come back on, but after a few attempts it did come on and the car connected again...
About 5 minutes later the same thing happened again. At this point my phone started to really slow down, I looked in watchtower and the bluetooth was at the top of the list, soon as I turned off bluetooth the phone was responding fine again.
I have since tried connecting to the car multiple more times and have contacted HTC about it, but it seems to disconnect at random times.
Has anyone else experienced similar problems? I heard of similar problems with the original desire so wondering whether it could be something similar.
Kev
Hi Kev,
I am having similar problems with my Desire HD and Audi in car bluetooth system. I posted on another forum and found others were finding the same...
I pair my phone and within couple of minutes the phone has disconnected and won't re-connect.
Not found any definitive answer as yet, but seems BT in this phone isn't so good. Also read a post saying HTC were aware of this but an update wouldn't be available for sometime.
Hopefully someone else can shed some light!
Ben
I also noticed this the last few days with my Bury CC9056 carkit. I have my DHD since October 18th, and up till last friday it connected fine. Since then it connects to the carkit, but within a few seconds the connection is lost...
Sent from my Desire HD using XDA App
Me too. My connection to my Jabra car kit is stable once connected... but trying to get it connected in the first place is a total headache.
Never had this problem with my Desire, so why HTC should change the Bluetooth function in the HD is a mystery.
Sent from my Desire HD using XDA App
tbh i'm glad its not just me thats experiencing problems meaning it could be a software problem rather than something with my handset in particular.
I have been in touch with HTC about this, and I have just sent them the link to this thread so they can see i'm not the only one with this issue, so if anyone else has this issue it may be good to try and keep it all in here.
quentin_rayner said:
Hi Kev,
I am having similar problems with my Desire HD and Audi in car bluetooth system. I posted on another forum and found others were finding the same...
I pair my phone and within couple of minutes the phone has disconnected and won't re-connect.
Not found any definitive answer as yet, but seems BT in this phone isn't so good. Also read a post saying HTC were aware of this but an update wouldn't be available for sometime.
Hopefully someone else can shed some light!
Ben
Click to expand...
Click to collapse
Mines also the audi in car system - do you find that you struggle to turn the bluetooth off and on again once it disconnects or that your phone becomes a little laggy until you turn the bluetooth off?
Yeah - I use the bluetooth widget on the home screen and once it disconnects, it will either take ages to turn off and on again, or it takes 2 presses to turn off.
I have just purchased a Plantronics 230 headset as need bluetooth for my job and it works perfectly - it's no where near the quality of the in car one though.
Also booked in my Audi as it's still under warranty - spoke to them on the phone and they said they will try and update the firmware but the Desire HD isn't on their supported phone list. Have seen a copy of this and not many phones are!!
I would of thought though, that as long as the phone does connect to the phone system in the car that it is compatible.
I have had 30mins once out of it before it disconnected and it was absolutely perfect in that time, including the phone book etc.
I do believe its something to do with the bluetooth on the phone as its a bit strange the way it struggles to turn on again once it fails.
quentin_rayner said:
.. Also booked in my Audi as it's still under warranty - spoke to them on the phone and they said they will try and update the firmware but the Desire HD isn't on their supported phone list. Have seen a copy of this and not many phones are!!
Click to expand...
Click to collapse
That really hacks me off. I mean, BT is a standard. The only reason Audi can give for not supporting a phone that supports at least the same level of BT as them is that they (Audi) do not adhere to the BT standard.
Now, we all know in real life that cars and phones have problems/bugs/whatever BUT unless they can show that there is indeed a *bug* with the phone then the onus should be on Audi to support it.
Dave
Just for the record, it is not just Audi. With me it is together with the Bury carkit, where it first worked fine. (and also works with all other phones...)
Leon
Sent from my Desire HD using XDA App
I can confirm the issues with the BT. I have a parrot Mki9000 in my car and the first time when i tried to connect the DHD , the phone stopped to respond and I was forced to restart it. Since then the phone is paired with the car kit and works fine in a2dp mode for playing music, but when i try to make a call it simply not work. Yo better discribe the problem I will give an example:
The phone i properly connected and playing music, then it's ringing, but the ring sound is coming from the phone speaker not from the car. Then If i answer the call the sound comes from the phone (it shows that there is connection to the car kit). I've tried to press the speaker icon and there is a list with output devices (the phone, loudspeaker, and my car kit) I've tried to select the car kit several times , but there was no success. When I close the phone the music start to play from my car's BT system , so I think there is a problem with the handsfree function/protocol only a2dp works great , and I didn't have any issues with it. Also I've tried file transfer via BT, it works fine two.
Mitsubish Outlander carkit
I can confirm the same issue with the Mitsubish outlander carkit. It even happens that it drops the conversation. sometimes it's ok for half an hour, sometimes it disconnects after 1-2 minutes.
I also have a Jabra (bluetooth) headphone and noticed that if you pick up a call on the phone the sounds doesn't route to the headphone. If I pickup on the headphone it works fine.
ZoidAndroid said:
I can confirm the same issue with the Mitsubish outlander carkit. It even happens that it drops the conversation. sometimes it's ok for half an hour, sometimes it disconnects after 1-2 minutes.
I also have a Jabra (bluetooth) headphone and noticed that if you pick up a call on the phone the sounds doesn't route to the headphone. If I pickup on the headphone it works fine.
Click to expand...
Click to collapse
I have a Pioneer head unit with BT in the car and that seems to work OK, not withstanding the fact that the HU has BT issues of its own (hardware fix needed - I'll get a new unit rather than fix it as I want one with A2DP) but once connected it works fine.
I have a Plantronics headset that seems to exhibit the same problems as your Jabra. At least if I use the phone to answer the call the sound comes through the phone. Also, if I have been using the headset the next call I make goes through the phone speaker which is a pain.
I'm wondering if HTC are routing the sound through the device that's actually *controlling* the call? So even if a headset is paired and connected to the phone, if you use the phone to make the call, as most people would, then it assumes that that's where the sound should get routed. If so, doh .....!!!!!
Just to add, if the sound does get routed to the phone you can use the 'choose speaker' option on the screen to route it to the headset but you shouldn't have to do this.
Anyone reported these issues to HTC and got a meaningful response?
Dave
I did send an email to HTC. Their wonderfull answer was about: "is your phone mentionned in the compatabilylist of the carkit, if not drop the problem there"...
I am still waiting for a response from HTC.
Mines got to a point now where I cant even make a call, it connects to the car, I go through phone book (on car) choose person to call, press call.. it tries for a couple of seconds then comes up disconnected, about 10 seconds later the phone disconnects from the car and will nto reconnect.
My phone then lags like mad until I turn bluetooth off which according to watch tower is taking up about 80% of the CPU.
any updates/solution to all these problems ?
I need it to work with MW600 before buying Desire HD
Last contact I had with HTC is they told me it had been escalted to the software team, so i'm guessing next time a software update comes out it could come about in that, but at the minute no still not fixed.
ZoidAndroid said:
I also have a Jabra (bluetooth) headphone and noticed that if you pick up a call on the phone the sounds doesn't route to the headphone. If I pickup on the headphone it works fine.
Click to expand...
Click to collapse
I've always thought that that's the way it is on all BT headset phones, it makes sense, if the incoming call was for my girlfriend, she can answer from the phone itself, and it automatically routes this through the phones speaker, and if it was answered from the headset, then it routes to the headset.. makes sense to me, I think it's quite good that it does that!
Do any of you have the process com.android.phone crashing when making a phone call through BT?
Ditto my mitsubishi outlander factory bt system. Seemed to work fine first time but then disconnected during first call and would not reconnect for days. Then after connecting not all functions would work ...no incoming call alert on car system, no dialling from car etc. I know the car system is fine as all functions work perfectly with my old nokia xpress music.
Sent from my Desire HD using XDA App
I trust that all of you bother to report this to HTC, at least once per instance ?
- otherwise I don't know when they'll fix this..
Hey everyone. Gotta say, i love this phone its the android device i always wanted. However, im having issues with my car bluetooth which i have not experienced before... namely, that random phonecalls sound completely digitized.
Ive come from an htc desire and htc sensation on the same car without issue and am worried i got a bad BT antenna-or its software...
Anyone out there experiencing the same thing? Any advice (other than buying a new car)?
I am having the same issues on a Verizon Galaxy Nexus V4.02. If I turn bluetooth off mid-call the earpiece sounds fine. The static only happens during voice calls, streaming A2DP sounds fine. There are bluetooth improvements listed in the 4.03 changelog, hopefully this will be resolved.
I had some problems with my BT speaker phone. I turned off the key press sounds and the screen off sounds and that pretty much fixed it.
I have an off topic question for you guys that use bluetooth streaming. Can start the car and press play from the HU to start music? I can with my old D2, but not my TB. I have to actually start the music player on the thunderbolt, then I can control it from my HU. I would like to upgrade, but I don't see a huge advantage in upgrading if I still can't start my music without having to actually take the phone out of my pocket. (Yes, I know it's stupid, but I'm lazy.)
I have this same issue in one of my cars. I ran a number of tests and the issue only occurs on my vehicle when the phone is connected to both for telephony and a2dp music. The static occurs whether or not a2dp is actually being used to stream music or not. This particular vehicle has two separate devices for music and telephony. If I unpair or disconnect the music device, then telephony works without the audio distortion. As soon as I reconnect the music device, the static is re-introduced.
v0yeur said:
Hey everyone. Gotta say, i love this phone its the android device i always wanted. However, im having issues with my car bluetooth which i have not experienced before... namely, that random phonecalls sound completely digitized.
Ive come from an htc desire and htc sensation on the same car without issue and am worried i got a bad BT antenna-or its software...
Anyone out there experiencing the same thing? Any advice (other than buying a new car)?
Click to expand...
Click to collapse
I am experiencing this issue as well and have not been able to resolve it. I've tried disabling the touch sounds, screen off sounds, etc. but to no avail.
It pretty much makes handsfree unusable while driving. What have you guys done in the meantime? Have you been able to resolve the issue yet?
Here's my specific details:
Phone: Verizion LTE Galaxy Nexus v4.02 stock/unrooted
Handsfree Car System (phone audio): Stock 2007 Audi A4
Separate A2DP Module (media audio): Dension Gateway Five connected to factory Stereo
All of my previous phones (Thunderbolt, Droid X, Incredible, OG Droid) have fully supported this setup with no issues whatsoever.
On a sidenote, my A2DP streaming is also unreliable. It first has trouble connecting to the device. If/when it does, audio constantly cuts out when streaming Pandora, Slacker Radio, Google Music... pretty much any streaming over network connection. I have not tried locally stored music yet as I don't have any currently stored on my device. Are you guys experiencing this A2DP issue as well?
I wonder how widespread this is and if it warrants opening an official issue with Google.
I used to have a Blackberry Torch, and I have a Ford Mustang. When I would connect the BT to it, if the Wifi was on, it would "interfere" with the signal. Turning wifi off, fixed the issue. This was a widely known issue with the Torch. Granted that shouldn't have to be a fix, but can any of you verify whether your wifi is on? (regardless of if its connected to anything or not). I'm wondering if the Nexus is using the same BT/WIFI chip that the Torch used.
radi0chik said:
I used to have a Blackberry Torch, and I have a Ford Mustang. When I would connect the BT to it, if the Wifi was on, it would "interfere" with the signal. Turning wifi off, fixed the issue. This was a widely known issue with the Torch. Granted that shouldn't have to be a fix, but can any of you verify whether your wifi is on? (regardless of if its connected to anything or not). I'm wondering if the Nexus is using the same BT/WIFI chip that the Torch used.
Click to expand...
Click to collapse
I appreciate the suggestion but unfortunately, I have the issue even if WiFi is off (I never use WiFi).
I'm going to try and toggle a few of the sound and haptic feedback settings a little more to see if it's pertinent to a certain on/off configuration. It's a shot in the dark but I'll try anything at this point.
ok it was worth a shot. Maybe on a whim turn off 3g/data so basically its airplane mode except BT is on? Just to eliminate any RF interference. Other than that I dont know
Spent quite a bit of time in the car today to try and pinpoint a cause and I have had no luck.
Phone audio will sound great and then all of the sudden turn digitized and distorted for a random period of time, then revert back to sounding great. One thing to note is that the distortion is both ways - the person I'm talking to also hears it when I speak and cannot understand what I'm saying. It's very frustrating not being able to use this feature.
I am on my 2nd replacement phone and ALL of them have had this issue (returned two others to VZW due to this issue and the speaker clicking issue). I am still wondering if it is software/OS releated or if it's due to poor hardware.
Quick Update (kind of):
I messed around with more settings last night. I am happy to report that after I disabled NFC last night, I made several handsfree calls in my car with perfect clarity and no issues. Also, A2DP streaming Pandora worked flawlessly! I was happy that I thought I pinpointed the issue - NFC interference.
BUT this morning, I made a handfree call and it was immediately distorted. Frownie face! A2DP Streaming Pandora still worked great. I am now trying to determine if my success last night was a fluke or if something is different with the phone this morning. The only difference from last night to this morning, that I have been able to identify so far, is I now have the extended battery in the phone. Last night's success had the standard battery. I'll switch them back at lunch and re-test.
Stowegy said:
Quick Update (kind of):
I messed around with more settings last night. I am happy to report that after I disabled NFC last night, I made several handsfree calls in my car with perfect clarity and no issues. Also, A2DP streaming Pandora worked flawlessly! I was happy that I thought I pinpointed the issue - NFC interference.
BUT this morning, I made a handfree call and it was immediately distorted. Frownie face! A2DP Streaming Pandora still worked great. I am now trying to determine if my success last night was a fluke or if something is different with the phone this morning. The only difference from last night to this morning, that I have been able to identify so far, is I now have the extended battery in the phone. Last night's success had the standard battery. I'll switch them back at lunch and re-test.
Click to expand...
Click to collapse
I've got the same issue. Even with NFC disabled. Makes listening to Pandora in the car unbearable. I've gone through the same steps as you, but hasn't exchanged the phone yet. I've had previous Androids and it was a hit/miss with the distortion, but with an iPhone or BB never had this issue. Go figure.
thanks to all the replies, will update to 4.0.3 and try out some more options.
- unplugging my music dongle had no effect on call quality
- NFC on or off had no effect
I also find that the music adapter never auto-connects and needs me to go in to the BT settings page and manually select it.
thanks all.
Hello again. So I have an update that adds to the flakiness ...
Updated to the Bugless Beast ROM and Franco's kernel. My intent was to completely reset the phone and hopefully get a new Bluetooth stack in the process.
Initially everything paired OK, but after a while my audio randomly disconnects after about 20minutes and then reconnects depending on its mood.
My phone connection is more controllable now: if the BT is enabled on my phone when I turn on the car, the sound quality is entirely digitized and unusable. If I turn on the car and THEN enable my phone, the sound quality is flawless every time.
Still not ideal, but manageable. For the music audio part, I lay the blame entirely on the Audi Music Interface BT adapter: the thing is crap and always in pair mode even with the car turned off! The telephone BT in the car head unit has seen several phones pair with it without any issues (I do mobile development so I get to play with many phones) so in that case, I can't blame anything but the Nexus.
I really hope someone at Google or Samsung reads these threads since it would be tough to troubleshoot, but there's no doubt an issue exists with general BT compatibility.
Sent from my Galaxy Nexus using xda premium
Anyone have an update on this issue? Does anyone know of a ROM with a different Bluetooth stack than AOKP? I love everything else about AOKP. I have had the same garbled bluetooth audio from stock - 4.03 with franco and faux kernels with the same result. I had similar problems with Cyanogen 7 ROM I was using on my Incredible the week before I bought the Nexus.
Update - I experimented with a couple of additional devices, and the multiple connections problem with my Nexus is limited to A2DP only devices.
I am now using a Garmin BlueTrip with "phone audio" deselected in bluetooth options. As long as the additional bluetooth device is handsfree profile capable, the A2DP functions perfectly, calls are clear, and the device reconnects after a power cycle consistently. I'm glad this appears to be a software issue and not something we will have to live with for the life of the phone. I'm sure a future update will correct this issue.
I'm also having a problem with Bluetooth calls sounding very digitized and/or choppy. It is bad enough that it can be extremely difficult to make out what the caller is saying. A2DP, on the other hand, has performed pretty flawlessly and the device consistently reconnects each time I get in the car (although it can take up to 30 seconds or so).
I'll have to do a little experimenting with some of the settings mentioned in this thread to see if they have any affect.
On a related note, I feel like sometimes calls made/recieved on the handset can sound digitized as well (although not nearly as bad as over bluetooth). Has anyone else experienced this?
My hardware is:
Verizon GNex (4.0.2)
Parrot MKi9000
Hello, I've got the LG G3 D855 on Lollipop and I recently bought a Motorola Hint. It's a great headset and works on every phone i've tried it with except fully for the LG G3. It doesn't seem limited to this bluetooth headset either as I've tried multiple and they all have this issue. It seems that when touching the headset button (the one for ending calls etc) it doesn't do anything on the phone. On other android phones it starts up google now or allows you to choose what launches when pressed, but on this phone it doesn't seem to even register. It does work however when in a call to work for answering and ending but it doesn't register when not in a call. It seems as though the phone doesn't pick up anything when pressed, it even works on an iphone to initiate siri and every other android phone but no my G3 though I have heart it works fine on other variants which allow to launch either google now or 'voice mate' , and by the way voice mate isn't installed anywhere on this phone either,. Also, when using google now normally by opening it, audio runs through the headset but not the microphone for voice input, this only works on calls. I would root the phone and put another rom on it but you also can't root the G3 which is running Lollipop before being rooted also aha.
All very confusing I know, but would love to know if anyone else has this issue or know how to fix it!
Thanks
fraserh02 said:
Hello, I've got the LG G3 D855 on Lollipop and I recently bought a Motorola Hint. It's a great headset and works on every phone i've tried it with except fully for the LG G3. It doesn't seem limited to this bluetooth headset either as I've tried multiple and they all have this issue. It seems that when touching the headset button (the one for ending calls etc) it doesn't do anything on the phone. On other android phones it starts up google now or allows you to choose what launches when pressed, but on this phone it doesn't seem to even register. It does work however when in a call to work for answering and ending but it doesn't register when not in a call. It seems as though the phone doesn't pick up anything when pressed, it even works on an iphone to initiate siri and every other android phone but no my G3 though I have heart it works fine on other variants which allow to launch either google now or 'voice mate' , and by the way voice mate isn't installed anywhere on this phone either,. Also, when using google now normally by opening it, audio runs through the headset but not the microphone for voice input, this only works on calls. I would root the phone and put another rom on it but you also can't root the G3 which is running Lollipop before being rooted also aha.
All very confusing I know, but would love to know if anyone else has this issue or know how to fix it!
Thanks
Click to expand...
Click to collapse
Exactly the same issue with my phone. I have been trying all afternoon (in vain) to get the phone button on the headset (Sena SMH5) to do anything. Similar to you, I can answer calls/end calls but in an idle state, the button does nothing. I called LG support but would have been as well not bothering as he suggested a "compatibility" issue as my headset is bluetooth 3.0, the LG G3 is bluetooth 4.0. I advised him that this was also the case on my previous Samsung S4 and that had no issues so the issue must lie with the G3 and in any case, bluetooth should be backwards compatible. I have also tried the bluetooth launcher app (which didn't work) and various other apps (utter, voice command,dragon) all with no joy.
I get the impression that the function is somehow disabled. The quest for a solution continues.....
LG G3 UK version running Android 5.0
Similar functionality got broken on the moto g by an update to the google/google now app. A rollback the apps to stock fixed it until moto released a patch. Worth a try?
Somewhat of the same issue got a jabra head set and my d852 does not respond to media buttons like changing tracks or play pause buttons
Same here with D855 lollipop V20h-EUR-XX and Jabra Motion. The Jabra Motion is able to launch Google Now with all my other phones.
same here with plantronics voyager legend.. call button does nothing..any workaround now?
Hello All,
I have had a strange problem with bluetooth calling on my phone that has popped up in the last few weeks. If I attempt to make or receive a call using any sort of bluetooth headset, or the hands free radio in my car, I am unable to hear the other person, but they can hear me. This issue only is related to calls. I can use my phone for streaming bluetooth music, to both my car and various speakers. Another thing about this that is strange is that I can listen to music with my Jaybird Bluebuds X, but if it were a call I would not hear anything. I have tried using another phone with my car's hands free system, and that phone works correctly. This is what leads me to believe that this is a phone issue.
About my phone. I have the Verizon Note 4, and have been running Jasmine ROM v6 since late May or early June maybe. My phone has worked fine until sometime in the beginning of August. Last night I decided to update my phone to Jasmine ROM v7, thinking that this is somehow a software issue (I had already tried wiping cache, deleting bluetooth devices etc.). I was able to update, but the issue is still there. I am now lost.
Has anyone experienced this before? This seems strange to me, that music works correctly, but call audio does not. I assume that the bluetooth hardware is working correctly, or else nothing would work and that the issue is somehow related to the software bluetooth profiles. Any ideas?
TL;DR; Bluetooth call audio on my end does not work, but music does. I'm not sure why.