Hi
I have an s620 and wish to install a bluetooth car kit but cannot find any clear guidance on comaptibility. I need to be able to access the phone book, and the two which interest me are the Bury CC9060 and the Parrot 3200LS. Does anyone know if either or both of these are compatible with the s620 or of any suitable alternatives?
Thanks
MB
As far as calling is concerned, you should have no trouble whichever route you go. The phonebook will give you the most trouble. There's a utility by a company called jetwaremobile.com that allowed my car's bluetooth headunit to receive the phonebook from the dash.
Thanks. Yes, I have heard of jetware - am just nervous on forking out around £200 to discover all it can do is make and receive calls. Which system are you using? Also are you on WM6?
Jetware have a compatibility list on their page for devices that have been proven to work (with a corresponding table of features supported by device.)
I'm using a Pioneer headunit with bluetooth built-in. I sync'd the phonebook under WM6.0. I'm on 6.1 now and haven't tried updating it.
I use this....
http://www.crutchfield.com/App/Prod...=105AVX810&search=JVC&searchdisplay=JVC&tp=75
with this....
http://www.crutchfield.com/App/Product/Item/Main.aspx?g=280050&i=105BTA200&tp=8272
but there are alot of better models out now..
Thanks for the advice. Have looked on the jetware site and they don't list the device I am after. Also, are jetware still going as on their own furums people believe they may have ceased!
Have contacted a few of the car-kit retailers and the feedback seems to be that HTC devices in general have a lot of compatability issues and the S620 isn't even listed on any device as being compatible. Am hoping to be able to test in store to see if I can make it sync so will feedback then.
For what it's worth. Dash/S620 works great out of box with BMW 2007 bluetooth. Have used with WM5, WM6 and WM6.1. Complete phone book sync, and send/receive calls.
The BMW is listed as compatible on jetware's site, as is the parrot device the original poster was talking about. It lists it as a 3X00, implying anything in the three-thousand series from parrot will work. I didn't see the Bury one listed. And whether or not they're still actively developing the software, it still works on the dash. It comes as a 30-day trial as well.
this my help
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?
Hi,
We have a company that is upgrading their fleet of cars to the latest Holden. The new Holden stereo has a touch screen setup that allows pariing with phones via Bluetooth.
I have tested the Android and it pairs fine, and I can make and receive calls.
However it won't allow me to view contacts or make calls from the contacts list.
The Holden Website ( http://www.holden.com.au/owners-info/bluetooth-and-devices/bluetooth-compatibility ) states that this is not possible with the HTC Magic (Android 1.6) but doesn't list any other Android phones. (Window Phones will do PBAP / Phonebook App no problems).
I was just wondering if anyone knows if this is a phone issue, and should work with future updates to the Android's ROM or if it's a Car issue and the HTC Desire will never work with these cars?
OR - is there anything that can be done to get the Android to allow the phones contacts to work with the car?
Cheers
Adam.
OK - Looks like the problem isn't just with Holden.
Came across this thread, and it would appear as though there is a problem with Android and the Bluetooth PBAP protocol.
http://code.google.com/p/android/issues/detail?id=8846
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 have a Galaxy Note 2 running Jedi Master 13. Every single thing is awesome about this phone...
EXCEPT:
I have a Lincoln with the new MyLincoln Touch radio. It supports text messaging ONLY with ICS or more specifically, Bluetooth 3.x. The Bluetooth MAP (messaging access profile) is different in 4.0 and thus not supported. Is there any way to downgrade said Bluetooth version?
I only use BT stereo and phone headsets normally, never use file transfers so the 4.0 advantages wouldn't affect me (I hope).
Thanks in advance for the input! :good:
Did u try and call the dealership, maybe ur car has update they can do
BACARDILIMON said:
Did u try and call the dealership, maybe ur car has update they can do
Click to expand...
Click to collapse
Yes, yes I did. I was in touch with the people that make the MyLincoln Touch device that works with Microsoft Sync. I have the newest version, which supports up to Android 4.1.1 and the Bluetooth 3.0 software, which has advanced compatibility with MAP. The Bluetooth 4.0 doesn't work the same and makes it lose the ability to do SMS from the car itself. Ugh.
I was hoping I could somehow put the old Bluetooth stack onto my phone to make it work properly. As of right now, Ford/Lincoln say that only Android ICS' Bluetooth stack is compatible. I feel better than the Apple community, they don't even get pictures to transfer. At least It's cool having the address book picture on my phone.
So can it be downgraded or not?
I am also interested in this (for another device though). Is it possible in principle?
No this stuff is way too complex due to the new advancement of spamsung Knox controling everything, we have very little control of our devices any more