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!!
Searched for this problem but couldn't find anything directly related. Is there an advanced search option on the forum?
I just got a Samsung S2 LTE/Skyrocket on the Rogers network here in Canada and love the phone so far. Only problem is when I have the phone in the car, the Bluetooth connects properly when I fire the car up, but it disconnects after a short period of time (2-4 minutes)...then it may reconnect on its own...then disconnects minutes later.
The car is a 2008 Audi RS4 which is basically the same bluetooth system used on the more popular A4, (2005-2008) so hopefully someone else has some input.
Initial thoughts
1. phone software - Maybe the phone needs a software update - this exact scenario happened on a blackberry I had a few years ago and updating the blackberry's system software fixed the issue. There is no 'firmware update' possible for the car for the record. The phone is running GingerBread 2.3.5
2. bluetooth/sleep/battery saver settings - as I've only had an Android for about 5 minutes, this is likely where I'm missing something. Is there a setting on the phone that puts bluetooth to sleep to save battery power? I've not downloaded any apps to interfere with power management yet etc. so I'm just on OEM settings.
Any thoughts would be appreciated!
This is more of a development forum than anything, so most of the folks are running custom ROM's here. But you'll still find knowledgeable folks when it comes to stock ROM.
I would try going to settings and at the bottom of the menu is a software update option. Some folks are getting 2.3.6 rolled out to them so it couldn't hurt to check and see if it's available for you right now.
Otherwise, you might try un-pairing the bluetooth connection, reboot and then try making a new pair?
Good luck.
To OP, sorry I don't have a solution for you. But I gotta tell ya, the bluetooth on this phone is pretty crappy, I'm hoping the ICS will fix a lot of Bluetooth bugs. I have an issue connecting with my Bluetooth Music Reciever (which is plugged into the AUX). I have a 2008 MB C300 and the Bluetooth wors about 95% of the time.
By the way Nice ride. RS4, same engine as the Audi R8.
Jamolah said:
To OP, sorry I don't have a solution for you. But I gotta tell ya, the bluetooth on this phone is pretty crappy, I'm hoping the ICS will fix a lot of Bluetooth bugs. I have an issue connecting with my Bluetooth Music Reciever (which is plugged into the AUX). I have a 2008 MB C300 and the Bluetooth wors about 95% of the time.
By the way Nice ride. RS4, same engine as the Audi R8.
Click to expand...
Click to collapse
thanks for nothing guys. this place sucks
just messing. Sorry, I didn't quite grasp that this was the premier developer forum vs. users shooting the **** about their phones. A buddy referred me over here when I told him about the problem.
Yeah, I've heard a few complaints about the bluetooth similar to yours Jamolah. Some guys complain that it only connects once in a while, so 95% of the time is pretty good! Mine connects right away every time which is nice...but the constant disconnect/connect/disconnect routine gets real old, and results in me turning bluetooth off. Unfortunately then you have to turn it on to use it etc.
Anyway, I'll keep trying for a solution to my seemingly unique problem and will see about an update to ICS when its available. Quite a different world, the android world (vs. blackberry or iPhone where everything's so closed and limited and simple).
Thanks for the input guys.
Hi,
if you keep your android running with the navigation app (preventing standby) do you still experience disconnects? If this helps you can try my app "BluetoothKeepalive" from the market, it automatically prevents android standby when being connected via bluetooth.
Regards
...Alex
I am pleased to report that the phone now works flawlessly with my Audi's bluetooth.
The solution? Ice Cream Sandwich / 4.0, the latest operating system available for my phone.
I upgraded the phone to ICS, and it immediately began co-operating with the bluetooth.
I recently upgrade to cleanrom 6 and then to hyperdrive 8.1, both have given me some issues with a bunch of features.
Im now back to running cleanrom 5.6 since it fixed 95% of the issues.
The only problem thats still persistent is the bluetooth headset not connecting automatically.
The cars bluetooth was giving me an issue with the other roms but someone advised me to change the build prop to false or true.
That seemed to fix the issue in the car but whenever i turn on the bluetooth headset it asks me if i want to connect it.
Does anyone have a fix for this?
I get extremely bad performance (bad, choppy fps, stuttering sound) when I have my bluetooth headset paired to the Shield while running stuff like retroarch. Is this an Android issue with bluetooth sound devices or something I'm missing with the settings? The moment I disable passing audio to my headset, everything runs normally again.
My bluetooth headphones did cause my android to crash once reboot (once so far), but other than that they have worked fine. There might be an underlying undiscovered bluetooth audio bug. Hopefully some more folks will chime in here.
metzroth said:
My bluetooth headphones did cause my android to crash once reboot (once so far), but other than that they have worked fine. There might be an underlying undiscovered bluetooth audio bug. Hopefully some more folks will chime in here.
Click to expand...
Click to collapse
Music, movies, stuff that don't stress the hardware seem to work ok. Its when I run emulators like retroarch (or probably anything that makes the Shield work harder) that gives me performance issues. Anyway, I think this is a known android issue since an admin in the retroarch forums confirmed the same thing, as well as some members in the geforce.com shield board. I did notice that this isn't an issue when I tried my headphones on my sister's nexus 7 2013 tablet, which is running android 4.4.2. Maybe kitkat addresses this (but I think I've been seeing bluetooth fixes in changelogs for multiple android firmwares now so I don't know)?
I've paired my pixel 2 with my uconnect system in my Jeep. Two issues, 1 the metadata (song titles and track info) doesn't show on the screen in my car. This worked fine on my last several phones. I've tried deleting and pairing again but it doesn't help. 2, the navigation directions from Google maps do not come through my car's speakers despite having that option checked in gmaps settings. Anyone having similar problems and figured out a fix? I'm on 8.1 Dev preview, and this also did not work on 8.0. I can't imagine that the phone isn't capable.
It appears there are lots of issues with Bluetooth on the Pixel 2s but no fixes that I can find. Hopefully Google will fix these soon as it's very frustrating getting a new very expensive phone which doesn't even do what you're old one did.
Sent from my Pixel 2 using Tapatalk
pabarker said:
It appears there are lots of issues with Bluetooth on the Pixel 2s but no fixes that I can find. Hopefully Google will fix these soon as it's very frustrating getting a new very expensive phone which doesn't even do what you're old one did.
Sent from my Pixel 2 using Tapatalk
Click to expand...
Click to collapse
Terrible, hope they fix it soon. Thought maybe 8.1 would help but no luck.
I feel sorry for you guys. OG Pixel had bluetooth issues on some cars and some of those issues are still not fixed 1 year later.
Bluetooth is great for me on my cars. Both newer GM vehicles. One with Android Auto, one without.
I have an SRT Hellcat with UConnect. It completely does the same type of stuff. Sometimes it fails to transfer calls. It also shows "Pixel 2" often rather than song titles, etc. If I disconnect BLE and reconnect it usually works better the second time. It is annoying.
How do they screw this up every year. Using play music now completely locks up my uconnect RHR radio. I really wish Google would test things before rolling out. I wish they would just release there new phones on the previous Android version and have a beta of the current since they always screw something major up.
---------- Post added at 04:53 AM ---------- Previous post was at 04:17 AM ----------
I upgraded my uconnect from 2.600 to 2.700 and deleted the device pairing a couple of times and now I can at least play media again although I no longer have song data displaying which was there before at least before my radio would lock up.
I also tried changing the Bluetooth codec via developer settings to ACC. However, after changing, it reverts on its own. I read that the November security patch supposedly contains some BT fixes, fingers crossed!
On my car (BMW 335i from 2008) the Bluetooth is so messed up that while I can pair the Pixel 2, if I actually play any audio it reboots the car's entertainment system and deletes all Bluetooth pairings.
The 8.1 beta doesn't fix the problem, either, so I'm not too hopeful about the next patch.
fishsupreme said:
On my car (BMW 335i from 2008) the Bluetooth is so messed up that while I can pair the Pixel 2, if I actually play any audio it reboots the car's entertainment system and deletes all Bluetooth pairings.
The 8.1 beta doesn't fix the problem, either, so I'm not too hopeful about the next patch.
Click to expand...
Click to collapse
Interestingly, I found a fix for my Bluetooth issue at least. In Android 8.1, they added the ability to set the AVRCP version back to 1.3 in Developer Options. (8.0 moved the default up to 1.4 and in 8.0 there was actually no option to set it below 1.4) Setting AVRCP 1.3 and the SBC audio codec fixed my vehicle Bluetooth issues.
Hmm didnt know of bluetooth issues. So mine paired but wont connect to my 2012 mazdaspeed3, but my aftermarket headunit in my 89 ram50 connects right up and has no issues. (Also connects right to my garmin 2589 and allows all functions including traffic reports)
I just assumed it was something bugging with the radio in my mazda since its always seemed a little weird with bluetooth
---------- Post added at 03:24 PM ---------- Previous post was at 03:23 PM ----------
Hmm didnt know of bluetooth issues. So mine paired but wont connect to my 2012 mazdaspeed3, but my aftermarket headunit in my 89 ram50 connects right up and has no issues. (Also connects right to my garmin 2589 and allows all functions including traffic reports)
I just assumed it was something bugging with the radio in my mazda since its always seemed a little weird with bluetooth
fishsupreme said:
Interestingly, I found a fix for my Bluetooth issue at least. In Android 8.1, they added the ability to set the AVRCP version back to 1.3 in Developer Options. (8.0 moved the default up to 1.4 and in 8.0 there was actually no option to set it below 1.4) Setting AVRCP 1.3 and the SBC audio codec fixed my vehicle Bluetooth issues.
Click to expand...
Click to collapse
Tried this but the codec keeps reverting to system default. The AVRCP version however will stay on 1.3. Still waiting for the November security patch with hopes that it will cure this all.
Not just with vehicles
760hacker said:
Tried this but the codec keeps reverting to system default. The AVRCP version however will stay on 1.3. Still waiting for the November security patch with hopes that it will cure this all.
Click to expand...
Click to collapse
Hello team,
I have seen similer problems with one of my Pixel 2's when using a simple Bluetooth device which may suggest that this goes beyond just vehicles. I tried turning on and off both the phone and device and ended up having to delete the connection profile and starting over.
The device would only partially handshake during the connection process and then hang which appears to be what's happening with the vehicle systems.
I thought I'd should mention this here as an FYI.
phonefreedom said:
Hello team,
I have seen similer problems with one of my Pixel 2's when using a simple Bluetooth device which may suggest that this goes beyond just vehicles. I tried turning on and off both the phone and device and ended up having to delete the connection profile and starting over.
The device would only partially handshake during the connection process and then hang which appears to be what's happening with the vehicle systems.
I thought I'd should mention this here as an FYI.
Click to expand...
Click to collapse
This is similar to what I see, both with my new Pixel2 and also my previous OnePlus3 on my Mazda 3. Phone will pair, but after a few seconds (or sometimes minutes) disconnect. Usually it will try to reconnect, and then be fine until the next time I use my car. Both phones behave identically, so it seems to be more a problem with vehicle systems that some phones (none I've owned unfortunately!) are more forgiving of.
Anyone know of a fix for this? I'm using uconnect and same issue, however my maps navigation does play over Bluetooth. Sometimes it seems to disconnect or mute after songs change, and the metadata issue is there. Super annoying that we go backwards in technology. My HTC M9 does this stuff flawlessly.
So I did the developer preview thing and set it back to 1.3 which helps the metadata issue. However, the music still pauses every once in a while, mostly between songs. I have to click to my AM/FM radio and back to bluetooth to fix that.
Well, it's always the same circle. There's a new device with a brand new Android version. Of course buggy a.f. They fix it over the time. The device works perfect. And then... a new major upgrade, which is buggy again.
7.1.2 worked perfect on my Pixel. Then came 8.0.
Bluetooth was messed up again. Now i use the Pixel 2, which is a great phone. But still has the complete bandwidth of bugs that were present in 8.0 on the Pixel 1.
Nice to have monthly patches. But instead of fixing so called security issues, they should focus on functionality bug fixes instead. Who has had a major security issue with hs phone at all, yet??
Google is like: "Fix: Someone could attack your phone using a backdoor in your bluetooth driver."
WTF?!
I can't even use my bluetooth to listen to audio correctly! Fix that first!
Long story short:
Yes, I have the same issue with meta-data in my car audio (Pioneer AVH-X2800BT). Sometimes it works. Sometimes it doesn't.
Just got November security patch which is supposed to include Bluetooth fixes but hasn't changed anything.
Sent from my Pixel 2 using Tapatalk
I'm on Nov update and I don't see AVRCP 1.3 anymore. Lowest is 1.4.
Haven't had to use BT (didn't drive the last 2 days) since the update but before that I had no issues with it linking to my wife's CX9 or my ancient 3-series. Calls work just fine and track information shows up accurate on the CX9.
scoliosis said:
I'm on Nov update and I don't see AVRCP 1.3 anymore. Lowest is 1.4.
Haven't had to use BT (didn't drive the last 2 days) since the update but before that I had no issues with it linking to my wife's CX9 or my ancient 3-series. Calls work just fine and track information shows up accurate on the CX9.
Click to expand...
Click to collapse
AVRCP 1.3 wasn't available in stock 8.0 either -- I had to put the 8.1 Developer Preview on to unlock it.
What is your Uconnect firmware version?
> the metadata (song titles and track info) doesn't show on the screen in my car
Mine does unless I'm running Android Auto