Share this project


Share this project

We started as the first commercial effort to bring Android to the PC. We're still at it, now on GitHub rebuilding - combining the best of the open-source world, with cutting-edge commercial drivers, licensed from Intel. (
We started as the first commercial effort to bring Android to the PC. We're still at it, now on GitHub rebuilding - combining the best of the open-source world, with cutting-edge commercial drivers, licensed from Intel. (
5,695 backers pledged $78,497 to help bring this project to life.

Introducing iConsole micro & Our New Company Name

Posted by Mobile Media Ventures, Inc. (Creator)

Hello everyone,

We're live at Mobile World Congress, and we've got news to share.

Introducing iConsole™ micro - The first Android™ stick that matters.

At the show today, we took the wraps off iConsole micro. And, we've reopened to start to promote it.

What is iConsole micro? It's our first consumer hardware, and it's incredibly small. It's the first Android "stick" that doesn't trade performance for size. Powered by a quad-core Intel® Atom™ processor, it will deliver the full range of Android-on-PC and Android-on-TV functionality, with the same performance that you've come to expect from PCs several times its size.

iConsole micro
iConsole micro

We'll have more to share on iConsole micro later this month, including tech specs, price-points, and a full announcement. You can learn more at both and on our new, unified company blog.

Also @ MWC

Not only are we introducing iConsole micro, but we're also giving live demonstrations of Console OS with Android™ rocking on Intel Core 2-in-1's... showcasing OpenGL ES 3 demos powered by Unreal Engine 4.

Our Mobile World Congress booth space for 2015!
Our Mobile World Congress booth space for 2015!

And, finally, for the first time, we're also live demonstrating Android 5.0 Lollipop builds of Console OS, running on a Minnowboard MAX. While still early, it shows we're alive and well on Lollipop, and we hope to ship these new builds later this month.

Our new builds of Lollipop are such an advancement, we've taken down our Lollipop Technical Preview to backers - our team is closing in on the stability we've been fighting for. Once our team is back from MWC, we'll be working non-stop to start finishing, polishing, and most importantly, shipping new Lollipop-based builds exclusively to Kickstarter backers.

Opening DR1 to All

We need your help. We need to show that people want to run Android natively on their 2-in-1. So, we've made it easy to share Console OS with your more novice friends.

Please tell your friends, favorite blogs, and social media spheres to go to - sign up, and download. Remember, signing up and downloading directly from is key - it helps us show the pent-up demand for Android on the PC. Uploading copies of Console OS to file sharing sites, not so much (so please don't do that).

We've done a few things to help make sharing Console OS with your friends a bit easier.

First, we've repackaged DR1 in an easier-to-install bundle. We've updated some of the bundled apps too. However, we don't recommend you reinstall DR1 if you already have it.

Second, we've revamped the Console OS Wiki to make it more novice-friendly.

Third, we've updated the entire workflow of downloading and accessing Console OS to clearly define where it works well, and give you the resources to keep it running great too. Just tell people to and you can sign up and download in just a couple minutes!

Finally, we want to thank everyone who has already signed up and started using the Console OS Forums. They're off to a great start. We've seen some great tips, tricks, and solutions... a few of which we didn't even know about!

As we mentioned, backers will continue to get exclusive first access to Lollipop builds soon after we return from MWC and do a bit more validation and testing. Once we stabilize Lollipop across our target devices, we'll resume adding Pro features... as the vast majority of backers voted for us to do.

Say Hello to Console, Inc.

This week, we submitted paperwork with the state of California to begin changing our name from Mobile Media Ventures, Inc to something... a bit more fitting. This isn't going to happen in a day, so please bear with us.

We like the name Console, Inc. and we've decided to adopt it. It really symbolizes what we're working hard on every day - both Console OS and iConsole™ hardware.

We have set up a great new corporate homepage that will guide us through this transition,

Please note that we're the same team, same company, same corporation... we're just gearing up to change our name to something a lot better.


Only backers can post comments. Log In
    1. MMV=$78K Payday! Backers got NOTHING! on

      This comment has been removed by Kickstarter.

    2. Brandon Gregg on

      This is why i stopped supporting kickstarter. I paid for an android os to run on any pc, not for you to change your name, create a new product I don't want and to stop supporting my PCs.

    3. Missing avatar

      Sebastian H.

      'we'd encourage you to check the forums... Where there are solutions to issues like the 'sector 63 error'.'

      So how about you point me to that supposed solution? The only thread that I found that claims to offer a solution also features a post saying that that leads to another problem, for which there doesn't seem to be a working solution either.
      Also, I want YOU to look for solutions to the problems that turn up when using DR1.That's what such pre-releases are for: To tell the the developers what they have to look into.
      Outsourcing the support to your users does not build confidence and trust in your work.

    4. Mobile Media Ventures, Inc. Creator on

      Sebastian, we'd encourage you to check the forums... Where there are solutions to issues like the 'sector 63 error'.

      While much of our team is traveling back from MWC at the moment, we have been quite responsive on each of these topics in the past.

      The Console OS Wiki lists device by device support, but over 40 devices currently run Console OS well or with minor/singular issues.

      We get it. You want your specific device to run Console OS. We're working hard to support UEFI32, and we have gone so far as building a device around it to encourage platform support from vendors and squash those last mile issues.

    5. Missing avatar

      Sebastian H.

      'We did when asked. We said clearly we couldn't guarantee all devices would be supported initially, but that we would support most devices by end of year. '
      So.. where did you support most devices by the end of the year?
      You supported NONE of the 32bit devices at that time at all, and many others where NOT booting DR1. Read the comments from that period as proof.

      'We did not know UEFI32 devices would not run KitKat properly until after our Kickstarter campaign ended.'
      And that is no-one fault but your own. How could you claim to support devices out of the gates that you hadn't done any reasonable testing on?
      During the Kickstarter (that is before August 11) you did NOT make clear that you hadn't even done preliminary testing on many of the devices. At no time did you make a distinction between devices that you had done some testing on and those you just added to the list HOPING that they might work. If I'm wrong, show me the exact update and sentence where you did. Don't just claim you did, PROVE it.
      That is disingenuous. That is luring customers in with claims of hardware support that you couldn't and (as of now) still can't fulfill.

      And you did not provide reasons why stuff wasn't working. You muttered 'Lollipop' every time you deigned to react at all. Thats not the technical explanation that you promised in one of your updates.

      And as far as I know you STILL haven't said anything about the problems we found with DR1. Have you found the reason for the sector 63 error? If I can't test Console OS on my DV8P I would have liked to at least test it on my Thinkpad (pretty much all Intel chips, so should have worked at least to some degree). But no dice.
      Have you communicated with us about that and other problems? No. I have not seen you acknowledge these errors in ANY of your updates.
      Open and transparent this is not.

    6. Mobile Media Ventures, Inc. Creator on

      @Gilbert - We certainly want to deliver iConsole micro soon, we expect to have a progress report on that by month's end.

      Obviously we also want to keep delivering to Console OS at the same time, and we only work on iConsole micro when we hit walls on that, and are stuck waiting for something else (driver revisions, patches, QA responses, etc).

    7. Mobile Media Ventures, Inc. Creator on

      @fmotta - You can see on the Wiki current device status, we're supporting most devices currently and on track to deliver for the rest.

      @Sebastian - We did when asked. We said clearly we couldn't guarantee all devices would be supported initially, but that we would support most devices by end of year. We met that benchmark. We did not know UEFI32 devices would not run KitKat properly until after our Kickstarter campaign ended. As soon as we did, we provided the reasons why and have been giving status updates ever since, leading right up to showing off our latest progress this week at MWC.

      We have been open and transparent on progress - claims to the contrary are simply wrong.

      Finally, we have not taken one dime of funding from the public since our Kickstarter campaign ended. So claims we're trying to "lure backers" is not only wrong, it's disingenuous.

    8. fmotta on

      @Creator: That was not a well hidden secret. But, working Console OS for our hardware is a Real secret that is hidden mightily.

    9. Missing avatar

      Sebastian H.

      During the Kickstarter MMV said that they will support a list of devices, including a bunch of devices with 32bit UEFI. They gave the impression that they already had Console OS running on the devices in the list. They did not make clear that at this point they hardly had anything working on all those 32 bit devices.
      Later, they claimed that Lollipop and the changes it brought was the reason support for devices with 32but UEFI was delayed. Yet the DR1 was not based on Lollipop and still didn't support any of those devices.
      First they promised support with DR1, then with DR2, now it is 'during the DR2 release cycle' (which translates to 'not with DR2, but maybe before DR3').
      And while they don't make any visible progress on this front, the stuff that they used to lure backers to their project (I certainly only support Console OS because they gave the impression I would get an Android running on my Dell Venue 8 Pro), they are spending their time working on other, new stuff. Stuff that takes away resources that they should spend fulfilling the promises that they made to get our money.

    10. Gilbert Vera on

      Now my question is I want one :).
      How much for one of those micros? And as backer can we purchase one first before the rest of the people ?

    11. Mobile Media Ventures, Inc. Creator on

      So, to let you in on a little secret... iConsole micro actually, deep down, pretty darn similar to these "last mile" devices we're still building out support in Console OS for. It even has UEFI32 firmware.

      To make sure we had the resources to support these devices, we needed our own reference platform that we could build atop. That's iConsole micro.

      Minnowboard MAX is, essentially, the missing link - it's a UEFI64 Bay Trail development board. We have Android stable on that and are now moving down to UEFI32.

      None of this is really new info, well, except for iConsole micro. We have said all along (since we got our first hands on Lollipop) that we would have to get things stable with UEFI64 Atom, then move to UEFI32 Atom.

      iConsole micro will also ensure we have the resources to support our goals in the PC Tablet field with Console OS, by pooling our engineering resources there.

    12. Pierre Laporte on

      Hello Console, Inc ! Yes, I like this name ! ;) and I like the iConsole micro ! I want one ! :)
      This update make me pleasure because it's on a Minnowboard Max that I want installing Console OS ! :) cool ! :)

    13. ET3D on

      @Daniel etc., to quote the wiki:

      "The Dell Venue 8 Pro is not supported by Developer Release 1. We are working hard to add support for Developer Release 2, as we transition to Android 5.0, Lollipop.

      The main blocking issue stems from the device not offering 64-bit firmware, despite having a 64-bit processor. We are working with relevant industry partners to add support for 32-bit firmware devices, like this one, to Console OS."

      Sounds to me like they're working on it, but it would take more time.

    14. Missing avatar

      Ian R on

      @MMV- focus.

    15. Keith on

      @Daniel, @fmotta

    16. Matthew Brooks on

      Despite all of the initial negative comments, which I expected, I appreciate the update and all of the details. Everything sounds good, and I like the direction that everything is going. Looking forward to a Lollipop build later in the month. Have fun at MWC.

    17. P. Vandeyar on

      Did I miss an email or announcement?
      I don't recall getting console os for my Asus T100TA.
      How about an update on that?

    18. fmotta on

      Apple tried to copywrite anything that started with 'e' (ala email) and failed.
      They tried again with 'i' - failed.
      Many years ago they disliked the common pronunciation SCSI (scuzy) - they tried to get the industry to pronounce it as 'Sexy' - failed.
      They are all about perception aren't they!

    19. Missing avatar

      Wouter Tweehuijsen on

      iConsole sounds like an Apple product...

    20. fmotta on

      Yep - hardware sitting waiting for software seems to be a common condition...

    21. Nabil Boutaleb on

      Lenovo Miix 2 8", feeling a little bit cheated at the moment.

    22. Missing avatar

      Daniel Schoonover on

      Venue 8 Pro here, with nothing for it.

    23. fmotta on

      Thanks for the 'pitch' on another project.

      How is the progress on This Project?