Related
I know this is for only XDA devices, & I tried searching but I didnt see anything except for 1 post. http://forum.xda-developers.com/viewtopic.php?t=11128&highlight=nokia+car+kit
But I thought I might try you guys here.
I have posted on other HP related sites as well for the same problem.
This site was so usefull when I had my Siemens SX56.
The only thing I wanted to know is if anyone knows if there is any add on driver I can add to it to make the hp6315 bond with my nokia bluetooth carkit model # CARK112.
I cant seem to get it to bond?
I did get my Jabra BT200 to bond and work correctly.
This is what nokia says about it?
*Compatible phones must support the Bluetooth 1.1 specification and Handsfree profile.
As far as I know the hp 6315 doesn't support handsfree only headset?
Any help would be greatly appreciated.
...have you tried the "explore a BT device" in the BT connection wizard, not the "handsfree/headset" set-up? I paired it together once & it worked fine...I do beleive this "widcomm stack of BT" supports handsfree...
BTW, after I added another headset (my SE HBH-65) it didn't connect again, but BT is funny/finicky doing multi-device connxns...
Nokia Carkit with HP6315??????
Thanks , I will try that I will let you know.
...another tip...even better tyhan the last one that I don't think is necessary if you use this one : when pairing h-set/handsfree device about half way thru the wizard hit the tools button (I think?) & it default-checks, "show only handsfree devices", uncheck that & you should now see the carkit show-up! This of course makes no sense since the carkit is a handsfree device but it seems to work so go with it...
thanks that did the trick!!!!!!
I just yest spent some extended time with CarKit (it in my wife's car) & it wasn't very reliable. After turning the car off & then back on it would not re-establish a pairing. After resetting both iPaq & carkit (turning off & on again, I'd go thru the wizard again & it would re-establish but would duplicate the carkit on the iPaq...
Has your kit been more reliable? (I have the nokia Cark112)
nokia car kit with ipaq
No. mine has been doing the same thing.
...ya, my work around has been to delete the previous carkit pairing & re-establish itself - a new one - obviously not great but workable if you need it...btw, every Nokia phone (even the newest ones) work fine with this kit...so who knows - I may get the Nokia 9500...
Hi Guys,
Recent got an XDA IIi after being with the older XDA II for over 16 Months.
But I have recently run into problems with my BT Car kit :
Motorola Bluetooth Car Kit HFW-8000.
Basically the problem is that it does not always connect to the Car Kit and when it does it will only from time to time connect and let me have a handfree conversation.
I have also used the Broadcom Bluetooth Cab file here in order to extend what Bluetooth Profiles that can be used but seems not to have any great bearing to stablize the issue.
So I went down the Hard Reset Road but again still intermittent issues, I then upgraded the ROM to the New one on the O2 Website the v 1.11.169 ROM.
I also had similar issues with the XDA II but it was resolved by using the Pocket Bluetooth tools, which was great and never once after installing it did I have any issues with the Car Kit.
http://www.bluetooth.jazztel.es/
One of my questions is, is there a similar programme to to above Pocket Bluetooth tools for the XDA IIi as I have tried it with the XDA IIi but does not work.
Or does anyone know how you would revert to have the XDA II radio or is there a work around for it.
Thanks Guys
Woody
Hi Woody_XDA,
I have had my XDA2i for a couple of months now and recently got a O2 blue headset for it, I had simular problems with the headset disconnecting and having to manually connect every time I switched it on. After browsing this wonderfull forum I decided to do a corperate install and get rid of the O2 active interface, since then no problems at all. I now use Pugs modified ROM version 162 with radio 1.04 and have no stability problems at all with no twice weekly reset. Hope this helps you and many thanks to Pug for his ROM.
Mace
Ditto, I also use the custom firmware with 1.04 radio and bluetooth works a charm. It still eats battery like nothing else, but it works with no problems. Also like the fact that the XDA can cope with my GPS receiver and my handsfree kit simultaneously, that's handy for in the car.
Cheers Guys for the information, took it on board and works great, did a great deal of stress testing in order to confirm it and works excellent..Thanks to PUG again and guys thanks for the info much appreciated and this is by far a great forum
Mace - you mention some bluetooth issues being resolved since you applied the custom ROM... I posted in the Alpine Applications forum here the other day a list of issues with bluetooth that I was wondering had been addressed - so far no reply - are these the symptoms that were cured for you??
Hi Bewlay Brother sorry, I missed your other post on Bluetooth issues, my original problem was that every time I switched on my BT headset , which is a O2 Blue, I had to open the BT manager and make the connection, the phone would then occasionally lose the connection and sometimes whilst still showing a connection refuse to transfer the call. This was using the official 162 ROM with the O2 active UI. I have since installed Pugs 162 ROM with radio1.04 and done a corporate install and BT seems to work perfectly, switch on the headset, it connects, never loses pairing and transfers calls.
Hope this helps you, and thanks again to Pug,
Mace.
Mace - what you describe sounds similar - my problems were essentially the loss of pairing with my Motorola headset a lot of the times when the XDAIIi switched off its display and went into stand-by mode, also if I closed the boom bike on the headset (to temporarily turn off the headset) it would fail to re-pair when I next opened the boom mike... the other issue was that I had to make sure the phone keyboard was displayed on the XDA once I had paired up otherwise the last number redial function on the headset would not work - if I pressed the dial button on headset and the phone display was not on the screen it would simply open the phone display function but fail to then dial the number - really crap. Also reception was poor to headset even over relatively short distances from the XDA. IF these areas in particular could be cured by the upgrade then I am eager to do it - I must admit I have read that this upgrade has not been without problems for some people here so it is going to be a tough call.
Just a thought, but have you done a personal or corporate install as I think the main fix with Pugs ROM was the upgrade to radio 1.04, which I don’t think affects the BT, so a corporate install with your existing ROM may make a difference.
Did a corporate install when it was new out of the box...
whats the difference between the corporate and personal install?
Corporate doesn't install ANY of the branded O2 interface - so no gubbins, nothing to slow down the phone, you just get a bog standard Windows Mobile 2003 SE installation, aside from the O2 GPRS and SMS settings. Bosh.
hi
i've been reading the posts and i have the same problem where can i get hold of pug's ROM if it's possible cos this seems to get rid of the problem
And then today, headset will not automatically connect, needing Bluetooth manager to be opened to make the connection. AARRRGH!
BT car kit problems
I have the 1.04 Radio, but it still won't sync with my 2003 BMW 325xi bluetooh or with my 2005 Acura MDX bluetooth.
Help!
Unstable Bluetooth Signal Strength - Samsung WEP200 Bluetooth Headset
Hi, I just got a Samsung WEP200 Bluetooth Headset. It would pair with my O2 XDAIIi but I cannot hear any voice in both incoming and outgoing calls. When I check the BT Manager, it shows a totally unstable BT strength that varies from very strong to very weak. The same headset worked well with other BT phones. My ROM version is 1.11.00 WWE, Radio version 1.04.00.
Any help would be greatly appreciated.
Hi all,
I have posted this question also over a 4winmobile as I cant access xda-dev from work. Hopefully someone here can help.
I've been having difficulty with my Kaiser and a Parrot MK6000 car kit. I have tested the carkit with a Nokia as well, and have some results to report to aid in troubleshooting.
The Nokia was paired with the Parrot MK6000 kit, answers and makes calls and streams audio no problem. When the car is turned off, the pairing ends, when the car is started again the pairing starts back up ... auto, no probs. In addition, if you make a call with the phone, at the end of the call the pairing is ended, but within a few seconds is re-established.
On my Kaiser, I can pair the phone and car kit, but if the connection is lost (ie the car is turned off or bluetooth is stopped on the phone) and then I turn the car back on, it will not automatically pair. It attempts to, the car kit mutes the car radio and plays a tone, but the pairing is not established by the phone. It continues to do this every 30 seconds or so, but does not establish a connection.
Also, if I make a call with the phone when it has been sucessfully paired, on ending the call, the phone will not re-establish the pairing.
My conclusion is that all of my troubles relate to the fact that the pairing will not re-establish once lost.
Is anyone able to assist? I have upgraded the Kaiser radio to 1.27.12.32 (yes ... just tonite, see http://forum.xda-developers.com/showthread.php?t=349528&page=2) but have also tried radio roms 1.27.12.11 and 1.27.12.17 with no success. The ROM version is 1.81.861.0. Ive also tried installing some of the BT stacks that were developed up for the Hermes with no success. I've also installed Jetware with no sucess.
Getting very frustrated!
Adam
adamcullen said:
Hi all,
I have posted this question also over a 4winmobile as I cant access xda-dev from work. Hopefully someone here can help.
I've been having difficulty with my Kaiser and a Parrot MK6000 car kit. I have tested the carkit with a Nokia as well, and have some results to report to aid in troubleshooting.
The Nokia was paired with the Parrot MK6000 kit, answers and makes calls and streams audio no problem. When the car is turned off, the pairing ends, when the car is started again the pairing starts back up ... auto, no probs. In addition, if you make a call with the phone, at the end of the call the pairing is ended, but within a few seconds is re-established.
On my Kaiser, I can pair the phone and car kit, but if the connection is lost (ie the car is turned off or bluetooth is stopped on the phone) and then I turn the car back on, it will not automatically pair. It attempts to, the car kit mutes the car radio and plays a tone, but the pairing is not established by the phone. It continues to do this every 30 seconds or so, but does not establish a connection.
Also, if I make a call with the phone when it has been sucessfully paired, on ending the call, the phone will not re-establish the pairing.
My conclusion is that all of my troubles relate to the fact that the pairing will not re-establish once lost.
Is anyone able to assist? I have upgraded the Kaiser radio to 1.27.12.32 (yes ... just tonite, see http://forum.xda-developers.com/showthread.php?t=349528&page=2) but have also tried radio roms 1.27.12.11 and 1.27.12.17 with no success. The ROM version is 1.81.861.0. Ive also tried installing some of the BT stacks that were developed up for the Hermes with no success. I've also installed Jetware with no sucess.
Getting very frustrated!
Adam
Click to expand...
Click to collapse
Have you tried these registry tweaks? http://msdn2.microsoft.com/en-us/library/aa915920.aspx
There is a know problem with the Parrot kit and you will find a thread in this forum where a member has contacted Parrrot who replied that they are addressing the issue.
This one my be usefull.
http://forum.xda-developers.com/showthread.php?t=340908&highlight=parrot
NuShrike said:
Have you tried these registry tweaks? http://msdn2.microsoft.com/en-us/library/aa915920.aspx
Click to expand...
Click to collapse
Hi, thanks for that pointer ... most of what is described in that MSDN library isn't in my registry.
Im going to manually insert them all and see what happens.
A
Still no luck
I tried updating the Reg with the tweeks as suggest ... but still no luck. All i get is still the initial pair, but on disconnection, no automatic re-pairing of the device to the car kit.
Im doomed at this stage.
You're not alone. I have the same problem with my Motorola S9 headphones and Microsoft SYNC in my 2008 Ford Edge. Sometimes I have to turn BT on and off a couple of times for it to connect.
agreed
Turning the BT on and off a few times has also be part of my "solution" package.
This really isn't acceptable though. This device should automatically pair up, just like every other BT device does. BT is a protocol that should be adhered to and just work.
I have also tried this on my other WM device. It pairs a little better, but is not great. I've tried compairing the registry values of that device to my Kaiser, but I just dont understand the functionality of the reg settings enough to work out what to change.
Is there some developer out there who can help? This type of problem was experienced by us all back in the early days of the Hermes and this community sorted it out.
Can any developer out there help, like working out a port of the Widcomm BT stack for Kaiser?
a
Interesting. I have a Nokia CK-7W bluetooth car kit and the Tyn II has re-connected/connected to the kit every time. Actually more reliable than my SE K800i. Sorry that it doesn't help you.
Hey Juzzman,
nah, that doesnt help ... but does increase the frustration level!
Seems like you need to have a Nokia component in there somewhere for it to work ;-)
Anyhow, Im still convinced it is a bluetooth stack problem in the Kaiser. I'm going to try flashing one of the AT&T based roms and the other radio version and see what happens.
Cheers
Adam
I've had BT issues with all of my HTC devices, it's very frustrating.
Currently I've got a Kaiser (Orange), E650 (Orange) and a new S730, none of which work on my Pioneer headunit without Jetware.
The Kaiser with Jetware pairs up ok, but the sound is really tinny.
The E650 with Jetware sounds fine, but I can only send 150 contacts to the headunit.
The S730 doesn't pair, haven't put Jetware on it yet.
In the past I've had BT issues with M3100, C600, C500 etc etc.
Why the hell doesn't MS sort out their bloody BT stack!!!
Bluetooth problems
I am having the same problem with my JVC bluetooth unit BT1000. It will pair ok first time, allows me to make 2 calls. Will not the reestablish a connection/pairing. JVC worked fine with my sony erricson and nokia phones. Anyone found a cure to this?
Same problem with the stock AT&T rom (1.27.12.11) with the H700 headset.
Turn bluetooth on it normally sees the headset. If not turn it off and on again to get it to work. Once working it normal looses the connection after an hour or so.
Could it be a BT 2.0 Compliant issue?
I have posted this same problem earlier in xda-deveopers, on htc wiki and aximsite. Many people have viewed and are experiencing this same problem, but no one has posted any solution specific to my problem either. I hope a developer can solve this one for us. Is it a BT stack problem, or a BT 2.0 compliant problem, or a need for an updated ATT ROM to solve this issue? (I currently am using the stock ATT ROM 1.57.. that shipped with my Tilt.)
When I use my Motorola H700 with the Tilt the BT works fine, UNTIL, I use the voice speed dialing from the Tilt. Once I use the voice speed dialing directly on the Tilt, the Motorola H700 will no longer connect. I have to do a soft reset or go through the pairing process again. Once I re-establish pairing again, the H700 will continue to work fine, UNTIL, I use the voice speed dialing on the Tilt. Then we're back to having to do a soft reset to again establish H700 connection with the Tilt.
NOW, I just received a call back from an HTC tech who told me the problem is likely due to the Motorola H700 being only BT 1.2 compliant. He recommended that I try the Motorola H12, which is BT 2.0 compliant, but he could not absolutely guarantee this would solve my problem.
Does anyone know for SURE that the Motorola H12, being BT 2.0 compliant, will solve my problem? Or is there another solution?
Note: I have tried MS Voice Command 1.6 (full version), but the above problem still occurs. I have also tried Jetware, but again, no go. I am not sure that there is going to be an updated AT&T ROM to solve this issue either.
Additional Note: I have also tried other BT devices, such as the Jawbone, and the Plantronics Voyager. All do exactly the same thing as above.
Anyone have any solution? If the Motorola H12 is the solution, that would be great...
Thanks in advance.
I'm having the same problem with my new carkit. Did anyone ever find a solution to this??
Please only repond to this if you have solved carkit issues.
I have a JVC AVX33 headunit with bluetooth, worked perfect on my old SE K800i, however on my diamond it keeps "booting" the bluetooth connection.
Connects for 30 seconds, looses connection, and connects again.
Is there a possible fix for this?
New Bluetooth Stack?
Tweak?
Or an explanation to why this is happening?
It Renders my Diamond useless in my car setup, and this would meen the world to me to have fixed.
Would purchasing a PARROT bluetooth carkit solve the problem?
Do you search the carkit with the phone or vice versa let the carkit search the phone?
I would recommend to test both setups. Do not forget to make your phone visible for the carkit when you want to pair it. Are you able to enter the bluetooth pair code on the phone when requested?
Hi, i have a Pioneer deh-p9800bt with bluetooth handsfree function and the only way to use it with wm6 and 6.1 (Htc Jamin, Gsmart i120 and Gsmart T600) has been to install Jetware HandsFree Extension. With the Gsmarts the Pioneer connects automatically and all works perfectly, with the Diamond the connection must be started every time from the Pioneer, but, then, all works (also battery and signal level): i think that a registry tweak has to be made in order to have an automatic connection.. i will try to see the differences between the registry settings of the i120 and the Diamond..
Yes i tried pairing both ways phone -> headunit and visa versa, and i am able to pair the two devices with code. However it keeps booting the bluetooth, looses connection and then getting it again. About every 30 seconds.
And i tried JETware yesterday without any change, however i am going through the different JETware config add-ons today to see if the result is better.
I think that its when the phone is trying to update the contact list to the headunit, it crashes the bluetooth. Anybody know if it is possible to change the bluetooth stack driver with another? on the HTC Touch Dual i had previous the bluetooth worked just fine.
bump bump bump
I'm having issues with a bluetooth conflict.
My set up is as follows:
- AT&T Tilt - WM 6.1 stock ROM
- 2009 Toyota Camry XLE V6 paired to the Tilt with Hands free profile
- Motorola S705 paired to the Tilt with Wireless Stereo profile ONLY -- I don't pair with Hands free profile. The S705 is connected to the Camry via an aux connection.
I also have GpsGate running in the tray with a bluetooth GPS receiver, but that seems immaterial to the issues I'm encountering.
When I pair the phone as above, the music from the car speakers skips to the point where it will be inaudible for 2 - 3 seconds per 30 seconds of music...no hissing or popping...just silence. The 2 - 3 second pauses are not regularly distributed.
In order to resolve the issue, I go to bluetooth setup on the Tilt and select the Camry Hands free and select 'Set as Hands Free', which, paradoxically, does exactly the opposite...it disables the pairing with the car (until I restart the car). However, once I do this the Wireless Stereo connection is rock solid. Alas, in this configuration, I can't get dial or hang up, hands free, via the steering wheel buttons.
I'm tending to believe the issue is the Toyota since I can connect a Scala 500 as Hands free without issue when playing music in the car (FYI, at no time do I have both the Toyota hands free connected and Scala 500 powered on at the same time).
I'd love to know:
- How I can confirm the problem is with the Toyota, since it is likely they will simply point to the Tilt or the S705 and claim that it is the culprit? I would like software output that demonstrates the Toyota's bluetooth implementation is ill-behaved.
- If the issue lies with the MS stack instead. My understanding from another site is that the MS stack was hacked to allow A2DP. I wonder if the MS stack is simply performing poorly and the Camry bluetooth setup is simply doing what it ought to do. If I could replace the MS stack with the Widcomm stack, this might allow me to test this premise.
In searching I've found some other threads which deal with Kenwood stereo systems and different symptoms (restarting), so I'm not sure the problem is related
http://forum.xda-developers.com/showthread.php?t=442370
I've also searched and found information on replacing the bluetooth stack. No confirmation in the thread whether this will work with the Tilt
http://forum.xda-developers.com/showthread.php?t=449775
Options i'm considering:
- replace BS stack with Widcomm -- no confirmation on whether it works on Tilt
- installing JETware -- mixed results in other threads, Tilt isn't listed as compatible
- reverting to 6.0 -- mixed results in other threads, don't relish the idea of going backwards (HTCHome via cab, etc.)
Edit: That would be the BT stack, not the BS stack (freudian slip)
Does anyone have any experience with the same problem, suggestions as to what options will likely bear fruit or if there is a simpler option? I'd prefer not to do a hard reset and re-install everything I have on this phone if I can get away with a simple fix.
Thanks.
Im having similar issue
I purchased a new headset for my motorcycle helmet.
I can not get the hands free working..
I have another headset that works with the phone, this ended costing me shipping charges thinking the helmet headset was bad.
I have searched many sites and have come to the conclusion it is the phone.
I have not seen anything that gives me an indication that we will find a fix..