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
Hi All I have just purchased a new nexus 5 (gear live pre-ordered) in a curious attempt to have a go at android from my Iphone 5c.
I am tweaking the handset at the moment to give me some lost functionality from IOS. I have stumbled across a really painful problem that i can not find a solution to. I use a pair of bose wired earphones to listen to music and use as hands free in the car. On my iphone, I am used to to pushing the mic button and activating the voice dial from the locked screen, all good.
When i try doing this on my nexus, i get the "can not use OK Google until the phone is unlocked" message in my ear.
I have to have a passlock on the handset due to work security restrictions.
Does anyone have a work around for this? I am hoping my new gear live will keep the pass lock when in close proximity (A major flaw otherwise - unlocking your phone before you can see anything on your smartwatch!) in the interim though, putting a pass key in the phone every time i want to make a call whilst riving is pretty poor!
currently on stock 4.4.4. not rooted yet -
Thanks all
randomtechgeek said:
Hi All I have just purchased a new nexus 5 (gear live pre-ordered) in a curious attempt to have a go at android from my Iphone 5c.
I am tweaking the handset at the moment to give me some lost functionality from IOS. I have stumbled across a really painful problem that i can not find a solution to. I use a pair of bose wired earphones to listen to music and use as hands free in the car. On my iphone, I am used to to pushing the mic button and activating the voice dial from the locked screen, all good.
When i try doing this on my nexus, i get the "can not use OK Google until the phone is unlocked" message in my ear.
I have to have a passlock on the handset due to work security restrictions.
Does anyone have a work around for this? I am hoping my new gear live will keep the pass lock when in close proximity (A major flaw otherwise - unlocking your phone before you can see anything on your smartwatch!) in the interim though, putting a pass key in the phone every time i want to make a call whilst riving is pretty poor!
currently on stock 4.4.4. not rooted yet -
Thanks all
Click to expand...
Click to collapse
I'll be honest and say that being able to make a call with the phone being pin locked would be a security risk. Now as for a workaround I can only think of one thing that would work but it requires some time to configure things correctly.
You could us ethe app tasker to automate this. You can set a profile for when you are in your car. When you are driving in the car (e.g. moving over 10 MPH) you can have tasker turn off your PIN Lock. Then when you get out of your car (eg not moving) it would reenable your PIN lock.
If that's too hard to configure (I can show you if you are interested in the above method) You can just set up a much simpler profile in tasker that whenever your BT headset is connected disable your PIN lock. THough this is less secure.
Those are the only options I can think of and honestly I would be surprised if anyone came up with a true solution to this
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.
I was hoping that CM13.0 would solve my Bluetooth problem but did not.
Although most of the time is working with a factory Bluetooth system (in a MB car) every now and then it disconnects.
Disconnection usually happens when there is an incoming call - before I press the accept call button, phone disconnects and reconnects a second or so latter.
I had this problem with CM12.1 and I was hoping CM13 would fix it - only in CM12.0 it was working fine.
Rare times it disconnects while idle – or it happens often and it goes unnoticed.
Is there any solution I missed?
Things like complete factory reset / clearing cash etc are done with no change in the results.
Car has no update (it’s an Alpine NTG2.5 system).
papars said:
I was hoping that CM13.0 would solve my Bluetooth problem but did not.
Although most of the time is working with a factory Bluetooth system (in a MB car) every now and then it disconnects.
Disconnection usually happens when there is an incoming call - before I press the accept call button, phone disconnects and reconnects a second or so latter.
I had this problem with CM12.1 and I was hoping CM13 would fix it - only in CM12.0 it was working fine.
Rare times it disconnects while idle – or it happens often and it goes unnoticed.
Is there any solution I missed?
Things like complete factory reset / clearing cash etc are done with no change in the results.
Car has no update (it’s an Alpine NTG2.5 system).
Click to expand...
Click to collapse
Sadly, this is a wide problem with a lot of Android phones.
One of the fixes Ive read around is to not give so many permissions when pairing a Android device. Example I read: Someone's device would never connect if they shared contacts with their car. You can share contacts and have the hands free not working or not share any contacts and have handsfree working. Its a trade off.
So far CM13 seems little better.
What I can't figure out is the pattern, if there is one. Why sometime it works and sometimes is not. When I initiate the call from the phone or the car keypad, 99% it will work without a problem.
When I receive a call, its a hit or miss. Sometimes it works, sometimes it doesn't. The only reason the phone is not landed out of the window is the fact that reconnection is quick, so I get to answer the call from BT no matter what. But is frustrating.
I remember my first phone with this car was a (non smartphone) nokia. In that case from BT I could hear the selected phone ringtone and the phone did not ring at all.
With any smartphone from then on, both the phone rings (with its own ringtone) and the BT rings with a generic tone. Oh well ...
BTW I had zero problem with BT when I first bought OPO - but then it had CM12.0 I think.
Hi guys, this is a very particular problem and it's annoying the hell out of me. Can't find any reference to it anywhere.
Phone was working flawlessly until a firmware update was pushed by Samsung, taking me to the APEQ firmware version. Since then, the phone will become unresponsive whenever this scenario happens:
Connected to bluetooth (BMW 3-Series, 2015)
On an ongoing phone call
A second call comes in, but I don't answer it. I don't reject it either, I just let it ring.
Phone freezes, Loses connection to the car. Original call drops. Will become unresponsive for several minutes, or outright reboot by itself.
I've noticed that the phone app itself seems to be slow to execute any action: Start a call, blank screen for 3-5 seconds. End a call: Phone app screen frozen, phone unresponsive for 3-5 seconds.
I haven't rooted my phone, but I've rooted all my android devices in the past, so I'm not a stranger to it.
Any suggestions? I'd like to avoid flashing a new ROM because of the hassle (I just don't have the time to fiddle with a new ROM) and my SD card is encrypted...
Thank you all
I have similar on Galaxy Note 4 and also Galaxy Edge after marshmallow update. If using bluetooth, cant answer next call even if first call is diconnected already. phone freezes, rings forever, cant answer thru phone (nothing shows up on screen even saying there is a call, not in call log either)-- phone will sometimes reboot or i have to pull battery to get it to stop ringing. I also never know who called because no record in call logs of the perpetually ringing call.