Bluetooth carkit - Nokia CK-7W

---

So I've made the leap from WM to Android with my shiney new HTC desire.

I've managed to pair and connect it to my Nokia CK-7W bluetooth car kit but the recipient complains of a terrible echo their end of their own voice. At my end it's fine.

I've tried adjusting the volume in the car with no effect. I'm guessing that their voice that's coming through my speakers is getting fed back into the microphone, causing the echo.

Anyone experienced anything similar or even better know of a solution??

It's worth noting that this was never a problem with my HTC Touch Diamond.

Thanks

Rob.

Sorry for not answering your question, but how did you manage to connect the desire to CK-7W, I've been trying but no joy .

Again help would be appreciated

It took a bit of fiddling and to be honest I can't remember exactly how I did it.

I definitely set it to discoverable, but it wouldn't find it at first. I believe I had to turn on or off FTP server in advanced settings.

To connect once paired you need to turn on BT on your HTC and press and hold the connect button on the ck-7w for at least a second.

If you get it working please test for echoing and report back

Cheers.

Rob.

same setup here, same echo..

---

Hi,

I have the same car kit, I have the same complaints. Terrible echo. It worked just fine with my previous phones (Kaiser lately).

Cheers,
A.

When I get chance I'll trawl the other android phone threads to see if anyone has come up with a solution.

Cheers for the reply rob, I'll hopefully get it 'paired' tomorrow & feedback regarding echo.

Rich

Same issue here. I have upgraded from a HTC TYTN II WM6.1 to the HTC Desire. After connecting via bluetooth to the Nokia car kit all of my calls suffer from bad echo at the other end. To combat this i have turned the speaker volume down as low as i can hear it which seems to help the other party. (My bluetooth pairing setup perfectly the first time)

I also recall that my TYTN II had exactly the same issue and i had to download a patch from HTC which fixed the issue fully. Maybe the Desire needs a patch from HTC.

Has this issue been submitted to them for consideration?

Re: Bluetooth carkit - Nokia CK-7W

---

This has been a bad problem since view first came out. It seems to be worse on the windows devices but it can and does affect even Nokia phones and still not an upgrade from Nokia.

I ended up having to get new parrots for our company cars as the drivers gradually upgraded their mobiles.

-------------------------------------
Sent from my HTC Desire

I found this thread over on the Xperia X1 forum with a solution they found to work

(See post #4)
http://forum.xda-developers.com/showthread.php?t=478612

I must admit I did this exact tweek a few years ago on my old M700 to get it to stream music via bluetooth to my a2dp enabled car stereo and it worked a treat.

Basically the M700 identified itself as a "smartphone" which the stereo didn't like. So I changed the "Class of Device" (COD) to identify itself as a normal mobile phone which instantly solved the problem.

I don't know if an Android has a registry or if it is editable but if it is identifying itself as a smartphone and it could be changed to a normal mobile phone then it just may get rid of the echo.

Perhaps there is another place on here that this question is better suited?

Originally Posted by neomagik

I found this thread over on the Xperia X1 forum with a solution they found to work

(See post #4)
hxxp://forum.xda-developers.com/showthread.php?t=478612

For those guys changing the device class from smartphone to phone helped. I'm not familiar with Android internals but in /system/etc/bluez/main.conf there's a section:

# Default device class. Only the major and minor device class bits are
# considered.
# Local device class
# 0x400000 - Service class: Telephony
# 0x000200 - Major class: Phone
# 0x00000C - Minor class: Smart phone
Class = 0x40020C

Would that help to to change it? I haven't rooted my desire (yet?). Would someone having the same problem and having a rooted device try changing the device class?