[Vibrant General] Jon C:
The Skinny:

I just spent the better part of a morning on the line with T-Mobile and Samsung escalated support. All issues have been reported to their respected corporate advisors for both companies. I will re-post this info in the other threads (GPS / Reception) at a later time, and will update as things unfold.

T-Mobile, as stated before, claims this is the first they've heard of the issues. I reported the broken Compass, GPS locking issues and general 'death grip' reception issues (which T-Mobile sales reps are now admitting to). All issues were escalated to the bigwigs in Bellevue, and I was told that we'll see a post in the official T-Mobile forums, as soon as they hear back from Samsung. The forums will be updated before the CSRs.

Samsung also reports that this is the first they've heard of any major issues regarding the compass, GPS or reception. The CSR was super nice and not at all shady. There are certain details that will not be divulged, but I presented myself as a power user, and was promised that as much information that can be reported back to me, will be.

Again, all issues were reported to HQ, to whoever receives these complaints.

The Compass:

It appears as if the problem is in 'Average Data' and 'Raw Data'. Either Google accepts average and the Galaxy S reports raw, or vice versa. Either way, they are not compatible. I asked if Google requests average, but Samsung sends raw, which is causing the problems, or if it's the other way around. We'll find out when Technical Support gets back to me.

At the start of the phone call, regarding the Compass issue, I was told that "It looks like there might be an OTA to fix this issue?" The question mark was part of that comment. Later in the conversation, that seemed to not come up again.

The information was confusing, as to which party is responsible for fixing the issue. The rep made it sound like it's up to Google. I asked if this information could be made available, so I can know if it's up to Google or Samsung to fix the issue. Can the phone be made to report values differently, or is it up to Google (and by that logic: all developers) to make an acception for the Galaxy S? We'll see, when I get my follow-up email.

More to that point: I asked if there was any way Samsung USA could find out if Samsung Korea did, in fact, update the international i9000 device with an OTA to address all of these issues. Obviously, they are different companies, but I was told that this information will be reported to me, if they can dig it up.

GPS:

As for the GPS locking issues, we didn't have to time to delve into that, too deeply. This is something I will press on when I speak with them again. Obviously, GPS is a delicate art, but the Vibrant is clearly experiencing issues. I'll post more about this when the time comes.

Reception ('Grip of Death'):

I'm starting to drop calls, and I live within a mile from a 3G tower. My T-Mo coverage is amazing, because I'm in their home market. I mentioned the reception problems, along with the fact that T-Mo sales reps know 'pull an Apple' and tell you to hold your phone a special way to avoid reception problems. It would appear that this issue is a known issue, and it was kind of avoided in this conversation. Whether or not it will (or even can be) fixed, we'll find out later.

Anyway, that's all I have for now. I have to get to work, but I'll post more info as it comes in. Hope that helps.