Share this project

Done

Share this project

Done
Console OS: Dual-Boot Android, Remastered for The PC's video poster
Play

We've rebuilt Android™ to be a primary operating system for your PC, 2-in-1 or PC Tablet. Over 100 new features built-in already. Read more

5,695
backers
$78,497
pledged of $50,000 goal
0
seconds to go

Funded!

This project was successfully funded on August 11, 2014.

We've rebuilt Android™ to be a primary operating system for your PC, 2-in-1 or PC Tablet. Over 100 new features built-in already.

Introducing iConsole micro & Our New Company Name

16 likes

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 iConsole.tv 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 iConsole.tv 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 ConsoleOS.com - sign up, and download. Remember, signing up and downloading directly from ConsoleOS.com 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 ConsoleOS.com 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, Console.com.co

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.

Why Lollipop is Such a Pain to Get Working (And, our rollout this week)

35 likes

Hello everyone, this is a busy week for us.

We’re going to be rolling out a lot of stuff… including our first Lollipop builds to backers. They’re being uploaded right now, and will be available over the next day or two. Another Kickstarter update will follow. Unlike KitKat, which we are also expanding access to this week, these will be backer-only for now.

We want to set the expectations right, so please note that these initial Lollipop builds are purely a technology preview, and not ready for general use. Device support will expand over the next month – so don’t be disappointed as we focused support on only a couple of configurations… we’re hoping to ship many more this month.

Why release a preview build? So you can see that we are moving forward with Lollipop.

While we are improving our Lollipop builds, we are going to continue to push and promote KitKat, Android on Core processors, and Android for 2-in-1's... while also refreshing our Wiki support documents with additional tips, tricks, and workarounds.

While we are improving our Lollipop builds, we are going to continue to push and promote KitKat, while also refreshing our Wiki support documents with additional tips, tricks, and workarounds. Our forums and the KitKat public rollout will arrive this week.

Many are asking why Lollipop has been such a pain. This is not a startup or Kickstarter-level-funding issue… it’s affecting every Android platform developer; giant and tiny.

The Technical Details

Both HTC and Motorola Mobility have recently come out saying the same thing - getting Lollipop to work has been much tougher than expected. No Intel-based Android device - other than Google’s own Nexus Player - is running Lollipop just yet. It’s no surprise then that over 99% of Android users (on the ARM or x86 sides of the aisle) are still running KitKat (or earlier).

At the same time, to grow Console OS, we have to push forward with Lollipop. In the future, supporting and sustaining KitKat would mean investing in code that Android/AOSP no longer supports. We’ve realized that it would be a losing game.

Just a mere two weeks ago, we were finally able to get access to all the private drivers and bits of code needed to support the same Intel Atom devices that we had targeted with our original release plans, now with Lollipop-capable drivers. We couldn’t affirm that we had the code… until we had it.

What we’ve found over the past six weeks (including, in particular, the last two weeks), is that Lollipop rewrites a lot of the fundamental code that gets Android up and running. That is why everyone is struggling with it.

Specifically, the AOSP 5.0 kernel lacks formal support for Intel Core processors, and the UEFI fastboot stack knocks down most of our existing bootloader support. Now that we have all the right tools, we can work on tackling these upstream issues.

On the bright side, Google & Co made these platform-level decisions so that major components would not have the rug pulled out from under them down the road. For example, UEFI devices on Android will now act identically to other Android devices - enabling us to push out firmware updates over-the-air with ease. But it will take time for us to rebuild the entire Console OS platform.

Two Big Things Coming Soon

Making good use of our time, behind the scenes, what we've been doing is building one reference platform that we can then branch out and support a broad range of devices.

We will be introducing that new reference device at Mobile World Congress, at Intel’s booth. We can’t share more on that topic just yet, obviously… so hang in there until the first week in March. It will show we haven’t been idle all this time, despite a laggard access to the bits of code we needed.

Opening Up Console OS

Finally, while Lollipop is quite painful, it has opened the door to us taking Console OS open source. The same changes that make Lollipop such a technical challenge, also give us the potential to finally open up Console OS.

We realize there are other Android on x86 solutions out there that are open source. There really are two - One that is not meant for end-users, and the other we have lost confidence in delivering commercial success. We think Console OS can deliver a new balance in this equation, and we look forward to taking it open source over the next few months. We can't do it just yet, but we are working hard on it.

We promise that when we do, we will put your Kickstarter money to work encouraging open-source developers to contribute improvements. Improvements that everyone in the Android world will benefit from.

While Lollipop has been a swift kick in the rear in terms of our development timetable, it has opened the door to us doing what we’ve wanted to do - make it so that anyone can build, and more importantly, contribute, to Console OS. And that is going to be our mandate for the first half of this year. In the mean time, we are going to open up Console OS DR1 with KitKat to everyone for free download, starting over the next week.

Merry Christmas & Happy Holidays, Backers

42 Comments
20 likes

For backers only. If you're a backer of this project, please log in to read this post.

Alternate Download Instructions for DR1

16 Comments
19 likes

For backers only. If you're a backer of this project, please log in to read this post.

Console OS Developer Release 1 - How to Get It [Backers Only]

18 Comments
27 likes

For backers only. If you're a backer of this project, please log in to read this post.