hi . google 15 november relaesed android 4.2 . CyanogenMod is relaesed android 4.2 ?
thanks CyanogenMod
first rule of cm, never ever ask for eta.
an0nym0us_ said:
first rule of cm, never ever ask for eta.
Click to expand...
Click to collapse
why not asking ?
Ask cm team themselves why they made that rule. And u probably could get proper answer if u ask that on cm's official forum. Maybe if u got lucky, cyanogen himself will answer it
Compiling android takes time let them do everything they are really working hard..
no release
FXP team discontinued cm development for 2011 devices, so no further release for us
Originally Posted by CYANOGENMOD
in facebook
CM 10.1 Status Update
So we continue to work through the merger of 4.2 code and our CM enhancements. A branch in our github repos called mr1-staging has been created to facilitate the merger and is the target for core CM items (not features).
mr1-staging is not meant to be compile-able, its only purpose is to be a staging grounds for our core work. Chances are, it is useless for independent builders.
CM 10.0 (4.1.2) code is in jellybean-stable, if you are working on a bug-fix for the last stable release, patches should be submitted against that branch. If/when we do another 4.1.2 release (ie CM 10.0.x), it will originate from code in this branch.
Once staging is done in mr1-staging, we will push all that code to a 'CM10.1' branch, and eventually back to our primary 'jellybean' branch. This process is in place to make sure that we effectively move forward from CM 10.0 code, instead of starting over as was seen with the jump from Gingerbread to ICS. Patches from gerrit will be accepted towards CM 10.1, but for now, please have patience while we work through mr1-staging.
While the 4.2 updates are on a smaller scale, they do present some changes that will need to be considered and will effect our implementation of features. Just to name them briefly: Telephony Split, Multi-User, Quick Settings, and Lock-Screen Widgets. These items will be a strong focus when the initial CM10.1 branch is created.
On the feature front, David van Tonder (dvtonder) decided to make his weekend productive, and has already worked on the code for the majority of our MMS enhancements: Emoji support, sms split, gestures and templates, quick messaging. Notably MMS auto retrieve is not being forward ported as Google fixed that themselves. As stated above, patches will hit gerrit review after this staging process is completed.
As always, a timeline isn't and won't be available. We will continue to provide updates as we have them.
Click to expand...
Click to collapse
Let's wait for further announcements
thanks but no CM10.1 for Neo and Neo V
mido_fedo said:
thanks but no CM10.1 for Neo and Neo V
Click to expand...
Click to collapse
CM 10 is available for Neo/Neov ..but its not the stable release ..they are close to making a stable release .. So I guess we might get 10.1 too
Abhiheart said:
CM 10 is available for Neo/Neov ..but its not the stable release ..they are close to making a stable release .. So I guess we might get 10.1 too
Click to expand...
Click to collapse
Even if we get a stable Cm 10 ,it would be worth it and I think Fxp would do that!
As for Cm 10.1,it's been answered already ,it's not just worth the efforts n hassles!
Sent from my MT11i using xda premium
---------- Post added at 09:42 AM ---------- Previous post was at 09:41 AM ----------
FXP said:
HY All
We said it already several pages back CM10 is last release for 2011 devices
Those devices use an old kernel (2.6.32) and old blobs for camera (ICS)
So even making those work with cm10 (jellybean) was an real pain
To update kernel to 3.0 we will require 6+ months (not worth for an 2 year old SOC) limited in hardware and memory
Even if we take this effort this device will not be able to handle next version of android after 4.2 because it simply lacks RAM
Even for Jellybean we had to use legacy camera to be able to use camera in an proper way (with broken panorama)
What's the benefit of having latest android if your device is not able to use new features?
We will continue fixing cm10 and releasing weekly updates with latest JB progress
Jerpelea
FreeXperiaTeam
Click to expand...
Click to collapse
Sent from my MT11i using xda premium
CyanogenMod 10.2 Nightlies brings android 4.3 jelly bean to Xperia Z Ultra. Download the CyanogenMod 10.2 Nightlies package for Xperia Z Ultra from the official CyanogenMod page. It is still unstable release, so there must be a lot bugs in this.
Post here your findings and bugs so we can help each other to work them out.
Download nightly
http://get.cm/?device=togari
Gapps
http://wiki.cyanogenmod.org/w/Gapps
Many thanks to the cm team!
No cm users that wants to share there findings?
boterkaaseneieren said:
No cm users that wants to share there findings?
Click to expand...
Click to collapse
There was a post started here http://forum.xda-developers.com/showthread.php?t=2503292
boterkaaseneieren said:
No cm users that wants to share there findings?
Click to expand...
Click to collapse
CM has little if anything to offer except a list of things that do not work and Android 4.3 (which is a moderate incremental step over the Android 4.2.2 Sony is using.) Even when CM goes to Android 4.4 some of the best features of 4.4 can be installed now with the current Sony software (launcher and hangouts.) What's the point of flashing a broken OS? Its not faster. Any customization can be done by rooting and installing recovery. You can hide apps with almost any launcher and do not even need root. A lot of features do not work. CM has lost any edge it had years ago when it improved speed, made customization possible, and closely recreated a pure Android experience. Flashing CM is as useless as it gets. Times have changed, the manufacturers have caught up with users.
Pretty sure this thread is for CM users
Sebring5 said:
CM has little if anything to offer except a list of things that do not work and Android 4.3 (which is a moderate incremental step over the Android 4.2.2 Sony is using.) Even when CM goes to Android 4.4 some of the best features of 4.4 can be installed now with the current Sony software (launcher and hangouts.) What's the point of flashing a broken OS? Its not faster. Any customization can be done by rooting and installing recovery. You can hide apps with almost any launcher and do not even need root. A lot of features do not work. CM has lost any edge it had years ago when it improved speed, made customization possible, and closely recreated a pure Android experience. Flashing CM is as useless as it gets. Times have changed, the manufacturers have caught up with users.
Click to expand...
Click to collapse
Dear all,
i own an Xperia P, now after all this while i know having a novathor chipset in our device is a curse. now We have atleast 10 roms based on latest 4.4 kitkat based on CM but each of it have bugs. this has been the case with all the previous CM versions. My Question is "Is it ever gonna happen that we would get a bug free,at least all the features enabled cm 11 version or its gonna be like all the other versions where the dev skips to the next version as soon as it arrives leaving the older version behind."
if thats the case then it time to sell my device and move on to another one. !!
Regards.
Joker. said:
Dear all,
i own an Xperia P, now after all this while i know having a novathor chipset in our device is a curse. now We have atleast 10 roms based on latest 4.4 kitkat based on CM but each of it have bugs. this has been the case with all the previous CM versions. My Question is "Is it ever gonna happen that we would get a bug free,at least all the features enabled cm 11 version or its gonna be like all the other versions where the dev skips to the next version as soon as it arrives leaving the older version behind."
if thats the case then it time to sell my device and move on to another one. !!
Regards.
Click to expand...
Click to collapse
Check this out:
http://forum.xda-developers.com/xperia-u/general/aosp-xperia-p-sola-t2684583
and keep your fingres crossed
Cheers
Cwikla
Well, that's about AOSP and while getting it perfect will certainly be a major step for a perfect CM some implementations are different (in fact this was a key factor in choosing to focus on AOSP -- upstream CM changes very often)...
About Bluetooth audio, it's almost a given everyone's waiting for the next version of Bluez (which will then need porting and experimentation) while for FM some progress by trial and error is apparently being made, and thank the ex STE company and their partners for radio support not having been ready a good 2 years ago...
Hi, some of you told me that want OMNIRom so I'm downloading sources now, I'll build 4.4.4, but next month I'll build OMNI 5.0 and others roms like du, but I have three reasons for build 5.0 next month:
1st, I have to sync all again in order to get 5.0 branch, and some roms don't have a solid base to start.
2nd, I want to see if CM device and vendor files for razr works, because, to build 5.0 i have to change some tools that only works for 5.0, so I can't build 4.4.4 like now.
3rd, I think that first build from CM comes on december, and it'll have a lot of bugs like 4.4, and the roms won't have a lot of stuff because, developers have to port all the features to lollipop.
Of course if someone wants to build it before me can do
Regards,
Juan Pablo Toniolo
And we should be lucky if the CM team make a working Lollipop rom for our phones...
Sent from my Razr XT910
welder73 said:
And we should be lucky if the CM team make a working Lollipop rom for our phones...
Sent from my Razr XT910
Click to expand...
Click to collapse
I think yes, because on omap4 and vendor and umts_spyder now have branch cm12, soooooo I'm sure that we have lollipop on RAZR
Guys, about support or maintience for all the roms that I build, I don't know how to, because I have 4 roms on my HDD Omni, DU, AOKP, and ProBAM, I love build roms, but I only have 250HDD reserved to android and now I only have 8gb free, so I can build only one rom(for xt910 and for xt912) per day. I don't want any money for this I only told you because, all roms that I build works but have some things that work bad or didn't work , I will try to do all my best to fix all the errors and give away stables roms to use it as daily driver, I can't try all the roms in slot stock so all the feedback would be apreciated.
To close this message. I want to ask you wich rom you prefer to build first(build, to build everything and try to fix some things), you have to know that I will make a new once a week for all the roms, but maybe for example I have to fix SU and a little thing in tiles for pro bam, in AOKP I want to change one thing to display the number of the month and I have to fix another thing that I no remember now, but think that fix anything on any rom tooks me one day, this will delay all the others maybe… my idea is to work on the errors at the week and in weekend, starting from friday, build all the roms, but, today and maybe tomorrow I want to work with Omni, so "weekly" builds from others roms will be avaliable from monday. The only thing that I want from you is to put all the "errors" or "bugs" in the "bugs" section in oder to be more easy to me to find all the problems that rom have, and fix it as soon as I can, and If you want I can upload to other server and put another build for BMM(with meta-inf changed, this will be the only change that I'll do)
Anndddd I delete "cellbroadcastreciever.apk" in order to have signal in all of the builds but of anyone needs this apk I can put ir again or make a flasheable zip to add again this app. And I have a new gapps with aroma installer made by me in order to install only the gapps that you want and install aditional apps, like whats app +, nova launcher and some usual apps
Regards and sorry for a extended message,
Juan Pablo Toniolo
tonyt. said:
I think yes, because on omap4 and vendor and umts_spyder now have branch cm12, soooooo I'm sure that we have lollipop on RAZR
Click to expand...
Click to collapse
Actually, I am attempting my first build with the CM12 source code.
Bobcus Leper said:
Actually, I am attempting my first build with the CM12 source code.
Click to expand...
Click to collapse
Any luck @Bobcus Leper?
Vlasp said:
Any luck @Bobcus Leper?
Click to expand...
Click to collapse
This morning I upgraded to 14.04 for performance reasons. After I finish syncing the cm12 repo, I will properly use the lunch command instead of the "outdated" breakfast one(I couldn't get blobs or device specific code). I will report back if I get a successful build.
Syncing should be done in a hour or two.
tonyt. said:
Hi, some of you told me that want OMNIRom so I'm downloading sources now, I'll build 4.4.4, but next month I'll build OMNI 5.0 and others roms like du, but I have three reasons for build 5.0 next month:
1st, I have to sync all again in order to get 5.0 branch, and some roms don't have a solid base to start.
2nd, I want to see if CM device and vendor files for razr works, because, to build 5.0 i have to change some tools that only works for 5.0, so I can't build 4.4.4 like now.
3rd, I think that first build from CM comes on december, and it'll have a lot of bugs like 4.4, and the roms won't have a lot of stuff because, developers have to port all the features to lollipop.
Of course if someone wants to build it before me can do
Regards,
Juan Pablo Toniolo
Click to expand...
Click to collapse
It would be great if you can focus more on DU 4.4.4 @tonyt.
taufiqs said:
It would be great if you can focus more on DU 4.4.4 @tonyt.
Click to expand...
Click to collapse
I will fix DU and AOKP, and then I'll build OMNI and AOSP 5.0 and DU(lollipop) and AOKP(lollipop) but first I have to build and fix all the ROMS 4.4.4 because when I want to build Lollipop I have to change SDK and other tools and I can't build 4.4.4 anymore
tonyt. said:
I will fix DU and AOKP, and then I'll build OMNI and AOSP 5.0 and DU(lollipop) and AOKP(lollipop) but first I have to build and fix all the ROMS 4.4.4 because when I want to build Lollipop I have to change SDK and other tools and I can't build 4.4.4 anymore
Click to expand...
Click to collapse
You are the best! Waiting for the last build then.