So I spoke with Verizon today

[DroidDev]

I was torn between the Fascinate and the Droid X. Leaning torwards the Fascinate because it doesnt look like it fell off the Ugly Bus among other things.

I am very concerned about the GPS issues people are having with no reliable work around.

So I called Verizon. Talked to a Tier 3 Technical Support rep about the GPS issues. Myself being a Test Engineer and Analyst I understand how the software testing process goes and I was able to get pretty far with him.

When I asked him about the GPS issues and a fix for them he said he has no timeline for the fix and just knows that it is at the top of Samsung's list and they are working on it. Expect it in the next month or two. This I expected.

When developers receive a request to fix something like this there are SEVERAL phases that need to take place before an official fix can be released. Generally this order:

1. Requirements Phase
   
   This is the phase where Project Planners and Developers look at the issue and draw up some business requirements that will follow the project throughout testing.​
2. Development
   
   This is the phase where the developers develop the code for the fix based on the Requirements from the previous phase.​
3. Systems Test (ST)
   
   This is the initial testing phase for what the Developers created (the fix)​
4. User Acceptance Testing (UAT)
   
   This phase tests the fix how the user would, via the applications and device.​
5. Production Testing (ORT and UCT)
   
   In this phase the testing builds upon what was done in ST and UAT. Generally geared mostly towards getting it ready and polished to be pushed out.​
6. Release to End User (Post Production)
   
   TADA!!!!!!! ​

I hope that sheds some light on how these fixes come to fruition. This takes longer because of the custom UI. So each phase has to be centered on testing the fix that the developers had to create (to be compatible with touchwiz).

Just be patient, it WILL be fixed.

 

[NickA]

Being a developer myself, I've been through many iterations of the System Development Life Cycle. One thing I've learned working on a team and on my own is that software is released with known bugs. I've done it, and I'm sure everyone else does. The GPS issue would never have made it past UAT. My guess is that a 2-5 minute lock was acceptable to them, and they know they will take some heat for it but simply had to get the product finished. Either that or they just have a poor quality assurance department.

 

[DroidDev]

Exactly. At the moment I am finding it easy to relate the people that coded the GPS software to IBM developers. Slow and lazy with the "lets fix it before the U.S. folkes wake up and when they ask why it was broken we can tell them we dont know it just started working and tell them it was user error" mentality.

To them I say....wait for it....

 

[zaphodbebleebrox]

there is a fix, its called GOOGLE MAPS, works perfect.

 

[DroidDev]

No, not really. Have same GPS problems.

 

[packerbacker]

Did you try GPS Test? I ran it once and then my GPS worked flawlessly.

 

[DroidDev]

Not yet but that is now at the tome of my list. Thanks!

 

[emptycube]

Did you try GPS Test? I ran it once and then my GPS worked flawlessly.

So it locks within seconds every time? Even after not being used for a while?

Once I get a lock mine will lock within seconds for a while but after some time of not being used it's back to 2-4 minute locks.

 

[SOTK]

So it locks within seconds every time? Even after not being used for a while?

Once I get a lock mine will lock within seconds for a while but after some time of not being used it's back to 2-4 minute locks.

Mine does the same. If I want instant locks, I have to run GPS Test every other day or so. I can maybe get through a day or two of instant locks after running it but that's about it.

 

[Kurolover35]

there is a fix, its called GOOGLE MAPS, works perfect.

Google maps is not the same as google navigation, nor can it do the same thing.
I ran GPS Test and I still have 2-5 minute lock in times and sometimes it wont even initiate when GPS is on and location services are enabled!