This is what I have found
There is a GPS v2.08 download on the TomTom website with the following statment.
"GPS version 2.08 fixes an issue in Windows Mobile 2003 running on iPAQ's where the iPAQ cannot be switched on after switching it off whilst a Bluetooth connection is open with Bluetooth GPS receivers."
I have also heard that this is a wider issue that goes beyond TomTom Navigator. It seems that it could be to do with the implementation of Bluetooth/communications in a Windows Mobile 2003 on a number of devices. My 2215 suffered some of the issues in this thread and I tried the following to at least settle it down. As far as I can tell, TomTom are the first to acknowledge and fix this problem. A problem that may not be entirely down to them to begin with, from what I am finding.
I tried a brand new install of everything while no other applications were running on the iPAQ. I installed latest version of Navigator (2.24) and GPS (2.08) from tomtom.com. I also installed by copying the CAB files to the iPAQ and running them from there and installed them in the following order: Navigator, voice then GPS. GPS last as it seems to purposely initiate a reset of the iPAQ.
What I have also read elsewhere and noticed about my Pocket PC is the following. Bluetooth under WM 2003 is too insistent on proactively activating associations between the Pocket PC and other communication devices. If you use software configured to access a com port used by a Bluetooth association the BT manager in the system will insist on opening that port, whether you want it to or not. This happens even if you've turned the radio off on the Windows Mobile device. What’s more, I can’t find any setting within the Bluetooth Manager or BT Settings that allows me the user to switch off or override this automatic element of Bluetooth.
|