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 FroYo Rollout Thread-Version2!****

I thought the larger file was captured after the pause in OTA updates as a improved OTA update by VZW, then packaged for manual updates???

Chris
 
New update?

well i woke up today, and my Droid had an update for 2.2! i have alot of friends with the droid, but im the only one with this update? any body else have this?
 
alot of users here have been getting the update. and i have also heard of reports off users being stuck at the motorola symbol at boot. :icon_eek:
 
the main thing stopping me from a manual update is i dont want to void my phones warranty.
It won't. It's the same file, installed in the same method, you just chose to do it yourself instead of waiting for the totally random update schedule to get around to you.

Cool, and I see there are two versions. a rooted and a non rooted. I think i want the non rooted version...thus keeping me stock? sorry im still new to this.

I think using the larger file is better, so where can I find that and instructions?
 
Confusion is understandable as this is a weird topic. There are two updates available; the basic OTA package that patches the existing OS in a traditional manner, and the other update that straight-up replaces it. There have been a lot of discussions over it in the circus thread.

http://www.droidforums.net/forum/dr...ircus-continues-frg01b-official-get-here.html

The testing and examination done by a couple of people has lead them to the opinion that the larger file does a cleaner install, with fewer problems, and if the OTA caused some issues like lag and force-close problems, the larger update has invariably fixed them. There have been a few cases of install problems, but it seems a lower percentage of those using either manual install than for phones getting the update pushed to them from Verizon.

This is THE issue that thus far has held me back from manually updating.

Some say to use this file, which is 76.91 MB: Free File Hosting Made Simple - MediaFire

Others say to use this file, which is 45.2 MB:
update.zip

Why EGGZACTLY are there two different update files of two majorly different sizes?
Where did each one come from?
Which one is being pushed out OTA now by Verizon?
Which one is recommended for manual update?

I had a G1 which I rooted, so I know how to apply this update. I have chosen to keep my Droid stock. But as I said, I don't want to apply the wrong update. Can someone clear up this confusion over two different updates floating around? I'm sure it must be confusing to others besides myself.

Thanks much!
The bigger file has more scripts in it and replaces the system data on your phone with all new code. This has caused far fewer instances of lags and force closes on the phones it was installed on, even those updating from a bad OTA update that didn't lock the phone up.

The smaller file comes from the Google servers, the larger one from a very respected member of the Android community, and has been inspected by several other members to vouch for it. The file is signed. That means it works with stock recovery images. It's impossible (or at least has been so far) to fake a signature for an install. That's some heavy-duty verification the file is legit.

The smaller file is being pushed OTA to phones as we speak. It uses less system resource on VZW's end and 99% of users probably wouldn't care if their phone never got updated, so if the update on their phones isn't perfect, whatever.

The bigger one is recommended for manual updates because the reports on here indicate the smaller file doesn't do as good a job of updating when averaged out when compared to the larger file. As already stated, and this is the really big part here that might swing you, the larger file has been used numerous times to clean up a bad install or a completely-corrupted system from the smaller OTA update package.

OK, furbearingmammal, you da mammal!! THANK YOU! for explaining that! really appreciate it! That is just what I needed. I just manually updated successfully, as it says I now have 2.2! Hubba hubba! :icon_ banana::icon_ banana::icon_ banana:

Haven't got a chance to check everything out yet, but it is working. :icon_ banana:

One question -- I read somewhere that in order to move some apps to SD card, that I need an application in the market, I believe it was called apps2SD if memory serves, but I can't find the app. Can someone please advise where to get that app so I can move a few large apps to SD, as I am getting low on space icon since the 2.2 update.
 
To move some apps to the SD card all you have to do is go to settings>applications>manage applications and then see which apps allow moving to the SD card. To move ALL your apps to the SD card you either need an app that may or may not be compatable with each app, or a ROM that allows force-installing to the SD card.

Apps2SD is native in Froyo, and the Android 2.2 SDK (software development kit) has been available to devs for a lot longer than even the rooters had access to leaked builds -- let alone source code -- but some devs haven't bothered to enable it (or have had trouble enabling it) for their programs. Of course, some apps in the market haven't been updated since Cupcake or Donut (Can't Google spell? :) It's Doughnut!), let alone Eclair, so YMMV with an app from the market.
 
This ANNOYS me to no end.

I have my original Moto Droid that I use every day and have yet to get the 2.2 force update.

I also have another Droid that I use essentially as a DroidTouch....
It just received the 2.2 update........
 
This ANNOYS me to no end.

I have my original Moto Droid that I use every day and have yet to get the 2.2 force update.

I also have another Droid that I use essentially as a DroidTouch....
It just received the 2.2 update........
Further proof that the rollout is totally random and may actually have some AT&T sympathizers directing the updates.

Half of that statement is true, half of it is false. A cigar (to be smoked by me) will be awarded to the first person to guess correctly if I'm full of it or not. :D
 
To move some apps to the SD card all you have to do is go to settings>applications>manage applications and then see which apps allow moving to the SD card. To move ALL your apps to the SD card you either need an app that may or may not be compatable with each app, or a ROM that allows force-installing to the SD card.

Apps2SD is native in Froyo, and the Android 2.2 SDK (software development kit) has been available to devs for a lot longer than even the rooters had access to leaked builds -- let alone source code -- but some devs haven't bothered to enable it (or have had trouble enabling it) for their programs. Of course, some apps in the market haven't been updated since Cupcake or Donut (Can't Google spell? :) It's Doughnut!), let alone Eclair, so YMMV with an app from the market.

OK, thanks much. I did that and went thru all my apps. Most of them can't be moved to the SD card, but enough of them could to create a fair amount of space on the SD card.

I ran Quadrant right after I got 2.2, and got a score of 868 with a bone stock Droid with about 170 apps, and I have maybe 6 or 8 widgets running. That is close to double, give or take, what I could get with 2.1 :icon_ banana: :icon_ banana: :icon_ banana:
 
This ANNOYS me to no end.

I have my original Moto Droid that I use every day and have yet to get the 2.2 force update.

I also have another Droid that I use essentially as a DroidTouch....
It just received the 2.2 update........
Further proof that the rollout is totally random and may actually have some AT&T sympathizers directing the updates.

Half of that statement is true, half of it is false. A cigar (to be smoked by me) will be awarded to the first person to guess correctly if I'm full of it or not. :D

Careful FB...'random' has both meaning and context...and I'm fairly confident I can prove the rollout is NOT explicity random. Still, I'd let you smoke the stogie, as I don't smoke. :) I agree that it's ATT's fault, though. :p
 
Back
Top