[HD2 Android NAND Development] AngelDeath:
Okay this is turning into real BS here, let me state some facts and then I'm done with all this going back and forth:

A) Never have I claimed that gps.conf fixed the AGPS.

B) I've stated it aids in acquiring a faster lock.

1) Does AGPS work? Answer NO.

2) Does GPS work? Answer YES.

3) Does gps.conf help AGPS? Answer NO

4) Does gps.conf help GPS? Answer YES.

5) Does gps.conf get used? Answer YES.

6) Is gps.conf useless? Answer NO.

Having said that I guess this piece of the logcat escaped everyone:

04-03 07:35:13.847: INFO/lib_locapi(157): [GPS:] Starting Loc NI thread...

04-03 07:35:13.847: DEBUG/GpsLocationProvider(157): /etc/gps.conf_unknown not exist. Fall back to /etc/gps.conf.

04-03 07:35:13.857: INFO/GpsLocationProvider(157): AGPS_WAKELOCK not set, default to disable

04-03 07:35:13.877: DEBUG/GpsLocationProvider(157): GpsEventThread starting

04-03 07:35:13.877: DEBUG/GpsLocationProvider(157): end of constructor

All of you have the right to believe what you want, you say it doesnt work, again I'l say, fine it doesnt work, I am not forcing anyone to use it or believe it, but I think there is enough people who would say otherwise. Also you dont have to wait 7 days just to truly test it, you can test it 3 days later or 4 days later. 6 Days is how long the info is good for supposedly. So let's stop pushing our energy into personal feelings, and use it to help whoever we can.

Mafioso, the only bad side to that is in a nand version it doesnt do us very much good, and Supposedly GPS Status is suppose to do this as well, but unfortunately we cant be sure since the logcat doesnt show that.

But even with my understanding, even if that infor is injected just for arguements sake into the chip, it would still take time to lock based on what was said in irc. the xtra.bin isnt the agps part. Its the same thing that I presume that gets downloaded on to standalone units as well. jonpry calls it the almanac.

Arne182,

Just wondering, one of the question was about the gps chip in the HD2 the same chip as in the DHD/Inspire, when I looked online it said they both were qualcom built in gps chips. Wouldnt say looking through a native phone like the inspire (Obviously someone like you) possibly find when the communication break down is?

Because I was testing another rom build out, and this is how far I got based on the logcat:

04-03 07:37:13.888: DEBUG/GpsXtraDownloader(157): Downloading XTRA data from http://xtra3.gpsonextra.net/xtra.bin

04-03 07:37:14.448: DEBUG/GpsLocationProvider(157): calling native_inject_xtra_data

04-03 07:37:14.448: DEBUG/GpsLocationProvider(157): Acquiring wakelock

04-03 07:37:14.448: DEBUG/lib_locapi(157): qct_loc_eng_inject_xtra_data, xtra size = 39767

04-03 07:37:14.448: VERBOSE/lib_locapi(157): qct_loc_eng_inject_xtra_data, inject part = 1, len = 400, len = 400

04-03 07:37:14.448: VERBOSE/lib_locapi(157): qct_loc_eng_inject_xtra_data, total part = 1, len = 400

04-03 07:37:14.448: VERBOSE/locapi_rpc_glue(157): loc_ioctl

04-03 07:37:14.448: ERROR/lib_locapi(157): qct_loc_eng_inject_xtra_data, loc_ioctl for xtra returned -1234

04-03 07:37:14.448: DEBUG/lib_locapi(157): qct_loc_eng_inject_xtra_data: injected 0, FAILED

04-03 07:37:14.448: DEBUG/GpsLocationProvider(157): Releasing wakelock

04-03 07:37:17.377: INFO/EventLogService(324): Aggregate from 1301816185517 (log), 1301814436510 (data)

04-03 07:39:27.627: INFO/(157): getProfileResume(): buf=0, value=0

The Bold obviously shows the failure, which I assume failed to inject the xtra.bin from what I'm reading, I dont know if thats of any help or not. But the Inspire doesnt fail because it stock, and has the same lines, Maybe looking for that part of the code in the source and seeing what would cause it to fail may help (I probably worded that wrong).