Get the really easy question out of the way first. In the wiki and other places concerning making settings last through a soft restart to poweroff the device for 10-15 seconds. What exactly does that mean, just press the power button and wait 10-15 seconds? I thought that only turned the screen off...so is that not the same as just waiting 10-15 seconds or am I missing something.
Now to the GPS issue. I got a BT-338 and iGuidance (2.1.3 + WM5patch from the inav site) for Christmas and installed it on my laptop and BA (PDA2K w/WM5). Everything works correctly on the laptpop, it shows the correct coordinates and the software worked great as I drove around. However, when I use iGuidance on my PDA, it gives me incorrect coordinates (ex 22.625977N 2.347656W which is in Africa and I am in Alabama). I have checked out the posts at gpspassion.com and followed the standard setup. I feel like I have tried just about everything, but I just can't seem to get it working.
So, does anyone have any insight as to what the problem might be or have any ideas as to how to trouble shoot this problem?
Thanks in advance for the help,
Jonathon
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
I am still on my S100 with tt6 6.010 (7720) and no SIM since I currently use it solely for navigation. What I experience is not really a lockup but just a big delay (almost 1 min) after tt has initialized and only if "Enable wireless data" is enabled.
UPDATE
Turns out that this was a system resource problem. I have Wisbar 2 Advance, PocketBreeze 5, Phone Alarm, and PhotoContacts Pro all active on my device. I guess this is just too much to handle for the Omap when I try to add TomTom on top of that. When I exit WA2, PA and PhotoContacts, shut the device off for about 30 seconds, then turn it back on and launch TomTom, I have no problems. I have also been able to do it only shutting down WA2 and PhotoContacts, but it still locks from time to time like this. I have to shut down all three to be safe. Leaving PocketBreeze running (with some plug-in tabs active too) seems to be a managable workload for the processor. It's kind of a pain, but at least it works! It's not like I need a nav program every day!
Later...
Glad to know you found the source of your problem.
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
psargent said:
Anybody seen this before?
My TomTom will freeze when I try to open it, leaving the top bar visible when the title screen shows and it just hangs. This seems to happen under the following circumstances:
1. If I have just closed it after using it, I cannot open it again immediately after without hanging. Must turn the unit off for at least 30 sec in between. Regardless of battery or a/c power.
2. When running on battery power, it seems to hang as described every time when I try to start it. UNLESS....
The only way I can seem to get it started is to connect to my laptop via usb. TomTom seems to boot fine then. Then I let it get a fix and then disconnect from the computer without turning the unit off. Then I turn off the P3300 and wait about 30 sec to a minute. Then when I turn it back on, TomTom will boot normally. It's like the start up on a/c power initialized the program to work on battery power! However, if I try to start it twice in a row without shutting off the PDA inbetween for this short length of time, it will hang again. Is there some weird connection between a/c power and TomTom stability? Why does the unit seem to have to rest between startups?
I've been messing with this for two days and that is the best I could do. Am I going crazy, is this a bad copy of TomTom or shoud I just learn to live with it? (Come on iGuidance...put out a patch for the P3300!!!)
***********UPDATE*****************
Seems like it is not a/c power, but the Activesync connection that is initializing my TomTom. Once I start getting these freezes, the only way to get back relatively normal initialization of the program is to connect to Activesync via usb, start TomTom and then unplug the usb cable with the program still running. Maybe someone can figure out the connection between the two - right now I'm drained and out of ideas. At least it works in some capacity. Maybe ignorance is bliss...
Click to expand...
Click to collapse
I'm having the same problem as above! I've installed Battery Status and overclock to 247... but no difference unfortunately. Anyone any tips for this problem?? It just seems to hang lots!!
Maybe Co Pilot would be better??
Have you tried to defragment your memory card of maybe even clear of any redundant registry entries. I was having issues not too similar to yours and I found that pocket mechanic was able to resolve some of the issues due to the card having so many redundant files and the registry. Give it a go using the demo may solve your issue?
Magic Button - Pocket PC Task Manager
This will CLOSE the program instead of MINIMIZING it to the background process.
JC#79 said:
Have you tried to defragment your memory card of maybe even clear of any redundant registry entries. I was having issues not too similar to yours and I found that pocket mechanic was able to resolve some of the issues due to the card having so many redundant files and the registry. Give it a go using the demo may solve your issue?
Click to expand...
Click to collapse
I only started putting things on the card two days ago - day two i started having tomtom problems.
I'll def give this a go though and let you know if any improvements...
Thanks!
i have the exact same problem with my dopod p800w/artemis etc etc......i found a way to eliminate the freezing and hanging.......rule of thumb is to open the program by going into its root directory and opening it from there, instead of opening it via the start/programs shortcut or today screen......basically just make sure you open the program by going into File Manager and look for the tomtom navigator.exe file (usually in the program files folder and then navigator folder) and open it that way......ever since i tried it this way i never get any freezing and the program would start all the time.......it works for me......
How can anything this good be this bad?
You can buy TomTom navigator5 for pda for £75 at PC World less on the Net
for this you get a 128meg sd card with tomtom on and a wireless bluetooth reciever and a Car charger.
You don't get a Mains charger but I found a USB hub Psu or my old toshiba pda E740 PSU will do the trick.
With the Universal software set up is a breeze. The trouble comes with the bluetooth gps which isn't adequately documented by tomtom. It is a good GPS receiver so whats bad.
on the Reciever are 2 Leds and a button
the first led has 3 states
Red totally discharged
orange charging
off fully charged (or fully discharged or broken or)
The 2nd Led is green
with 3 states
green - got a lock
green - flashing got a lock and talking to your Pda
off - switched off, or not got a lock and switched on, or its broke.
The button
push for a second on
push for a second off
push for 3 seconds reset
push repeatedly - unknown state (and it can take up to a minute to get a lock)
The problem is that fully charged and indoors you probably will get no lights at all and will not be able to tell if its on or off or broken.
if its not talking to your pda it will turn itself off after 5 minutes also if your stationary.
you can spend forever trying to get it working if you go in under bluetooth you should be able to discover it. but if you start the tomtom software it will tell you no gps.
The only definate way to get it connected is to go outside press the button and then the green led should light letting you know its on and has found some satellites. then if you start the tomtom software and choose tomtom gps it will connect.
you can share the gps using the gps settings in connections and bluetooth
(but someone else can explain that).
if you are indoors and trying to set this up, you will get nowhere.
hope this is useful info.
one more thing each gps has its own mac address as well as its display name so its possible you think you have a partnership but thats a different tomtom wireless gps unit. (the one you took back coz you were convinced it was broken).
blackest_knight said:
<snip>
if you are indoors and trying to set this up, you will get nowhere.
Click to expand...
Click to collapse
The only comment I can make here is that a lot of GPS recivers won't work indoors. I'm using a GPslim236 and this works ok indoors (at home) as long as you are close to a window (within 6ft). This uses the SirfIII (?) chipset. The earlier chipsets wouldn't work at all indoors (iirc).
Mav
The tomtom bluetooth gps is sirf III,
Seems to get a good signal most of the time.
you would think getting two bluetooth devices to pair together, location would be fairly unimportant. However with the tomtom unless its got a fix it doesn't want to play.
once you 'grok' the device its ok, but I still would have prefered an on off switch with some feedback.
I no longer have working GPS. I first noticed when I went to the latest NRG ROM and assumed it was something in the ROM or update but having flashed back to stock multiple times I cannot get it working. Neither Google Maps nor HTC GPS tool can get a lock on any sats. (NRG or stock)
Anyone know what may be wrong?? I've never messed with any GPS anything...aside from enabling AGPS.
Go to the Rhodium Windows Mobile ROM Development forum and you'll see the Task 29 sticky. Get it. Then, rename the .nbh of the custom ROM you want to "RHODIMG.nbh" without the quotes and copy and paste it to the ROOT OF YOUR SD CARD. By root, I mean not in any folder, just loose on the first part of the storage card.
Then while connected via ActiveSync or Windows Mobile Device Center, run the Custom RUU (ROM Update Utility) that came with the task 29. When it is done, remove the USB cord and battery. Replace the battery, and hold volume down then press and hold the power button until the tricolor bootscreen comes up. If you named your ROM right and it's in the root of your storage card, it will prompt you to install the ROM. Do what it says. When it is done, soft-reset using the stylus.
Then, immediately hard reset by removing the battery, remove microSD, replace battery, and press and hold the green and red answer/hang up hard buttons and while holding those press and hold the power button until it brings a gray screen with blue lettering about how it'll restore to manufacturer defaults. Follow the direcitons until it's done, and then when it is press volume up to boot.
Run the ROM's autoconfig and then soft reset. Then after that do the Connection Setup, and then soft reset again. Then test your GPS. If it still doesn't work, PM me. I've gone apesh*t tweaking my GPS, and it works quite well.
awenthol said:
I no longer have working GPS. I first noticed when I went to the latest NRG ROM and assumed it was something in the ROM or update but having flashed back to stock multiple times I cannot get it working. Neither Google Maps nor HTC GPS tool can get a lock on any sats. (NRG or stock)
Anyone know what may be wrong?? I've never messed with any GPS anything...aside from enabling AGPS.
Click to expand...
Click to collapse
Are you by chance on AT&T? In many areas, AT&T has done something to their towers that breaks the CellID resuests over 3G, which allows AGPS to work properly. If this is the case the solution is to toggle off 3G and switch to Edge. Then soft-reset and re-run your GPS app to get an initial lock. Once you get an initial lock you can flip back to 3G.
is your device seeing satelites and not locking, or not seeing satelites at all?
get htc gpstool, or chartcross gps test, if no satelites what so ever are showing up (in view) than something could be physically wrong with your device (which i highly doubt but i've burnt out a gps antenna on my original tilt).
Also, are you in an open area? i can't get a lock (or it takes significantly longer) even when i'm on my balcony, which is on the north side of my building, but if i just go to the opposite side of the building, i get an instant lock so make sure you have no obstructions at all.
My suggestions would be to install the aGPS cab in my sig, soft-reset, update quickgps, then run chartcross gps test. See how that works out for you and report back (btw, the agps cab in my sig gets me cold locks in 10-15 seconds!)
VoiP ?
i had the same problem and found out that it was VoIP which was causing it.
I flashed my phone to clean everything and did not reinstall VoIP.
Why do i have to wait so long to get gps steady and ready once i have destination from a to b set ? on my htc one one- two seconds bang and it's ready..
GalaxySIIII said:
Why do i have to wait so long to get gps steady and ready once i have destination from a to b set ? on my htc one one- two seconds bang and it's ready..
Click to expand...
Click to collapse
same here, takes ages sometimes... b114
Mine sucks too. Last time it did more than 60 secs to lock in an open field (no buildings nearby). Also, it seems when you move to another city and have the phone rebooted, the locking time gets higher.
Mine was horrible for two days. No lock during a 40min run with no buildings nearby to block the signal. Nowadays i get a lock in two days and theres loads of satellites when checking the gps-stats. I guess it has to be a software issue that got fixed during a reboot(forced reboot) or factory reset.