Here's what leads me to think so: when I run 3G only, it's perfect. No problem with the antenna or reception at all. 4G isn't as widespread so a lot of users aren't even using it. As for those that are, I think that most of them are in here. I had a previous SGN that was moderately better than my current phone, but candidly, it was pretty terrible also considered to pure 3G. The issue is such that we get a FULL 4 bars on 4G, then it goes grey, then I lose connectivity, and then it often never comes back on to 3G or 4G until I enable and then disable airplane mode. At that point, connection is back to four bars and works perfectly. To me, it just appears to be related with the coding for signal degradation. Then again, I'm not saying it with 100% certainty, just a reasoned hunch is all.
But see none of that makes me believe it's software. I, too, was having the signal drop (both voice and data) with 4 solid bars in a strong (nowhere near the edge of 4G or an extended 4G) area. I don't think it's related to the signal strength at all. I think there's a bug in the radio (or maybe radio firmware - so pseudo-software) where if a certain condition happens on the tower or the connection to the tower, the modem freaks out and OS resets it. I don't remember if it was this thread of the one in the general nexus forum, but I posted the dmesg output that corresponded to the drop, and the kernel was clearly doing a hardware re-init of the device. I don't know why, in a strong area, a software problem would cause the kernel to actually hard reset the device.
To me it seemed more like:
- connection fine
- some boundary condition or problem the radio can't understand, so it returns a weird status or no status
- OS waits a bit for it to recover
- radio/modem does not recover, so the OS sends a reset signal to it and all radios/modems
- after a brief period, radio comes back up and connects
When this happened to me, it always came right back on its own with in 30-60 seconds. Never did I get stuck without voice and data, requiring a reboot or airplane mode toggle. Not sure if that is significant data in this problem or not.
Hopefully it IS a software problem, but unless Verizon/Google/Samsung are seeing a lot of reports of the issue (which is why starring the google bug report is important!), it's probably going to go unfixed.
On the other hand if it's partially or totally a hardware problem, again if V/G/S are unaware of it, they probably will not replace it under warranty or they will send it back untouched claiming it is fine. Speaking of, how exactly does Samsung test it? it's not like they have a large LTE network running on Verizon's spectrum to test, right? I'm sure they have a lab with it emulated or something, but if it's related to or triggered by something
Verizon is doing, how can we ever hope to have Samsung reproduce it and acknowledge the problem?
