CyanogenMod plans a quick leap to Jelly Bean for version 10


Recommended Posts

CyanogenMod plans a quick leap to Jelly Bean for version 10, existing devices likely to tag along

cid-1338807413.jpg

Whenever there's a new version of Android, Steve Kondik and the CyanogenMod team tend to swing into action almost immediately with plans for a major revision of the fan-favorite platform overhaul. For Android 4.1 Jelly Bean, that swing will be faster than ever. The crew's early looks suggest that there will only be a few minor tweaks needed to merge Google's latest with the custom Android code, making CyanogenMod 10 a relative snap to produce. The update's release is still very much up in the air without the Android Open Source Project code available to modify; that said, device compatibility also isn't expected to be an obstacle. Any device that can run CyanogenMod 9 should run version 10 when it's released. As long as we're willing to wait for a stable 9.0 to emerge first, there are few barriers to making Jelly Bean that much sweeter.

Source: Engadget

Link: CyanogenMod post regarding CM10 on Google+

Link to comment
Share on other sites

I hope CM10 isn't going to be too hardware intensive, my budget Android phone runs ICS really smooth.

If anything it should be smoother due to Project Butter, but who knows.

Link to comment
Share on other sites

I hope CM10 isn't going to be too hardware intensive, my budget Android phone runs ICS really smooth.

If anything it should be smoother due to Project Butter, but who knows.

I ran an early JB rom a day after it was announced. REALLY smooth over ICS and faster as well. Love the new features and Google Now is pretty sweet. Since it is running better that ICS, you should have no problem on your budget phone. I switched back to my ICS build since the JB ROM had issues. Going to try another/newer ROM over the weekend that should have addressed everything.

Link to comment
Share on other sites

I haven't jumped to JB because of CM9 and a lot of the features I can't live without. I will make the move the second an officially CM10 nightly is out.

Link to comment
Share on other sites

I can't wait till CM10 releases an RC or goes stable. I'm using CM9 RC1, and it's pretty stable so far. I'll never settle for their nightlies, I don't have enough time to keep wiping/flashing my phone.

Link to comment
Share on other sites

I hope CM10 isn't going to be too hardware intensive, my budget Android phone runs ICS really smooth.

I have a ZTE Crescent (Orange San Fran II) which apparently will never get official CM9 (therefore CM10 neither) because it has an Armv6 processor and so can not have the OpenMax Integration Layer (and Qualcomm have stated that it never will) which means we can't get proper GPU acceleration for video, youtube, etc.

The rom still runs quite smooth for me though and to be honest I never watch videos on my phone.

This problem also applies to MANY other phones, the original Orange San Francisco (ZTE Blade), the Orange Monte Carlo (ZTE Skate) and lots of HTC ones included. It also prevents them being "officially" supported by CyanogenMod. You will still get other people porting them though.

Link to comment
Share on other sites

Yeah I read that too...

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 to http://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.

You can post comments on our Google+ post

[Source]

Link to comment
Share on other sites

AOKP plans on this too can't wait !!

BRING ON THE BEAN !!

Yup. Last Milestone should be out over the weekend and thats the last ICS build they are doing. I have AOKP on all my devices. Works great and love the extras included.

I am going to try the Jelly Belly ROM over the weekend and see how that goes.

Link to comment
Share on other sites

i wish CM was available for my Rezound. im getting tired of relying on official releases!

i put CM9 RC1 on my Touchpad last week. I cant believe i waited so long to do it!

Link to comment
Share on other sites

I have a ZTE Crescent (Orange San Fran II) which apparently will never get official CM9 (therefore CM10 neither) because it has an Armv6 processor and so can not have the OpenMax Integration Layer (and Qualcomm have stated that it never will) which means we can't get proper GPU acceleration for video, youtube, etc.

I have ZTE Blade, ****ty phone brofist.

Link to comment
Share on other sites

Those devices aren't even *that* old. Shame on Qualcomm and HTC for dropping support so quickly.

Link to comment
Share on other sites

Running 4.0.4 successfully here off the Cyanogen Nightlies for my T-Mobile Galaxy SII, i'm sure this phone will take on Jellybean just fine.

Link to comment
Share on other sites

I really hope my Evo 3D gets a official build, it never got a stable CM7 build and the current CM9 build (unofficial) makes the phone run really hot and battery life is horrible. I am currently running the ICS leak from VM/Sprint and it runs great but I really miss AOSP from my Evo 4G. Guess I can't complain to much as Sprint sent me 2 Evo 3D for free for all of my problems I was having with replacement Evo's. :) This phone is barley a year old and HTC and Sprint have both dropped support on these devices and the 3D is a great phone and quite powerful. I could care less about 3D functionality (I can flash to Sense if I really want it) or 4G as it's no existent where I live anyway.

Link to comment
Share on other sites

I really hope my Evo 3D gets a official build, it never got a stable CM7 build and the current CM9 build (unofficial) makes the phone run really hot and battery life is horrible. I am currently running the ICS leak from VM/Sprint and it runs great but I really miss AOSP from my Evo 4G. Guess I can't complain to much as Sprint sent me 2 Evo 3D for free for all of my problems I was having with replacement Evo's. :) This phone is barley a year old and HTC and Sprint have both dropped support on these devices and the 3D is a great phone and quite powerful. I could care less about 3D functionality (I can flash to Sense if I really want it) or 4G as it's no existent where I live anyway.

evo3d got the major bitch slap imho virgin mobile got ICS before sprints version .. hell boost evo design has 4.0 on it ..

Link to comment
Share on other sites

This topic is now closed to further replies.