I recently purchased a Volvo and for whatever reason, I can't stream audio from my Evo. Syncing the phone book and making calls work fine, but whenever I try to switch the input to the Bluetooth and play music from the phone, it refuses to work.
The streaming did work the first time I connected my phone to the car, but after that it does not. I have also tried re-pairing the phone to the car and ensuring that the settings allow both streaming and phone control.
My Evo is running the following setup:
ROM: CM 7.0.3.1
KERNEL: Tiamat 4.0.1 sbc+
Hardware: 0004
Any ideas would be great!
Try another kernel, I had a kings kernel that did the same thing with my mazda, switched to another and everything worked fine. I was using sense based roms so YMMV
Is this a factory installed Bluetooth system? What year an model of Volvo?
I created an app just for Blueotooth in the car. I have also installed many aftermarket Bluetooth systems for handsfree and A2DP. My app is free, open source, and no ads. It is available on Android Market. Just search A2DP Volume. The open source project is on Google Code. I would post the links but I am a noob ;(
It may not fix all your issues but once you do get Bluetooth working, it really helps out.
Related
I'm thinking of upgrading to this phone, one of the main reasons is that my current device, which has galaxy S guts, is not compatible with most bluetooth devices. I like to use an app called blueputdroid that turns my phone into a universal keyboard as well as an ELM bluetooth device that turns my phone into a dyno along with the torque app for my car.
For some reason the way samsung built the bluetooth makes it not work with a lot of these things, I know it's not the apps or 3rd party devices as I use my old G1 now for it, but would much rather just have my main phone be my one device.
Have any of you tested blueputdroid or any bluetooth devices? If not could someone try out blueputdroid with this phone (it's free in the market) any help would be much appreciated thanx!!
Says it has detected unsupported Bluetooth stack.. Install cyanogen Rom, etc.
Thanks, at least this phone is likely to get cyanogenmod support which will fix the problem my SK sure as hell won't
My GS2 works perfect with my ELM adapter. It worked perfect with my Vibrant too. I've never had a single problem with any bluetooth device on either of them.
I've had a lot of bluetooth problems with both my vibrant and now my GS2. Both work reliably with my wife's mini cooper bluetooth but they both have had problems connecting to the garmin nuvi I use for handsfree in my car (and forget about the A2DP on it).
I tried a lot of roms on my vibrant (incl stock) and they did lots of cool stuff but never made the BT connect reliably. Then I came across this thread: http://forum.xda-developers.com/showthread.php?t=795691
I made the suggested change to /system/etc/bluetooth/audio.conf and voila! I finally have good BT with my vibrant.
So I got my SG2 last week, rooted it and found that it also had the bad settings in /system/etc/bluetooth/audio.conf. However it also lacked BLN (backlight notification) and few other tweaks I've come to love on my vibrant so I flashed juggernaut 2.6. That fixed all the major foibles with the SG2 but it still won't reliably connect to my garmin.
I opened up the filesystem to find that /system/etc/bluetooth/audio.conf is no longer there! Does anyone know where it went?
Apparently I don't have enough posts to ask in the dev forum where juggernaut was posted http://forum.xda-developers.com/showthread.php?t=1322642 so I'm hoping someone will see this plee for help.
thanks
the phone has BT 3.0, but it is backward compatible with BT 2.0 and 1.0 devices
i haven't had any trouble using it with my car deck (streaming audio & phone), my large collection of stereo BT devices, and other BT enabled phones & PCs/Laptops
the remote control feature from the stereo headsets works properly, for fast forward, backward, play, pause, talk, mute, etc
the only thing i have yet need to test BT on is with a BT smart wrist watch
I've tried to connect my phone via BT to two different cars and have no luck. It will scan for devices but won't find them at all. Does this happen to anyone else with the SIII? Strangely enough, it finds and connects to my JamBox is just fine.
What ROM are u on ? Stock or rooted?
What kind of cars I know my Audi A8 will connect but I always have to connect manually and enter the 1234 paswrd.
Sent from my SAMSUNG-SGH-I747 using xda premium
bbgt2 said:
What ROM are u on ? Stock or rooted?
What kind of cars I know my Audi A8 will connect but I always have to connect manually and enter the 1234 paswrd.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Still rocking the stock and unrooted for the phone. I tried on a Lexus GS and a Scion xB but no results show up. How do you connect manually? I should try that
Phone calls and bluetooth streaming works fine in my 2009 Mazda 6 (GT, no navigation). My phone is stock + root.
I use Slacker Radio everyday, launched by Automateit Pro when the connection to my car is established.
IIRC, I had to input a PIN on my phone, then in my car to do the pairing, and after that, I had to connect the phone manually to the stereo, but only once. After that, it's automatic when I start the car. Watch out for the "Only visible to paired devices" setting on your phone. It must not be checked.
I too have major issues with bluetooth, my phone connects whenever it feels like. I had to flash to cm9 to be able to listen to music in my G37. No problems in my other car (it has aftermaket pioneer system).
PS Just flashed the CM10 since they finally figured out A2DP, but the image is broken. (Note to myself: "Read the thread before flashing") Will wait for the next nightly build.
Nissan's always had a horrid BT stack in it. I'm in an 09 Altima and BT just sucks. I know it's not the phone as I've tried multiple phones from multiple vendors and they all suck. Nissan won't fix it either.
[Q] Bluetooth issue with Cars
I have AKOP Rom and KT Kernel. My bluetooth connectin to Mazda Cx-5 is fine. However, the problem I have is a lot of phone information (Song title, Battery Status) I used to have on stock, now are gone. Previously, I can fast foward or Rewind a song, also, once BT is connected, the default music player will start automatically
Can someone suggest a BT manager app which can change and enhance BT setting?
I have a 2009 Mercedes B200. My phone connects to the car just fine, but no sound comes from the speakers and no sound goes into the microphone. Same thing with my car and the HTC One X, although that was fixed with a stock ROM update. Bluetooth on cars can be very hit and miss.
I bought an Alpine CDE-HD137BT headunit for its Pandora functionality. However, I learned you need to have an AVRCP 1.3 supported ROM to use the BT Pandora source versus the less functional BT Audio source. So I found Codename Android and flashed it, but that didn't completely solve my problem.
Here is the situation:
If my radio is on the BT Pandora source and I launch Pandora the radio will read "No Pandora". The only way to get it to connect to Pandora is to
1. Start Vehicle (it is in BT Pandora mode)
2. Launch Pandora App (it will start playing but no audio will come out the radio)
3. Cycle through all the options back to BT Pandora.
4. Let it connect and enjoy.
Does anyone have any experience with this?
Edit: I tried to connect straight from the BT Pandora on an Incredible 2 and it worked. I'll test another ROM.
Alpine bluetooth
Hey, just ran across your post. Did you ever find a fix to the problem?
I have the same issue on my nexus 4. Bluetooth for automotive is checked in Pandora
so... I think I've narrowed down my issues with newer ROMs coming out and my bluetooth not working in the car anymore. just a little background information,
- 2011 Toyota Camry SE w/ JBL Audio
- Verizon Galaxy Nexus using various ROMs
prior to any newer releases, I would use voice/audio over bluetooth, ran great without a problem. I didn't get metadata on screen but was ok. pandora, spotify, notification sounds, google music, etc... worked like a charm.
well... now I noticed that only voice calls & google music work over bluetooth connection in the car. I thought this was first an issue with pairing the device to the car, so I deleted all the profiles in the car and redid connection on phone. I still couldn't get sound out of any other media application i.e.; pandora, youtube, notifcations, spotify, etc... I could only get google music to work correctly. the apps not working look like they are playing, I turn off bluetooth on phone and it continues playing, but when bluetooth is on I hear nothing.
so after researching, I see that majority of new releases include AVRCP 1.3 which pushes metadata to the displays. I noticed this now works with google music, but I can't for the life of me figure out how to get other media services working properly. I've researched on RW, Google, other Android forums and can see some have similar issues, but the thread soon dies. [/background]
can anyone tell me if I can use an updated ROM with AVRCP 1.0 instead of AVRCP 1.3 to test? does anyone have suggestions I could try to get other media services working? thanks!
RBalber said:
so... I think I've narrowed down my issues with newer ROMs coming out and my bluetooth not working in the car anymore. just a little background information,
- 2011 Toyota Camry SE w/ JBL Audio
- Verizon Galaxy Nexus using various ROMs
prior to any newer releases, I would use voice/audio over bluetooth, ran great without a problem. I didn't get metadata on screen but was ok. pandora, spotify, notification sounds, google music, etc... worked like a charm.
well... now I noticed that only voice calls & google music work over bluetooth connection in the car. I thought this was first an issue with pairing the device to the car, so I deleted all the profiles in the car and redid connection on phone. I still couldn't get sound out of any other media application i.e.; pandora, youtube, notifcations, spotify, etc... I could only get google music to work correctly. the apps not working look like they are playing, I turn off bluetooth on phone and it continues playing, but when bluetooth is on I hear nothing.
so after researching, I see that majority of new releases include AVRCP 1.3 which pushes metadata to the displays. I noticed this now works with google music, but I can't for the life of me figure out how to get other media services working properly. I've researched on RW, Google, other Android forums and can see some have similar issues, but the thread soon dies. [/background]
can anyone tell me if I can use an updated ROM with AVRCP 1.0 instead of AVRCP 1.3 to test? does anyone have suggestions I could try to get other media services working? thanks!
Click to expand...
Click to collapse
I think it's AVRCP 1.3 in CM 10 based roms that breaks this. I just switched to jelly belly 9 (4.1.2) which rolled back bluetooth profiles back to AVRCP 1.0 and pandora etc. works but without media info obviously. I also saw a AVRCP 1.3 patch for Pandora somewhere that may make it work. It's possible that the problem isn't that the ROM is not compatible, but that the Apps aren't.
osurferx said:
I think it's AVRCP 1.3 in CM 10 based roms that breaks this. I just switched to jelly belly 9 (4.1.2) which rolled back bluetooth profiles back to AVRCP 1.0 and pandora etc. works but without media info obviously. I also saw a AVRCP 1.3 patch for Pandora somewhere that may make it work. It's possible that the problem isn't that the ROM is not compatible, but that the Apps aren't.
Click to expand...
Click to collapse
Ok... I've confirmed it has to be AVRCP 1.3
Last night I took advice. I installed Jelly Belly 9 "4.1.2" w/ reverted AVRCP 1.0 because of BT issues, and this morning I went to work, tested connection with BT and everything worked! So... Looks like the issue lies with AVRCP 1.3. I don't see metadata on screen anymore but it doesn't bother me, I'd rather have all other media players working.
To touch on what others are saying, statements Google Music works perfectly fine with AVRCP 1.3 based ROM's as well as voice through BT. It's just the other media players i.e; pandora, slacker, youtube, notifications, etc.... that don't work. I'm guessing from what I read, is that the applications do not support AVRCP 1.3 and will not push to Toyota head units properly. Not sure if this is going to get fixed or not, but sucks because this limits what I can/can't use for ROMs at least a solution was found and reason why. Thanks bud!
You could also try https://github.com/loganakamatsu/PandoraAVRCP for the Pandora patch. Maybe patches exist for other apps as well...
I read on another thread that any app that supports the Scrobble Droid API hxxp://code.google.com/p/scrobbledroid/wiki/DeveloperAPI will pass the meta info to AVRCP. So I assume if you install ScrobbleDroid app hxxps://play.google.com/store/apps/details?id=net.jjc1138.android.scrobbler&hl=en from the play store any app that it is compatible with will also pass the meta info to the display.
As noted, Pandora is not supported as it does not broadcast its intents. I personally had issues getting the PandoraAVRCP github to patch. If anyone has a patched pandora.apk, I would certainly appreciate a PM.
Good luck.
Hello there. I've been experiencing a problem with my OP3, regarding the BT connection to my car stereo.
I recently bought a new head unit for my car, a Pioneer MVH-X580BT unit, it Works fine. However, when i connect my phone to it, it allows me to playback áudio, but i won't allow me to use it for hands-free calling. The Bluetooth menu on the phone says "MVH-X580BT - Connected (no phone)". It happens with any CM-based rom that i've tried so far.
However, when i install a stock rom (Oxygen OS, Freedom OS also works), it works just fine, both audio and phone mode.
Is there something in custom roms that changes some sort of parameters in the ROM that makes the phone refuse a phone mode connection from the radio?
Any tips i can use?
Thanks!
logcat of the incident:
Here.
Hope it helps.
I've had the same problems. It's an issue with the LOS BT stack. I've created several unofficial versions of my favorite ROMs using a different BT stack that fixes this problem for me. Let me know if they work.