Related
Hi all,
I have just bought a tomtom bluetooth gps system, I can bond to the gps receiver ok, but it just wn't connect. There is deffinately a connection during the bonding process but that is it, it never connects again.
Any help would be greatly appreciated.
Thanks
Steve
If its anything like the EMTAC then it needs to be considered as a serial port...
Have you tried changing the connection settings in the GPS icon? Default prob to Com1, so try changing.
I can't remember the options 'cos I haven't got it installed myself until later today - but using an EMTAC obviously
Puff The Magic Wagon! said:
If its anything like the EMTAC then it needs to be considered as a serial port...
Have you tried changing the connection settings in the GPS icon? Default prob to Com1, so try changing.
I can't remember the options 'cos I haven't got it installed myself until later today - but using an EMTAC obviously
Click to expand...
Click to collapse
I think the problem is that the xdaII doesn't support a bluetooth serial port profile. I have tried virtually everything and had no luck.
Please keep me posted on how you get on, I really hope we can get this sorted or I will have a gps reciever paper weight.
Steve
Hmm
Due to the nature of yesterday, it wasn't until midnight (GMT) that I could get to have a play with my XDA II & EMTAC BTGPS (& I wasn't sober )
Installed TTN2 and tried to connect - not a sauasage
There "seems" to be something using COM6 and as such TTN2 can't use that as the path to the EMTAC - check box in the GPS options won't check. Turn off BT & you can check the box, but it won't connect as something else obviously can't use it either :? Dunno - I'm not a programmer but I'm going to have to check this out.
I'll speak to a contact @ EMTAC & see if they have been sucessful in bonding to an XDA II (HTC2?) & if so how. Otherwise I'll keep on playing with it & see what I can find out.
Anyone else got any tips or ideas what might be the way of resolving this?
Have you tried turning off the "receive incoming beams" under settings/connections, that may or may not free up the first com port.
I know someone with the same problem. O2 have told him that Tom Tom are working on a new version of software to fix this specific issue and it will be downloadable from the TT site. They couldn't say when.
xdaguru
Beam off did seem to allow me to connect to COM6 but not for my device Might be worth trying Steve because TT Wireless was one I could connect to.
IIRC from iPaq Bluetooth Manager, you had to bring up the device options once bonded and then select a serial connection. Pocket Loox as well. The BT Manager in the XDA II is very basic. So I do wonder if its a TT soluble solution or does it need an upgrade to the BT Manager?
If its a problem soluble by TT then I'm prehaps more hopeful
Sorry to go off topic but I wonder if this is the same PTMW that I know?
How you doin m8?
Hello Danny
Yes it is I
Can't be that many PTMW!'s about
All's well & I'll catch you on the other side one day
Yeah I guessed there could be only one PTMW
I take it you're lucky enough to have an XDA2 already? I always knew u were a gaget fan like myself. I have a month left on my XDA1 contract
Hopefully Tom Tom will have the problem ironed out by then as I have TTN2 aswell.
Pay us a vist on Scoobycity soon. Alots changed and we're alot bigger now
Any bluetooth GPS working with the XDA2 ??
Is there anyone who got the XDA2 working with a bluetooth GPS ? I am very eager to get one (both the XDA2 and a bluetooth GPS) but I would like to hear from some who got a combination working .
Thanks,
Marco
Its being looked into Marco
It may be that the BT Manager may not have various BT options enabled, so it may need a software update/patch from O2.
Spoke to O2 this morning.
They are "aware that not everything works with BT" and are working on a software update.
No timescale offered
I have an Emtac and was going to buy the XDAii to replace my Loox but without this bluetooth connectivity I will save my money. However interestingly it does say on the XDA website...
...or use TomTom Bluetooth with Xda II and cut down the amount of wires in your car
Click to expand...
Click to collapse
I'd say this is enough to get a refund if you want one. Page in question is located here...
http://www.my-xda.com/gps.html
TomTom and Bluetooth
The fault with the TomTom software and Bluetooth lies solely in TomTom's software. TomTom have recognised this and are aggresively working to fix the problem.
The TomTom GPS software doesn't know to read the details of the virtual com port. So give them some time to fix the problem....
Where did this info come from? do you have a link? I had heard that it was to do with the Bluetooth GPS itself not the TomTom software? If you're in the know, could you do a little expaining for a half-wit like me?
Hi
I too have just upgraded to the XDA II from the Ipaq 3970, and I also have an Emtac BTGPS.
Speaking to O2 it appears they used to support the TomTom BTGPS but do not any more.
It would be very interesting to find out if any one has a TomTom BTGPS and can serial link it to the XDA II
Dom
TomTom and Bluetooth
mother said:
Where did this info come from? do you have a link? I had heard that it was to do with the Bluetooth GPS itself not the TomTom software? If you're in the know, could you do a little expaining for a half-wit like me?
Click to expand...
Click to collapse
The fact you're able to bond with the unit shows that bluetooth is working correctly.
The issue is that the tomtom software can't read com6: (which is where bt is hiding) or do anything with it, because of the way the software works.
This is because the Bluetooth manager on Xda II is from MICROSOFT, whereas on other devices it's manufacturer specific. As far as I know this is the first ever deployment of the MS Bluetooth stack directly.
Speaking to O2 it appears they used to support the TomTom BTGPS but do not any more.
Click to expand...
Click to collapse
Then why do they say they support TomTom on their website? Seems like a few people at O2 dont really know what's going on?
I've not known that O2 has ever supported EMTAC BTGPS 'cos the XDA (1) didn't have bluetooth support :?
Surely it is the BT manager that is at fault? Not allowing the a serial connection from the manager to the Emtac?
TomTom is looking to read Com6 (when told to) but the info its getting is not sufficient or mapable.
I've run BTGPS with a TDK B/tooth card and it needs to be told (as do other managers) to make a serial connection to the BT device.
Test for someone (I'll try & do it too)
Find an alternate mapping software that *should* accept a BTGPS device & try to connect...
i had the QTEK 2020 and that worked perfectly, i recently upgraded to an Orange SPV M2000 and i just cannot send any files with bluetooth, on the QTEK 2020 you just press down on what you want to send and select "beam file" and it searches for infrared and bluetooth devices, but my SPV M2000 only picks up infrared and no bluethooth, its wierd because i can recieve anything with bluetooth but jus cant send...
Maybe there is some setting that i must change, i dont know, but can anyone help me or point me in the right direction, any help would be awesome?????
bluetooth problem solved...
well guys i got it sorted out, basically the M2000 comes standard with bt3500 series which for some reason doesnt support "send via bluetooth" ...only in the contacts menu, but it doesnt send files...wierd i know, there is a long way around, if you explore files on a bluetooth device through your bluetooth manager, you can send them that way, but its such a mission...
i downloaded bt3900 series, and now you can press down on any file and it has a "send via bluetooth" option...so problem solved for me, if you have the same problem then i reccomend installing bt3900...you can get it from the link i put below...
http://wiki.xda-developers.com/index.php?pagename=BA_Bluetooth_1.0.0.3900_Upgrade
Since v1.60c my bluetooth second binding/connection is distorted.
In the car, first my TomTom gps binds and connect perfect and then my carkit Parrot 3100 binds and connect perfect. But when i make a phonecall, the line is very distorted. Some buzz is on the line.
And if i change the sequence, by first binding the carkit, and after that trying to bind the TomTom gps. The gps will not bind at all.
The last version that worked correct was the version 1.60c
Somebody with the same experience?
PS. is it possible to extract the Bluetooth files from the v1.60c version and save on the latest versions?
Gps & Parrot Together With Wm2k5 : Bluetooth Incompatibility ??
Same happens to me.
I'm experiencing this problem since I upgraded from WM2003SE.
Every WM2K5 ROM I've tryied does the same.
If once gps and parrot both are binded, you go to bluetooth settings/devices/and you disable hands free service, wait for few seconds and enable it again, then the parrot should work with no trouble.
It's the only that works to me...I have to do it every time I get in my car.
If somebody has the solution I would apreciate.
FRANCESC
Yes, it works for me too. But it isn't a beautiful way to connect!
Somebody know what this could be?
hi
could the both of you with the parrot 3100 please tell me:
.) does it sync the phonebook with pda's contacts?
.) does it show the name of the incoming call?
.) does it show mobile providers net status (=strenght)
if not: have you tried www.jetwaremobile.com ? does it work with that "enhancement"?
thanks!
regards ize|man
I will try!
Thanks for this information, I'll try.
izeman said:
...
if not: have you tried www.jetwaremobile.com ? does it work with that "enhancement"?
thanks!
regards ize|man
Click to expand...
Click to collapse
Not working for me!
I think that I'm suffering with the same problem. I used to use a Nokia CK-1W for hands free and a iBlue BT GPS with Tomtom6 on my Jasjam/Dopod/Hermes and had no problems whatsoever. I've just changed the car and have fitted a Parrot CK3100 (FW 1.6C) and I can no longer connect to hands free and the GPS at the same time.
If I bind to the GPS first everything is fine until I attempt to pair with the Parrot. Upon pairing synchronisation starts and then for some reason the bloody thing starts to make a call!!! The phone doesn't recognise that it's calling, it's just the kit doing it. Once paired and synched the GPS connection is killed.
If I bind to the Parrot first I have no bizarre calling issues but I am unable to locate the GPS device.
What the hell? Have I bought a turkey?
Anyone with a suggestion as to how to fix it?
EelcoV said:
Not working for me!
Click to expand...
Click to collapse
so. none of these three questions is answered with YES? does it work out-of-the-box?
so if i get you right: there is no way to sync my contacts with the 3100?
thanks ize|man
I mean it's not solving my problem
Didn't solve mine either. In fact, it made it worse! I still have all the connection problems but in addition, the battery meter no longer shows on the Parrot. Uninstalling jetware returned the meter.
Hi, guys. I'm having a problem with connecting to my Harman/Kardon GPS-810 portable navigation device. I had trouble prior to hacking my phone with WM6, but now when I attempt to connect, no audio is transmitted. At first, I thought it was just a problem with Nitro's bluetooth stack, but I've since replaced his ROM with Gnat's 6.1, and I'm having the same problem. The GPS-810, by the way, is based on Windows CE, so you wouldn't think there would be a problem. Has anyone else experienced something similar with a GPS device? My phone connects fine with my Motorola headset....
Daryl
Yes, I have the same problem with my Tornado/Gnat WM6.1. I can send files via bluetooth without any problem, but I can't receive anything! Others see my device name, but it fails to send something to my device.
Anyone has any suggestions?
Oh, this is a different problem ... I'm connecting my GPS to MY PHONE. It downloads my phonebook and call history, but when it connects with a call, it refuses to transmit any sound to its speaker. It worked with the old WM5 (it was flaky, though).
Daryl
Has anyone else experienced this problem?
Daryl
just check Receive incoming beams in Settings->Connections
Thanks for the suggestion, but that did not work. I had figured that that was for infra-red connections, anyway. I had tried calling my voicemail, though, and after a brief moment, the audio was transferred to my GPS, but when I called another number, it didn't transfer at all, and this time, there was no audio in the phone, either. Strange.
Daryl
Does ANYONE have a solution to my problem?
Daryl
Hey there, I'm running Treo750 Unofficial WM6.1 OS5.2.19199 build 19199.1.0.0 - Standard OEM Version, which doesn't have Voice command included.
I was wondering where I might be able to find a cab file that installs Voice command 1.6 for WM6.1 on my 750. Would anybody be able to point me in the right direction?
just search the whole forum not the cab. The cab is for all Windows Mobile phones not just one particular for the Treo 750
found it, thanks, works like a charm.
are you able to voice dial with a bluetooth headset using VC and 6.1 ??
jcrompton said:
are you able to voice dial with a bluetooth headset using VC and 6.1 ??
Click to expand...
Click to collapse
If you have the 19209 build, that shouldn't be a problem.
kareem9nba said:
If you have the 19209 build, that shouldn't be a problem.
Click to expand...
Click to collapse
I am using build 19209 of MSVC with WM6.1. When I fresh install MSVC, I can voice dial through my headset, hear the prompts in my headset, etc, just like normal WM6 on my Treo 750. Once I soft reset, it goes back to sounding the prompts through my phone speaker, not accepting voice commands through the headset, etc. It does transfer the calls to the BT headset, but still not functioning properly.
Also, possibly related to this problem, my carrier line's BT icon does not indicate if my BT headset is connected (stays blue, not white). It toggles for on/off (grey to blue), but not connected (white). With MSVC uninstalled or a fresh install before a soft reset, it works just like it had with WM6.
Any ideas folks?
I have tried various reg edits that claim to solve the problem (ie. HKLM\Software\MS\Bluetooth\AudioGateway) and hacks for other phones, but nothing seems to set it right.
peeps said:
I am using build 19209 of MSVC with WM6.1. When I fresh install MSVC, I can voice dial through my headset, hear the prompts in my headset, etc, just like normal WM6 on my Treo 750. Once I soft reset, it goes back to sounding the prompts through my phone speaker, not accepting voice commands through the headset, etc. It does transfer the calls to the BT headset, but still not functioning properly.
Also, possibly related to this problem, my carrier line's BT icon does not indicate if my BT headset is connected (stays blue, not white). It toggles for on/off (grey to blue), but not connected (white). With MSVC uninstalled or a fresh install before a soft reset, it works just like it had with WM6.
Any ideas folks?
I have tried various reg edits that claim to solve the problem (ie. HKLM\Software\MS\Bluetooth\AudioGateway) and hacks for other phones, but nothing seems to set it right.
Click to expand...
Click to collapse
bump....anyone???
peeps said:
I am using build 19209 of MSVC with WM6.1. When I fresh install MSVC, I can voice dial through my headset, hear the prompts in my headset, etc, just like normal WM6 on my Treo 750. Once I soft reset, it goes back to sounding the prompts through my phone speaker, not accepting voice commands through the headset, etc. It does transfer the calls to the BT headset, but still not functioning properly.
Also, possibly related to this problem, my carrier line's BT icon does not indicate if my BT headset is connected (stays blue, not white). It toggles for on/off (grey to blue), but not connected (white). With MSVC uninstalled or a fresh install before a soft reset, it works just like it had with WM6.
Any ideas folks?
I have tried various reg edits that claim to solve the problem (ie. HKLM\Software\MS\Bluetooth\AudioGateway) and hacks for other phones, but nothing seems to set it right.
Click to expand...
Click to collapse
double bump...
Search for 'jabra bt registry' on this forum. I found a registry hack, that says this:
When VC 1.6 gets itself installed, it modifies the following registry key from:
FROM: (Original Registry without VC1.6)
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Au dioGateway:BTAGExtModule = BTAGExt.dll
TO: (with VC1.6 installed)
HKEY_LOCAL_MACHINE\Software\Microsoft\Bluetooth\Au dioGateway:BTAGExtModule
=\Program Files\Voice Command\vcbthag.dll
When I have set this registry back to BTAGExt.dll ( I have used CEregedit to make the replacement) my Jabra BT Headset was able to listen and deliver Voice Commands to the device and viceversa the device was able to deliver messages and notifications to the BT headset.
Simply make the registry change and soft-reset the phone, and you are back in business.