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!

Motorola Droid Maintenance Release Prelude to Android 2.1

hmmmmmm....this just seems to be way too easy or somethin...and none of the mods or anybody else has really commented on this...would u be kind enough to post that link to alldroid man? i would just like to read through that discussion over there....I'd appreciate it...
 
FYI Got the OTA on this past Monday and my build is ESD56!
Interesting. Perhaps 2.1 is ESD59?

hmmmmmm....this just seems to be way too easy or somethin...and none of the mods or anybody else has really commented on this...would u be kind enough to post that link to alldroid man? i would just like to read through that discussion over there....I'd appreciate it...
AllDroid - View topic - 61MB Maintance updated being pushed out
 
For the record I started that thread there linking it to here in hopes that one of the guys there would post a link to the OTA update :-P
 
FYI Got the OTA on this past Monday and my build is ESD56!
Interesting. Perhaps 2.1 is ESD59?

hmmmmmm....this just seems to be way too easy or somethin...and none of the mods or anybody else has really commented on this...would u be kind enough to post that link to alldroid man? i would just like to read through that discussion over there....I'd appreciate it...
AllDroid - View topic - 61MB Maintance updated being pushed out

thanx!!!! :)
 
Well i took the bait, downloaded and installed it. Like everyone else that got the OTA i see no difference. No issues here.

Did u install it properly? like from the recovery menu? And is ur build # still ESD56?

The files in update.zip all have modification dates of 2009-05-04 and build.prop contains the following info. Look at Build ID and Version release and build date. I think you might have installed an early 2.0.1 build instead of the update we're waiting for:

ro.build.id=ESD56
ro.build.display.id=ESD56
ro.build.version.incremental=20996
ro.build.version.sdk=6
ro.build.version.codename=REL
ro.build.version.release=2.0.1
ro.build.date=Wed Nov 25 17:42:57 PST 2009
ro.build.date.utc=1259199777
ro.build.type=user
ro.build.user=android-build
ro.build.host=android-test-10.mtv.corp.google.com
ro.build.tags=test-keys
ro.product.model=Droid
ro.product.brand=verizon
ro.product.name=voles
ro.product.device=sholes
ro.product.board=sholes
ro.product.cpu.abi=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=sholes
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=voles-user 2.0.1 ESD56 20996 release-keys
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0.1/ESD56/20996:user/release-keys
 
It would be nice if someone who is getting the update could figure out how to share it and view it to see if it is just a refresh of 2.0.1 or if it has anything newer in it.
 
I retract what I said about build.prop. Compared it to what's on my phone and the info is the same. Still odd that the update.zip would have file modifications all from May, 2009. Oh dwell....
 
The files in update.zip all have modification dates of 2009-05-04 and build.prop contains the following info. Look at Build ID and Version release and build date. I think you might have installed an early 2.0.1 build instead of the update we're waiting for:

ro.build.id=ESD56
ro.build.display.id=ESD56
ro.build.version.incremental=20996
ro.build.version.sdk=6
ro.build.version.codename=REL
ro.build.version.release=2.0.1
ro.build.date=Wed Nov 25 17:42:57 PST 2009
ro.build.date.utc=1259199777
ro.build.type=user
ro.build.user=android-build
ro.build.host=android-test-10.mtv.corp.google.com
ro.build.tags=test-keys
ro.product.model=Droid
ro.product.brand=verizon
ro.product.name=voles
ro.product.device=sholes
ro.product.board=sholes
ro.product.cpu.abi=armeabi
ro.product.manufacturer=Motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap3
# ro.build.product is obsolete; use ro.product.device
ro.build.product=sholes
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=voles-user 2.0.1 ESD56 20996 release-keys
ro.build.fingerprint=verizon/voles/sholes/sholes:2.0.1/ESD56/20996:user/release-keys

Same thing I see with that Update file, weird!
 
Anyone with VZW experience (Miami, perhaps) know if the order we get this "phase 1" patch in correlates to the order that we'll get the final 2.1 update? In other words, if we were one of the first wave for this update, does that mean we'll be in the first wave for full 2.1 release?
 
Back
Top