We’ll be restructuring our approach to Remix OS and transitioning away from the consumer space. As a result, development on all existing products such as Remix OS for PC as well as products in our pipeline such as Remix IO and IO+ will be discontinued. Full refunds will be issued to ALL BACKERS via Kickstarter for both Remix IO and Remix IO+. In addition any purchases made via our online store that has remained unfulfilled will also be fully refunded. This requires no action from you as we will begin issuing refunds starting August 15th.
In the light of Google pursuing further Android-ChromeOS convergence, they may have come to conlusion Remix OS future is shaky. Piggybacking is always a gamble.
Sooner or later Google would have caught the iteration. Hence it’s been a 3 years old gamble though…
They had hoped they would get far enough along that Google would just buy them out rather than implement the features themselves. Google has instead decided to work on replacing the whole underlying system making their work redundant.
I was hoping Jide would get far enough along that one could install it onto Chromebooks in place of ChromeOS.
A desktop-oriented Android install, with proper multi-window, and mouse/keyboard support would be much nicer than shoehorning Android app support into the Chrome browser, IMO.
I don’t think either approach is going to get all that far if the apps aren’t properly equipped to treat kbd/mouse as an equal to touch input. Ironic really, that iOS apps have more keyboard shortcuts than Android apps do even though Android, as an operating system, has better keyboard support built into the basic UI and thus better support for direct keyboard navigation.
Remix OS would either not install properly or not support network cards I threw at it.
Don’t really feel the effort was put in. So, not surprised at this outcome.
About how they handled this.
Theres Phoenix OS that is way ahead:
http://www.phoenixos.com
Hrm, interesting. Wonder if this would install onto a Asus eeePC 1005 that I have kicking around …
Is it still incompatible with AMD CPUs?
There are a few of us with AMD hardware out there. Last time I couldn’t install your product at all.
It was dead in the water from day one as far as I was concerned, due to the oppressive license.
Nope, sorry, my content is my content. If I take a photo with a Nikon camera, Nikon has zero say in what I do with that photo. It’s the same with a computer OS; Microsoft doesn’t own the rights to a single phrase or word I type while working in Windows, and neither should Jide.
Good riddance.
I have no idea why they included such an over-the-top clause. I guess if ever tested, it would have been null and void
Maybe someone should flood them with pedophile content and report them to the nearest police station – after all they claim they own it, so they should die from their own sword
As there had not been any updates since, I guess last October, this was something I had been expecting.
It is a bit sad, as this was a project with active partnership with the main developer of Android x86. I hope this does not stifte the further development of Android x86