2.1 ESE53 will be Official Release on the VZW Motorola Droid
This is a discussion on 2.1 ESE53 will be Official Release on the VZW Motorola Droid within the Droid News forums, part of the Droid News & Site News category; **UPDATE on 3/18 2.1 Release**
As we move through the day more information begins to trickle in. The latest report comes from Phone Scoop. They ...
2.1 ESE53 will be Official Release on the VZW Motorola Droid
**UPDATE on 3/18 2.1 Release**
As we move through the day more information begins to trickle in. The latest report comes from Phone Scoop. They were contacted via email by Spokesperson Thomas Pica. Here's the latest:
In response to reports that Verizon Wireless had suddenly delayed its planned roll-out of the Android 2.1 update for the Motorola Droid, Verizon reached out to Phone Scoop. Spokesperson Thomas Pica said in an email, "The Android 2.1 upgrade for the Droid by Motorola was deployed to a small number of Verizon Wireless test users as scheduled. It is expected the broader phased rollout to all Droid by Motorola users will take place, but not just yet. No date scheduled yet." This message is essentially the same as the one provided yesterday by Verizon Wireless. Users should not expect their devices to update today or at any time during the next several days.
sadly i wont be returning to stock. bugless beast is so much better than this and all or the stuff on here will be coming to bb at some point. plus bb has interactive wallpapers already.
Galaxy Nexus: ICS53F Rooted/Unlocked Thunder Bolt: CM7.1.1 Droid 1: CM6
Team Shadow
want to buy me some orange juice?? Donate if you like my work
Yar. Too late Verizon. You had me excited and teased me for months. Then anguish put a serious strain on our relationship and I needed someone to comfort me. Unfortunately for you, Blackdroid and crew are my new baby momma's.
Yes, my love it is true. You have been upgraded for someone better.
Well I'm glad that the audio handset issue will be fixed in 2.1. I know that has been a major complaint for a while now. I guess it was indeed a software issue not a hardware one.