Hey guys I am having some trouble with my universal and iGuidence. The program loads fine but as soon as it connects to my GPS receiver it freezes. I have the latest patch from inavcorp and both program and receiver worked fine on my treo 750, but for some reason it doesnt like my Uni. I have tried hard resets, soft resets, uninstalls, reinstalls, and even 4 different roms (WM6 and WM5). Nothing seems to work. Any ideas?
mikef1182 said:
Hey guys I am having some trouble with my universal and iGuidence. The program loads fine but as soon as it connects to my GPS receiver it freezes. I have the latest patch from inavcorp and both program and receiver worked fine on my treo 750, but for some reason it doesnt like my Uni. I have tried hard resets, soft resets, uninstalls, reinstalls, and even 4 different roms (WM6 and WM5). Nothing seems to work. Any ideas?
Click to expand...
Click to collapse
Works fine for me. I installed it on a 133X card; is yours fast enough? Cheers,
Related
Hi all...
Ive got TomTom 2.4 installed and am using the Rikaline x7 GPS receiver.
On two occasions when using the navigator to get me to a destination... it has crashed requiring a hardreset - it seems to crash wehenver i try accepting a call and navigating at the same time. Normally i annoyingly have to softreset the phone, but on the last occasions have had to do a hard reset. Any ideas why this could be happening and how i could try and avoid it. i am also having to use Towa's patch is that of any help, without which i can get the GPS receiver to work.
Thanks
Faisal
I just purchased the Fortuna Clip_On Bluetooth Reciever for my XDAII. First install went fine, I set it all up and used it walking home from the station. The TomTom software worked faultlessly and was quick to use. When I got home I closed TomTom, turned off the GPS and put the XDAII on the charger. In the morning I opened TomTom to setup a trip to France. When I opened TomTom it was VERY slow. It took about 8mins to open the application and navigating around the software was impossible. It did not crash or give me any errors it was just real slow. I uninstalled the application and reinstalled it. This seemed to solve the situation temporarily and off I set on my journey. After the first leg of my Journey I turned it off whilst on the Ferry. Next time I turned it on it was back to snails pace and so rendered it useless for the rest of my journey.
Any ideas whats going on? Is this a common problem?
WiZeR said:
I just purchased the Fortuna Clip_On Bluetooth Reciever for my XDAII. First install went fine, I set it all up and used it walking home from the station. The TomTom software worked faultlessly and was quick to use. When I got home I closed TomTom, turned off the GPS and put the XDAII on the charger. In the morning I opened TomTom to setup a trip to France. When I opened TomTom it was VERY slow. It took about 8mins to open the application and navigating around the software was impossible. It did not crash or give me any errors it was just real slow. I uninstalled the application and reinstalled it. This seemed to solve the situation temporarily and off I set on my journey. After the first leg of my Journey I turned it off whilst on the Ferry. Next time I turned it on it was back to snails pace and so rendered it useless for the rest of my journey.
Any ideas whats going on? Is this a common problem?
Click to expand...
Click to collapse
What type of card? sd/mmc?
what version xda roms
what other apps. e.g. GPRS mon is known to cause problems sometimes.
try tomtom 3, it's much faster / more reliable.
I'm using xda2(1.6) + sd +cf, tomtom 3.01 + fortuna gps without problems.
you need GPS driver version 2.09!!!
I had the same problem cause I was using driver version 2.00, then I moved to v2.09 and it worked perfectly.
Ciao :wink:
I tried last week TomTom3 + i-mate+ Royaltek BT GPS, I drove in the UK. Everything worked very good all the time.
I am using all the latest ROMS, with Bluetooth tools.
How can I check my BT driver version?
It is a 256 SD card (Viking Interworks)
Rom Version: 1.60.00WWE
ROM Date: 12/03/03
Radio Version: 1.10.00
Protocol Version: 1.337.18
ExtROM Version: 1.60.50
Not much else is installed, I am using 1-calc and the check/clear notifications app. Thats it
Where do I get the updated GPS Driver?
give me your email via pvt msg and I will send to you, ok?
I tried to post it in the forum, but no way.....
its ok i found it on pocketgps. However it has not solved the problem. I installed the GPS update, cold booted and the same problem exists
Any other ideas?
what i do not understand is why it would work perfectly for about 2 hours then just slow right down like this.
Have you set GPS connections to:
- TomTom Wireless GPS
- Bluetooth GPS
I have these settings in v2.09 GPS and it work perfectly with fortuna clip-on...
I repeat that I had the same identical problem as you have and I solved with 2.09 driver and the settings you see above...
good luck
oops, actually i just noticed its 2.07 i updated to.
How big is the 2.09 update?
I found the 2.09 update on the web, but its not solved anything
after the update it is still really slow
Have you set GPS connections to:
- TomTom Wireless GPS
- Bluetooth GPS
I have these settings in v2.09 GPS and it work perfectly with fortuna clip-on...
Click to expand...
Click to collapse
?????????????????? WHAT ABOUT YOUR SETTINGS ??????????????
GPS Connections? I'm not sure what you mean by this?
Under TomTom GPS I have it set to:
SiRF 38400
COM5
I have it unticked at the moment as I am just trying to get it working properly. The PDA Slider is set to Zzz and sound is on.
Under TomTom GPS I have it set to:
SiRF 38400
COM5
Click to expand...
Click to collapse
change to:
- TomTom Wireless GPS
- Bluetooth GPS
and see what happen... 99% you solve with this settings cause it was the same for me. TRY these settings, let fortuna and XDA2 communicate and that's it!
I don't want fortuna and xda2 to communicate. I want to be able to use create routes without the gps reciever connected. At the moment it takes about 5mins for TomTom to just launch.
i tried these settings and it is still slow, i timed 6mins to launch the application and a further 1min to open the menu.
what other apps?
Wizer,
What other apps do you have?
Have you tried hard reset + reinstall ? First backup with say sprite backup.
I think this is driver related. Uninstall tomtom then reinstall with the latest gps drivers, I am not sure you should be selecting sirf 38400 either.
i tried installing from clean install and i tried with the latest GPS drivers. Nothing solved it. In the end I have had to install tomtom3 which has strangely solved the problem for now. All I have to do now is find the Great Britain maps
Hi All
I have the above setup and am having a nightmare trying to get the bluetooth GPS to work. I have tried every setting I can find and even upgraded the ROM to 1.90.96 to see if that helped but still no joy. Basically whichever COM port I assign 0,4,5 or 8 (the only options allowed) it shows up in the "Other Bluetooth GPS receiver" catergory in TT6 but it will not connect. I have also noticed that the only time the BT LED on the Holox device flashes is during the initial pairing with the jasjar, before the device default password "0000" is added. Once this function has been completed tthe light remains solid and tt6 does not recieve the gps signal.
I know the Holox unit and the TT6 is working fine as I have tried it on an old HP 1940 with wm2003 and it works perfectly.
Has anyone got any ideas, suggestions or experienced the same problems
When you set up the Pairing with the GPS receiver use COM0 and select the serial port. Once this is done, set up a new outgoing COM port and make sure that the "Enable secure connection" box IS NOT checked. My Exec never works with any BT GPS receivers if this box is checked.
Then in Tomtom set use other BT GPS receiver and select COM0.
Pug.
Hi Pug
No joy I'm afraid. Have tried this more times than i care to mention but TT^ will not recognise the gps device.
Sounds like a problem with your BT stack then. If it worked on your other device then it's obviously a problem with the Uni. Seen as this isn't a common problem, might be some problem with your setup. Thinking about it now, Tomtom overwrites some BT files during install, as you seem to be using an AKU3.2 ROM which will have updated BT stack, try deleting these from the windows folder.
ttn6bt2003.dll
BtCoreIf.dll
BtSdkCE30.dll
If it doesn't work, you can always re-install TT6
Big G said:
Hi All
I have the above setup and am having a nightmare trying to get the bluetooth GPS to work. I have tried every setting I can find and even upgraded the ROM to 1.90.96 to see if that helped but still no joy. Basically whichever COM port I assign 0,4,5 or 8 (the only options allowed) it shows up in the "Other Bluetooth GPS receiver" catergory in TT6 but it will not connect. I have also noticed that the only time the BT LED on the Holox device flashes is during the initial pairing with the jasjar, before the device default password "0000" is added. Once this function has been completed tthe light remains solid and tt6 does not recieve the gps signal.
I know the Holox unit and the TT6 is working fine as I have tried it on an old HP 1940 with wm2003 and it works perfectly.
Has anyone got any ideas, suggestions or experienced the same problems
Click to expand...
Click to collapse
Try reading here:http://forum.xda-developers.com/showthread.php?t=283253
That should sort it.
Mav
Still No joy with Jasjar, Holox BT-321 GPS & Tomtom 6
Hi All
I've tried all fixes for the above problem suggested by pug and mavrik64 earlier on this thread but without success. This is a little frustrating to say the least. The Jasjar has had clean install with nothing loaded other than the default programs included with the latest ROM build 1.90.96 from Jwrightmcps, the UK 'O2' setup and TomTom 6. As I know the software and Holox unit work fine on my old HP1940 running on wm2003, I'm convinced it is something in WM5 that is giving me the problem. I have read other forums were other people appear to have similar problems.
Please note; the main reason I flashed the ROM from that previously installed 1.30.76 was to try and find a fix for this problem. The older version gave me exactly the same problem.
Anyone got any ideas
I am using Ivans Beta 15 and no problems, try flashing with that.
You have a new PM in a few moments as well.
PUG
Any idea where I can get hold of a copy of Ian's Beta 15 ROM. I've trawled round this site but can't seem to locate it
Big G said:
Hi All
I've tried all fixes for the above problem suggested by pug and mavrik64 earlier on this thread but without success. This is a little frustrating to say the least. The Jasjar has had clean install with nothing loaded other than the default programs included with the latest ROM build 1.90.96 from Jwrightmcps, the UK 'O2' setup and TomTom 6. As I know the software and Holox unit work fine on my old HP1940 running on wm2003, I'm convinced it is something in WM5 that is giving me the problem. I have read other forums were other people appear to have similar problems.
Please note; the main reason I flashed the ROM from that previously installed 1.30.76 was to try and find a fix for this problem. The older version gave me exactly the same problem.
Anyone got any ideas
Click to expand...
Click to collapse
Sorry to hear this didn't work. I am using JCs current rom with TT6 and Holux GPSlim 236 and it works like a charm.
Good luck
Mav
i have a xda exec with crossbow i tried delorme 2005 and streets and trips from microsoft but none work does anyone know one that will work
TomTom 6 works, iGo also works, but sometimes hangs every few seconds for me.
thanks
will try
AlanJC said:
TomTom 6 works, iGo also works, but sometimes hangs every few seconds for me.
Click to expand...
Click to collapse
exactly the same here. TomTom 6 works flawless and iGo sometimes gets really slow (but it did that on AKU 3.5 too) and sometimes it quits. Didn't try Navigon though. Perhaps next week.
I've found the hanging on iGo to be a result of looking for an attached, either wired or otherwise, gps device. You can disable the auto searching for the gps and still use iGo for general mapping/routing. In fact its actualy very very good. Graphics wise much better than TomTom. It can be speeded up by deleting any non-UK languages/voices stored on the sd card.
Hi there I recently upgraded my blue angel to WM6, And ever since TomTom Navigator 6 has been running so slow its unusable. Every time I press anything I have to wait between 40-60 secs before it executes the press. Everything else apart from TOMTOM runs fine and zippy. Is there a patch or tweak to give me the speed back.
Thank you for taking the time to read this.
I have tried both Tomtom 5 and Tomtom 6 on thisd WM6 ROM and have no problems at all. It runs very fast. The problem is with your machine.
Just one tip: TomTom is really ****ty app and sometimes have such odd delays because of searching for GPS. Turn GPS function off (offline mode or whatever is the name) or connect the GPS before starting TT. It helps. This is the only aplication I know that has this king of problem.
On WM5, the solution to TomTom slow down was to make sure the phone radio was turned on before launching TomTom. For some reason Tomtom freezes up if you start it when the phone radio is off.
thank you Fredrick_Fredrickson. Worked a treat . Thank you everyone else that took the time to read and reply.
Have exactly the same problem, but my phone is always turned one. Maybe someone got some more ideas?
U pleople are legends
Thanks for all the help in this forum
Very late arrival to this thread, but just wanted to say a big thanks to Fredrick_Fredrickson for that advice, which works great - had the slow/unusable Tomtom bug across different versions of TT Navigator and on different roms - just turned the phone radio on and it suddenly works perfectly. So glad I found this thread!
I had similar issues with tomtom after upgrading to wm6.1, make sure your beam is turned off which should help, as it uses one od the avaliable com ports, My problem resolved by moving on to a different version of TomTom as the one i had was just so glitchy when BA was running on battery power,