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.

We're Headed to IDF!

Posted by Mobile Media Ventures, Inc. (Creator)

We apologize for the repeated delays. As we'll explain, it's good news all around though for Console, Inc. - and for our backers!

First, Android on Intel - An Update

We've held a lot of meetings with Intel over the past few weeks. We had the same concerns that many have had lately about the state of Android on Intel.

While we can't answer all questions today, we can say that Intel has assured us, and we can in turn assure the community, that Intel remains committed to Android. There certainly have been, and certainly will still be, some bumps in the road along the way.

To recap the news that is public, Intel will skip Android support for its upcoming "Broxton" line of Intel Atom processors. But, the Intel Atom "Cherry Trail" processor fully supports the same I/O (including USB-C with USB 3.1, and even DisplayPort mode), and will be built on a long-life basis over the next 24 months. We expect to keep making devices on Cherry Trail, until the successor to Broxton emerges.

Right now, we're sure the big question on your minds is about Nougat. Will Intel support Nougat on their chips? And in the FOSS community?

We can't answer specific questions on that today, other than to say some Intel Atom chips will be supported by Nougat. The Google Nexus Player, for example, which is powered by an Intel Atom "Moorefield" processor, will be upgraded to Nougat.

But, it is true, Intel is temporarily pulling back Android support. They've been up-front with the media, and with us, about that. That means a lot of Android devices may not see Nougat. We're trying to make sure that the devices that we're building, that depend on Nougat, will make the cut.

Intel has shared with us their timetable, and we in turn are working with multiple partners in the Intel ecosystem to make sure that Intel's support of Android strategically aligns with all the goals of both the IoT community, as well as companies like ours that are still committed to making great Android mobile devices with Intel processors.

To this end, we have started to take Console OS temporarily offline. We still hope to keep to our current plan of shipping a FOSS-friendly, stable Marshmallow release later this summer. We won't be able to decide about the future of Console OS beyond that, until after Nougat's source code is publicly available (and despite some broadly-held misconceptions, the source code for future Android releases is not fully posted, until after the final release is pushed out the door by Google).

And, consistent with our last update, we will offer backers multiple options as we pivot to focusing on hardware. If we decide to stop making Console OS, we'll offer you the chance to request a refund - or something better, your call.

Console Developer Rewards - It floats!

A famous David Letterman sketch was "Will it Float?" - where David Letterman out of the blue, would drop objects into water, and see if they sink, or swim.

When Intel pulled back on Intel support for Android, we weren't sure if it was the end. So, we held off on Console Developer Rewards. To recap, it's our initiative that funds FOSS developers in the community, to squash bugs and build out features on a bounty basis.

Our first full round was rolled out last month, along with a new open-source project called the OpenHU Project. A key developer, Mike Reid, tragically passed away, and we were working with him on his Android projects. One of them was very key to an upcoming device that we are well into developing. We were in contact with Mike up to the day he went to hospital, and tragically, he died suddenly.

As the story goes, right after he passed away, Google beamed down a GMS update that broke his hard work. So, we put up a $10,000 bounty to fix it. One developer, Emil Borconi, answered the call. And while Emil decided to decline the reward, we're planning on making a sizeable donation to Emil's continuation project, and we also plan to roll up / wind down the OpenHU project into that effort.

We didn't share any of this in an update previously, because we didn't feel it was worth sharing without some conclusions. In memory of Mike Reid, we've kept going, and the product that we showed him before he passed away, built atop his FOSS contributions, is something we're excited to be announcing in the near future.

This first cycle of Console Developer Rewards was a great learning experience. It showed that small amounts of money can galvanize communities, and bring attention to underserved FOSS projects. In other words, Console Developer Rewards definitely floats.

After our summer announcements, we hope to roll out a new round, and with Intel's commitments, assuming we can keep building Console OS, we expect to focus on Android-x86 in the next wave. Yep, that means rewarding developers, with cash, for their hard work.

Onward to IDF

Originally, our plan was to unveil our next wave of announcements this week. But, at the last minute, Intel graciously decided to offer us a kiosk at the Intel Developer Forum, kicking off August 16th.

So, we're going to align our announcements closer to that date. But this is great news for us. Actually, it's the first time we've ever exhibited at an Intel Developer Forum. It's one small way that Intel is demonstrating a commitment to Android.

A lot of startups follow the "fail fast" methodology. As we enter year two of this Kickstarter, we certainly have defied that model.

It has been an interesting, challenging, painful, fun, and stressful two years.

So, kicking off this second year - we're going to echo our last update's promise, because it's an important one. We'll do what it takes to do right by all of you, even if it means refunding those that think we haven't done enough, despite the pullback in silicon support. We wouldn't be here without you.

Jerry Farmer, Michael K, and 7 more people like this update.


Only backers can post comments. Log In
    1. Mobile Media Ventures, Inc. Creator on

      @Scott - We're sorry you feel that way. But please be constructive with your input. We wouldn't be exhibiting at IDF in two weeks if we didn't have something new to share.

    2. Missing avatar

      Scott Kuban on

      These updates are always entertaining - like a soap opera, but less believable.

      But thankfully the "repeated delays [are] good news... for our backers!"

    3. Missing avatar

      Mikael on

      You are doing an amazing thing with Console OS!
      And you should get all the praises you deserve. from everyone.
      Also that you are so open about progress even if it is a very difficult task you have set to do and the news aren't always the best you still fighting and that makes me believe in you even more,
      It's sad to see people getting mad at you.
      I'm really appreciate your hard work and that you don't give up.
      You have my support.

    4. Mobile Media Ventures, Inc. Creator on

      @Mikael - Please be respectful and do not misrepresent our work. We do not reply to posts that insult or violate Community Guidelines, other than to call them out for such behavior.

    5. Mobile Media Ventures, Inc. Creator on

      @Nigel - That's just not true. We shipped Console OS KitKat atop Intel's Android-IA kernel for PC hardware. After it was suddenly discontinued (seriously disrupting our work), we then moved to the Android-x86 kernel and shipped Console OS Lollipop to keep the project alive.

      Please read our past updates for more details on the evolution, thanks.

    6. Missing avatar

      deleted on

      This user's account has been deleted.

    7. Mikael Draca Wedlund on

      This comment has been removed by Kickstarter.

    8. Mobile Media Ventures, Inc. Creator on

      @Stuart - So, that's a good question that we should probably move to the forums since it's not really tied to this update's material. - We just would like to go chip-by-chip and address that there.

      But in sum, the reason why we set the stretch goal for Surface support so high, was that not even traditional Linux still totally handles Surface Pro 3 fully well, until perhaps the most recent versions of traditional Linux OSes. Microsoft chose really specific Windows-only chipsets, and engineering Android support on Wi-Fi and other fronts costs a lot of money.

      Since our Kickstarter ended, Intel has pulled out of supporting Android on Core processors completely. All the Android-on-PC distributions now have fallen back on Linux kernel mainline support... which is not where we wanted to be. But today, we have no choice, and that's one of the reasons why we're focused on our own hardware today more than Console OS.

      At least with our own hardware, we can make sure it works great, and make sure chip makers keep to their support commitments.

    9. Missing avatar

      Stuart Bevan on

      Could you please help me out - I originally backed this Kickstarter as a Surface Pro 3 owner, looking to recreate the Android experience on much more capable hardware. I understood, going in and with all the various surveys, that only earlier Pro Surfaces were being looked at during the campaign. Since then, I'm honestly not sure where I stand - will this ever be compatible with the SP3? It seems to me that there is an awful lot of politics over time, but not a lot of clarity. Your feedback would be appreciated.