yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze General] Da_G:
You're supposed to be able to change it by setting the key:

[HKLM\Drivers\BuiltIn\DriverName]
"Priority256"=dword:0

But it doesn't look like the gps driver reads that key, as it reports the same priority afterward.. looking into it :)
[Touch Pro, Fuze General] Da_G:
While i'm digging around in here, gpsdriver.dll has a hardcoded fallback agps pde server of supl.agps.emome.net, maybe we can try using that and see if it feeds us valid data.. it does return to a valid ip.. haven't checked if the service is running though.
[Touch Pro, Fuze General] noellenchris:
Can we add a priority to HKLM\System\CurrentControlSet\GPS Intermediate Driver\Drivers etc.

The more I dig into the registry, the more questions I have....

There are alot of settings for the SDHC etc...I wonder if we could speed that up too. ? I'll just have to save that for another project. lol
[Touch Pro, Fuze General] Da_G:
Well, sure you could put the key there, but the program doesnt read it :(

So far I haven't seen any priority key that it reads.. :(
[Touch Pro, Fuze General] Black1982:
just my thoughts

This (the audio cue being spot on, while the display is lagging)has been reported many times. I also have this experience

My simple logic: tomtom simply can not update screen fast enough!

I can only guess at what is causing this.

(maybe something to do with the notorious drivers issue)

Posts bij Da_G, Sleuth ea seem to indicate that there is nothing wrong with

the GSP system and settings (at least to me).

Is there any solid method of testing this hypothesis?
[Touch Pro, Fuze General] Sleuth255:
The voice synchronization reports are what let me to speculate that graphic drivers are behind (at least some of) the lag issues. I need to stress "at least some of" here because I really think there's more than one position lag root cause.

Key to this is going to be folks like Kavi that load Da_G's ROM and report. Using v2.04-MSVC as a baseline for this test is also important as it will reproduce my exact configuration from a loaded ROM standpoint. Tests should be conducted with TomTom using the base ROM (disable UC by pulling your SD card) and with the GPSIDRegFix cab applied. Anyone who has noted voice synchronization should try this.
[Touch Pro, Fuze General] Ouzo:
Well, as my audio is in the right place but the image is not, I guess this makes me a candidate to try your suggestion Sleuth255.

Noob question, but will TomTom Home have a fit if I flash a new radio (I'm only on 1.02.25.28) and ROM to my device? I don't really want to have to pay for the software a second time.

Also Sleuth, my 8gig SD card is only a class 2. Would that screw up the comparison?
[Touch Pro, Fuze General] noellenchris:
Flashing your radio will not affect TT license. If you haven't Security Unlocked your radio, you can flash only the Rafael radio's. I would try the M1. If you have security unlocked your radio, flash the BS radio Sleuth is using.

Your SD card should be fine since the PDA's internal transfer rate isn't that fast. Have fun and good luck...:)
[Touch Pro, Fuze General] Ouzo:
Thanks noellenchris, I'd read about security unlocking in mskips' tutorial for noob's, but never got round to doing it as it wasn't necessary to go from stock (.19 for me) to .28. I had COMPLETELY FORGOTTEN about it too, so thanks very much indeed for reminding me :)

If I had brains I'd be dangerous ; )
[Touch Pro, Fuze General] kavi:
Sleuth,

Flashed the stock SPL and the TP is in the box ready to be returned today.

After reading rest of the thread going to Hard SPL again and go with 2.04 and M1 will report back later today.

BTW: I did try the 2.06 and M1 and the lock times were excellent but still had the lag issues.
[Touch Pro, Fuze General] Da_G:
Did some testing while driving around, running a program in the background to eat cpu cycles.. to see if the priority would be causing this issue..

With my cpu near 100% and barely able to update the screen, it was still showing the same lag behavior. :( (if priority affected it, it would get far, far worse)

Even odder, the debug log shows:

12:56:10 [D:GPS] GPS: [ProcessPollData] --- g_hStateChangeEvent Received!

========POSITION REPORT========

valid 0Xfffdfyear = 2009, mon = 1, day = 18, h = 20, min = 56, sec = 11, ms = 200

The GPS timestamp was about 300ms ahead of the phone timestamp..

what the heck? :)
[Touch Pro, Fuze General] Da_G:
It would be slightly difficult, but diagnostically useful, if we could set up the following test:

HTC GPS Tool with NMEA Logging enabled

GPSID_HTC.dll with NMEA logging enabled

debugtool with GPS position report logging enabled

that would give us 3 different sources of data - the debug log would give us the raw output from gpsdriver.dll's position report, the NMEA log from gpsid_htc would give us the output after GPSID's processing, and HTC GPS Tool would spit out the final NMEA log that the application sees.. we could sync the times up for all 3 and verify that everything's hunky dory at each point in the pipeline.. that should conclusively narrow it down to either 'graphics lag' or 'something lower level than gpsdriver.dll', at least :)
[Touch Pro, Fuze General] kavi:
Here's the test results on 2.04, M1 and regfix

1. Lag is still there, almost the same with 2.06.

2. End call (on BT) signal lost/re-lock still exists

3. Warm lock varies
[Touch Pro, Fuze General] dharvey4651:
What registry changes are these? I can make a cab file that will make all of these changes if you can provide those registry changes above.
[Touch Pro, Fuze General] NLS:
It has already been done (and more than once).
[Touch Pro, Fuze General] Sleuth255:
I've no experience with the M1 radio. I only ran it for a short time during testing for "nan" in $GPVTG. I've used .28 and blackstone .25

While I can't speak empirically to points 2 & 3, you've definitely stumped the chump on point 1. IOW, if you have the same hardware and are now running the same software from TT -> ROM -> Radio, then how can your results be different from mine :confused:

Answer has to = hardware variances or it really has to be either the 1.02.10.28 Raphael or 1.10.25.25 Blackstone radio or your baseline was somehow different from mine (ie: you ran cabs that I didn't or I ran cabs that you didn't).

The only interesting point I can see is your observation of "Voice sync" during guidance.

One thing I will be doing this afternoon is a 32 mile run from Atlanta to Norcross. For the first time, I'll be relying on my fuze for navigation while driving on a variety of roads. If there is some time related issue that makes my Fuze unusable for navigation then it'll come up then.
[Touch Pro, Fuze General] Ouzo:
This may be off topic, but I have an idea...

HTC Europe have agreed that I can send my Pro into one of their service centres. In the end this was partly due to my GPS problems, and partly the 'broken screen' corruptions and the screen showing what looks like 'snow' on an old analogue TV. As Kavi doesn't seem to have made any progress by using Da_G's ROM or the BS radio, I'm now inclined to take HTC up on their offer and see what happens.

If my phone is returned and the lag problem has gone away, would there be any way to tell if anything inside had been changed? (main board?) IE, would a 'before' and 'after' snapshot of the registry highlight anything, or would inspecting the hardware itself be the only way to tell?

I only ask because I'm wondering if there ARE hardware differences as Sleuth suggests, or perhaps if, due to some unknown problem during mass production, some of us just have partially defective phones. It does seem really weird that some of us have big lag problems and others either don't or can tune most of it away....
[Touch Pro, Fuze General] s.bonito:
@noellenchris

I couldn't find any lags you asked for. Last weekend I travelled around 2000 kilometer through germany. Only "the frames per seconds" are a little bit to less. BUT this has nothing to do with the gps-settings or the software. I use garmin mobile xt, just one time I needed to make a soft-reset. :cool:
[Touch Pro, Fuze General] kavi:
I think the lag variances are hardware related since I didn't install anything else but TT7 and regfix cab file.

Last Friday I was relying on the Fuze to get me to my destination and it really let me down, specially with the end call signal lost - just drove me nuts.
[Touch Pro, Fuze General] fourcc:
i also think that there are HW differences between TP devices.

For example, for me, BS 1.10.25.25 has produced a lot of drop calls (in fact all the calls i did) and bad GPS FIX times. I can understand that becasue as I have Orange in Spain, this radio shouldn't be so Great for me as it is for others with different operators and localization. But what about GPS FIX times, localization & operator shouldn't affect at all.

A part, i suspect another thing, there are strange behaviours using the same ROM + Radio + REG fixes. When i just flashed my Device using Proven Rom 1.12 & M1 Radio, after update QGPS just after flashing & softresetting i got cold Start GPS fixes of less than 15 seconds and warm start with 6 seconds. After some days, using the same config, i've not been able to repeat them. Now i'm at 30 seconds and 15 respectively, not bad but no so good than when just after flashing it. And i've had the same experience flashing 1.08 & also with different radios such as Experia 1.10.25.18. When trying to Fix GPS after a flashing, cold start & warm GPS fixes are always very good, after some days, they become not as good.

Weird!:confused:
[Touch Pro, Fuze General] NLS:
no so much

it probably stores something somewhere that instead of helping - messes things up
[Touch Pro, Fuze General] fourcc:
ok, maybe, but this mess is not in the usual GPS reg entries & gps drivers for sure.
[Touch Pro, Fuze General] NLS:
if this is definite - then it's a file somewhere
[Touch Pro, Fuze General] Da_G:
Sleuth255:

Don't forget, aside from software, registry settings, and radio rom, there is also NVRAM parameters.. it is quite likely that for different batches, etc, there are different NVRAM parameters in use..
[Touch Pro, Fuze General] fourcc:
ufff! too advanced for me. i'm lost :confused:
[Touch Pro, Fuze General] Da_G:
When the system first boots, in the early stages (first handful of seconds after poweron) the chipset needs to know certain things about the hardware it's attached to.. how much voltage to supply to the LCD to turn it on, for example.. in the case of the GPS there are about 20 settings related to it..

A quick google brings up this:

Our gpsOne configuration is probably pretty similar looking. These settings are stored in NVRAM (Non-Volatile RAM) and are read during bootup and operation of the device.. we need access to the radio ROM to be able to configure these settings.. i've been trying for some time now o.O
[Touch Pro, Fuze General] fourcc:
thanks for the explanation, but again, too advanced for me.

We regular XDA users are lucky for being part of a forum like this one full of "Masters" that discover such interestings things that make our Devices working better than how were released by the manufacturer. (sorry if my english is not clear enough)
[Touch Pro, Fuze General] Sleuth255:
Not forgetting but it appears that Kavi and I even share same device variant/operator.

You'd think that NVRAM changes here would be less likely unless AT&T is actively trying to discourage standalone navigator use in favor of their pay-as-you-go Navigator (which would have built in correction for the positional variance of course).

Now why would they ever want to do that I wonder :rolleyes:
[Touch Pro, Fuze General] noellenchris:
Thanks for the update. TT7 is working great for me. But it's only the free map. Garmin still lags in position. I also realized that our stand alone garmin also lags about 2 sec. Glad to hear yours is lag free...Still working on getting mine to work that way.:)
[Touch Pro, Fuze General] Da_G:
oi, this issue drives me up the wall :)

remember how before I said the gpsdriver.dll was reporting a timestamp 1 second behind the cell network, and that pointed to some lag further up in the system.. well..

14:23:27 [D:GPS] GPS: [ProcessPollData] --- g_hStateChangeEvent Received!

========POSITION REPORT========

valid 0Xfffdfyear = 2009, mon = 1, day = 19, h = 22, min = 23, sec = 29, ms = 500

now i'm getting position reports 2 seconds AHEAD of the cell system.. lol

i think i've just about exhausted options i can influence other than nvram..
[Touch Pro, Fuze General] noellenchris:
Any chance that HTC will release an updated radio ...what about the latest Quartz radio? Number wise it's the newest...
[Touch Pro, Fuze General] Neoo330:
Hi all, i dont think, that there is hardware problems on touch pro, because before i bout TP i was on Diamond an there was thesame GPS isues. BUT on some costum ROM's and what is most important thing ON ORIGNAL ROM, GPS lag was't at all for me ...

I'm using Lantis RC1, its great ROM, but TT7 lag is bad, just tried instal TT on my memory card, and now its even worst :(

Sorry, about my english :p
[Touch Pro, Fuze General] maw:
Hi all

I saw that there is a new Blackstone Radio 1.09.25.35, anyone tried it already?? I was reading the thread over at ROM development and it seems this one is even better than the BS Radio 1.10.25.25 version. Anyway, just wondering if you guys tried it out and if there are any changes that will improve the GPS reception, maybe something for Da_G and Sleuth to investigate.....
[Touch Pro, Fuze General] noellenchris:
I haven't tried it yet, there is also the new Quartz and the number is even newer than the BS ones. I'm really close to just trying the quartz to see if HTC has made any NVRam changes.....hmm...:confused:
[Touch Pro, Fuze General] mindfrost82:
The Blackstone Radio 1.09.25.35 doesn't seem any different.

I'm getting EXCELLENT battery life, the usualy EXCELLENT call quality of the other BS radios, a little better reception than the 1.10.25.25 radio.

GPS seems the same though.

Its almost 3:30pm here now, I took my phone off the charger at 8am this morning and the battery just now went down to 99%. I just soft reset and its at 95%, but that's still ALOT better than any other radio I've tried. Even if its just sitting idle, its usually down to about 85% by now or lower.

I haven't tried the Quartz radio, but the last Quartz one didn't have the call quality the BS radios have had.

IMO, NO radio has beat any of the BS radios in terms of call quality. The M1 radio was actually close, but I had a ton of dropped calls with that one, even though they were clear lol.
[Touch Pro, Fuze General] p50kombi:
Don't go for Quartz

I tried both 1.09 BS and Quartz.

Quartz is a definite battery drainer.

Didn't get a chance to try the GPS, but flashed phone last night with Quartz radio and this morning it was down to 40 %, with no use overnight.

Whereas BS radio just kept their charge, or maybe lost 1% at most.

SO flashed back the 1.09 BS radio this morning.

Just a tip ;)
[Touch Pro, Fuze General] maw:
Okay thanks for the feedback on the new BS and Quartz radio. Since no major improvements, I'll still with the radio I have until HTC either comes with a new ROM or Radio for the Touch Pro.....
[Touch Pro, Fuze General] Maranelloot:
As my Touch Pro is being picked up today to go back to HTC (because of this lag problem), I switched to a Tytn2 (Kaiser) for the time being. Well, it's a huge difference compared to my TP. The Tytn2 is spot on, where the Touch Pro was always late...

I'll post it here when I know more...
[Touch Pro, Fuze General] joeltje:
Same Lage here, being it that it is once in a while... It looks as though the GPS doesn't cope very well with the speed differences you have when driving (It is like a GPS unit on a large elastic band :rolleyes: ).

I try the CAB for the tweaks after I do a custom ROM on my device...
[Touch Pro, Fuze General] Izzm:
i've got the same lag, like about 3 seconds (30-50 meters, depending on car speed) and nothing in this thread solved this problem

but i've got a solution to solve my 5-minutes-waiting-problem to get a gps-signal:

programs -> quickgps -> options -> 3x enable

(i disabled the second option and had to wait a very long time to get a gps-signal)
[Touch Pro, Fuze General] Minus-1:
Hi, Izzm.

Where do you see this option ("3x enable"). Are you joking about this?

I only see three options in QuickGPS:

1. Remind me when data expires

2. Auto download when data expires

3. Auto download when connect to PC via ActiveSync

My TomTom takes FOREVER to get a fix (but once it does, it does track properly).

Thank-you!
[Touch Pro, Fuze General] joeltje:
The tweaks did not improve my fix speed, as this was already in well under 1 minute. So no complaints there. I did notice improvement on the lag though, now the very tip of the arrow is exactly where I am...

The speech is spot on.

No complaints for me, as this is only a secondary navigationsystem, primary is Factory installed :)
[Touch Pro, Fuze General] Izzm:
sorry guy, i've got the german version and didnt know the english menu names

so, enable every menu option (especially Auto download when data expires) and try again a gps fix

here i get a gps fix in 20-30 secs with the option enabled, and more than 5 minutes when disabled
[Touch Pro, Fuze General] apd:
That's what he means by 3 x enable - i.e. enable all three!
[Touch Pro, Fuze General] gervasius:
but, my question is:

why other devices (not raphael) works WITHOUT quickGPS,

and Raphael must have quickGPS??

next question: wrong position, gps lag
[Touch Pro, Fuze General] Minus-1:
Lol Izzm & apd!

I feel so silly now. :)

Like you, I had all of them set 'cept option 2 ("Auto download when data expires"). Of course my thinking is/was why would I set this if I'm already syncing the data much more frequently than the expiry period, etc.

But, I will set it and hope somehow that it is a magical fix!

Oh boy (pinkies crossed). I'll let you guys know!

Thx for the help.
[Touch Pro, Fuze General] Flying Kiwi:
Sticking with the Kaiser

Thanks for that feedback. Aside from the fact the screen cant be tilted like on the TyTN II for watching videos, the poor GPS on the Touch Pro is yet another reason why I'll be hanging onto my TyTN II (with standard WM 6.0 ROM) until something truely better comes along. Nice to know the TyTN II isn't obsolete yet :D

A shame HTC don't seem to be very good at sorting GPS (and general) driver issues though.
[Touch Pro, Fuze General] mrvanx:
OK so far my replacement raphael has had some major GPS issues so ive been hunting and testing out things.

The problem was that it wasnt getting a fix AT ALL, regardless of if i was outside in an open area or indoors, i left it searching for a fix for a couple of hours to make sure and no deal, finally i spotted the (apparently) newer HTC GPS tool floating around and tried the technique posted earlier of clearing out the memory and turning off QuickGPS which did the trick.

The raphael now aquires a fix, nice and solid, in around 20 seconds when in a decent are, indoors doesnt work well at all but who cares?! :)

Ive attached the cab for reference, just clear the memory then leave it for a while to aquire a fix on its own steam, untick ALL the options in QuickGPS.

I suspect this is only an issue for certain models as later models seem to work fine. I cant comment on LAG just yet as ive done no testing of it.
[Touch Pro, Fuze General] NetRipper:
Let us know when you have results regarding the GPS lag. Without QuickGPS it takes up to 5 minutes before I get a fix. With QuickGPS I get a fix in 20 seconds. I only have a few seconds lag, but if you trick can fix the lag completely, i'd happily turn on tomtom 5 minutes before I go out to drive. ;-)
[Touch Pro, Fuze General] Izzm:
no.

the fix is very fast, maybe in 20-30 secs even while driving

but the 3-secs-lag (50 meters, depending on speed) still remains!

no.

tomtom7 navigating becomes sooo crappy!

lag still remains yet, and my position on the map is warping like tabletennis ball in a whirlpool :<
[Touch Pro, Fuze General] TomasNM:
Your position is jumping around your current,but I tried today iGo8 and my position was in opposite direction,so the map was going backwards. Tomtom was much better in this case. But as I said before...it varies with different cars. Don't know why,but in my bussiness car Skoda Octavia is the navigation useless(of course,because in this car I am travelling most long ways and I need it sometimes in strange locations - Murphy's law). In my private car(Volvo460) and also in friend's Seat Alhambra was it working very good with more than 5 sats fixed all the time(travelling via known locations,just testing). Geocaching is also possible in the forest with very good accuracy <10m(using Beeline GPS). So why the new,expensive cars are designed for signal cutting?
[Touch Pro, Fuze General] bauerpavel:
Explanation is very simple: metalic layer on the windshield usually used for either sun blocking or heating.
[Touch Pro, Fuze General] NetRipper:
Yep, coating. I have it on my car as well but I still have a stable fix. Just the few seconds lag is annoying.
[Touch Pro, Fuze General] topspeclt:
For the record - i've tried this registry fix and it doesn't improve the lag at all! In fact, I've noticed other anomalies too.

Oh well, it seems that us Touch Pro owners will have to put up with GPS lag forever because I'm sure it is a hardware issue.

(Mark my words).
[Touch Pro, Fuze General] karloe:
I haven't noticed the lag in the 3 weeks I've been using my Vario IV, it's always spot on.

(If it's hardware, then something should be different in the T-mobile version RAPH300)
[Touch Pro, Fuze General] groofoo:
ok, here is a little thing i found while using tom tom.

this afternoon i drove to my work using the tom tom nav app.

no lag or what so ever, like before (never had a lag problem).

until someone called me, i anser the call, the screen goes to black, ended the call, turned the screen back on, and switched back to tom tom using the taskmanager.

and there it is, a 50 meter lag.

i solved the lag by shutting down tom tom, and starting it up again.

so i was thinking, on my old (very old) SPV M500 with an external GPS reciever.

if i didnt have the phone capabilities (flight mode) on, the bleu tooth function wasn`t working, (blue tooth didn`t work).

on my trinity, if the phone was in flight mode, the internal gps reciever would not start.

so maybe if you have a poor phone connection to yourre telecom provider, you may suffer from this lag.

its just a suggestion what i tought off.

maybe it has nothing to do with each other but ... the noob as i am ;)
[Touch Pro, Fuze General] topspeclt:
Thanks for that.

Could you possibly supply us with details of your ROM and Radio versions?

I highly doubt they changed the hardware between the two.
[Touch Pro, Fuze General] Black1982:
One strange thing: After using Sleuth's registry settings cab (the 1 that had the typo adding the registry key):

My GPS programs: TT7, GPS Test, BeelineGPS, don't show any "birds".

I can get a fix fast enought, but the are no

bars indicating visible birds, TT7 doesn't show any active, but it functions normally.

Anyone?:confused:

Something to do with buffers?
[Touch Pro, Fuze General] hopper13:
Huh? Typo? What typo? Now I'm concerned! lol
[Touch Pro, Fuze General] Black1982:
The cab added: HKLM\SYSTEM\Cur0rentControlSet. No big deal, just deleted it.

Don't be alarmed :)
[Touch Pro, Fuze General] hopper13:
Don't see that in my registry. I must have missed the typo! :-)

All is running well with the registry tweaks, pretty much no position latency. Now the question is: Do I have the guts to learn to sim unlock and flash the blackstone radio to cure the time to lock/Quickgps/a-gps issue?