Database Info

Kenwood BT-200 Handsfree Kit

I've got a Kenwood BT-200 bluetooth handsfree car kit and have found the following issues with it;
1. Everytime a call is completed, the phone book downloads all over again and takes over 10 minutes, preventing making follow on calls till complete.
2. The received and dialed calls list doesn't work
3. Cannot initiate a call from the head unit unless the phone screen is on (was working perfectly on previous HTC Touch Cruise).
4. Unable to initiate voice dialing on Phone using Microsoft Voice Command whereas with previous HF kits it was as simple as pressing and holding the call button.
Anyone else use the same Touch Pro - BT200 combination? Or experience similar problems with other HF kits?

I have Pioneer BT unit. I can not connect, but I installed Hands-Free Config from JETware Mobile Software and it solved all my problems. There are many setting options which should help you...

Hi Pritman,
I just went through the same thing after upgrading to the Touch Pro from the Dopod 838Pro (Hermes).
There's a firmware update available for the KCA-BT200 which may well fix your issues (certainly did mine).
I created a post about this earlier today (didn't see your post here).
http://forum.xda-developers.com/showthread.php?t=440494
The firmware flash is very easy to do. You will just need a laptop with a bluetooth adaptor.
Codenix.

Kenwood have released another update.
See my other post at http://forum.xda-developers.com/showthread.php?t=440494 for details.
Codenix.

Wow, never thought I would fine anyone else with the combination of Kenwood DNX-7100, KCA-BT200 AND the touch pro. I am having similar issues.
DNX-7100 with BT100 worked fine with touch pro.
"upgraded" to BT200, and I have nothing but headaches.
I have tried two different BT200, and both have been flaky.
I have tried BT200 firmware 1.60 and 1.70, and both have been flaky.
My problem is similar to the ones you folks have been experiencing, mainly it is constantly downloading, and the interface is super sluggish when downloading. I can retrieve a name and phone number from the BT200's memory, but when I call out it will say downloading and do nothing. Sometimes it won't "pair" with the phone automatically unless I manually select my phone from the DNX-7100, and sometimes it will just drop the connection. I used the BT100 for about a year, and it was solid 95% of the time. I am running stock Telus rom, btw. I have also played around with the dip switch on the BT-200. From the shipped manual, DNX-7100 belongs in group F, which is off, off, on for dip switch 1, 2, 3. But when I searched online, some of Kenwood's info listed the DNX-7100 under group G, which has dip switch off, on, off, just to add to the confusion. I have also tried removing the "wireless stereo" profile as well as the "serial port" profile, but that fixed nothing. Lastly, just to kick me when I'm down, when it list the numbers, sometimes it list them as first name, then last name, but sometimes it list it as last name then first. This is super irritating as you can't be sure where anyone is listed ..... so far my experience with the BT200 has been nothing but horrible. I am on the verge of flashing my touch pro to a cooked ROM just to see if it is due to the stock Telus rom's bluetooth (I went back to stock as the juggalo rom I used became corrupt after a few weeks).
So, did you guys finally find a solution that worked 100% of the time?

Idea
Hi Guys, I'm glad there are more people out there with my combination.
Upgrading the BT 200 to 1.70 has improved things significantly but not as good as it would be with another handset like a Nokia N95. The download delay and sluggishness still exist.
I recall when I paired the TP, a notice came up on the TP that the BT 200 is requesting access to the phonebook or contacts and prompted me to allow or deny. I'm wondering what would happen if I deny? I do know that when I first paired the N95 with the older firmware, it wouldn't syncronise the contacts and I had to manually send the contacts to the BT 200. If this can be done with the TP, it may eliminate the constant downloading, perhaps.
Anyone else willing to try this. I may not be able to do this till later this weekend so if any of you do manage to test this before me, please post the results.
Good luck!

If you don't give it access to the phonebook, I suspect it can't download your phonebook automatically, and you would have to manually push the phonebook over, which defeats the purpose of the BT-200, effectively making it a BT-100. After trying a 2nd BT-200 for 3 days, I have given up and chalked up the BT-200 as extremely flaky, and is easily the worst purchase I have ever made as:
1) Half the time it won't pair with the phone automatically
2) The other half when it does pair, you can't dial out as half time time again when you want to make it call, it decides to do a download from your phone instead (never mind that it already "downloaded" when it paired already. Half x half = quarter.
3) Half the time when it does manage to make it call, it magically drops the bluetooth pairing and drops the call.
If you're keeping track, we are at half x half x half, which is 0.125, or this damn thing only works 12.5% of the time. This is not a time saver, nor a gadget of convenience/safety. It is the ultimate source of anxiety, danger (as you're trying to get the damn thing to work), and a big disappointment. Kenwood, shame on you for putting out such flaky products, and especially for not fixing it (look at the first post, it is from Oct 08).
I am going to return both of my BT-200 to Clutchfield, and am going back to my 99% stable BT-100. BT-100 actually is not as horrible with the TP as TP runs WinMo 6.1, which lets you push multiple phone book contacts at once (not like the older WinMo where you had to push contacts ONE BY ONE!!!). The only caveat with the BT-100 is if you need to delete or modify any contacts, you can't, and you have to delete all the entries for a particular phone and repair and push all contacts again, which takes 1 minute now as oppose to half an hour with pre-WinMo 6.1. When I buy a HU next time, I don't think I will consider Kenwood again due to:
1) Flaky software/interface.
2) Poor documentation.
3) Poor service support. Kenwood Canada actually NEVER REPLIED. I only received the auto-gen email notification indicating they received my email. Clutchfield Canada has been very supportive, and I will pay more to buy from them in the future solely due to their strong customer support.

Hi Johnnysks,
As far as the Touch Pro is concerned, I understand your frustration and totally support your argument.
On the other hand, I have tested the BT-200 with a Nokia 96 & my previous Touch Cruise, works like a dream! I've had good responses from Kenwood UK but whenever I contact HTC, I alway get vague responses, which to me suggests that Kenwood must have been making the effort but keep getting let down by HTC. Ultimately the BT-200 works with majority of the handsets out there.
I will still keep trying for a solution though as I really do like the TP and the BT-200!

I have no doubts the BT-200 works with other phones, and I know my TP works with my BT-100 flawlessly. I also know from prior personal dealings with Kenwood Canada's technical support that:
1) They're rude, have a bad attitude, and unprofessional (as my first inquiry for a different product from a year ago was met with a reply that was condescending, unhelpful, and was not even in proper English). I'll be more than happy to dig up my old email for you if you have any doubts.
2) They're not responsive. It's been over a week, and they never replied to my current inquiry regarding the BT-200 (funny. They used to be rude and unprofessional. Now they're missing in action)
Perhaps Kenwood USA, Kenwood UK, or Kenwood Japan are doing an awesome job. However, I can only go with what I have personally experienced.

Anyone find a fix for this? I have the same problems with my DNX8120. Tried Jetware, no luck, I would try BTRestore, but it won't work with .net 3. My biggest complaint is that even if it is connected via bluetooth, it won't start a call from th eheadset unless the phone is not in standby. Next biggest issue is that it drops the connection after hanging up from a call.
Very f*&%*g annoying!
FYI, worked with 2 different ETEN's

[voip][sip] FUZE and GIZMO5 what do you need to make it work?

[voip][sip] FUZE and GIZMO5 what do you need to make it work?
specifically, I'd like to know if anyone has used their Fuze with Gizmo5(SIP voip) and Google Voice for free USA in/out via WiFi or 3G. I've searched and read and my head is spinning, most search results bring up the android, which already works: http://forum.xda-developers.com/showthread.php?t=541177
but for WM6.1 there's still lots of reports of broken GPS, cannot uninstall, need hard reset, etc. It seems these are the files needed, with the related xda threads:
from thread VOIP in WM61, done! old thread not raphael/fuze
http://forum.xda-developers.com/showthread.php?t=401608
destr0_VOIP_WM61___SIP_Config_1.1.CAB
from thread VOIP (SIP) on Rapahel / HTC Touch Pro ???
http://forum.xda-developers.com/showthread.php?t=426583
RAPHAEL_VoIP.zip post24 mrvanx
InternetCalling_21109.cab post72 sleuth255
then there's WM6voipFULL cab post86 working on Kaiser w Betamax SIP
several members reported audio not working on the Fuze, even when using troca2.exe or Marcelo's AudioSwitch.
most of these threads are old, and the only thread related to the FUZE has broken audio = not working. Besides, there's the lingering question of broken GPS, and having to manually switch audio between back and front speakers when using troca or audioswitch.
If anyone has the FUZE+GV+Gizmo5 setup working, are there other files I need besides the 4 listed above? I have hardSPL on a stock ATT FUZE rom. I have done enough hard resets and already have 50+ programs, so don't want to approach any solution that would involve further hard resets/broken gps/reinstallations/etc as either one of those problems will eat up a whole day. maybe next weekend.

atlaswing said:
[voip][sip] FUZE and GIZMO5 what do you need to make it work?
specifically, I'd like to know if anyone has used their Fuze with Gizmo5(SIP voip) and Google Voice for free USA in/out via WiFi or 3G. I've searched and read and my head is spinning, most search results bring up the android, which already works: http://forum.xda-developers.com/showthread.php?t=541177
but for WM6.1 there's still lots of reports of broken GPS, cannot uninstall, need hard reset, etc. It seems these are the files needed, with the related xda threads:
from thread VOIP in WM61, done! old thread not raphael/fuze
http://forum.xda-developers.com/showthread.php?t=401608
destr0_VOIP_WM61___SIP_Config_1.1.CAB
from thread VOIP (SIP) on Rapahel / HTC Touch Pro ???
http://forum.xda-developers.com/showthread.php?t=426583
RAPHAEL_VoIP.zip post24 mrvanx
InternetCalling_21109.cab post72 sleuth255
then there's WM6voipFULL cab post86 working on Kaiser w Betamax SIP
several members reported audio not working on the Fuze, even when using troca2.exe or Marcelo's AudioSwitch.
most of these threads are old, and the only thread related to the FUZE has broken audio = not working. Besides, there's the lingering question of broken GPS, and having to manually switch audio between back and front speakers when using troca or audioswitch.
If anyone has the FUZE+GV+Gizmo5 setup working, are there other files I need besides the 4 listed above? I have hardSPL on a stock ATT FUZE rom. I have done enough hard resets and already have 50+ programs, so don't want to approach any solution that would involve further hard resets/broken gps/reinstallations/etc as either one of those problems will eat up a whole day. maybe next weekend.
Click to expand...
Click to collapse
I've been running this for a while now...
Use these:
1. InternetCalling_21109.cab - the other ones will break your GPS
2. SipConfigTool_2_0_1.CAB http://forum.xda-developers.com/showthread.php?t=303493
3. AudioSwitch - if you dont use a wired earpiece or a bluetooth earpiece you will need this otherwise sound always comes out back speaker.
4. Make these registery changes:
[HKEY_LOCAL_MACHINE\System\VoIP\SIP]
"EnablePort5060"=dword:00000001
"OutgoingFailOn302"=dword:00000000
"RtcInitFlags"=dword:00000000
[HKEY_LOCAL_MACHINE\Comm\RTC\SymmetricResponseRouting]
"ResponsePort"=dword:00000001
[HKEY_LOCAL_MACHINE\Comm\RTC\Threads]
"EngineThreadsPriority"=dword:00000121
"TimerFrequency"=dword:00050000
Do these and it should work over wifi. Next thing you'll discover is that ATT blocks voip so you can't use it over 3G, just wifi - although at one point it was working for me over 3G when I first got my phone.
The other issue you might find is that even though on yer today screen it says "selected" - meaning its working - that after a while it's really not. I think it's timing out or something? simply changing it to off and then back on fixes it. I'm thinking the "TimerFrequency" reg entry might have something to do with that - perhaps you can try making it lower if you have the issue and see if that fixes it.
...anyway thus far this is the best solution I've been able to come up with and I've been messing around with trying to get the windows mobile native voip crap to work for about 2 freakn years now...ha

^ Thanks! I'll try them next weekend. So, to recap, I'll need the newer SipConfig v201, and not bother with WM6voipfull nor Raphael_voip.cab.
I want the apps, but I'm really not looking forward to the potential problems with the gps or audio. I've gone into a habit of full backups with Sprite Backup and SKtools before installing any new software, as both of them only work only half the time, so hopefully, i'm covered.
edit:
the 2007 sipconfigtool v201 is only 23kb, whereas destr0's v1.1 I posted is 1.8MB, from 2008. I'm definitely missing something. regardless, I'll test them next weekend.

Would love to hear how it works out
Atlaswing,
I am in the same boat as you. Banged my head against the wall with this for a few months and got tired of having to reload and rebuild.
I never could get Gizmo5 to work right. From my digging there could be issues with the codecs and the only thing I could find with updating codecs required ROM cooking type stuff. I surely could have missed something though.
Let me know if it ends up working for you with Gizmo5 and what it took.
I also have GoogleVoice ... so this could be sweet if it works.
Later
P.S. --
Don't know if you caught it ... but there's a ROM update from HTC for the Fuze. You can get it from the US HTC Support site. Came out in May I think.

Never gave it a try as Gizmo5 stopped their free GV integration, making the whole process pointless. No more free outgoing calls, so you might as well install the other free incoming SIPs that are well established, i.e. SIPgate, for your Google Voice free incoming calls. My first post has links to 2 sipgate sip threads, and I'm not even gonna try it, as the few cents I save from free incoming calls is not worth the days/hours of troubleshooting and reinstallations if it wrecks my gps.
I already have a usb DECT yahoo voice cordless phone for 1cent calls when i'm at home (linksys cit310 for $9-$15), so, again, not worth my time to wreck my TP over this.

HTC (AT&T) FUZE BT earpiece issues

I re-downloaded the new ROM for the FUZE. The first time, I noticed the change in the phone with the slider added but it became painfully obvious that my earpieces ( motorolas HS850 AND S9-HD ) don't pick up (hands-free) anymore. I have to slide the bar and hopeit pics up - that takes a few seconds also.
Seems like this second time has put some pieces I guess were missing but the BT ear piece stuff is still an issue.
I wish they never got rid of the app. I used to call hands free on the 8125. Can't stand Voice Command never gets my calls correct so I just keep it disabled. At least with the other app. I could go to each contact and "train" it to respond - had hiccups but at least it worked more than not.
I've used Andrea F's weatherdatabase to add cities to my accuweather app. on the touchflo 3D. So i'm wondering is there anything I can do about the above.
I'm running Windows Mobile 6.1 Professional.
HTC say that they are getting lots of calls on this but for now nothingas far as a fix.
Any help with the BT issue or even voice command would be greatly appreciated.
Thanks T.

Moved as not ROM Development.

Bluetooth A2DP now on Jawbone ICON earpieces

So sweet. Jawbone now has an update for the Jawbone ICON which allows it to pair as an A2DP device. This means I can route all sound to it: music, movies, navigation, FartDroid, Robo Defense, etc.
There has never hasn't been a fix for this since the 1.5 ROMs. I'm on Fresh 2.0d
This awesome earpiece can be had for around $75 if you look hard enough.

Happy he posted... I am very happy, since I already have an ICON but didn;t know this

maybe not a big issue with people on this forum but this was a huge android issue in general. pissed a lot of people off.

HeroMeng said:
And, this was important enough to post a new thread about? Sorry, but it's cluttering up our tiny forum.
Click to expand...
Click to collapse
Holy ****. This just cluttered up this thread.
This was a huge deal with Android and Jawbone just solved it for me.

Good to know. Knew I got my Icon for something. Thanks for the info.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk

Can the ICON connect to the phone and allow voice dial ? Thats one feature I miss. All the crazy advances and this is one feature that hasnt been fixed. Oh well. By the way the Q1 does the ad2p thing and also allows 8 presets that allow the unit to at least connect and call out which is handy. It also allows you to connect hands free with just your voice. Not too big of a deal if your driving but if your a biker it's a pretty awesome feature ;-)
I wonder how hard would it be to program an app to wait for the button press on a headset and set it to use the voice recognition on the phone that is used by google search/nav etc...

jcf304 said:
Can the ICON connect to the phone and allow voice dial ? Thats one feature I miss. All the crazy advances and this is one feature that hasnt been fixed. Oh well. By the way the Q1 does the ad2p thing and also allows 8 presets that allow the unit to at least connect and call out which is handy. It also allows you to connect hands free with just your voice. Not too big of a deal if your driving but if your a biker it's a pretty awesome feature ;-)
I wonder how hard would it be to program an app to wait for the button press on a headset and set it to use the voice recognition on the phone that is used by google search/nav etc...
Click to expand...
Click to collapse
Maybe it was a multi phone pairing issue, but I found that the Q1 didn't reconnect automatically if I walked away from the headset with the phone or vice versa. Also didn't like that the buttons were easy to press and hence a lot of pocket headset redials...
I am very stoked with the a2dp on the icon as that's the headset i had just before being convinced by someone else that the q1 was the way to go and since having gone back to the icon
Thanks for the info, I forget that the icon is updatable and haven't checked in a while...
r

seeing as this is a relatively active bluetooth-related thread, i was wondering if someone could answer a q for me.
im on fresh 2.0d and whenever I tried to play anything via A2DP in my car, the audio was sped up and always skipped about every second...has anyone else experienced this? if not, could you tell me which ROM you are using so I could give it a try?
appreciate any info anyone can offer...thanks

jcf304 said:
Can the ICON connect to the phone and allow voice dial?
Click to expand...
Click to collapse
Here's a bit of info on the Jawbone ICON website: "To encourage Google to support voice dial via Bluetooth on the Android OS, vote at Google product ideas or post a reply on Motorola's DROID forum."
I have found that the Voice Search app works a little better than the Voice Dialer app on the Hero. I just place a shortcut on my home screen. If I open the app and say, "Call Dennis at Home," it will dial home right away. Not quite "hands free" dialing, but as close as I can get for now.

2015 Honda CR-V EX-L and bluetooth

I have posted a similar post in the CRV Owners forum, but I thought this forum would make more sense since it's filled with a bunch of hardware-hacking programmers!
The interface between my car and my phone (LG G2 Lollipop stock) is abysmal. I have seen a number of posts on the web about this issue with modern cars, but no real solutions. The following is a list of what I would like the interface to be between the phone and car. Then at the end of the email I'll flame a little about the "why"s.
GIve me a button to allow me to talk to my phone directly without the HondaLink getting in the way. There was a similar issue with a Volkswagon and a solution using Tasker to intercept the call. That solution doesn't work with my Honda and is a kludge.
Always have the phone interrupt the radio (whether it's a call or audio, e.g. Google maps navigation). For me, the information coming from the phone will always be more important than the music or talk show on the radio.
Mirror the phone screen onto the car screen when I'm driving (so I can see my map when I need to)
When I receive a call, let the phone do the talking (the phone can speak the caller's name to me and can send the caller's name over the bluetooth connection) and let me hit a button to answer it.
Has anyone successfully hacked into the firmware/software in the CV-R to fix these issues? Is it possible? At this point, based on my research, I see no other option. If there is another option that doesn't involve replacing the system or "just dealing with it," I'd love to hear it.
The "why"s:
My phone is custimizable, has all of my contacts, recognizes my voice, has GPS, accurate and up-to-date maps, and does everything that I need a phone and navigation system to do. The Honda solution tries to duplicate all of that functionality and does it very poorly. As one user wrote last year, my $50 bluetooth headset can listen to my phone and pipe in navigation directions and let me know when I get a call. It is a joke that an expensive car can't even get that part right. The fact that I can't put my phone screen on the car screen while I'm driving is idiotic. Now I've got to find some way to hold my phone up for navigation. I don't want this post to degenerate into a series of posts and counter-posts on whether drivers can handle the increased cognitive demand. I've been driving long enough to see that the majority of drivers are not paying any attention at all to the road anyway and no one seems to care.
The hardware in the CR-V seems to be capable of doing the things that I have listed above. So, if the Honda programmers can't get it the way I want it, the only solution is to take the programming away from them and do it ourselves. Has anyone done this yet?
Thank you in advance for your help.