yashsingh1/xdaforums huggingface dataset:
[Touch Pro, Fuze General] dizzyraider:
There is not problem when I change the PollInterval, but it is with the addition of the buffer registries that breaks my Garmin XT. When I fire up Garmin with the registries, it would open up for a couple of seconds then exits by itself. Then when i try to open it again, a small error window shows up and won't restart the program. It would work again after I take those registries out (soft reset after registry change).
[Touch Pro, Fuze General] noellenchris:
Here is what I found on google...sounds good I guess?

The eGML is a strongly speed optimised 2d/3d graphic library. The render engine is optimised to read out high quality images with smooth colour transitions and sleek bends. The eGML is basically designed to run on different hardware and software environments. PocketPC

OpenGL ES-compliant graphics library and embedded 2D/3D Graphic Multiplatform Library (eGML), for the real-time generation of display graphics; Imagem’s spline-based library for handling bitmaps, frame buffer accesses, drawing of graphic primitives and object handing and movement;

Sounds better....
[Touch Pro, Fuze General] Da_G:
Raphael has native OpenGL ES drivers so that should indeed perform faster.

That being said, I would be hugely surprised if it made a difference in GPS lag..

No matter how terrible the performance of the graphics driver is, it should not cause lag, only frame dropping.. not as 'smooth' in other words..

So far my tests with AGPS are coming up with wierd results, it doesn't seem to be working at all. I'm thinking the RIL is set to use the IP/Port in NVRAM and not reading it out of the registry.. only way to tell is to set up a gprs packet sniffer though.. anyone know of one that works? :)

Tried the verizon AGPS server, supl.nokia.com, and at&t's, all are yielding the same results.. im thinking agpsnvsetting needs to be set to a value that ignores the NV agps servers and uses the registry ones.. assuming that's what that key controls. still debugging..
[Touch Pro, Fuze General] yzf750:
I never seem to get a gdop value under 4 on my fuse. At least in the car. In the open yes its better (1.5-2.5). I contribute this as the reason to the position being off by 50-200 feet at times which is super annoying when you have 2 roads side by side within 50 feet or when it showing you 50 feet to the right of the road then jumping you on to off ramps at times passing them by. What are other people getting for readings in a car off the fuse gps?

DOP Value Rating Description

1 Ideal This is the highest possible confidence level to be used for applications demanding the highest possible precision at all times

2-3 Excellent At this confidence level, positional measurements are considered accurate enough to meet all but the most sensitive applications

4-6 Good Represents a level that marks the minimum appropriate for making business decisions. Positional measurements could be used to make reliable in-route navigation suggestions to the user

7-8 Moderate Positional measurements could be used for calculations, but the fix quality could still be improved. A more open view of the sky is recommended

9-20 Fair Represents a low confidence level. Positional measurements should be discarded or used only to indicate a very rough estimate of the current location

21-50 Poor At this level, measurements are inaccurate by as much as 300 metres with a 6 meter accurate device (50 dop * 6 meters) and should be discarded
[Touch Pro, Fuze General] kk0813:
I just checked my fuze in home using GPS Test and HDOP is between 1.2 and 1.8 and some time going to 3.20 and immediately coming down to 1.4
[Touch Pro, Fuze General] noellenchris:
Which program are u using to see GDOP? HTC test?

Which radio are u using?
[Touch Pro, Fuze General] Da_G:
More info..

Using AGPSNVSetting = 5 causes the gpsdriver to load agps pde info from registry..

16:59:34 [D:GPS] GPS: [HTC_EnableConnManager] GPRSConnection = MEdia Net
16:59:34 [D:GPS] GPS: [NMEAThread] --- PosReqSentEvent RECEIVED!
16:59:34 [D:GPS] GPS: [SetupGPSConfigForGetPosition] Using AGPS settings from registry.
16:59:35 [D:GPS] GPS: [HTC_EnableConnManager] GPRS connection established!!
16:59:35 [D:GPS] GPS: [HTC_EnableConnManager] hHTC_Connection = 0x00000000, HTC_LocalIP = 1.1.1.1 (redacted)
16:59:37 [D:GPS] GPS: [SetupGPSConfigForGetPosition] Transferred from [supl.nokia.com] to [66.35.236.25]
16:59:37 [D:GPS] GPS: [SetupGPSConfigForGetPosition] NEW ServerIP = 66.35.236.25
16:59:37 [D:GPS] GPS: [SetupGPSConfigForGetPosition] AGPS Mode - ReAiding is Enabled.
Wimmob: ip address 0x19ec2342, ip port = 7275
pdsm: ip address 0x4223ec19, ip port = 27420
16:59:37 [D:GPS] GPS: [ProcessGpsFixRequest] ============================================================
16:59:37 [D:GPS] GPS: [ProcessGpsFixRequest]	operation_mode = 1
16:59:37 [D:GPS] GPS: [ProcessGpsFixRequest]	num_fixes = 999999999
16:59:37 [D:GPS] GPS: [ProcessGpsFixRequest]	time_between_fixes = 20
16:59:37 [D:GPS] GPS: [ProcessGpsFixRequest]	accuracy_threshold = 50
16:59:37 [D:GPS] GPS: [ProcessGpsFixRequest]	gps_session_timeout = 89
16:59:37 [D:GPS] GPS: [ProcessGpsFixRequest]	server_adrs = 66.35.236.25
16:59:37 [D:GPS] GPS: [ProcessGpsFixRequest]	port_id = 7275
16:59:37 [D:GPS] GPS: [ProcessGpsFixRequest] ============================================================

In this test, i've set GPSMode to 1 to force agps results, and set to obtain a fix every 20 seconds to allow more time to the system to get a fix.. (GPSMode 2 falls back to standalone if AGPS has issues and default fix is once per second which is not possible on gpsmode 1 because assistance data must be transferred for every fix)

odd is pdsm's port reply, it doesn't match up with what i fed it..

note gps driver's reply of gps_session_timeout = 89 also, this matches up with registry setting QOSPerformance, older gpsone documentation talks about it..

anyway, thats what i found out for today :P

Oh yeah, and re: pollinterval, i've tested 100 500 and 1000 so far, and as i predicted at 100 there's 9 poll events with no data returned, 1 with return.. 500 is every other poll event, and 1000 data is returned on each poll event. so it seems there's nothing to be gained by polling faster other than wasting cpu cycles. :)
[Touch Pro, Fuze General] Da_G:
Also observed the differing behavior of seeing 16 sats and narrowing it down vs. seeing one sat and building up from there, per the debug log the difference is if quickgps has downloaded and injected the epheremis data yet (injecting is not immediate after downloading)- if not, you start with 1 sat and build up from there.
[Touch Pro, Fuze General] mindfrost82:
Have you looked into something like the PPST files for Sprint and Verizon?

I know when we were trying to get GPS working on the Sprint Touch we had an extremely difficult time until someone figured out we needed to run a PPST file that was in the /Windows directory to get aGPS to function. Someone guessed it wrote data into NVRAM or into the radio. Sure enough, once we got that file it worked great after that. The PPST file was different for each carrier too.

That could just be a CDMA thing though.
[Touch Pro, Fuze General] Da_G:
believe me i wish it was that easy :) cdma raph test rom comes with all drivers etc necessary to access radio rom directly, gsm does not. and the tools for each are different (msm75xx vs. msm72xx)

i believe the method to access radio rom on our device is similar to method for ks20 (compositefn + windiag).. we have windiag but not compositefn drivers.. i have not been able to get ks20 ones working yet.. but i believe a working compositefn driver + usb switch is what we lack to get access to radio rom nv.

note that registereditor that i posted in raph software forum is capable of editing nv registers. but we need to know what address corresponds to what register..
[Touch Pro, Fuze General] yzf750:
Stock att radio. I tryed 28,32 and m1 also. I think gps test which is floating around the forum shows the 3 dop values (v, h, and 3d) not sure as I use a few different programs at times. havent tried htc test yet. But to me its showing poor reception (unless totally outside of a car) which most likely is hardware related I think. My tilt was always under 2 in the car. I dont suffer a real lag issue, at least with igo8, maybe 1-1.5 sec most the time. Its the location (50-150) feet off that causes my problems. if i hold it out the window it gets much better 25-50 feet. it shouldnt be that bad in a car and its not just my car, it happens in any car ive tryed it in.
[Touch Pro, Fuze General] Sleuth255:
VisualGPSce also shows DOP on the stats panel.
[Touch Pro, Fuze General] noellenchris:
I was updating my "GeoScout" software for geocaching and under the sat info...it shows the data output and interprets it in a window below. Seems usefull, but I'm not Da_G. So it might as well be german to me.
[Touch Pro, Fuze General] X2D:
I haven't had much opportunity to do much flashing and testing so I've stayed relatively quiet in this thread because I have nothing to contribute but when I read this comment this is what my face looked like --> :eek:

I flashed my phone within 3 days of having it but the thought of holding my phone outside a moving vehicles window is a disheartening thought lol.

You sir are a committed tester. ;)
[Touch Pro, Fuze General] noellenchris:
Maybe I can try to scare my TP....especially if I hold it loosly out the window..lol:D
[Touch Pro, Fuze General] kavi:
Another test:

The whole day I have been flashing different roms, radios (raphael) and applying patches mentioned all over.

I was testing the TP against my tilt running stock ATT and a Kaiser running HDIII Raphael. All the fixes so far just nudges the problem up and down but nothing really fixes the position lag issue. Lock times vary between ROM's and Radios but does not effect the position issue at all.

Results in brief:

Gradually Gaining speed:

REAL 20 30 40 50 60

KAIS 20 31 39 49 61

RAPH 15 27 35 44 59

Coming to a complete stop:

REAL 40 30 20 10 0

KIAS 40 31 21 8 3 2 1 0

RAPH 40 30 35 25 20 18 11 8 5 3 2 1 0

Passing cross street:

^ Direction of travel

==========================

----Actual Car

------------------Kaiser

==========================

------------------------------TP

Hope we can find an actual fix fast.
[Touch Pro, Fuze General] Sleuth255:
Could you post a reg containing your GPS Intermediate Driver key and subkeys? What ROM/radio are you using now on your raphael? You should be able to tweak it to eliminate Position Lag with the verison of TT you are running.
[Touch Pro, Fuze General] kavi:
I am using your regfix cab from the thread.

Radio 1.08.25.20M1 Raphael

ROM NATF 4.1 Standard

Reg entries are attached. It would be great if I can get this fixed.
[Touch Pro, Fuze General] noellenchris:
Da_G, have you tried the latest xperia radio? Some ppl are saying it fixes the GPS....I haven't tried it yet. I'm guessing it's just luck....:confused:
[Touch Pro, Fuze General] kavi:
Is it just faster lock times or a real fix for the pos. lag issue?
[Touch Pro, Fuze General] noellenchris:
In the radio thread people are saying it fixes the everything. But I've heard that before. I've got rid of most of my lag by reducing the maxbuffer to 256. But's it's still got speed lag. So it's a small achievement, but not a good fix. Da_G is working feverishly debugging the gps drivers and stuff beyond most of us. Hopefully he discovers the cause of these issues.

Also some ppl report that installing the AT&T Navigator fixes the gps too. I'm curious to see the added reg settings or drivers if any are added.
[Touch Pro, Fuze General] kavi:
I am also hoping that Da_G will put and end to this misery.

Did you try the ATT Nav App?
[Touch Pro, Fuze General] noellenchris:
I loaded it, but didn't subscribe. I inspected the registry, and couldn't find any changes after install. All my nav programs work the same but haven't test lag. I was hoping to find some registry changes since it requested a reboot after install. I may activate it and see what it does....I'm also thinkin on changing to the xperia radio. This Blackstone radio is so good on the battery though...GPS time is soso. I think for me the M1 radio was quicker on fix...
[Touch Pro, Fuze General] kavi:
I will also try to install and see whether it makes any registry changes. Sadly reglogger is not working for me. Planning to do a whole registry compare with BC.

BTW I am using M1 and GPS lock is good although having band switch issues @ home that I never had with the Kaiser. :mad:
[Touch Pro, Fuze General] Da_G:
I looked at the cab installer for telenav when i first dissected the fuze rom, it didn't seem to change anything gps related in the reg.. don't remember if i disassembled the exe to see if it does when it loads though..

BTW the new leaked sprint rom has new gps drivers, but i see they have some cdma specific code, let's see if they work/help.. :)

They're significantly different than the one's we're using.
[Touch Pro, Fuze General] noellenchris:
was gettin worried...thought you found another thread to hang in...lol I'm flashing the xperia radio now. Would like to see the new drivers too. well you know more than me about what your lookin at. Is the Sprint TP's having any gps issues? Thanks again for all your work:D
[Touch Pro, Fuze General] Da_G:
Duno, the ROM is so new I don't know if anyone's running it yet..

But with the new driver, no response from GPS unit at all, probably the CDMA specific code at fault there.. doh!
[Touch Pro, Fuze General] kavi:
I guess then it's pointless trying to capture the registry changes. Will wait for your findings.

Thanks for all the hard work Da_G:)
[Touch Pro, Fuze General] Sleuth255:
Two Questions:

Do you have the option for a "Builtin GPS receiver" device in TomTom?

Have you tried the 1.02.25.28 Radio?
[Touch Pro, Fuze General] mindfrost82:
I loaded the Xperia radio last night and tested GPS this morning.

The initial fix was pretty fast, probably faster than the Blackstone one.

The lag was still there but maybe a little less than it was with the BS radio.

When going 40mph using iGo, it was like the point of the arrow was at the back of my truck rather than the front. In other words, when the back of my truck crossed the intersection is when the point of the arrow would cross the intersection. So that's like 20ft off and probably less than 1 sec lag.

I'll have to test if the call quality is on par with the BS radio though. Call quality and reception is #1 for me and GPS is after that. The Xperia radios have always given me the best reception but the call quality hasn't been as good as the BS radios.
[Touch Pro, Fuze General] noellenchris:
LOL.....I did the same thing last night and my results are just like yours. I did make some calls today and it seems just as good as the BS. So far the batter seems just as good also. The GPS does seem faster than BS (For me anyway). The internet seems good to go also. Lag seems the same too.

I did notice though that "Nan" is still there.

My Garmin was flashing back and forth from one red dot to full bar in gps signal strength with the BS radio, and now it is steady with good strength. But it still lags identically to the BS. TT7 seems the same also. The speed lag did seem a tiny less (could be due to the threat's I made about hanging it loosly out the window...lol).

Sleuth: did you ever figure out that nan thing? It always seems to pause at that $PSTSa? :61 string. :confused:

Mindfrost: does iGo give traffic etc.? like Garmin?
[Touch Pro, Fuze General] Sleuth255:
NaN doesn't affect anything since it's only an initial value that goes away as soon as you start moving. I don't think we'll ever change speed lag because its a function of the chip which I've also seen expressed in the actual $GPVTG sentences (when stopped, I've watched $GPVTG sentences go by, dropping the speed to zero at the same rate). $PSTIS is a proprietary sentence not used by navigation software. I thought Da_G mentions it in this thread as an input sentence. I think the pause is simply the 1 second poll rate. You can see this in HTC GPS tool. Sentences seem to pulse once per second. Sometimes $PSTIS is the last sentence before the next poll and sometimes it isn't.
[Touch Pro, Fuze General] mindfrost82:
No, iGo doesn't do traffic unless you can do the TMC thing over the FM transmitter I think.

That's one thing I liked about Garmin, well that and the real-time Fuel Prices.

I just wish it had TTS and smoother map updates.

Oh, the other thing I noticed is in VisualGPSCe, my 3 DOP readings were around:

1.6-1.9

0.6

1.6-1.9

That was all the time while driving about 40mph. I never looked to see what it was at with the BS radio.
[Touch Pro, Fuze General] mindfrost82:
Oh yeah, these are the settings I've been using. Since you guys said there's basically no reason to put the PollInterval below 1000 (because it only updates once per second), I changed that to 1000 and I also increased the SleepOnNoData to 1500 since Garmin seems to want that higher than the PollInterval, otherwise the signal keeps jumping around.

HKLM\System\CurrentControlSet\GPS Intermediate Driver\Drivers\GPSOneDevice

PollInterval = 1000

HKLM\System\CurrentControlSet\GPS Intermediate Driver\Drivers

InputBufferSize = 256

OutputBufferSize = 128

SleepOnNoData = 1500

HKLM\SYSTEM\CurrentControlSet\GPS Intermediate Driver\Multiplexer

MaxBufferSize = 256

HKLM\System\CurrentControlSet\GPS Intermediate Driver

MaxLogFileSize = 0

CurrentLogFile = null

OldLogFile = null
[Touch Pro, Fuze General] noellenchris:
Interesting observation with the sleep to 1500. It makes sense though, you wouldn't want the GPS trying to go to sleep.. Otherwise my settings are identical. I'm gonna change my sleep to 1500 too.

I'm still trying to see if I can change my dpi (so i can run in QVGA) so that GuitarHero will work, and also Garmin may perform better. Strange course of action, but I'm really curious... :D
[Touch Pro, Fuze General] iRiKi:
intersections arent a good way of measure IMHO.

one of the most fiable test is driving in a highway, and when passing under a bridge check the gps and you'll see how much lag your device has :)
[Touch Pro, Fuze General] noellenchris:
I'm going back to the BS radio. I had an echo on 3 different calls today....:(
[Touch Pro, Fuze General] kavi:
I have finally decided to go back to my faithful Kaiser. I've had enough playing with the GPS. I have been using the Kaiser in the evening and now I know what I've been missing :)

More issues I noticed with TT7 and TP:

> Loss of signal at the end of a voice call (using BT). Takes a few seconds to regain location and if you are just about to make a few corners it really messes things up.

> Not every warm start is the same all though they are at even intervals.

Also the band switch delay is longer than the Kaiser and the time without signal is considerably higher. It maybe just my device but I seriously expected more from HTC. With time and this much user feedback they should be able to deliver on basic functionality.

I am thinking of going for the Xperia since the GPS lock and slide and type is just amazing. I will continue to keep an eye on the developments hopefully Da_G will come up with something.

Thank you all for the great tips and help.
[Touch Pro, Fuze General] iRiKi:
It's almost the same as the Fuze:

Qualcomm MSM7200A Embedded gpsOne GPS module

Find the Xperia zone in the forum, they're having the same problems as we do :)
[Touch Pro, Fuze General] kavi:
That's news need to read more then. But my friend's one just works flawlessly with TT7. Thanks for the heads up. Looks like it's kaiser for me for a while. :rolleyes:

Edit:

Some more things I noticed while doing my tests (hope this helps the the testers)

> The driving speed on GPSTEST is quite accurate (almost the same as Kaiser) and in sync with the vehicle speed

> HTC GPS tool reports the laggy speed in sync with the TT speed

Most important

> The voice prompt is dead on. How? Well the same route, same map and same version of TT running on Kaiser and TP will announce at the same time. This leads me to believe that the display drawing is the one that's behind.Of course I could be wrong :)

My theory:

TT will announce the next turn depending on the distance from turning point. This is set by the program and it's a constant. If both devices are announcing at the same time that means both TT's know exactly how far you are from the next turning point (GPS cordinates must be identical or very close). Why it displays the position differently is the million dollar question!!!
[Touch Pro, Fuze General] Sleuth255:
I'd at least flash Da_G and the blackstone radio before giving up on your fuze. Unless you choose not to believe your eyes, the comparison video on post 400 clearly shows that the problem can be solved. It documents the fact that I have zero lag and better signal strength than my tilt. The GPS on my fuze is superior IMHO and I'm running the same version of TT that you are.

Hint: Da_G has paid special attention to graphics performance. I'd try the exact 2.04-MSVC version I'm using first.
[Touch Pro, Fuze General] mindfrost82:
I also went back to the BS radio. This Xperia radio was just like the others I've tried in terms of call quality.
[Touch Pro, Fuze General] kavi:
Ok then it's time to CID unlock and try what you are suggesting over the weekend.

BTW did you notice the drop of signal at the end of a call with the combo you are using?
[Touch Pro, Fuze General] Ouzo:
kavi, please could you let us know how you get on with Da_G's ROM? So far I've changed the radio on my Touch Pro, but I haven't plucked up the courage to try a different ROM yet..... took me a whole year to flash my old Elf, and it completely transformed it!

I've tried TomTom 6.0, 6.030, and now 7.910(?) with UK maps 8.15 and no amount of reg hacking has helped me get rid of the lag. Like you, the voice is almost always spot on in TomTom so I too had begun to wonder if this is a video issue.... the graphics performance on my Pro is worse than on my Elf in certain instances (I know some people don't have lag).
[Touch Pro, Fuze General] Sleuth255:
I've never had a call come in while using the GPS. Sorry.

Read through this thread. Leaving the SIM/SD cards out is a bit excessive and completely unnecessary IMHO but the rest is good stuff. You need to get to hardspl before doing anything. No CID unlocking is necessary when its installed. Blackstone radio is your last test and may be unnecessary. It will cost you to go there anyway since you need to security unlock to run it.
[Touch Pro, Fuze General] Da_G:
More info: if you have both ServerURL and ServerIP under \Software\HTC\SUPL AGPS, it pulls the value from ServerURL and uses that. (not related to lag, just sharing more info i found in the process of poking)

Another observation: The NMEA thread reports a Priority Level of 251, which is a non-real-time priority level.. this could be allowing anything using more cpu with a higher priority to take precedence, causing/adding to the lag issue..
[Touch Pro, Fuze General] Da_G:
Note the times in this log: (i'm replying to myself to bump thread because this seems significant)

18:13:38 [D:GPS] GPS: [ProcessPollData] --- g_hStateChangeEvent Received!
========POSITION REPORT========
valid 0Xfffdfyear = 2009, mon = 1, day = 18, h = 2, min = 13, sec = 37, ms = 200

There is a consistent one second lag in the position report vs. the log timestamp (log timestamp generated from time on cell towers, which should be getting its timesource from the same place as the gps chip, the satellites.. so that shows that there is a real 1 second lag somewhere in the system before the NMEA data even hits the GPSID..)

These values are generated directly by gpsdriver.dll so that shows gpsid_htc.dll is definitely NOT at fault with the gps lag, and it's either gpsdriver.dll or even further up the system in the radio rom itself.. i'm still thinking it's a simple NVRAM bit flag..
[Touch Pro, Fuze General] noellenchris:
Can we change Priority Level for the GPS via reg?