I never stated we’d not see updated binaries. My point in example: We have 4.0.3 AOSP code right now. But *no* OTA from which to pull 4.0.3 binaries from. (Amazingly, we have no 4.0.4 code…but binaries for 4.0.4…)

It’s messed up…and always has been, but now there is more reason to fear that the AOSP code will hit and we will still be working with older binaries until VZW/Sammy release them. If VZW/Sammy delays the binaries multiple AOSP releases, we could see some pretty major incompatibilities. (I am not saying this *will* happen)

Example again: 4.0.3 came and went…no Sammy/VZW update. 4.0.4 gave us an update (leaked…)..but what if they’d waited until 4.0.8? AOSP would have dropped source for all builds in between…but we’d be using 4.0.2 binaries to run ‘em all. (Again, I am not saying this *will* happen, just stating how being at the mercy of manufacturer/carrier isn’t the land of roses and honey everyone seems to be trying to insinuate here…)

Thanks.

“Google won’t give us the means to easily build new ROMs from source, so the best thing to do is go get a completely closed phone that will never be open source.”

…which still sucks to varying degrees and could introduce…issues….but I suppose it is better than nothing.

(Actually, it doesn’t seem all that different from the Fascinate.  We’d be stuck with old drivers that we’d have to hack the hell out of AOSP to support until we got some newer binaries from an actual *release*.)