yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze General] maw:
Okay I tested it at poll interval 2500, I got good results on speeds higher than 50 km/h almost no lag, but at slower speeds the position lag doubled. So then I tested at 1500, lag improved quite a bit but not yet perfect, but almost no visible positional lag. So I reduced it now to 1250. I haven't yet tested it as yet. I hope that this interval will be perfect. I think the settings posted in the first post are really meant for the best results in pedestrian mode. At least that is what I think because at 250 it is perfect for low speeds, no positional lag, speed lag 4-5 seconds. But at high speeds high positional AND speed lag. So I'm guessing 1250 is better.... Will test it out tomorrow morning when I go to work. Not leaving the house tonight... too much ice on the road and its going to be -21 C tonight....
[Touch Pro, Fuze General] licht77:
Hi guys, hi Sleuth!

i am kinda stuck at this point with my GPS... (see http://xdaforums.com/showthread.php?t=466908 and / or http://wiki.xda-developers.com/index.php?pagename=GPS Issues )

I use Romeos 1.51 GER (where several users attested that their GPS is working flawlessy) and the same Radio like u (BS 1.10.25.25). Although i tried several other RadioRoms too.

I played with this hint ( http://xdaforums.com/showthread.php?t=427888 ) as well as this ( http://xdaforums.com/showpost.php?p=2894542&postcount=1 ).

Within Romeos, there is no flag=2. I played with GPSGate too - but no constant fix possible.

With the latest config, i managed to get somekind of fix within 5-10min, but it stalls after approx. 1 or 2 seconds. Just like a flashlight, the Satellites jump to green and back to red (3d fix -> no fix -> 3d fix -> no fix etc.). Tried with HTC GPS Tools, GPStest and VisualGPS.

On a short trip with the car it worked "somehow" for 5mins or so (although laggy and jumpy positions) but when traveling faster than 100 km/h the connection is lost (so i dont need to talk about 160 or faster *g*).

I stopped and started GPSGate in order to stop that on/off behaviour... but up from that point there is no GPS fix anymore.

So - before i kick that device away i am graceful for each hint...
[Touch Pro, Fuze General] maw:
Install this program on your internal storage and it will go away. Although it says lag fix, it doesn't fix the lag, it will however fix the problem with the GPS switching on and off, the problem you are having now.

Installeer dit programmaatje op je interne geheugen en het zal jouw probleem oplossen met het aan en uit knipperen van jouw GPS ontvanger. Het repareert, ondanks de naam, niet de "lag"!
[Touch Pro, Fuze General] licht77:
Ill give it a try... what exactly does this tool do? Which registry settings are changed?
[Touch Pro, Fuze General] maw:
I don't really know what it changes. But I had this problem also with the GPS switching on and off the whole time and when I installed this the problem went away! So give it a try....
[Touch Pro, Fuze General] licht77:
Ah ok... the cab contains all the fixes here from omega01: http://xdaforums.com/showthread.php?t=427888

Already applied this manually - but ill give it a shot!
[Touch Pro, Fuze General] Sleuth255:
It's usually having AGPS turned on that causes the problem you describe.
[Touch Pro, Fuze General] maw:
Well... AGPS is turned off, don't know who you posed the question to... Anyway, the cab file fixes the problem so I guess it works. Did you try changing the poll interval and check what effect it has?
[Touch Pro, Fuze General] Sleuth255:
I've not had any reason to change the poll value from 250 actually. I will play with this but I'm more focused on getting the video out to everybody atm. My first run over lunchtime was a bust b/c the camera just shows glare on the two screens during the day. I have a newer "Rightlight technology" logitech cam I want to try and I'll also do a night run which will eliminate the glare but will make it harder to show the car's actual position when crossing side streets. I'll want to do a freeway run as well since it seems that lag gets worse at higher speeds. It should really make any differences between the Tilt and the Fuze much more pronounced if lag does change in this manner. Too bad I have a day job and won't be able to try again for another 2-3 hours... Kinda tough in a recession to explain driving around shooting TomTom on various HTC devices during work hours.

Of course, if they fire me, all I have to do is go to AT&T's mobile devices division and tell them I'm a mod over at XDA. That'll either land me a job or put me in the slammer.... either way its food and a roof over my head :)
[Touch Pro, Fuze General] maw:
Well just be careful and indeed it ain't worth losing your job over it! Besides ATT mobile division you can try land a job with HTC or Qualcomm LOL :) I do think it also has something to do with the polling interval though, I will test it in the morning while driving to work, its 20:40 here at the moment. I just hope it doesn't snow again tonight, the weather here is terrible at the moment! We have an easterly wind blowing subzero temperatures out of Siberia across Europe.... so I'm not going outside if I don't really have to, -21 C is too damn cold!
[Touch Pro, Fuze General] AllTheWay:
Really? That's all it takes? Why didn't I try that sooner? BTW I was looking at your signature and noticed the 1.20.25.25 blackstone radio. Do you have a link for that radio? All I have seen is the 1.10.25.25 radio.
[Touch Pro, Fuze General] Sleuth255:
fat fingered it.... DOH!
[Touch Pro, Fuze General] tr72:
touch pro gps lag problem

hi everyone,

i had the same problem and test a lot of solution. For me the big problem was the fix wich was very long or which never come.

Now my tp works nice with this changement :

- first i change the radio with the 1.02.25.28 (hardspl needed first, no phone or connection problem with this radio)

- i set my gps on 38400 bauds (i did it with gpstest to be sure that the setting stays on 38400)

- agps enabled (i have unlimited data)

- with diamond tweak i put the logfile to 0 (that was tghe setting of a blackstone wich has a very quick fix)

With this setting i now always have a fix in a minute.

Some people use gpstoday, like that they can open the gps everytime to have a quick fix when they launch ggogle map or tomtom... Good for gps but bad for batterie. With the settings I huse I didn't need it.

hope can help someone

tr72
[Touch Pro, Fuze General] mindfrost82:
I'm experiencing the speed lag as mentioned earlier by sleuth and maw.

I'm using the 1.10.25.25 Blackstone radio with the tweaks on the first page and different PollIntervals.

I tried 1250 last night as maw suggested and still noticed it at 50mph. At 30mph it was right on, but once I got to 50+ it started to lag by about a second or so.

1250 is better than it was at 100 or 250, with the lower settings I was getting lag even at 30mph.
[Touch Pro, Fuze General] maw:
Hi Mindfrost

I tried 1250 as well and it improved the lag, but not yet perfect. So I lowered it now to 900. I will see what difference it makes after work, otherwise I will put it back to default 1000. I think the settings in post 1 work only with pedestrian mode but for motorized transport it is terrible. The higher (faster) the polling interval, like 250 (0.25 sec) or 100 (0.1 sec), will force the position to advance while walking, but since you are walking maybe 3 to 4 km/h it has time to adjust your position in the navigation. But if you are travelling in a car at 50 km/h and faster it just can't update it that fast! So by polling at a lower (slower) setting, default 1000 (1 sec) or maybe 900 (0.9 sec) it will adjust to the speed of the car. I will test on the way back home and see what poll interval 900 will do. If it is spot on then I can make some conclusions this evening....

The most perfect solution would be an automatic polling interval feature that will automatically adjust to the speed you are moving thereby assuring that your position is acurately being adjusted in the navigation. Is such a thing possible??
[Touch Pro, Fuze General] Sleuth255:
@mindfrost82: Could you be referring to "position lag" instead of "speed lag"? I say this because you mention it happening at 50mph. Speed lag is a variance of the displayed navigator speed to the displayed speedometer speed and is best noticed right after you stop your vehicle. Position lag is a variance of the displayed navigator position to your vehicle's actual position and is best noticed when driving at a constant rate by noting side streets or other landmarks.
[Touch Pro, Fuze General] mindfrost82:
I guess I have both, but as you stated in your previous post, its not enough to make it unusable for me.

For speed lag, when I come to a stop it'll take 1-2 seconds for iGo to show me at 0mph, which is fine with me. I think my Tilt did the same thing.

For the position lag, it seems to get worse at faster speeds, which is why I referred to it as speed lag. If I'm going 20-30 mph it is almost dead on when I cross a street. I can be crossing a street and look at the screen and it'll show me crossing it too. When I get up past 40mph, then its about 1-2 seconds behind. I'll be completely past the street then look at the screen and it'll show me passing it a second later.

I don't really remember how my Tilt was with position lag, and I might do a test like your's just to see. I know when I used Garmin on my Tilt, it was just as accurate as a Garmin Nuvi. I took a 600+ mile trip with a Nuvi and Garmin running on my Tilt side-by-side and the voice prompts were almost identical in timing.
[Touch Pro, Fuze General] mindfrost82:
How can you tell if we have a newer version or an older one? Would a serial number help? I'm curious to see if I have an older one or newer one.
[Touch Pro, Fuze General] Sleuth255:
Just look under your battery for the first 3 digits of the serial number. This is the revision number of your device. You can use it to tell how old it is. Mine's in my sig.
[Touch Pro, Fuze General] Black1982:
I think you are right about this! It would be great if such an app could be made to see if it improves the lag! I still dont think "the lag" has anything to do with faulty hardware!

Mazzel
[Touch Pro, Fuze General] btprice2001:
For what it's worth, my Fuze is a HT843, and I am seeing the position lag.
[Touch Pro, Fuze General] mindfrost82:
Mine is HT844
[Touch Pro, Fuze General] Sleuth255:
Easy test: load my ROM/Radio config and run TomTom. Got lag?

As you can see in the video, I have no positional lag so it is possible to configure a raphael to eliminate this. We haven't ruled out hardware yet though. To do this we must load ROM/software from a known good device on proven laggy device or ROM/software from a known laggy device on a proven good device.

Navigation software may play a role here as well. I have not tested iGO but other's have reported the same positional lag issues between tomtom and iGO.
[Touch Pro, Fuze General] Sleuth255:
:eek: the perfect case! You are running damn near the same config as me already. Do you use TomTom navigator?
[Touch Pro, Fuze General] btprice2001:
Are you sure about this? Why would position indication have changed? Obviously if I assume that my position is indicated by the leading point of the arrow, the difference between the indicated position and my actual position would be less. If this is the case, maybe this is why some people are thinking they have more of a lag, ie they're thinking their position should be the center of the arrow. I feel like this isn't the case though; I haven't had a chance to watch your Youtube video yet, but when I turn corners it would seem that my position is indicated still by the center of the arrow but with the position lag. Turning corners is when my position lag is most noticeable/annoying. What do you find when you turn corners? Does your Youtube video show any corners?

Thanks for all of your efforts in looking into this matter. Hopefully there's a solution for all of us!

[Edit] Sorry I didn't see your post. Yes, I am running Tomtom 910.9185.
[Touch Pro, Fuze General] Sleuth255:
Watch it please. It shows everything.
[Touch Pro, Fuze General] maw:
Okay I tested at 900 poll interval, lag was almost gone, now I changed it back to default, almost perfect! So I can conclude the following by trying out all these different polling...

If you are going walking and need navigation, change the poll interval to 100 or 250.

If you are going biking and need navigation, change the poll interval to 500

If you are going with a car, leave the poll interval at default (1000) for best results!

Increasing the poll interval any higher will result in more speed lag but better positional lag.

I think if they came up with an automatic poll interval changer that would adjust to the speed you are going then you would have near perfect results in any scenario. Maybe something the developers can work on...

Going to look at Sleuth's video now!
[Touch Pro, Fuze General] btprice2001:
@Sleuth, watched it. Thanks for doing that btw. When going straight, your position appears to be dead nuts on with the Tilt with no lag in crossing intersections. I don't see any indication even of a difference in position indication between the leading point or center of the arrow. I definitely see more of a position lag then that on my Fuze. (I wish I had kept my Tytn II to make the same comparison you did:o)

As I mentioned before, my position lag is more problematic when making turns. I do see an example in your video that illustrates what I always see; it's the right turn at 2:40. While not as pronounced as what I see on my Fuze, I would consider this an example of position lag. What do you think?

@maw, sorry, what program are you running for these comparisons? Your findings seem interesting.
[Touch Pro, Fuze General] Sleuth255:
That would be the right turn onto davidson road. My thinking is that its speed lag that causes it. I think this way because the car overshoots the position because speed is too high and Tomtom is using both speed and position to plot. As the position changes, TomTom "snaps" the indicator back onto davidson road.

This might also be TomTom 7 related. I'll have to go back and check but I believe that when I originally ran the test with TomTom 6 loaded on both devices I didn't see that issue nearly as pronounced. It might have something to do with VGA refresh as well (4X as many pixels to update).
[Touch Pro, Fuze General] btprice2001:
So you're able to load Tomtom 6 on your Fuze? When I tried to install with the cab I had used on my Tytn II, I got a not intended for device type error.
[Touch Pro, Fuze General] Sleuth255:
Yeah, I had no problems. I believe I have the cab in my v3.0 sleuth kaiser rom (click my sig to link).
[Touch Pro, Fuze General] maw:
I'm using iGO8 version 8.3.2. TT7 is not as acurate as iGO8 and I find the lag within acceptable range as well. In TT7 the lag is too much!

Sleuth, thanks for the wonderful video you made! Consider yourself blessed that you don't have the problems some of are encountering! I did however seem some lagging on the Fuze but like you say, it could be caused by the VGA refreshing.
[Touch Pro, Fuze General] Flying Kiwi:
Achieving optimal GPS on the Kaiser

Thanks for taking the time to produce this video comparison. I do like the sound of that car but I'm surprised it's a manual transmission in America - that must be a rarity. You're running the same TTN version I'm using with my TyTN II but I found running it on the HTC WWE Windows Mobile 6.1 ROM (with the HTC official 1.65.17.56 Radio) resulted in weak (and fluctuating at low speeds) signal reception. The other GPS problem I had was it took ages to get a fix - a matter of several minutes when moving, sometimes still with no fix after 10 mins and at least one minute when still from cold). Since my TyTN II was reverted back to WM 6.0 the GPS is once again excellent. The only problem (and it's a biggie) is that there are no newer maps for TTN 6 and the 'latest' one that I have is very much outdated.

These days stationary fixes from cold out in the open are consistently around 20 ~ 25 seconds and from warm (ie having already run Tomtom at some stage since the PPC had booted) about 4 or 5 seconds (both timed from when the driver has fully loaded and Tomtom starts trying to get the satelite lock). If you want to get even better GPS performance from your Tilt and you haven't already done so, perhaps a WM 6.0 ROM/Radio may offer that - at least if HTCs efforts for devices over this side of the ditch are anything to go by. Turning off POIs on both devices for future video tests will also ensure a fairer comparison. I realise most people are going to want to use 'the latest and greatest' ROMs (many people will imagine the two go together) but I'm just suggesting these ideas as ways to maximise the differences between the Kaiser and Raphael for testing/video 'evidence' purposes.
[Touch Pro, Fuze General] Sleuth255:
Yeah the BMW dealer was all smiles when I ordered it with a manual transmission. Most Americans are more interested in good cup holders than a true driving experience it would seem :rolleyes:

Anyhoo.... one more test to go and we should be able to tell what's causing this.
[Touch Pro, Fuze General] Sleuth255:
@btprice2001:

Let me make sure that I've got your device correct:

AT&T Fuze SN HT843

Da_G 2.03-MSVC

Stock AT&T radio v1.02.25.32

TomTom v7.910.9185

You have position lag that's worse than whats shown in my clip

Try this: change PollInterval to 250 in HKLM\System\CurrentControlSet\GPS Intermediate Driver\Drivers\GPSOneDevice

Still have more Position lag than the Video?

I'm going to say that this is the test here. You have almost my exact config and the exceptions shouldn't affect results because of the following points:

I never experienced positional lag with any radio I tested and yours, (1.02.25.32) is almost a dead ringer for the one I was using the most (1.02.25.28). My testing seemed to show that radios affect lock time and overall signal strength but had no effect on lag. So your radio is a wash IMHO.

You are runining the same ROM as me. Da_G already incorporates most of the tweaks I use with the exception of PollInterval above.

I never experienced positional lag with either TomTom version I tested with. It's reasonable to assume that your newer version of TomTom 7 wouldn't introduce lag either.

Let me know what you uncover with the PollInterval change!

edit: I know this is asking a lot for the community, but if you do have more positional lag would it be possible to create a YouTube showing this? Simply set up a camera as I did then say "mark" as you pass side streets. This will show us all the amount of positional lag you are encountering and at what speed.
[Touch Pro, Fuze General] kk0813:
I have the following device,

ATT FUZE

ROM: NATF v4.0

Radio 1.02.25.32

S/N: HT843

I am using Iguidance v3.01 and Copilot Live 7 and I have the exact same lag issue. I am getting the gps fix in just few seconds but while driving I can see clear lag. After seeing your video and reading your post Last night I changed PollInterval to 250 and also to (512) in HKLM\System\CurrentControlSet\GPS Intermediate Driver\Drivers\GPSOneDevice and I still have lag.

Actually I tried all the changes that was mentioned in first post

Under: HKLM\SYSTEM\CurrentControlSet\GPS Intermediate Driver\

- Drivers\GpsOneDevice\PollInterval -> 100 (default is 1000)

- Drivers\InputBufferSize -> 512 (default is 4096)

- Drivers\OutputBufferSize -> 512 (default is 4096)

- Drivers\SleepOnNoData -> 100 (default is 1000)

- Multiplexer\MaxBufferSize -> 512 (by default not present, you have to create it)

After testing this PollInteval was changed to 250. but I left every thing else as mentioned above.
[Touch Pro, Fuze General] Sleuth255:
@Flying Kiwi:

I did want to respond to some of the other points you made in your excellent post. You are correct about the WM6.1 Kaiser GPS issues. I found that my Sleuth v3.0 ROM never really suffered from warm-start acquisition issues after the first week or so. I attributed that to the validity of AGPS ephemeris data improving at the site coded into my registry.

My Tilt also hot starts in about 5 seconds and warm starts in less than 2 minutes. Anything over 2 minutes is a "Cold Start" and minimum time will be 5-10 minutes depending on how "lucky" the GPS chip is while it is randomly searching for satellites. Your comment on signal strength differences is interesting though. I didn't know that! Maybe that is why my Tilt seems to under perform in that respect.

Your point about POI settings differences is valid too. I was going to re-run with POI off on both devices but my original side by side TomTom v6 tests ran with identical POI settings as well and there were still no differences. I think that POI affects map re-draw times when there's a lot of POI positions to mark. Its also an easy test for everyone to perform: Turn off POI. Got position lag?
[Touch Pro, Fuze General] Sleuth255:
@kk0813: Evidence is mounting that Positional lag is hardware related. However, perhaps you might want to try this to help us all out:

Follow the link in my signature to my Kaiser Sleuth v3.0 ROM.

On page 1 of that thread, go to the "Recommended Goodies" section and download TomTom v6.032.8351 at the link provided. This is the free, fully functional taster edition of TomTom 6. Install on your fuze then download the test map of your area when it asks.

Fire it up and go driving!

Got Positional Lag?
[Touch Pro, Fuze General] mindfrost82:
I might try this and have my Tilt next to it. Mine isn't unusable, but you can notice it.

I have a small handheld camcorder, so if I can position the phones in a good location I can use that to do the video.

I will be using the exact same iGo8 8.3.2 on both phones with the same configuration.
[Touch Pro, Fuze General] noellenchris:
I'm also using the stock radio & tried to change the polling from 250 to 1000 and no help. I thought that the screen redraw on Garmin Mobile XT was about 1sec so polling at 1000 should sync up. It actually seemed like more lag than 250. As soon as I security unlock my radio, I will load the latest BS radio and see if it makes a difference. OliPro hasn't responded to my PM, so I will donate tonight and give it a go. My radio is ser#HT844...
[Touch Pro, Fuze General] kk0813:
Sorry I didn't find the Recommended Goodies so I installed Tomtom 7.910.9185 and the free map of my region, and went for a drive. I was driving at 40 mph and I still see lag, even at 20 mph. The pollinterval was set to 256.
[Touch Pro, Fuze General] Sleuth255:
fwiw I don't see supported evidence that a radio upgrade cures position lag yet..
[Touch Pro, Fuze General] cmloo:
Hi Sleuth255,

Sorry to be a bit off topic here. Loved your ROMs in the Tytn and TytnII. Are you going to be cooking any for the Touch Pro? Maybe we can have a chance of your clean, fast and minimal GPS lag of your TP?

Thanks
[Touch Pro, Fuze General] Sleuth255:
I would but Da_G is already pretty much doing what I would have done. I'm running his build already. Whether or not this affects position lag is undetermined atm.
[Touch Pro, Fuze General] mindfrost82:
I completely got rid of my speed lag but I still have some positional lag.

As soon as I stop now my cursor in iGo stops and as I slow down its much more accurate.

These are the settings I just tried:

InputBufferSize = 128

OutputBufferSize = 128

SleepOnNoData = 100

Multiplexer MaxBufferSize = 256

PollInterval = 1000
[Touch Pro, Fuze General] land2634:
I am on a Sprint Touch Pro and have positional lag problems. Hoping to find a solution, as I would like this to be reliable for navigation.
[Touch Pro, Fuze General] maw:
Hmmm interesting.... I read in another thread that Da_G tested this and actually came to the conclusion that changing all these settings, except the pollinterval, made no difference whatsoever because the GPSOne chip only checks the pollinterval value and doesn't check the rest. So I think that you are getting better response with the pollinterval set at 1000 rather than 250 or 100.

Read my earlier post with my conclusions regarding the pollinterval.