Hey guys, I got a Bluetooth headset (a noname caller ID one from Target) about 1 week ago hoping to pair up with my 8125. It worked that night and made one test call with no problems. Got up the next morning, and it would not make a call with the headset. After a couple of tries, I deleted the partnership. From that point, it would not detect the headset again.
I then attempted to pair with my girlfriend's Tilt (which had worked before), her Motorola M500 headset, and a speakerphone kit. In all these cases, the 8125 would not any Bluetooth devices. I turned on discoverable mode, same result. I installed the Jetware extensions, still nothing detected. I then installed the Broadcom Bluetooth stack. With this installed, I could not even turn on Bluetooth. A message told me "The bluetooth radio failed to turn on due to insufficient driver memory available."
At this point, I couldn't even uninstall the stack, as the uninstall program just locked up the phone, causing me to press the reset button. I reflashed the phone with the same rom, WWE OS CE 5.2.20273, hoping the fresh start would help. Retried all the above steps, still couldn't detect other devices.
I then downloaded and flashed my 8125 with WizFlo 20273 with added Manilla 2D. Tried all the same steps, got all the same results.
I even tried scanning with btCrawler at various points and was not able to discover any devices this way either. Prior to pairing with the Target headset, it detected not only the headset but also a couple of my neighbors' devices (I'm in an apartment).
Can anyone think of anything I've overlooked? Is there some trick I haven't tried? Thanks in advance.
Related
Hello,
does anyone here drive a recent BMW that has the Bluetooth phone interface (essentially a bluetooth headset built into the car)? If yes, are you able to use it with an XDA-II?
I can't seem to bond the device with the car - the phone thinks it's done it, but the car just shows "BLUETOOTH PAIRING" and when I try to place a call the phone asks for the passkey and goes through what seems like a successful pairing process - but it does not actually work. The "BMW ULF wants to bond, enter passkey" message keeps appearing and appearing after every seemingly successful bonding attempt.
Anyone?
Marton
bmw bt
with the kind of money you paid for that car, the salesman should come over and do the pairing for you.
I remember reading somthing on this subjet on the forum.
Search the forum:
http://forum.xda-developers.com/viewtopic.php?t=4258&highlight=bmw
http://forum.xda-developers.com/viewtopic.php?t=3981&highlight=bmw
http://forum.xda-developers.com/viewtopic.php?t=5029&highlight=bmw
cheers
Thanks guys! I guess I'm out of luck then.
I tried to use a spare Nokia 6600 I had lying around and I got a bit further, but it's still unusable. The Nokia bonds perfectly, I can call with the car's interface, incoming calls ring in the car's speakers - but whenever the call is answered only the phone's speakers and mic work...
Apparently not only does the XDA-II not support the handsfree profile (if you think about it, why should it? it would be a surprise if ANYTHING BT-related worked on it) but the Nokia 6600 is screwed up too.
I guess I'll have to get a Nokia 6310. That's one of the the recommended phones by BMW:
http://www.circlebmw.com/parts/blue/phones.htm
I just thought that since I had a "universal phone kit" in the car it was supposed to work with any recent BT phone. Universal? That list above is shockingly short.
Have you installed the latest version of bluetooth tools?
Well, Bluetooth tools actually made things worse. It still wouldn't bond correctly with the car, but after that it kept connecting and re-connecting to my PC every few seconds, even when BT was off! (It seemed to turn itself on automatically after a few minutes.) The TDK systray notification was driving me crazy. Getting rid of BT Tools solved this partucular problem.
How is the new MDA-II ROM (1.72) in regards to Bluetooth? I hear that some bonding problems have been solved - is the handsfree profile supported yet? I'm tempted to upgrade but given that it's just a beta and it's hard to go back if I end up disliking it is discouraging.
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..
I don't know what is going on, but last night for no reason, my bluetooth hands free function has stopped working. I've tried 2 different headsets now, un-paired and re-paired, etc etc. It has the 'hands free' checked in the Bluetooth manager, everything looks just like it always has and I never changed any settings. It just will not send the audio to the headsets at all for phone calls. My stereo bluetooth headset will still play music just fine. It also still sends the signals such as to instigate a Voice Command, but it only listens and outputs through the normal speaker on the phone. Really annoying!
Anyone had this problem? It just appeared for no reason. Was working all day and then suddenly stopped. Nothing new installed or anything.
HELP!!!!!
Yes, I have the same problem. It happened about two weeks ago. Although I can usually get the handsfree to do what I need it to do just by tinkering with it. (Deleting the device re adding it deleting again, letting it do it's own auto pair thing etc. etc.) It's a real pain in the ass tho. Sorry I can't really help, but at least you know your not the only one.
p4000 (telus)
Motorola h700
sony dr-bt21g
Opera browser
tnt task manager
spb backup
pocket e-sword
microsoft sqlce 2.0
pocket virtualboss
Microsot voice command (with patch)
Anyone come across this message yet? I added my Bluetooth headset today for IP SoftPhone purposes, and saw that the Shift found a "Bluetooth Handsfree Device (Evaluation Copy)". The headset works fine, but the "Evaluation Copy" somehow does not inspire confidence. Potential license issue in the Bluetooth stack perhaps??
Yes, I saw that when I paired my Motorola HT820 headset, which also gives me a Bluetooth Remote Control Device (Evaluation Copy).
All works fine though.
All worked fine for me aswell... Untill today that is, the connection seemed to skip and after I recoupeled my ht820 I only get sound through my internal speakers.
Both my shift and headset indicate that they are paired.
Very anoying, anyone else had this problem?
Just FYI, its a very basic BT stack included in the Shift, (you will get an error PID install for an HP 460WBT printer when connected via BT but just diasble the offending PID item in device manager and all will work fine.
I am afraid we are victims of our own devices and it goes back to something I said in the Wizard and Kaiser forums...If people here are willing to put in the unpaid hours to sort out HTC's problems they will be inclined to put out more and more devices in "Hobby" mode...
We are unpaid BETA testers for HTC don't ya know!!!
Update!
If you have Vista set to automatic updates for other downloads, CSR have just issued full versions via the service.
Thought I'd fire off a thread to see if anyone else was having issues with BT on their x10's, this stems from an issue I was tracking originally shown by the Wiimote controller app (http://forum.xda-developers.com/showthread.php?t=672884 from about page 21 onwards) where by bluetooth on the phone and effectively the controller would lock up and both would need resetting before they would work again (turning off the bluetooth on the phone would work but then not allow it to be switched back on again untill the phone was rebooted).
I then also tested the BT by trying to do a large file transfer (700mb) via BT from my laptop which was unsuccessful even after several attempts I was never able to get past about 5% (small files <10mb seemed to be ok as I've transfered photos etc accross with out issues), this however didnt result in a complete lockup of the BT it just stopped transfering after a while and would eventually time out (although i did have to unpair and reset both on one occation as the laptop started to fail transfers imediatly before even actually trying to send).
Has anyone seen similar?
Yes, I have had some BT issues, just like you I had BT crash and had to restart the phone to be able to start BT again.
If I remember right, I was just connecting my MW600 headset to the phone, and already had my macbook associated to the headset.
Playing around trying to make the headset work somehow crashed BT (forcing a restart of the phone)
And another problem i´ve had is that sometimes you are unable to reconnect the headset and having to restart BT in the phone to make it work again.
BT also crashed once when I had it connected to my car, in the middle of a conversation, again forced to restart the phone to be able to start BT.
Yeah, there are some issues to iron out...