I think I found the culprit for the gps issue.
I have been messing with gapps and making my own installs via a zip recovery, which I have FINALLY found after about 8 hrs of exhausting testing and re-testing. I've installed and re-installed a rom and gapps, and the gapps I made of my own so many times I'm surprised my phone hasn't exploded

.
Here is what I found and I can finally replicate this each time, this is what makes me think it's something in the gapps files, the google.xxx files. Since I'm not a programmer of any kind just a simple IT type person, from my knowledge I would assume that the networklocation file is causing the issue, but I could be totally off base and this file is simply for 3g location stuff and not gps, I'm not sure.
I have modified the gapps folder and taken out (for my personal preference) som apk files.
The files I have taken out are as follows:
ThinkFree
Talkback
Talk
Microbes
ChromeBookmarksSynceAdapter
The rest of the files I left alone as is.
I remade a zip called it MyGapps.zip and put it on my phone.
I cleared Dalvik and cahce partition
I have done both ways, format data, and the above 2 only, and both ways I get the same results.
I am useing the milestone1 aokp rom.
On to my findings.
When I install the rom, and install google maps to test gps, it works like a dream, no lag time in locking, and locks within 2-5 seconds, it also finds my location very close, withing 8 meters it says, but it pinpoints where I am quite nicely.
Now, when I install gapps, be it my_gapps that I made or the default gapps I downloaded online (gapps-jb-20121011-signed.zip), I clear dalvik again, clear cache partiotion, and again I have tested both ways of a format and not formatting, and came up with the same results. I get 2 kind of reactions:
1: the gps takes forever to lock on and may or may not lock on
2: the gps "says" it locks on, but it shows me like anywhere from 10-20 miles away from where I am at, and the gps lock is solid, not bliinking, and I get no message about "cannot locate" or "waiting for location".
I can replicate this same affect each and everytime I go thru the steps I mentioned.
I have also tried it with the tweaks/fixs that are for download on xda forums as well, the gps fix didn't resolve anything after I applied it via a zip in recovery.
ALL this being said, I am thinking that the gapps files, (not sure which one) but they are causing the gps issue that people are having perhaps.
Can anyone that's more knowledgeable about this either fill me in more or confirm/deny this, and please correct me if I am mistaken about the files, just from common deduction of my IT type background, it seems to result in gapps being the culprit.