Asterix - the link you had to droid forums to go from FRG01B to FRG22, does that mean you're now rooted or you just did what a true OTA update would've done?
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
[How-To] Force the Official Android 2.2 Froyo Update for the Motrola Droid (FRG01B | Update 1 of 2)
- Thread starter Trident
- Start date
-
- Tags
- motorola droid
Asterix - the link you had to droid forums to go from FRG01B to FRG22, does that mean you're now rooted or you just did what a true OTA update would've done?
huff825
Newbie
Anyone having problems with launcher pro after 2.2 update? Every time I hit the home button, it goes back to the stock home. Can't seem to make it stay. Tried keep in memory in preferences which did not work.
Found my own solution, download ClearDefaults app., that will give you the option to save Launcher Pro as the Default. Hope that helps someone else.
Found my own solution, download ClearDefaults app., that will give you the option to save Launcher Pro as the Default. Hope that helps someone else.
I've been running FRG01B for two days now with no problems beyond icons for apps moved to the SD card randomly disappearing and reappearing in GDE. Bluetooth and Flash are working just fine. Network connectivity has been solid, too. Exchange email works better with our 2007 server than my company-issued Crackberry with BES.
I can't find a thing to complain about overall. I loaded 2.2 from my netbook to a stock, non-rooted 2.1 update 1 unit.
I can't find a thing to complain about overall. I loaded 2.2 from my netbook to a stock, non-rooted 2.1 update 1 unit.
wrstone
Newbie
i should be clear: I have absolutely no connection with Verizon or Motorola -- I'm a customer just like everybody else. I have no idea what they're doing beyond what they tell us.
That said, I'm also a systems administrator who's dealt with bugs like this before. You really don't want to know how often updates get into your favorite Web sites, only to be pulled within half an hour because they were buggy. It happens -- just part of the business.
So if you look at it from the perspective of the problem, the answer becomes clear:
Given: FRG01B contains a buggy networking stack that unpredictably affects some small percentage of users.
I'm absolutely certain the networking stack is involved, based on my years in the industry. It just screams networking problem.
We can be fairly certain that the number of affected Droids is small. It's not scientific, but anecdotally the number of people reporting problems seem to be small. The problem is just so intrusive that we've been very vocal.
Unfortunately, just because some small percentage are currently affected is no guarantee that it would remain so. By the time the upgrade was fully deployed, it could be 75%. Maybe it could be only 3%. There's no way to know.
The buggy code, however, is contained in 100% of the FRG01B upgrades, whether any individual Droid is impacted or not.
On the remote chance that it's 75%, Verizon had no choice but to halt the FRG01B upgrade. The first step in solving the problem was to stop causing it.
Furthermore, because of the nature of the problem, it was absolutely imperative to stop it. If the Droid couldn't connect to the network reliably, there would be no way for Verizon to push a fix over the network.
The next problem is that now some small number of users have build FRG01B.
There are a couple of ways this could be addressed. The way Verizon/Motorola chose to address it was with an FRG22 patch.
I should be clear, here: when I say "FRG22 patch", I mean a patch. It's not a major upgrade as the pushed FRG01B was. It is a patch to FRG01B that brings the build revision to FRG22.
We know this because Verizon has told us that in order to apply the FRG22 patch, the Droid must already be on FRG01B. If it wasn't a patch, it wouldn't matter if the user was on 2.1 or FRG01B.
This choice wasn't without merit: if the issue is frakked-up networking, it's far more likely that a small patch will make it to the Droid than an multi-megabyte upgrade.
What everyone who got FRG01B needs to end up with is FRG01B + FRG22-Patch = FRG22.
Everyone on 2.1 simply needs FRG22.
What's pushed to the two groups must be different. One is an entire upgrade while the other is only a patch to an existing system.
Logically, there's really no other way to deal with the problem. Two groups, two different upgrades at this point.
As I say, the bug seems to have bitten a minority. However, just because you weren't bitten doesn't mean the bug isn't there. It just means that some other factor is impacting your Droid and consequently your networking is reliable.
For all I know, the first thousand cases of Droids shipped out of China were pushed .002nm too deep on the motherboard: now they're all a little more heat-sensitive. An increase in processing caused by the 2.2 upgrade means more heat, means more dropped packets. Combine this with a slight bug in the networking stack and you have a recipe for disaster on those Droids.
Maybe no such thing happened. It could be a hundred other things, none of which is very predictable.
Doesn't matter in terms of solving the problem, though:
Current FRG01B users need a patch: FRG01B + FRG22-patch = FRG22.
Current 2.1 users need just need FRG22.
Did I say versioning could get hairy? I'm glad I don't work for Motorola or Verizon right now. I can only imagine all the conversations: "Wait, upgrade FRG22 or FRG01B+FRG22? Patch or not-patch? For 2.1 or 2.2?"
I guarantee you that everyone in their IT departments are correcting themselves every few minutes.
Bill Stone
This is fun. There are groups of Noobs and Professional's who have difficulty communicating. I am a Noob and would like some clarification:
1. The OTA FRGo1b zip from Trident; if installed am I rooted?
2. I assume the Droid Forum post from 6/6/10 about FRG22 is for root users?
3. When the official FRG22 is released Trident will post instructions?
If someone could answer yes or no to these three questions I would greatly appreciate it.
1. The OTA FRGo1b zip from Trident; if installed am I rooted?
2. I assume the Droid Forum post from 6/6/10 about FRG22 is for root users?
3. When the official FRG22 is released Trident will post instructions?
If someone could answer yes or no to these three questions I would greatly appreciate it.
yeah, quiet a bit different.
When first plugged in:
when brigness turned down (new brightness button looks like a sun half shaded):
Then after left idle for about 5 minutes (time bounces around the screen):
I have a question I have a "weather information currently unavailable" message in the corner where the weather should be. I went into location and security and checked off GPS to see if it would work. It didn't. any suggestions?
I did the FRG01b update the other night on Droid1, stock 2.1; all seems well but have noticed a few minor things. I know some have posted a link to droiforums.net to get FRG22. If you scrool down to the section that says goig from FRG01B to FRG22, it sounds just like what I did to get FRG01b. If I do what it says there, does it mean I'm rooted? I don't want to root.
http://www.droidforums.net/forum/dr...royo-step-step-installation-2.html#post528613
If I leave the phone as is, will I get any VZ update that gets sent OTA or will I have to manually install FRG22 like I did FRG01b?
Also, I noticed someone said ATK was "fixed" for 2.2, but I thought most people are saying task killers are not necessary even wasteful.
Thoughts/ideas?
http://www.droidforums.net/forum/dr...royo-step-step-installation-2.html#post528613
If I leave the phone as is, will I get any VZ update that gets sent OTA or will I have to manually install FRG22 like I did FRG01b?
Also, I noticed someone said ATK was "fixed" for 2.2, but I thought most people are saying task killers are not necessary even wasteful.
Thoughts/ideas?
jonsquared
Lurker
Froyo's not playing nice with my Ford SYNC Bluetooth media streaming. When using Slacker radio before I could use my steering wheel controls (forward button to skip to next song). Doesn't work anymore. Also getting audio skipping now. I paired again but no change.
In addition I get a long pause going to and from home (painfully slow).
Only strong positive I've noticed is faster browsing.
Hopefully OTA update will correct.
In addition I get a long pause going to and from home (painfully slow).
Only strong positive I've noticed is faster browsing.
Hopefully OTA update will correct.
johnlgalt
Antidisestablishmentarian
The problem is that most here have not been in those hairy situations time and time again b/c they are sysadmins / assistants of any type. You obviously have been, and so have I, but the multitudes here (I'd venture) are command-line illiterate, much less savvy about how this stuff works in the real world.
Still, thanks for putting it so clearly and succinctly. I only hope people will actually read your post and take it to heart.
Just did my upgrade and it is FC a lot of internal apps like launcher and every press takes like 10-30 seconds for anything to happen.. Tried restarting several times and each time it goes back to taking forever to open an app or click on a setting.
Used the first link to DL and again the install went flawless. no errors other than the very first expected one.
Any ideas???
Used the first link to DL and again the install went flawless. no errors other than the very first expected one.
Any ideas???
There are both rooted and non-rooted (clean / virgin / Odexed) versions of all the Versions out there. Problem is, though, that, in order to use Recovery, I thought you needed to be rooted?
At any rate, check out Peteralfonso.net - he has a repository of all the files there. De-odexed files are the ones that have been manipulated (and thus have root and such), whereas Odexed are the untouched ones.
Thanks for your input/thoughts. I did the OTA update to FRG01b, I think. I didn't do anything special, just d/l the file, rename to update.zip, then booted with finger on the X and "applied" it. A few q's:
1. should I d/l the FRG22 and apply like the instructions on droidforums.net?
2. If I don't do #1 (or if I do), will I still get OTA updates from VZ? I thought Trident or someone said to apply FRG22, you have to have FRG01b?
3. Your thoughts on task killers?
At any rate, check out Peteralfonso.net - he has a repository of all the files there. De-odexed files are the ones that have been manipulated (and thus have root and such), whereas Odexed are the untouched ones.
Thanks for your input/thoughts. I did the OTA update to FRG01b, I think. I didn't do anything special, just d/l the file, rename to update.zip, then booted with finger on the X and "applied" it. A few q's:
1. should I d/l the FRG22 and apply like the instructions on droidforums.net?
2. If I don't do #1 (or if I do), will I still get OTA updates from VZ? I thought Trident or someone said to apply FRG22, you have to have FRG01b?
3. Your thoughts on task killers?
johnlgalt
Antidisestablishmentarian
Are you saying you tried applying it twice, or just once? If just once, hell, try again. You should not be having such issues, but just in case you are, a battery pull might not hurt.
1: Sure. Or you can get the files from Pete's site as well, although if I were you I'd stick with P3's from the site you linked to - IIRC, it already has Busybox, which Pete's does not.....
2: Well, since FRG22 is what the OTA is going to, probably not - but there is a small likelihood that *everyone* will get a notification for the final 2.2 OTA, b/c I was running Pete's BB 0.4 and *I* received the notification for the 2.2 first OTA last week.
For future OTAs, you should receive notifications.
3: There is a whole school of thought on how you don't need them and I tend to agree - however, I keep one installed b/c 1) I bought it, and 2) for those Justin Case moments (sorry for the play on words).
Android is pretty efficient at managing your memory, and killing apps that automatically load actually slows performance, b/c temporarioly your phone is faster while you're doing something, and then it slows again as it continues to do what you're trying to do *and* starts re-loading those apps that were running in the background. If there are apps you don't want running at all, you're better off uninstalling them.
If they are system apps, like Corporate email, then you're better off learning how to root and removing them yourself so they won't auto run.
Another theory would be to look into AutoStart apps and configuring those, if possible (never tried it myself).
Ummm, no, b/c Facebook is an app that you install from the market - and the last two updates from market were made this past week. After this version was already primed and readied for release.