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?
Hello Everyone,
I have a Note 3 Neo 7500Q ( Turkey Version). I am overall satisfied with the phone, but when I try to connect to my multimedia car kit via bluetooth, I have problems. It pairs up with the kit, but neither my nor the other parts voice is transmitted. I tried to every way without luck. Does anyon else has or had the same problem? Is there a way to overcome this issue? All kinds of help is appriciated.
I use the BT car kit all the time, with no issues whatsoever. My unit is a Parrot MK9200 or something. It is 4 years old, can't remember the exact model number. Phone calls, music streaming etc. works fine.
Here are a few suggestions you might try:
1) When I had the Parrot initially, 4/10 the phone was failing to connect over the Bluetooth. I upgraded the Firmware of the Parrot. Ever since, no connection issues. Check whether your Bluetooth unit has a FW update!
2) When the phone pairs with the car the first time, it asks for permisson to access the Phone book, logs etc. Mark "Always yes". That might be your problem.
Hi,
I tried connecting my bluetooth with my car (2003, bmw e46), the pairing works, but it keeps disconnecting and I can't receive any calls thru my car.
From what I've read, there is an issue with the bluetooth stack that was changed in android 4.2? Can I patch/edit it somehow so it can work?
Found a similar guide here (for the same car), but didn't manage to make the edits.
http://forum.xda-developers.com/android/help/qa-lollipop-bmw-e46-carkit-bluetooth-t3045523
Finally managed to apply the fix in the url above and works perfectly.
Hello everyone, I was wondering if this has happened to anyone else.
I updated my rom to "Johny DJ" MicroG apps 5.1.1, everything is working except bluetooth seems a bit strange, on the Bluetooth app I cannot see any connected devices, or I cannot search for any devices, but I can connect to it from my phone, if I make a call I can hear it though the car, but the app still does not see the phone, so I cannot search for any contacts.
Additionally it also means I cannot connect a OBD2 because I cannot see it through the unit.
The only Bluetooth that work is the WQ_BC5, can it be an issue with the bluetooth manager.apk and that specific module?
Had anyone else had this issue?
Thanks
Hello
I'm facing the problem that the bluetooth connection to my cars multimedia unit is a big mess since 2020.
But not only when connecting to the cars BT. Every BT connection will randomly asks for permission to the contacts or messages...
The phone will not store this information correctly anymore. My car is an 2020 Opel and sometimes it says that the bt connection can't be established, but it actually plays music over this connection and phonebook is also transfered.
I have the pixel 3XL since it came out and it is completely stock non rooted or something like that (I'm to old for this stuff as a daily driver )
So, did google mess the driver up that it will not work correctly anymore? Or does someone know what's going on in the device?
Daimonion1980 said:
Hello
I'm facing the problem that the bluetooth connection to my cars multimedia unit is a big mess since 2020.
But not only when connecting to the cars BT. Every BT connection will randomly asks for permission to the contacts or messages...
The phone will not store this information correctly anymore. My car is an 2020 Opel and sometimes it says that the bt connection can't be established, but it actually plays music over this connection and phonebook is also transfered.
I have the pixel 3XL since it came out and it is completely stock non rooted or something like that (I'm to old for this stuff as a daily driver )
So, did google mess the driver up that it will not work correctly anymore? Or does someone know what's going on in the device?
Click to expand...
Click to collapse
Have tried different ROM's on this Pixel 3 XL so I completely understand the Bluetooth issue. Have grown to rely on turning off Bluetooth before using the passcode; kind of helps with the new ViPER4Android FX,
Since using ScorpionROM, haven't had any Bluetooth issues. Maybe give it a shot and see if it helps