Echo on Nokia Bluetooth Carkit - General Topics

I know this may not be a PDA specific problem but I'm asking for any help! I have an XDAIIs which after unlocking am now using with my work Orange simcard. They kindly supplied me a new Nokia (CK7?) bluetooth carkit that pairs very easily with my xda. Problem being that the person on the receiving end of the call, whether on mobile or landline, gets immediate echo back of anything they say. (Sound quality is excellent at my end) All I can think is that the mic on the XDA is live alongside the carkit microphone causing one to pick up speech and send it straight back. Has anyone else encountered this problem and had any joy in remedying it!!?? Any help great fully accepted as I'm getting fairly reliant on my PDA now and it is very annoying not being able to use it in the car!
Thanks, Steve

You have a Nokia CK7W I expect. Welcome to the club! There is currently no solution for this problem, although upgrading the Bluetooth stack is rumoured to help. I have Radio version 1.13.00 with BT stack 1.0.0 Build 3900 from Broadcom and this problem persists.
So, unless anyone comes up with any other suggestions you are stuck with it for the time being. I wouldn't rule out upgrading to WM5 but I have not heard anything of how the BT performs in that image.
Sorry couldn't be more positive

I am also a member of the club tried everything. The most easy thing to do is to lower the volume of your carkit speaker. This could mean that the PDA is catching up what the other side tells you. But i tried everything, even different profiles (pocketalarm) but it is still there. So let hope someone comes up with that everwanted solution.

Maybe the voice coming out from car kit speakers reenters car kit microphone

Thanks guys, looks like I'm stuck with it for now...

tailazoom said:
Maybe the voice coming out from car kit speakers reenters car kit microphone
Click to expand...
Click to collapse
I had the same setup with my Nokia 6260 and everything worked perfectly. I sold the phone and bought a S100 and now i have this problem, so it is not the issue that the speaker is to close of the microphone. My guess is that nokia uses a different protocol in their BT stack. To ensure that you will use Nokia forever.
I also asked the other side to talk while i putted my hand on the carkit miicrophone. The echo is still there. A new BT stack would be handy.

AE problem
Hi!
nothing about your problem - but something you may interest to hear.
- simple one - Acoustic Echo becomes to Far End user (not you) as result of passing signal from your speaker to your microphone.
- how signal passing from.. to.. - not necessarily by air - and for mobile devices it is usually passing through its case and its board. So if you put your hand on mic - you won't achieve any "improvement".
only what you can do:
- find from what part problem comes - as you have 2 mic on your sytem try to find which one "cause" the problem. Acoustically separate PDA's mic - if echo still presents - the problem exactly in hands free part.
If it is - BT stack software cannot help you. BT stack software is responsible for data transportation. Only if inside new firmware some one put AECanceller software (and hardware) iprovements.
hardware means - physically prevent (provide good case and board design) passing cpeaker signal to mic. Actually this way is quite reasonable - for example HP 2210 PDA has several times smaller and shorter ImpulsResponse compare to Qtek S100. This means that in equal other condition HP provides smaller echo signal. For both devices echo path lies "inside" them - I am not targeting application like conference-room.
Second way is - to use software AEC - in nowadays it is normal and usual function in such device's firmware. So maybe next firmware will have it.
What can you do more - try to play with mic sensitivities and speaker loudness - it may help... a little.

Related

MDA2 Carkit is silent after upgrading ROM

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 ?

Anyone experience with the Parrot CK-3100 bluetooth carkit

Does anyone have experience with the Parrot CK-3100 bluetooth carkit ?
I was about to go for the new Sony Ericsson HCB-300 unit when I encountered the Parrot. Featurewise it looks like a great unit, but I am interested in anyones experience using this unit.
What is the sound quality ? Are all features (like caller id etc) usable with the MDA/XDAII ...
Thanks !
Taco
Hi there,
I have recently fitted the CK3100 & have to say its been really good. It integrates with the vehicle, just like any other professionally available car kit.
That's the good news - the bad news is the XDA II (in all its guises) - still the age old problem of the lack of car kit profile means that the functionality is limited.
Yes, it does pair with the CK3100. Yes it will send and receive calls. What it won't do is make any proper use of the LCD display, nor will it allow access to the address book on the PDA.
In short, it will interact in the same way as it would any BT headset - because that is what it thinks its talking to !
If I use the car and need my handsfree - I have to muse my old Nokia 6310i - which works perfectly - allowing full use of the LCD screen and 100% access to all the data on the phone.
You may wish to check out the other threads on this site regarding the known and ongooing problem with the BT stack on the XDA II.
It's really pathetic that my old nokia beats the more advanced XDA II hands down when it comes to BT integration.
best of luck
Redz
Redz,
Have you tried installing the Pocket Bluetooth tools (http://bluetooth.i-networx.de/index_e.html) to create a carkit profile in the XDAII ?
I've ordered the Parrot and will receive it later this week.
A slight diversion
I hate hijacking but any of you guys know how to get the Motorola car kit to answere calls. O2 blame Pocket Windows 2003. MS blame Motorola. Making calls is fine but answereing is a no no so Ive to call callers back when on the road. Any ideas
GJW
redz said:
Hi there,
I have recently fitted the CK3100 & have to say its been really good. It integrates with the vehicle, just like any other professionally available car kit.
Redz
Click to expand...
Click to collapse
Hi Redz
Tell me....does it only work for the phone function, or does it puts out other sound like mp3 or Tomtom nav directions ?
thx in advance,
iGadget
igadget said:
Tell me....does it only work for the phone function, or does it puts out other sound like mp3 or Tomtom nav directions ?
Click to expand...
Click to collapse
Phone only, and just using a headset profile, without the option of adjusting the volume which results in (too) loud sound, causing echo.

Parrot CK3300 BT car Kit

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 !

voip not through loud speaker possible?

did anyone succeeded using voip through the normal phone speakr? (the ear speaker, not the music/loud speaker), preferably with the integrated wm6 voip?
if so, what is your rom type and version?
what is the size and date of your \windows\rtcdll.dll?
thanks.
not sure if any non real phone apps got access to that speaker
if it is possible then i believe that programs have to be written to use it
and skype being developd as a pda program rather then a pdaphone program
prob use the only speaker normal pda's got
i could be wrong though
maybe you can get it ot use a bluetooth headset with less hassel
HEllo,
I discovered yesterday the issue with the speaker and went through many forum but did not find any positive answer on how to get the sound directed to the good speaker.when using SIP.
I even did not understood if it is a problem of the touch cruise only or a general issue ...
Is the issue solvable - So I can still hope - or is there any hardware limitation
This issue means that using SIP with the Touch cruise is not possible except if we agree to have everyone in the room listening to the phone call ...
So if you have any positive information/solution ... Thank you
Franck
Search for a sip client agenet mobile or something. It's not exactly the name, but I can't dind it again. But this one is the only one that works at least on some of the smartphones with the earspeaker. And they want to add more supported devices in the future.
Generally it's a general problem, not a TC problem. The telcos just don't want a proper SIP integration in WM or they even deactivate it completely. It's a kind of squeeze to Microsoft. But MS won't disrespect them because they all like money.
Thank you for the answer.
I found Agephone mobile. Is it the one you were thinking about ?
I just tried it but no success, sound still come out through the rear speaker ...
Franck
Yeah, that's it. I've tried it right now as well but no luck. It's quite useless, as long as the ear speaker is not working. But it's not their blame. On the Trinity it's working allegedly.
Maybe we can them them a log. For some models they fix it.
phone speaker
it must work cause it works for me.
Hello papasieg,
Does it really work for you ? with the sound coming from the normal sound speaker and not the rear one ?
Take care that a trick exist with some SIP softphone which reduces the level on the rear sound speaker, giving the impression that it comes from the normal sound speaker but is is not the case ...
I am going to have another look at agephone
I had a discussion with eyepmedia (they produce eyepcommunicator). They answered:
Regarding our SIP softphone - eyeP Communicator for Windows Mobile – we have not yet made any certifications (nor tests) with the HTC Touch series. Until last year, previous HTC devices (HTC TyTN, 9100, etc) exposed a hardware bug which did not allow to handle the back and phone speakers correctly. But we hope this issue has been sorted out by HTC on new devices.
For information, we intend to make a new certification versus an HTC Touch Cruise before the end of the year. If your project has shorter timelines, then I suggest organizing a conf call to a date/time which works fine with you.
Franck
New test with Age phone
I made a new test with Agephone Version 2.63 (2008.08.28) and did not managed to have it working properly (I tried several configuration for the audio device).
So if someone has a working configuration ...
Sincerely,
Franck

Ms bluetooth stack vs broadcomm stack

My touch pro seems to have real bluetooth issues with my JVC KD-NX5000 stereo system. My kaiser worked flawlessly with it but with the touch pro it wont pair at times and when it does it wont let me use any of the many functions that the stereo offers (voice dialing, downloaded phonebook, etc) I assume this is a problem with the ms bluetooth stack and was wondering how tough of a job it would be to switch to a broadcomm stack or if anyone has thought about making a custom rom with the broadcomm stack. Just curious if Im the only one with issues with wm 6.1 and bluetooth.
i have the same problem with my diamnd anbd jvc car audio
Slightly OT rant:-
I had the opposite problem with pioneer + broadcom...
Pioneer only looks for handsets which identify themselves as phone or smartphone, and my device identified itself as a pda.
I actually told pioneer about the problem, and rather than forwarding on to the developers, I got a stock reply:-
"This phone is not on our compatibility list" (so we don't care)
So I went and got an MS based phone (you can change it to smartphone with a regedit).
Never buying pioneer again...
- Anthony
Similiar issue with my opel carkit.
Tried to make the broadcom stack working, but got a memory error when opening its blue tooth manager.
After uninstalling, bluetooth didn't work at all anymore, needed to perform a hard reset.
Has anyone successfully installed the broadcom BT stack on the touchpro/raphael?
I found that my Touch Pro would pair and then drop out when connecting to my Kenwood DDX5032 car stereo bluetooth adaptor. I couldn't dial from the Kenwood kit, couldn't use A2DP (wouldn't even connect), and really couldn't use any Headset Profile functions at all.
I persisted with pairing and unpairing in different ways (you can initiate the pairing from the Kenwood itself rather than the phone), but nothing really worked.
Then trinode's post about changing a registry setting sent me down that track and now everything is working fine
I found the relevant setting from http://forum.xda-developers.com/showthread.php?t=290871, which is [HKLM\Software\Microsoft\Bluetooth\sys\COD], and then changed the HTC TP default value of '5898764' (decimal), to the value from my old Dopod838Pro, which was '5374228' (in decimal).
I didn't even need to repair the Kewood to the HTC TP - it just worked straight away, as if it said "Oh, sorry, did you want me to work? I thought you wanted me to be in 'stupid' mode! My bad - everything will work now."
So all good, and thanks to trinode for pointing me in the right direction.
Codenix.
After hard-resetting my Touch Pro to fix another separate issue, now this problem has come back and this time changing the COD value hasn't fixed it. It would appear my previous post may have attributed my success to the wrong thing
The search for the answer continues!
I found a firmware update for my Kenwood's bluetooth adaptor which fixed the problem. I don't know why it ever worked at all before this update, but there you go!
I'll create a separate thread to share this with others in case anyone else out there has a Kenwood bluetooth kit and a Touch Pro or a Diamond.
Thanks.
The thread I created re the Kenwood is at http://forum.xda-developers.com/showthread.php?p=2835805
@ Trinode
Pioneer sent my unit back, but never told me that my phone was not supported. Where did you flag the smartphone in the registry? Did it fix the BT connection/unti reboot issue? I had a AVIC F500BT (sold it) now have a AVIC X910BT same issue as the 500 had.
@ Trinode. I found the hack , tried it, but it still doesn't resolve my issue. Are there any other mods out there for the BT Stack prob?

Categories

Resources