I had been using iGuidance4 on my old Samsung i730 off a 4GB SD Card. It worked very well . I used it syncing with a BT iTrekM5+ BT GPS Receiver (MTK Chipset) in my wife's car and with a Parrot 3400 LS-GPS (it is an intergrated Hands free BT and GPS receiver).

I have recently upgraded my phone to a HTC Touch Cruise and am using iGuidance4 now on a 6GB MicroSDHC card. It works flawlessly with my Parrot and iTrek Receivers.

The problem that I am having is that iGuidance4 is barely working with the Touch Cruise inbuilt GPS. The phone runs on a Qualcomm MSM7200 (Chipset) @ 400MHz,and has bulit in GPS. The iGuidance program works in fits and starts with a very, very long lag time, so as to render the program unusable.

I thought that there may be a problem with the intergrated GPS on the phone, but I don't think that this is the case, because the inbult intergrated GPS of the Touch Cruise works perfectly eith both Google Maps and Microsoft Live Search.

I wonder if anyone might have any thoughts
or suggestions on this problem.

I will also post this on the XDA Developers
site.(iGuidance 4 Problem on HTC Touch Cruise/Polaris - xda-developers)

Thanks

Turnip

pardon the question and lack of help as I have no idea how to help you other then to suggest perhaps because iGuidance is such a large program, the microsd card is the bottleneck.

My question is: you have your carrier listed as verizon, but I assume u switched to AT&T because I don't believe there is a CDMA version of the Touch Cruise out yet (or I missed something really big.)

I was also under the impression that the HTC Touch Cruise had a built in real gps, not agps. Now I'm not so sure. Anyone know? Is agps good enough to replace a bluetooth gps?

Perhaps you should test your 6gb microsdhc read speeds? Get a faster 2 gig card for maps etc? There was always a slight pause when I opened up iGuidance on my 6700 but nothing annoyingly long.

Thank you for the reply.

Yes, indeed, I did change from Verizon to AT&T.

The Touch Cruise has a real built-in GPS (I'm not sure if it is intergrated into the Qualcom MSM7200 chipset or a seperate SiRF StarIII Chipset).

I had also thought that perhaps the problem was the microSDHC card, but the program works great with the externel BT GPS receivers in both my wife's and my cars.

so you're saying the internal gps works great with Google and Live Search, and iGuidance works great with bluetooth gps units? That basically tells us that we have no idea what's going on.

Perhaps you need to be at a different baud rate, or iGuidance just needs some tweaking for the internal hardware and we're stuck till someone hacks it or there is an official update. If I had an touch cruise to play with I'd try iguidance on it for you.

Can you set iguidance to work directly with the internal gps instead of using the 'windows gps' settings to communicate between the two? (the 6700 could have a registry hack that would enable the gps menu which would sorta act as a proxy between the two, or you could just manually set your settings in the program and with the bluetooth gps)

Thanks for the reply.

Yes you are correct in thinking that I have very little idea as to what is going on.

The internal GPS works perfectly with Google Maps and Windows Live Search.

On iGuidance one can manually choose which com port to use for the GPS connection.

I have set the Parrot to COM1, the iTrek M5+ to COM8 and the Touch Cruise internal GPS to COM4 (I also set it to COM4 in the WM6 GPS Setting app)

I had not thought to change the BAUD rate for the COM4 connection - That is a good suggestion and I will try it out shortly.

I have included a reply that I just now received from iGuidance Tech Support:

Hi Turnip:
It's possible that it's designed to only work w/ Tom Tom which is the integrated and pre-installed gps software. It may work still w/ Google & MS LiveSearch since these 2 programs don't provide voice iguidanc nor dynamic reroute feature and thus don't require all the GPS sentence and data as full version of gps software does. On the other hand, you mentioned the program takes a long time to launch, so this may be a program conflict issue w/ your data connection and NOT a gps connection issue. If this is the case, then you are probably on ATT network as this conflict only occurs w/ ATT MediaNet. If you are able to select any other gprs setting other than ATT MediaNet (ex. Cingular GRPS), then there won't be any conflict. Withouth changing the gprs setting, the only other way to go around this issue is to make sure you launch iGuidance 1st BEFORE your gprs setting on your HTC phone is enabled.

Thank you.
Support Team


Thanks once again.

Well I tried different BAUD Rates - unfortunately no difference.

I have now changed the instalation from the main memory to my SDHC storage card - Ill try this out shortly.

T

that's the problem of inav not working well w/ MS intermediate GPS API.

Solutions for similar problems with iGuidance on the Titan are here:
http://pdaphonehome.com/forums/ppc-6...w-refresh.html

The solutions may also work with the Touch Cruise.

I'm having the same problem as you. For me, it doesn't take long for iGuidance to load or for it to lock on the the satellite. The problem is that it doesn't correctly track my location. Ie, with the GPS locked on, my car can be moving but the iG doesn't recognize that. Or, it mistakes me to be on a different road.

I know the problem is not with Touch Cruise as it works perfectly with Garmin Mobile XT and iGo.

A friend of mine runs iG on TyTN II, and it works perfectly for him.

For anyone using my iGuidance with the Internal GPS, I updated my internal GPS autolauncher script, you can get a new version here:

PPCGeeks - View Single Post - Official Titan built-in GPS Thread

This makes the entire AstroGPSLauncher/GPSgate/Shortcut process much easier/smoother. As a bonus it skips the iGuidance warning screen, and temporarily turns off the backlight/power timeouts while iGuidance is running.

This solution work great on the Titan. Let me know if this solution, or part of this solution (you may not need AstroGPSLauncher), also works on the Polaris.

I've got iguidance 4, did you know there is a 4.02 update on their web page? The damn thing runs fine on my old tmobile mda but tmobile has soooooo much garbage on the wing it doesn't have enough memory to run. I put iguidance on my old toshib e805 running pc2003 se with a sirf IIe chipset (two different cf gps units) and the one barely even runs and the pocket xtrak does what you describe, herky jerky can't seem to keep a signal fix. Both these gps units worked fine the last time I used them I believe it's the iguidance that's not handling the chips in the gps units properly. I ordered a sirf III cf unit will be here in a couple of days (tried to get bluetooth on the toshiba but no one seems to sell the adapter anymore so that seems to be out), it sounds to me like iguidance doesn't work with anything but new gps units I'll know in a few days when the new one arrives. Iguidance tells me they no longer support pc2003 so I had to manually move the installer to the pda and install from the sd card (so you don't support it but you still have the executable? These guys sound like idiots). I really don't want to lay out 4 hundred bucks for a standalone navigation unit but it sounds like the pda support is next to dead....I found it interesting that microsoft has told all the pda makers they'd give them licenses to upgrade ppc on old pdas but that still requires companies like dell and toshiba to get off their hineys and put it out and I'm pretty sure that won't ever happen unless they have a riot on their hands. I love my e805 for it's day it was a fantastic machine and still is but it needs mobile 5/6 so it can run software like the gps package properly.