Today it was reported that the Cyanogen Team will shortly start working on CM10, which of course will be based on the newly released Jelly Bean OS. They informed us that it will not take nearly as long as CM9 has taken, simply because there are minor tweaks in the Android code to get it from ICS to Jelly Bean. Was delighted to hear that because after playing with my buddy’s Gnex with Jelly bean on it, I got goosebumps. Could not believe how much smoother it was compared to ICS. I really wish I did not play with it now.
So now since we got word from the Cyanogen boys, it is time to hear from Android rock stars of AOKP. Lead designer Roman had some words to say about the upcoming plans for AOKP, such as retirement of certain devices, AOKP Milestone 6, and when they will start working on Jelly Bean. Here is what he had to say:
After a great deal of conversation within the team, I’ve decided to make a formal announcement regarding the future of AOKP.
To start, I’m officially announcing the retirement of the following devices as supported:
- HTC Incredible (inc)
- HTC Desire (bravo)
- HTC Evo 4G (supersonic)
- Amazon Kindle Fire (otter)
These devices have a number of problems for our team; first and foremost the fact none of us own any of them. Beyond that, they’re falling behind in terms of hardware, and maintaining them blindly defeats us before we begin in our goal to create stable releases. I’ve come to the conclusion that by supporting these devices we’ve overextended ourselves, and the team is in agreement. Long story short; we can’t release a Milestone build and call it ‘stable’ with these devices in our farm. The code for these devices will still be in our repos, so anybody who wants to compile them can do so if they wish… they just won’t be receiving “official” builds any longer. We’re all very sorry about this, but we feel it is necessary for the health of the ROM (and the team making it!).
Now that the bad news is out of the way…
Milestone 6 is coming! We are shooting for a release sometime this weekend. No promises! We’ve been working for the past few weeks to squash as many bugs as we can. This will be our final ICS release.
After Milestone 6, the team take a short break in preparation for Jelly Bean. We’ll be taking a different approach to JB; starting fresh. With a clean start, we’ll be able to set things up properly from the get-go. We’re a much more experienced unit now, and we believe merging all of the JB changes is just asking for trouble.
When I started AOKP back in November, I really hadn’t intended on releasing it to more than Nexus devices. AOKP has grown bigger than anyone has expected, most of all me. It quite literally blew up in my face. Right now, according tohttp://stats.aokp.co, there are almost 50,000 devices running AOKP and almost 120,000 devices using some kind of AOKP code-base (aka a KANG). Bear in mind this stats system was implemented only starting with build 39. This is absolutely insane to me!
In closing, Team Kang is just a small group, and AOKP was started for fun. We aim to keep it fun. Putting together a feature-rich and buttery-smooth ROM with unrivalled stability is fun both because of our love of doing it and getting to share it with all of you. Thanks for understanding the things we need to do to keep it that way.
Awesome to hear all that from the leader of the pack. I have tried AOKP on my phone and I have no complaints on what these boys have developed. Cannot wait to see where they take their “unicorn” when they start converting it to Jelly Bean. Let us know what you guys think.
Source: AOKP.co
Share This Article....
If you like that, Try these....
About the Author
Im sorry, but the ROM game isnt like it used to be in 2009-2010. I understand there are so many devices now to keep updated and change code for, but our premier phones and devices like the Evo and fire especially. Also waiting for a damn CM9 stable never seems to happen when they said it would come February of this year. Getting longer to wait between each. They used to update so quick, used to be able to buy a phone and never worry if a CM ROM would be available or not, they would be working on it. Now days, you have to watch what phone you have, will it get a stable ROM release, will the damn camera work in that release, its just crazy. For me, its Nexus straight on out, hopefully as long as Google doesnt switch to Moto as there only Nexus maker. I do miss features from CM, but ill live without as long as my Nexus runs perfect stock the way it is.
@FILA – Or you could stop complaining about how long it takes to get ROMs out and contribute.
CM9 has taken so long because the whole platform and their entire build process had to be completely redesigned from the ground up. It was a *MASSIVE* change from CM7 and older builds. It was essentially like switching from a RedHat based Linux distro like CentOS to a Debian based Linux distro like Ubuntu. The whole system is very different and required a very different process to build it and develop it.
As for watching what devices you buy, why is that an issue?
The CyanogenMod guys, the AOKP guys, and all the other AOSP based ROM teams out there are *DONATING* their time and expertise to produce something for love. Its not like they’re getting paid to do it. Its not like they’re receiving money for every ROM package downloaded by end users. Its not like they’re forcing you to donate anything in return.
What this means is that these guys can only develop for, and build on, and support, the devices they themselves have access to. They can’t make a ROM that will work on Every device out there. Funnily enough, hardware is different across all manufacturers, and even inside product ranges (look at how many different flavours of the Samsung Galaxy S and S2 and S3 there are all over the world as one example.)
Your sense of entitle-itus is insulting and offensive to all those that do make an effort to contribute, that do donate money, time, resources, skills, expertise and generally volunteer to help in any way.
If you want a ROM built for a specific device, either help the devs by contributing a device to someone that can do it, or do it yourself. But don’t you ever dare complain just because you can’t get the ROM you want at the time you want it.