Hi Guys,
I've got the O2 XDAIIi with TomTom6 installed and working fine aside from one thing, if I leave the phone on (flight mode OFF) whilst I use TomTom for my Sat-Nav the phone will crash, everything just hangs and I can't get anything working without a soft reset, this only tends to happen at certain geographic locations so I don't know if it's when the phone switches to a different antenna.
When I use TomTom with the phone off (flight mode ON) it works flawlessly.
I've had a chat with TomTom but the only thing they can suggest is that I just turn flight mode on when I'm using TomTom, this solution is all well and good but if it means that I can't receive any calls whilst I'm driving (don't worry I use a bluetooth handsfree kit)
Has anyone else experienced this problem and know of a solution?
Regards
Will
i've had the exact opposite - XDA2i with TT6 and a BlueTooth GPS receiver works perfect when flight mode is off - put it on to STOP calls and the GPS doesn't work
No idea about the solution - I just leave it on. Maybe check which Rom you are running
Stuart
If you enable flight mode it turns off anything that is wireless (including bluetooth) so that it doesn't interfere with equipment etc. This explains your loss of bluetooth connection to your GPS
I have read of a flightmode bluetooth workaround on John's Reviews
Thanks for replying guys but I'm using a cable GPS receiver not a bluetooth one.
Any ideas what I can do to sort it?
Regards
Will
NO GPS DEVICE - TomTom SatNav on XDA IIi
Guys and Gals,
All you need to do if using a cabled GPS receiver, is as follows
START >
SETTINGS >
CONNECTIONS tab >
BEAM >
Untick the receive all incoming beams,
The IR receiver and GPS receiver both use COM1.
Problem Solved....! Neil
Thanks Neil but this isn't the fix for my problem, I already know that the IR and the physical connection share the same COM port and the IR needs to be disabled before a device is found but this isn't the problem. The issue is with TomTom hanging the device during useage when the mobile aerial is turned on - IE. Not in Flight Mode. It seems that TomTom will only reliably work when I use it with Flight Mode turned ON.
Related
I thought I would add my tuppenyworth to the Tomtom problems with the XDA 2i. Bought a wired Tomtom "Official" GPS receiver for it and tried it with TT5 to no avail. It would not recognise the receiver at all no matter how I tried to specify it's com ports etc..
I eventually upgraded to TT5.1 and it worked immediately with no problems at all. Been working fine ever since.
if it matters
hi, i have a xda 2i and use tomtom 5.20, when i use my wired gps i was told to switch off the infra red beam, mine seams to work like that.
port problem?
could anybody help? my xda2i never works with tomtom5...
how to switch the beam off pls??
switch off receiving beam????
under setting > connections > beam
O2 XDAIIi with tomtom 5.21 and BT GPS receiver
but there is still problem with the signals, it can display the right UTC time, and numbers of satellites, such as 29 on the North, but there all gray and said no valid GPS signal!
the com ports couldn't be changed which are com5 inboard, com6 outboard.
does anyone know what the proble is pls??
ps: I installed the BTHTools1100, but no change
see the attachment pic
many thanks
Hi Piers,
i've got exactly the same problem :-(.
With a GlobalStar BT348, the GPS signals are plainly perfect. But when i connect the official Tomtom wired receiver, i only get the grey bars, although, like you, the UTC and spinning wheel are there, indicating the GPS is detected.
I looked at the compatibility list on the Tomtom site, and besides Dell and iPaqs, there seems to be nothing compatible with the wired receiver.
Anybody has other information?
Hi again,
I think I found the solution
1. of course, "receive all incoming beams" has to be off
2. apparently, you can not have a paired BT GPS receiver (even inactive) when you want to use the wired Tomtom receiver... :shock:
I guess it has to do with the way WM2005 deals with GPS... :?:
So, in BT devices, delete the partnership with the BT receiver and everything works fine with the wired one. In TT5, simply declare the receiver as a wired Tomtom
I used it this morning, driving 100km, 90minutes, without a crash or anything
I have a XDA 2s with Tomt Tom 5 on.
I have paired the Bluetooth gps receiver and although the GPS Viewer program picks up the gps signal on the pda via the Bluetooth receiver, for some reason Tom Tom doesn't connect to The Bluetooth Receiver.
It was working and it's suddenly just gone off.
I have tried uninstalling and re-installing Tom Tom but no luck.
Can someone help me please.
Daft question, but have you disabled InfraRed Beam in connections?
No i haven't but i can sure try
and i'll try anything at the moment.
I've disconnected all beams but no luck, i've even tried doing a hard reset but that didn't work either.
I wonder if anybody knows if it is possible to have two (or more) divices connected at onceon a Blue Angel?
eg. Tom Tom 6 plus a hands free connection.
I have tried every configuration I can think of, different ports ect, but to now avail.
With the gps connection up and running, as soon as you turn on the hands free , the gps connection link is lost, turn off hands free and it will resume connection.
I am using BA WM5 AKU3.5 R4 - xplode's excellent rom
In GPS settings
Program is using COM 5
Hardware is using COM 0
Manage GPS settings set to Auto
In Device settings,
BTGPS unit is on COM 0 (Serial box ticked)
Hands free is unassigned
Any help will be much appreciated.
any idea's anyone?
On Last Baniaczek's ROM I made an experiment just a moment ago: BlueAngel, Navigation system (Polish one, Automapa), plus GPS on Bluetooth and A2DP headset - first connected headphones, then added GPS (using automatic GPS connection - it's M$ Stack) - Everything seems to be working fine. I thought it was a bit unstable at first, but AD2P stops sending data, when there is no sound from the device.
GPS Settings are default: COM6 for applications and GPS has COM7 assigned on Hardware tab and in Bluetooth outgoing port. Quite seamless.
then I made the 2nd one: same headset connected in Handsfree mode: indeed turning on navigation made it connect and disconnect every few seconds.
For me it seems to be fault of M$ BT stack: it cannot hold 2 similar streams on BT (COM and Handsfree/Headset are both typical serial connections of highest priority in BT stream). At the same time it can cope easily with two different streams (A2DP is lower priority, high-bandwidth BT connection).
I'm not sure, but I think when I used old Helmi 1.3.2 with Widcomm stack it could cope with GPS and Handsfree at the same time, but it needs more testing.
jakubd is right it is limitation in MS BT Stack
Don't give up and it should start to work. I have similar problem with BT GPS and BT headset. GPS goes on and off while headset is on. And than I try to switch headset off and on, BT off and on, GPS off and on and after some time it start to work together with no problem. It takes first 10-15 minutes of my voyage but then it works for the remaining few hours.
Sorry, but I still didn't find out what combination make it work. If I do, I will post it here as workaround.
And I'm almost sure that I had no such problem with Helmi 1.4 ROM.
Thanks guys,
have tried every configuration I can think of, but its always the GPS connection that is dropped, not the hands free, this would not be a problem if it was just when you are answering a call.The GPS reconnects only when you disconnect the hands free connection. ?
Has anyone Successfully used the Widcomm stack with this type of setup?
I am sure alot of members would find this usefull if it can be made to work!
This is my experience:
ROM : Helmi_BA_WM2k5_AKU3.5_v1.4.CF2.R2 (baniaczek)
Tom Tom 6
GPS : Bluetooth
Headset : Nokia BH-300
When the headset is on and connected, the GPS doesn't work (TT say no GPS found). When I turn off the headset, the GPS is working.
With ActiveSync I have the same problem: when the headset is turned on, I can't establish a connection with the PC via bluetooth.
BUT!
If I use a different headset, a Logitech HS03, all is working fine. I can leave the headset on and the GPS is working. I can receive incoming calls with no problem (using the headset) while I'm driving without loosing GPS signal.
With ActiveSync is the same: I can connect my PC with the headset on.
I have no idea why there is this difference with these two headsets, but one is working and the other no. I don't know if the problem is the MS BT stack, but my test demonstrates that under some circumstances this stack could manage more than one connection at time.
bigmike said:
I don't know if the problem is the MS BT stack, but my test demonstrates that under some circumstances this stack could manage more than one connection at time.
Click to expand...
Click to collapse
Bigmike, my point exactly. As I wrote in my post I keep turning on and off until finally it works. So there are some circumstances under coexistence is possible.
It seems that devices try to use same port which means that first device does not reserve port for itself. I am not an expert but it seems if we could somehow force devices to use different ports problem would be gone.
bigmike said:
If I use a different headset, a Logitech HS03, all is working fine. I can leave the headset on and the GPS is working. I can receive incoming calls with no problem (using the headset) while I'm driving without loosing GPS signal.
Click to expand...
Click to collapse
If this works with one set and doesn't work with another, it might be connected to list of profiles supported by the headset:
1. Headset - HSP - more common, typical profile for use with cell phones (supports AT commands)
2. Handsfree - HFP - audio-centric, used mostly in cars, less common
http://en.wikipedia.org/wiki/Bluetooth_profile
My SonyEricsson HBH-600 has both profiles (checked with services list on SonyEricsson phone), but I don't know how to select which profile is used by headset.
Just a thought...
sassa said:
Bigmike, my point exactly. As I wrote in my post I keep turning on and off until finally it works. So there are some circumstances under coexistence is possible.
Click to expand...
Click to collapse
I hope you haven't misunderstand my previous post. I haven't in mind to minimize the value of your post (very useful is someone will try to investigate about this problem).
I was thinking that somebody, reading your contribute, could wrongly think: “you're are a lucky guy and turning on-off the headset repeatedly you crash some library and the two devices are working together”.
My intention was to remark the fact that under some circumstances the headset and the gps can connect together every time and always at first try: it's not lucky, crash or random events.
jakubd said:
If this works with one set and doesn't work with another, it might be connected to list of profiles supported by the headset
Click to expand...
Click to collapse
I have a similar thought.
It seems to me that some times ago I have read that it should be possible to change some profile's parameters “playing” with the registry.... but I could be wrong...
bigmike said:
I hope you haven't misunderstand my previous post. I haven't in mind to minimize the value of your post (very useful is someone will try to investigate about this problem).
Click to expand...
Click to collapse
No I have not, bigmike, just the opposite. I was delighted that somebody confirmed my point.
bigmike said:
My intention was to remark the fact that under some circumstances the headset and the gps can connect together every time and always at first try: it's not lucky, crash or random events.
Click to expand...
Click to collapse
Couldn't agree more. And I think it's worth trying to resolve it.
Multiple BT connections - solution?
I think I find a solution for this, or maybe we can call it workaround. At least it works for me.
As I wrote in my previous posts, I could make it work every time just didn't know how. Now I established repetable procedure which worked every time for reasonable number of experiments.
Secret was to turn on BT headset (in my case Plantronics) and BT GPS device (Haicom 406-BT) and GPS program (iGo) first, and then go to Comm Manager and turn bluetooth on.
So my procedure is:
1. make sure that BT is off in Comm Manager
2. turn on BT headset
3. turn on GPS device
4. open iGo program
5. minimize iGo
6. turn on BT in Comm manager
7. open iGo and make sure it's connected
8. go to phone and call myself just to make sure it works
9. back to iGO and make sure it works
If 8 or 9 fails for the first time, just turn BT off and on again in Comm manager and check it again. I never need to do this more than twice.
Try this, guys, and good luck.
P.S. I don't know if it matters, but make sure that in Settings/Connections/GPS "GPS program port" and "GPS hardware port" is set to (None) and "Manage GPS automatically" unticked.
Very good! Many thanks Sassa!
I have tried for two times your procedure and both tries worked very well (with TomTom6 and Nokia BH-300)
I use a slightly different procedure:
1. BT off in Comm Manager
2. turn on BT headset
3. turn on GPS device
4. turn on BT in Comm manager
5. open TomTom 6 (wait some seconds and make sure it's connected)
6. go to phone and call myself (on the first call the headset is disconnected)
7. back to TomTom and make sure it works
I have noticed a different behavior of the BT headset having the BT always on (in Comm Manager) and using this procedure... but I need to make some tests before writing more.
Guys / Gals
I have just picked up a WIRED GPS reciever and want to get it to talk to my XDA11i.
I also have tom tom that I want to use .
Tom tom expects to see the GPS unit on Com 1 ?
How do I set up the XDA to recieve GPS on com 1 (Tried all sorts of things but no joy , didnt believe I was an amateur but seesm I am . I haVE TURNED off " recieve all beams " but still no joy .
Any help greatfully appreciated.
Astro
I do use Pugs rom but have read that it is still possible to link to a wired device ? if not I will have to splash out on a Tom Tom Bluetooth Gps ? or will others do ?
Firstly, I am assuming you have got some way for the wired GPS to connect to your PDA (via car cradle or similar cable).
Ensure GPS unit is switched on & running, and connected to the PDA.
Start TomTom, which will ofc bleat "No GPS device!"
Tap screen, Change Preferences, tap next twice to take you to prefs screen 3, tap Show GPS status, then tap Configure
Tap the left/right arrows until Other NMEA GPS receiver is showing, then tap Select
Accept the default BAUD rate of 4800 for now, and tap Done
Now, you will be presented with a list of the available ports that TomTom can 'see'
You will probably have several COM ports available. (mine showed up with COM2, 4, 5, 6, and 9 available for example, but ymmv)
Checking that your GPS unit is still on, select the first suitable COM port in the list, whatever it is. This will take you to the GPS status screen.
IF you are lucky enough to have selected the correct port for your wired GPS unit first time, you will now see the yellow/black wheel at the top right rotating, which indicates it is receiving data from the GPS unit. (a non-rotating wheel means TomTom can't 'see' any GPS data coming in)
If the wheel is NOT rotating, don't panic, but once again tap the Configure button and repeat the steps, this time slecting the next COM port in it's list.
Repeat this process, moving down through the available list of COM ports until you hit the one where the wheel is rotating: this indicates that TomTom has successfully 'found' the GPS unit and is receiving data from it.
Assuming you DO get a rotating wheel, click done on the GPS Status screen and you will go back to TomTom's main screen, hopefully now with the correct location showing!
Hope this is of some help.
Joe Pinball
P.S. if you have had no joy with this, or dont have/cant find a cable to connect the GPS unit to the PDA/cradle, you may well find a Bluetooth GPS unit is a better way to go (try and get one with the SIRFSTar III chipset, as it's way better performance in marginal conditions): I navigate and leave my BT GPS (GlobalSat BT338) in the car glovebox and STILL get a good signal! - Joe
Wired GPS connection to XDA11i
Joe
Thanks for the info I will try that one out tonight .
To try out the system I have picked up an early Rikaline wired unit which connects directly to the XDA11i socket as well as the car lighter socket to rum them both.
My question was did i need to do any thing to the XDA to tell it to accept the plugged in device ? as you would if you set up a bluetooth system ?
Does the XDA11i automatically SEE the device you have plugged in ?
Duncan
The XDAIIi's socket contains both a USB interface (for the cradle) audio (for in-car sounds/wired handsfree) and a serial port, so as far as I know, once the GPS unit is plugged in (and assuming it outputs the NMEA standard for GPS data, which they all seem to do) all you would need to do would be to configure TomTom with the unit plugged in & working.
Once set up correctly, and you have a decent positional fix, quit TomTom in the normal way, leave it a minute or 2 and then re-start TomTom to check it saved the settings correctly.
If the settings were stored correctly, TomTom should start (can take a while with version 5.XXX, now down to a couple of seconds with V6.XXX) and then a short while later TomTom will announce on-screen "No GPS Device!"
(note: I have a bluteooth GPS and find although TomTom is capable of switching on BT for me, it will never 'see' the GPS this way: I have to switch BT on first, THEN run TT for it to see the GPS. It is entirely possible, that with a wired serial connection, TomTom may well see the GPS data immediately and NOT flash up the "no GPS device!" message, in which case it's win-win for you!)
Be patient at this point and it should soon 'see' the GPS data coming in and get a position up on the map.
Hope this helps
Joe Pinball, now with a fixed screen! yay!
Still not working !! Doooh
Joe
After a frustrating day with the wired device I gave in and picked up a Bluenext BN-806F bluetooth gps unit .
But I am still having problems. I am not sure that the uinit is not faulty as even when paired the status shows NO data going either way . PS when I go to Blue tooth manager and then active connections there is only an outgoing connection set ???
Any chance yo can run through the set up for blue tooth gps and tom tom for me ( I have a copy of tt5.21).
Do I need to set any thing ref the Com ports / beam / baud rate ?
How do I set the time that the XDA11i holds an active connection before it times out ( if no data recieved ) as the XDA breaks the connection after a while of no activity ?
Best regards
Astro1
I connect my alpine to the gps receiver, but after few minutes, the conenction drops. I have not figured any problems with my bt hansfree.
Can anyone help??
turn off bluetooth
dropped connection
I have a similar problem . Alpine and BN806F , It pairs , wont talk then drops out ? I wonder if there is a time out after no activity ?
As my post says I am having a problem getting tom tom to see my gps reciever , do you have the some problem ? what am I doing wrong ?
Astro1
I downloaded a bt patch but the problem remains. I wonder whether it's a software or hardware problem..
Yes, I can't make my navigation program to see the gps receiver and after a while it gets disconnected...
To the OP - you said you cant get your navigation software 'see' the GPS - this is the root of the problem.
If your BT GPS unit doesnt see any requests to send data to the PDA, it will auto-switch off after a set period of time.
Once you can successfully configure your nav software to receive the GPS data, your bluetooth GPS unit will remain powered on.
You should have a software CD that came with the GPS unit (if not there are a number of freely downloadable GPS utilites for PDAs, some of which can scan for the unit to find it)- there's usually some very low-quality GPS checking utility that displays what satellites the unit can see, signal strength and so on: try using these programs to see if you can connect to your GPS, and if the unit than keeps the BT link open.
Maybe finding out which COM port the GPS unit appears on, will allow you to configure your nav software correctly to see the GPS.
Joe Pinball
I managed to connect it succesfully some times. Usually, it connects via bluetooth but it drops until I load navigator ( my navigation program). When I close the program, the bluetooth is off. I tried to search windows for power save settings but I didn't find something that would help.
GPS problems
Joe
Thanks for your advice I am still haviong big problems .
I have managed to get Tom tom to recognise a wired reciever ( but only once , and then when the cigarete lighter plug moved the unit powered down all was lost.
Do you know of any utilities that will show what is connected to what port as I believe this is the real problem . Aparently tom tom has a bad history of hijacking ports ?
It would be good to see what was actually going on .
Astro1