What's new
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!

OFFICIAL FRG22D OTA patch is here. DOWNLOAD NOW!

After the official FRG01B update, other app updates no longer advise what permissions are required. Anyone know how to reinstate that? The only conspiracy I worry about is what Google wants with all my info. LOL
Yeah, I noticed that too -- but I think they only advise with the updates if the permissions have changed.
 
Hey Fur,
Thanks for putting the manual install info all in one place.

Sorry if this has been asked previously, but if we manually install, will the OTA attempt to overwrite it, or will it just not attempt? This is key for me, as Verizon *could* update the patch before they push it, and if so, I'd want the latest.
If the ping that's used to read your phone for updatability is different enough that it sees your version as "wrong" it will attempt to overwrite it. However, the worst this would really do if you're running stock is realign you with the official build and follow it with the other update. I haven't heard of anyone getting an OTA push after installing this update, unlike the one P3Droid released. That non-stock kernel he put in it seems to have been what was causing the foul-up.

So, in short, if the update is updated you'll get the new update because anyone who got the old update would require an update to their phones so they're running the latest official build. Hence another update would hit them.


Took the words right out of my mouth FBM... sort of.

I was going to post that if you do manually update using the "Official" file off of Googles servers and for some reason VZW changes the file to a different one in the push you can rest assured that once someone gets a true OTA straight from VZW there will be a hundred developers checking out the code to see if it is in fact the same as the one we are using currently (From Google) then it would just be a matter of updating again should the actual release be close enough that it would not automatically get pushed to a manually updated phone.


Or is that what you just said?:)
Mas o menos, sí.

I also flubbed and left out a word or two in there along the lines of "when Verizon/Google pings your phone to check to see if there are any updates, if it sees that your phone isn't running the latest official version..."

Sorry, going on very little sleep and I'm so stiff and achy I'm moving like an 80 year-old after a motorcycle accident today.
 
After the official FRG01B update, other app updates no longer advise what permissions are required. Anyone know how to reinstate that? The only conspiracy I worry about is what Google wants with all my info. LOL

I think it tells you on new installs, and if an update changes the list from the earlier version.

If I've already agreed that DroidBoobs 4.6.2 is allowed to access my location, do I really need to agree that the 4.6.2.a update is also allowed to do that?

And of course you don't need a conspiracy theory on why Google wants your information. They want it to take over the world. Duh.
 
I believe "take over the world".

I always got permission requests even with installed app updates. My daughter also has the Droid and updated manually and hers still asks. I avoid apps that want to much.
I've avoided Maps updates but it doesn't even mention the permissions now.
 
I believe "take over the world".

I always got permission requests even with installed app updates. My daughter also has the Droid and updated manually and hers still asks. I avoid apps that want to much.
I've avoided Maps updates but it doesn't even mention the permissions now.
So uninstall and check the new permissions. My ROM lists which programs have which permissions so I can go check it out at any time.

And taking over the world is my bag, Pinkie! ;)
 
I believe "take over the world".

I always got permission requests even with installed app updates. My daughter also has the Droid and updated manually and hers still asks. I avoid apps that want to much.
I've avoided Maps updates but it doesn't even mention the permissions now.

The maps that came installed on the phone likely allows the same permissions as the updates. The original installed apps just don't ask you if it is OK. Look at manage applications in settings to see if the original already assumes all the same permissions.
 
Sorry, going on very little sleep and I'm so stiff and achy I'm moving like an 80 year-old after a motorcycle accident today.

What happened? Are you OK?

Gotta watch those cage operators out there! One reason we stick to the woods on the Dual Sports and the back roads on the HD.
I'm fine -- I was saying I was moving like someone who, at age 80, was in a motorcycle accident. :) When I woke up this morning I was stiff, sore, and I couldn't even make a fist, let alone walk normally. Had to cancel my plans to go to the State Fair because of it.

Thanks for the concern, though! :D

Back on topic -- I now have proof that among the other things this update does not do, it does not prevent sore and aching joints first thing in the morning.

:icon_ banana:
 
Thanks to all.

OF, what an eye opener. Is there a way to uninstall the apps that come with the phone like Goggles and Twitter, etc?
 
Im a dudette....and i'm sick of verizon's bull kaka.. don't need to be told manual is available. Its not about that. Snark elsewhere, svp. :)

You're not alone, Sal, and you're right, it's not about knowing there's a patch available to download manually.

It's been nearly 52 hours since a report came in that "I have an OTA update sitting on my phone this morning..." The image that accompanied it is and was also avaliable elsewhere in internal VZW/Moto/Google documents. That report was received only here in this thread and not in any other thread or forum anywhere. No one else anywhere on the Web has reported getting a live FRG22D OTA from VZW servers. Something smells fishy.

What I can say is what others who have loaded this patch have said. It runs nicely. In my mind it runs better than any leak that I've run before, and although I'm not convinced yet that it is *the one and only* official build that will be used by VZW in their OTA sends, I am convinced it's something official since it is on Google's open website... And I'm extremely glad to have it on board for now.

Again, though, it's not about that.

We still don't know a lot about the actual VZW OTA. This is like every other OTA that Verizon has done, it's a step forward and a few steps backward for a while as they get every piece together. As a career software developer, I have to admit that I'd rather pull something out of production and get it right, then deploy it to 3 million users in a bad state and get that many complaints -- even though delaying or pulling an OTA out of production is extremely embarassing. My user support people would hang me if I knowingly let serious problems be installed on this many users' systems.

From my standpoint, I've got plenty to play with while we all wait to see what happens. But I still need convincing, and the only way that will happen is when I see the VZW OTA servers churning out thousands of final Froyo updates to the Droid1 community. And then I'll want to see what that update has in it.

:)


Yeah, you totally get me on this. I'm less interested in the state of my own Droid -- which is just fine at the moment, with 1st wave froyo -- as in why a communications giant like Verizon does such a poor job of, you know, communicating. Accuracy, immediacy, and thoroughness are alien concepts -- and there's just no reason for it.

Got an update? Cool. Give us details, a date range and then do that. If you can't, no sweat, just tell us what's happening and what the new target dates are. Furthermore: Give us lots of info so we can decide when/how we want to upgrade hardware. Twitter is available day and night.
 
Back on topic -- I now have proof that among the other things this update does not do, it does not prevent sore and aching joints first thing in the morning.

:icon_ banana:

I am sick and tired of people making wild claims about how broken Froyo is. Just because it hasn't helped YOUR sore and aching joints first thing in the morning, doesn't mean it won't help MOST people's sore and aching joints first thing in the morning.

Some people just don't understand simple logic.
 
Yeah, you totally get me on this. I'm less interested in the state of my own Droid -- which is just fine at the moment, with 1st wave froyo -- as in why a communications giant like Verizon does such a poor job of, you know, communicating. Accuracy, immediacy, and thoroughness are alien concepts -- and there's just no reason for it.

Maybe they're just gathering data on who installs these things OTA, and who installs by various other routes.

After all, 99% of Droid owners probably have no idea an update is coming, and in a few days, they'll be like "Oh look, a new update. Guess I should install it. Pass me another donut please."
 
Thanks to all.

OF, what an eye opener. Is there a way to uninstall the apps that come with the phone like Goggles and Twitter, etc?

Rooting, I'm afraid, is pretty much the only way to uninstall most of the bloat.

I am sick and tired of people making wild claims about how broken Froyo is. Just because it hasn't helped YOUR sore and aching joints first thing in the morning, doesn't mean it won't help MOST people's sore and aching joints first thing in the morning.

Some people just don't understand simple logic.

True. I should have put YMMV in there. ;)

Now I wonder if the vibrator app on my phone would help relax my sore neck.
 
Back
Top