Related
Hi,
I've got a problem with my carkit (O2 XDA-Carkit) after I upgrade to the new ROM-Version of T-Mobile (1.60).
With the old Rom-Version, the carkit works as a loadspeaker for all kind of sound. The voice-instructions from tomtom for example, came out of the carkit-speaker loud and clearly. Each kind of sound, the device made, came out of the speaker of the carkit.
Now, after upgrading to the new ROM, only the telephone works with the speaker of the carkit. With Incoming or outgoing calls I can use the carkit as usual...the speaker works and the mikro works also. But every other sound (e.g. tomtom voice-instructions) came direktly out of the speaker of the mda2 in a poor quality.
Some hints, how I could use my carkit again as a speaker for all kind of sound without goinig back to the old ROM ?
Any other kind of hints...maybe to use a bluetooth headset therefor (so that all kind of sound came out of the headset....not only telephone...I've got a Plantronics Headset...but also only the telephone works)
thx for help
best regards
rob.
Yep.......I have the same problem here.......don't know why they changed settings on the handsfree profile here.
Another thing you will find out is that the charging is very slow on the XDA carkit with the XDA II. If you run TomTom, Yeti and a bright screen the xda II will not charge, but drain!!
It has something to do with the wiring of the interface, but unless someone will come up with a solution I will go for a new carkit or a BT solution. (It's a bloody shame though it doesn't work properly with the XDA carkit! :evil: )
Hi,
the charging-problem is also a mess.
I think, the problem is only the GPS-driver from tomtom. In my tests, only when the GPS-driver is loaded, the battery-power goes down. With stopping the GPS-driver, the battery will charge again, but only, if the battery-power is more than about 75 - 80%.
If the battery is less than 75%, it will not charge at all, even if, there is no App runnung and the screen is off.
You said, you will go for a new carkit or bluetooth-solution. Do you know a carkit or bluetooth-solution, wich offers the feature, that all sounds (tomtom instuctions...etc.) came out of a loadspeaker or thru a headset (without connecting the wired headphone ;-)
As far as I know, at the moment all devices works only with the telephone-funktion....
best regards
rob.
Same here,
i have build my own carkit, and have put ground to pin 19,
sound was normally going though the connector to my car stereo
now it doenst anymore :evil:
I am sure this isnt a hardware thing it is software
could be the settings on the handsfree profile. on the xda2...
this is very very frustrating. just being finished with my carkit and now i cant use it anymore
also you cant set the phone to speakermode anymore..
I am sure this isnt a hardware thing it is software
could be the settings on the handsfree profile. on the xda2...
Click to expand...
Click to collapse
Does anybody know how to change this back?
I found that the registry points to a certain file in your windows directory: HandsFree_Dll.dll
(I found this here: HKLM\Services\Handsfree)
Can someone with the old 1.03 ROM please upload this file so i can try if this solves the problem...
TIA,
Max
Akira, Max :
I am building my own car kit, and have no success.
I do not obtain audio out with or without grounding pin 19.
I'm running Rom 1.60.00WWE.
Did you solve your problem ??
I must correct my last update.
I obtain audio when in phone mode, but not during playing waves or TomTom directions. Even Ring Tones do not go out trough the bottom connector.
So is it a software problem ?
Can it be corrected ?
On http://wiki.xda-developers.com/wiki/Connectors it is clearly explained that the MDAII connector has following audio-related pins:
1 CAR_MIC_IN
3 CAR_AUDIO_R
4 CAR_AUDIO_L
With the original T-Mobile MDAII carkit ALL audio (phone & pda) is said to go via these pins
With the XDA2 carkit only phone audio (after accepting a call) goes via these pins.
Maybe this has also something to do with the switching of the in-car signal on
19 CAR_ON
:idea: CAR_ON is connected to +6V on the car charger which makes the phone go to speaker mode immediately when picked up or dialing.
>> This is the behaviour of the XDAII carkit!!!
When this pin is connected to ground, the internal mike and speaker are turned off, and audio input is taken from the audio input pin on the connector.
>>Is this the behaviour of the MDAII carkit??
:?: So: Would it be worth trying to connect pin 19 to ground instead of +6v inside the carkit cradle??
Can't believe no-one with a XDA2 / Expansys carkit is looking forward to solving these issues too . . .
I checked this a couple months ago when I dismantled my expansys car kit. I'm sure I found pin 19 is already grounded on the carkit. With regard to this part of the pin 19 description:
"...CAR_ON is connected to +6V on the car charger which makes the phone go to speaker mode immediately when picked up or dialing. "
"Speaker mode" in this case means the handsfree mode, where the integral xda II speaker is turned up to "distortingly loud" and the internal mike is used in call, similar to what happens if you push and hold the green/send button during a call. If pin 19 is raised to +6V, this will be the xda II's default behaviour with the phone function. This is so you could plug in a simple car charger that puts pin 19 at +6V and that provides only power to the unit (no mike, speaker etc) and allows you to make/receive calls through the builtin speaker and mike without having to hold the xda to your ear.
I feel that if pin 19 is grounded, all audio should be sent through the bottom connector and then into the car kit. Indeed, this is the case with some ROMS / software versions, but not in others. I therefore think it is a software/ROM issue.
I found with my uk o2 xda II, with both the launch ROM and 1.60.50 ROM I got the same behaviour - the unit did not send pda audio to the bottom connector whether pin 19 was grounded, raised to 6V or left floating. Yet other HTC Himalaya owners have reported things differently with different ROMS.
Firstly I thought this to be a s/w issue as well.
But then: The T-Mobile MDAII carkit seems to be working as desired no matter the rom version . . .
Could we get together a list of device/rom/carkit combinations with the actual behaviour in sorting this out?
ANYONE: pLEASE POST YOUR CONFIG HERE.
MINE:
Config: MDAII / 1.60.00WWE and 1.60.36 ext / XDAII Carkit (Expansys like)
Bahaviour: Only phone audio via carkit when in a call
Configs
I am having an identical problem
Build: 13252 - 1.60.00WWE EXT. 1.60.50
I have an XDA I've been messing about with in the car to try to make myself an in-car kit and that was all going fine (Although the phone is now stuck in in-car mode, think i've blown something up ). For the kit I made there, +6v on pin 19 output all audio to the connector.
I then bought an XDA II and in-car kit, wired it all in and then tried to play audio through an in-car cassette adapter lugged into the headphone socket that's built in to my in-car kit. The phone outputs to the speakers fine, but the audio, (Mp3 and the like) won't go to the conncetor at the bottom. (Note that the in-car kit's jack socket is driven off the 22 pin connector at the base of the XDA II)
I'm dissapointed that it could be a softwaer problem, although surely someone somewhere must know a way to force the software into in-car mode constantly and playing the audio out?
Any solutions then let me know cos I'm really irritated that I've just spent £150 on the in-car kit only to find that it don't work yet!
Roll on the XDA-Developers Special Ed. ROM for the XDA II, I bet that'll fix the problem!
Keep me posted on any updates,
Will
**********************
Just done some more reading on the forum and cam accross this
http://forum.xda-developers.com/viewtopic.php?t=8346&highlight=car+automobile+mode+xda+ii
not sure how easy it will be to change the dll files over, anyone with some experience in doing this fancy having a go first and letting me know how it gets on? Is it possible to do? What do I have to do once I mess up the ROM on the pda by overwriting a dll file? Can I just hard reset?
Just letting people know that the Parrot CK3000 car kit works great with my XDA2. It only uses "headset" mode, so functionality is limited, but it routes the calls through the car speakers and mutes the stereo, so that's all you can really ask.
On my Alfa, I couldn't use the standard ISO connectors, as the car has a separate amplifier in the boot, but chopping the ISO connectors off and connecting the wires separately to the "telephone in" connectors on the back of the radio worked just fine. I can even adjust the volume of the phone call via the steering wheel audio controls!
There's a reassuring "beep" when I turn on the ignition to let youknow tha the devices have bonded and every few days, something goes skewey on the PDA and I have to do a soft-reset to make the bluetooth bond work again, but otherwise, it works fine.
I've put an icon on my PDA for the warm-reset, so that I can do it easily in the car if I realise that it hasn't bonded automatically.
The only real glitch I've found is that if you get to your destination whilst still on the phone, I can't find any way to transfer the call back to the handset without terminating the call - any help on that would be gratefully appreciated.
Good to hear it works, I have a CK3300 with the BT GPS Functionality on route for review.
In asnwer to your question, to hand over the BT headset call to the phone just tap the 'Headphone' Icon on the status bar of the XDA.
Darren,
Funnily enough, I was just outside in the car experimenting when you replied.
Sure enough, if you tap the headphone icon on the PDA, the call is successfully transferred back to the PDA and you can carry on the call directly on the PDA.
If you then press the green button on the car kit, the call will also transfer back to the car kit again.
But - Here's my last issue - If you get into the car with a call already in progress on the PDA and then turn on the car ignition, the car kit beeps to confirm that it has bonded, but I can't find any way to actually transfer the open call to the car kit....
Finally - I've come to the XDA forum for a break from Pocketgps.co.uk! I usually spend my evenings on your site. Tonight, for the first time in weeks, I thought that I'd go and seek other company. Who should be the first to reply to my post here but you!
You're going to tell me now that you also drive an Alfa and that you too frequent the alfaowner.com site as well aren't you!!!
Cheers Darren.
Ah well you see we obviously share a passion for gadgets but not Alfa's, current car is an X-Type shortly to be replaced by a Discovery and yes I spend time at both of their owners ites as well (Note to self, need to get out more!).
I think I'm correct in saying that you can't hand over an active call to a BT Handsfree be it headset or car-kit, I suspect this is a limitation of the XDA's BT Stack (thanks Microsoft NOT!)
I shall leave you in peace now, you've probably had enough of my ramblings back at home base ;')
Is this the same kit: http://www.expansys.com/product.asp?code=PAR_CK3000
There is also an upgrade http://www.expansys.com/product.asp?code=FLS-KIT but it doesn't say what you get for your £45.
Any ideas?
alfiejts said:
But - Here's my last issue - If you get into the car with a call already in progress on the PDA and then turn on the car ignition, the car kit beeps to confirm that it has bonded, but I can't find any way to actually transfer the open call to the car kit....
Click to expand...
Click to collapse
Hit the green button on the carkit, that should do it.
If not, install the XDA2 Bluetooth tool, and retry...
Nope - Green button is documented as being the way to do this for most phones, but it doesn't work with my XDA2....
I did try to install Bluetooth tools ut then couldn't get the devide to pair with the Parrott at all, so I hastily removed them.....
I'll think that I'll live with as it is, now that everything else is stable and works OK....
I have tried searching the forums and can't find much Info.
Is anybody here using the above system for telephony & GPS; If so how do they intergrate/do they work well on the XDA II (I have ROM Version 1.72 with Radio1.17)
I Know about the headset profile probs not giving full functionality of the Handsfree use of the car kit but this doesn't bother me to much as long as I can Make and receive calls.
Thanks in anticipation!
I was going to get a CK3100, but heard so many problems regarding build quality, and lack of support, I got a HCB 30 instead.
It did not help when I tried to e-mail parrot for advice and 3 different e-mail adresses bounced back.
Works Perfect!
Just had the CK3300 installed today and it works perfectly - I Knew some of the functions didn't work because the XDA2 only supports headset profile but once you have transferred your contacts to the kit via bluetooth it works well.
Also the GPS works well with CoPilot 5 live; it picked up the signal straight away ; well pleased with this set up!!
same to me have the ck3300 tested with qtek2020 - works fine. problems with 9090 but after bluetooth update now it works fine. No tests with S100 at this time.
tested GPS with destinator 3 and map&guide fleet navigator and mobileobjects fleet management system.
don't use bluetooth tools after Rom 1.66 :!: CK3x00 didn't work aber installation of this
Set up
Just had the CK3300 installed today and it works perfectly - I Knew some of the functions didn't work because the XDA2 only supports headset profile but once you have transferred your contacts to the kit via bluetooth it works well.
Also the GPS works well with CoPilot 5 live; it picked up the signal straight away ; well pleased with this set up!!
Click to expand...
Click to collapse
Any tips on setting up the CK3300 with my XDA2?
Just had the car kit fitted - i need both nav and handsfree functions - but i am not sure that i have got the phone and ck3300 to bond properly. So everything is 'greyed out' on the parrot.
Using ROM 1.72.00WWE (1.72.181) and radio 1.17.00
Thanks for any help received.
If everything is greyed out then it isn't bonded properly!
Step 1
Delete the pairings you have from XDA2 and car Kit;
Step 2
On the car kit turn the control knob untill settings appear- then scroll to 'Advanced Settings' - 'pairing a telephone' - 'windows CE device'
Step 3
Now search for devices using your XDA2 and the car kit should be shown.
Step 4
Enter passcode 1234 and accept headset and serial profiles when shown.
PAIRING COMPLETE
to access your phonebook you need to transfere the contacts via bluetooth to the car kit.
Hope this helps
XDA2 CK3300
Managed to get the GPS set up (fiddling with COM ports - even imbeciles strike lucky sometimes)
Some items are now in black. However, I am not sure that I have done it right as I cannot get it to use my phone to make calls or receive them. Which is exactly why I bought it in the first place.
So, please (please please) can you tell me how to exchange my phonebook?
I am going to sit in the car right now and have a go at your bonding advice...maybe all will become clear (but that is not often my experience!)
Thanks again for your help.
You need to bond the phones in the manner I described or it will not work ; this is clearly ststed in the Parrot instructions and on their website.
(I have noticed a strong correlation between people who do not read instructions and complain things do not work!!) - Joke
You also need to make sure your headset profile is active on the XDA 2 for it to work. Again reading the instructions for the phonebook - you tap and hold a contact on the XDA2 and select 'beam contact' - 'via bluetooth' the bluetooth search then comes up and the car kit will be found you then 'tap to send'
Now i have the opposite problem!
Believe it or not, I have now got the XDA2 and the CK3300 bonding automatically so I can make and receive calls whilst driving. It works pretty well (occasionally makes an awful noise, but only occasionally). I am impressed.
However, once I had done that, the GPS is undetectable. I have tried all sorts of combinations. I have checked the instructions - and selected the long code (ends in 9600) but I am not certain that I am using the right com port. I have tried most of them without success.
Oddly, this is the one thing that WAS working before I got the car kit to work (for calls). Somehow, either I have lost the right settings OR the XDA2 won't do both (although I read somewhere that it would) OR my ROM needs updating (uh?)
Please help.
BTW, I am due a phone upgrade - I love the xda2 but would consider getting another phone if necessary, if anyone can recommend one that is fully CK3300 and TomTom compatible.
I don't use Tom Tom myself but from reading these forums I think you need to install the patch on their website to allow Tom Tom to use the correct Port .
Your Car Kit also needs it's software updating if it makes a noise like you say. On the Car Kit go to > settings-advanced settings-information and you will find the software version (sounds like 4.03) if it makes a noise. The latest on the Parrot website is 4.10b and this will fix the noise issue.
If you need help installing this let me know.
The best Phone is surprisingly the Old Fashioned Nokia 6310i - it has a good bluetooth stack and uses the handsfree profile rather than the headset so contacts sync automatically but if you require live traffic info best stick with what you got as the Nokia will not pair with the XDAII and the car kit at same time.
Which COM port?
For the moment, I have a temporary solution.
However, I have updated the TomTom Navigator software and the GPS, but still don't know which port the GPS in the CK3300 should be connected to.
Any ideas?
And, thanks Nikpro for the excellent help so far - you are a true altruist and a star!
The outbound port on the xdaII is port 5 by default
On XDAII go to Settings - System tab - Bluetooth settings and make sure you check the tick box for outbound COM port.
There is also a chance you have deleted your serial port profile so tap on the bluetooth icon in the Today Screen and go to bonded devices. Select the CK3300 and delete partnership (do not delete pairing from car kit end!)
Then search for new devices from the XDAII and the CK3300 will again come up; create a new partenship and everything should be good.
Still having problems
Oddly, I still cannot use the GPS on the CK3300.
I am using my old TomTom at the moment for GPS and the CK3300 for headset - which works fine, but I wanted the CK3300 to do both.
When I try and reset the GPS to the (series of numbers ending in 9600) as stated in the info and the instructions (Nikpro, take note - I have read them - but your comment made me laugh), the TomTom just 'freezes'. Wait - and wait - and wait - and when it reincarnates itself, no GPS at all.
I am using the 1.72.00WWE rom and radio 1.17.00
I think that I have tried every permutation for the COM port.
Has anyone any ideas? Please?
When you initially pair your XDA to the car kit do you get a message about serial connection show on the screen? The problem must be with the tom tom software as with copilot and mapopolis it works fine? or the way you are pairing the two!
What software version is the car kit? PLEASE DESCRIBE HOW YOU ARE PAIRING THE DEVICES??
Hi all, 1st post and all that.
Have you tried falshing the parrot with the newest rom, mine picked up enough to make and recieve call, but i flashed my xdaII with 2.02.T1WWE this morning and it works even better.
Hope you get a result
nikpro said:
I don't use Tom Tom myself but from reading these forums I think you need to install the patch on their website to allow Tom Tom to use the correct Port .
Your Car Kit also needs it's software updating if it makes a noise like you say. On the Car Kit go to > settings-advanced settings-information and you will find the software version (sounds like 4.03) if it makes a noise. The latest on the Parrot website is 4.10b and this will fix the noise issue.
If you need help installing this let me know.
The best Phone is surprisingly the Old Fashioned Nokia 6310i - it has a good bluetooth stack and uses the handsfree profile rather than the headset so contacts sync automatically but if you require live traffic info best stick with what you got as the Nokia will not pair with the XDAII and the car kit at same time.
Click to expand...
Click to collapse
Use Bluetooth tools www.bluetooth.jazztel.es
and edit the registry under hkey local machine, builtin, BTIBserial, rename BTIBserial.dll into BTIOBserial.dll
and go Start, Settings, System, Bluetooth settings and check both inbound and outbound.
Delete ALL paired devices, reboot, and re pair them.
You will now have an option for two serial ports, one for each device.
This is the only way to do it if you have two devices that need a serial port. If you have a third, you are SOL.
Normally, the stupid programmers who made the MS BT program, made it so it only had one dynamic port for BT. Some people would experience having to reboot before switching BT devices, most would have to re pair every dam time.
The new 2005 does not have this problem but it has other bugs.
They smart people at MS changed the databases so Mapopolis and other third party programs can not read the contacts or have other bugs with them. Plus the 2005 version here limits your memory.
The 2.02 - 2.06 will NOT work with Hands Free and most car kits need it and if you have caller ID via BT, you are SOL too.
The 2.20 is a stable and a good OS and the Hands free works much better. The down side is, when I get a call on the call waiting, even if I did not answer, it would disconnect the BT headset and no sound through the phone too. I would have to, click on Tools, Hands Free off, tools Hands
Free on before it would work. I have lost many clients this way.
I decided to disable call waiting in the phone settings and it only has a few bugs now like I have to turn off and then back on the BT headset after ever call or it would revert to Headset mode.
The caller ID will not display if the call is in the history of my BT headset or if it is in my contacts database.
I mention my BT headset because it is like a car system when used in Hands free mode.
Good luck, let me know if you have any trouble now.
Parrot 3100 with XDA II
Hello,
I have just put in a Parrot 3100 and it works fine as a handsfree phone.
is there any way when I am not in the car though to use my Jabra 250v headset without rebonding and selecting it as the preferred headset device?
I can't seem to switch between the Parrot and the Jabra when the other one is not in use without repairing.
Thanks for any advice
BT
Try turning of one and turning on the other and soft reset..
Ok, I have just spent my entire weekend trying to get my Qtek 9090 to communicate to my newly installed Parrot CK3300 (with GPS). I have read the manual about 3 times from beginning to end, know the whole website parrot.biz by hard (ugly site BTW), and have tried about everything in configuring, but with no success so far.
Initially I had the 2 devices paired to each other, but after I installed Tom Tom 3, it is impossible for me to get them to pair again. Nevertheless, the 2 devices "see" each other (when asked in "Linked devices"), but they can not get to communicate. From all the stuff I have read on forums and sites, it seems that I need to upgrade my Bluetooth version, but I have no idea how and where to start this procedure.
Can anyone help me out here ?
Any tips are welcome !
Ok - I've got the Desire, and I'm liking it.
I've also got Spotify, and it's excellent.
But Spotify in the car would be amazing.
So, question is, would the above kit be a useful purchase?
This particular Parrot comes in 3 flavours, the bog standrd MKi9000, but there's another two which also have a small screen accompaniement.
Question is, which should I get?
Or should I get something else entirely?
I like the idea of FM transmitters, but pretty much across the board, they are meant to perform poorly. I also don't like the idea of being restricted by having to instal some of them in the cigarette lighter - I'd rather the stero component was hard wired if possible (and easy to fit myself as I'm on a budget).
So, any advice peeps?
I have a parrot SK4000 and it's terrible.
I've got a Parrot Mki9200 and it's great. It's a Parrot device so you have to expect the occasional oddity but I just get in the car and I have bluetooth handsfree and A2DP streaming from my Desire. I'm even contemplating changing my earlier Parrot 3400GPS in another car.
Haven't tried it with Spotify but I can't see why it wouldn't work. Works fine with Google Maps Navigation, although occasionally the A2DP streaming takes a second to kick in which means you miss the very first part of the voice instruction.
Edited to add that you can plug the Desire into the USB connector which both charges it and allows you full onscreen browsing of the media on your Desire. Select songs by album, artist, playlist, folder, etc.
Ian A.
Thing is, do you need the small screen that comes with the 9200, if you only use it with a Desire? I mean, what exactly would you use the screen for, assuming you've already got your Desire on a dashboard mount anyway?
I'm clueless about in car bluetooth connectivity and suchlike, so any advice is great. You can get the mki9000 quite cheap if you look around, but with the screens, you add a fair bit to the cost.
So - any other advice?
I had a MKi9100 Parrot which had to be returned as it had a fault. However, i was really disppointed with the quality of the music, as it uses its own inbuilt amp, not the car stereo amp. Quality suffers as a result.
With the MKI9200, I believe that there is a way to wire the kit, so the music plays through the car stereo, but you then have to have a separate speaker for phone calls, else you won't hear calls when the stereo is off. A good source of info can be found at the Parrot forums.
The benefit of the Parrot gear is that you can integrate it with your stearing wheel controls (if fitted), although you will need the additional control module.
Given my rather unreliable experience of Parrot gear, I'm looking to ditch my present Parrot CK3000 unit in favour of the Bury cc9060 kit. Not only does this kit have A2DP (music via bluetooth) and the ability I believe to route music via the stereo (please check to confirm), but most impressively it has multipoint - the ability to connect 2 bluetooth phones at the same time. A real bonus for those of us with 2 mobiles....
Hope this helps.
Parrot
I have the LS3200 and there is a lot of problems with the Desire sync of contacts from phone
This is exactly the kind of info we need.
I hadn't even heard of Bury kits, so cheers for the heads up...
crazybones said:
With the MKI9200, I believe that there is a way to wire the kit, so the music plays through the car stereo, but you then have to have a separate speaker for phone calls, else you won't hear calls when the stereo is off. A good source of info can be found at the Parrot forums.
Click to expand...
Click to collapse
The Parrot instruction manual is wrong on this. If you have a decent car stereo, you can wire a line-out from the Parrot to the Line-In from the car stereo and use the car hi-fi amp for streaming music. You still connect the speaker bypass which kicks in if you get/make a voice call. I've confirmed this with Parrot tech support.
As for the screen, if you've got (or are getting) the Desire car dock and you only listen to music from the phone, I guess you don't need the screen. However I find that I use the SD card & USB connection to listen to music as well so the screen is pretty essential. The 9200 is only around £20 more than the 9100 so it was a no brainer for me.
However I did look at the Bury devices as well. I do expect the Bury ones are slightly more reliable (although the 9200 is better than expected) but I found them lacking in some features.
Ian A.
ray4438 said:
I have the LS3200 and there is a lot of problems with the Desire sync of contacts from phone
Click to expand...
Click to collapse
I've also got a 3400 (same thing but with GPS, not the most reliable of devices!) and the best way is to delete all contacts, re-pair the phone and then send a multi-contact VCF file to the Parrot. You can create a multi-contact VCF from MS Outlook if you have that.
I've managed to get multi-number contacts (so you can do voice dialling with "Call... Alex... Home"), contact pictures and all features working correctly with the Desire. It did take some fiddling though, especially compared to the 9200 which was pretty seemless.
Ian A.
Just got an MKi9200 and installed in my 2008 Civic. I am loving it so far!!
I have paired my Desire which I plan to use for calls and sat-nav using the bluetooth audio feature.
I also plugged in a 32Gb USB stick which I will be using for playing music.
All this works well so far, except for a few little niggles.... I am hoping someone can help
1. When the phone sync's with the Parrot I get a message "File format not supported" which appears, disappears and appears again during the sync. Its possibly contact related (either pictures or the contact themselves) - can anyone advise??
2. When the sat nav (Copilot) gives directions, the sound comes out of the Desire AND the cars speakers. This is fine but the phone sounds up first, then after a 1/2 second delay the same instruction comes through the cars speakers. Any ideas on how to get them to play at the same time or mute the phones instruction but still hear the car speakers?
Any help gratefully received!
Thanks
zippyioa
I use the venturi mini on mine and it works flawlessly the only problem is it does plug into the lighter socket, I did end up buying a 3 way extension plug for the socket though off ebay so it is now mounted elsewhere and i still have 2 spare lighter sockets and a usb charging port on it as well as on the bluetooth car kit.
the kit was about £20 off of ebay of £50 in the shops, phonebook dl all ok even transmits it on the head unit if it has RDS on it.
ray4438 said:
I have the LS3200 and there is a lot of problems with the Desire sync of contacts from phone
Click to expand...
Click to collapse
I have the exact same model, had the exact same problems but cured it.
I wrote a post about my experiences http://forum.xda-developers.com/showthread.php?t=668042 , but I think the upshot is actually to break all the "links" in your contacts.
My LS3200 works flawlessly now.
advice please
I'd like to get Bluetooth handsfree set up with my Desire in my Toyota Rav4 (2005). Am looking at the following:
1. Brodit active cradle (hardwired to car, avoiding cigarette charger)
2. Parrot BT kit
So, my questions are: which Parrot kit am I best getting (dont want to spend a fortune, but would be nice to stream music from Desire through stereo speakers), & can anyone recommend a company to do the installation professionally in London? (as much as I'd love to do it all myself, probably not a good idea to open up the dashboard etc?)
Its a no brainer to go wth the MKi series, thebosh, but it depends if you want clutter on your dash or keep it clean and minimalistic.
But following the parrot forums loosely, its seems that more and more people are having difficulties with the 9100 and 9200 than the 9000 due to the added screens and with displaying what they wantr and how they want it, especially with software updates, changes to phonebook layouts and intergrations with social feeds etc.
For me, it had to be the 9000 with just the remote, which I mounted on a spring clip and then to a face vent.
I also got a brodit active charger (the one with the hardwired charging lead) for sat nav purposes, so I saw no need for an extra bluetooth screen you have to mount somewhere.
I too am planning to cut the cigar charger plug off and hardwire it, just need to get around to it.
The sound quality from the desire to the parrot 9000/9100/9200 BT is exceptional, and the music bass/treble is well balanced.
As for installation, register on the parrot forums and ask there.
You'll be surprised how many installers are registered for troubleshooting and can give you some sort of price/advice on whos doing it in that area.
I put mine into my 206, and its no sweat.
Thanks for the really helpful advice Touch Graphite. The 9000 seems perfect for my needs.
Had my first quote this week for professional installation - £244 for the lot. No idea if that's any good or not!
Will do as you suggest re. Parrot forum, as it would be awesome if I could do it all myself!
(For info, the quote came from avrmobiles.co.uk, & guy I spoke to warned me to rather go for the Bury 'Music' as he had experienced issues with Android & Parrot devices...)
Sent from my HTC Desire using XDA App
Zippy,
There are alot of bugs when it comes to the screened versions of the Mki series, hence my recommendation of the 9000.
I have no such problems with any sort of delay in sat nav commands, music quality or phone sync from my desire.
Only niggle I get is blipping when im canning the music at full chat from my desire on fuller vocal songs,
but using the Mix-zing app, and turning up the buffer size does help.
Keep It Simple.
IPAddis said:
The Parrot instruction manual is wrong on this. If you have a decent car stereo, you can wire a line-out from the Parrot to the Line-In from the car stereo and use the car hi-fi amp for streaming music. You still connect the speaker bypass which kicks in if you get/make a voice call. I've confirmed this with Parrot tech support.
Ian A.
Click to expand...
Click to collapse
Hi,
This is exactly the kind of solution I am looking for! I just got my MKI9000 installed and unfortunately the installer routed all 4 speaker output through the cutoff and not through the line-in.
I have a Skoda (part of the VAG family) and I am now trying to cross information so I can come back to the installer and get him to fix the installation (he will learn a thing or two from the infinite internet wisdom )
Any more information you can share on this option?
Moshe