Related
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
Is anyone else having problems with Bluetooth Audio on Kitkat. Mine glitches quite oftemn with my Sony MW600 headphones and also my Bose Soundlink 2 Speaker, I didn't notice it before KitKat? I have also tried the Headset-Bluetooth-Fix_CWM but no change really?
Any solutions out there? anyone else using similar Hardware to mine without problems?
wilx said:
Is anyone else having problems with Bluetooth Audio on Kitkat. Mine glitches quite oftemn with my Sony MW600 headphones and also my Bose Soundlink 2 Speaker, I didn't notice it before KitKat? I have also tried the Headset-Bluetooth-Fix_CWM but no change really?
Any solutions out there? anyone else using similar Hardware to mine without problems?
Click to expand...
Click to collapse
Hi,
I also have all sorts of problems with bluetooth, but I have not been able to find a good fix. To me it seems like issues with 4.4.2 and not specifically the Galaxy Note II. Looking at a LG forum, some guys adviced that switching off WIFI seemed to help. I have tried it out for one of my problems (microphone on BT headset stopping in the middle of a phone call), and it actually seemed to help. You could try it out.
Initially I thought it was issues with a Sony SBH-52 headset, but now that I also have issues (though different) with a Jabra Play, I have come to the conclusion that it must be the phone (software).
I am in contact with my local Samsung support team, and trying to see if they want to take the phone in for service.
Good luck!
spip72 said:
Hi,
I also have all sorts of problems with bluetooth, but I have not been able to find a good fix. To me it seems like issues with 4.4.2 and not specifically the Galaxy Note II. Looking at a LG forum, some guys adviced that switching off WIFI seemed to help. I have tried it out for one of my problems (microphone on BT headset stopping in the middle of a phone call), and it actually seemed to help. You could try it out.
Initially I thought it was issues with a Sony SBH-52 headset, but now that I also have issues (though different) with a Jabra Play, I have come to the conclusion that it must be the phone (software).
I am in contact with my local Samsung support team, and trying to see if they want to take the phone in for service.
Good luck!
Click to expand...
Click to collapse
Thanks, I may try the Wifi next time I use, let me know what Samsung say please
Hi all I recently updated my verizon note 8 to 8.0 and all is well except bluetooth. Even connected to my car songs will skip stutter and often disconnect itself from bluetooth altogether. I never had this problem on 7.1. Any ideas how to fix this? Anybody else have bluetooth issues with this update?
I only use it on my LG HBS-1100 Headset and no problems. BTW, love all the sound optimizing this phone has.
Now if ONLY it could be rooted so I could have Viper back
I've noticed some lag or difficulty connecting since updating to Oreo. Have not tried diagnosing yet though.
I have stuttering on 7 and 8. But just on bluetooth speakers not headphones.i just associate it with using cheap speakers and higher quality headphones.
Hello.
I am on latest AEX 6.7, I have bought a pair of bluetooth 5.0 headphones, and the audio on call is really bad (they hear me far away). I'm pretty sure it's the ROM's fault (the headphones are of excellent quality).
Is bluetooth bad on any AOSP ROMs? Do you have any suggestions?
Scofield1990 said:
Hello.
I am on latest AEX 6.7, I have bought a pair of bluetooth 5.0 headphones, and the audio on call is really bad (they hear me far away). I'm pretty sure it's the ROM's fault (the headphones are of excellent quality).
Is bluetooth bad on any AOSP ROMs? Do you have any suggestions?
Click to expand...
Click to collapse
Try magisk module call recorder skavalex.. No issues for me in any ROM from nougat to.pie
sanjay.2704 said:
Try magisk module call recorder skavalex.. No issues for me in any ROM from nougat to.pie
Click to expand...
Click to collapse
Is this module for record phone calls? The recording of phone calls is already integrated in the AEX, and that isn't the problem.. the problem is the poor quality of the microphone of the bluetooth earphones in phone calls.
Scofield1990 said:
Is this module for record phone calls? The recording of phone calls is already integrated in the AEX, and that isn't the problem.. the problem is the poor quality of the microphone of the bluetooth earphones in phone calls.
Click to expand...
Click to collapse
If you using default call recorder, tty changing the format from arm to aac and then check..
sanjay.2704 said:
If you using default call recorder, tty changing the format from arm to aac and then check..
Click to expand...
Click to collapse
You didn't understand the meaning of my post.
Phone microphone is ok, both in voice call (also recorded), and VoIP.
The problem is when I connect a bluetooth headset, so the default microphone becomes the bluetooth headset, so when I make a phone call (normal or VoIP) my voice feels very low and far, and my caller struggles to hear me.
So, I asked, since I'm sure the bluetooth headsets are of excellent quality, if I could do something to improve the bluetooth of the zuk in the calls, because I read around that the problem could be of the AOSP roms, but I don't want to go back to a rom stock only for bluetooth (and I'm not even sure it would improve).
(If even now you have not understood the meaning of my question, you are a troll)
Scofield1990 said:
You didn't understand the meaning of my post.
Phone microphone is ok, both in voice call (also recorded), and VoIP.
The problem is when I connect a bluetooth headset, so the default microphone becomes the bluetooth headset, so when I make a phone call (normal or VoIP) my voice feels very low and far, and my caller struggles to hear me.
So, I asked, since I'm sure the bluetooth headsets are of excellent quality, if I could do something to improve the bluetooth of the zuk in the calls, because I read around that the problem could be of the AOSP roms, but I don't want to go back to a rom stock only for bluetooth (and I'm not even sure it would improve).
(If even now you have not understood the meaning of my question, you are a troll)
Click to expand...
Click to collapse
Is the recording OK when not using BT headset keeping recording format same.
Just to let you know.. There are other users who have faced problem of similar kind whose issues have resolved by changing audio recording format to aac.. I also use Bluetooth headset seinhizer HD 4.40 BT.. I have no such issues coz I always use the module and no such issues for me.. That's why I suggested..
I don't troll.
Skavalex has option to select recording source as internal and not mic which could have solved your problem.
sanjay.2704 said:
Just to let you know.. There are other users who have faced problem of similar kind whose issues have resolved by changing audio recording format to aac.. I also use Bluetooth headset seinhizer HD 4.40 BT.. I have no such issues coz I always use the module and no such issues for me.. That's why I suggested..
I don't troll.
Skavalex has option to select recording source as internal and not mic which could have solved your problem.
Click to expand...
Click to collapse
Ok, i will try. Thanks ?
Tws earphones are often limited in this, the mic is actually far away from your mouth so you might get low input from them, the fault isnt your phone, its just that even the pricier tws earphones suffer the same problem. Its just physics, when you speak, the sound goes forward but the mic of the tws is near your ear so the sound gain is very low. Try using the same tws on other phone amd see if the problem persists
Scofield1990 said:
You didn't understand the meaning of my post.
Phone microphone is ok, both in voice call (also recorded), and VoIP.
The problem is when I connect a bluetooth headset, so the default microphone becomes the bluetooth headset, so when I make a phone call (normal or VoIP) my voice feels very low and far, and my caller struggles to hear me.
So, I asked, since I'm sure the bluetooth headsets are of excellent quality, if I could do something to improve the bluetooth of the zuk in the calls, because I read around that the problem could be of the AOSP roms, but I don't want to go back to a rom stock only for bluetooth (and I'm not even sure it would improve).
(If even now you have not understood the meaning of my question, you are a troll)
Click to expand...
Click to collapse
Hey there..I am facing the similar issue. Did you solve it?
Yogesh Kulkarni said:
Hey there..I am facing the similar issue. Did you solve it?
Click to expand...
Click to collapse
Yes.. I solved it by changing the smartphone Unfortunately, by switching to ROM AOSP there is a worsening of many things, which come out in daily use, for example, the audio in VoIP video calls (whatsapp, Instagram, etc.) is poor .. they hear me very far away or with disturbances .
Hello. I change phones alot and have noticed that some phones(all android) have better bluetooth playback than others.
I had a oneplus 7 pro before this phone and the bluetooth quality to my truck was great and had no issues but with this phone the highs sounds scratchy or like if the speaker is bad. But if i connect it with a wire connection it sounds great. Everything with the 2 phones is the same. On both i was using the galaxy watch and pretty much the same apps. On a previous phone the note 8 i had the same issue but it was a different car. Seems like its the way samsung handles bluetooth.
Has anyone had this issue? If so was there a fix?
Thanks
make sure not on mic
Sent from my SM-N975F using Tapatalk
jemfalor said:
make sure not on mic
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
What do you mean?
The only two things I think about is the codec used that may be different across devices, and the Bluetooth settings that sync the phones volume with the headset (the differences are noticeable).
Since no DAC is used in Bluetooth, I don't think it can comes from them, for a same headset.
On Samsung phones you should run the adapt sound process. Try this.
I tried with the sync volume off too and no improvement.
I looked for the adapt sound and my phone doesn't have that setting. Or is it something different?
It's in Sounds and Vibration 》 Advanced Sound settings 》Sound Quality and effects 》 Adapt sound
You have to do this in a quiet place and ensure to answer honestly. If you can't hear the beeping press no.
After doing this the sound quality is night and day difference.
Ok found it. Ill play with it a bit. Thanks
I've had issues sometimes with audio being piped through the "Calls" Bluetooth channel versus the "Audio" channel so worth checking as the quality is obviously night and day.
I also like enabling Dolby Atmos on my Note 10+ for music so worth playing with too. Additionally, I recently found Samsung's Sound Assistant app which let's you customize a bunch of sound settings so worth checking out as well:
https://play.google.com/store/apps/details?id=com.samsung.android.soundassistant
sansnil said:
I've had issues sometimes with audio being piped through the "Calls" Bluetooth channel versus the "Audio" channel so worth checking as the quality is obviously night and day.
I also like enabling Dolby Atmos on my Note 10+ for music so worth playing with too. Additionally, I recently found Samsung's Sound Assistant app which let's you customize a bunch of sound settings so worth checking out as well:
https://play.google.com/store/apps/details?id=com.samsung.android.soundassistant
Click to expand...
Click to collapse
Is there an easy way to tell if the audio is going through the call channel?
ErickF said:
Is there an easy way to tell if the audio is going through the call channel?
Click to expand...
Click to collapse
Easiest is probably just uncheck calls in your phones BT settings for your truck (and make sure audio is enabled). If the sound is still not great then this isn't the issue.
Sorry to respond to an old thread, but I was wondering if any of this fixed the OP's problem. I followed all the recommendations here and on other threads but have not been able to solve my recent Bluetooth audio problem. The sound has been terrible lately.
Same issue here on my s10+. When playing any audio in my car via BT i hear the distortion/hissing noise especially when the song has a higher treble frequency.
I have just about tried all fixes i could find on Google, and no luck.
When connecting to my ear buds (Jabra Elite 65t) it disappears and checked in developer mode that it supports to AAC for BT Codecs.
But when connecting to the car it reverts to SBC.
The issue clearly lies on Samsungs side, as my brother has a Huawei p30 Pro, also has bluetooth 5 and plays amazingly well in all aspects (Bass-Mids-Treble).
I know I'm posting this almost a year later, but i am desperately looking for a fix.
SN. I have recently updated my phone to Android 10, despite all the complaints to Samsung from many users... Sadly this issue has not being fixed on my side.
From what i see online, people have given up on Samsung and opted for Rooting their Samsungs and installing Viper4Andriod.
Has any one done this and can confirm that it fixed the issue?