Share this project

Done

Share this project

Done
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.
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. (Console.com.co)
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. (Console.com.co)
5,695 backers pledged $78,497 to help bring this project to life.

Use this space to cheer the creator along, ask questions, and talk to your fellow backers. Please remember to be respectful and considerate. Thanks!

    1. Missing avatar

      Owen Shadbolt on November 27, 2015

      @Everyone, Firstly I'd just like to say that I'm not at any time going to be requesting a refund from MMC for this project. I backed a kickstarter project, on its merits and knowing the risks. Backers not prepared to go all the way and accept the risks just increase those risks. Not to mention the likelihood that the project will fail. So even if I loose faith in the eventual outcome of a project, for the sake of all concerned I can and will simply accept the loss and if I couldn't I wouldn't back it in the first place!

      Thats not to say I don't have cause to be disappointed with this project. My first disappointment came when they offered a voting process, because as an industry insider I knew that exactly what we have today would the ultimate outcome!

      My second disappointment is that they (partially as a result of the outcome of the voting) have been incredibly at the mercy of capricious third-party companies like Google, Intel and MS.

      And finally I have been disappointed that they continue to miss their own dead-lines and use "jargon" that needlessly makes them look "shifty" I mean what the hell is a 'payload'! Why not just tell it like it is, e.g. "Today we uploaded a pile of patched code". Perceptions in a case like this are just so important that I even suggested (several months ago) that they use some of the funds to hire a PR consultant.

      I hope the project is a success and that someday I will be able enjoy the benefits of it! I don't believe MMV have at any time acted in anything other than good faith and can forgive their mistakes, down (I believe) to inexperience.

      Owen.

    2. Mobile Media Ventures, Inc. Creator on November 25, 2015

      It certainly has been an interesting week in the Windows world. As we mentioned, we were upgrading our installation guide to reflect changes in Windows "Threshold 2" or TH2 for short.

      Well, guess what? Mid-week, Microsoft pulled the update from its Media Creation Tool. Then, a couple days later, they took the update offline completely.

      And, now, it's back.

      While we regret the delay in posting our install guide -- can't blame us for following the shell casings each step of the way. On the bright side, TH2 is a solid update to Windows 10 - and does make installing Console OS much easier.

      We're now resuming work on the install guide, hopefully Microsoft won't pull another rug out from under us... at least, until next week.

    3. Mobile Media Ventures, Inc. Creator on November 22, 2015

      Cross-posted from our unified Facebook page: https://www.facebook.com/ConsoleInc/

      Hint: Follow us on Facebook using the link above!

      "Evening all, we've locked down our per-device build targets for staging on GitHub. As soon as they pass QA, they'll go to GitHub for you all to play around with.

      That may take a few days as we can't build in parallel for this task just yet. If we have to work through Thanksgiving, we will... Black Friday is a bust these days anyways."

    4. Mobile Media Ventures, Inc. Creator on November 22, 2015

      @Ripton - Frankly, the whole team disagrees with your assessment. Emulators have stumbled in handling Android. We're glad you like the solution you have chosen, but we receive requests every week in our inbox complaining about those solutions. Even Microsoft has put theirs on an indefinite delay.

      We are uniting the Android-x86 and Android-IA kernels today - because frankly, neither provides great per-device, fine tuned support. If they did, everyone would be using them. People use them because there isn't a better option - not because it works great.

      That's what we're here to solve, and again - if your original statements had validity... we would have taken the money and run. Clearly we have not.

    5. Mobile Media Ventures, Inc. Creator on November 22, 2015

      (Clarifying: In the Linux community, DRM means two different things. Our DRM references in our comment yesterday were to the Direct Rendering Manager - or what communicates with the graphics driver. Digital Rights Management is a Widevine issue... and separate from what we were discussing).

      And yes, it would be nice if the were two different acronyms, and no - this isn't the first time people have layered the two together.

    6. Mobile Media Ventures, Inc. Creator on November 22, 2015

      @Tim - That is a Widevine issue, but not a DRM issue. We have requested to join the Open Handset Alliance, and will continue to work with Google on licensing Widevine. If we run into issues there, we'll let the community know. Our first goal is to resume shipping Console OS Lollipop - from there, we can start addressing those issues.

    7. Missing avatar

      tim on November 21, 2015

      I'll bite, does the libdrm allow dish anywhere or rhapsody work on your build?

    8. Missing avatar

      Ripton on November 21, 2015

      Ok, I might've been a little bit harsh in my las commebt but come on... A project that started after yours and it doesnt even went trough crowdfunding is having a greatpy working version. I am talking about AMIDuOS.
      Also Android X86, which is completely free and all the money they receive is from donations, is working 100%, it is stable with GApps, it is lollipop and it has a working bootloader. I am currently dual booting lolipop(Android X86) and Windows 10(with a SD Card) on Asus T100. And I have payed 0£ for it. I dont think that your excuses are viable anymore.
      Even if you release a working version, probably no one will care anymore. It would probably have bugs and what not while other OS/Programs are almost 100% bugless at the moment.
      However, I would be seriously happy if you release a verson that took you some effort to make unlike the first version you gave us.
      There might still be time to save this project, even though I doubt you can.
      Good luck to you and I really hope that you guys are serious and just going through a lot of problems rather than scammers like I initially assumed.

    9. Mobile Media Ventures, Inc. Creator on November 21, 2015

      Hi all, we are staging the per-device builds and final driver payloads on GitHub over the weekend. This isn't a guarantee we'll be live next week - but rather, our goal. We have the Android Developers Conference in Santa Clara - but we will be working through Thanksgiving if need be.

      We had an opportunity this week to fight for some time at CES - which we obviously get a little window to do. While we can't share what we pitched, it's in your interest and ours to fight to get that kind of attention.

      Silicon executives (we wish we could name them here) got to use Console OS Lollipop a couple weeks back. They sure liked it. It has been a tough year, no doubt, but we're far from throwing in the towel.

      To those that claim we are squandering your funds, it would have been very easy to have simply posted a technical breakdown of what changed after our Kickstarter ended... from Intel pulling the plug on formal support for Android on Core processors - to Google Verified Boot breaking our bootloader.

      And while this is still a work in progress, our next steps are to deploy libdrm and the Intel UFO driver on our consolidated community kernel. Steps we'll be rewarding the community to help us do as we roll out on GitHub.

      We have faithfully been giving you the blow-by-blow, and frankly, it saddens us when people claim we've run off with the money. The carpal tunnel alone from hammering out these updates, would strongly differ.

      So, cheer up, we're at 33 build targets verified and counting. We can't promise 50 pushed to GitHub by next week - but we're fighting for that goal at 2 AM right now.

    10. Missing avatar

      Ripton on November 20, 2015

      Android X86, AMIDuOS, and even Bluestacks are working great an all windows devices, even the ones with Baytrail processors.
      I've lost hope in this project for a long time. The latest Android X86 builds are working amazingly on my Asus T100 and to be fair this project is dead.
      I am really sad to see such cool anf ambitious project being a total failure.
      The truth is we've been scammed... Yes, this whole thing is one big scam. For ONE WHOLE year all we've seen from those guys is one non working version that was 100% copy of Android-IA and a few videos that as far as we know could be fake. Everyone with a decent video editing knowledge can make even an oven to run android.
      Those guys will get 78k, Kickstarter will get 5% of that and everything will be "ok"... We'll be left here waiting for something while those guys come here occasionally to lie to us that they are doing something.
      However, we are the ones to blame. Kickstarter project are unsafe, most of them come from shady and unknow companies such as this and many of the projects are either unsuccessful (even with successful crowfunding) or a total scam, such as this...
      In the end, crowdfunding has its own risks that we should accept when we give our money away, knowing that we will never have them back.

    11. Serge Ecoiffier on November 19, 2015

      This comment has been removed by Kickstarter.

    12. Daniel Blizzard on November 19, 2015

      Been over a year and you guys have really dropped the ball, I gave up on this project once I managed to get android X86 installed on my 2 in 1 tablet/laptop. Now I see that software such as AMIDuOS is running on par so disappointed, So much potential wasted.

    13. Richard Yiu on November 18, 2015

      you have promised to release DR1.5 for our bay trail devices last November. A year have passed and still that's no sign of any releases. When will you release build for our devices? I don't want to ask you again next November for the same thing.

    14. Mobile Media Ventures, Inc. Creator on November 17, 2015

      @Mark - Not unless you have WIMBoot - which is why we suggest upgrading to Windows 10. With Windows 10, the Disk Cleanup tool will remove WIMBoot automatically, reducing the recovery partition to under 500MB.

      This is actually why we're rewriting our install guide this week, because Windows 10 Threshold 2 made material changes to this process. It's good because it's much easier under TH2. But, it's bad, because we had the whole guide in the can... and it's time consuming to rewrite it.

    15. Mark Lester Cruz on November 16, 2015

      Do we need to remove our recovery partition in DV8P when we install console OS?

    16. Mobile Media Ventures, Inc. Creator on November 16, 2015

      We mentioned that Windows 10 Threshold 2 upgrade would help simplify our guide. Testing now shows that, thankfully, you can upgrade to Windows 10 now directly, using a Windows 7, 8, or 8.1 product key, or BIOS key.

      This is great for Bay Trail tablet owners, because the install process was convoluted and time-consuming - often taking multiple days. Now a user can just boot a Windows 10 install - do a clean install - and proceed to move on to Console OS.

    17. Mobile Media Ventures, Inc. Creator on November 16, 2015

      @Dennis - Lollipop will work on nearly all target devices, and we expect Dell Venue 8 Pro to be among those. The only decay we have noticed is that with Windows 10, you will not be able to dual-boot if you have less than 32GB of storage built-in.

      We expect Console OS Lollipop to be where we expand to most PCs in channel. As part of open-sourcing, others in the community will be able to test - and contribute - per-device build targets.

    18. Missing avatar

      Dennis on November 16, 2015

      yup i have seen those on youtube. thanks. just wondering if anyone else could post their devices. at this point i no longer need console os on my venue pro 8. just curious to see how this project i backed was coming along since most of the comments here are from those asking when will it work on their device.

    19. Mobile Media Ventures, Inc. Creator on November 15, 2015

      @Dennis - Did you search YouTube? A quick search for "Console OS" found several matching videos - including a few doing cool stuff.

      At this point, you're best waiting for Lollipop however. It will require a complete reinstall, as Intel yanked the bootloader we were basing atop - which means structural changes to the underlying partitioning. After we ship Lollipop, we'll outline our plan for moving forward, and (hopefully) unifying the different Android bootloaders on x86 (we count at least three divergent bootloaders - it's a royal pain, and shouldn't be).

    20. Missing avatar

      Dennis on November 15, 2015

      could someone (besides the creators) post a video or something of their device with a working version of kitkat? I've yet to see one but the updates and comments from the creators make it seem like there are backers out there enjoying what they paid for. I'd really like to see what it looks like. thanks.

    21. Mobile Media Ventures, Inc. Creator on November 15, 2015

      @pk - We certainly will if we have a chance!

      We're doing our best to get Lollipop out the door in completed builds (per-device, and there are *dozens* of per-device builds at this point), so our goal is for this only to push back when our repos are live on GitHub (they aren't right now, so don't freak over what's on GitHub currently if you're searching there).

    22. Missing avatar

      pk on November 15, 2015

      Perhaps the staff at Santa Clara could produce a video of a working version, now that you have the time.

    23. Mobile Media Ventures, Inc. Creator on November 15, 2015

      @KIHWAN - We are not doing refunds, sorry. We followed the wishes of backers when we got to Lollipop, after meeting our December 2014 timetable to support most devices with KitKat. We will only do partial refunds if for some reason we cannot ship Lollipop - which is highly unlikely at this point.

      @RiceFryer, Karol - Please stop. We aren't - so continuing to post the same remark is simply a waste of people's time. We've had several opportunities to say that the task at hand became too large after Intel, and Google, rewrote their roadmaps with Lollipop... and yet, we've persevered.

    24. Missing avatar

      KIHWAN JIN on November 15, 2015

      Give me back my money $ 10!

    25. RiceFryer on November 14, 2015

      Do not use 'good' 'Hi', and 'hello'. We are not hello.

    26. Karol Putra on November 14, 2015

      This comment has been removed by Kickstarter.

    27. Mobile Media Ventures, Inc. Creator on November 14, 2015

      Kickstarter's lack of a comment edit button has bit me yet again, that last post was from @chrisprice myself - if you want to complain about this decision -- feel free to send it there... but before you do, please contribute to the IFRC or similar organizations in France. We deal with code, at this hour - they're in desperate need for blood.

    28. Mobile Media Ventures, Inc. Creator on November 14, 2015

      Good evening everyone,

      We have contractors, and people that we definitely feel that are on the team, that have stood by us throughout this very unique path that this startup has taken. Our team stretches from Santa Clara, to Australia, to yes, even Paris.

      Before I email the team, I wanted to make the decision - we're not going to ask our teammates in Europe to burn midnight oil to ship source code this weekend. Some cannot even leave their homes, and are under curfew. France is in a state of emergency not seen since World War II at this hour.

      Everyone at Console, everyone, is tearful for the tragedy that hit Paris today. We will continue on with Console OS going open-source over the next week.

    29. Missing avatar

      Tony on November 13, 2015

      the heat is on. leo laporte is liking having amidous installed on his surface book. the only thing he said does not work is the camera. i'm getting a surface book next week. which android os will i end up with?!?!?

    30. Mobile Media Ventures, Inc. Creator on November 12, 2015

      Hi all, while we are retooling our install-prep guide to account for Windows 10 TH2, we split the difference by creating a Storage Requirements guide on our Wiki that will help explain some of the storage changes that Windows 10 has brought to the table.

      http://wiki.console.com.co/w/Storage_Requirements

      (Console OS Lollipop isn't out yet - this is just a preparatory advisement).

    31. Mobile Media Ventures, Inc. Creator on November 12, 2015

      @Christopher - Within a few days. We caught some major colds at a private retreat - but we have final code from all hardware partners cleared for release. It's really just a race to stage and then triage what bugs you all find. Documentation is going to be key, and that's our biggest stress right now.

    32. Christoper Rogers on November 12, 2015

      In the previous campaign update, you said that some form of console OS, be it the source code or a preview build, would be available with a target release date of November 15. Are things still on track for this day?

    33. Mobile Media Ventures, Inc. Creator on November 12, 2015

      Good morning all, Windows 10 "TH2" was released this morning. It actually changes a couple of the steps in our pre-install guide... but in a good way. It will make it easier to prepare your system for installing Console OS. We're working right now on integrating these changes.

      Because TH2 installs automatically, we won't provide older guides for past Windows 10 versions - we will remind you to make sure Windows is up-to-date in the guide, however.

    34. Mobile Media Ventures, Inc. Creator on November 12, 2015

      Good morning, during a team meeting, we realized there was a typo in our last comment...

      Most BayTrail-T devices do not support *microSD* booting - It appears auto-correct rewrote that to microUSB... somehow. You can boot Console OS over micro-USB (you have to, to install it, obviously), and even Windows To Go theoretically will work... but that would be a bit impractical on a tablet with the size of today's flash drives.

    35. Mobile Media Ventures, Inc. Creator on November 12, 2015

      @Harry - So, we are getting good results on DV8P. A good chunk of the problems boiled down to BIOS. Many BayTrail-T BIOS patches were held back for Windows 10. It wasn't until the last BIOS update, literally a month ago, that things stabilized.

      We all can be angry at the OEMs for not making their BIOS updates timely, but please don't be angry at us for that. The OEMs have their lines of business, and this just wasn't a priority to address.

      As to usability, we will be recommending you dedicate the device to Android, unless you have a high-spec version (as in, 64GB). Most of these tablets do not support microUSB booting, and Windows 10 clocked in on the very demanding side of things.

      It is possible however to have a very usable 24/8 arrangement, where you dedicate 24GB of eMMC disk space to Windows, and 8GB to Android... followed by offloading content onto the microSD slot. When you get down to 16GB, it starts to become unviable.

    36. Missing avatar

      Harry Elliott on November 11, 2015

      @Ian R - I sincerely was not intending to tread on you. I was and am impressed that this comment section has remained civil. You have very valid points and did not mean to come across as attacking. I agree with you that the point of this and every Kickstarter is to produce what is promised and to date we have seen very little from @MMV. Perhaps I am too forgiving. My own experience between Kickstarter and the other popular crowdfunding platform is that I have only received 50% of the rewards promised and of the 50% I did receive, none have been on time (I am hoping a certain Bluetooth headset will arrive on time and change my percentages). Of course those numbers are what they are because I tend to back cutting edge electronics and such that are inherently risky. I have worked with other "dual boot" android OS's for windows machines and, while they mostly worked, I backed Console because I want an easy to use, idiot friendly (a requirement for my level of technical experience), dual boot Android package for my Venue 8 Pro. It looks like I may never get that and believe me, I am not happy about it. I can now only hope that what is delivered will be usable on my next windows tablet.

      @Anthony Horne: re x86 - touché!

    37. Mobile Media Ventures, Inc. Creator on November 11, 2015

      @Ian - Our guide was delayed due to storms Sunday and Monday that knocked power out in the bay area. It's welcomed rain - we're in a severe drought, but it came at a bad time. We're hoping to get the work uploaded later this week. We have to make sure we ship this month, so like a cancelled flight, we have to reshuffle the deck to keep that on track.

      @Tommy de Neef - That is simply not true. Console OS contains additional drivers and enablers that are not part of Android-IA, including the ability to run legacy ARM apps, and a functional user environment. We are carrying that forward to a new kernel right now.

    38. Missing avatar

      Ian R on November 10, 2015

      @Harry
      If you think I haven't heard that KS is not a store, think again. I am well aware of the risks. When creators promise a reward and cannot deliver, under KS TOS, they are 100% liable to the pre-purchaser. I am NOT, by any sense a "backer" because that would mean I too would profit if there was a chance of success. The KS model is very much a pre-purchase system with great liability to the creator. I choose to voice my opinion and not get tread upon. You can choose to defend the creator as you wish, but don't use you opinion to attack those who are rightfully demanding exactly what was pushed during the pledge stage.

    39. ACH on November 10, 2015

      @Harry:

      "If you expect any Kickstarter venture to deliver exactly what they promise when they promise, then you should go to a store and not to Kickstarter!"

      They absolutely need to deliver concrete backer rewards at the very least, which they haven't.

      "Christopher Price is a well respected member of the Android community and I there is no way he would risk his reputation just to rip of people on Kickstarer for $78,497."

      Certainly not well-respected among the android-x86 team.

    40. Tommy de Neef on November 10, 2015

      @Lucas The 'early build' is a total copy paste is Android-IA, nothing added, nothing removed, same installer and everything..

    41. Missing avatar

      Harry Elliott on November 10, 2015

      @pk, Thank you for your refreshingly respectful and honest reply. It seems congenial discourse is the exception to the rule around here sometimes. I understand your point, but I do not think the team is in over there heads. I think they have been pretty clear about why they have struggled to date. I am pretty sure the double whammy of Google's Lollipop rules and the Intel suspending support for Android on Core, both of which happened after the Kickstarter campaign ended, would have stopped most companies in their tracks. Those two events were huge impediments to the original plan and I think that they have been pretty clear about it.

    42. Missing avatar

      pk on November 9, 2015

      @Harry You are entitled to have your opinion and I respect that. I can't speak about Christopher Price, I don't know him. What I do know is that EVERY time this project sets a time frame, it fails to deliver. Head on over to the Campaign page and have a good read of that and decide if that have been met for ANY backer. This wasn't our commitment, it was theirs and they haven't met it.

      As to the reasons why they can't meet their commitments, all we can do is guess (unless you have some really good insight in to why). My theory is that they are in over their heads and have invested their own funds and can't see a way out and so have to keep the dream alive.

    43. Missing avatar

      Harry Elliott on November 9, 2015

      @Ian R, @pk, by my count, there are exactly 58 out of 5,695 backers who pledged $100 or more. 5,137 backers pledged between $10 and $24 dollars and based on the total amount raised the vast majority of those pledged $10. Kickstarter is not a store and it is not without risk. If you cannot afford to lose what you pledge, you should not pledge. I have lost far more on other projects than I stand to loose here. But I back projects because I believe they are worthy and I hope that they succeed. If you expect any Kickstarter venture to deliver exactly what they promise when they promise, then you should go to a store and not to Kickstarter! Christopher Price is a well respected member of the Android community and I there is no way he would risk his reputation just to rip of people on Kickstarer for $78,497.

    44. Missing avatar

      Ian R on November 9, 2015

      @pk

      Actually, yes. All sarcasm aside, when someone asks for my money with the promise of votes and an OS, and I give it to them, I expect them to deliver exactly what they promised. No matter what the pre-purchase amount is.

    45. Missing avatar

      pk on November 8, 2015

      @Ian, You aren't actually expecting them to produce something tangible. That doesn't happen here you know. The only reason that they communicate on here is that it is part of the Kickstarter terms that the engage with their backers until such time as they deliver the rewards. That it isn't factual or real bears little relevance.

    46. Missing avatar

      Ian R on November 7, 2015

      It is now "later this week" / weekend. How's the guide coming?

    47. Mobile Media Ventures, Inc. Creator on November 5, 2015

      Good morning all, we are preparing a guide that we'll release later this week. The guide will focus on steps you need to take before installing Console OS Lollipop.

      More specifically, it will handle the steps you can do right now to get ready, from backing up your machine to clearing out Windows temporary files (which is actually super important on Windows 8.1 tablets upgraded to Windows 10). It also will handle standard best-practices like updating your BIOS and backing up.

      More to come soon!

    48. Mobile Media Ventures, Inc. Creator on November 5, 2015

      Also, on the Kickstarter side, we have had a conversation with Kickstarter staff as late as last month. There is no claims by Kickstarter that we are violating any rule. They have not asked us to do anything different than what we have done.

      If they have concerns, we're more than happy to meet with them again. But to be clear, nobody at Kickstarter has claimed we have broken rules. If there was such a concern, we would bend over backwards to address it.

      Again, the Lollipop Logjam was something that Google's rules actively prevented us from being aware of while we were fundraising. We obviously would have provided different guidance had we received confirmation of Android on Core being suspended, and of things like Lollipop's dramatically reworked bootloader and update processes.

Show older comments