Related
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?
After searching this forum there is no thread on Bluetooth issues connectivity.
For a wile now i been searching the net and different sites for a fix between my phone and my car bluetooth. Before the epic i had a windows phone and the connectivity was fine including all the phonebook would load up and everything the system was build to do. With Android Epic i been having issues. Sometimes I cant connect to the car and other I am able to connect but phonebook wont load.
With all the Geniuses in the website i am sure someone can come up with a fix.
I figured i open this thread hoping we can find a final fix to retire this problem.
If it helps I am running the latest Viper Rom with Genocide kernel at 1.2ghz
However the rom did not change the statues of my issue.
Any help would be appreciated.
Thanks
I also have connectivity issues with bluetooth, in my case the car has A2DP allowing for music to be played over the car's stereo. It cuts out so much that it is completely useless for music. I mostly listen to podcasts but Pandora would be nice. However it cuts out so much that it isn't worth it. So if anyone does have a solution. To me though I've tried so many kernels, and roms to no avail that I'm pretty sure taht the software Samsung has shipped has faulty drivers. By the way it also seems that the cut outs occur when switching towers, however I could be wrong.
I use this in my car: http://us.kensington.com/html/14484.html
It may cut out every 45 seconds or so but it's the only thing I've used. Got it on sale for $20.
I've got a pair of a2dp bluetooth headphones that I use to listen to podcasts via my Epic. I've had zero problems with those (using DK28 atm, for the record). So I don't think there's a hardware problem with the Epic's bluetooth.
If we're going to get some troubleshooting done, we should get a bunch of details from everyone. Like exactly what bluetooth hardware they're using, and what roms they're running.
thezero4 said:
I also have connectivity issues with bluetooth, in my case the car has A2DP allowing for music to be played over the car's stereo. It cuts out so much that it is completely useless for music. I mostly listen to podcasts but Pandora would be nice. However it cuts out so much that it isn't worth it. So if anyone does have a solution. To me though I've tried so many kernels, and roms to no avail that I'm pretty sure taht the software Samsung has shipped has faulty drivers. By the way it also seems that the cut outs occur when switching towers, however I could be wrong.
Click to expand...
Click to collapse
Does everything cut out, or just Pandora? If it's just Pandora and other apps that need data connection, it might not be a bluetooth problem as much as a data connection problem.
I would suggest testing it by trying the car bluetooth with something that requires no data connection at all, like pre-downloaded podcasts.
I am talking about connectivity issues with in stock car bluetooths.
this problem is big many people been having this issue and there is a list of stock bluetooth cars that android wont pair with. I had the touch pro 2 for sprint with windows system and it worked fine in my car bought the epic and there we go. Now looks kind of bad that i would need to get an aftermarket piece to listen to bluetooth calls and load up the phonebook from android to my car.
Windows got it right even though i would never go back to a windows phone so i know there is something that android messed up here
Below i will put some links to show you how there is A LOT of people that been having this issue.
http://code.google.com/p/android/issues/detail?id=3960
http://www.google.com/#q=android+bl...start=0&sa=N&bav=on.1,or.&fp=3f40f95b1b9c7c0d
I have a 2006 Dodge Durango. It has Bluetooth. My old phone, a Samsung flip phone would connect without issue. My new phone, a Samsung Captivate, will connect most of the time, but often times, once it connects, it drops the call.
I understand this is an Epic thread, but I thought I would add my input as I am having similar problems (and this came up on my search).
If I understand you correctly, you connect some of the time and sometimes not.
Regardless, if your phone is rooted you might wanna try this.
I had a lot of issues with my bluetooth after upgrading to froyo and tried a lot of fixes including wipe3x and odin to stock....this is the one that worked for me.
http://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Ensure that you first
- delete the car from your phone,
- delete the phone from your car,
- disable bluetooth,
- delete the file,
- CHANGE YOUR BLUETOOTH DEVICE name,
- restart,
- reenable bluetooth
- re-pair your phone with the car.
Situation:
I'm using a Xlink bluetooth gateway in my house to connect my phone with and I also have a Mazda CX-5 with integrated Bluetooth system with the latest update from TomTom and Mazda. In the Mazda, I use the Bluetooth mainly for the phone, but occasionally use it to stream audio.
Phone:
T-Mobile samsung S2 x SGH-T989D with ICS 4.0.4 (Rogers leak)
Issues:
At first (With official Gingerbread)... everything was working fine. Both device paired and all functionality worked.
Then, applied official ICS update from Kies software ICS 4.0.3 and Bluetooth issues started. I first paired my Xlink device. So far it worked. Then tried to pair my Mazda, everything was really slow but managed to have it work. Turn the car off, get back in the house and the phone is now able to pair with my Xlink device, but cannot connect as a phone audio. Even if I go manually in the Bluetooth menu and try to activate the Phone audio it wont work. Only way to have it work again is to unpaired the Mazda and reboot.
After reboot, the phone works great in the house with my Xlink device. Going back to my car and try to pair my Mazda. Same issue. The phone does pair with the Mazda, but I'm unable to make a call since the phone cannot activate the Phone audio.
Look online and have tried the ICS 4.0.4 (Rogers leak) and same issue with Bluetooth.
The only way my devices works perfectly is when I only pair with one device at a time. There is something happening when you pair more than one device, even if not both device are turned on or in range.
Anybody got the same issue or a fix to that?
Thank you and sorry if my post is a little long... but that issue is the only thing that make me not enjoy my phone.
I have probably not so unique situation.
My Honda allows for calling via bluetooth but not audio streaming. I use an old Blackberry Gateway for that which works perfectly when I had my Samsung S2.
With the Note, the BB Gateway connects and streams audio fine but the car cannot maintain a constant connection at the same time.
I use A2DP volume (which is pretty awesome for free) to force connection attempts. If the BB gateway is not connected, the car maintains its connection. It seems the Note2 cannot do both.
Does anyone have similar problems or a work around? Or maybe know if the new leaked update fixes this? I heard it does update something about BT...
I'm stock rooted BTW
scoobmd said:
I have probably not so unique situation.
My Honda allows for calling via bluetooth but not audio streaming. I use an old Blackberry Gateway for that which works perfectly when I had my Samsung S2.
With the Note, the BB Gateway connects and streams audio fine but the car cannot maintain a constant connection at the same time.
I use A2DP volume (which is pretty awesome for free) to force connection attempts. If the BB gateway is not connected, the car maintains its connection. It seems the Note2 cannot do both.
Does anyone have similar problems or a work around? Or maybe know if the new leaked update fixes this? I heard it does update something about BT...
I'm stock rooted BTW
Click to expand...
Click to collapse
I'm having the same problem. I have a 2006 Pontiac GTO with a Kenwood touch screen and my Note 2 will connect fine, and it will stay connected with no issues until I switch to another playlist, artist, or song. That's when it seems to just disconnect itself and then, about 30 seconds later, reconnect itself.
I've tested this on stock unrooted (LJ1 and LJC), stock rooted (LJC and LK8), Jellybomb v10.2 and v11 (LJC), and H20 beta's 2.1 and 3.1 (LK8) with no luck. I also just recently started trying to use A2DP volume and it definitely helped with displaying the correct song name, artist and album (it wasn't changing when the song would change prior to using A2DP) so it's definitely an improvement but...
Considering how much I drive and how much I LOVE music this is becoming an area of major concern. If any of the amazing developers, or anybody for that matter, has any words of wisdom, suggestions, fixes, etc. it would be HUGELY appreciated.
That_Guy0505 said:
I'm having the same problem. I have a 2006 Pontiac GTO with a Kenwood touch screen and my Note 2 will connect fine, and it will stay connected with no issues until I switch to another playlist, artist, or song. That's when it seems to just disconnect itself and then, about 30 seconds later, reconnect itself.
I've tested this on stock unrooted (LJ1 and LJC), stock rooted (LJC and LK8), Jellybomb v10.2 and v11 (LJC), and H20 beta's 2.1 and 3.1 (LK8) with no luck. I also just recently started trying to use A2DP volume and it definitely helped with displaying the correct song name, artist and album (it wasn't changing when the song would change prior to using A2DP) so it's definitely an improvement but...
Considering how much I drive and how much I LOVE music this is becoming an area of major concern. If any of the amazing developers, or anybody for that matter, has any words of wisdom, suggestions, fixes, etc. it would be HUGELY appreciated.
Click to expand...
Click to collapse
I'm having similar problems with certain roms. Only my truck is a Chevy not Honda. Using blackberry audio gateway. The "Note Card 2.2" rom works perfect for me, along with JellyBomb. I didn't like JellyBomb. I want to switch to another. I need to spend time and found out what is different between the working and non-working Roms. I had the same problem with my EVO 4g. Some Roms worked perfect, others acted up.
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