Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I did the GSM reset on my Samsung Cantlocate and the GPS worked much better for 2 days and now it won't hold a lock for more than a few seconds.
Great. So I permanently lost ALL my stuff for nothing.
Re the problems with the Galaxy S:-
The problems are all down to the new combined Broadcom chip which is used to cover GPS, BT & Wifi.
As you already know both the GPS & Wifi have issues on the Galaxy models.
This has been found to be a driver issue with the Broadcom chip.
Samsung passed the problem to Broadcom who fixed the drivers and then handed it back over to Samsung.
Now problem one.... Samsung then had to engineer the fix into the Filesystem but this was then found to also be in error.
This was fixed and was just about to be released as the GPS fix (which would also have corrected the Wifi problem) but just at the last minute it was halted as Froyo was about to be released and this had yet another different Filesystem which was found would alter all the hard work on putting the new drivers onto the system.
So a decision was made to halt the release, work the fixes into Froyo and then release it this time as a combined Froyo and GPS/Wifi/Filesystem/Lag fixes.
However..... last minute checks found an error and this has put it back.
It should now make it to mid October and I am confident this will happen.
As to does it fix the problems...... No idea.
Is it already out in one of the other releases..... Absolutely not.
None of the present releases holds any of the 'official' fixes, be that GPS/Wifi/Lag/Filesystem.
he said, We are expecting to have Android 2.2 ready to "pass on to service providers" sometime near the end of this year or early next year. Then it will be up to the providers to release it to their users"
I've only had my phone for a couple of weeks, and for the most part I love it; however I am growing increasingly frustrated with the lack of GPS.
Truthfully GPS isn't a feature that I would use that often even it were fully functional, but the nagging thoughts that I paid for a product that is not fully functional is beginning to eat away at me a bit.
I would be perfectly fine with waiting for a true GPS fix is Samsung would come out and own up to the issue and communicate clearly with what progress they've made to address the problem and give a proper time table for when the fix will be implemented.
Just my $0.02
So now that we have a dedicated GPS thread, I thought I'd ask a few questions that have been on my mind about the Captivate's GPS behavior. Maybe some of the folks who really know the nitty gritty about GPS, like our friend Mr. GPS, will have some insight into this. I'm not sure if it offers clues into what the Captivate's GPS problem really is or if other people's experience is similar, but it seems potentially interesting.
Anyway, if I walk outside and launch GPS Status, it typically takes a few seconds and then gradually starts seeing satellites, but not yet using them. So I get 0/2, 0/3, 0/4, and then somewhere around 20-30s after I launched it, typically, it will get a lock and a location, usually reporting something like 3/4 or 4/4 (used/seen). But, and this strikes me as weird, it generally loses that initial lock almost immediately, within a second or less, dropping back to 0/3 or 0/2. Then over the next 30s, it starts seeing more and more satellites, 0/4, 0/6, 0/7, 0/8, and then, 30s or so after the first lock, it gets a second, better lock, usually something like 6/8 or so. It then almost immediately gets worse again, but usually doesn't lose lock completely, just drops to 2/6, or 3/5 or something. At this point it generally holds a lock of sorts more or less indefinitely (if I don't move), but the number of sats used/seen fluctuates wildly, as do the various SNRs. I find this behavior pretty strange. Why does it always lose that first lock so quickly? Only to subsequently get a better one? That really doesn't feel like a hardware issue like bad antenna or anything, because why would it vary?
The other thing that seems strange to me is that if I then quit out of GPS status and go into maps, it starts blinking the GPS icon at the top and stays that way for a looonnng time, typically a minute or more. Shouldn't the driver still have the data from when GPS status was running a mere instant before? Why does maps seem to need to re-aquire the lock all over again from the beginning? I thought the driver was supposed to cache recent data-- this is the premise behind apps like Tracker Booster, which sit in the background and repeatedly query the GPS so the data will always be fresh, allowing GPS tracks to be smoothed out. Maybe the maps app makes some call that forces the GPS to restart from the beginning? Anyone know?
Anyway, these are just a couple GPS conundra that have been bugging me recently.![]()