Hi,
Destinator problem with XDA II ROM:
ROM-1604eng
ROM-16036wwe
ROM-v16050
ROM -16021wwe
ROM-16052ger
All these ROM versions has the same problem, The PowerLOC Destinator can not find com 5, if I use the Pocket Blue Tools patch the freeze in com 7.
The only way I find to use the PowerLOC Destinator in the XDA II is with the Rom version 1.03.00 wwe_o2 asia together with the Pocket Blue Tools.
Somebody suceed using the PowerLOC Destinator with new Rom?
Best,
Dias
PowerLOC Destinator problem with XDA II new ROM:
My Destinator works fine with bluetooth patch and 1.66.00WWE ROM. Don't know what your problem could be, other than not doing things in the finicky order the XDA II requires with BLuetooth.
Bluetooth Destinator Problem
Vitor,
You could answer some questions: :?
1) Which is the version of the destinator that are you use :?:
2) You are using the Pocket Blue Tools :?:
3) Which is the GPS you are using :?:
4) Which setings that you are using is the xda II :?:
All the best.
Dias
Bluetooth Destinator problem
As I stated, everything is working rosy for me here...
Data:
New I-mate with newest ROM
Destinator 3
Haicom CF GPS with Bluetooth Slipper (BT-4 "something")
Pocket Bluetooth download
Sometimes it can be flaky, but that is only if I don't follow the same simple procedure all of the time.
1. Add bluetooth device pairing. When the Bluetooth add in asks me which type of setting I want (last step in the whole process), I choose COM 7.
2. Connect to the device
3. Start Destinator, and have it hunt down the settings (or set them to COM 7 and NMEA 4800)
4. you are done.
Upon subsequent usage of the Destinator / GPS / Bluetooth combo, do the following and it works EVERY TIME
1. Leave bluetooth on the XDA off
2. Plug in the CF GPS to the Bluetooth slipper (light flashes)
3. Start Destinator
4. You receive the message that bluetooth is not on, do ya want to turn it on (say yes -- I do not choose to "not have the message displayed again")
5. Wait about 5 seconds until the Destinator Software shows the Agree/Disagree screen - hit agree (obviously)
6. You are rockin and rollin very fast and reliably.
If anything is unclear here (as this is from memory), please post again and I will answer
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 would like to help other people out there wishing to use TomTom Mobile v5.20 on an WM5 device to solve a problem which prevents using any kind of external GPS unit (beside the TomTom one).
Should you need to connect a thirdy party GPS device to your WM5 device using TomTom, please note that the name of the BT device (upon recognition), should be modified to contain the letters " GPS" at the end of the name, if this is not yet provided by the device name itself.
I had to google around very long to be able to find this trick, but it seems it only appears on WM5 devices (I had not such problem on a WM2003 SE device...).
Hope this helps someone with more GPS units as I am.
Ciao
hi have tried all sugestions on the forums but still no lucck im using tomtom 6.02. could someone be nice enough to post directions to how they got it working step by step thanks.
The GPS is on Com5 at 9600 bps, try turning off the microsoft GPS manager thing in control panel and set com5 9600 manualy in TomTom.
"Scott Scott, do I turn left at the next junction?"
Tomtom
Mine works perfectly, just make sure your GPS receiver is the build in one that is used by Tomtom!
Harold
Orbit2-- GPS cannot be detected with IGO PLS HELP?!?!?
I have a HUGE problem with getting my GPS running on my Orbit2. It came from O2 with CoPilot7 preinstalled with the maps of UK and Ireland, which I dont use, because I am not located inthere, nevertheless Copilot detects GPS signal and shows positioning, but i dint have the maps for the area that i am in.
I tried to install IGO6 and then IGO8 but I have the same problem-- it cannot detect GPS device, no matter what which COMM Port and BAUD Rate I select.
How come CoPilot detects, and IGO does not? I read that Orbit2 is not locked?!?
Should I boot the whole device using some other ROM.
Please do not double Post
I suggested an answer for you over in the Athena post. In the future, please do not double post as this only clutters the forum.