Need help with Bluetooth problem - 8525, TyTN, MDA Vario II, JasJam General

Hi all,
Just upgraded myself from a Wizard to a Hermes and am mostly happy, I used the crack program to unlock it from T Mobile and upgraded it to WM 6.0.
Mostly it is great, I just have two problems at the moment,
1. I am able to pair any bluetooth device, but when I try and talk with my BT headset ( WEP200) all I get is white noise, it worked fine with the Wizard.
2. I have paired my GPS unit ( also worked OK before) but I do not know how to make it recognizable by the software ( i-go) I have tried using the 'External GPS' feature but nothing, any help would be great.
THanks

same problem for
i try with 2 different bt headset
any idea to fix?

Related

Help please! Bluetooth headset woes...

I have purchased an O2 XDAII in Oz which is loaded with the 1.66 ROM. I have tried connecting two headsets to the phone over bluetooth with many problems.
Both seem to bond ok and work initially but later they fail - the XDAII doesn't respond to anything I press on the headset. Or the XDAII does respond (answer or end call) but no-one can hear me either through the headset or the phone.
Deleting and re-bonding seems to temporarily solve the matter. But if the XDAII goes to sleep and comes back on it stops working. Will also just stop working for no reason after a call or two is made or received.
I have tried installing the bluetooth tools which is cool because the XDAII can recognise some of those extra headset profile functions (like redial) but I still get the same problems as above.
Tried Plantronics M3000 and Motorola HS801
What can I do? Is it this Bluetooth stack problem from MS I have read about? Do I need a ROM upgrade? Do I need Widcomm something installed on the XDA II? I don't know how to do any of these myself. Any kind advice from a pro is appreciated in advance.
When you installed bluetooth tools did you delete any bonding and pairing of devices beforehand? it can make a difference if you havent done this.
Yes. I tried it twice thinking that maybe I might guess a way to make it work.
First I deleted the bonds after installing BT Tools and then rebonded.
Then I deleted the bonds before installing BT Tools and then rebonded.
I spoke to my Telstra dealer again today and they received a list from Brightpoint (a distributor) that matches various headsets against various PDA's available in Oz.
Not all BT headsets will work competently with all PDA's. The M3000 is marked as NOT compatible with the O2 XDA II available in OZ. So was the Motorola too.
I am now using a Hello II headset which so far is fantastic (very small and comfortable to wear) and is working with no modifications to the XDA. I will post back in a week with a fuller review. I'm going to re-install BT tools and see if that make a difference with the available functions.
Anyone else wanting to test these out in Perth, WA, (Australia) - they are available from Communications Plus.
Help
I can stop the sleep mode ... I have a MOTOROLA HS-801 Bluetooth Headset
Help
how can I stop the sleep mode ... I have a MOTOROLA HS-801 Bluetooth Headset
I had a problem with my Plantronics M3000 too so I called Plantronics themselves who said that the problem is with the phone, not the headset. It's a compatibility issue with the software.
Unlikely to be any fix, at least not in the near future.

O2 Clip BT headset and XDA2i

Hi
I've received my XDA2i today and am very pleased with it...even if my girlfriend was less than impressed given it's likeness to the XDA2! Hehe...
Anyway, I am having great difficulty getting my o2 bluetooth clip headset to pair up and connect. I have tried and rechecked everything I can think of, yet when I try to connect it as a headset / handsfree in BT Connection Wizard, it comes back (after asking for the legtimate pin) saying "an error occured while attempting service discovery. Please make sure the remote device is turned on, BT is enabled and the device is discoverable and try again".
I've checked on my old XDA2 just now and it recognises it straight away. Obviously the 2i is doing something because it asks for the pin.
Can anyone help?
Cheers
Anthony
I somehow managed to pair the headset which does now show in bonded pairings.
Also whilst performing a hard reset I managed to make it a hands free headset briefly so there doesn't appear to be a problem with the headset (and it works fine with the XDA2).
Is there a way of removing this broadcom stack and replacing it with one that works better? it's currently build 3900.
Cheers
Anthony
Thanks for all the responses!
:shock:
However, now I've resigned myself to this I was wondering if anyone DOES actually knew of a way to remove the standard xda2i BT stack and replace it with a version akin to that present in XDA2 ROMs.
I personally couldn't give two shiny sh*tes about all the other features, if having them means I can't use the damn thing whilst driving!
Cheers
Anthony

Bluetooth and GPS problem

Hi all, I bought a Qtek S100 and tried to connect it with my BT GPS receiver (Falcom Navi 1). It didn't work properly and I suddely lost te BT icon on the lower right hand side of the S100. It hasn't re-appeared even after several soft resets?
Does the S100 have the sae BT problems with GPS as the xdaII had?
I use BT GPS and the only problem so far is that I have to re-pair them sometimes.
Try Start->Settings->Connections->Bluetooth to get to the same screen as you would get to by clicking the BT icon.
THanks for the reply. Which BT GPS do you use? and with what Navigation program?
Holux GR-231 and TomTom3.
I am having problem with Bluetooth GPS as well. I have 2, one is iTrek Bluetooth GPS and one is ArcoreTech Bluetooth GPS.
Since I have tried both GPS units, I am pretty sure it's i-Mate JAM's Bluetooth problem.
Instead of upgrading my ROM to 1.06.00 WWE, I should have tried it out with version 1.03 first. I upgraded from 1.03 to 1.06 as soon as my JAM finished charging. BIG MISTAKE!
I ended up usiing "Pocket Bluetooth Tool" to designate COM8 (for example) for my GPS. However, if I happen to soft reset or turn of Bluetooth, I would have to pair it again.
I read many article's on the internet and the problem seems to point to the MS Bluetooth stack (instead of Widcomm used in my i-Mate PDA2K - and by the way PDA2K works perfectly with my GPS units).
Hopefuly i-Mate will address this problem during the next ROM update.
So how come Loboman's holux works ok?
Loboman are you using a different BT stack?
I would like to guess that he uses ROM version 1.03...
Jazzedout said:
So how come Loboman's holux works ok?
Loboman are you using a different BT stack?
Click to expand...
Click to collapse
I use 1.06.00. All i do is that I tap on the BT icon, choose 'Devices', tap 'New...' and waits until the phone finds the GPS. Then I add it and pair it with the passkey. Then I had to scan all serial ports using a program that Holux supplies (I bet it works with any BT reciever though) to find out that my port was COM5 and finally I set my programs to use COM5. As I previously stated, I do have to re-pair them sometimes for some reason, but I can live with that.
I previously had an Acore unit which worked ok with my iPAQ 5450 (also MS BT stack) in WM2003. It took me all the way from northern Sweden to Barcelona in Spain last summer
I have not used Pocket Bluetooth Tool, but I have read about it. I think that it works without it so far. I also leave my BT on 24/7 since I don't think that it uses too much battery.
I hope things work out for you.
Absolutley no problems with Rom 1.01.01 Ger and Navilock BT-308 GPS-Mouse
I am not sure if the following has anything to do with Bluetooth but at least it cured my Bluetooth vs. GPS problem, for now.
On Club i-Mate's ROM update page, I found out that if the radio version is 1.10, then I am NOT suppose to apply the camera patch. After I uninstalled it, my JAM seems to work better with Bluetooth GPS units. My biggest problems were:
1. Once I soft reset my JAM, I have to re-pair my GPS units.
2. PrymeNav software took a long time to scan for GPS - and crashes sometimes when I designate already-scanned port.
3. Unable to hold two paired GPS units in Bluetooth Device List (though only used on at a time).
I have played with it after I uninstalled the camera patch and to this morning my GPS units still function well. Another key is to turn on the GPS unit and make sure it is linked (as indicated by its LED) - then turn on the GPS software. That way the hardwares are ensured to be linked.
As a side bonus, now I can perform Bluetooth Activesync on my Mac (via PocketMac software). However, I still require Pocket Bluetooth Tool installed on my JAM.
Weird!

Bluetooth

I'm hoping someone is having the same experiences or can help recommend a solution.
I have trinity (Obviosuly) with the latest WM6 rom from the Manufacturer, with Radio 1.50.
I use a TomTom One v2 (with bluetooth), and a Parrot 3200ls.
The TomTom has the latest firmware, as does the Parrot.
When trying to get traffic updates to the tomtom thorugh my trinity, the connction works the first time, but switch off both the tomtom and the trinity, the connection never works again and has to be re-setup.
The Parrot will connect to the phone, but sometimes will not connect at all until i reset the trinity, when it does connect sometimes the sound and mic wont be routed to the car kit and you have top physically pick up the phone , not a good idea in communist Great Britain when your driving!
Ive tried different ROMS, I even tried downgrading my radio to 1.45 with no success.
The trinity is a great device but not being able to use the bluetooth car kit safely, and the tomtom plus services, is seriously making me consider going back to my SE k610, which I really dont want to do but I know works flawlessly.
Thanks in advance.
Craig f said:
I'm hoping someone is having the same experiences or can help recommend a solution.
I have trinity (Obviosuly) with the latest WM6 rom from the Manufacturer, with Radio 1.50.
I use a TomTom One v2 (with bluetooth), and a Parrot 3200ls.
The TomTom has the latest firmware, as does the Parrot.
When trying to get traffic updates to the tomtom thorugh my trinity, the connction works the first time, but switch off both the tomtom and the trinity, the connection never works again and has to be re-setup.
The Parrot will connect to the phone, but sometimes will not connect at all until i reset the trinity, when it does connect sometimes the sound and mic wont be routed to the car kit and you have top physically pick up the phone , not a good idea in communist Great Britain when your driving!
Ive tried different ROMS, I even tried downgrading my radio to 1.45 with no success.
The trinity is a great device but not being able to use the bluetooth car kit safely, and the tomtom plus services, is seriously making me consider going back to my SE k610, which I really dont want to do but I know works flawlessly.
Thanks in advance.
Click to expand...
Click to collapse
Hi there,
I havebeen struggling with issues on my P3600i (trinity) and Parrot 3200 LS. It seems parrot have issues with WM6. The problems I was facing was reset of parrot during call, random divert of calls through handset, I answr sometimes and have to turn off handsfree on the call menu on my phone so I can hear the caller through my handset.
Today I downloaded the latest software for the parrot and uploaded it to the car kit via bluetooth on my laptop. There is a new feature in the paired devices list of "Forced Connection". I used that and low and behold my issues apparently have stopped. I noticed that my phone book isnt synchronising but the fact that I can actually use the car kit is fantastic!!!! I have been dealing with these issues for over 7 months!
Update to the latest version and see if this fixes it.!.!.!

Bluetooth problem

Hi everyone
My Wizard has a strange problem with bluetooth: I pair the devices (in my case, the GPS and the headset), and they work fine. I leave the car, turn off both devices to save battery.
When i'm back in the car, i turn on both the devices and none work with the wizard. I have to pair them again.
Anyone with this problem, or anyone who knows the solution?
Thanks
PS- My wizard has the CR86 1.2 Rom (but before this rom, this problem ocurred).

Resources