Related
Hi all,
I just bought the Parrot minikit Hands Free car kit.
I am facing allot of problems with this device:
1. The main one is that when I am issuing a call from the TOUCH, the sound remains in the TOUCH and is not routed to the car kit.
2. When someone calls me most of the times I can answer the call and it works fine, but sometimes the phone rings and the car kit not.
I read in the trinity accessories forums that people faced the same problems with other Parrot car kits when they upgraded their roms to WM6.
I opened a SUPPORT case to Parrot and they are saying:
"We have fully tested the HTC Touch in France with our Minikit and we did not see any impediments. "
So I emailed them back with allot of links describing the problem.
Did anyone faced problems with the Parrot Mnikit or any other Parrot car kit with the Touch?
Thanks,
Carmi
Carkit problem
Hi,
I have a similar problem. I have my HTC touch paired with a Nokia Bluetooth carkit. I get incomming calls over the speaker but when I answer the call I first have to go to the menu and select "enable handsfree calling".
I can make outgoing calls directly via the carkit whitout selecting an option in the menu. Furthermore the volume is very low compared to my prvious PD (MDA Vario).
Has anyone a fix for this?
Gus
I have The same problem
I have an HTC Touch with a Parrot CK3100 freehand car Kit and have the same problem.
Often, when I receive a call the car kit show the call in display but when I pick up the CK shows an icon (like a musical note) and the audio is not transferred.
When I call from the HTC, some times works fine and some times no.
A partner of my company with the same car kit and a HTC Touch dual, has the same problem too.
With WM5 works fine (I test it with HP6515).
did you set the "services to use from this device" to "Hands Free" ?
This is a known issue with Parrot devices and WM6. I've had the same problem with a couple of different HTC WM6 devices. The problem is specifically related to Parrot, not WM6 in general. I've used the Tytn II with Motorola and BlueAnt BT devices without any problems. I upgraded my minikit from v1.02 software to v1.03, but that hasnt fixed the symptoms which we are all complaining of.
ARE YOU LISTENING PARROT?! Ive had the minikit for 6 months and I'm getting tired of waiting for a version of software that will fix all our problems.
I have the exact same issue with my Parrot 3200. I'm also waiting for a solution from Parrot!
Parrot MINIKIT and Touch problems
I've similar problem.
paired the two devices, sometimes I can start a call from my Touch and the sound is on the MINIKIT speaker, but most of the times the is still on the phone and I have to press the green button to switch the call on the parrot speaker.
I've upgraded the firmware from 1.02 to 1.03.
Another information: I've tested the MINIKIT with my blackberry 8100 and works perfectly, when paired and connected every calls is routed to the parrot speaker, so I think It's an issue between the parrot and WM6.
Any news?
thank you
Besides my Touch I also use my BlackBerry 8800 and that also works fine. With htc it's not working as it should be.
HTC Touch Parrot mk6100 PROBLEM!
With the Parrot mk6100 I have all the problems possible.
This Parrot is supposed to play properly the mp3 files that I have in the touch, but everything is a dissaster. Very long to write. The thouch gets hunged every time.
The worst problem is that the Parrot can't read the contacts in the Touch.
I have spoken with Parrot and Htc here in Spain and both say that the problem is Windows mobile 6.
I don't know what to do...
ive got the dual w mk6100
after having a lot of issues i found out i had to pair it both ways and the mk6100 got to say "bye". then everything worked fine. well almost. but pretty good indeed.
i posted in niki accesories.
it takes time to sync the contacts, true, but it finally does.
as far as i know, touch and touch dual is not that different , except for the mhz.
let me know what you think
Touch cruise and Parrot Minikit
I have the similar problems too. Sometimes the sound cannot be routed to the car kit. There is no way to understand the reason why one time it works fine and another time it cannot move the sound via blue tooth. Sometimes pressing the green button of the parrot minikit is possible to move the sound to the car kit, sometimes it doesn't help - the sounds remains in the HTC. I tested the Parrot minikit paired with Nokia E70 - I haven't seen any problems. Also I have tested the HTC paired with another blue tooth car kit - BHF-200 and all was OK.
I wonder ... if someone knows ... if the WM6.1 (by Bepe) will fix the problem!
Thanks in advance !
Parrot Minikit just tested with QTEK 900, WM6.1-Ranju
The Parrot minikit was tested with my other PPC - QTEK 9000 (HTC Universal) and I didn't see any problems. The QTEK works under WM6.1 (Ranju pack).
So I really wonder ... to upload WM6.1 to my HTC touch cruise ...
Any comments and opinions are welcome.
Thanks in advance !
p.p. My HTC touch cruise is still with its original WM6.0 ...
Bluetooth Hotfixes
Has any of you guys or girls tried any of the "Bluetooth Hotfixes", that are available for HTC branded devices on the HTC e-Club site.
It seems to fix dropped calls and connection probs. (and it seems to work)
The hotfix is available for several HTC devices.
You just have to register your HTC branded phone to get to the download portion of the site for your model, and see if it's available.
It's definitely there for the Elf, Tytn II and S710 (i'm not sure if it's there for the Touch cruise)
Hi there!
My friend has an Artemis and a VW Passat with a bluetooth radio (VW).
The radio requires sap, which was not supported with the old windows version that was installed on the phone.
We updated it with the newest T-mobile version (it is a t-mobile device) and now he has the sap-settings.
Unfortunately we still have some problems.
The car now finds the phone, the phone connects and both are connected.
Just to disconnect one second later.
We restared the device, we restarted the car, we changed the settings for the file-sharing.
We deleted the connection and connected again.
We still have the problem that the connection is lost one second after connecting.
Does anyone know the probelm and a solution??
Thanks in advance!
Cholera
noone having hte same problem?
I've got a Seat Leon (effectively same company) & i have had no problems connecting to the bluetooth within my car. I do however, have Meschles latest Rom installed & its based on Windows Mobile 6.1 professional - not sure what your T Mobile device is based on ?
I have had this trouble too. I can connect to the car OK but if I disconnect the phone will not restart, then if I try to connect to the passat again it connects and disconnects. Seems to be 6.1 is my problem. When I roll back to origanal HTC WM6 all is OK again. Maybe it is the new SAP becuae the HTC SAP icon is not the same (oldversion?)
I have a passat too. I've tried it with meschles and with mossis rom. There were
no problems with the bluetooth device.
My passat only can connect with bluetooth over the handy holder from nokia which has to plug in the UHV.
No SAP is possible.
So what system is in your passat?
My Passat is 2008 with premium bluetooth factory fitted (with the pop out keypad). I have to talk with my main dealer because they can change the module for a HFP instead of SAP?
Hi - I was wondering if it is possible to use my htc diamond as a bluetooth headset for another phone (blackberry in my case).
I have a workphone (bberry) and personal/car phone (diamond) and wanted to ensure that any call that comes on the bberry always goes via bluetooth to the htc diamond. Currently I forward all calls to the htc diamond, which is connected to the car audio via aux-in, however a better option would be bluetooth. This way I can always use the htc diamond and keep my workphone out of sight and look at it only for emails, etc.
I see no option in the bberry to assign the htc as a bluetooth headset - any ideas or clues on how to do this would be nice
This has been asked here on the android forum too
http://androidcommunity.com/forums/f44/use-phone-as-bluetooth-headset-for-another-phone-28050/
if the other device's bluetooth stack support audiogateway as headset and handsfree is not an option in that case
otherwise no unless one get a bluetooth stack which support audiogateway
thanks for the reply - so you are saying on the htc diamond end there are no issues and no changes needed. Its the bberry i need to take care of and make it recognize audiogateway?
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,
We have a company that is upgrading their fleet of cars to the latest Holden. The new Holden stereo has a touch screen setup that allows pariing with phones via Bluetooth.
I have tested the Android and it pairs fine, and I can make and receive calls.
However it won't allow me to view contacts or make calls from the contacts list.
The Holden Website ( http://www.holden.com.au/owners-info/bluetooth-and-devices/bluetooth-compatibility ) states that this is not possible with the HTC Magic (Android 1.6) but doesn't list any other Android phones. (Window Phones will do PBAP / Phonebook App no problems).
I was just wondering if anyone knows if this is a phone issue, and should work with future updates to the Android's ROM or if it's a Car issue and the HTC Desire will never work with these cars?
OR - is there anything that can be done to get the Android to allow the phones contacts to work with the car?
Cheers
Adam.
OK - Looks like the problem isn't just with Holden.
Came across this thread, and it would appear as though there is a problem with Android and the Bluetooth PBAP protocol.
http://code.google.com/p/android/issues/detail?id=8846