So I've made a couple posts about my problems with bluetooth audio streaming, but I have a bit of a different question this time. I have been trying a multitude of AOSP roms (4.1, 4.2, and 4.3) trying to get my bluetooth audio to work properly. I have had no luck, the audio is super choppy and distorted.
Recently I tired the Eclipse 5.1 ROM which another user told me specifically his bluetooth audio streaming was fine (on the same model phone!). I did a 100% clean install, I wiped everything, including internal & external storage. I tried fixing permissions (which he said he did to get it to work), and nothing. I still get choppy audio over BT. Does anyone have any idea what could be causing this? What is there beyond the ROM that would affect BT?? I even tried CM 10, which is 4.1 (a version with the old BT stack implemented) and still got choppy audio!! The only thing that seems to work for me is TouchWiz roms.
One thing I notice, and I'm not sure this affects anything, is when I boot into download mode in the binaries line it says "(3 count)"
If anyone has any light to shed on this it would be awesome!
Thanks so much.
Hello all... Hoping to get some help for my unlocked AU Oppo R7plus f handset with ColorOS 2.1.1. I have a new car with Android Auto, and my phone doesn't seem to function correctly.
I've enabled developer mode to enable USB debugging which allowed my handset to be detected by my car but the audio quality is distorted using Android Auto. It isn't streaming audio quality I am referring too - all google and navigation commands and music stored on my phone have the same issue.
Its not the car or the USB cable as I've tested my Samsung and Apple handsets and they work with my car.
What else can I try?
Can you safely uninstall ColorOS and install Android Marshmallow instead? I'd need guidance
Any idea on when ColorOS 3.X will be released?
Thanks in advance!
Lukey G said:
Hello all... Hoping to get some help for my unlocked AU Oppo R7plus f handset with ColorOS 2.1.1. I have a new car with Android Auto, and my phone doesn't seem to function correctly.
I've enabled developer mode to enable USB debugging which allowed my handset to be detected by my car but the audio quality is distorted using Android Auto. It isn't streaming audio quality I am referring too - all google and navigation commands and music stored on my phone have the same issue.
Its not the car or the USB cable as I've tested my Samsung and Apple handsets and they work with my car.
What else can I try?
Can you safely uninstall ColorOS and install Android Marshmallow instead? I'd need guidance
Any idea on when ColorOS 3.X will be released?
Thanks in advance!
Click to expand...
Click to collapse
I have exactly the same issue.
I have come across this issue on updating my car radio to one that is Android Auto compatible (Hyundai i30 GD-03 radio). My phone is an Oppo R7sf ColorOS 2.1.0i, Android 5.1.1.
'All' music, voice directions, Google assistant, youtube audio come through with a horrible distortion with the original signal barely audible beneath. The distortion is a short transient produced every 43ms (approx 23Hz).
I initially thought it could be some sort of electrical interference issue (but surely the USB audio is digital?). In experimenting with audio played through Android Auto via Black Player, I came across some songs on my phone that would play perfectly!
Looking at the 'good' and 'bad' song files in detail, it became obvious that all of the distorted (bad) songs were 44.1kHz sample rate. Other files with sample rates of 96kHz and 48 kHz played perfectly.
Which now makes me think this is a software issue with my phone. I tested with my wife's Samsung Galaxy S5 and it worked perfectly.
thommo101 said:
I have come across this issue on updating my car radio to one that is Android Auto compatible (Hyundai i30 GD-03 radio). My phone is an Oppo R7sf ColorOS 2.1.0i, Android 5.1.1.
'All' music, voice directions, Google assistant, youtube audio come through with a horrible distortion with the original signal barely audible beneath. The distortion is a short transient produced every 43ms (approx 23Hz).
I initially thought it could be some sort of electrical interference issue (but surely the USB audio is digital?). In experimenting with audio played through Android Auto via Black Player, I came across some songs on my phone that would play perfectly!
Looking at the 'good' and 'bad' song files in detail, it became obvious that all of the distorted (bad) songs were 44.1kHz sample rate. Other files with sample rates of 96kHz and 48 kHz played perfectly.
Which now makes me think this is a software issue with my phone. I tested with my wife's Samsung Galaxy S5 and it worked perfectly.
Click to expand...
Click to collapse
just curious. is this issue present on Official LineageOS 14.1 for the R7S?
celoxocis said:
just curious. is this issue present on Official LineageOS 14.1 for the R7S?
Click to expand...
Click to collapse
Hi celoxocis, I am unsure. My R7S is currently stock (it is my day-today phone). I COULD try and install Lineage, although currently don't want to risk bricking anything (small chance I know). So I'm PROBABLY going to get a new phone at some stage. So then I'd be able to test out LineageOS
Hi, last week I installed the OTA Android 8.0 update on my HTC U11.
Since this update the audio quality when streaming to my car's audio system or to my pioneer hi-fi system at home is a lot worse than on Android Nougat. Especially on tracks with a lot of high tunes. There's always a slight 'clink' noise. I don't know how to explain this in English..
Have you noticed this issue as well? Is there something I can do about it? Thanks
question are you using any sound mods?
6th_Hokage said:
question are you using any sound mods?
Click to expand...
Click to collapse
No, I don't use any sound mods.
joscht said:
No, I don't use any sound mods.
Click to expand...
Click to collapse
Same for me. Since this update, the quality of phone call when connected to Bluetooth to my car is really bad. No problem with music stream connected to the same car.
I tried managing the new bluetooth options in developper mode menu but it doesn't solve the problem.
The codec used is all the time SBC even is I change it to AAC or aptX or AptxHD.
Fredz said:
Same for me. Since this update, the quality of phone call when connected to Bluetooth to my car is really bad. No problem with music stream connected to the same car.
I tried managing the new bluetooth options in developper mode menu but it doesn't solve the problem.
The codec used is all the time SBC even is I change it to AAC or aptX or AptxHD.
Click to expand...
Click to collapse
I have the same issue, it seems it was fixed in 42 version for US market(at least for LDAC)
I have 2 issues with Bluetooth connections with the car. The first is that it picks up interference from the noise of the wheels and engine while driving, and the sound quality suffers and it sounds unclear, unless I mute the vehicle.
The second is that it has a lot of trouble connecting to the car at times. Or, more often, it would not connect the media through the car. Don't know what's up with that.
I know how you feel
I've got exact same problem like yours. Although I'm using HTC u11 plus. My new pair of Bluetooth headphones have the same not OK audio quality. You're right especially the high tunes. I'm desperate, trying to reset everything, but doesn't help. If you find the solution, please let me know. Thank you.
joscht said:
Hi, last week I installed the OTA Android 8.0 update on my HTC U11.
Since this update the audio quality when streaming to my car's audio system or to my pioneer hi-fi system at home is a lot worse than on Android Nougat. Especially on tracks with a lot of high tunes. There's always a slight 'clink' noise. I don't know how to explain this in English..
Have you noticed this issue as well? Is there something I can do about it? Thanks
Click to expand...
Click to collapse
Same issue here. I have the U11 as well and just updated to Oreo and I have the same issue as well. Music over BT was ok on Nougat but after the update, music sounds as if there is digital clipping. And it's there with both my headset and car audio system.
Got the same issue, hope they fix it soon. The only solution seems to do a RUU right now.
Btw. I am on a custom rom (LeeDroid), gonna go full stock and try again.
I would suggest looking in developer options and trying some of the different options for bluetooth in there!
Settings > about > software information > more > then tap the build number till it says you are a developer.
Then
Go to developer options and check under networking, there are some settings to toggle in there.
You may find something you are looking for! I personally haven't tried bt since the update so I don't know if it is a common issue. Good luck!
Thank you!
Thank you very much.
Playing around with the bluetooth options in the developer's menu solved this issue.
The audio quality through bluetooth is now pretty much the same as it was with the previous android os
joscht said:
Thank you very much.
Playing around with the bluetooth options in the developer's menu solved this issue.
The audio quality through bluetooth is now pretty much the same as it was with the previous android os
Click to expand...
Click to collapse
Share what settings you stuck with so it may help the other people with the same problem
Hey there!
Same problem for me since updating my U11 to Oreo - very poor bluetooth audio quality...
I tried using different bluetooth settings under the developer options but the thing is: no matter what I choose, it keeps switching back to the default values not affecting anything at all.
If it switch back to default SBC it means your headset/BT device doesn't support other codec.
Alpert3 said:
If it switch back to default SBC it means your headset/BT device doesn't support other codec.
Click to expand...
Click to collapse
That's not necessarily true. On 7.1 both Bluetooth devices which I use can support either AAC, SBC and aptX. My understanding is this issue occured because of the removal of AVRCP 1.3. I think Google added 1.3 back to Android 8.q because of this.
yournamehere484 said:
That's not necessarily true. On 7.1 both Bluetooth devices which I use can support either AAC, SBC and aptX. My understanding is this issue occured because of the removal of AVRCP 1.3. I think Google added 1.3 back to Android 8.q because of this.
Click to expand...
Click to collapse
Yours is not necessarily true either. I'm on 8.0 and I can still use aptX if I want but only if my BT device supports aptX.
Alpert3 said:
Yours is not necessarily true either. I'm on 8.0 and I can still use aptX if I want but only if my BT device supports aptX.
Click to expand...
Click to collapse
I'm not arguing that aptX and other codecs aren't working on 8.0. What I'm saying is that with certain devices, we are no longer seem to be able to use certain codecs that we could use prior. It's obviously device dependent, but to say their isn't a problem and blame it on the Bluetooth device is incorrect. Infact the same problem has occurred on non HTC devices when they've upgraded to 8.0 such as the OnePlus.
yournamehere484 said:
I'm not arguing that aptX and other codecs aren't working on 8.0. What I'm saying is that with certain devices, we are no longer seem to be able to use certain codecs that we could use prior. It's obviously device dependent, but to say their isn't a problem and blame it on the Bluetooth device is incorrect. Infact the same problem has occurred on non HTC devices when they've upgraded to 8.0 such as the OnePlus.
Click to expand...
Click to collapse
Fair enough, I didn't understand.
Does anyone know how to make the bluetooth options under developer options stick? I'm on stock unlocked Oreo, and they go back to defaults as soon as I change them. I've tried changing them whilst connected in the car, but no change. The only thing that could make a difference is that I'm running Pitch Black Substratum theme. Anyone else got them to stick?
In my Audi a3 2015 before oreo i can able to skip the track with entertainment commad and in the display i saw name of the track. After update i have lost all funtionality and the car see my device only like esternal suorce . Can i do something?
Currently on Android 11 with Android Auto v 7.0.614134 and V4A v 2.7.1.6. When connected via bluetooth music is processed via V4A and sounds fantastic. When connected with Android Auto via USB, music does not get processed via V4A even though there is a USB setting in V4A. Music also does not get processed via the Speaker tab, which it defaults to when plugged in with Android Auto. I have researched this extensively and found it's a limitation for whatever reason. Also odd that I can't find any recent topics on it. The newest discussions are from 2019 to mid 2020.
I have tried disabling USB audio routing in Developer Settings to no avail. My solution is to use the EQ settings on Rocket Player to compensate, and it helps...but it's not the same as V4A.
However, I read somewhere that Android 12 "fixed" this issue. Or perhaps I misunderstood what I read. Any any case, can anyone on Android 12 using V4A and Android Auto confirm if audio is processed with V4A while connected to AA? FWIW, I have a PIxel 4a 5G and have been putting off the upgrade to 12 (hate setting up phones) but if A12 will "fix" this issue I will bite the bullet.
Thanks!
I don't know if I'm in the real place, I'm really new here(about posting something)
So I got an a51 from my brother, it was rebooting constantly and wouldn't play or record audio. I tried a bunch of things that will be listed further. But you know now what I know. I can't tell when it started, the phone is kinda old. And that's what I got. Audio wouldn't play, I started to focus on that first. Weirdly enough when I first flashed stock firmware, audio was working just fine, until it rebooted by itself. Also, after that, I noticed build.prop was missing almost everything, including USB mtp settings, audio codecs, just quite literally enough to boot phone. I tried to change it for some fota.zip that came in ap with stock firm, no luck tho. If you think that's the problem, can you help me find a stock and not installation build.prop or idk?
It recognizes if the one connected is a headset, or a Bluetooth, or even the phone's speaker, but nothing. If I try to play an audio file it says the format is unsupported, and any application that uses microphone or audio output will prompt an error.
I've tried:
...Flashing custom audio (drivers? Idk, it was v4a and james)
....Changing the entire sub board, or whatever it's called in English
...changing settings
...nand option in Odin
...downgrading to android 11 and 10
Device:
...android 11 (it came as android 12)
...sm-a515f/t
...carrier: zto
I thank you since now sz