Second Android Update 2.2 Froyo (FRG22 Rolling) Out Now

[hookbill]

I'm not going to accuse anybody of anything, and thanks Bear In NM for your explanation of the change in the file name with the fix, however I still don't think a market fix should have been necessary.

I fully expect and believe that FRG22D will be the file released OTA and Ihave no doubt that it will be exactly as P3Droid has it now. It's just that nobody else has received it and the Market is still not prepared for it.

When Verizon sends it ota it will say FRG22D. That's what I want on my phone too.

 

[esaslaw]

All of this would be avoided if Verizon just explained what they are doing and when they are doing it.

The link to their site being posted is to the same page announced the original Froyo OTA (FRG01B), so that does not tell me anything.

 

[Bear in NM]

CK and JNT,

I agree the wording sounds like he got the OTA by the OTA method, but if you consider his usual method of getting the OTA file as leaked by CZ, and the situation with the C & D's for the X, I can also get a read where he got the OTA file, source not specifially defined (presumably CZ) and he is being a bit obtuse (or parsing as I stated), especially by not addressing the one direct question in the MDW thread. But I do agree his absence from the MDW thread, or specific clarification has cast a shadow on this. All I am saying is that I can see an explaination, albiet somewhat convoluted.

Craig

 

[xmguy]

So will people like me who have a custom rom that blocks OTA. Be out of luck to get access to the market. This sounds like what Sony did with the PSP when I had one. I had custom FW on it. But you could only access the PS store if you were running the newest FW.

 

[esaslaw]

Some of y'all need to relax a bit. The reason Moto/Verizon want to keep the phones up to date, running well, with the most current stuff available is so that when your contract is up, you stay with them since you like them and the way they service your 'phone.

To those of you who have elevated your Droid or any other 'phone to be the central guidepost of your life, this may not make sense. To the rest of us, it does.

Fur,

What makes no sense to me is why moto is spending any money at all trying to tweak a phone that is already at the end of its service life, and has been replaced by several new models. Throwing good money after bad comes to mind. There is the issue of perhaps rooted and broken phones hitting the bottom line, but I think most agree that the rooted folks make up a small percentage of the overall community. There was that little news item about VZW tech's getting bonused for spotting rooted bricks, so perhaps there is more to the supposition that we aren't that many.

If I screw the tin foil hat down real tight, perhaps I might suggest that as we have the romming/dev. community going crazy with an unlocked phone, perhaps VZW is taking the counter position by seeing what they can do from their side to an unlocked phone. Perhaps this is what you mean by proof of concept? Ooh, counter-intelligence maybe.

And if I dive down into my tin foil bunker, I can even imagine some programmer at VZW telling his boss, "hey, if we can shut down a big chunk of the hacking community that happens to be hacking our "old" phone, perhaps we can drive some of those evil hacking minds to go onto bigger and better things, like hacking pc's".

But as you noted, this horse is out of the barn, with no intentions on going back.

Craig

 

[cereal killer]

CK and JNT,

I agree the wording sounds like he got the OTA by the OTA method, but if you consider his usual method of getting the OTA file as leaked by CZ, and the situation with the C & D's for the X, I can also get a read where he got the OTA file, source not specifially defined (presumably CZ) and he is being a bit obtuse (or parsing as I stated), especially by not addressing the one direct question in the MDW thread. But I do agree his absence from the MDW thread, or specific clarification has cast a shadow on this. All I am saying is that I can see an explaination, albiet somewhat convoluted.

Craig

As long as the members here know that the build was NOT pushed out by VZW and will not be considered Official until then I'm good : )

 

[hookbill]

All of this would be avoided if Verizon just explained what they are doing and when they are doing it.

The link to their site being posted is to the same page announced the original Froyo OTA (FRG01B), so that does not tell me anything.

Well, you just have to have the correct link:

http://support.vzw.com/pdf/system_update/moto_droid.pdf

Verizon is clearly saying it is FRG22D. I don't know how much clearer they can make it - unless you want them to give you the specific time and date for your dorid.

 

[Bullitt6996]

Frg22d

Shadez, where is the indication that this update is FRG22?

Hook,

It says in the bigger print in the notice, FRG22D.dancedroid

 

[hookbill]

Shadez, where is the indication that this update is FRG22?

Hook,

It says in the bigger print in the notice, FRG22D.dancedroid

I think I'm aware of what it is now.

http://support.vzw.com/pdf/system_update/moto_droid.pdf

 

[Spyte]

furbearingmammal, believe that reference way back on page 8ish was from the Bible, something about the philestines. Would have posted this sooner, but 30 pages takes a while to get through. And to stay on topic, a big giant meh goes out to 22d. I can wait.

 

[Sal]

Just gotten this tweet a minute ago.

@VZWSupport: Verizon Wireless introduces a new software update for the DROID 2 by Motorola. The 2.2 update will roll out in batches. Enjoy!

 

[Sal]

Just gotten this tweet a minute ago.

@VZWSupport: Verizon Wireless introduces a new software update for the DROID 2 by Motorola. The 2.2 update will roll out in batches. Enjoy!

Would they roll ours and there's out at the same time?

 

[dwoid]

I agree that P3's wording is "interesting". But we've seen that before too. I don't think this is anything nepharious though, I think his sources are reliable enough to trust what he puts out. By virtue of the lack of an original "odexed rooted" version, I suspect that P3 is trying to avoid a C&D order by providing his leaked FRG22D version with significant value added. As such I dismissed the OTA relationship early on and have been enjoying P3's FRG22D since shortly after he released it.

P3's FRG22D is noticably smoother and crisper in operation than his FRG22 was. I've had no Market (or any other) issues and I only wiped cache on install. I am not seeing Flash in the Market yet.

Btw, I just rebooted and am now receiving another "Froyo 2.2 Update". At 76.9MB, I suspect it's just FRG01B again, but I'll do some file compares with it as soon as it's downloaded.

Does anyone know where the build number lives in the update .zip file?

 

[MotoCache1]

I agree that P3's wording is "interesting". But we've seen that before too. I don't think this is anything nepharious though, I think his sources are reliable enough to trust what he puts out. By virtue of the lack of an original "odexed rooted" version, I suspect that P3 is trying to avoid a C&D order by providing his leaked FRG22D version with significant value added. As such I dismissed the OTA relationship early on and have been enjoying P3's FRG22D since shortly after he released it.

P3's FRG22D is noticably smoother and crisper in operation than his FRG22 was. I've had no Market (or any other) issues and I only wiped cache on install. I am not seeing Flash in the Market yet.

Btw, I just rebooted and am now receiving another "Froyo 2.2 Update". At 76.9MB, I suspect it's just FRG01B again, but I'll do some file compares with it as soon as it's downloaded.

Does anyone know where the build number lives in the update .zip file?

Easiest thing to do is look at the filename. If it is 9046f5a3ec09.signed-voles-ota-45394.zip then it's just the "full" FRG01B.

 

[dwoid]

Yup, it's FRG01B, by the filename, and in the zip file, in META-INF/com/android/metadata, it pretty much confirms...
"post-build=verizon/voles/sholes/sholes:2.2/FRG01B/45394:user/release-keys
post-timestamp=1279140904
pre-device=sholes"

Like everyone else, still waiting with at least skeptical interest for the 22D OTA...

Easiest thing to do is look at the filename. If it is 9046f5a3ec09.signed-voles-ota-45394.zip then it's just the "full" FRG01B.