Just wondering if you guys can help
My touch Pro 2
Vodafone UK
ROM - 1.14.161.6 (50207)
Radio - 3.44.25.27
Protocol - 61.25t.25.19U
links to the 2009 BMW 5 series iDrive and reads the phone book I can make calls fine but if I pick up an in coming call using the iDrive controller it makes the connection but there is no sound either way.
If I press the phone answer button on an incoming call then it works perfectly.
It does not do this all the time but its more like 90% can't hear and 10% works fine.
I contacted HTC who said that the phone matches the bluetooth profiles and it should be fine BMW have not got back to me yet (4 weeks so far)
this also happens to some one else I work with and his touch pro 2 on his 2005 BMW with the older iDrive and built in BMW Phoneprep.
another guy with an Audi has no issues at all. I also contacted Bury who make the Uni-System 8 car kits about when they were going to do a cradle for the TP2 and I was informed that they were not planning it at present, I asked why and they said "HTC's bluetooth was flakey"
I put the hard SPL on the phone and upped it to the latest HTC build
ROM - 1.19.707.2 (51489)
Radio - 3.44.25.27
Protocol - 61.25t.25.19U
but have put it back to the Warranty status as it did not make any difference
Any help appreciated
I know Parrto is a different BT HFBTP but I had all kinds of flakey problems until I updated to the latest Radio in the TP2 and upgraded to the latest firmware for the Parrot CK3100 Car Unit.
Try an update to your iDrive system.
More car kit problems
I'm really disappointed by the bluetooth in the TP2. Having just upgraded from a Snap which worked perfectly with all my attachments, the TP2 is a disaster with the car kit in my (new) Volvo. (A bit like the BMW story at the head of the thread.) Won't connect to my TomTom sat nav. Almost works with my Parrot (upgraded as recommended above). Not what you expect from a 'top of the range' piece of kit from htc. I hope there will be a patch for the BT stack. In the meantime I have to revert to my Snap for car journeys. Bizarre.
This happened to me:
If I don´t set up a data connection to my carrier, the link to my bluetooth car kit works perfectly, meaning that I can answer calls and hang up using the button on the steering wheel.
Once I set up a data connection, I can only answer and hangup using the buttons on the telephone. In any case I can listen and talk using the car kit.
TP2
The same issue here. My TP2 won't connect properly to my Volvo V70 2009 BT Car kit. It is connecting and synchronizing but then it won't make call's. (sometimes it suddenly does work). My phone is getting really slow. And somethine the connection fall's away during a conversation. Even when i shut down all data connections on my phone it behaves as mentioned here above. HTC and Volvo just point at each other and a solution seems far away. Yes. I did the firmware upgrades on both sides. At this time i would not recommend the HTC TP2 as a business phone. My collegues have similar issues with other car brands.
Volvo V70 2009 - Firmware November 2009
HTC Touch pro 2 - WM 6.5 UK (and a dutch vodafone office account)
Anyone with a solution? Suggestions? thnx.
My TP2 (unbranded) was working fine until I updated it to WM6.5 (an official release). Now, there are no issues when it gets paired with my son's Mitsubishi Lancer but it refuses to work correctly with my Audi A4. It picks a call but stays silent until charger is connected. Disconnecting of charger "fixes" the situation so I start hearing a call.
Bluetooth wasn't working for me either. Pairing went fine, answering worked, but no sound at all... I followed instructions on this page: http://www.everythingwm.com/forum/moto-q-9c/q9c-and-infiniti-g35x-bluetooth-problem-16833-4.html and now everything works as expected. I'm driving a Renault Espace with a built-in stereo/gps/carkit.
i bought a car kit MP3 player for my car. I paired it with my TP2 and enabled the "BT Audio" and "BT Handsfree". Outgoing calls work fine with no problems at all. But during incoming calls there is a problem. If the incoming call is from someone saved in my contacts, the BT carkit does not ring. If its from an unknown number (not saved in my contacts), it works perfectly. I tried all the tweaks and hacks in this forum but nothing worked. Anymore ideas.
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!
Im Using a Car-Radio with Bluetooth as Hands-Free Device. Everything works fine so far. I can acces the SIM-Phonebook on my TP2 directly from the Radio etc.. Wenn I get an call, the Number of the calling Person is shown in the Radiodisplay, but not the Name of the Person.
With my older Ameo the Name was shown in the Radio Display too, so im searching for a Posibility to activate this funktion in my TP2.
Does anyone know how to get the Name transfered to the Radio?
King Regards,
MrMmmkay
probably you need to update your radio
i had the same problem with my parrot carkit
when you connect it with your laptop via bluetooth you can update a parrot
probably you can get a software update from the site of your radio developer
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.
Good morning,
I've a problem with miui 7 (6.6.3) and car bt.
When I use Google voice, in the car start a whistle for about 10 seconds even if the communication is ok, and this is the major problem, if I try to compose one phone number from the car audio (the model is a Kenwood ddx6023bt) the feedback from the radio is "dial error".
These are rom bug because if I use the s.voice (official firmware 4.3) I'haven't any problem.
Could you help me as relsolve the problem? I could also install another rom... ( I tried 7.1.2 but, is a my opinion, isn't reactive).
Thanks!!
Nobody could help me?