Database Info

still no solution on navman with xda2?

I just bought a navman 440 for xda2 but foud the pairing problem....
read someting from previous threads...
it is been a while.....does any one know how to solve this?
please!
thanks

Have you upgraded to the new rom version? I heard it solves the bt-gps problems....

Navman
The navman pin code is NAVMAN
Doesn't work with Xda II BT, which expects numbers.
Oh well - put pressure on Navman t change their firmware and O2 to change Xda II.

The 4400 is a sealed unit, there's no way of hooking it into a PC to change any firmware.
As to the passkey issue, it's Microsoft not allowing blank keys which is the problem, the 4400 isn't the only device which wants to pair without a numerical passkey...

Navman BT GPS - on XDA II
You'll find that loading the Widcomm BT stack on the XDA II (it can co-exist with the Microsoft one) should fix it from what I've been told.
It certainly fixes the issue on the Leadtek GPS units and I'm told that the Widcomm stack works with non numeric pins.
Search these forums for current location of the link to the Widcomm stack (The Towa fix won't help you BTW).
Cheers
Andy

I'm probably going nuts, but I can't find working links anywhere in the forum to a copy of the widcomm stack.
Can someone help? Please?

Solution wihtout using the WidCom Software
If you still did not find a solution please try the folowing
- Get the file http://www.angeltowns.com/town/bluetooth/EnableCharPin.zip
- Copy the file EnableCharPin.exe to you PDA
- Start the bonding dialog until you get the password screen
- Now launch the explorer and start the executable (you will get a small message)
- Get back to the password screen (if you don't find it click on the BT icon in the today screen)
- Characters are now enabled
Best regards,
Tobias

Can anybody get this link to work, I cant get it even using cut and paste to web browser address window.
http://bluetooth.i-networx.de/

Problems: TomTom2 + Rikaline GPS

Hey all...
read through lots of posts, but can't think of a solution to get the gps working.
I have a Rikaline 7 series BT GPS receiver and TomTom2 (Updated to 2.4 and GPS 2.09). I have bonded the device to the xda ok, but can't get the gps to start. I have selected Tom Tom Wireless and BT on Com 6.
Also switch off beams... any tips???
I did a hard reset before i installed tomtom2, no other bt device attached at the minute.
Thanks
Fais

I got my Rikaline via post via ebay today. The instuctions were all wrong, telling me that it would be on Com8, when it appeared on Com 7 after some resetting of the PDA (it just wasnt seen at first even though it had bonded) ... sorry, but can't be of any more help than this .... make sure you get the alternative bluetooth stack at:
http://bluetooth.i-networx.de/index_e.html

Try removing the gps from your bonded devices, run the tomtom wizard making sure that bluetooth is in "discoveravble" mode, it should then prompt you to choose, click "new" in the gps manager then when it finds the gps click it and finish. Go to bluetooth manager, switch to "on" and then run tomtom. Might help.

Thanks for the replies - really appreciate it. I tried what you both mentioned, and in the end i had no choice but to use Towa's BT tool and set it on serial com 5 for tomtom2 to pick it up. Every so often i have to rebond the device to keep it working which is a pain, but it works at least.
For some peculair reason, if i take the device out of range, without exiting tomtom2, again i have to rebond the device.
Thanks for the help!
Fais

BT GPS COM port not showing in TomTom

Have just installed WM6 (JW 2.02.02 WWE) and everything appears to be fine except for the BT com port in TomTom Nav5. Have paired the BT GPS, set the outgoing port (COM0) but it doesn't appear in the list of ports available in TomTom.
Is this a known issue or have I got to set something else? Have also tried the External GPS manager in 'Settings' but that port doesn't show either.

Sheepdip said:
Have just installed WM6 (JW 2.02.02 WWE) and everything appears to be fine except for the BT com port in TomTom Nav5. Have paired the BT GPS, set the outgoing port (COM0) but it doesn't appear in the list of ports available in TomTom.
Is this a known issue or have I got to set something else? Have also tried the External GPS manager in 'Settings' but that port doesn't show either.
Click to expand...
Click to collapse
I've had the same problem.
What I've done about this, is I've added a Serial port profile for the GPS device. Then went into TomTom and the port was in the list. This port has worked fine.
Tried setting External GPS in the Settings/Connections, to share it, well - TOUGH, does not work.
So I have a working TomTom and I gave up for now about the sharing stuff...

Try setting port 8.

I'm not interested in sharing it (at the moment).
Can you explain what you mean by 'added a serial port profile'?
I've set up an outgoing com port in settings > bluetooth > COM ports but it's not seen by TomTom

tyl said:
Try setting port 8.
Click to expand...
Click to collapse
I must have tried all the ports that were available but none of them show. All I get is the standard TomTom list: -
QCT Data Interface
Serial Cable on COM1
COM7
RIL on COM6
Infrared Port
Ir on COM3
and of course non of those work either.

Sheepdip said:
I must have tried all the ports that were available but none of them show. All I get is the standard TomTom list: -
QCT Data Interface
Serial Cable on COM1
COM7
RIL on COM6
Infrared Port
Ir on COM3
and of course non of those work either.
Click to expand...
Click to collapse
Exactly where you wrote it, in COM ports.
Then I've selected "Other Bluetooth GPS receiver" as receiver type in TomTom 6, and here's what I have:
COM5:
QCT Data Interface
Serial Cable on COM1:
COM7:
RIL on COM6:
Infrared Port
Ir on COM3:
COM4:
COM5 is my attempt to share GPS which is failing so far, so disregard it for here (but I'll try COM8 later). COM4 is the Outgoing Bluetooth port and that's the one I selected.
I must admit that I honestly don't understand why this setup works for me. I expected to put Incoming port number (a common for all devices) there, but obviously didn't have it.

Hmmm, that's strange. What you have is exactly what I used to get in WM5 but it doesn't seem to work in WM6? I'm also on TT5 so that may be an issue?
From what I can see, the 'QTC Data Interface' is the GPS sharing port and is actually COM9, installed by the OS. But it doesn't work!
Frustrating............!
I'm also getting tons of memory leak by the looks of it.

SORTED!
Feel a bit stoopid. Checked the version of TT5 and it showed 5.0. Upgraded to 5.21 (which is what I thought I installed) and bingo! Com port shows and works.
Thanks to all who made suggestions.

Sheepdip said:
Feel a bit stoopid. Checked the version of TT5 and it showed 5.0. Upgraded to 5.21 (which is what I thought I installed) and bingo! Com port shows and works.
Thanks to all who made suggestions.
Click to expand...
Click to collapse
Man, my TomTom is version 6.010.
Just in case, it's available.

put in External GPS the program port on 8.
then you will see com 8 in TomTom.
connect it in TomTom and after that change the program port back to none and hardware port on 8.
problem solved.

I've had this problem on a Mini S, Exec, Vario II.
Some times just removing TomTom and re-installing it seems to work. On several occasions the correct COM port shows up in TomTom. I honestly don't know why. It seems a bit random.

Airax said:
I've had this problem on a Mini S, Exec, Vario II.
Some times just removing TomTom and re-installing it seems to work. On several occasions the correct COM port shows up in TomTom. I honestly don't know why. It seems a bit random.
Click to expand...
Click to collapse
I have seen some recommendation to not select Bluetooth receiver. I don't know, I thought it would be un-cool So I made it work with Bluetooth receiver.

EastExpert said:
Man, my TomTom is version 6.010.
Just in case, it's available.
Click to expand...
Click to collapse
I know, but the old TT5 maps won't work with 6 and I've got quite a few that don't come with the Europe disk.

solution to tt gps connection problems
hi everyone with this problem,
no matter what your setup is vario, xda, dell, tt5 or tt6, tomtom gps or other GPS try this method (it does bloody work) :
STEP 1 : INSTALL TOMTOM5 OR TT6
You do this by copying the CAB files from the CDROM using JasJar or using SD card o any other way
STEP 2 : UPGRADE (THIS IS NOT ESSENTIAL, ONLY DO IT IF YOU HAVE A NON-HOKY COPY OF TT)
http://www.htcclub.net/storage/ppcupd510.rar
or just overwrite patched version of main executable file over original
also having this install on some vario 2 may also help BTHTools1100.
STEP 3 : ACTIVATE THE GPS CONTROL PANEL
this is hidden option but if you use this wisely you will take control over your GPS but in many cases this is reson why tt sometimes works sometimes doesn't.
Fire up a registry editor (eg http://www.freewareppc.com/utilities/phmregistryeditor.shtml )
Go to: HKEY_LOCAL_MASCHINE\ControlPanel\GPS Settings
Delete the DWORD marked "hide"
Add a DWORD called "Group" and give it the value of "2" (dec)
The GPS panel will now show up in your connection settings.
STEP 4 : INSTALL TOMTOM
1. Establish a bond with your GPS and select the checkbox for serial access.
2. In BT, select the OUTGOING port to 8. (optional: make it non secure if available)
3. In the GPS control panel, select the GPS program to 0 and make sure that the hardware one, is set to None, also you should pay attention to 3 tab and allow windows to manage it - for now, you don't really want Bill managing things as it is recipe for disaster.
4. Start TT and the GPS settings, select another bluetooth GPS, and you will see COM 0 free. Select COM 0 and close TT5. (if you don't get the port go back one step and check 3 tab)
5. At the GPS control panel again, now select COM 8 (before we set it up at 0).
6. At BT: select OUTGOING port to 0.
7. Back again to GPS control panel and select NONE.(and now is the right time untick 3 tab option and stop auto managing)
8. Finally start TT and it should connect automatically. Wait for a couple of seconds and click the GPS settings and you should see it has connected.
Congratulations
well, in case something didn't go well start from scratch - reset your software restore your registry and reinstall as much as you can get back to factory defaults using hard reset and etc.
I know this is is in bits available elsewhere but this is more complete and little bit more up to date, but there is still hundreds of people looking for this.
THE SUMMARY
I've spent many many days looking for solutions, registry and web and all sort of tools to solve this, but this method works the treat - and it does make perfect sense - I suspect the reason why this is such a problem is timeout. windows is not a good platform - and it is locked by ms and all sorts of legacy issues. Obvious reason is tt doesn't load quickly enough and and detecting correct port seem to an issue so if you follow instruction you will see that sulotion is guiding your software to speak with 3party hardware having windows in the middle
good luck

Paulius - Excellent instructions and they work just great.
However....For me it only works one time. By that I mean after I turn everything off and then want to use it another time - it again cannot see the GPS device - and I have to do all of the above again.
Do you know why the settings are not retained? Note; I have unticked the the stop auto managing option already.
Hope you can assist.

Paulius - Excellent instructions and they worked fine but only the first time unfortunately for me.
i.e the next time I want to use tomtom - i have to go through all of the above again as it cannot find the GPS again.
Have you come across this before. Note: I have done exactly everything you have instructed above

Tomtom loses GPS settings
Paulius - Excellent instructions and they worked fine but only the first time unfortunately for me.
i.e the next time I want to use tomtom - i have to go through all of the above again as it cannot find the GPS again.
Have you come across this before. Note: I have done exactly everything you have instructed above

I had the same problem.
Luckily I had a backup of my TomTom installation.
It all comes up to the navigator.cfg file inside the Navigator folder. I copied the old one over and did not enter TomTom's GPS Setup menu anymore.
All I did after flashing was to just pair my BT GPS receiver and start TomTom. One needs to wait 5 seconds or so after the main screen opens, until the GPS is found. Do not try to select the receiver in the settings menu!
This happend on both my devices (BA and UNIVERSAL) after installing a WM6 firmware WITH the GPS Manager in the Settings.
Cheers,
vma

Thanks VMA - I understand.
Did you setup an outgoing port though in Bluetooth?

reply to nsm
hi nsm, sorry it took this long to respond, I didn't know the solution to your problem.
However, after few gliches with my pda's I think I can add to the list of thing to go wrong.
First is WM itself sometimes causes problems - so before you do anything else turn it of and on again - it did happen to me in the middle of london and I come from Lithuania well, it can be good fun navigating through canary warf without gps - aim for tall buildings :-D or away from them.
Second is once you followed my original instruction do not go back to gps settings menu, because after this you will have to start again from begining.
Third - is do allow minute or few for gps to lock onto satellites - especially if you are in doors or between buildings. Once in Crete it was quite hard to find satellite signal because of a mountains and I had clear sky view to one direction - but as you drive especially bigger cars, metal body will block signal.
Fullproof recipe is to have two units, if possible for one of them use bluetooth separate gps module as this will allow you to place both gps unit and pda screen in ideal locations for satellite signal and driver.
Fourth - this is boring and can take a lot of time, but may resolve lots of weird issues. Follow my instructions and then you set your tomtom to use data transfer baud rate 4800, 9600 and etc do try all the options - from low to high rate, this means that every time you'll have to start again instructions from beginning. TT6 on some of my pda's prefers 56700, tt5 - 4800 and so on. give this some time explore all the settings.
And finally if you have stability issues check your pda memory limits - try not to push it to 90%+ on unit or memory car, best is to leave plenty on both, this may cause settings not to be saved and all sorts of bugs.
the practical advice is to keep selling and buying pdas till you find one which will do the job for you, Try ebay , but do check descriptions and guides and most important sellers rating! All pda, mda and nokia simbion phones I tried with enough effort will work but many many of them have issues with stability or are difficult to setup.
Hope this helps.
Good luck

Route 66 Navigate 7 on VOX

It works, but same problem as with TomTom, no keys - only fake cursor

What version are you using? After trying a few of the 'trial' versions out on the Net, I finally plunked down the cold hard cash for the retail version. After installing and then installing the update from Route 66's website, it works great with the d-pad and softkeys. I'm on version 7.0.3995 and it's by far the best Smartphone-compatible nav software I've tried. It doesn't support landscape though, and their support people couldn't tell me if a landscape version is in the works or not.
Also, if you're trying to pan the map via the d-pad, that doesn't work on any version of R66 for the Smartphone. The only way to pan is to navigate around current GPS location without setting a destination. Rather limited in my opinion, but R66 support also said they had no plans on changing that functionality.

I have just copied files from CAB to phone and made shortcut, i am using PDA version 7.0.970.1 There are only 2 files: /programm files/route 66/R66Navigate7PPC.exe and /windows/R66WCESetupDLL.dll

R66 7 smartphone
Hi,
i'm running a R66mobile7 build 7.0.2992 and works perfectly.... no need to use a ppc version

just got R66 mobile7 same build 7.0.2992 and yes, it works fine with numpad.
but i can not find configuration for GPS how to connect it with BT GPS wich is on COM7 ?
at programm startup it just shows that GPS not found.

did you add bluetooth serial port after pairing gps device ??

I got ir working. Started TomTom, connected to BT GPS, started R66, and in strange way it connected to BT GPS, closed TomTom and R66 still working. And now it work every time, even without tomtom

very strange way... i only need to launch the program to make it work....

quits
MY Route 66 crashes just after i have selected the map

symbian?
hi
Im a little new to this!
Will the symbian route 66 work on smartphones?

hi,
can anyone post a download for the Route 66 7 like with TomTom Navigator?

hi there it has been a while but i am uploading a easy install for route 66 smartphone you will have to find your own maps as i only have a english one but any way give me 10 mins and i will start a new topic hope this helps

Bluetooth Activesync. Which ROMS have it working?

Long time reader, less time poster so don't NOOBIFY me please. Thanks.
OK. I've flashed several roms, enjoying frying my Wizard into something new for the past year and a half. Nuff said bout that...we are all there if we are on this board.
I actually had it BT-AS working on my MDA with one of the roms, forgot which one unfortunately. I never had problems with the WIDCOMM/BROADCOMM stack on my old AXIM wth WM2003SE with activesync profile but I guess that is the difference with Broadcom and the cruddy Microsoft Stack.
My favorite ROM is the OCTAIVOI 6.0 so far. I tried out the bluetooth activesync and it will NEVER give me an activesync profile, just the serial port profile.
The MDA also seems to only have ports 6 and 7 open for bluetooth purposes.
Now I have tried registry hacks from other postings and other fixes that seem to work only with previous activesync 4.2. I USE 4.5. I know Microsoft jacked with it for some dubious security reason (which is irrelevant to home users...only enterprise users)
Anyway. Has someone got this thing to work? I love my ROM but am willing to ditch it for something that has a properly functioning connection thru AS and BT.
Thanks.
(some seem to have tried to port the Bluetooth stack from x50-51 from Dell over to wizard..has that worked out?)
too many questions...again..don't kill the "noob" poster.
Thanks

gfourner_austintxmda said:
Long time reader, less time poster so don't NOOBIFY me please. Thanks.
OK. I've flashed several roms, enjoying frying my Wizard into something new for the past year and a half. Nuff said bout that...we are all there if we are on this board.
I actually had it BT-AS working on my MDA with one of the roms, forgot which one unfortunately. I never had problems with the WIDCOMM/BROADCOMM stack on my old AXIM wth WM2003SE with activesync profile but I guess that is the difference with Broadcom and the cruddy Microsoft Stack.
My favorite ROM is the OCTAIVOI 6.0 so far. I tried out the bluetooth activesync and it will NEVER give me an activesync profile, just the serial port profile.
The MDA also seems to only have ports 6 and 7 open for bluetooth purposes.
Now I have tried registry hacks from other postings and other fixes that seem to work only with previous activesync 4.2. I USE 4.5. I know Microsoft jacked with it for some dubious security reason (which is irrelevant to home users...only enterprise users)
Anyway. Has someone got this thing to work? I love my ROM but am willing to ditch it for something that has a properly functioning connection thru AS and BT.
Thanks.
(some seem to have tried to port the Bluetooth stack from x50-51 from Dell over to wizard..has that worked out?)
too many questions...again..don't kill the "noob" poster.
Thanks
Click to expand...
Click to collapse
Did you flash your carrier rom before flashing 6.0
In 5.9 it did not work for me, but in 6.0, bluetooth active sync works for me.

Great advice on flashing carrier ROM first.
This is something I usually do and when jumping from one OCTAIVOI to another, I skipped the step.
Giving it a go and will report back.
Thanks for your patience and kind answer.
I hope this works..as trying to uninstall activesync 4.5 and putting 4.2 was fruitless. WM6 says I have to use 4.5 when I guess I remember my old WM5 roms allowing 4.2.
Lets get flashing.

Reflashing with 2.26 ROM then WM6 doesn't solve BT-AS Prob
I tried the advice given above, normally excellent catchall to fix a lot of problems. This time, it unfortunately is stuck on the *&*& serial port option with no option for Activesync again.
To see how it used to work in original T-Mobile 2.26 WWE, I reflashed it and it worked beautifully. Ok, so I wasn't nuts for remembering that it worked in WM 5.0. However, putting Octaivoi 6.0 on it or several other ROMS in the last few months does not allow proper BT connectivity in using Activesync.
TNT, Blackdiamond, NBD (Where are U Zoki?) are some of the ROMS I remember having problems with also. It could be that you got it to work? Chime in.
I am going to go back to an INgeNetics type rom from original Wizard wm6.0 ports and see if they work.
I love the features on .1908, .1921, 1933,.1938 type roms but this is ridiculous to not work. Maybe I'll try that .1948 on I just saw on the boards.
ANYBODY have more input on this. SOMEBODY else tell me that they are having this problem...EVEN BETTER...FOUND A SOLUTION.
sorry for shouting...about to toss my MDA in the toilet over this.
(blasphemy)

Note also, i followed some adive that was given to me in 5.9 that didn't work. But did in 6.0
Remove all paring before flashing to 6.0
Remove all bluetooth settings also in rom.
Flash
Re-pair
Mine worked on my Wizard.
Hope that may provide some incite.

Am I the only one who is having Bluetooth-Activesync Problems?
Rocoafz-thanks for all your input. You seem to be the only one who is not apathetic to this issue. I've seen your other posts on other threads and I know you went through a lot of what I am going through now. Thanks for understanding.
ROCOAFZ said:
Note also, i followed some adive that was given to me in 5.9 that didn't work. But did in 6.0
Remove all paring before flashing to 6.0
Remove all bluetooth settings also in rom.
Flash
Re-pair
Mine worked on my Wizard.
Hope that may provide some incite.
Click to expand...
Click to collapse
Tried this and unfortunately all I still get is the serial port option and no opportunity to do both incoming and outgoing com ports like you can in basic windows mobile 5.0 "T-Mobile 2.26" rom or in Button 1.05 rom.
Hell I started fresh. Uninstalled my Dell Bluetooth (widcomm stack) from laptop, uninstalled Activesync 4.5...so no more pairings at all.
Fresh flashed the carrier rom.
Installed fresh WM6 ROM.
Result.
Same nonsense. Different day....oh well.
In WM5 I have no problem connecting but nothing seems to be working.
I am wondering if a bluetooth stack can be corrupted from all the flashing or is each flash a true clean wipe that gives you a fresh start. Is there something residual from another ROM or registry hack that is screwing with this? Just curious.
APPRECIATION To any forum member with solutions or attempted solutions.
It just sucks to not have this function as my laptop seems to OVERHEAT when I am USB connected for Activesync.
G

gfourner_austintxmda said:
.
Hell I started fresh. Uninstalled my Dell Bluetooth (widcomm stack) from laptop, uninstalled Activesync 4.5...so no more pairings at all.
G
Click to expand...
Click to collapse
Of course, I reinstalled them before reflashing. LOL.

Check these threads...
http://help.lockergnome.com/general/Activesync-Port-Availability-Bluetooth-ftopict26563.html
Some of these worked for people

Possible Answers and a Question
To answer your question: XDA Mobile v5 (of mfazzz) does have a working ActiveSync via BT - I used it. However, it has another problem: files don't sync no matter how you connect (wi-fi or cable).
NTS's ROMs also sync via BT.
Octaivoi is a nice ROM though - I'm using it myself now and am quite happy with it. It would be nice to crack this bug...
If you do have the ability to add ports in the BT menu, it should be doable - that's how I did it with other ROMs.
I'm not sure I understand your post completely though: do you or do you not have an option under BT to add ports? I'm asking since I don't - that's what is preventing me from getting ActiveSync run via BT.
I'll still stick with Octaivoi though (at least, for now) - I like this ROM. And, perhaps we (or somebody else) will figure out how to do it.
gfourner_austintxmda said:
I actually had it BT-AS working on my MDA with one of the roms, forgot which one unfortunately. I never had problems with the WIDCOMM/BROADCOMM stack on my old AXIM wth WM2003SE with activesync profile but I guess that is the difference with Broadcom and the cruddy Microsoft Stack.
My favorite ROM is the OCTAIVOI 6.0 so far. I tried out the bluetooth activesync and it will NEVER give me an activesync profile, just the serial port profile.
The MDA also seems to only have ports 6 and 7 open for bluetooth purposes.
Now I have tried registry hacks from other postings and other fixes that seem to work only with previous activesync 4.2. I USE 4.5. I know Microsoft jacked with it for some dubious security reason (which is irrelevant to home users...only enterprise users)
Anyway. Has someone got this thing to work? I love my ROM but am willing to ditch it for something that has a properly functioning connection thru AS and BT.
Thanks.
(some seem to have tried to port the Bluetooth stack from x50-51 from Dell over to wizard..has that worked out?)
too many questions...again..don't kill the "noob" poster.
Thanks
Click to expand...
Click to collapse

BT active Sync
For i have tried allmost every WM6 rom available on this board
but only TNT rom's have working Active sync via Bluetooth

You could try this procedure too (at least I will have a feedback if it's working for somebody else too )
http://forum.xda-developers.com/showthread.php?t=363144

Thanks for the new round of input on BT-AS issues.
Each bit of new information provides us with a solution eventually.
I have been deleting COM ports on my laptop that were blocking my use of COM3 and COM5 etc.
Figured out how to kill them finally and recreate bare COM ports for use by whatever USB or BT device I wanted.
Only snag now is I must have killed my entire internal BT adapter for my Dell laptop...thats another story.
I'll try to put in my Kensington BT USB dongle and try from scratch.
I think I am getting somewhere.
Should be able to add ports again from the Wizard side, usually 6 and 7.
Found another program, not shareware called VSPB..virtual serial Port builder. It may or may not help with this Serial Port problem.
Greg