Database Info

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?

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?

neomagik said:
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
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
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?

Hey aszeman,
What application did you use view the contents of that file? I can browse to it but can't open it.
If rooting is what it takes to change the value, I'll give it a try.

neomagik said:
Hey aszeman,
What application did you use view the contents of that file? I can browse to it but can't open it.
If rooting is what it takes to change the value, I'll give it a try.
Click to expand...
Click to collapse
I did not check it on the phone as I could not read the file, but I used a downloadable stock rom.
I run the RUU updater, checked with "filemon" where it temporarily extract content. From rom.zip I extracted system.img. From that with unyaffs I extracted the system content. Browsed that around, and found the bluez setting there. I'm still hesitating about the rooting as there I see some issues floating around bricking USB/BT/FM. If someone has already done the rooting he/she could give it a try to change CoD.

You're obviously more 'in the know' than I am about these things.
Am I right in saying that if my phone was rooted I could view and alter these files directly on the phone?
I'm guessing that there are not that many people who own an HTC Desire, CK-7W car kit and who have rooted their phone. I hope I'm proved wrong but if no-one comes forward soon we'll have to take the plunge.

neomagik said:
You're obviously more 'in the know' than I am about these things.
Am I right in saying that if my phone was rooted I could view and alter these files directly on the phone?
I'm guessing that there are not that many people who own an HTC Desire, CK-7W car kit and who have rooted their phone. I hope I'm proved wrong but if no-one comes forward soon we'll have to take the plunge.
Click to expand...
Click to collapse
This is my first Android phone. Zero experience. I'm just guessing and making assumptions, and I'd assume with root rights one can change that file.

So I've now rooted my phone and changed the Class = 0x40020C to Class = 0x000200 and guess what.....no change.
I also got in touch with some people in the HTC Hero forum who have a CK-7W and they confirmed that they have no echo.
I then requested if someone could post the contents of their bluez folder which is different to ours. I copied the files onto my device, rebooted and still no difference.
Then, just for a test, I deleted everything from the folder and rebooted. Again no difference but to be honest I was surprised that it still worked at all.
It must be using information from elsewhere but I'm damned if I know!

I have the same problem with the Nokia CK-7W carkit and an HTC Desire smartphone.
I've had the problem before with my Xperia X1 (like someone said earlier) but then the problem was fixable within the registry of the phone.
My HTC Magic is paired without any echos or other problems, but still the HTC Desire has an terrible echo for the other party.
The answer of HTC was "buy a newer carkit", but that is insane, the basics are the same and it is depending on the phone so...

Hello,
I have the same setup and guess what...the same problem. I've updated the SW today but still no change.

Good news, the DeFrost Froyo rom has completely eliminated the echo, at least for me anyway.

The problem still exists... And i don't want to root my phone and flash a new ROM on to it.

Me also !
neomagik said:
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.
Click to expand...
Click to collapse
Incredible .. Ive also made the leap from WM tot Desire and have the same problem with my Nokia Carkit. !!
Can't find the solution anywhere !!
greeds Rob

[Q] Newbie to HTC Legend

Hi all,
I have a friend who has a bricked Legend, and I have said that I will attempt to install a updated ROM for her.....
Problem is, although I have done this a few times with MY LG GT540, I have done nothing with HTC.
Could anyone point me in the right direction for a guide to updating the Legend to the latest ROM, including any downloads that I'd need.
Thanks very much,
Mango

I would start with the sticky at the top of THIS page.
Good luck.

Thanks Dirk (Love the name, by the way!)
But looking through that it's very difficult to get a sense of what I'll need to do, and in what order.....
The LG is pretty easy, as you have a KDZ installer......But on that stickie it seems a bit random!

Right....having now got the Legend in front of me, I need to know what to do!
It seems to be having a software glitch on the previous update.....Cannot get in to see which update it was, and my friend has no idea either.
She had sent it back to V'phone, and also HTC to get them to do something, but they keep fobbing her off.
I said I'd have a look, but it really doesn't seem as straight forward as LG!

Are you ever able to boot into a working OS (doesn't sound like it), or does it crash out before loading the desktop?
What sort of errors or faults are we dealing with here basically?

Basically, it starts up.....
It loads up the OS, but from there, it can take anything from 2-5mins to freeze up.
The notifications bar will not pull down, and then, when it does it sticks.
I've said that she probably needs it to be re-installed.....(Hopefully with a newer version).
Vodaphone and HTC have both been useless for her. I woulda thpought HTC would've just flashed it and be done....but no!
So I thought I'd come searching on here! But the sticky doesn't help me that much! I'm from the LG forum, where everything is set out in !idiot guides"!!
I do work in IT, so I am pretty competent, but haven't touched an HTC before!
Thanks for your replies

Right....Done a factory reset, and when the Legend comes on, it is completely unresponsive.
Plus, the screen image shakes from side to side, in a quite violent manner!
It would appear that I can move the screen without even touching it!
Any help is gratefully received!!

Sounds like a hardware issue then. If you were able to factory reset without any improvement at all i'd say that software problems are pretty much ruled out.
If i were you i would have a good rant at Vodafone until they agree to swap the unit with a working model.

Thanks again, Dirk....
I have emailed her to let her know your thoughts!.
Long, dark tea-time awaits

Always a pleasure to speak with a fellow fan
Good luck with the phone. Vodafone have always caved in when i've kicked up a stink about various faults etc so i hope your friend gets a result.

Apparently, she has already been intouch with both HTC and V'phone....and neither are prepared to do anything about it.....
Still worth a screaming match with them???
On an unrelated point..... Did you see Steven Mangan as Dirk? Was disappointed that the book was so thoroughly mashed, but was still entertaining!

[Q] Droid 2 bootscreen and unroot

First of all, I would like to thank the owners of this forum for providing such a great resource for simpletons like me to use. While in real life I'm an Air Force officer, when it comes to Android rooting/modifications/etc. I know close to nothing.
Before I begin, I would like to let you all know that I HAVE searched Google and this forum for answers to my problem. While I have found solutions that look promising, I am still not comfortable with them as many of these threads are from the September/October timeframe (i.e. they're OLD!)
Here is my situation:
I bought/rooted my phone back in September. I can't remember exactly how I did it, but it WAS through USB debugging mode and a command prompt on my PC. I believe I downloaded a series of Motorola drivers, etc. but my memory is hazy at best. I successfully rooted my phone (got the little Superuser Ninja listed under my applications) and apps that required root all worked. I never put any custom themes/images/etc. on my phone - I only used it for Wireless Tether.
Shortly after rooting I was having Star Wars envy and put the custom bootscreen and sounds on my phone from the R2D2 Droid 2.
Then.. everything was fine for several months. I accepted the OTA update from Verizon sometime in October? and I am running version 2.3.2.. with my phone still rooted.
Now, here's my problem:
My microphone AND external speaker have both stopped working on my phone two days ago and I need to return it to Verizon under its warranty. I understand that Verizon will NOT accept my phone if it is rooted and if tampering is evident (i.e. custom bootscreen).
My question is this:
What is the easiest/simplest way to unroot my phone and return it to the stock bootscreen and sound files? I don't want a Verizon technician looking at my phone and saying, "What is this?"
While rooting my phone has nothing to do with the hardware.. I know they'll look for ANY reason to deny my warranty claim. The fact that my external speaker and external microphone have died on this phone are HARDWARE issues that Motorola should be liable for.. and in its current state my phone is unusable for making calls (nobody can hear me) and I need a new one.
I hope someone in this forum can point me in the direction of the proper solution.
Again, I'm sorry for posting a question to a problem where there already may be an answer.. but I don't want to take any chances.
Thank you.
btw I CAN make calls.. but I have to use a bluetooth headset!

Excellent question. If one can do, one ought to be able to undo.

Boot into recovery (google the button combo, it should include the power button and some other button(s)) and then use the speaker buttons on the side to navigate to factory reset. This will return your phone to how it was when you first took it out of the box. Hope this helps
Sent from my DROID PRO using XDA App

SORRY! >.< [for those who tried Tinny fix zip]

Dear community,
I sincerely apologize. I seriously did not think that would've happened. Honestly it was my first time and I thought it would work, as I had performed the update on my friend's Inspire 4G and it worked [Honeysense HD]. I didn't doublecheck the script in there, and that was my error. I really am sorry.
I am currently trying to redo it and this time, I will gather a bunch of my friends in order to test it out on several devices and several different roms. If it works again, I'll post it with caution in case anyone else seems to be having problems (when I first flashed CM7's fix, it sent the phone into a bootloop and stopped the phone from working).
Once again, I apologize for such a noob mistake. I honestly thought it would work and I will never, ever let that happen again. I'm only trying to learn more about the android system, and I wanted to help out, even though I didn't have a Inspire.
If anyone's phone was damaged, please PM me. >.<

jojojohnson7410 said:
I am currently trying to redo it and this time, I will gather a bunch of my friends in order to test it out on several devices and several different roms. If it works again, I'll post it with caution in case anyone else seems to be having problems (when I first flashed CM7's fix, it sent the phone into a bootloop and stopped the phone from working).
Click to expand...
Click to collapse
I didn't flash your fix, but thanks for the apology.
Just so you know, you don't need to go to the trouble of testing it and posting it again. This fix isn't needed. All of the ROMs in the Inspire section either come with the fix already in place, or they've got a fix that is flashed separately, that has already been tested by the dev of that ROM. For a "universal" tinny fix, there is already a thread for this. So any additional tinny fixes are simply not needed.

Tough lesson, but great way to deal with it! Mistakes are only n00b the second time you make them!

[Completed] [Q] HTC One Bluetooth issues drives me nuts

Hello there!
I just created an account and would like to apologize in advance for any rookie mistakes; using the wrong terms/words and expressions, posting in the wrong place etc... I have seen a lot of very helpful threads but I have yet to find an answer to my issues with my phone.
I have an HTC One (I believe it is the M7) and the service provider is Verizon. The phone was rooted when I bought it and has
"NuSenseSIX-KitKat-m7vzw_RC4.2_032914"
I am having problems with using a bluetooth earpiece together with the phone. (You will get a ticket if driving and talking in the state of WA) and it drives me nuts! I have tried 3 different brands/kind of bluetooth devices as well as made sure that they work on other phones.
I am able to connect/pair the devices - no problem. I can listen to audio, both music/sounds on the phone as well as during calls or using Voxer Walkie-Talkie. There was never an issue on my end as far as hearing sound BUT, not once have I been able to be heard on "the other end". All they hear during a call is a "high-pitched crackling, static, robotic, very annoying" noise which makes the device useless for its purpose.
I have tried restarting, repairing and whatever other "simple" troubleshooting steps I could think of.
I did back the phone up and then did 2 or 3 factory resets, I have "un-rooted and re-rooted" the phone using SuperSU (which was already installed). I have tried to do the wipe/reset/recovery procedure a few different ways, one being a complete removal of Dalvik, cache, and whatever else shows up (sorta scary since I don't have very much experience)
Anyways, I am stuck and wonder if there is anyone out there who can possibly help me..? Is there a "fix" that I can install/apply or is there a better ROM I can use? I'm afraid to try "ROM or Kernel-swapping" on my own before I get some feedback on the procedure...
Sorry for the long post but I really need help....
Thanks - Bob the Swede

Bob the Swede said:
Hello there!
I just created an account and would like to apologize in advance for any rookie mistakes; using the wrong terms/words and expressions, posting in the wrong place etc... I have seen a lot of very helpful threads but I have yet to find an answer to my issues with my phone.
I have an HTC One (I believe it is the M7) and the service provider is Verizon. The phone was rooted when I bought it and has
"NuSenseSIX-KitKat-m7vzw_RC4.2_032914"
I am having problems with using a bluetooth earpiece together with the phone. (You will get a ticket if driving and talking in the state of WA) and it drives me nuts! I have tried 3 different brands/kind of bluetooth devices as well as made sure that they work on other phones.
I am able to connect/pair the devices - no problem. I can listen to audio, both music/sounds on the phone as well as during calls or using Voxer Walkie-Talkie. There was never an issue on my end as far as hearing sound BUT, not once have I been able to be heard on "the other end". All they hear during a call is a "high-pitched crackling, static, robotic, very annoying" noise which makes the device useless for its purpose.
I have tried restarting, repairing and whatever other "simple" troubleshooting steps I could think of.
I did back the phone up and then did 2 or 3 factory resets, I have "un-rooted and re-rooted" the phone using SuperSU (which was already installed). I have tried to do the wipe/reset/recovery procedure a few different ways, one being a complete removal of Dalvik, cache, and whatever else shows up (sorta scary since I don't have very much experience)
Anyways, I am stuck and wonder if there is anyone out there who can possibly help me..? Is there a "fix" that I can install/apply or is there a better ROM I can use? I'm afraid to try "ROM or Kernel-swapping" on my own before I get some feedback on the procedure...
Sorry for the long post but I really need help....
Thanks - Bob the Swede
Click to expand...
Click to collapse
Hi , we have specific forum for your device , so post your further queries here One Q&A, Help & Troubleshooting.

Thread closed, thank you.