[HD2 Android NAND Development] AngelDeath:
Ok pardon my dumbness in this, Yes the file was from the site you stated, but if the .c isnt part of the kernel source, then where would the .c file be place to be compiled? I know your working on gingerbread, and most have no time, I have been trying to see about how to pull that info and look thru it, unfortunately I cant de-compile and am not that good. And being the Inspire from ATT (DHD is it?) works amazing (I know native android) isnt the hardware near the same? Isnt the GPS chip the same as the HD2? Would it be more interesting to rip apart a Inspire Stock Rom instead? I know I wont be able to have it as everyone wants it, but As this point I am shooting for consistency then speed, because to me 60seconds or less I think would satisfy just about everyone for cold locks, and under 15seconds for relocks.

And a few more tweaks I think I can get it there, the biggest stumbling block is getting the info to be read right by the gps chip. But I think I'm making progress :)

Do tell when you do I'm curious cause obviously its mixed results.

The xtra.bin file shouldnt have to be manually copied, where did you get that file? Because this file needs to be downloaded for your location, the xtra.bin file from my understanding its all the gps sats, but sats from your own area, so I would be curious to see where the xtra.bin came from.

Well first locks can, there are so many factors involved, but if your re-locks occur under 30 seconds at least thats the right direction.

At this point, I am happy that people are getting there locks in 60 seconds and relocks in under 30seconds. Until either I or all of is figure out the right way to impliment this, I think I can speak for most that they would be happy of the consistent <60second locks and under <30 second relocks.

Mafioso, I actually was looking at the kernel sources, not the compiled sources, because the .h or .c file are soruces, like a Dev told me, the .h file is a header. So I was looking in the right direction, just dont know where I would be lookinbg for the .c file in the source. Which I am still alittle confused.

memin1857,

Your right about the agps dtat being cleared, I dont think it doeds make a difference, nd the reason why is cause the gps status program I ran with a logcat and I cant see where it is downloading this file to, I ran the same agps download in the inspire, and its the same thing, but I dont know where even in the stock desire its being downloaded to, the logcat doesnt show anything, and I think thats the gps status being not logcat friendly, I think that would help with the hd2 if I could see it.

As I said, I dont think we wont (dare I say) will ever get it like a native android, maybe I'm wrong, but we'll see. But like I said I think everyone will be happy with <60 seconds and <30seconds for re-locks. At this point I think consistency is more important across the board then speed. But we will see, I'm trying to weed thru different things to see if I can find the "magic bullet"

I think the user plane and control plane is in the scripts, but I'm going to look at the scripts again.

And as the way the gps status works on the inspire is when you run it it comes on and shows me x/x before the locks, and then a few seconds it locks, where in the HD2 it doesnt show me the x/x on the right so I think the info gps pulls for that might be a starting point as to where its looking.

Will keep you guys posted.