Motorola clears the air on Droid Turbo Lollipop update

12 June, 2015
According to Motorola's David Schuster, the update is still in the lab test cycle.

Sort by:

  • s
  • smh
  • jZn
  • 22 Jun 2015

why not android m

    • m
    • magus
    • wfI
    • 13 Jun 2015

    I have Lollipop and there's no operating manual for it. I do think Google and Motorola could have co-operated a little more in the interests of the customer, rather than being in a rush to distribute a system that still needs refinement/improvement in a straightforward area like answering incoming calls.
    It would also be nice to have the choice to un-instal unwanted google apps.

      • R
      • Ryan
      • jEt
      • 13 Jun 2015

      Might as well go right to Android m now.

        • N
        • NAdoroare
        • GeB
        • 12 Jun 2015

        AnonD-405693, 12 Jun 2015Than Verizon reps need to quit lying called on the 10 th wi... moreReally? VZW typically wont say at all. So I don't know who you got in service willing to talk about that they don't know.

        - Bug thing wouldn't be an issues if wasn't that phone was not just in hands of power users, its people who need to just pick it up an use it, bugs would decimate those users for VZW.

          • ?
          • Anonymous
          • uvd
          • 12 Jun 2015

          What about MOTO E lollipop update

            • m
            • mixa
            • pwT
            • 12 Jun 2015

            Turbo's users actually must be happy that they skipped 5.0.x, it's one of the worst androids ever made.

              • D
              • AnonD-405693
              • R1$
              • 12 Jun 2015

              Than Verizon reps need to quit lying called on the 10 th with yet another issue which couldn't be resolved till update rolls out and she assured me it was rolling out Wed would have it no later than 2 weeks for all droid users so another lie from big V tech support to get me off the phone

                • D
                • AnonD-269736
                • 3Nd
                • 12 Jun 2015

                Better to wait for a propper update (5.1) than receive a buggy one (5.0.2)