Well, the biggest thing about this update is the ability to get Flash from the Market. You can always add it yourself; there are links on this site for that.
DroidForums.net | Android Forum & News
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!
Second Android Update 2.2 Froyo (FRG22 Rolling) Out Now
- Thread starter Shadez
- Start date
Well, the biggest thing about this update is the ability to get Flash from the Market. You can always add it yourself; there are links on this site for that.
furbearingmammal
Super Moderator
Yeah, I can see why you'd do that instead of setting it to on-demand in the settings so you still have it but don't have to use it.
Yeah, I can see why you'd do that instead of setting it to on-demand in the settings so you still have it but don't have to use it.
Even though you smiled the rolleyes came through.
MotoCache1
Chief Droid Scientist
I just went ahead and put P3Droid's FRG22D leak on in the hopes that I'll immediately get the "full" FRG01B package sent down as well. I want to take a look at it and I haven't seen it posted yet...
Yeah, I can see why you'd do that instead of setting it to on-demand in the settings so you still have it but don't have to use it.
Where are those settings? Is it in the browser?
Bear in NM
Active Member
A couple of points.
First, P3 has never let us down in the past. His leaks are just that, leaks (hey CK you gave up too easy). But, if you understand the way the process works, these files are sent to folks who test and report. If they pass muster with all of the players, then they get sent OTA. If they fail, then they get updated at the source, assigned a new build number and then resent for testing. In this process, CZ and P3 have a source who leaks these files to them. Perhaps not what will OTA, but a release candidiate none the less. This is the situation with the first frg22 that many of us are running. If you look at P3's presence on the other board, it becomes pretty evident that the only reason that he would alter the file and report it as something it is not would be for fame or money. If he were to do this, it would be the last "android" thing that he ever did, publicly, as the tar and feathering would be pretty severe. I have a real hard time believing this theory.
Now, will this be the frg22d that verizon OTA's? Could be, and I would say that if Verizon says the OTA will be a file labeled frg22d, then likley this is it.
Now, back to Flash. If you remember how many of these OTA type files work with the market, then you will understand that Moto/VZW has to make the source available to the development world, prior to the OTA. The way this works in theory is that once the source is released to the app world, then the app developers are responsible to get their programs up to speed, so that they will be available for us. In theory before we get the OTA.
Here is where I am a little fuzzy. The N1 see's flash in the market. But, the N1's files are different than ours. I could easily understand that the folks at Adobe (and all of the other apps) will have to do some "stuff" on their end for market to link our phones with their apps. Perhaps it's an API build number, or some other thing that will read the frg22d footprint correctly.
It is very likley that this file is just like all the earlier leaked "source" files in that when you get the leak before you are intended to have the leak, and perhaps before the source has been dropped to development, you will have some things not work (market speaking), like Flash, or Homerun Battle, etc. Folks, think back a few months, and perhaps your perspective might be changed.
So, does anyone know whether the source code has been dropped to the development world? In the past, this was the cue that the OTA was coming, and what you might call a clue as to what we have here.
Craig
First, P3 has never let us down in the past. His leaks are just that, leaks (hey CK you gave up too easy). But, if you understand the way the process works, these files are sent to folks who test and report. If they pass muster with all of the players, then they get sent OTA. If they fail, then they get updated at the source, assigned a new build number and then resent for testing. In this process, CZ and P3 have a source who leaks these files to them. Perhaps not what will OTA, but a release candidiate none the less. This is the situation with the first frg22 that many of us are running. If you look at P3's presence on the other board, it becomes pretty evident that the only reason that he would alter the file and report it as something it is not would be for fame or money. If he were to do this, it would be the last "android" thing that he ever did, publicly, as the tar and feathering would be pretty severe. I have a real hard time believing this theory.
Now, will this be the frg22d that verizon OTA's? Could be, and I would say that if Verizon says the OTA will be a file labeled frg22d, then likley this is it.
Now, back to Flash. If you remember how many of these OTA type files work with the market, then you will understand that Moto/VZW has to make the source available to the development world, prior to the OTA. The way this works in theory is that once the source is released to the app world, then the app developers are responsible to get their programs up to speed, so that they will be available for us. In theory before we get the OTA.
Here is where I am a little fuzzy. The N1 see's flash in the market. But, the N1's files are different than ours. I could easily understand that the folks at Adobe (and all of the other apps) will have to do some "stuff" on their end for market to link our phones with their apps. Perhaps it's an API build number, or some other thing that will read the frg22d footprint correctly.
It is very likley that this file is just like all the earlier leaked "source" files in that when you get the leak before you are intended to have the leak, and perhaps before the source has been dropped to development, you will have some things not work (market speaking), like Flash, or Homerun Battle, etc. Folks, think back a few months, and perhaps your perspective might be changed.
So, does anyone know whether the source code has been dropped to the development world? In the past, this was the cue that the OTA was coming, and what you might call a clue as to what we have here.
Craig
furbearingmammal
Super Moderator
Yup. Open the browser, get into the settings, then scroll down till you see "plugins" or something similar. Set it to on-demand and you're ready to roll.Yeah, I can see why you'd do that instead of setting it to on-demand in the settings so you still have it but don't have to use it.
Where are those settings? Is it in the browser?
For a similar experience on your PC, and you're running IE, well, best of luck to you. If you're running Firefox, go to the add-ons and download FlashBlock. If you're running Chrome and there's an option and you haven't found it yet, you're not geeky enough for Chrome!
Back on topic -- Everyone should be aware of this setting for when the update allows us to get Flash from the market so they don't have to deal with all the ads on the websites if they don't want to.
SnoDrtRider
Member
No what I'm saying is the reason everyone who is updating to the FRG22B is still getting update notices for FRG01G is that the 22B rollout has not officially started yet so the updater is seeing the wrong OS on the updated phones and knows that the current OFFICIAL version is 01B so it prompts the phone to update.
I think that this will continue until Verizon starts the official OTA or FRG22B
As far as p3s file source? It may be or is probably the real deal but I doubt anyone really got the OTA yet, if they did there would be at least a few people on here or MDW reporting the FRG22B OTA plus we would have a stock un-rooted update zip available for those who do not have or want to root.
It was a pre-release version of flash - what did I care? I've never been excited about getting it in the first place.
:
:Yeah, I can see why you'd do that instead of setting it to on-demand in the settings so you still have it but don't have to use it.
furbearingmammal
Super Moderator
Ah. I have a final build, so I'm set. I'm just hoping when Adobe and Verizon and Motorola and the MIBs working for the Illuminati finally let us have Droid-flavored Flash it'll let me watch some stuff on non-mobile-optimized sites as well as maybe play a game or two I've had my eye on.
infinity8x3
Member
On a short side note...
Isn't the flash that is going to be in the market for FRG22D supposed to be optimized for droids omap cpu? Apposed to the final that's out now that's optimized for the N1's snapdragon?
Isn't the flash that is going to be in the market for FRG22D supposed to be optimized for droids omap cpu? Apposed to the final that's out now that's optimized for the N1's snapdragon?
furbearingmammal
Super Moderator
MotoCache1
Chief Droid Scientist
And voila -- just like that 9046f5a3ec09.signed-voles-ota-45394.zip is coming down into my /cache folder. Yay!
SnoDrtRider
Member
Allow me to speculate and add more fuel to the fire...:icon_ poke:
Now this is total speculation on my part but what if...
Since the updates are "MANDATORY" if someone (or their device) refuses or blocks the update X amount of times the device is remotely shut down citing TOS violations?
Maybe it won't happen this time but with the way Motorola/Verizion are throwing up more roadblocks with each update possibly some thing to ponder in the future:icon_eek:
MotoCache1... I highly respect your opinion on the possibility of this.
Now this is total speculation on my part but what if...
Since the updates are "MANDATORY" if someone (or their device) refuses or blocks the update X amount of times the device is remotely shut down citing TOS violations?
Maybe it won't happen this time but with the way Motorola/Verizion are throwing up more roadblocks with each update possibly some thing to ponder in the future:icon_eek:
MotoCache1... I highly respect your opinion on the possibility of this.
