I have the Motorolla S9 bluetooth A2DP stereo headset.
I also have the Hero currently running VillainROM 3.4 but I've been trying to run a bt connection for A2DP media playback with almost all Android 2.1 ROMS with same results.
The phone pairs fine but once I start playing any mp3 headset disconnects and reconnects at random.
I should mention that bluetooth works great in my car with the stock stereo system for simple phone calls.
I searched the entire forum but couldn't find anyone else with this issue ... Modaco 3.1 people report bt stereo playback to be working fine .. I think this is a 2.1 issue as VillainROM 3.3 and 3.4 and BeHero and other 2.1 based roms have this issue.
please HELP
Hello rafynet
i had same problem and i have solved with this method:
your phone must be rooted
there is a file in /etc/bluez/audio.conf
copy that to your pc.Change the lines
from
-----------------------------
Enable=Source,Control,Sink
Disable=Headset,Gateway
-----------------------------
to
-----------------------------
Enable=
Disable=Headset,Gateway,Source,Control,Sink
-------------------------------------------
save it.
copy the changed file back to /etc/bluez/
I have tried this solution in all rom that i have tested and all work well for me, watch the entire article:
Issue 3960: Bluetooth issues with car systems in Android 1.5 / 1.6
I'm sorry, i can't post this link on forum!!
search it in google.
sorry for my english!
I'm waiting your feedback!!
I hope this solution works well for you. Try this!
your solution helped a little bit ... but bluetooth connection still drops and re-connects all the time ... it's very annoying.
I'm fairly sure this will be fixed when we get the official Hero 2.1 update.
I had noticed the same thing with my Motorola T505 ROKR handsfree adapter. Worked fine in 1.5, but in 2.1 it would disconnect every 30 seconds or so, then reconnect.
However... I've just got a new car stereo (Pioneer DEH-P6100BT) and it actually works *BETTER* in VillianROM 4.0 than it did in Modaco 3.2. In Modaco, it would only connect to "phone audio" and not "media audio," and I had to go into the Android settings and enable "media audio" each time I got in my car. With VillainROM, it connects automatically and it doesn't disconnect. Also, I've found that in 2.1, when listening to BT Audio, the music doesn't get interrupted by notification sounds, which I hated about 1.5.
I've had nothing but problem with a2dp on the hero, and it's probably the feature I need to work the most. I tried a whole host of 1.5 and 2.1 roms but none of them would consistantly connect to my pioneer deh-p700bt. I read somewhere that it's been a problem for lots of people since the 2.73.x series of updates, so I downgraded to the T-Mobile 1.76.110.6 stock rom and it's worked perfectly for me ever since! I'll have to stick with that one for now and hope it gets fixed in the upcoming 2.1 update
Hi,
I have a question about this subject :
i have a bluetooth car stereo with phone handfree inclued.
With all ROMs I tried (and a tried a lot...)
the phone handsfree always worked
Depend of the ROM, some items were available or not : (battery indicator or signal level indicator for example)
With only one ROM (and I don't remember which one), I could transfer my contact list from the phone to the car stereo system (with bluetooth).
Does someones knows if this feature will be again available into the next ROM (official or not) ?
Thx
PS : sorry for my bad english
yan74s said:
Hi,
I have a question about this subject :
i have a bluetooth car stereo with phone handfree inclued.
With all ROMs I tried (and a tried a lot...)
the phone handsfree always worked
Depend of the ROM, some items were available or not : (battery indicator or signal level indicator for example)
With only one ROM (and I don't remember which one), I could transfer my contact list from the phone to the car stereo system (with bluetooth).
Does someones knows if this feature will be again available into the next ROM (official or not) ?
Thx
PS : sorry for my bad english
Click to expand...
Click to collapse
The Android SDK did not include a bluetooth API in 1.5, but it is included in 2.1. I would guess we'll see a big improvement with the official 2.1 update.
Related
Hi there,
I have HTC Universal and Dell BH-200 stereo bluetooth headset.
Situation:
- WM5 ROM (for example newest KDSkamal) - after a bit of fiddling A2DP works, also HS profile is working
- WM6 ROM (for example Tomal's 8.5, 8.2) - A2DP works after fiddling, unfortunately HS profile's not working - headset turns itself off after 5-10 second of call, during which nothing can be heard
- WM6 ROM + Broadcomm stack - A2DP works flawlessly, HS doesn't.
From what I know, no WM6 device works correctly with Dell BH-200. It's interesting though, that WM5 devices appear to work. Also, I've read here that Broadcomm stack doesn't support HS profile, so out of luck here.
Now, I was trying to just overwrite WM6 BT stack dll's with ones taken from WM5, but it didn't work either - maybe that's because I was doing it rather randomly, without solid knowledge of the matter.
As I see many skilled hackers here, maybe someone would take his/hers time to help me out a bit and figure what has to be done to have working WM5 BT stack on WM6 device?
So I've done some primitive hacking, here are the results. I've been using files extracted from newest T-Mobile WM5 ROM, on my device there is Tomal's 8.5.
First, I just used every bth* dll file I could find and overwritten ones in Windows folder:
bthutil.dll
bthusb.dll
bthuniv.dll
bthuart.dll
bthsc.dll
bthlink.dll
bthidsvc.dll
bthhid.dll
bthcsr.dll
bthasplugin.dll
bthamb.dll
BthAGPhonebook.dll
btdrt.dll
btd.dll
btagsvc.dll
btagext.dll
After this, Uni wasn't even able to turn on GSM - no idea why.
Then I tried with just
BluetoothSetting.dll
btagsvc.dll
btagext.dll
Much better stereo - it works now, before there were lots of noise; also, headphones no longer switch off when receiving phone call; unfortunately, no handsfree support.
Will try more...
OK, false alarm - just found out that I need to force pairing from the headset (using Play/Pause button) and the A2DP works, even without replacing btag[svc|ext].dll. After this sequence A2DP works, but Handsfree doesn't (but at least it doesn't turn off the headphones)
maybe some reason
i have special infomration ..
I have TOmals ROM and i found this ...
if i will turn first bluetooth on my Uni and then i switch on my headpohones - everything works great. Also in my car parrot works perfect - A2DP and also i HF ...
If i will start bluetooth after bluetooth in car or headphones ... then A2DP makes sound pause ... and HF is not so clearly as usually ...
i dont know why .. but it works like this ...so try to switch BT on pohoen first and thne accesorries and youll see ...
Bye
I tried that, but to no avail.
But now the fun part started: if I extract files from Tomal's ROM nbf, they are in different size that the ones _from the same ROM_, just installed on Uni. Even better, if I overwrite installed ones with extracted ones, radio, SD, camera and so on stops working. I wonder where is connection between SD, camera, USB connection and bluetooth...
Now I replaced only btagext.dll (however, I think that all this replacing effects only in disabling replaced dlls...) and best thing I achieved is that
- A2DP works almost flawlessly with Dell BH200 (if I keep correct order of switching devices on)
- HFP works with second device, Sony Ericsson HBH-PV708 (had to disable HFP profile in BH200)
Audio switches when receiving phone call.
Obviously, that's not the best solution (far from it), but it's at least something...
Hi all,
Anyone can confirm that Desire has a rSAP (remote Sim access)?
Some people are saying it doesn't work with their Nav, some say it is working.
Any one got it hooked up to their Vw/Audi/Skoda RNS Nav?
Looking to change from my TouchHD.
Cheers,
Android does not support the SAP/rSAP protocol. It may be that some people have it working on cars that use the HFP or HSP profiles.
Thanks mate, not good at all!!!
A little up now the phone's live...
Does it support rsap? is there any way to push contacts etc...?
I got an audi with a built in Bluetooth system, pairing ok, phone etc ok, but no possibilities with my desire to have rsap working
swissman said:
A little up now the phone's live...
Does it support rsap? is there any way to push contacts etc...?
I got an audi with a built in Bluetooth system, pairing ok, phone etc ok, but no possibilities with my desire to have rsap working
Click to expand...
Click to collapse
I also have the Audi built in BT system, and it works fine except that from what I've read about rSAP, I don't think it's working in that mode with the Audi.
The only difference (problem) I've been facing with my HTC phones vs. Nokia e71 is that the phone ring tone is not pushed to the car speakers when receiving a call. I was hoping it would work with the Desire as the default Audi BT ringtone is stupidly annoying.
Sorry off topic again, but I was wondering, are Bluetooth profiles generally defined by hardware or software? Or some by this, some by that?
Maybe you could check if it has another setting to retrieve data from the phone.
From what i know the new modules used in audi/vw/skoda are Novero modules (part of the nokia business) which only supports rsap.
The older modules are from harman/Becker and do support al the possible connectiontypes.
You can check which type you have under the passengers frontseat, the modules are build in under the seat, not in the radio.
If you have a Novero, tough luck. But you can always check on the local car junkyard if you can find an old car which does have a harman/becker, and build that one in
salahag said:
I also have the Audi built in BT system, and it works fine except that from what I've read about rSAP, I don't think it's working in that mode with the Audi.
The only difference (problem) I've been facing with my HTC phones vs. Nokia e71 is that the phone ring tone is not pushed to the car speakers when receiving a call. I was hoping it would work with the Desire as the default Audi BT ringtone is stupidly annoying.
Sorry off topic again, but I was wondering, are Bluetooth profiles generally defined by hardware or software? Or some by this, some by that?
Click to expand...
Click to collapse
Just wanted to add to eliminate any confusion. I can dial contacts saved on the phone and directly search for them on the car screen. But what I understood is that rSAP profile connects to the SIM card and fully replaces the phone, where it goes into some kind of sleep mode!
salahag said:
Just wanted to add to eliminate any confusion. I can dial contacts saved on the phone and directly search for them on the car screen. But what I understood is that rSAP profile connects to the SIM card and fully replaces the phone, where it goes into some kind of sleep mode!
Click to expand...
Click to collapse
Exactly... you can even read/send sms directly through the display and through your car multimedia system.
Ford
Just a little extra info, Desire now works with the Ford Convers+ system but ONLY on Android 2.1 Update1 (the stock Android 2.1 didn't work).
Just thought that may be why there's mixed reports of working/not working?
Tirinoarim said:
Just a little extra info, Desire now works with the Ford Convers+ system but ONLY on Android 2.1 Update1 (the stock Android 2.1 didn't work).
Just thought that may be why there's mixed reports of working/not working?
Click to expand...
Click to collapse
I got the stock Android and it's showing Android 2.1 update 1.... but not working ;-)
Hmm - well I'm trying to use my HTC Desire with a 2010 Audi A3 with BT and not having any luck so far. Although it paired and transferred the phonebook (took quite a few minutes with a couple of hundred contacts), it's now being really flaky and sometimes just refusing to connect at all. I tried un-pairing/re-pairing but to no avail. It just seems to work sometimes for a bit then stop again. By comparison pairing my Desire with a Jabra BT headset worked fine.
Anyone else having these problems? Anyone know of any updates for the Audi software? (if not I suppose I'll just need to wait for Froyo and hope that it fixes things )
my desire works well with my VW golf.
phone book, calls (dialing and receiving) and status dispay working. not working is SMS
Hey Folks,
there is room for some BT "education", because most people don't know the difference between rSAP and Handsfree.
Handsfree is working like a BT headset - most disadvantage - you are using the phoneunit of your mobile.
rSAP is using BT protocoll to get only the SIM card of your mobile and work together with the phoneunit of your car.
For Audi you can see on which mode your are conntected at the MMI-Display => "SIM card icon" stands for rSAP while "Mobilephone icon" represents handsfree mode.
no rSAP
I could be wrong, but I was of the impression that Nokia had patented the RSAP protocol, so you're not going to see it on non-Nokia phones. Irritating, really. Some car users have retrofitted their handsfree kits with a module that uses handsfree profile with some success but it's not going to use the car antennae etc in this case.
rSAP is a "STANDARD" for bluetooth protocoll in general.
Nokia was one of the first, thatswhy the Nokia unit has some "problems" in early releases....
Well I picked up my Skoda Superb last week, dealer told me they were fitting the new GSM 3 units that had just recently changed, not that it meant much to me.
Anyways it did work fine first couple days then started playing up with not connecting, I went into the options because I found it was connecting to media, but not phone, so I disabled the media option on the phone for the bluetooth connections and its been fine ever since.
Desire running Modaco R4, R5 & R6 now also ok.
Also saw a file posted on there that is meant to fix the iffy bluetooth connection problems, its been confirmed as working but I've not tried it as I've not had any more problems with it.
Will take a look though see if its connecting with a phone or sim card, I had noticed the signal always seemed really good even if the phone was berried in the car somewhere so maybe the rSAP explains it.
Tinyk said:
Also saw a file posted on there that is meant to fix the iffy bluetooth connection problems, its been confirmed as working but I've not tried it as I've not had any more problems with it.
Click to expand...
Click to collapse
Do you have a link to the thread that includes this file by any chance?
Do not mix up android 2.1 and 2.2.
AFAIK the modaco roms are froyo which should have a better bluetooth stack than eclair.
Well some good news! The FroYo/2.2 update on the Desire seemed to do the trick for me and I now seem to be able to get a stable BT connection with my A3. Phonebook transfer working fine too and it's reacquiring the connection when getting back into the car.
Any hope for Android 2.1?
Alanjrobertson: did you say you got your HTC Desire Android v2.1 phone working with your Audi, albeit a bit flaky? I cant get my HTC Desire Android v2.1 phone working with my VW EOS working at all.
What was the process you followed? The process I went through was to turn on phone’s bluetooth and make my phone discoverable. I then initiated a search from the car. It found my phone and displayed the correct name. However, when I chose the “connect” option on the car, it gave the error message: "mobile telephone phone is not compatible" on the car’s MFD.
Is this what you did? Is there a better way of connecting?
The car’s entertainment system is RNS510. I’m not sure if this is associated with Bluetooth or not.
My previous phone (Nokia 5800) worked OK, but my Desire doesn’t.
I am hoping that the Android v2.2 upgrade will fix my problems, but I’m still waiting for the update from Orange. It could take a while by the sounds of things.
I contacted HTC and they told me “The HTC Desire does not have the remote sim access profile. we currently have no plans to update the Bluetooth profiles on the device.” This makes me worried that when I eventually do get the Android v2.2 upgrade it will not work.
Any ideas other than waiting for the Android v2.2 upgrade?
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
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.
Hi all,
like many 5T users I bothered problems with bluetooth connection in car audio system (spotify and calling). I've tried everything what I found on forums (downgrading software, clearing cache, energy settings etc.) but with no success. Finally I red somewhere that problem is OOS itself and custom rom should do the work. My question is: what custom rom should I use (on my earlier phone (samsung note 3) I used Ressurection ones)? Did someone tried this way and could tell about results?
Im on cnp and everything seems fine when I connect to my truck.
Thank You for fast reply, but did You experience bt problems on car audio system earlier (with official oos)? And what is cnp?
Pan_Hrabia said:
Thank You for fast reply, but did You experience bt problems on car audio system earlier (with official oos)? And what is cnp?
Click to expand...
Click to collapse
Codename Phoenix rom
What problems? I've been running oos all long and no issues with my car bt.
Problems with bt connectivity (spotify does not work - stuttering and disconnects and calling also). On official forum it's a popular problem and has many potentially solution. None works for me so far.
Many problems with my car BT (mercedes w211) with TugaPower ROM (now on v26.0)
After the initial connection car reports no (mobile) signal but I can manually dial. Automatic / voice dialing does not work.
Almost on every call BT disconnects and I have to redial. I make the call and few seconds into it, it drops call back to the phone with the car radio reporting "waiting for BT connection"
I tried to look into the logcat but I see no related error(s).
I'm also looking for a good rom that works with my car BT.