Hi everybody,
I do really need an extra help with my XDA and Mapopolis GPS kit. I connected everything right, the GPS antenna (Holux 210) works fine bilinking since the sats are linked, but my Mapopolis software regularly mounted on my XDA doesn't want to work. It still keep itself "frozen" searching for on COM1 port and it did not reply to any command on touch screen.
What's wrong???? Anyone can help me? Please...
Thanks so much for your help....
Lele
ITALY
[email protected]
Not sure if this will fix your problem, but I had a similar situation with mapopolis a while ago.
I'll assume you already have your GPS set up to do NMEA at 4800 baud. Also, this process is described for PPC2002, I haven't been able to try out PPC2003 yet.
Go to the PPC settings window (Start Menu->Settings), and choose the "Connections" tab. Tap "Beam" and ensure that the box for "Recieve all incoming beams" is NOT checked. Click ok.
When this box is checked, it creates some kind of conflict over COM1 which prevents Mapopolis from connecting to the GPS. When I turned this option off, everything started working.
Good luck!
Because of all the expected mssing around with my original T-Mobile 1.60.00 ROM combined with a Bluetooth GPS, I decided to upgrade. It all works now, just let me share my findings with you:
I wanted the 1.72WWE and 1.14 Radio ROM, no Beta, but also wanted to keep my Dutch T-Mobile custumisations.
I took the recently released QTek 1.72 ROM
Unpacked it
Threw the extende rom file away
Changed the 'country code' from qtek to tmobile (see link on xda-developers mainpage)
Backed up my device using Activesync backup
Started the upgrade
UhOh: 'USB 1.03' on screen and nothing happening
Restarted upgrade
Went smooth all along
Hard reset: YES!! 1.72.00WWE / 1.14.00 radio with all my beloved Dutch T-Mobile customisations (ext rom 1.60.38)
Performed restore. THIS probably wasnt the smartest idea, because right after that my device was quite unstable. '
So: Did a 'permanent save' backup
and a Hard reset again.
Rock steady since then!
To get Bluetooth & BT GPS working frightened me a bit: getting that to work should be proof of the pudding to justify my upgrade.
Fiddled around 2 hours (com ports, gps viewer software that accompanied the GPS and what have you got . . .), until I tried the simple stupid method:
Switch on Bluetooth
Bond the BPS
Start TomTom GPS
Select NMEA 0183v2 9600 and Bluetooth GPS
I am very happy!!
For those that are still lokking for a decent cheap BT GPS: Search on ebay for DCONNEX. They sell for around 80 euros + 28 euros shipping. The DCONNEX DC-230 is in fact a rebadged Holux GR-230. Works like a charm, and for the price of a wire solution!
Works!!!!!
even imat v1.72 works great with BT GPS with no added BT tools
gazzaman2k said:
even imat v1.72 works great with BT GPS with no added BT tools
Click to expand...
Click to collapse
Is the same ROM.
Eelco is right
As long as you look just at the os & radio roms both QTek 1.72 and IMate 1.72 are the same.
Difference is withing the extended rom.
because I liked to keep the Duthc T-Mobile customisations (well not all, but most of them) I re-used my old extended rom.
Hello,
Help with 1.72 ROM set up.
I'm very excited about how you have set up your device, but I'm not fully certain how to do the same.
I have looked for the ROM unpacker, but the only thing I see on this site is the ER-Edit.
I currently have the T-Mobile UK Beta 1.72 on my device, and I'm not real happy with it.
If you can and if it is not too much trouble, could you please provide me a little more specific directions on how you accomplished your set up. I'm in the USA, and I upgraded from 1.60.36, which I was not very happy with either. I liked 1.60 better.
My major concerns lie with the country id error, and using parts of different extended roms and radio stacks, but I'm willing to try.
Thank You, Ed
Well since you now have 1.72 on the device its really quite simple.
(You might as well consider upgrading to the non-beta 1.72 from imate or Qtek, i used Qtek)
Foor the external rom customisations:
Unpack an update (like the 1.60 you mentioned) using winrar
Using the directions on thsi site determine your current çountry id FOR THE EXTENDED ROM
using the directions on this site (xda2nbf) change the country id for the extende rom file (ms_.nbf)
remove the other .nbf (nb and radio) files
Upgrade your device
Cold reset
Yopur device should now be a bit in the right direction
Install the extende rom-unlocker found in this forum
unhide & unlock the extended rom
Now you can add/remove programs from the extended rom.
adding goes like:
1. place .cab file of program to be installed in extended rom
2. add CAB line in config.txt just before the current last line
removing goes like:
1. remove cab file of program you dont like
2. remove accompanying line in config.txt
Dont forget to lock you extended rom afterwards so the contents is kept during any reset.
hope this helps.
also : search the forum on the topics extended rom unlock
edsub,
Thank you very much. Your response is very helpful, and sends me in the right direction. The winrar was the missing peice that I did not have.
I'm familiar with the extended rom part, but I have not played around with the .nbf, nor the rom locking.
The UK beta 1.72 I have does not seem real stable to me. I'm thinking of going with the iMate or Qtek 1.72, as you suggest.
Thanks again I'll see what I can manage.
Ed
hey all, im on o2 in uk, my current settings are :-
Rom version :- 1.60.00WWE
Rom date :- 12/03/03
Radio version :- 1.10.00
Protocol version :- 1337.18
ExtRom version :- 1.60.50
i knw this mite sound abit basic...but what difference would it make in me updating to this 1.72 rom ?
is there any point ?
edsub said:
i used Qtek
Click to expand...
Click to collapse
Maybe off topic but where did you get the QTEK ROM from?
Can you share the URL.
Thanks,
Mark
Hi all,
I've recently bought a DC-230 GPS BT, but I cannot use with TomTom3
I have:
ROM VER 1.72.00WWE
Radio 1.14.00
Ext 1.72.104 (with some cabs added by me)
And a XDA 2 (rom is a Qtek 2020)
I've tried:
Hard reset - no BT Tools - Bond GPS - Success with GPS Viewer (that is in boundle with DC) on COM5 9600
Started tomtomGPS, no success (with or without START GPS with GPS Viewer).
I've tried
- NMEA 0183v2 9600 on COM5 and on Bluetooth
- NMEA 0183v2 Bluetooth on COM5 and on Bluetooth
- SiRF 9600 on COM5 and on Bluetooth
- SiRF Bluetooth on COM5 and on Bluetooth
I've removed bond with GPS.
So i've installed BT Tools 1.1. Bondend and added profile on COM7
GPS View didn't see the GPS
TomTom the same (i've tried the same drivers)
Any suggestion?
Thanks
Fabio
try changing to nmea 4800 on the same port that the gps view is showing, make sure gps view is closed when starting tomtom. Alsi instead of choosing from the upper drop down box in tomtom, look in the lower drop down, you may find your gps is announced/listed there.
cruisin-thru said:
try changing to nmea 4800 on the same port that the gps view is showing, make sure gps view is closed when starting tomtom. Alsi instead of choosing from the upper drop down box in tomtom, look in the lower drop down, you may find your gps is announced/listed there.
Click to expand...
Click to collapse
no success
I don't know why doesn't work
GPS View found my GPS... TomTom GPS no
Is the right version of TomTom GPS? (down right i see V2.09 305/393)
In the lower drop down box I see only com/irda/bt ports...
Thanks
You should have totmtomgps V3.02. It is available on their site.
Downloaded TomTom GPS 3.02...no success
But is correct that GPS Viewer when i push on Start GPS show
Date: 2002/11/10
Time 01:01:xx
Long:
E: 0'0'0.0''
Lat
N: 0'0'0.0''
Dop: 50.0
Aciring: no fix
Direction NE 0
Alt 0m
Speed 0km/h
PDop50.0
And i get a red point on the N on the map...
news...
With BT Tools installed i've tried GPSDash and MapSonic...
They connect to com7, but I get Satellites in use: 0 of 1 sats
Quality of Fix: no fix / n.a.
What's meaning?
Thanks again
I cannot use any sats..whats wrong ? is the gps broken ?
Aehm....uhm...
Er...is possible that it is low of battery? I put on charge and now I see 7 sats..
Bluetooth authomatic activation problem
I am sorry to jump in this discussion, but I had a BT problem, I couldn't connect to a GPS (Leadtek), and I did almost the same thing you are talking: I upgraded my QTEK2020 to 1.72.00WWE/1.14.00/1.72.602.
After the upgrade I installed the Pocket Bluetooth Tools and after some bondings/"unbonding", the COM7 profile appeared and everything worked fine from that moment on.
Now, there are 2 things I want to share:
- first, in order to have a diferent Bluetooth serial connection to the same or another port, I had to kill the the bond I created with the Leadtek GPS, then bonded again without activating the serial profile and then killed that bond again. Only after this series of actions, with a soft reset between all of them, I was able to bond with a diferent GPS bluetooth (I think it was from Globalsat), using the Com7 serial profile.
- second: my Qtek activates randomly the bluetooth by itself...
Does anyone know how to solve the authomatic random activation of the GT?
Try to activate in start/settings/system/bluetooth settings the extended port com 5. This helps with leadtek and emtac bluetooth antenna's for tomtom, and alturion.
Cheers
Why are you using Pocket Bluetools with rom 1.72??
NO NEED TO!!
Just use native MS BT Stack.
Bond the BT GPS, say yes when asked to assign COM port.
Let GPS software use COM5
Settings for TomTom3: NMEA Bluetooth GPS / COM5
Works flawlessly
I'm just recently using tom tom for first time and TOM TOM tells me everytime that COM1 doesn't exist.
I'm able to downgrade back to plain old 2003 to try it , however I'd rather have a fix or work around before I do so....
any thoughts or experiences?
Hi,
This will happen if the GPS cable is not connected correctly. Disconnect the cable and reconnect then start TomTom. I get this now and then. Everytime i reconnect it works just fine. Also check within TomTom if it is configured to use COM1 via serial and not Bluetooth.
Cheers
Jay
Right, just been down to the car, everythings plugged in correctly, tried multiple soft resets but keep getting the message "cannot open COM1: Port Does not Exist"
I tried using the serial on USB option instead (just clutching at straws) and get no error messages, just GPS Position unreliable. As far as I can see TOM TOM knows something is being plugged in as the flashing disconnct icon dissapears when i plug in the GPS reciever.
Any further ideas? I want to try it having downgraded back to 2003 but I don't have any backup software apart from xBackup and I'm reall yfond of SE.
Solution to Com 1 problem
Hi,
Go to connections, and disable the IR search for other devices, and IR in total, then the COM 1 is released.
Took me quite some time to figure that out my selv when having the problem.
Cheers.
Esor
Missing COM1 Port
This happened to me too and I discovered that it was being caused by the IR Beam being on receive by default. This inhibits the use of COM1. Solution - Navigate through the System functions to find the IR Beam option. Disable that and this may solve your problem.
Cheers Hissing Syd, I was just about to try flashing my rom but this fixed the com1 issue, next to try it in the car..
Could anyone help please? I have searched and searched to no avail..
I have the xda 2 and have had all sorts of problems running some software but the phone part appeared to be ok !?
I can now run all the things I want and they work,usually, ok. However the phone is now getting so bad it is beyond belief.
If I do receive calls I cannot answer them - well this is what I thought for the first few weeks. It now appears that I have to just keep saying "hello, hello, hello" until I can hear the calling party. I used to hang up because nobody appeared to be there.
I thought an radio rom upgrade to 1.19 may be the answer and tried (4times) to do that: I click on the HimaUpgrateUtHTC and away it goes...but it disconnects the Activesync connection, does not reconnect and then comes up with the error connection code 101.
1. Will the upgrade cure my phone probelm - if not , any other suggestions, please
2. How do I upgrade only the Radio when the Activesync connection is shut down by the process?
Thanks for all guidance.. Great site by the way.
usall5 - ripping out the the hair I have left..
xda2 on T-mobile via Virgin
ROM: 2.06.00WWE
ROM Date: 06/14/04
Radioversion 1.14.00
Protocol: 1337.24
ExtROM: 2.06.100a
No replies, so I moved on myself -
Info' for all out there, as it may help someone, below.
I found that if I did a complete redo that the Activesync did not go off. But phone problem persisted. Search all over again and found an incling that BTHTools1100 may be the culprit/adding to..
I have uninstalled BTHTools and soft reset and the phone works much better now... Apparently the Bluetooth had to come on before the call could be answered....
I had this on before and did not notice any probs though, so ??
I now have to switch on bluetooth manually before using sat nav whereas before BTHTools did that automatically.
Anyone any ideas on how to set up so phone and sat nav work correctly? That is doesn;t come on for ohone but does for sat nav.
Ta
usall5
Hi guys
could any one please be so kind as to help me with a problem im having.
i have a spv m5000 on orange which i have change the mother board over with a o2 exec mother board running windows mobile 6.1 seems to be working fine no issues however i have tried to pair both my gps units with it but to no avail, i have a Holox BT-541 and a navicore BT-GPS-32354D i have tried both of them and have same problem,
my xda see's them and adds them fine but when i try to connect to one in the xda it says unable to connect or wrong passkey i have used 0000 for holox which thats what it says in the holox pdf but have also tried 1234 but i think this is a com port problem i have tried all com ports some will go in ok but still cant connect to gps i also tried this "go into TomTom and use the NMEA devices with baud rate of 38400" this did not work, before i changed mother board i had these working fine on older tomtom and original spv m5000 mother board so i dont know if this is a win mobile 6.1 problem or not i see quite a few people with same problem but no solution that worked for me any way.
i have seen thred taking about pairing before tomtom installation but not sure that will fix my issue as i think i tried to pair before i installed any way.
has any one any ideas on this any help would be really appreciated this is getting to be a pain in the rear!.
also there is an icon in the system tab "external gps" can any one tell me the correct settings in there ie for program tab and hardware tab what com port and baud rate should be and whether the manage gps auto should be ticked
many Thanks in avance for any help you can give here.
Kind regards
Daz
Ok found solution,
after spending way too much time on this crap! I finally found the issue as I stated I thought
it was a mobile 6.1 issue and I was right, in mobile 6.1 they have added a external GPS shortcut
in system tab it is here the problem exists.
my problem was resolved by the following procedure.
On your XDA go to Start/Settings/Connections click on Bluetooth short then add new device once it has found it
enter passkey 0000 or whatever yours is once it has made the first connection then do the following,
1. Under "device tab" click on your unit and make sure the serial port is "UNCHECKED" disabled then click save.
2. Under "Mode tab" make sure (Turn on blue tooth) and (Make this device visible to other devices) are "CHECKED" enable them.
3. Under "COM ports" select a port, I chose 0 don't think it matters but if so chose another but remember what one you choose.
4. Under "Security tab" Authentication (passkey) required "CHECK" enable it click ok to come out of Bluetooth.
5. Under "System tab" click on "External GPS short cut.
6 Under "Programs tab" select (None) for GPS program port.
7. Under "Hardware tab" select port 0 or same as you gave your Bluetooth com port and issue the "Baud rate" 115200 or lower rate.
8. Under "Access tab" Manage GPS automatically (recommended) "CHECK" enable
9. Finally check your xda is blinking a blue light and turn on your tom-tom software it should now pick it up, all done.
Final note it seems that Microsoft have made one more buggy operating system, no change there then LOL
and as a result you can't seem to use the blue tooth pairing process as intended so this is a working work around
one more thing there is a 2nd bug found and that is when you turn off your GPS unit and try to use your xda you might
find that your last page froze up here you will have to mess around with it i.e. try turning off your tom-tom software first
and then your GPS, Thanks to bill gates for yet another windows operating system that doesn't work as advertised.
Well we had Hendrix king of rock, Marley king of reggae, Elvis king of rock'n'role then there's you bill gates king of crap!
Long live the king!!!!! LOVL
A big thank you goes' out markanthonypr on xda-developers for pointing this out, nice one m8
http://forum.xda-developers.com/archive/index.php/t-476940.html
hope this comes in handy for others "knowledge is the real king give it freely"
regards to all
Muzz