PDA

View Full Version : Universal + BlueTooth GPS problem, help


Shef
4th October 2006, 12:38 PM
Dear Htc fellows,

My bluetooth GPS is working strange on my Universal, but on iPaq with
WM2003 works as a charm. The BT GPS is new Solar GPS with new Mediatek
chipset.
It's not working with iGo 2006 and even not Tomtom 5 or Tomtom 6.
I can find the BT GPS in BT manager, I can pair it, but I dont know why,
it needs a pass key even if it shouldn't. Then when I explore it's
services, The popup come again asking me if I will allow external BT
device to connect to my Universal and it come asking passkey again (Why?).
I can't even enter an empty passkey (bt device doesen't require it). After that I have successfully paired the device. I can add it's serial port to enumerate on com ports 8 or 4.
When I start Tomtom, it doesent detect the device at all. If I use iGo, it detects, gets datas and disappear, it's allways appeared for 1 second and then 5 seconds not. No matter Which bitrate I set (device is written to be 9600) it needs to be in NMEA protocol, not SIRF.

When I use some freeware GPS programs, it seams to be working ok, it shows satelites and it's not disappearing.


What can I do with that???
I have some idea that it's probably about WM5 and it's security....
How can I setup com security in registry? can I set the port speads manually atd... I had performed a hard reset and it still don't work. Can ROM update or AKU update help me?

Does anyone have some idea what should I try now?

O2 XDA EXEC:
Rom: 1.30.107
Radio:1.09.00
P:42.42.P8

BT GPS: model: BT 2.5MR
made by f-tech.com.tw

Thanks;

Shef

ska
11th January 2007, 10:03 PM
Hi,

I have the same problem exactly and could not find anything on the net. Did you solve your problem?:confused:

dhob187
11th January 2007, 10:12 PM
i know that there is a problem with GPS and WM5 and so there is this patch which i install every time i hard reset .....

the guys i bought MY GPS from gave me this ... and they are pretty knowledgable .....

it works well ....

try it !

ska
11th January 2007, 10:30 PM
My OS version is WM2003 but tried anyway.. Did not work.. :( can there be version for WM2003??

dhob187
12th January 2007, 07:41 AM
did you define an outgoing com port for the device (com 4 for example ?)

ska
12th January 2007, 01:12 PM
well, igo finds the device an COM 6 actually, it connects too.. but stays connected just for a second, then again and again..
I installed GPSGate and created a virtual com port 7. I manually configured the GPS receiver connection to COM 7 on igo.. But all the same.. ::(
do you advice another way?
one other thing the device works with navigon 5.0 and tomtom 6.0 smoothly, no problem.. only igo..

dhob187
12th January 2007, 05:07 PM
IGO is CRAP ... that is well known .... lots of bugs ...

i am sorry .. i do not know how to solve your problem...

but i suggest using destinator 6 ..... (that's what i use) ....

simple ... nice looking .... big buttons and able to navigate to your contacts directly (especially useful if you have Phone Edition)

oh ... and ... works great !

adad
22nd January 2007, 03:21 PM
I got the Holux GPSlim 236 GPS. I can pair the GPS with Universial. But I cannot set the com port at all. A pop up window always say the com port (I tried everyone of the ports) is not available.

Any one got a solution, does the GPS bug fix help ? and what does it fix ?

EastExpert
22nd January 2007, 07:12 PM
Might seem a bit obvious, but have you tried the code "0000" when pairing your device?

tripledes
22nd January 2007, 07:31 PM
Once paired...did you define an outgoing serial port on "Bluetooth Settings" menu on your WinCE?

I have a royaltek bluetooth GPS and it's been working well with TomTom[5|6]...I use '0000' as passkey (default on many 'non-interactive' devices), once paired I clicked on 'COM Ports' tab and defined a new outgoing port, the wizard should list the GPS as an available device to create a COM port so I used it and I got a 'com0'.

Once the outgoing port was created I had to tell TomTom to use the new 'com0' and worked like a charm :)

It's been working since TomTom 5.21 (previous versions didn't work).