At my case it stutters all the way, and the problem doesn't depend on BT receiver and radio interference.
Switching to adaptive mode almost eliminate the problem, but almost only (and how does want LDAC 330 Kbps?).
I have a completely similar situation on this tablet.
And also the problem is solved only by switching to the mode: "balanced audio and communication quality"
Related
I'm on 8.1 dp2 in hopes of a fix but it doesn't seem to have helped. My Bluetooth audio skips once every song or two and it's super frustrating while in my car. I've tried disabling WiFi and Bluetooth scanning and adjusting the codec options but nothing seems to work? Anyone else with this issue or a solution? I just received wireless earbuds so I'll test those to make sure it's not my stereo but my s8 had worked fine...
Ok say my new ear buds are Bluetooth 5 and I haven't noticed a single skip yet. My stereo is only 3 so maybe that has something to do with it? As far as I can find however there are no current bt5 stereos so I'm not sure what the issue or solution would be...
Enable the developer options. You can choose between sound quality and connective stability. You can also lower the sampling rate to 44100kHz. In a word, reduce the data transferring rate. I think these might help.
I did all of that and have tried all the options
slyr114 said:
I did all of that and have tried all the options
Click to expand...
Click to collapse
I have had this problem cropping up on various Toyota forums with the root cause being the automotive entertainment systems. It appears that most newer systems are still based on 2008/9 technologies which only have a limited ability to buffer the B/T audio. I'm not suggesting that this is your car but I thought it is worth mentioning.
Ive got a Sony stereo I put in myself haha it's relatively new
Been using the Pixel 3 as my daily driver for a while now, but just recently came an interesting piece. Apparently, the Pixel 3 doesn't support LDAC at Optimum Audio Quality (more details here - https://themrphone.com/article/google-pixel-3-xl-doesnt-support-ldac-at-optimum-audio-quality/)
I was planning on buying a high-end set of Bluetooth headphones, in fact, was considering the same ones used in the link above. Can anyone else confirm this?
varounmirchi said:
Been using the Pixel 3 as my daily driver for a while now, but just recently came an interesting piece. Apparently, the Pixel 3 doesn't support LDAC at Optimum Audio Quality (more details here - https://themrphone.com/article/google-pixel-3-xl-doesnt-support-ldac-at-optimum-audio-quality/)
I was planning on buying a high-end set of Bluetooth headphones, in fact, was considering the same ones used in the link above. Can anyone else confirm this?
Click to expand...
Click to collapse
Working fine for me with both LDAC (detected and used automatically) and "Optimised For Audio Quality" (switched from default "Best Effort" in Developer Settings)
Pixel 3 (non XL) with Sony MDR-1000X (gen 1 of the headphones in your linked article) and Google Play Music.
Granted GPM isn't a Hi-Res source, but it's playing fine! There was a momentary drop in audio for a split second on changing bit rate but it resumes with no issue!
I had this same issue with my Audeze Mobius--the Pixel 2 allowed me to set the rate to 990, but the Pixel 3 would do as described in the link. Seems like a software bug, I doubt it actually isn't capable of using the full rate
I can't say, I'm much of an audiophile or anything but I do like to play with settings for what sounds best with what I have. On my Galaxy s8 running oreo and my previous s5 running aospx/oreo I could change the developer Bluetooth settings on the fly and notice the difference instantly (avrcp/bt_codec/sample_rate/bit_rate/ldac_codec).
If I do it on the pixel 3, the Bluetooth just falls out, connection wise it stops but still shows it's connected, app wise I can't close and reload the app. I have to turn the Bluetooth off or reset it completely sometimes.
It's kind of a bummer, being a brand new phone and all, I noticed the absolute volume disable didn't seem like a difference either.
I hope they resolve it.
Update: disabling bluetooth a2dp hardware offload let me freely change all those settings while in use with out locking anything up. What that necessarily does or the effect of changing the settings and how well they actually change??? I can't answer with any rational or testworthy explanation as my audio products are oem Bluetooth radios in vehicles.
Every device I've tried with my note 10 has had awful bluetooth crackle unless I really turn down the volume. For some devices (car etc) this is fine, but for something like headphones they become unusable, either being too quiet or sounding awful.
Anyone run into this problem, or have a fix for it? I'm going to try factory resetting the phone and if that doesn't work I will get rid of it and buy something else.
I use my Mi Note 10 with Global rom with my Mondeo mk4 (FL). Full volume, zero crackle/issues.
Check Developer Options, as far as I know you can specify like codecs and whatnot. You might have to set that on your car.
Figured it out. The crackle for me happens when I'm connected to a weak 2.4GHz WiFi access point. Connecting to a 5GHz WiFi or a strong 2.4GHz signal solves the problem completely
It's co channel interference between WiFi and Bluetooth. Hopefully Xiaomi can make some improvements in updates (changing modulation, etc)
I have the Exynos 10+ 5G and the Snapdragon Tab 6S. LDAC at 990 kbps only works properly with the Snapdragon device; too much distortion with Exynos. What is your experience?
Solved. Distortion only happens when the screen is on. That means BT is affected by the Note's special screen!
Incrredible
I had the same probleme with my Galaxy note 10 plus.
LDAC 990 b/s only works when the screen is off.
Who would have thought of that ?
Thanks a lot.
same problem here, SM-N975F. Exynos.
Fiio BTR3 receiver.
Turning the screen off allow 990 sound but as soon i turn the screen on, the sound start to stutter,then if i turn it off, the sound is clear.
Samsung support tell me to let the bluetooth setting to ''best effort''... classic level 1 support answer.
I'm not sure that best effort use 990 bandwith when the screen is off but since i don't manage to find out any sound improvement between 660 and 990 (I listen my music on spotify), i gave up.
Same problem here but it happens even with screen of with Sony WH-1000XM3 / best quality LDAC, april 2020 update. For anyone that cares about BT/LDAC or music in general (considering there's no 3.5 jack), just avoid this phone!
PapaSpiro said:
same problem here, SM-N975F. Exynos.
Fiio BTR3 receiver.
Turning the screen off allow 990 sound but as soon i turn the screen on, the sound start to stutter,then if i turn it off, the sound is clear.
Samsung support tell me to let the bluetooth setting to ''best effort''... classic level 1 support answer.
I'm not sure that best effort use 990 bandwith when the screen is off but since i don't manage to find out any sound improvement between 660 and 990 (I listen my music on spotify), i gave up.
Click to expand...
Click to collapse
Funny enough S8 Exynos was and is perfectly fine with 990kbps!
Only drawback - sound issues started to appear on 75% of max distance (of 330kbps).
Difference 660<>990 is definitely there! But sadly S10E Exynos can't handle it.
Note 20 ultra Exynos, same problem here.
Work around:
1. Install Sony music center. In bluetooth output setting, sellect Prioritize LDAC.
2. TURN OFF LOCATION in Android settings
3. Enjoy LDAC 990 )
tamthoima said:
Note 20 ultra Exynos, same problem here.
Work around:
1. Install Sony music center. In bluetooth output setting, sellect Prioritize LDAC.
2. TURN OFF LOCATION in Android settings
3. Enjoy LDAC 990 )
Click to expand...
Click to collapse
One more thing: don't use 2.4Ghz wifi (use 5Ghz only or turn off wifi and use Mobile data while listening using LDAC 990kbps). This is so because Bluetooth devices (including Bluetooth headphones) operate on the same frequency range with wifi 2.4Ghz and may interfere with each other.
I have a P7P, Galaxy Watch 4 and Sony WF-1000XM4 LDAC iem. I'm noticing a LOT of stutter when I set the Codec Playback Quality to "Optimized for Audio Quality (990kbps/909kbps)".
The stuttering goes away and sound is perfect when I place the GW4 in sleep mode. This seems to only be an issue with Pixel 6 and up - has there been some low level change to bluetooth hardware/stack since Pixel 6? Is this a bandwidth issue?
This isn't an issue with other Android 13 phones from what I am hearing - this is close to a deal breaker for me unless there is some workaround/fix. Has anybody else noticed it? Would a custom kernel help?
Some discussion on Reddit:
https://www.reddit.com/r/GooglePixel/comments/y859oi
Thanks,
plemen said:
I have a P7P, Galaxy Watch 4 and Sony WF-1000XM4 LDAC iem. I'm noticing a LOT of stutter when I set the Codec Playback Quality to "Optimized for Audio Quality (990kbps/909kbps)".
The stuttering goes away and sound is perfect when I place the GW4 in sleep mode. This seems to only be an issue with Pixel 6 and up - has there been some low level change to bluetooth hardware/stack since Pixel 6? Is this a bandwidth issue?
This isn't an issue with other Android 13 phones from what I am hearing - this is close to a deal breaker for me unless there is some workaround/fix. Has anybody else noticed it? Would a custom kernel help?
Some discussion on Reddit:
https://www.reddit.com/r/GooglePixel/comments/y859oi
Thanks,
Click to expand...
Click to collapse
This is due to how LDAC works, it steals bandwidth from the BT data streams to carry that bitrate. It may be an issue with other devices, or other devices may have some QoS or something to that effect on the bluetooth side of things to prioritize the audio streams over data.
You could try a custom kernel in case it is some frequency capping or something on the device causing the issue.
DespairFactor said:
This is due to how LDAC works, it steals bandwidth from the BT data streams to carry that bitrate. It may be an issue with other devices, or other devices may have some QoS or something to that effect on the bluetooth side of things to prioritize the audio streams over data.
You could try a custom kernel in case it is some frequency capping or something on the device causing the issue.
Click to expand...
Click to collapse
It doesn't seem to be an issue on earlier Pixels or other phones, just PIxel 6 and up. I'm not very familiar with the available custom kernels for P7P, reading up on them now.
Anybody have any suggestions on a stable kernel that could potentially address a possible frequency cap?
I solved this problem by turning off Ultra-Wideband (UWB) under connection preferences.
I presume bluetooth scanning is a part of this function, and makes sense if while scanning momentarily the available bandwidth is reduced.
This is not solving your problem but I play exclusively FLAC both 16 and 24 bit, have developer options switched on as well and have zero stutter or any other problems (that I've noticed). Strange that a lower quality format has these problems. It is not hi-res, typically has a smaller file size and is easier to decode after all.
blackspp said:
This is not solving your problem but I play exclusively FLAC both 16 and 24 bit, have developer options switched on as well and have zero stutter or any other problems (that I've noticed). Strange that a lower quality format has these problems. It is not hi-res, typically has a smaller file size and is easier to decode after all.
Click to expand...
Click to collapse
Did the OP mention file types? I was under the impression the Reddit thread was a separate discussion not started by OP. I may have missed it though. My pedantic self would argue no Bluetooth audio is capable of true hi-res.
I believed this thread (and my issue) was to do with Bluetooth bandwidth, not directly the file type which obviously dictates the required bandwidth. The same issues persist for me whether it is a very high bit rate lossy format such as MP3 above 990kbps, or a lossless format such as FLAC. It was also irrespective of whether the hardware decode was handed off to the reciever or computed on the handset.
Anyway, for whatever reason having UWB off solved my particular issue. I primarily use lossless media codecs such as FLAC for reference.