This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
I get the impression that Verizon *is* simply pushing each OTA to every Droid. There's too much "unofficial" variety for them to be worrying about what build every phone has on it.
I'm running P3s FRG22D and it's definately *not* based on the 1.6MB update that was described with Verizon's memo. Based on size (76.4MB) I suspect P3s FRG22D is more of a complete update, more of the form of the FRG01B and FRG22 that were out earlier, that had everything in them so you could do a complete install.
One thing that we should all recognize here is how hard it is for any company to do an OTA of the scale that we're talking about. This appears as a circus to us here because we're ahead of the companies involved with the builds we're using, but we've got to remember that the leaks and ROMs we use are not supported by anyone but ourselves -- there is no "official" customer service among us hackers...
Verizon on the other hand is testing and tweaking based on their business needs, including how they will support the OTAs in their customer service departments. So for them to release mutliple OTAs, to tweak a build without changing a build number or to release and then pull back an OTA is all fair game in trying to make sure they can support what they sell.
I'm liking P3's FRG22D today, but it wouldn't surprise me if the 1.6MB OTA build that Verizon's memo discusses is something significantly less that this. It will be interesting to see if this OTA build is actually named FRG22D.
I got the same thing right after installing p3's frg22d. I dunno ether... It does seem weird. Maybe vzw is looking for something other than just the biuld number to push the update. Or maybe they are pushing it to every droid no matter what the build number.