I 've spend lots of time searching (google and all) but could not find a answer:
I (actually my Wife) have a Nokia CK-1W Bluetooth Carkit (no remotes and stuff) In the earlier days (Donut) I managed to pair my Wife's HTC Magic with it at some stage with Cyanogenmod we battled with the same problem but around 5.x it worked and it was remebered over to 6.x (I don't have those roms (4.x,5.x) anymore so I can't see what the config was)
We both upgraded to Sensation but now we cannot pair with it (Nokia Ck-1W)
It seems the Phone want to pair with 0000 but the kit has a different number (last four digits of the serial number). Problem is it never gets asked for and fails.
I prosume the auto_pairing.conf file in the /etc/bluetooth folder should be able to resolve it. I tried putting in Nokia (after BMW,Audi,Parrot) without success.
I have S-OF,root& AdroidRevolutionHD, she does not (yet)
Anyone with some info, link or pointer that could help me out?
A solution that would work on Stock is prefereable, but we have S-OFF ...
Thanks
Tobie
HTC Sensation: S-OFF Android Revolution HD 1.1.6
In the mean while I've tried many different settings in the configuration without success (auto_pairing.conf and audio.conf)
I also found that the phone has a dynamic_auto_pairing.conf which seems to be copied over to the data folder once the ROM is running.
I'll try adding Nokia, Nokia CK-1W and 00:08:C6 modded into the ROM with a super wipe when AR HD 1.1.7 gets to us... ( :-( did not work...)
There also seems to be some database living with the bluetoothd files.. don't know how they work:-(
Any luck so far? I'm having a similar problem with my HD2 (BOYPPC CM7 SD build) and CITROEN C4 Picasso built-in bluetooth handsfree (I believe the make is Siemens). I was going to modify audio_pairing.conf, but if that fails for me, it would be great to know if you found another way around this.
Nothing yet Sorry!
I had the same problem. My HTC Magic (CM6.1) worked fine with the Nokia CK-1W, but when connecting my ZTE Blade (CM7.1) it told me that my passcode was invalid, without ever prompting me for a passcode.
The solution was simpler than I had thought: You just need to reset the CK-1W.
With the power off, press the button on the remote for about 15 secs until the light starts flashing. After about 10 secs the carkit will beep 2 times to signal that it has been reset.
If you have multiple phones, remember that the first phone you register will be the "default" phone (the phone the carkit will connect to automatically).
Related
Hi all wondering if anyone can shed some light on this one:
i recently bought a htc kaiser (yay) and its great! but i cant get wifi and bluetooth to work simultaneously in any way shape or form - every time i connect the wifi, the bluetooth connections will die - so far ive tested it with multiple devices and its a consistent problem
i even sent the unit back for a replacement but they tested it and said it was fine (i don't believe them cause i tried every which way to get it working) either way ive got the unit back now and i still cant get both to work at the same time - ARGH!!
if i cant get the bastard to work in the next week or so im going to return the unit as its inside the 28 day period - i just wanna be able to stream music from the net over wifi and listen to it using my a2dp headset
anyone have any guru zen insight on this one they feel like sharing?
cheers
fusi
must be a kaiser or rom thing cause i do it all the time at home with the hermes (go hermes go!!!)
have the wifi running fine with AD2P via motorola Ht820s
My Kaiser does both WiFi & BT with no issues. The only thing I can suggest is tinkering with your WiFi access point settings (change the channel, encryption, etc.) -- in particular, channel changes may do the trick, as both BT & 802.11b use the 2.4 GHz band.
thanks for the replies guys i swear im going loopy with this thing - what wifi channels can you confirm it works on for you?
well ive tried every permutation. it doesnt work - supergps are talking out of their arse when they claim they got it working. im really sick and tired of bull**** companies. dont buy from supergps - they might be cheap but you get what you pay for.
Why don't you try asking supergps what they did to get it working and how they have their wifi configured? Sounds to me like it's something in your setup that's causing it if they confirm the device works.
i did
they claim they connected up a lenovo laptop and a sony phone and it 'just worked'
i tried it with the exact same make model etc of kit (and a whole host of other devices (must be about 30+ different devices now)) and it consistently fails
i cant see how they got it working - unless they were testing a different unit or they didn't understand what the fault was - even though i explained the fault in precise detail in about 5 different ways to them over the duration of the day they were testing it
i reckon they just dont wanna deal with the hassle of getting a duff device back
p.s. this is with factory defaults - no customisations or anything (though ive also tried with every permutation of configuration i could conceive) - it just doesnt work
I have a Treo 750 and a Gtop G33 BT GPS. When I try to connect I can get to the password and if i put nothing in (Gtop says no password needed) and press next - it connects (light flashes slower) but Treo asks for Password again and this time it wont allow me to press next till I put a password in (next is grayed out.) I've tried 0000(Gtop says use 0000 if devise must have a password) and 1234 but as soon as I press next again GPS disconnects (light flashes fast again) and Treo says it is now connected.
I have been all over this sight for the past 2 days and have learned a lot, I even flashed my rom, OS-WM 6.1 WWE lite and radio1.54.07.00, but so far I still cant get this to work (bluetooth), perhaps I cant see the forest for the trees.
Any help would be greatly appreciated!
Jim
GPS CONNECz
Check to see if the treo proccessor speed 300Mhz is compatibalbe with the GPS RECR.
else i don't know I'm a novice
Me too- only with bluetooth headset
I had the same issue under WM5, but did found a way past it once and then of course it was irrelevant. That was months ago and now I can't figure out how I got past the problem. So I'd appreciate it if anyone could clue us in.
Thanks
I've managed to find a way past this
There appear to be multiple versions of WM6.1 around. I had the same problem until yesterday when I re-upgraded to a different version of WM6.1.
Not sure of the version (I'm in New Zealand, so using an Australian rom).
The version that doesn't work is easy to spot as there is no battery indicator and it uses the Microsoft Inbox for texting. The version that does work has the battery indicator and uses the Palm version of texting.
Once I'd got to this version, it no longer insisted on having a bluetooth password.
Cheers, Hope this helps.
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 just bought the Kenwood KDC-BT50U for my car. I plan to use it with my HTC Desire via Bluetooth, mainly to play my mp3s. It paired and plays mp3s just fine, but it does not show the track names on the device and I cant skip tracks. It also does not sync my contact names from the phonebook, except for the call history.
Did anyone get it to work, and if yes with which firmware? the kenwood website sucks and they do not list the htc desire on their firmware update pages..so I have no idea which one to get...any help would be great!
I've got a BT60U and a Desire and it works all fine - it didnt in the beginning though.
My problems were that there was no adressbook sync and that I got random disconnects while driving.
But at some point it just started working. I remember that it was around when I started rooting (the first hacked 2.2 on the Desire) and then later the first AOSP roms. Dont know what made the deal for me but might be a hint.
At some point I also did a complete reset of the headunit.
I know it is a bit vague but I'm running fine with the BT60U (which got the same BT kit as yours) and my rooted Desire running DeFrost 6.1 (but also with OpenDesire and MIUI, don't know about Sense Roms though)
EDIT: forgot to mention: It is normal that the head unit doesn't show track titles etc but the forward/play/pause keys should be working...
What you can try is that you delete your phone from the BT50U's Bluetooth menu (at least mine got an option saying 'Delete BT Device') and deleting your Kenwood on your phone to start it from scratch again.
Hi.
Which number firmware of bluetooth unit is it?
I had the V 3.11.0 but the last is the V 3.12.0: this add the only forward/play/pause keys but doesn't show the track titles (in fact the A2DP protocol doesn't support this).
To upgrade it: manual, software, firmware (or go here and select "HTC Tattoo").
It's very simple to upgrade but, if you can wait, during this week I'm uploading a video about it: I did it last weekend.
Unfortunately, this last firmware doesn't resolve any problems like doesn't sync contact names from the phonebook neither the call history.
Moreover I can't use the "red button" because it kills the app "phone" so I have to reboot or enter again my PIN code.
I have a Wildfire with Froyo 2.2.1 stock.
Bye.
! !
Ps.: my unit has some problems so I have to bring it at assistance.
It's normal that there is always the "FAV" icon at top right of the display?
Thank you.
The protocol for track names is AVCRP rather than A2DP, but unfortunately the result is the same, the bluetooth stack in Android does not appear to be 1.4, rather 1.3 which doesn't have the feature.
Do you have an import via bluetooth option on your Kenwood. At first my JVC wouldn't sync and I just had to export the cantact list and then use a bluetooth transfer app to transmit it across manually. One day it just started working as mentioned above.
@400ixl: there is an automatic sync of all datas every time that the phone connects to the Kenwood radio but with Android it doesn't work, unfortunately.
I hope there will be an another Bluetooth firmware upgrade.
Thank you.
Bye.
! !
I uploaded a short video about the upgrade.
If you would like see it, I'll write the link.
Bye!
! !
thanks very much
Video.
Bye!
! !
Hello Everyone,
This issue has been bothering me for over a month. I have searched several "MS support forum" threads, XDA Dev threads and multiple Audi forums, but all in vain.
I am not sure if anyone in here has had any issues with the Audi MMI while using a WP7 Handset. I hope that some smart person will have a word of advice for myself. Provided below is the process that I followed for pairing and testing:
1.Cleared all the existing paired devices from the MMI.
2.Cleared all the pairings from the cellphone. (Just to start with a clean slate).
3.Paired cellphone to MMI.
4.Check marked the prompt on cellphone, to Allow MMI to access my phone books and other cellphone data.
5.Call logs and telephone directory is accessible on the MMI.
6.Outgoing Calls from the MMI work without a hitch.
Up to here, everything is good. However, I am unable to answer the call from the car's MMI. If I may paint a scenario:
A call comes in.
The audio system gets paused.
I can hear the call ring, and Caller's ID is displayed in the car.
I click "Answer" from the MMI.
The call gets answered, but the only way to get the audio onto the car's system is to pull over and yank the phone out of your pocket and click the bluetooth button on the call menu.
But 1 in 10 times it would work just by clicking answer from MMI.
I have never had any issues with my Blackberry. Is anyone else aware of a similar issue or a resolution to this?
Thank you very much!
Details:
Cellphone : Nokia Lumia 800
OS Version: 7.10.8107.79
Vehicle: Audi S5
Audi MMI Version: HNav_US_P0110_D1 (Third Generation, HDD based)
is ur phone locked by any chance (I mean have u kept a lock on the screen) if you have than try once after removing the lock
I thought of exact same thing. Tried it both ways, same result.
Stealership!!
Well, took the car to the dealership, to check for any MMI updates that might be available. In the end, the guy said that there are no updates available, and they charged my 90 bucks for the labour . Gotta love Audi. And the car has "New car warranty" till 2015. Glorified car wash.