Related
SYMPTOM:
Hi,
After I upgraded to Dutty's V4 and then later on to DCS's V1.5 (both are great ROMs by the way), I am having difficulties using iNavigator (iGuidance) on my Tilt.
Symptom:
When I start driving, the location on the map does not update as I go. It ONLY updates the second that it enters full screen or exits from full screen (i.e. I click on the screen when it's in full screen mode).
The COM port is set to COM4 and Baudrate is 57600. Is it because iNavigator is not fully compatible with this ROM or radio?
BR...
Click to expand...
Click to collapse
SOLUTION:
http://forum.xda-developers.com/showpost.php?p=2114969&postcount=25
http://forum.xda-developers.com/showpost.php?p=2120352&postcount=35
http://forum.xda-developers.com/showpost.php?p=2114969&postcount=40
Click to expand...
Click to collapse
I had this as well with Sleuth's v3 (WM6.1) rom as well, I went back to Sleuth's v1.2 (WM6) and all is good again with iGuidance.
vip_snoopy said:
Hi,
After I upgraded to Dutty's V4 and then later on to DCS's V1.5 (both are great ROMs by the way), I am having difficulties using iNavigator (iGuidance) on my Tilt.
Symptom:
When I start driving, the location on the map does not update as I go. It ONLY updates the second that it enters full screen or exits from full screen (i.e. I click on the screen when it's in full screen mode).
The COM port is set to COM4 and Baudrate is 57600. Is it because iNavigator is not fully compatible with this ROM or radio?
BR...
Click to expand...
Click to collapse
My Tilt with DCS's 1.5 cannot run iGuidance 4 totally.
vip_snoopy said:
Hi,
After I upgraded to Dutty's V4 and then later on to DCS's V1.5 (both are great ROMs by the way), I am having difficulties using iNavigator (iGuidance) on my Tilt.
Symptom:
When I start driving, the location on the map does not update as I go. It ONLY updates the second that it enters full screen or exits from full screen (i.e. I click on the screen when it's in full screen mode).
The COM port is set to COM4 and Baudrate is 57600. Is it because iNavigator is not fully compatible with this ROM or radio?
BR...
Click to expand...
Click to collapse
Try baud rate at 4800. See if that helps.
I think v4 is far inferior to v3. I have both and v4 is uninstalled. No map generation and compatibility problems.
J
I've found v4 to be OK on Hermes and Kaiser with WM6.0. I've played with baud and it doesn't matter, from 4800-38400 same refresh rate seen.
so, set it to 4800? will try tomorrow when I drive
vip_snoopy:
Don't bother. It won't help. It has something to do with the internal GPS on the Kaiser and WM 6.1 that iGuidance 4 doesn't like. I had the same issue as you (and others). As a test, I paired my bluetooth GPS to the phone and iG4 worked great.
However, other GPS based software (ie Live Search) works fine in WM 6.1.
I cooked my own ROM from Alex's 3.02 package...
shadee
slimshadee said:
vip_snoopy:
Don't bother. It won't help. It has something to do with the internal GPS on the Kaiser and WM 6.1 that iGuidance 4 doesn't like. I had the same issue as you (and others). As a test, I paired my bluetooth GPS to the phone and iG4 worked great.
However, other GPS based software (ie Live Search) works fine in WM 6.1.
I cooked my own ROM from Alex's 3.02 package...
shadee
Click to expand...
Click to collapse
so you said you cooked your own ROM from Alex's 3.02 package, is that WM6.1? could you provide some more details about it?
Yes. 3.02.405.0 ROM base (WM 6.1). It is Alex's v5 Kitchen.
I just got iG4, so I never tested it with any of the ROMS I cooked from WM 6.0. I did however, use iG3.01 sucessfully on all of those WM6.0 ROMs.
I was fortunate to have a bluetooth GPS from my old Hermes and Wizard PPC's, and used it to confirm the problem with iG4 / WM6.1 (3.02 ROM) was related to the internal GPS on the Tilt / Kaiser. iG4 works like a champ with the BT GPS, but craps out constantly when using the built-in GPS.
IMO, the built-in GPS is significantly inferior to a paired BT GPS.
And, BTW, iG4 is slower than iG3.01, probably because of the added POI's and the fact the entire map must be loaded on your storage card. I really miss the maploader program from version 3.
Get a BT GPS and enjoy iG4...it's still the best nav software in my book.
shadee
My two cents worth... I have Handymap (South African Version of Papago) and it also was very sluggish, used to update every 300m or so when going at 100kmph. I complained to the vendor, and since then they have released a cab install specifically for the Tytn II.
So it seems to me that the way the internal GPS chats to the software is different than the way an external BT GPS does.
Just to get this thread back on track and see if anyone can help us find a solution. I am also having the same issues that you describe with iGuidance 4. I am able to get a satellite lock quickly, but while driving, the map does not refresh or update unless you tap the screen. The interesting thing about this problem is that the same version iGuidance works incredibly when using a WM6 rom. This problem only occurs when using WM6.1. Additionally, using the 6.1 rom only seems to impact iGuidance and not TomTom.
I did some research on other devices and saw that some people had success using Franson GPSGate, but I am looking for a solution that doesn't require it as it was not required in wm6.
Please do not turn this thread into a debate over which gps application is better or which version of iGuidance is better. Any suggestions as to what may solve this issue would be appreciated.
I found two issued with iG4 and WM6.1
1 - the map gets a fix but doesn't update unless the screen is touched
2 - the TTS in iG4 uses "canned" speech for most commands, and TTS to just say the street names. With 6.1, the TTS engine seems disabled as well.
3 - Just an FYI, there is a reg setting to force iG4 to only use canned speech like the previous versions like iG3 which does speed up the prog. You can also force full TTS which slows the prog more, so the current hi-brid method is a performance balance.
If GPS Gate fixes this, I'd be OK with that for now till a better fix comes along. Anyone have solid information about this? I'm on Sleuth's v1.2 WM6 rom till then, which is a solid rom, snappier than the stock Kaiser which was very good.
My experience with tech support with iNav will be that they will deny the existance of WM6.1 and any issues, then fix it in the next release. That's what they've done year over year. But I still love the prog.
slimshadee said:
Yes. 3.02.405.0 ROM base (WM 6.1). It is Alex's v5 Kitchen.
I just got iG4, so I never tested it with any of the ROMS I cooked from WM 6.0. I did however, use iG3.01 sucessfully on all of those WM6.0 ROMs.
I was fortunate to have a bluetooth GPS from my old Hermes and Wizard PPC's, and used it to confirm the problem with iG4 / WM6.1 (3.02 ROM) was related to the internal GPS on the Tilt / Kaiser. iG4 works like a champ with the BT GPS, but craps out constantly when using the built-in GPS.
IMO, the built-in GPS is significantly inferior to a paired BT GPS.
And, BTW, iG4 is slower than iG3.01, probably because of the added POI's and the fact the entire map must be loaded on your storage card. I really miss the maploader program from version 3.
Get a BT GPS and enjoy iG4...it's still the best nav software in my book.
shadee
Click to expand...
Click to collapse
well, although I do have a BT GPS, I'm just lazy to carry another one around since I have an "Internal GPS" for the Tilt. So for the meantime I'll be using TomTom until someone figures how it works out. - Hopefully by then iGuidance 5 will be out
I have seen this as an issue as well...But i actually saw it in one of Dutty's WM6.0 ROMs. I then updated to Schaps 6.0 rom and the problem went away. I've since installed only one WM6.1 rom, the udK 7.0 R1 Vega - WWE | WM6.1 CE OS 5.2.19199 (Build 19199.1.0.0). I was going to try a different rom, but i'm not sure that it will solve my issue after reading this thread.
Rom Doesn't Matter
I've had this exact problem ever since the first cooked WM6.1 ROMs have been made available. I have tried every radio and almost every WM6.1 ROM and all have the exact same problem as mentioned in this thread.
But a Bluetooth GPS reciever does work so I'm just going to go with that for now since I only use GPS in my car anyway.
Also I registered my program with iNav and there are no updates to the software yet. opefully when there is it will fix the problem.
temporary work around
Ok, I've given up searching for now and believe that the only solution is to use GPSGate as discussed in this post
http://forum.xda-developers.com/showpost.php?p=1862272&postcount=4
GPSGate is not free, but there are alternatives to it out there that haven't been tested yet. I did download the trial of GPSGate and can verify that it does work. It's not too expensive either for just the ppc license.
To use the mortscript script that is discussed in this thread, you do also need to download AstroGPSLauncher which can be found here:
http://forum.xda-developers.com/showpost.php?p=1870976&postcount=1
It seems as if we are stuck with this until iGuidance can resolve it. The more users that contact them, the better chance we have of getting a fix. However since 6.1 isn't officially released yet, they will more than likely deny the issue.
Heres what iNav support had to say in response to my e-mail
I don't think any of these options will fix the 6.1 compatibility issue...what do you all think?
MY SUPPORT REQUEST...
Hello,
I have Windows Mobile 6.1 on my AT&T Tilt Pocket PC. iGuidance recognizes my internal GPS, but does not automatically refresh the screen. I have to zoom in/out or change something with the screen to get it to refresh. Do you know how I can fix this problem?
THEIR RESPONSE...
There are several possibilities:
1) GPS connection issue : the program is not connected to your GPS and thus unable to update your current position. If it's connected, the arrow/cursor in iGuidance map screen should be in yellow or green. And when you click on view > gpsinfo, you should see the screen w/ NMEA data being updated continuously. If the cursor continues to stay at grey color, this means iGuidance has not been connected to your GPS. If the cursor is red, then this means it has found your GPS but is in the process of locking and searching for satellite signals. The GPS connection indicator information can be found under Section IX step #6 of the iGuidance Installation Guide, and the step-by-step instruction on how to configure and connect iGuidance to your GPS is available under Section VIII step #4 of your iGuidance Installation Guide.
2) Normal program operation: whenever you've just entered an address and click on "nav", the program will automatically enable panning mode. You will need to click on the "X" button at the lower right hand corner to exit the panning mode to see the screen refresh. If you don't manually exit, it will self auto-exit after 40-45 seconds. So if you didn't know how to operate the program and didn't wait for 40-45 seconds, it's likely you will think that the screen is not updating.
3) Program installation: it is also possible that some files were corrupted during installation. You might want to following the uninstall/reinstall instruction in Section II of your iGuidance Installation Guide and reinstall the PPC version.
Tilt is the most popular pocket pc phone used by our customers, so there's no compatibility issue w/ the hardware nor the internal GPS. Most likely, scenario #2 or 3 is the problem.
Has anyone figured out how to get iGuidance 4.0 to work on Windows Mobile 6.1 without spending more money? I know about the GPS Gate trick, but would rather not spend another $20 when iGuidance worked flawlessly by itself on WM6.0.
afgoody said:
Has anyone figured out how to get iGuidance 4.0 to work on Windows Mobile 6.1 without spending more money? I know about the GPS Gate trick, but would rather not spend another $20 when iGuidance worked flawlessly by itself on WM6.0.
Click to expand...
Click to collapse
If you click on my link from two posts above, you'll see that they mention a free alternative called GPSProxy
Hi, i work everyday yesterday and today trying to make the destinator 6 work,
I use the duttýs feb.08 rom and radio i also try a lot, i am using now, the 1.58.21.23 NIKI
The problem is i can found the Gps port with destination configurations on COM4, 115200 , NMEA but WHEN I PUT IN THE SCREEN TO FIND THE GPS POSITIONS, I READ A MESSAGE " GPS ANTENNA NOT FOUND"
I only make it work emulating the gps position with FRASON GPSGATE .
I think the problem is the time or delay of antennas, what ca i do?
NOTE: AFTER A DESINSTALL THE FRASON GPS GATE I DO A HARD RESET.
tHANKS
FLAVIO MARTINS
SAO PAULO-SP
BRAZIL
any news?
Anyone have any news?
Flavio,
I installed destinator 6.1 and I'm having the same problem. It finds the GPs and keep changing from " GPS Antenna found" and "GPS Antenna not found" in each 2 seconds.
Is it the same problem that you are having?
I'm using Confused Stu's Windows Vista 1.3 Cooked Rom with Radio Ver 1.65.14.06 and Destinator 6 works perfectly
C
I'm using Dutty's WM6.1 Hybrid v2 5.2.19716/5.2.19700
Destinator 7 work fine (downloaded a trial version) but id doesn`t have the language that I need, so I rather use Destinator 6.
Tried several versions of this ROM (Cube, no Cube and lite) and in everyone the same thing happens: It keep changing from "GPS Antenna found" "GPS Antenna nof found" every 3 seconds.
I think I gonna try one WM6.0 ROM to see if it works. I'll try Sleuth 1.2 first, than Confused Stu's Windows Vista 1.3 Cooked Rom.
Thanks
Try 6.0 NOT 6.1
Hi everyone,
This is my first post here and I would like to share my experience with the WM6.1 update and Destinator. I had been using an Asus n30 and for that to work I had to install Destinator 6.1.1 otherwise it would loose GPS etc. When I tried the same 6.1.1 update on my Kaiser (Vodafone version) with WM6.0 it worked basically but when I drove at higher speeds above 140-160 km/h (here in Germany this is quite a normal speed on the highway) the display would freeze and stop updating and I would no longer get voice instructions from Destinator.
So I had the crazy idea to update to WM6.1 to fix this...Big mistake...at first
Well as you have also found out it made things worse and I got the "GPS Antenna not Connected" issue.
I was able to solve my problem after a lot of tinkering with different radios and two ROM images one from Vodafone UK (3.28) and the last ROM posted from Dutty - which I am using now great stuff! both are WM6.1. What helped solve the problem was to revert back to Destinator 6.0 i.e. the original version from the CD-Rom that I had bought. After deleting the 6.1.1 version and installing 6.0 everything was fine no more "GPS antenna not connected" and no more freezes even when driving at over 200 km/h (130 Mph).
My guess is that the 6.1.1 update was optimized for slower devices like my n30 but the measures taken in that update that made slower PDAs work with WM3 SE were counter productive under a more modern OS like WM6.x
Even though this took me 3 days and a lot of head scratching to figure out I am very happy I did go through this process. Now thanks to this great community I have learned to flash Hard SPLs, change my ROMs as I please and as a result I have a much more powerful Kaiser . All of this despite what the lady at the Vodafone hotline told e "you can not use an update from the UK...or from HTC" ha ha .
I hope this may help some of the other users who have destinator 6 trouble.
Cheers
htpcman
Kaiser Problems
i have an htc 8900 series(its called the ATT tilt in the States, i think its called the Kaiser everywhere else) and i'm having problems with WM6 and desitnator 6. i installed it as instructed and when i try to open the program it seems like it tries to open it, but nothing happens and i get taken back to the today screen. i've even uninstalled the program and sent all the installation files from my ASUS 696 via bluetooth to my phone's card, but that didn't work either. Dest 6 works perfectly on the ASUS.
On my phone, GPS settings are Program port Com4, GPS hardware port (none), baud rate 4800. And the phone will not let me change the baud rate or the hardward port. It doesnt' save my changes. ANy help is appreciated.
Thanks
My friend and I both have Tilts running the following:
HardSPL 3.56
Death V4.1
Radio 1.58.16.24
The only difference between the two phones, is that I used the cab widely available here for TomTom and he bought a full fledged copy on DVD.
When I go to use my phone for navigation everything is choppy like so many others, but he showed me a route demo and it's smooth as the Magician in the htcclassaction.org demonstration video. I can't figure out how it's so smooth though. He's not using the "D3D drivers", either, so I'm at a loss.
His TomTom is 6.01 with 6.01 USA and Canada
Any ideas as to why / how TomTom got around the choppyness of DirectDraw?
Nothing at all?
I think this could be very important for DirectDraw and 2D acceleration if someone could figure this out
What I found when running TomTom on my Tytn II is that if you disable all the POIs from showing on the map while you are navigating then the software runs very smoothly.
If you use any speed cam warnings etc these still show up on the map as you navigate but it has no impact on the speed etc.
Let me know how that works.
Paul.
What about differences in the speeds of the SD cards? What do you have and what does he have? There have been reports that the 4GB and higher capacity cards cause Tom Tom to run slow.
how is it laggy?
Err...could this be the old Windoze analogy???
Increase of version = extra stuff to do???
Like early version just drew maps,,,new version waits for you to talk to it, checks traffic draws more items and still wants to work on same memory and processor???
you disable all the POIs from showing on the map while you are navigating then the software runs very smoothly.
Click to expand...
Click to collapse
I'm sure glad to have seen this post. I've posted on 2-3 different forums, including teh TomTom support forum here; I've Called TomTom support...all to no avail.
This fixed my problem.
how is it laggy?
Click to expand...
Click to collapse
Go in and check a dozen or so POIs to display while driving, and I suspect you'll find out. Map was jerky; I could make a turn, and be a half block down the road before it know I had turned.
I have an 8GB Sandisk MicroSDHC card and he has a 4GB Sandisk MicroSD card. I'm going to try disabling POIs, but I don't think that's it.
NerdsMcGee said:
I have an 8GB Sandisk MicroSDHC card and he has a 4GB Sandisk MicroSD card. I'm going to try disabling POIs, but I don't think that's it.
Click to expand...
Click to collapse
Disabling POIs sped up TomTom IMMENSELY. Thanks for the info.
NerdsMcGee said:
Disabling POIs sped up TomTom IMMENSELY. Thanks for the info.
Click to expand...
Click to collapse
You're welcome.
I have a 4gb micro sd card and the speed has nothing to do with the size or speed of the card.
I wonder if the video of the 2 machines on the class action lawsuit website had the Tytn II displaying all the POIs.
I think they would be a bit embarrassed if that turns out to be the case
I think the problem is just TomToms laggy software rather than the PDA
Paul.
firstandlast said:
You're welcome.
I have a 4gb micro sd card and the speed has nothing to do with the size or speed of the card.
I wonder if the video of the 2 machines on the class action lawsuit website had the Tytn II displaying all the POIs.
I think they would be a bit embarrassed if that turns out to be the case
I think the problem is just TomToms laggy software rather than the PDA
Paul.
Click to expand...
Click to collapse
I wouldn't be surprised. TomTom has always been smooth and lag-free for me, even with the stock HTC shipped ROM.
I forget which versions I've used, but I think it was:
6.02?
6.030 (or 6.032? I can't remember)
7.450 (the latest TTN7)
Well, at least video is smooth. I had sound issues with 6.030/32 and TTN7 that did not occur with the first version I used.
As you can see by my current sig (although soon to change) I'm using the latest HTC WM 6.1 ROM and 1.65.17.56 Radio with the correct 3.28.0000 SPL and I get very laggy GPS performance full-stop. It's not necessarily jerky (although on occasion where lots of movement such as going around a roundabout occurs, it can be) but it is very laggy. By this I mean I can be sitting in the train stationary and from the train starting to move and Tomtom Navigator actually registering movement/speed, it can take up to 25 seconds - and this is with a reasonable signal reception averaging 3 or more bars the whole time. I put this down to the actual GPS perfomance of the Radio module driver. Tomtoms call centre in the UK advised me that TTN Version 6.032 (the HTC official version) isn't actually supported under WM 6.1, only the original WM 6.0 O/S so guess what's happening to my TyTN II later this week at the HTC repair centre.... I'll be so pleased not to have to put up with rubbish GPS performance anymore. Next time I'll only upgrade to WM 6.1 once I get the all clear that they've fixed their WM 6.1 ROM/Radio combination.
Oh and I have tried TT 6.10 when Tomtom were first attempting to work out why their software was playing up after the WM 6.1 upgrade (they provided me with a free 'crossgrade' for faultfinding purposes) and I fould in terms of smoothness, it was identical to 6.032. I went back to 6.032 because 6.10 didn't have fully working customised things like jog button volume control, volume change screen indication and native inbuilt 'internal' GPS setting. The start menu also misbehaved or the physical Windows button on the phone wouldn't work properly when TTN was running, something like that - altogether not as 'Kaiser friendly'.
NerdsMcGee said:
Disabling POIs sped up TomTom IMMENSELY. Thanks for the info.
Click to expand...
Click to collapse
Perhaps this works with Navigon, too. Gonna try that later
I am using TTN 6.032 on the latest WM 6.1 with a maximum of POIs enabled and it runs smoothly.
I've tried a version lower than 6.032, and based on my personal experience it didn't really make a difference. As long as you turn off the POI the TT will run like crazy, and plus the lower version is not as user friendly as the 6.032, or even better V.7, that's if V.7 will accept the maps from V.6, just my 2 cents.
Flying Kiwi said:
As you can see by my current sig (although soon to change) I'm using the latest HTC WM 6.1 ROM and 1.65.17.56 Radio with the correct 3.28.0000 SPL and I get very laggy GPS performance full-stop. It's not necessarily jerky (although on occasion where lots of movement such as going around a roundabout occurs, it can be) but it is very laggy. By this I mean I can be sitting in the train stationary and from the train starting to move and Tomtom Navigator actually registering movement/speed, it can take up to 25 seconds - and this is with a reasonable signal reception averaging 3 or more bars the whole time. I put this down to the actual GPS perfomance of the Radio module driver. Tomtoms call centre in the UK advised me that TTN Version 6.032 (the HTC official version) isn't actually supported under WM 6.1, only the original WM 6.0 O/S so guess what's happening to my TyTN II later this week at the HTC repair centre.... I'll be so pleased not to have to put up with rubbish GPS performance anymore. Next time I'll only upgrade to WM 6.1 once I get the all clear that they've fixed their WM 6.1 ROM/Radio combination.
Oh and I have tried TT 6.10 when Tomtom were first attempting to work out why their software was playing up after the WM 6.1 upgrade (they provided me with a free 'crossgrade' for faultfinding purposes) and I fould in terms of smoothness, it was identical to 6.032. I went back to 6.032 because 6.10 didn't have fully working customised things like jog button volume control, volume change screen indication and native inbuilt 'internal' GPS setting. The start menu also misbehaved or the physical Windows button on the phone wouldn't work properly when TTN was running, something like that - altogether not as 'Kaiser friendly'.
Click to expand...
Click to collapse
Google "static navigation". The oddball performance at low speeds (such as lag from a stop) is not TomTom's fault. It's a setting in the GPS receiver that (unfortunately) can't be disabled on the Kaiser.
Hi,
I'm using version 7.915 of Tomtom Navigator with UK and Ireland maps. I used to have a HTC Touch that ran Tomtom 6 perfectly. However this version on my Diamond is really slow often showing junctions once i've driven past them. I'm finding the whole thing unusable.
I'm aware of the issue of GPS lag with the Diamond but the screen seems to refresh about once every two seconds. I'm running BsB's 6.5K ROM but the issue has been exctly the same regardless of ROM version.
I dont have alot of other applications installed, mainly Fring and Core Player.
Is there anyone else with this problem and if so is there a cure/solution?
Many thanks for any help with the issue.
Too many POIS activated maybe, uncheck all your POIS and try it.
There is a registry setting which sets the polling interval of the gps driver.
It's in milliseconds (1000ms = 1 s). Mine is set to 1000:
HKLM\System\CurrentControlSet\GPS Intermediate Driver\Drivers\GPSOneDevice
PollInterval = 1000
Maybe yours is too high?
On my Touch Diamond TomTom v7.910.9185 runs a lot smoother than 7.915.9196! Try it.
Thanks for the help guys. I'll try the registry entry first. I've not got any POI's apart from Speed cameras. I'll also see if I can 'find' the other version somewhere!
v7.910.9185 is the latest official version specially for Touch Diamond directly from TomTom. You can get it via TomTom Home if your installed version is lower.
installed the 9185 version and it works much better thanks, for everyone else's info the 9185 version is the official diamond one and works alot better than the other versions.
Thanks again for the help guys
Happy now!
On most ROMs I had, it was impossible to start IGO8 alone while AGPS was on. The PDA would simply freeze or never detect the GPS.
The workaround was simple however, you had to start the GPS with another software before (and staying in background).
Recently, I found this thread on Development And Hacking and I gave a try. This is a driver enhancement to fix lag. But as a side effect, it prevents IGO from freezing !
I can finally start Igo8 alone, it works great !
(results may vary depending on the ROM - I'm using TPC StockLike 23049)
yes, you are right. my igo8 now starts with a-gps on if i run VisualGPSce first. (i used advanced config to turn it off a-gps a while back)
but what does a-gps do? it was not any quicker fixing. or am i missing something?
on the page you linked, what exactly did you install? there cabs and registry fixes (sorry i am being lazy, there are 14 pages)
I've just installed the cab on the first post (v0.9) and voilà, no registry change needed (those are for fine tuning).
igo8 version?
Which igo8 version you used? I have been using a lot of different igo 8 versions and never had a problem not detecting the GPS. A-GPS asks me weeky to allow downloading the newest GPS data from internet, so I guess I am using A-GPS as well.
The GPS itself is not too quick though, my g/f's diamond locates our position every time way quicker. Will this cab you mentioned speed-up getting the fix?
I used PDA Corner ultimate x-v4 to date, just upgraded to x2-v11.
Altough QuickGPS is asking to download every now and then, that does not mean that AGPS is enabled. Most ROMs I have used (PDACorner's ROMs included) disable AGPS by default.
Any version of iGO I used would freeze with AGPS enabled, while they work with AGPS disabled.
From what I tested, the driver lag fix helps when moving slowly or not moving at all. It doesn't get a GPS fix faster. However, since it redirects GPS calls, iGO does not freeze.
AGPS can help getting fixes in a couple seconds. Diamond has no issue with iGO and AGPS.
Grrrr
Doet voor mij geen donder. Jammer
Didn't do the trick for me. Installed GPSMod 1.39 on Ultimate X-2 V11 ROM on a Tilt (TyTN II) and IGO still hangs on 'Starting'
This is using the default GPSMod Port Com1.
If someone does get this working on a TyTN II / Tilt, let me know