[sigh].......

[DaRkL3AD3R]

It does. And Google released "Jelly Bean Release 2" (4.2) a few weeks ago and 4.2.1 just came out a couple of days ago. My Nexus 7 is happily running 4.2.1, as are most Nexus devices (with the sole exception of the VERIZON Galaxy Nexus, which just received the original Jelly Bean 4.1 release a couple of weeks ago, AFTER 4.2 had hit the streets and months after Jelly Bean was on AOSP.

Google releases Android updates regularly. It's up to the third-party manufacturers and their carriers to update them. This is how it works. And Verizon has the unfortunate distinction of interfering with and delaying even Nexus releases, meaning they probably won't be given any more Nexus phones for a long time, if ever.

This.

I've come to the conclusion and realization that it's Verizon's fault. You can be a phone OEM, make this awesome update that's say 467MB and is guaranteed to work great on all Thunderbolt's out there, but at the end of the day it's Verizon who has to push it out over their towers to the users. I bet they are looking at the figures of just how small a population of users are that own the Thunderbolt and figure it isn't worth the effort. Thus end users get shafted.


Oh well getting my Galaxy Note 2 and saying screw it. I'm tired of the ROM business. I'm tired of trying to keep up with AOSP. Verizon Note 2 has legit root already and the stock ROM has the best feature set of any Android phone on the market. If Cyanogenmod could somehow make the S Pen work just as good on their ROM as it does on the stock TouchWiz then I may consider doing the ROM shuffle with the Note 2. But until then, !@#$ it.