Share this project


Share this project

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. (
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.

Use this space to cheer the creator along, and talk to your fellow backers.

Have a question?

Only backers can post comments. Log In
    1. Missing avatar

      alan robinson on July 27, 2015

      I would also like a refund. All i keep hearing is excuses, surely you must run out of them soon.

    2. Hifihedgehog (AKA "That Headphones Guy") on July 25, 2015

      @MMV: Explain how you do not have a choice whether or not to give the money to the backers. Are you saying that the remaining funds are so low you could fulfill what was promised? Clear answers for those who want what they paid for, besides paying to support what they initially thought was a worthy cause, is what everyone now wants. There is an elephant in the room and everyone wants to know what is possible financially for rewards. More than anything, they want a choice since their money should talk for the project they backed. Else, individuals may ask for Kickstarter to initiate an investigation so you truly don't have a choice.

    3. Missing avatar

      Steve Clark on July 25, 2015

      How does one see about getting a kickstarter refund since this project is apparently DOA?

    4. Mobile Media Ventures, Inc. Creator on July 24, 2015

      @That Headphones Guy - We would ask if we had a choice. At the moment, we don't.

      On the bright side, we have received a new round of Mixed Mode patches from Intel. We will begin testing them over the weekend.

    5. Hifihedgehog (AKA "That Headphones Guy") on July 24, 2015

      While i agree that financially the best course action would be to postpone the delivery of all physical rewards, you forgot one absolutely vital step before you made this decision: you forgot to ask the backers, the ones who are footing your bill. Do a poll and see if waiting is actually what they are willing to do. You may be ticking off the majority of backers right now for putting their physical rewards on the chopping block. For people who donated more, which fortunately does not include me, the incentive that drew them to donate more is essentially gone if you are going to risk the funds needed to deliver their goods. Please, out of decency and respect, ask first.

    6. Mobile Media Ventures, Inc. Creator on July 23, 2015

      Latest ETA is either Friday or Monday for delivery of a new set of patches to try and restore Mixed Mode to the Android Linux 3.14 kernel.

      As soon as we get them, we'll begin testing and integration.

    7. Mobile Media Ventures, Inc. Creator on July 22, 2015

      @Tony - We addressed that in our last comment. Until we can stabalize Android-IA for Lollipop, we are not going to spend any more Kickstarter funds.

      Unfortunately, our upstream hardware partners did not honor their commitments to support certain things. We're having to pick up the slack. Which do you want, Console OS to keep shipping? Or a laptop skin? We may be at the point that we have to make that decision for the community.

      But if we do, we'll give you an email address or two to nastygram upstream at our hardware partners, should it come to that. We're not there yet, and to be honest, we're still hoping to turn things around and get things like Android on Core... back on track.

    8. Missing avatar

      Tony on July 21, 2015

      It seems to me that Lex was referring to the items listed as rewards for each of the different backer levels. Has anyone here received any of these items? The free month of Spotify? A pre-launch flier? The laptop skins? The t-shirts? A personal G+ hangout? An Intel 2-in-1 laptop with console os on it?

      Anyone? Anyone?

      $25 reward

      105 backers

      Backer Plus. You get Console OS Pro free for life, 25 hardware votes, and also:

      * One month of Spotify Premium
      * A signed pre-launch flier
      * A custom Console OS laptop skin

      Estimated delivery: Dec 2014
      Ships anywhere in the world
      $50 reward

      145 backers

      Give one, get one. First, for giving us $50 or more, you get a special launch-edition T-Shirt. We'll post the design in an update. But, more importantly, you get to gift Console OS Pro v1.0 to a friend in addition to your own copy... and you both get free upgrades for life.

      Estimated delivery: Dec 2014
      Ships anywhere in the world
      $100 reward

      52 backers

      Lifetime recognition. In addition to everything in the $50 tier, you'll also get your name immortalized in the Console OS About Box. Geeky homages welcome, dirty stuff - not so much.

      Estimated delivery: Dec 2014
      Ships anywhere in the world
      $500 reward

      3 backers

      Wealthy Benefactor - You get ten copies of Console OS Pro to gift to others. And, you get a personal Google+ Hangout with at least a few members of the team to say thanks, and tell us what you'd like to see from Console OS.

      Estimated delivery: Dec 2014
      Ships anywhere in the world
      $1,000 reward

      3 backers

      Major Award - You get ten copies of Console OS Pro to give away free-for-life benefits to others. And, on top of that, we'll also send you an Intel 2-in-1 laptop with Console OS all set up on it.

      Estimated delivery: Dec 2014
      Ships anywhere in the world

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

      @Lex - We have delivered Console OS DR1. Check the updates tab and view the backer-only updates once logged in. We said we would deliver Console OS for most target devices by the end of 2014, and we met that goal.

      As to other perks, as we have mentioned, keeping Console OS alive through the Lollipop Logjam is our top priority. Intel did pull the rug out from us by pulling support for key features we depended on (IAGO, Android on Core, etc) after our Kickstarter ended. Once we ship Console OS DR2, Lollipop, in open source, we will review what resources we have and keep shipping.

      We may have to put up remaining funds as bounties to assist where needed, and also launch a campaign to encourage hardware partners to keep supporting what you want us to support.

      It's not ideal, but it is the best plan to keep Console OS going. We're welcome to suggestion... constructive suggestions.

      At the moment, as you can see in depth below, we are waiting on patches to fix the Mixed Mode situation, which (ideally) will enable us to continue shipping for Bay Trail tablets and also finalize iConsole micro... ideally.

      (And yes, we get backers emailing us asking to re-re-re-summarize what we have posted below - all the time).

    10. Lex Chien on July 20, 2015

      I have yet to receive any of my awards. What gives

    11. Mobile Media Ventures, Inc. Creator on July 19, 2015

      Update on the Mixed Mode slog - After several conversations between our engineers and Intel engineers, we determined the Mixed Mode fixes we were sent... were defective. Stepping up to a newer kernel would not resolve the situation.

      This puts the ball back in the hands of Intel's EFI/Kernel engineering team, and we hope to have a revised fix later this week. We realize this is week four of just one issue. But by giving such great detail, we hope you understand why we have been stuck in the mud for the past nine months.

    12. Mobile Media Ventures, Inc. Creator on July 19, 2015

      @Michael - We appreciate that you're willing to free us from, what has honestly been an uphill battle - but we don't think other backers are as considerate. Further, it wouldn't help - we need to stabilize the Android-IA kernel across several systems before we can really grasp any other targets.

      KitKat is obsolete at this point, but Lollipop is quite aligned with Android M. So the work we're doing today should hold for Android M too.

      Even without Mixed Mode, we're finalizing support for Bay Trail-M 2-in-1's and laptops, and we are preparing to make one final effort for Android on Core. We think it's the best case yet. When it's time to involve the community, fear not, we will.

    13. Missing avatar

      Micheal S Hood on July 18, 2015

      It seems to me that you guys should have figured out that the Lollipop project should have been scrapped over 6 months ago. It's simply amazing that you keep beating this dead horse. Stop! Focus on something you actually might be able to accomplish! I knew from the moment I saw the voting results that this was going to end up being delayed, but I never thought it would end up being such a fiasco.

    14. Mobile Media Ventures, Inc. Creator on July 18, 2015

      @Arul - As we have said, as soon as we clear these blocking issues in the Lollipop Logjam, we'll begin shipping builds again. We'll resume shipping the source as soon as we have something buildable - even if only on a small set of UEFI32 Bay Trail tablets.

    15. Missing avatar

      Arul Jayanth Muthukumar on July 18, 2015

      So, now what is the possible time frame for releasing console os? Will it be within this year?

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

      @Tony - We need folks to stay realistic here. What we said was we may get Mixed Mode fixed next week. Not that we'll be releasing next week.

      We still have to do much testing, see if there are other blocking issues, and package the code up for shipping... then send it on to vendors to review and make sure we didn't leak anything out.

      That all takes time. Time we weren't supposed to be into July on, but without getting Mixed Mode fixed... we can't even boot the kernel to see what we have left to do. Mixed Mode shouldn't have been taken out of the Android-IA kernel, but we're all working on getting it back in there - so we can see what's left to do.

      Likely because of these delays, you can expect we will focus our efforts on open-sourcing Console OS first - so that the community can help us attack remaining issues (Mixed Mode is too big for the community we're afraid). After that, then we can start shipping compiled builds again.

    17. Hifihedgehog (AKA "That Headphones Guy") on July 16, 2015

      Inching ever closer... Woohoo! Hopefully, no more foreseeable speed bumps. The projected renewed interest in desktop computing from Windows 10 may actually make Console OS more appealing again. You and us need Intel and your other hardware partners to retain support for Android. This will be focal point of our success in the end.

    18. Missing avatar

      Tony on July 16, 2015

      This is wonderful news! We will finally see the project realized next week! Woohoo!

    19. Mobile Media Ventures, Inc. Creator on July 16, 2015

      Update: Our latest efforts to get Mixed Mode up and running hit another speed bump... to make a long story short, we have to step up the kernel a few more revisions (fifteen to be precise).

      Once we complete that step-up, we'll lather, rinse, and repeat trying the latest bevy of patches. This process could take 1-3 business days because we have to obtain external patches, so it may spill into next week.

    20. Mobile Media Ventures, Inc. Creator on July 15, 2015

      Correction: We referred to "Google Secure Boot" - the correct name for Google's initiative is Verified Boot. But it connects with UEFI Secure Boot, which we also have to support underneath as that is how Google complies with Verified Boot.

      Note that you will continue to be able to use PCs and PC Tablets with Secure Boot disabled. The nice thing about all this painful transition is that we are prepared for Windows 10 devices, wherein it may not be possible to disable UEFI Secure Boot. You will be able to boot signed Console OS builds and open-source builds where we sign the kernel with the VeriSign Other OS key.

      We will begin that signing process if and when it becomes necessary. We hope most OEMs continue to offer an option to disable UEFI Secure Boot, and we encourage you to contact OEMs and tell them that - should the need arise.

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

      Let's clear up some misinformation here.

      Nowhere did we say we were contemplating dropping support for Bay Trail. We'll spend every last penny of Kickstarter money, if that's what it takes. We'll bounty out bugs we can't fix.

      We are committed and determined to that goal. Just today, we received new bug fixes from Intel that we are exclusively testing.

      We do hope to support Cherry Trail once Intel offers ISV vendors a BSP for it. Bay Trail will continue to be supported on Console OS for as long as Intel publishes a BSP for ISVs.

      Intel has suspended development of Android on Core. We are working with Intel to create a path that resumes development... clearly we have expressed our dissatisfaction to them on this decision.

      We were not involved in the decision to suspend development of Android on Core at Intel. And we were not notified of it until after the Kickstarter campaign ended. In recent months we have begun to have opportunities to make the case that development should resume, and we have spent the "downtime" working with OEMs and vendors to make a more compelling case. You'll see the results of that down the road.

      As others have already done below, you're free to check with Intel to see if we are misrepresenting any of the above. This has all been independently verified.

      @Alex - We are having to completely rebuild the bootloader. Part of the Lollipop Logjam is that Intel was forbidden from telling us that Lollipop added additional security restrictions - preventing our existing Intel-built dual-boot system from working in Lollipop. Dual-boot tablets from China use two separate BIOS - something we obviously can't just install on an existing system.

      Our replacement bootloader will build atop the new, Google Secure Boot-compatible bootloader, which Intel calls KernelFlinger (along with its non-OTG subsystem, UserFastboot).

    22. Missing avatar

      tim on July 14, 2015

      @Sebastian, I totally get what your saying. I too have a dv8p and that's why I supported the kickstarter. I installed the rc1 on my surface pro 2, but without sound and WiFi and BT support it was pretty much useless. I guess at the end of the day I see this (for me).... Its a non-licensed gapps product, it will never support widevine, and that's needed for DRM (rhapsody, dishanywhere,hbogo). I'm personally not satisfied only running apps that work from the amazon store. I did install gapps and downloaded using the play store, but the apps I wanted were hit and miss when it came down to actually running. When I asked for help, I was offered nothing to solve the issues.
      Hopefully developers will embrace the Astoria SDK as the world transitions to Windows 10. As for BayTrail... I would buy a dual OS tablet from china.. Teclast or Pipo that may be the fastest route to what your seeking. As for me, I check out this site once every two weeks to see if anything has changed... I believe they want to do right, but don't have the resources to get it done. As for a roadmap. If your spending all your time working on a chipset that is old, you may not have the resources to work on the chips coming down the pipeline. And you will always have a product that is untimely. I'm sure this is why dell never released a firmware needed to run this OS... Why invest hours on a dead chipset. Any how....

    23. Missing avatar

      Sebastian H.
      on July 14, 2015

      @Alex Cutter: I asked MMV to look into this problem and provide a solution. But they don't seem to care. They only pointed me to the forum posts you found that only lead to more problems. But hey, they delivered DP1 before the end of last year, that's all we're suppposed to care about. Nevemind the fact that DR1 runs just barely on some devices and not at all on many others...

    24. Missing avatar

      Sebastian H.
      on July 14, 2015

      @tim: There are quite a few people who backed because MMV claimed support for Bay Trail devices. When you're now suggest dropping Bay Trail support that is a slap in the face of those people. I for one still have my DV8P and see no reason to buy something new. Also, MMV made a promise to their backers.

    25. Alex Cuttler on July 13, 2015

      I've posted on the forums, I've sent messages, so I guess the next stop is here. My computer is not one of the supported devices, but hopefully the issue I'm having can still be solved. Every time I run the installer, I get the block 63 error. Julian on the forums posted a workaround that resolved the block 63 error, but presented a new error. The installer now hangs at "Resizing the filesystem on /dev/block/sdb9 to 973831168 (1k) blocks". Anyone know what could be causing this and how (if possible) I would go about fixing this? Thanks.

    26. Mobile Media Ventures, Inc. Creator on July 12, 2015

      @Tim - While Cherry Trail has been announced, it is unlikely that you will see many Cherry Trail devices before Android M. Cherry Trail has an easier launch ramp on the Windows side because there are fewer changes needed there.

      More importantly, like all Intel processors, Bay Trail will continue to be sold alongside Cherry Trail for a considerable period. The Intel Compute Stick launched, with Bay Trail, in the last few weeks for example. We still hope to ship iConsole micro using that technology - it will still be the most powerful Android TV stick launched.

      As to Core M and Broadwell, we are preparing our final push to convince Intel to resume development there. If unsuccessful, we'll take it to the streets, and ask you to tell them to do it. But, these initiatives, pushes, and campaigns take time. And right now, Intel is listening.

      We know it stinks to ask people to wait, we're feeling that pain (literally, physically, and monetarily) much more than you guys right now. But - there's still a path to getting Android back on Core, and really changing the notion of what Android can do.

    27. Missing avatar

      tim on July 11, 2015

      Does anybody really care about bay trail anymore? Other than for novelty purposes? Intel has new chips out now, I wouldn't waste my time or money on a legacy cpu unless I had a very specific reason or cost I had to hit.

    28. Mobile Media Ventures, Inc. Creator on July 10, 2015

      Happy Friday all. We're making the progress that we had expected on reviving the 32-bit kernel... a painful setback but we certainly have the time on our hands.

      On a brighter note, we can confirm Intel is analyzing and working on restoring Mixed Mode to the Android 3.14 kernel. They have acknowledged that this roadblock pretty much froze all 40 million Bay Trail tablets from running any community build of Android... which again, was nobody's intention. So, we are holding off on burning Kickstarter funds in a bounty-thon.

      Meanwhile, our graphics peeps are working on a revised branding and logo for the Lollipop re-launch. Feel free to tweet/retweet/post feedback:

    29. Missing avatar

      Tony on July 10, 2015


    30. Hifihedgehog (AKA "That Headphones Guy") on July 9, 2015

      Yep. Just sharing my distraughtedness for the bad turn of luck for the good guys behind the project here. :)

    31. Mobile Media Ventures, Inc. Creator on July 9, 2015

      @That Headphones Guy - Preaching to the choir here. We cannot support a device unless the silicon within it has Android drivers. Once we ship Console OS for Bay Trail, we'll have more flexibility (and resources) to help you get that message out to the people that matter.

    32. Hifihedgehog (AKA "That Headphones Guy") on July 9, 2015

      Well, that stinks for us. Intel is probably banking on Windows 10 pulling ahead with its goal of a projected 1 billion device userbase and thus eliminating the need to invest in Android support. It's a real pity for everyone here, though, especially what with the leaked Skylake Core M benchmarks showing a graphical performance boost of five- to ten-fold that would be a dream for Android gaming. And yes, this performance does outdo even entry level Nvidia graphics! See for yourself by playing around with this tool here:…

    33. Mobile Media Ventures, Inc. Creator on July 9, 2015

      @That Headphones Guy - As we have mentioned, Intel has temporarily suspended development of Android on Core, including Core M. This occurred after our Kickstarter campaign ended. We are continuing to discuss with Intel resuming support for Android on Core processors - we have to prove there's sufficient demand there. We're confident that with Console OS going open-source, that we can demonstrate that demand... but it's going to take time.

      @Ron - Unfortunately, there are no plans at any OEM to upgrade BayTrail-T devices to 64-bit firmware from factory 32-bit. The problem is if someone were to run a Windows System Restore, and not then immediately run Windows Update, the InstaGo bug could be flashed back onto the device. For that reason, most OEMs are just going to wait for the next hardware cycle to ship 64-bit firmware, with Cherry Trail devices.

    34. Hifihedgehog (AKA "That Headphones Guy") on July 8, 2015

      I can't wait to see something functional now come because Intel and partners, new and old, are getting closer and closer to putting the pedal to the metal and getting the kernel in working order. Just out of curiosity, how does Console OS run on Core M hardware, specifically the Dell Venue 7140? (Anyone who has tried running it besides MMV is welcome to answer this question.)

    35. Missing avatar

      Ron Coit on July 8, 2015

      Thank you fro the detailed response. It makes it much easier to appreciate the position you are in.

      Have you considered multiple releases. I understand that a lot devices you are targeting are atom based wit 32bit firmware (including my own) and I certainly don't want you to give up on them, but there must be a lot of devices with 64bit EFI firmware OR even old BIOS firmware that do not have this problem that you could release to now.

      Just a thought ;)

      Again thanks for the feed back

    36. Phil on July 8, 2015

      Thanks for the update! Good to her what's going on, even thought it's mixed news

    37. Mobile Media Ventures, Inc. Creator on July 7, 2015

      And yes, we have tried ourselves to just graft Kernel 3.15's Mixed Mode onto 3.14 - there are too many differences to just copy-paste that in. EFI Mixed Mode depends on EFI_Stub and many other calls that vary greatly between the two branches.

      It's going to be far easier to clean up the 3.14 backport that broke between MR0 and MR1, than to recycle 3.15's kernel code.

      But, we are still working on it. We don't want to jump the gun, but we're getting more optimistic this will be resolved.

    38. Mobile Media Ventures, Inc. Creator on July 7, 2015

      @Ron - The problem is that Intel decided to use Kernel 3.14 for Android-IA Lollipop kernels. We can't step up to 3.15+ yet... and probably not until a future major Android revision.

      You are correct however that this will not be an issue in future Android kernels. But unfortunately, it is today. Intel is actually way ahead of Google, using kernel 3.14. For Lollipop, Google uses Kernel 3.10.

      That may sound like ancient history, with the Linux kernel past v4.0, but this is how Android works. Android cannot use the latest Linux kernel because it would cause major reversioning issues.

      Groups like Linaro and Yocto are working however to remove many of those barriers, and that's why we're so happy that Console OS, and Android-IA are now using, Yocto-infused releases... it greatly reduces the odds of this kind of problem happening in the future. But we still have to get through it today.

    39. Mobile Media Ventures, Inc. Creator on July 7, 2015

      @Samit - The instructions are in the Updates tab (we did send the email notifications via Kickstarter). Simply log in to your Kickstarter account and tab over to Updates, scroll down and read the instructions a few/several posts lower.

    40. Samit on July 7, 2015

      BTW, I was no aware this had launched and I do receive Kickstarter emails normally, so don't think it would have gone to spam. How do I go about downloading my copy. Thanks!

    41. Mobile Media Ventures, Inc. Creator on July 7, 2015

      @Cykit - To be clear, we promised backers that we would ship a working beta of Console OS for most target devices by the end of 2014. We met that goal.

      All Kickstarter projects have a potential risks section - we're required to. Even if we weren't required to, we readily noted that one major risk with Android is that Google prohibits partners from alerting others about what is coming in future versions. The Lollipop Logjam was something that Google actively prohibited partners, including Intel, of explaining to us.

      What will not tolerate people, yes even backers, accusing us of lying or intentionally misleading the community. Full stop. We have absolutely zero benefit in doing that, and our only goal is to start shipping builds of Console OS for Lollipop as quickly as possible.

      When a timetable has an issue, we have been totally open and honest... at times to the grief of some of our partners, but as we (and others) have demonstrated, not to the detriment of the community.

      And with that, we're getting back to work testing our Plan B - of resuming 32-bit kernel shipments while others are working on Mixed Mode. We're optimistic we'll have tangible progress on that path sooner... and as usual, we'll keep you posted.

    42. Missing avatar

      Cykit on July 7, 2015

      Well, I agree some of the technical issues are not easy, however we backers did not set up the time table, you did. And you revised it again, and again, and again. And you never deliver. If you are about to tell us "hey, you are going to use android on your current Intel device in two to three years! Native!" when you started the campaign, my bet is you will probably not get much. So before you accuse YOUR BACKERS passive aggressive, nay-Sayers, or whatever you call them in the comments, ask yourself, so far what have you delivered, how many deadlines that were set by yourself have been met, and master of lingo, what would you call people like that who do not keep their promises?

    43. Missing avatar

      Ron Coit on July 7, 2015

      Sorry I forgot to mention bellow that I am exclusively using 64bit kernels in the comment bellow, which is what the mixed mode problem is about. 32bit kernels are not a issue with 32bit UEFI firmwares

    44. Missing avatar

      Ron Coit on July 7, 2015

      The thing I don't understand is that the Linux kernel has supported mixed mode since 3.15 (out around April last year). I have been using GRUB to boot into Linux on my BayTrail tablet (Lenovo MIIX2 8") with 32bit firmware from USB for months now with different kernels and it mostly works find. Some hardware does not work (SD is read only, Camera does not work, bluetooth often causes a kernel faults) but, It boots up and runs a graphical interfaces, the touch screen and sound work great and I can connect to wifi. You guys are using a third party Linux kernel, not a Android specific kernel, so the patch should already be there. Even before this patch came out I understand that it was still possible to booth a Linux kernel as long as you turned off some features that required it to communicate with the firmware.

      I am not trying to accuse you of guys of anything and I am sure I must be missing something, but I just don't understand why this is a problem?

    45. Missing avatar

      Harry Elliott on July 7, 2015

      @MMV - I appreciate the updates. I understand the delicate balance of trying to run a project AND trying to keep your various constituents adiquatly informed. Not an easy task, but I do concur with @Owen Shadbolt's comments below. For what it is worth, I reached out to someone who works very closely with Android on Intel and they either confirmed through their direct knowledge or deemed highly likely based on what they know the technical issues addressed by @MMV in the last two posts.

      Since I am going long here, I will attempt to add a bit of levity. My current dream device would be a dual boot Win10/Console Surface 3 with LTE, where I can use native GoogleHangout in Console as my primary phone number (yes, I get that I need to add Gapps, etc). Talk about Phat Phablet! I cannot wait to see the look on peoples faces when I hold it up to my ear!

    46. Missing avatar

      Owen Shadbolt on July 7, 2015

      @MMV, Awesome update, thank you! I for one do understand the difficulties you are facing and hope you continue to work through them. The one thing I would ask is that you keep updates like the last two coming.

    47. Mobile Media Ventures, Inc. Creator on July 6, 2015

      @Peter - You can check with Intel if you don't believe us. They have acknowledged everything we posted below.

      While Microsoft did fix the InstaGo issue, unfortunately, Intel has decided that all production BayTrail tablets will continue to use 32-bit firmware, until the next generation Cherry Trail tablets arrive.

      This is because Intel can't tell which devices have fixed InstaGo software, and which do not.

      (And please don't reply saying you have no plans to read our reply - it's passive-aggressive at the least).

    48. Missing avatar

      pk on July 6, 2015

      In all honesty, you talk a good story but I don't believe you.

      The issue you seem to be talking about is the the Istago feature from Microsoft which was buggy on 64bit. Therefore they shipped with 32bit firmware.

      Here is the point, this was resolved at least 12 months ago.

      From my perspective, I believe this project to be dead in the water but feel free to prove me wrong. No need to reply as I will no longer visit this project to follow its progress

    49. Mobile Media Ventures, Inc. Creator on July 6, 2015

      Hello everyone. We have constructed a patch to the Mixed Mode issue - but it is still not working. We are still on it.

      To recap, Mixed Mode is needed because of a perfect storm of Intel woes. Intel locked all consumer Bay Trail devices to 32-bit firmware (due to a Windows 8 bug), then created Mixed Mode to allow them to run 64-bit Linux kernels (including Android Lollipop). Unfortunately, between Android 5.0 and 5.1, Intel removed Mixed Mode.

      We have talked to the very engineers that took the code out. They have admitted that they really didn't realize how devastating that this would be. But even they agree, it really whacked us hard.

      Unfortunately, because of how Android is built inside Intel, we are on a 3-4 month code lag behind when they do stuff. We can't just "roll back" either, though Intel has agreed to put things in place that will make it easier for us to do that in the future. Transitioning to - something they did in Android 5.1, will greatly help this.

      So where do we stand? We have offered four-figure incentives to people we trust to fix this, this week. If they can't, we're going to offer five-figure incentives to the community next week... using your Kickstarter funds to do it.

      We're not happy about this one, and we think rightfully so. But this is the best path we have at this point. Intel is in the loop, and we're isolating other paths to fix this - including resuming development and fixing the 32-bit kernel. Nobody wanted this to happen, and we're all trying to fix it.

      @Phil - As we have said in the past, we are using Kickstarter money to survive. We have to make rent. But we have kept a significant amount available for circumstances such as the above.

    50. Christoper Rogers on July 6, 2015

      With the June passing with, yet again, no release, I think we deserve an update. Please explain what the current situation is.

Show older comments