Another Motorola DROID OTA coming in late January?

Whisper

One of our connects has informed us that while the current OTA has only gone out to around 10,000 devices, there is already another one waiting in the wings and it’s tentatively scheduled for late January. Could this be for an Android OS 2.1 update? We’ll see…

42 Comments
  • davidlw

    Please don’t use that black type on dark blue, I cannot even read the type.

  • ChocoTaco

    “We’ll see”? We won’t see anything BRG, not with this font and background color choice. Who did your design team consist of? Stevie Wonder, Ray Charles and Helen Keller? Your normal color scheme on all the typical posts is great. Why change it up for these extra updates? I’m hoping if enough people complain you’ll fix this!

  • Melikey Awesomecolors

    Wow I love how this gray font pops out at you! bravo!

  • Bob Guenthner

    I am hoping it is to make it Enterprise ready. Support encryption, remote wipe, etc…

  • carig

    Did maybe fading to black sooner and then doing white on black text ever occur to you, it’d be a nice android kinda thing. Of course did making these readable ever occur to you at all?

    btw I like how the tags are blue on slightly darker blue, making it look like simply an oddly spaced row of commas, BRILLIANT!

  • Random

    Old news; the Verizon support document that was leaked last month already stated they were planning updates for Exchange support in late January (the 22nd).

  • anonymous

    dark gray font on blue blackground? ick

  • phaberl

    Funny how a lot of the rants about the droid are completely false…

  • anonymous

    I love how all of these “tech savvy” readers have a complete inability to grasp something as simple as a CSS stylesheet error. Do you really think the author made an intentional choice to put black text on a blue background? Give me a break. Nice to see that it’s fixed, though… no thanks to the snarky comments of course.

  • cece

    Yay 2.0 hopefully here we come

  • Mark

    Hopefully that update will fix some of what 2.0.1 broke. =(

    http://code.google.com/p/android/issues/detail?id=5337

1 2
blog comments powered by Disqus