Hi!
I have a Logitech Mobile Pro 2 headset.
It was working fine until yesterday. The ppc just forgot its settings and I tried to pair again. It does not pair anymore.
Pairing with other device worked fine tough.
I suspect that there are still some entries for this device in the registry (I already found some entries and erased them) and because of this the ppc thinks, it is not possible to pair with this device.
Before I make hard reset and have do all the installation again, does anybody have any idea, where in the registry I should look to clean up? Or any other ideas?
71 views and no answer?
nobody has any clue?
Do you have any unpaired devices you can test with?
I already made tests:
pairing the headset with other phone worked ok
pairing other phone with my pda worked ok
only pairing headset (which was previously paired with it) with my pda does not work
I would export your registry to your desktop and do a search for whatever you named your pairing and delete those keys on your phone.
I already tried to search in the registry with total commander...
how do I export the registry on my desktop???
I suddenly have the same problem with my Plantronics 590a
Hi,
I'm desperatly searching the forums for solutions for this problem, because i suddenly have the same.
A couple of days ago, nothing was wrong... My MDA Pro and my Plantronics Pulsar 590a had been paired for a couple of months, and life was good.
My headset would play the beautiful music my MDA streamed from the world wide web, and would happily switch to telephone mode on demand. Not a cloud in the sky...
But then, suddenly, after a day's worth of perfect operation, i received the message on my MDA that a bluetooth device called 'plantronics 590a' wanted to pair with the phone... Okay, i thought, and entered the top-secret passcode: '0000'. strangely, it did not accept the code, and the bond was forever lost...
I've tried several things, but havent been able to pair the two devices again...
here a list of bonds that i tried:
* my universal - my plantronics 590a = no bond, passcode not accepted (worked previously)
* a htc tytn - my plantronics 590a = no bond, passcode not accepted (worked previously)
* my universal - motorola h500 = succesful bond, only headset profile supported
* plantronics 590a transmitter - plantronics 590 headset = succesful connection
* motorola v3 - plantronics 590a = succesful bond, only headset profile.
* my universal - tomtom BT GPS receiver = succesful bond
needles to say, this is quite confusing...
my universal accepts other headsets,
my plantronics accepts other phones
but somehow they dont wat to pair together.
And if I try it on an other htc device with wm5 and a2dp, it also doesnt work anymore...
I've even called plantronics and t-mobile, but they dont understand the problem either... plantronics says it must be a phone problem, and the phone company (which are utter dimwits...) say it must be a headset problem...
Can anyone help me out?
my universal has the latest t-mobile NL rom on it:
ROM: 1.30.115 WWE
Radio: 1.10.03
ExtROM: 1.30.233 WWE
programs installed include:
Pocket ZenPhone
SPB pocket plus
Resco Explorer
Opera
Tweaks2k2
tomtom
wm5 storage
logmein remote control
SOTI pocket controller
My first BT headset had a feature to reset the headset, do your devices?
Pairing goes both ways and although the Universal isn't perfect in a lot of ways, neither are BT devices always faultless.
If you can do a reset on them, good. If not, pull the battery out (mind that warrenty!) for a while and try again.
resetting the headset
Hmzz.. resetting the headset... would need to remove the battery for that...
Sounds a bit tricky, I'd better call plantronics up for that again...
Thanks for the advice though!
Called plantronics today...
I rang plantronics up about this problem today, and suggested removing the battery to them. They said this can't be done without breaking the device, apparently they never replace the battery but just replace the entire device if there is something wrong...
i'm not quite sure if this is just to scare me off, but has anyone ever opened their pulsar? and if they did, how?
the only other option plantronics gave me is to send an email to their customer service, so they could have another look at the story...
I'm pretty pissed off right now, it's a bloody expensive headset, and plantronics keep telling me there is nothing wrong with it, and that it must be the telephone.
And the phone company says that it must be the headset...
aargh!
I'm being sent from the cubbard to the wall!
Well... thats a litteral translation of a dutch saying which basically means that you are being sent backwards and forth between two companies who point the finger at eachother..
Related
I have only had my XDA 2 for a week and I can’t get my Motorola 810 head set to work. The XDA finds it and tells me that it is compatible with headset profiles but it doesn't seem to work. Can anyone advise me?
Thanks
Andy
Have you followed the procedure for pairing the device,ie: place xda in discover mode, when it finds the headset, tap then enter code for pairing, once paired switch bluetooth to on, then make sure you have bluetooth headset turned on from the main/today screen.
I seem to have problems with my bluetooth headset every once in a while also. I have a HBH65. On ocassion, the connection doesn't seem to be working even though headset is enabled and they are paired. I've found that if I soft reset the XDA2, that the bluetooth headset will work again.
Have you installed towas bluetooth tools patch, this fixes a lot of problems with bonding and alos makes things work where they couldnt before. I was told that the latest rom release here in UK was going to address all these problems too but I havent got around to upgrading yet, I hope it supports full headset profiles so I can originate calls from the headset as well as answering the call.
I have downloaded the new Rom update and it seems no different. I have tried a soft reset and this did not improve the situation.
I know the headset works fine as I use it with my nokia handset with no problem.
Has anyone got a Motorola 810 that works ok on the XDA ?
cruisin-thru said:
Have you installed towas bluetooth tools patch, this fixes a lot of problems with bonding and alos makes things work where they couldnt before. I was told that the latest rom release here in UK was going to address all these problems too but I havent got around to upgrading yet, I hope it supports full headset profiles so I can originate calls from the headset as well as answering the call.
Click to expand...
Click to collapse
did the bluetooth tools patch support voice dial from bluetooth headset? if not did anyone know the new rom from O2 works with this function? thanks!
Andy, no it doesnt support originate call from headset but it did allow lots of different gps and headsets to work, the headsets work for answer call/drop call only as far as I know, in the notes for the xda2 upgrade it mentions the headset profile but I dont know if anybody has hot the headset facility to work yet, I havent upgraded yet so I am yet to test it.
I have installed the new ROM and as far as I can see it does nothing for Bluetooth beyond fixing some compatibility issues on some headsets. It still only allows one headset profile (so if you have a headset and a handsfree kit as I do you need to delete bonded pairs when you change devices - now there's intelligent functionality!!). No headset dialing so still not a complete BT headset implementation. No handsfree support.
Anyone else think that the XDAII is a great PDA but about the worst apology for a GSM phone in the last 10 years?
If anyone can point me to a decent set of BT tools to add on let me know.
Not really.
I fully agree the XDAII is a poor phone, with the best agenda and contact list available, but that is!
I wonder if Phone-pda makers are really going the so called "convergence" way.
To date, and after many different PDA/phone/PDA-Phone devices I've tried, no one is even close to the mark.
Something so "simple" such as merging an OLD Ericsson (or Sony-Ericsson) T-68 phone abilities, with just a PPC 2002 (yes, not even 2003) PDA, should produce a combo, no machine on the market is even close to.
IT'S SO DIFFICULT?
:evil: :evil:
The btagsvc.dll on the Universal does exist, but it is empty (same with the HID dll). So that may be the reason why Audio Gateway is not working (getting the system sound forwarded to the BT headset).
Now, a friend showed me an interesting trick. Run a music file or any other program that outputs sound (like a navigation instruction from TomTom) and then press the Speed Voice Dial button.
Interesting, isn't it? So maybe all we need to do is prevent SpeedVoiceDial from exiting again?
Hey!!!!
A2DP is already there...just do a search :lol:
hdubli said:
Hey!!!!
A2DP is already there...just do a search :lol:
Click to expand...
Click to collapse
If you're talking about the M$ stack on the Universal, then you'll have to elucidate a bit more than that - unless you mean:
"The A2DP profile is introduced in AKU 2.0 of Windows Mobile".
But then isn't that scheduled for first quarter 2006. Even then, surely it's down to HTC to make it available for the badging suppliers, o2, T-mobile, etc., to decide IF and WHEN to issue the update.
I tried the LaunchAPEnable = 0 registry hack but it won't stick. My Jabra 110 headset would only receive the audio for a few seconds and then it would all fall back into the Xda Exec. I'll try another headset just to be sure but I'd have to agree - this seems far from being solved.
EDIT: indeed it works with another headset (Solteras Halo). Is the Jabra too agressive in it's power saving quest?
nice to see its doing you head in master :lol: :lol: the jabra bt250 is the same as is my logtech and motorola bluespoon 3-4 secs via voice dial and nothing
nice to see its doing you head in master :lol: :lol: the jabra bt250 is the same as is my logtech and motorola bluespoon 3-4 secs via voice dial and nothing
I've been using a bluetooth headset (Jabra BT-800) to listen to audio books just fine on the JarJar Universal. There are two ways (so far) to get it to work. One, if you install Microsoft Voice Command and use the registry hack found in this forum to make it the default via the Voice Dial button, run it, then let it cancel on its own, the BT audio connection stays intact for running regular audio through it.
The second (and free) way is to use a utility found in the I730 forum in pdaphonehome.com called BTAudioToggle. Written for the I730, it works on the Universal too. I imagine it will work on all the flavors of the Universal. Connecting your BT headset, followed by running this BT app will also activate the BT audio connection. Its pretty rock solid though its mono, not A2DP
Nice application but it only works for Universal for a few seconds. Then it returns to the device with the voice dial application activated.....
So, it seems that I have to disable the voice dial application. Anyone knows how????
Thanks in advance.
Cheers,
I tried the BTAudioToggle on the Xda Exec, and it doesn't seem to do anything .
@chris_khho: try a different headset. As I wrote the Solteras Halo was working fine with the registry hack but the Jabra 110 would only work for a few seconds. I'll need to check what profiles each of them suports.
RE
Hi!
BTAudioTogggle works on my QTEK 9000 for a few seconds when Voice Speed Dial is activated. Once Voice Speed Dial ends the music transfer stops
:roll:
Mine works fine and I've played my audio books for more than an hour and it never dropped. I'm not sure why it doesn't work for you guys. Maybe the reason the BTAudio hack works is because the MS Voice Command setup is installed and the BTAudio hack just makes use of it.
You know, now that I think of it, I have an I730 too and before the BTAudio hack came out, I was already using MS Voice Command to activate audio over BT. I think there's a (good) bug in Voice Command where VC does not release the audio stream if you activate it, then don't give it any commands. The BTAudio hack just made it easier to activate.
OK I see.
I tried this:
hklm\software\oem\voicecommand and set the value of "launchapenable" from 1 to 0
And it works with my i-tech clip s and jabra 258 (not sure the model no.), and WMP but it doesnt revert to BT headset after finished call....
Yes it is "mono" but its good though....just wait for AD2P..... Many people are working on it I think.....
Great People Great Work!!!!
Cheers,
Any more info on what each update fixes.
Of particular interest is the bluetooth patch????
Ok I see.
I tried this:
hklm\software\oem\voicecommand and set the value of "launchapenable" from 1 to 0
And it works with my i-tech clip s and jabra 258 (not sure the model no.), and WMP but it doesnt revert to BT headset after finished call....
Yes it is "mono" but its good though....just wait for AD2P..... Many people are working on it I think.....
Great People Great Work!!!!
Cheers,
_________________
Chris
Thanks Chris,
I have a o2 exd exec with the h500 and this works perfictly
Jeff
I have a Nokia CK-112 (now CK-1W) Bluetooth Car Kit and seem to have a problem connecting it to my Wizard.
It was working brilliantly with Nokia 6310, 6310i, 6230 and 6230i phones.
Now, I have tried to use it with my Wizard. Wizard has correctly discovered Carkit 112 appliance, but is not showing any services available. I can pair it, but option Set as voice ... smth, I don't know exactly what it is called on English ROMs is grayed out when clicking on the paired device. This way, I cannot use in handsfree mode.
Any advice anyone?
Kotek
Addition
Just to update:
1. My Wizard is AKU 1.1, so it should support both headset and handsfree profiles.
2. In Bluetooth settings, I can see Carkit 112 with a headset icon next to it.
Best regards,
Kotek
Possible Solution
Same problem.
Tried a trick I found in a german site but unfortunately.
I keep on and come back
GV
Edit: perhaps TOO late but found the way! It has to do with fiddling with the registry and adding some missing keys and values taking as example a working bluetooth device....
ive searched for ck-7w in the hermes section but finds nothing? surely others must use this handsfree kit?
Well my issues, my hermes wont find it when searching for bluetooth devises? Never had any issues with my wizzard?
ive tryed a few different wm6 roms, now on the black.
Is there a cab somewhere to fix this, as i cant, use this phone until i get it sorted with my car kit
Hi fil,
I can't speak to WM6 but my 7W works well (usually) with my 8525 WM5 ATT Upgrade Rom. I remapped the ptt button to activate the built-in voice dialing. Sometimes the system announces the name throught the 7w speaker, other time via the 8525 speaker. Who knows why?
The quality of the recognition software is fair. I am planning on re-recording some of the voice tags in the car via the 7w mic. I have a feeling this will result in greater accuracy. It has to do the the acoustics where the tags are recorded.
My BT settings in the 8525 are
Mode = Turn on BT and Make device visable
Devices = add new device, if it finds it, click on Nokia CK-7w & check off Hands Free, at the bottom of the screen hit Save
BTW, the 7w data cable 5 volt lead does not have enough balls to charge the 8525.
Let me know if you get WM6 working with the 7w.
Lyle
You've already tried to reset the CK-7W ?
Especially when your Nokia Carkit has an other mobile paired in his memory (an old one for example) it won't pair the Tytn.
Worked for me (reset CK-7W).
After that my carkit works fine with yhe Tytn but has proplems if I wan't to pair a second (Symbian) phone.
alylea, my tytn wont even find it, when searching, have ticked the make seeable to othe devices, the method you discribe works perfectly as said on my wizard
davw, reset the ck-7w how?
tho the ck-7w can do up to 7 phones in its memory i belive, had no issues with a wizard and 2 different nokia all paired on it allready?
davw said:
You've already tried to reset the CK-7W ?
Especially when your Nokia Carkit has an other mobile paired in his memory (an old one for example) it won't pair the Tytn.
Worked for me (reset CK-7W).
After that my carkit works fine with yhe Tytn but has proplems if I wan't to pair a second (Symbian) phone.
Click to expand...
Click to collapse
again how'd you reset it? dont have the manual
still aint working, see unable to see the kit!???
anyone?
right its working now?, done nothing different?
was sitting in my car thismorning doing a bluetooth search for my new stereo headset i picked up from the PO on my way to work, it found it and the carkit , and paired with both!
well problem solved, but **** knows how ???
No idea what did the trick but here is the Nokia Europe site for the manual.
http://www.nokia.co.uk/A4222096
So iGuidance voice instructions do not come out of the CK-7W speaker not do the voice dialing confirmation names, although basic HF function works. I'm testing an inexpensive application that routes all audio from the 8525 to the BT output. I'll let you know if it works.
I have Jabra BT320s stereo Bluetooth adapter, which I use flawlessly with Nokia E71. When trying to pair it with my HTC Magic, it fails. Basically, I put Jabra into pairing mode, then invoke pairing from Magic, and it says 'Pairing...' forever - virtually nothing happens on both Jabra and phone side after that. However, occasionally Magic pops out a PIN request after a while of waiting, but putting default 0000 PIN also doesn't help. I've even tried a hard reset (factory reset, that is) today but still no luck.
Anyone tried pairing A2DP device with Magic and could tell their story on this?
Sony DS970 pairs & works - mostly.
I have managed to easily pair a set of Sony DS970 earphones. The sound quality is very good and can control the standard music player.
The process went: turn on bluetooth -> discoverable -> search -> find -> pair -> working
It won't control TuneWiki though which is a shame.
Occasionally I have suffered from sound drop off when listening to music although it's fine when using in calls.
Thanks for that BigRD. I will try to hard-reset and/or upgrade firmware in my Jabra A2DP adapter later in the evening. Maybe that would help somehow...
I have finally managed to pair my Jabra successfully. I did firmware reset on it, but at first Magic still wasn't keen on pairing. But I tried couple of times, and finally took different approach. Once Magic stopped scanning BT devices ('Scanning...' and circling indicator have both disappeared), I've then started pairing process. Voila! Paired within seconds!
Excellent news
You're next mission:
By the end of today I would like you to figure out root access and share with the community
BigRD said:
Excellent news
You're next mission:
By the end of today I would like you to figure out root access and share with the community
Click to expand...
Click to collapse
Hahaha! I am not that Android-power-user (yet)