I bought a set of motorola s305 bluetooth headphones. I've tried a few different audio programs to see if it was maybe the playback prog. What I've seen is that if i keep the phone in my pocket ~2feet distance the audio skips in and out almost like one of those old CD players. If I hold the phone in my hand and keep it within about 18 inches it seems to be fine. Any suggestions or if it is possibly the headphones or if switching to one of hte nightly rom builds might fix this.
Related
I'm looking at buying a new car and I tried playing music through a couple 2010 Toyota non-navigation radios. All the Android music/video players I tried would sound great for the first few seconds and then start a subtle warble/echo that continues until you pause/resume or switch tracks.
I've got an ADP1 currently running Cyanogen 4.2.11.1, but I saw the same problem with 4.2.9 and 1.6 (don't know about all the other various builds). I have several A2DP headsets and they always work fine (no warble).
I believe this Toyota radio is running Symbian OS from what I found on the web; and I'm going to try to see if Toyota has a software upgrade tomorrow. (I doubt it) Toyota does mention that most Bluetooth features are supported for the MyTouch, but doesn't mention A2DP either way. http://toyota.letstalk.com/brands/toyota-bt/home.htm
I'm downloading the whole Cyanogen tree and preparing to build it and then sniff through the code for buffer sizes and other likely suspects.
I just thought I'd pop this on XDA and see if anyone else has seen the same problem and found a solution.
Or does anyone know specifically where to look in the source to adjust buffer sizes and other things that might cause a warble with Bluetooth audio.
You should test before getting the car, ask the dealer if you can test the BT with the car when you get there.
I have been running A2DP on my Sony headunit for some time now. I have never experienced a warble on any of the roms I have used. I do get another issue however and maybe they are related. I can not stream stereo audio over BT to any device it seems, IF I also have my phones wifi enabled. As stated I do not get a warble, I get an audio drop for a few seconds every 30secs or so. This does not seem to happen if the headset is the only part connect, as soon as I connect the A2DP portions it starts up. Disabling wifi is my work around at present.
I have tried A2DP with/without WIFI enabled. No difference; still warbles.
Nothing interesting shows up in logcat.
I run A2DP through my ford focus with the microsoft sync system with no issues. Although the AVCRP does have issues. The control won't work after the phone goes to sleep.
The warble or echo may be due to an active system used to reduce road noise when using the phone hands free via bluetooth. Might check and see if there is a way of turning that off. Some of the foreign cars have active mics placed in the car that might cause this.
try an eclair rom (like manup456's 1.3)
BLUETOOTH IS IMPECCABLE ON THESE ROMS
it will work.
I tried turning off/on the auto volume; no help.
I'm not sure how to check/disable any bluetooth feedback; but it doesn't sound like that.
My friends Blackberry either worked fine (no warble) or was very very jerky (played quarter second, cut out a half second). And split its time about 50/50 between these modes.
I should mention the "warble" is not very pronounced, I can listen to most music without it making me crazy; but it bugs me.
Finally got all the stuff from git; now compiling the kernel.
I will try the compiled kernel tonight and if no luck there I may try the eclair rom mentioned; but I thought Steve's build already had most of the eclair stuff; maybe he is waiting on his experimental branch.
Edit:
oops, looks like a2dp stuff is not in the kernel....
I run A2DP on my kenwood deck. The only issue I experience is if I turn off the car and kill the stereo before killing my BT on my phone, my phone goes into freak out mode. I can't enable or disable BT untill I give a 3 finger salute and it just runs really slow. No warble, actually from CM 4.2.11.1 it sounds pretty damn decent.
I'm still trying to figure out how to compile the code from git; got the kernel and main tree compiled; but not the external apps (like a2dp).
Toyota gave me phone #s for Panasonic and somebody else who make the head units. So I am still pursuing a software update from that end as well. I'll call them next week after the holidays.
I've read thru the liba2dp.c code and have a couple ideas to try if I can figure out how to compile it (haven't really tried that hard, just looking for the official directions so I don't waste hours on something that is already known)
dude your doing too much work just try the eclair rom!!
I paired my phone with my car's bluetooth radio and noticed the following behavior:
- If I turn on my car radio and then turn bluetooth on on my One X, it will auto connect and start playing music.
- If I turn on bluetooth on my One X, get in my car and turn on the radio, my One X will not auto-connect. I have to go into the bluetooth settings screen and select my car's device name (CAR M_MEDIA) and then it connects and starts playing music.
I can turn on and off my One X's bluetooth repeatedly while in the car and it will connect each time, but it doesn't ever connect if I turn on and off the car's radio.
I tried a bunch of roms, including Stock, CleanROM and others in the development forum and finally I tried CM10. They all behave the exact same way.
Seeing that CM10 also has the issue caused me to give up and come here for help, because my Atrix 4G with CM9 never had this issue. I might try CM9 on my One X as a last resort.
Any help on this one?
What model/year car, and is it a manufacturer stereo, or a 3rd party head unit? Every stereo head unit and phone is a bit different, and some combinations simply don't play well together.
I have had the same issue with my 2012 Subaru Impreza, with factory stereo (non-nav version). Tried any of a variety of things (different ROMs, editing some of the BT config files), and nothing worked. Also have the issue that even when i manually connect it, it doesn't connect maybe 20% of the time. And when it does, the steering wheel controls to change the music track only works maybe half the time.
I called HTC support, had to escalate the issue to get anyone to listen to me, and they tried the usual (update phone firmware, safe mode) with no luck (not surprising). They said all they could do was log the issue, and hope that it gets addressed in a future update. Probably the most you can do is call HTC also, so they at least start to get the message that its a known issue. The HTC tech also mentioned it may be a feature that is disabled on purpose, due to a known security issue.
I think its a fault of the BT stack, which is HTC proprietary. On my old HTC Desire Z, newer versions of Sense seemed to work better with my car stereo BT. Unfortunately, with the One X, it seems they have taken a step backward. I also noticed on my old DZ that AOSP based ROMs worked better with my car stereo BT, and also displayed the track info (artist, title, etc) on my car stereo which is something that the HTC Bluetooth stack never does. So I assume it was a different non-HTC Bluetooth stack. So therefore, like you, I thought an AOSP ROM might fix the problem. I tried AOKP (ICS) but not CM9, and AOKP didn't help. Not being a dev, I'm not sure where the BT stack comes from in AOSP ROMs. On AOKP, the track info was not displayed on my car stereo, and the config files were the same as HTC stock, leading me to believe it was the HTC stack. Maybe somebody with more knowledge can shed some light on the matter of AOSP ROMs and the Bluetooth stack, as I've been wondering this.
My car is a 2011 Subaru Impreza. Coincidence? Probably not. I know the car does something different than my other Bluetooth headset because music starts when it connects to the car but not when it connects to my headset. I have to press play on my headset for the music to launch.
Also the headset auto connects reliably to my One X, no matter which one I turn on first, unlike my car. Perhaps a hint is there? Maybe some logs would shed some light on the problem?
Edit: just tried CM9, same result. I never did logcat so I'm not sure if that would help, would it?
Hello there!
Recently I have encountered a strange issue with the wired headphone stereo balance. The volume on the left side is as expected, but audio on the right channel is all but inaudible. It´s there, but extremely quiet. If I set the volume to maximum, audio on the right ramps up to being listenable (with what would usually be a low to low medium volume setting)...while the left is blazing like crazy, of course.
Using a stereo test MP3 (ping pong sounds, basically), I could verify that the channel seperation is correct, just to rule out that it´s a headphone jack/plug problem (i.e. the plug making no contact with the correct connectors inside the jack). Or, to put it simply, both audio channels do indeed get to the correct side of the headphone, just not enough on the one side.
I have no idea what could have caused this. Stereo balance was definitly working correctly the one time I tried wired headphones on the stock ASUS ROM, way back before I unlocked, rooted and installed custom ROMs. I haven´t tried it since, until a couple of days ago and that´s when I noticed.
Things I´ve tried since then:
- Dozens of different headphones, headsets, adapter cables. All show the same problem.
- Tried to clean out the headphone jack as best as possible.
- I even filed down the tip of one plug a bit to maybe get a better connection, but the connection itself doesn´t seem to be the problem.
- Factory resets, full wipes, different ROMs (stock, CM, CROMi).
- Different audio DSPs.
- A LOT of audio related apps (Volume+, EQs...)
- Audio players with built in balance control. These do indeed shift the stereo image to the right side, but don´t make the right channel itself louder, which results in a very quiet, kinda mono-y, hollow-y sound at normal volume levels.
I am assuming there is a hardware problem, and I assume it´s not the headphone jack itself, but something else in the circuitry.
I really, really, really don´t want to RMA the thing, since it took me *weeks* of discussion with ASUS support to get it unlocked in the first place (wasn´t able to, due to the infamous MAC/server mismatch thingie), and I don´t want to get it back with a new mainboard and perma-locked.
So, my questions are: What else can I try? Is there a way to boost the one faulty audio channel? Maybe by editing some system file or writing a script or something?
I´m unlocked, rooted and running CROMi-X 4.3b4 now (which is going to be great, once it matures, btw).
Thanks!
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
Anyone else finding that the Bluetooth audio can be a bit hit and miss, the audio has just fully cut out on me, but it displays as if it's still connected and playing via the headphones. I had no audio through either headphones, switching BT off and on, and rebooting headsets didn't solve it. Rebooting the phone brought the audio back, phew!
Out of the two headsets I have, My cheap Sony WI-C310's seem to work better, Using my jabra halo smart headset, it doesn't seem to connect media audio if it's also allowed to handle calls. I have to toggle calls off and just media to use Spotify with the headset (this could just be that headset being weird, think it got discontinued for not being great)
Anyone else having BT audio issues?
I've got a Huawei smart band 6 connected at the same time if that's a factor, it wasn't a problem on my original Nord though.
I have been facing the same issue for a while now, it's pretty random. There are times where it works perfectly and other times it either doesn't connect at all, or has a very weird delay, where it's fine in the beginning of say a video and gets a delay mid way through it. There are times where it only connects to one earphone, just issues all around. Also am using the oneplus buds z2, so honestly would expect it to work flawlessly with a oneplus device. The earphones work fine with other devices.
I've been getting random drop outs.
Both with connectivity with my car infotainment system and my cycle computer.
When I had my OP7Pro, never experienced anything of the sort when connected to these two same devices.
I've also tried enabling Bluetooth Gabeldorsche in the developer settings, and that didn't make a difference.
Will try changing the Bluetooth AVRCP version to see if that improves anything (currently set to the default of 1.5).
Has anyone else played with those settings and tested the impact?
Tested with 3-4 Bluetooth devices and no drop outs.
I notice that when I put the device in aereo mode the Bluetooth remain active, but in the latest days this problem doesn't happen anymore, maybe was a bug of the first fw, and after last update they have fixed?