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 have been searching for days trying to resolve this. I have a new cordless landline phone (Uniden) that has a great feature where it will bond to my mobile via Bluetooth ... allowing me to accept and make mobile calls via the cordless landline handset. When I try to bond though - it fails.
I read the Uniden instructions - and they say it requires Bluetooth 2.0 or greater ... and my HTC Touch Pro 2 (Australian Telstra version - initial release version from a couple of years ago) has version 1.9.2 Build 600.
I read that the more recent models of the Touch Pro 2 have Bluetooth 2.0, so I ordered a replacement HTC Touch Pro 2 and it arrived today. Sadly - it has the exact same bluetooth version as my 2 year old version.
Next - I try to flash the ROM (thanks to ENERGY ROMS). It works great - but the bluetooth is still 1.9.2 build 600. So I flash the radio. It works great - but the bluetooth is still 1.9.2 build 600.
Around about now - I realise that I don't have a clue what I am doing and that randomly flashing things hoping for an update is not the way to go. So - can anyone out there please help me to figure out how an HTC Touch Pro 2 can have it's bluetooth updated to 2.0 or beyond?
Many thanks,
Scott
Can I drop my Bluetooth version from 2.1 back to 2.0?
Looking further into this - I have noticed that despite the Bluetooth module reporting version 1.9.2, if I look at Device Information (Hardware) - it reports that I have "Bluetooth version 2.1/2.1 + EDR". This has me thinking that my problem is actually that my Bluetooth version is beyond the spec that my Uniden cordless phone can deal with (Uniden claim that their bluetooth hookup is only compatible with version 2.0). I have heard of others with this problem when trying to hook up to their car bluetooth eg. GM only supports connections with devices running up to Bluetooth version 2.0.
Given the above - what I am now looking for is a way to dumb my bluetooth down to 2.0 from the current 2.1 spec it seems to be running. Has anyone managed to achieve this - perhaps through some sort of registry editing?
Cheers,
Scott
Noone answered this so I'll take a crack at it... 2.1 is backwards compatible, so it'll work. You need to figure out what profile the Uniden requires. Is it handsfree or headset? When you try to bond (pair) there are two things that'll fail it... wrong passcode or device accepting the pair NOT in discovery mode. Since I doubt it's the passcode, it must be the latter. I assume you're turning on the BT on the Uniden and having the TP2 discover it. It'll see it... but it won't pair. Turning on the BT doesn't put the device in discoverable (pairable if you will) mode.
Hi could someone please help me out please
I have a Supertooth Buddy Handsfree Kit and It connects to my HTC Desire, but it only connects on the Phone Audio profile and NOT the Media Audio profile... My N97 seems to work fine it can stream Media Audio and Phone Audio
Right I contacted HTC see if they could help they said its impossible to do that Nokia phones do it coz they have more Bluetooth profiles than HTC coz they helped create the the technology....
okay to the point I know stuff can be hacked and altered/added (unofficial/illegally whatever you wanna call it) so I came across this How to connect mini bluetooh keyboard to Desire Froyo
That thread up there seems to explain how to add a Bluetooth Keyboard, so am guessing its actually adding in a Profile.
Is it possible that someone can help me out on this? I already have a rooted phone.
Hi everyone, I'll try again with this post
So the htc one v doesnt have AVCRP for bluetooth connection to certain devices.... I am trying to get my head around the different bluetooth profiles. It has A2DP, which is unidirectional, so does that mean there is no compatible bluetooth headset or car kit system for this device? if it only transmits music etc TO a speaker?
This seems like relatively 'dark ages' technology to me, and i find it really hard to beleive. Someone has previously told me Cyanogenmod is 'working on it'. I know this is a ROM (i dont know much more than that), so this implies to me that the phone has the capablity for AVRCP, but htc didnt put it on there?
I really want to just be able to run my phone through my car stereo to make and receive calls.
It might be a whole other thread topic, but would cyanogenmod help make my phone better i.e. faster and not like a piece of s**t?
Thanks in advance
Roxi
Does anyone know anyone in Melbourne Australia who offers a phone overhaul (root etc) service?
I can't help with the blue tooth questions, but most custom Roms will have the OneV working better. If you want to root it, I advise doing it yourself with the AIO tool. All the info for this is available on these forums.