Related
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.
I have had the TP2 for a couple of weeks now and am generally very happy with it, but for some reason the Sim Access Profile is not working correctly with my Audi. I have paired the phone with the car and have enabled SAP in the phone's BT advanced settings page. Unfortunately the car will only access part of my phone book (only contacts under A to B are showing). The phone has all of my contacts on it and all of the other features of SAP seem to be working. I know that I can use JETware as an alternative but would like to know if I am doing something stupid with the phone before I go down the JETware route.
Any help would be appreciated, thanks.
I put my problem / question in this thread:
I use the TP2 in my skoda with a audi BT-SAP-Adapter this combination works, tested it before with my S/// X1.
When i pair my phone with the sap-Adapter the adapter recognizes that the TP2 can use the SAP-BT-profile and use the longer pairing PIN (when you pair a mobilephone wich has no SAP-profile the adapter use the Handsfree-profile and shows you a shorter PIN). As far, everything seems to work great.
But when my TP2 want´s than to connect with the adapter i see that the statusline shows the typical symbol for the flight mode and in the BT-menu at the BT-adapter i see the words "SIM-Access" for very short time (~ one second). Next the line “Stereo-profile” or something else (it is to fast to read) appears and half a second later the line “Handfsree” appears. The Symbol for a handsfree connection is shown at the statusline and the sign for flightmode changes back to the normal symbol for filedstrength.
what i tried as far to solve the problem:
1) i contacted the HTC-Support. They told me. that they made, at the moment, a test-row to solve specially the problems between HTC-WINMob-Handsets and car-handsfree-sets. So i got from there a software which i had to install at my phone and got a error-report. This i had to sent to HTC. No further comment from them.
2) i searched at very much forums at the car and mobilephone scene.
3) I tested the combination with different SIM-cards from different Providers and different ages.
4) I deleted my contacts at my SIM and wrote some newer one with an NOKIA Phone (this helped by some other SAP-car-FSEs)
5) I used No-Data
6) I installed the newest radio-rom.
Nothing of this brought some solution.
As i found at my recherches i´m not the only one who hast this problem with the HTC and sap-car-handsfree-set.
I thing, that this is a problem with the BT-Stack which is used at the TP2 and other HTC, is it?
Dose somebody solved this problem? Even with an other HTC with the same BT-Stack???
Has somebody any other idea to solve the problem??
Any help??
Merci
Quino666
I had no problems with SIM access on my 2010 A3 TDI -- worked flawlessly with my Tilt 2 with stock ROM. I haven't checked the car's phonebook lately, but last time I looked, everything was there.
1) With update on WM 6.5 or the first WM 6-version of the ROM?
2) Do you use a build in Handsfree solution with sap-profile or the adapter-solution?
Merci
Quino666
Hey,
I have a similiar Problem with the rSAP snap-in Adapter in my 2010 iDrive BMW. rSAP (telephony) just works great, but it only syncs the simcard's PhoneBook entries.
The BT-Monitor on my TP2 (Energy Rom WiMo 6.5.6) shows an active SAP and PBAP connection. Any ideas how I tell my TP2 to distribute the internal Exchange contacts and not the SIM-Contacts?
bye
Darky
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?
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
tifosi256 said:
My girlfriend and I both have HTC Desires (one unbranded and one Vodafone). We recently got a 2005 BMW 5 series with the I-Drive Pro Nav system in it.
When I try to use BT to connect to the car, I can manage to pair them, but when the phone goes to connect to the car, it only connects for a few seconds and then disconnects. It then connects again and the whole thing repeats. The disconnect is frequent enough (every few seconds) to render the whole thing unusable. It also means that it isn't connected long enough to transfer the phone book.
Both our Desire's have this problem (they have different firmwares). I thought that maybe it was the car, but I put my SIM into my old Xperia X1 and it worked flawlessly with the car.
Is there a setting on the phone that needs adjusting or is it a firmware problem? I hear other people with the same car having no problems with the Desire. I've also used my Desire in a Toyota Avensis and a Vauxhall Insignia with no problems.
Any advice would be gratefully received.
Click to expand...
Click to collapse
Hi,
I know there are some issues when it comes to Bluetooth and Android, and especially car kits.
Ref (sound quality): http://code.google.com/p/android/issues/detail?id=9888
Ref (disconnections): http://code.google.com/p/android/issues/detail?id=5452
This is supposed to be a fix (I did not get it to work properly): http://forum.xda-developers.com/showthread.php?t=731626
I know that Cyanogenmod has made some changes to their kernel in 6.1 that adresses audio quality (bitpool increased), and I also think that the disconnection is adressed. I'm actually testing it for the moment (6.1RC2).
Thanks very much for your reply - very useful. The link to disconnections that you gave shows someone else with the same car as us (slightly different model) with the same issue.
It's very strange as there are people reporting no problems at all with that car/phone combination.
Unfortunately, I can't try the suggested fix as I don't want to start mucking around with my ROM.
I have a problem with my Volvo and the Desire. No disconnections, but I can't get into the phonebook, using PBAP.
Flashing a MIUI Rom works charming for the bluetooth connectivity, however I'm missing my SenseUI.
Just hoping, praying, some def will include the AOSP bluetoothstack in a SenseUI-Rom
BMW Software update
Hi
I´d try contacting your local BMW workshop, to let them do a reading on your car to establish which software version your car have.
If it´s a rather old software version your car have, I´d suggest that you have it updated.
The software update might be the answer to your problems, and can also explain why other users with the same car don´t have this issue (they might have a newer software version than you).
Remember, this phone is way newer than the car, and also the software in it.
I´d give it a try
PS: Be advised. Updating from very old software to new software might cause "in car-hardware" compatibility issues, and demand new hardware in the car (computer modules ect.), so make sure you talk over which consequences the update could have for your specific car before the update is carried out
Cheers
-Buggi- (BMW workshop foreman in Denmark)
Thanks for that advice. I'll talk to the dealership and see about software upgrades. Fingers crossed!
I have a 2008 530i and my Desire (and my other halfs) work fine, so hopefully there is some newer firmware for yours. They facelifted the cars and slightly changed the iDrive in 2007 though so fingers crossed there is an update that fixes the pre-LCI models with a Desire.
Just for reference, this is sorted out now.
My I-Drive actually broke and I had a whole new unit put in (under warranty thankfully!). Since they were doing that, I begged them for the latest software, not just for the Bluetooth module, but for the system as a whole.
Since the software upgrade, the phone stays connected and everything works great.
The only fly in the ointment is that it seems that for some reason, not all numbers of contacts (or all contacts) make it into the car's phone book (most of them do).
Anyway, for anyone else having this issue, get BMW to upgrade your BT software (or the whole system if you're brave).
I have similar problem when i try to pair the phone with volkswagen tiguan 2010, it says "your phone in not supported"
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.