Would You Buy a MOTOBLUR DVR?

From almost day one, we’ve been saying here at AndroidGuys that we expect to see some DVRs and set-top-boxes with Android under the hood.  After reading an article on the Wall Street Journal, it appears we might finally be seeing some more movement out of the hardware manufacturer.  Rather than spinning off Motorola into two completely different divisions for mobile and home products, CEO Sanjay Jha will be heading up the new entity.

One of the first elements to be shared will be Motoblur, currently a feature on newer Motorola phones that combines address books with email and social-networking accounts. The company is testing Motoblur on TV boxes, where it will likely appear this year, though that could slip to 2011, Mr. Jha said in an interview.

Do you guys think that MOTOBLUR or Android would work well on a DVR?  Would you take either platform into consideration were you to purchase a new DVR?

The above video is a demonstration by MIPS who were showing off their concept for an Android-based DVR from CES earlier in the year.  (Source: Androinica’s Andrew Kameka )

  • I think that DVR/TV is going to be Google's next big move. Much bigger than mobile, in fact. I blogged about this here: http://bit.ly/a02rP4. I posted that entry a few weeks ago, and some of my assumptions (e.g. about NexusOne) were a bit off, but I think that two years from now many of us are going to be interacting with our TVs in very different ways. There's too much at stake for this not to happen and happen quickly.

  • hazydave

    This could be good news… finally.

    Back in 2000, I was working at a set-top box company I co-founded, called Metabox AG. We had spent some years writing our own STB-based OS, designed a custom hardware platform, etc. This was the Metabox 1000, a large improvement over some of the earlier units we had produced. This one could play DVB television, DVD video discs, browse the web, PVR your TV shows, play video sources PiP on the HTML-based desktop, etc.

    I was looking at applications, and decided that a Java API would be ideal. We already had MHP support in the STB, and it would really interesting to mate this with mobile devices (in those days, I was thinking "PDA") under the same small gaming API. Imagine you're a kid, playing a game on-screen, when it's time to drive an hour to your Aunt's house. Rather than shut it down, you turn on your phone. The phone links with the STB, and you simply fling the game from the STB to the phone… and continue playing the same game, now on the phone. Same with recorded videos, etc.

    That was the ultimate goal. It would have been fairly difficult to make it quite so slick given the state of both STB and handhelds ten years back. Today… not so much. This could be just that slick. It's a shame the startup failed, but I'd love to see this kind of thing become reality, even if other people are doing it (I had a few others that kind of started "before their time" and failed, whether because of it or do to other issues… still waiting for that stuff to hit the market, too).

    And Android's a great platform for this kind of thing. Linux is certainly mature enough to handle the OS-level stuff we had to do custom ten years back. The Java layer assures that at least potentially, the same programs can run on STB and handheld, even if they have different CPUs at the heart. They'd need an API for "dehydrating" and "rehydrating" running applications between devices, but that's also very doable.

    There's also some power to the idea that you don't have to worry about learning a dozen different device APIs. It's fairly natural for novices to ask why you can't run PC games on your iPod, or vice versa… more now than ever, given that games are arriving via download, so "the cartridge doesn't fit" argument fails. But it's actually a very good question to be asking, in general.

  • i think its too expensive for the feature man..

  • thanks for your sharing. great post! like this :p