I have been watching the Signal Strength from Settings > About > Status and noticed the reported numbers do not correlate with the Cell Bar Level display at the top or the numbers I am logging with the Cell Connectivity Tracker application.
Here are some observations from using the "Cell Connectivity Tracker" application:
Cell strength as it relates to the Cell Signal Bars
0 bars = -106dBm
1 bar = -101dBm
2 bars = -96dBm
3 bars = -91dBm
4 bars = -86dBm
Right now I have no visible Bars being displayed and my Signal Strength is -72dBm on the Status page and the Cell Connectivity Tracker logged -106dBm. My phone even went to 1x (xRTT).
My phone is constantly changing from -101(dBm) and -106(dBm), constantly jumping between Cell Locations and reporting Physical Link Down. My TWAS (Time without a signal) was 61% for 1h 7m. I'm also less than 1/2 mile from a VZW tower.
Speed Test #1 was 159kbps D/L and 224kbps U/L.
Speed Test #2 was 118kbps D/L and 365kbps U/L.
Speed Test #3 was 50kbps D/L and 469kbps U/L.
Something is definitely not correct with the cell signal strength reporting on the Fascinate.
What if the phone's software is reporting a higher signal than what is actually being received and this incorrect information is being used to make operating system/network connectivity decisions? Might this cause all types of issues from lagging, slow data performance and bad battery life? I find it very strange that all three signal strength measurements are reporting different values.
What if a significant number of Fascinates have cell strength issues, wouldn't this support some type of "electronics lemon law"?
I am on my second Fascinate and both have exhibited the same symptoms. My wife's Fascinate is having issues too.
Other Samsung Galaxy S phone users don't seem to be as vocal about the battery, cell strength and lag issues. This makes me wonder if the Fascinate really does have a design/hardware issue. To top it off, the Fascinate is one of the last Galaxy S phones to receive Froyo. Maybe the supposed "issue" is causing problems with the developer testing of Froyo?
Just thinking things through,
Tim