Related
Hi there,
I was using Mapopolis GPS software ver 3.20 on my SX-56 and it was working fine with the GPS reciever being picked up on COM 1. Suddenly one fine day, the Mapopolis software would not work at all and the phone for some reason would not detect the reciever on COM 1. I re-booted, re-installed and eventually blew my ROM and thus the phone entirely trying to work the GPS but to no avail. I kept trying since when I connect the GPS reciever even now directly to my laptop, it still works fine so I assume there is nothing wrong with the GPS unit itself!
I have just bought a new T-Mobile WM 2003 unit and after installing mapopolis on it, it still is not working on the GPS and giving me the exact same problem. I have put it on "autodetect" and it goes in a loop on the COM Ports and starts from COM3, then COM8 and then COM9 then back all over again...it does not even start from COM1...when I remove "autodetect" and set it on COM 1, it keeps saying detecting and nothing happens, I've left it like that for more than an hour!
I'm just wondering why it was working before and not anymore? Any suggestion or ideas are more than welcome! Are any program trying to block the COM1? If so, how do I get rid of them or free the COM1? I'm stuck...
Thanks.
Try to deactivate the beam of IR port.
Or take a look if the Activesync doesn't use the com port.
It you're using a IR external Keyboard deactivate it...
Bye, M.
Re: COM Problem
Sir,
You are a king!!! Just saved me from blowing up yet another fantantic PDA!!! I don't know how to thank you, it was the IR port occupying the COM and it is working great now after I disabled it!!! Just a small question for you, is it possible to fix my old PDA which I totally messed up because of re-setting etc etc.? I have the problem posted on:
http://forum.xda-developers.com/viewtopic.php?t=11858
Thanks in advance.
Munz.
tv tuner
Is it possible to use mda2 as a monitor to watch tv out of home, connecting it to an usb-tv tuner?
Re:
I doubt it since the USB-TV Tuner would require a USB port for a connect through and I do not know of PDA which have that, but then I may be wrong....
I'm struggling to get my GPS software and bluetooth receiver to work together in Faria's REAL THING ROM. I've paired the devices, used the wm5gpsfix.exe and all the settings under the sun but I still can't get my software to see the gps receiver.
The software is Destinator Lite (for the moment, until I can make sure everything's working fine and then I'll buy a better one) and the bluetooth GPS is a Navman something-or-other.
Is there any difference between wm5 and wm6 that would make the fix for wm5 not work any more? Has anybody else had any problems using GPS receivers and software in wm6?
No problems here. Have you set an outgoing port?
I've paired the phone to the receiver, and set the outgoing port to 5. Then, using the GPS settings in wm6, I have set the hardware port co COM5 and the program port to COM4. Destinator Lite will only let me select 0, 1, 2, 3, 4 and 9 for my COM ports, but I can't select any of those for the outgoing port which is why I'm using the GPS settings bit.
Does anyone know if the button on the receiver is supposed to do anything other than double-flash all the time and then turn off?
myk_83 said:
I've paired the phone to the receiver, and set the outgoing port to 5. Then, using the GPS settings in wm6, I have set the hardware port co COM5 and the program port to COM4. Destinator Lite will only let me select 0, 1, 2, 3, 4 and 9 for my COM ports, but I can't select any of those for the outgoing port which is why I'm using the GPS settings bit.
Does anyone know if the button on the receiver is supposed to do anything other than double-flash all the time and then turn off?
Click to expand...
Click to collapse
I don't think all programs work with the GPS manager thing, I think they have to be written to that specific API. I have TomTom 6 and although this lets me select the GPS program port I have configured (COM7) it doesn't see the GPS. If I reconfigure it to work with the GPS hardware port (COM6) it works fine. I also have Pocket Streets 2006 installed and this works with either. Strangely If I start Pocket Streets first and minimise it then load TomTom it works with the GPS software port. I assume Pocket Streets kick starts something that activates COM7, whereas TomTom doesn't do this automatically.
HTH
Andy
Thanks for your help! Unfortunately, I can't set my outgoing port in bluetooth settings to any of the numbers that my program will accept. Is there any way of freeing up any of the others? At the moment, it just says "COM port could not be created. Check your settings and try again."
GPS manager sucks
I never got the gps manager working. I go direct to the GPS port and it works fine. Never applied any fixes either ... ?
I had to change my port from Com7 under WM5 to Com6 in WM6 in order for my software to "see" the bluetooth receiver. I'm using OnCourse Navigator6 with WM6 and was using their Navigator5 software with WM5. Not sure if there's a difference with the actual ROM or the software, but COM6 is the only one that works for me at this point.
However, under WM5, if I tried to pair map4pda with the bluetooth receiver, it never would detect it. But, with WM6, it found it using the COM6 port that I use with OnCourse. Strange. . . but, as long as it's working now, that's all I care about.
Working... somehow
Ok, I now have my receiver picking up through bluetooth and my program can find it. Not quite sure how it works, cos to me it looks like it shouldn't. But anyway, here goes.
First, I searched through the registry on my wizard for all references to COM3, which was one of the ports my GPS program could see but that I couldn't set as the outgoing port for my receiver. I changed all the (2) values to COM5, as COM3 is for IR which I never use.
Then I paired my receiver, and tried to set the outgoing port as 3, which still didn't work, so I went for 5, which did. Then used the GPS manager thing to set the hardware port as 5 and the program port as 3. (I don't think the GPS manager is working with my program though)
Then in my sat nav software COM5 was available, and now COM3 has disappeared (before there were 0,1,2,3,4,9 available) so now I can choose 0,1,2,4,5,9. So I selected 5, and it found it!
So now it works, but I'm not sure if this is an ideal way of doing it (messing with the registry ) and I don't know if I'd be able to use my IR port for anything now. I was thinking of playing with some of the "universal remote" programs that are knocking about, so I guess we'll see. But for now, at least my GPS is working!
Now I just need some better software...
I noticed that some programs see gps wehen it is paired and others when not paired.
I use TT6 with my Holux GPSlim 236 (both WM5 and WM6) and I set the outgoing port (in bluetooth setting not GPS setting) to COM6. Then TT6 sees the COM6 in the "Other bluetooth GSP" setup so I could select the port.
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
Yesterday I did a hard reset of my device with Midget_1990 v1.0 and spent the evening reinstalling my apps and setting it up to my liking. I have previously used this version of WM6 with no problems and it works great.
Today I have tried to pair my universal to a GPS reciever to run TomTom. Initially it paired up and I set the outgoing port to port 4 and set this on TomTom but it wouldn't find the device. I then tried to delete the pairing in bluetooth settings and repair. However after doing this I can get as far as inputting the passkey key but the screen asking me to select serial port is no longer there. Also when I go to the Comms port tap it is also blank with no New Outgoing Port to select.
I am reluctant to go through the reinstall process again so I would be very greatful if anyone knows how I can restore things back to normal.
Thanks in advance
Dan
Hi,
I'm trying to go the geotagging way on twitter. I found an old bluetooth GPS thing from TomTom and I hooked it up to my phone. I created a COM port for it (first COM0, but then I found out some programms don't scan that one, so I went with COM1). When I launch Goolge Maps and I enter COM1 and baud rate 4800 manually, it all works like a charm. But when I let Windows manage it, it doesn't work. Why let Windows do the trick then? My twitter app, PockeTwit doesn't let me configure port and baud rate...
I read about the non-configuratable (for smartphone) hardware/software port that's been added since WM5, but since I got a smartphone, I can't set my hardware port.
Does anyone here know the default hardware port that windows uses, so I can set my receiver to that port?
Or is there any way to configure that manually through the register or some tool?
x5x_tim
(Sorry for the repo, but I thought this thread would fit in better here)