[Verizon Samsung Galaxy S III] TheAnarchist1:
Tekhna: I would not be led to place such blame upon CM10 per-say though. If the build were to be outright 'buggy' as in pure CM10 bugs, and not facilitated by fluctuations in hardware quality, then common sense would warrant that every CM10 user on this particular device would have rougly the same issues, such as NFC, which is shot for EVERY person without the fix posted in the OP now. The quirk is though, that many people are experiencing many different bugs, which leads me to believe that 'user error' and hardware fluctuations in quality are more or less to blame.

I more or less agree with you on the significant contribution of 'user error' (which even I am guilty of) such as the varying states of installation form ie: some dirty flash, others clean flash, some use custom kernels, others use old radios, some neglect to acknowledge that RPM files even exist, etc, and other users simply not being as 'technologically apt' as others to blame for many of the bugs that individuals may or may not be experiencing in their builds.

With all of this stated though, so becomes even more clear, the reason that CM Devs do not peruse these forums listening to us, or take bugs without a proper logcat submission and having gone through the 'process' of bug submission. One would be led to believe that this particular version of CM10 was practically unusuable if they kept up with this forum and continued to read through all the pages, when in reality, with the proper NFC patch, and tethering patch, for all intents and purposes, this is a daily driver.

No hard feelings though, and no blood in the water. You are totally right Tekhna, all discussion and all fun! Its Android, its open source, its a hobby and a love, not an obligation or a war call! Hahahaha

PS: I feel semi-trollish with this post....bad me -slaps own hand- :o

---------- Post added at 12:35 PM ---------- Previous post was at 12:14 PM ----------

Restola: I am beginning to wonder if Touchwiz infused Android, and CM10 AOSP sourced Android read signal differently. I remember from the Galaxy Nexus days that VZW claimed that AOSP read signal more accurately then 'skinned' proprietary Android builds such as the Rezound Sense builds or Touchwiz based builds. I personally believe, after owning the phone for a year, that the Galaxy Nexus simply had a sucktastic internal radio, but I also subscribed to the belief that AOSP and proprietary Android builds do read signal differently to a certain extent. Perhaps AOSP Is more accurate, or Touchwiz JB is more generous? I have noticed on AOSP that if my signal sucks, then it performs the proper shift to 3G (though I virtually NEVER touch 3G) and the moment I get into a stronger area, it shifts back properly (98% of the time). Touchwiz based Android roms, at least in my experience, tend to 'hold' the appearence of a weak LTE signal until you actually do something that requires data such as hop onto browser, and then it completely bottoms out, at times not even returning to LTE if I am in a full bar roughly 97dBM area. I am not totally sure that we are really gaining, or losing signal on either AOSP or Touchwiz based roms, but rather one is less generous in the LTE threshhold then the other. As for signal 'holding' and not restoring when you get to a strong LTE area, well that has a LOT to do with the age of your sim card, whether your modem or RPM flashed correctly, or even on a broader sense...the quality of the signal from your local VZW towers, which do fluctuate from day to day. Either way, I believe that we are all essentially getting the 'same' signal, but the appearance of different readings because of differences in the the two builds. Either way though, all speculation...

PS: I feel LESS troll'ish' in this post! LOL