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
Related
Just one caveat: I have done searches (read: multiple).
How in the world does CyanogenMod get to all of the supported devices? All of a sudden once CM9 is released, for phones/tablets moving from CM7 to 9, does it go out to all devices or what? Does it need to get ported from the source for each and every individual device? In general, how is CM updated and how does it get out to the officially supported phones/tablets?
Cyanogenmod ROMs do indeed have to be ported to each individual device and maintained. Once a device receives official support from the Cyanogenmod team, daily changes made to the AOSP source code (tweaks and bugfixes by the various contributing devs) are automatically compiled by a "buildbot" and released at the end of each day (thus these builds are called "nightlies"). These nightly updates are then made available for download through the Cyanogenmod website and through ROM Manager. Once code updates reach a certain plateau, a "final release"-worthy balance of features and stability, the build is released separately as a "stable" build (such as CM7.1), though you can still download it from the website or from ROM Manager just as with the nightlies. CM9 will eventually receive the same treatment and be released in the form of nightlies and stable builds.
Further (highly recommended) reading can be found here: http://www.cyanogenmod.com/blog/the-current-and-future-state-of-cyanogenmod-nightlies
Has anyone seen John Connor?
so the nightlies don't have to be ported, but every major revision does?
hugabu said:
so the nightlies don't have to be ported, but every major revision does?
Click to expand...
Click to collapse
No.
"Porting" is just a word used for the process of making the rom work on any certain device.
So to answer your question, once the work of porting CM to the certain device is done, that port is used as the base for both the stable and nightly builds.
Look at the analogy of when a new phone comes out, case manufacturers create a mold to use to make their cases fit the certain phone, and that mold is used to make all kinds of cases. Same concept
Google has pushed Android source code for Jelly Bean
Google has now
pushed the Android 4.2 Jelly Bean
source code to the AOSP (Android Open
Source Project). The SDK platform is
now available to developers, so hopefully
we will see some custom ROMs based
on Android 4.2 appear in the not too
distant future.
The SDK includes access to a number of
features including interactive lock screen
widgets, a ‘Daydream’ interactive
screensaver mode, support for exteral
displays and native RTL support. We do
hope that Sony received the PDK prior to
this and is already hard at work
optimising Android 4.2. Time will tel
Source
http://www.xperiablog.net/2012/11/14/source-code-for-android-4-2-jelly-bean-released/
Sent From Xperia Sola White (MT27i)
Rooted Stock ICS
Hit Thanks If I Helped!!
Useless for our devices
Sony released sources to 6.1 soft(ics) few days ago.
Sent from my MT27i using xda app-developers app
Why isn't there any 4.1 Rom for Sony xperia p? Source code was released long.time back. Also it meets all the requirements of jellybean
Sent from my HTC One X using xda app-developers app
yes, but no one except fxp and sony are working on it
so development is going slow
screensaver? i hope "they" develop it :fingers-crossed:
Also CyanogenMod is working on it:
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 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.
From Google+ CM profile.
I'm a smultron user,
For high end models we could see a large number of roms present (we could even make a big list) but for xperia 2011 devices there are few roms out there but they are all stuck at ICS or JB 4.1 or 4.2.
The jellybean 4.3 are very very very few.
Since the android 4.4 [KitKat] is made considering the devices with 512mb ram like smultron can we see a large number of 4.4 custom roms with great features for our devices??
cybercop007 said:
I'm a smultron user,
For high end models we could see a large number of roms present (we could even make a big list) but for xperia 2011 devices there are few roms out there but they are all stuck at ICS or JB 4.1 or 4.2.
The jellybean 4.3 are very very very few.
Since the android 4.4 [KitKat] is made considering the devices with 512mb ram like smultron can we see a large number of 4.4 custom roms with great features for our devices??
Click to expand...
Click to collapse
Hmmm...the key word is " BE PATIENT " about it...there no Custom Rom yet for 4.4...just wait until Cyanogenmod Team release their Custom Rom first then ONLY then we can talk about 4.4 Custom Rom on Xperia 2011 devices...
iPusak Gaoq™ said:
Hmmm...the key word is " BE PATIENT " about it...there no Custom Rom yet for 4.4...just wait until Cyanogenmod Team release their Custom Rom first then ONLY then we can talk about 4.4 Custom Rom on Xperia 2011 devices...
Click to expand...
Click to collapse
yeah i cant wait man. i should try to be patient.
officiallysonyrebel has said in his beanstalk thread that android 4.4 is coming soon for xperia 2011.
cybercop007 said:
yeah i cant wait man. i should try to be patient.
officiallysonyrebel has said in his beanstalk thread that android 4.4 is coming soon for xperia 2011.
Click to expand...
Click to collapse
Haha....before you get too excited, here is another key word for you " COMING SOON "....are you sure its coming soon as officiallysonyrebel said????
perhaps you should read THIS and THIS....
Cyonagenmod team HAVEN'T started to build rom for 4.4 and yet officialsonyrebel confident that it will coming soon...for your info, Beanstalk rom are also base on CM source code...if Cyonagenmod haven't started building it then where will any dev get the source code????
i quote....
we will continue to work on the 10.2 code branch, in parallel to all of our Android 4.4 efforts. For those that will inevitably ask, we have not made any decisions with respect to what devices will make the leap to the KitKat code base and likely won’t have that information for a few weeks
Click to expand...
Click to collapse
We are not in a rush to get 4.4 builds out . We are going to continue the process of working on CM 10.2 M1 - getting that out the door and onto your devices. Further, we will 'finish' the 10.2 code base, similar to what we did with 10.1.
As a friendly reminder, please don't flood us with requests for 4.4 - we all want new and shiny things, but we will not do so at the expense of abandoning the hard work our contributors have put into 10.2.
Final note, a lot of folks are reading into the "512mb" item on the release notes. No, this does not mean a sudden resurrection of older hardware, there are dependencies beyond the RAM (and CM has enforced that minimum since ICS)
Click to expand...
Click to collapse
cybercop007 said:
I'm a smultron user,
For high end models we could see a large number of roms present (we could even make a big list) but for xperia 2011 devices there are few roms out there but they are all stuck at ICS or JB 4.1 or 4.2.
The jellybean 4.3 are very very very few.
Since the android 4.4 [KitKat] is made considering the devices with 512mb ram like smultron can we see a large number of 4.4 custom roms with great features for our devices??
Click to expand...
Click to collapse
I guess it is for a reason. In all JB roms on 2011 Xperias camera's quality is poor, also hard to make some stock apps and features to work.
iPusak Gaoq™ said:
Haha....before you get too excited, here is another key word for you " COMING SOON "....are you sure its coming soon as officiallysonyrebel said????
perhaps you should read THIS and THIS....
Cyonagenmod team HAVEN'T started to build rom for 4.4 and yet officialsonyrebel confident that it will coming soon...for your info, Beanstalk rom are also base on CM source code...if Cyonagenmod haven't started building it then where will any dev get the source code????
i quote....
Click to expand...
Click to collapse
officialsonyrebel: current update is the last update for 4.3 ... as we are moving level up to 4.4 Kitkat .. for all 2011 line up..
I again read what he wrote and it seems that he meant to stop 4.3 with that build and start to work on 4.4 when it is available...
Final note, a lot of folks are reading into the "512mb" item on the release notes. No, this does not mean a sudden resurrection of older hardware, there are dependencies beyond the RAM (and CM has enforced that minimum since ICS).
Click to expand...
Click to collapse
That's from the CM post ...
It will take lot of time & effort for a 4.4 port ..........Dont expect anything this month or this year for that matter ....
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...
This is unofficial build of OmniROM I decided to share with community.
Installation:
Copy ZIP to SDCARD
Flash boot from ZIP using fastboot
Enter recovery (HOME button when notif LED is on and logo is displayed
Do Wipe / Hard Reset
Install ZIP and GApps
Download:
ROM Download
Previous build:
ROM Download]
GApps Download
Notice: This is very minimal gapps, contains only needed apps and libs to work with Google Account and Play Store.
Info links:
OmniROM Project site
Source code (branch: android-4.4)
This is a Q&A thread for OmniROM Unofficial Build for Xperia 2011.
Please submit bug reports (if you found) using dedictated XDA DevDB form (on top of thread).
Please post non-development post about this project here, not on DevDB OmniROM thread (it's for developers)
Thank you for taking the time to make this ROM! Does it include the latest LX and CM changes? I'm asking because I had problems with VIber on the latest LX build, but they seem to be fixed on the build that hasn't been released yet?
EDIT: when I click on the download I get only the coconut version? Do you have builds for other MDPI phones?
Well it's a little bit not actual as LX (I haven't got gerrit merge access to device tree), but the most of bugs was solved.
pcfighter said:
Well it's a little bit not actual as LX (I haven't got gerrit merge access to device tree), but the most of bugs was solved.
Click to expand...
Click to collapse
What about builds for devices other than coconut?
I posted build for Haida also. Other can be builded for demand.
Button backlight doesnt turn off when the device is locked
You need to disable it until it's fixed
Changelog
BUILD 27.09.2014
* Synced with last LegacyXperia sources: (+ my change)
- Fixed "New SIM card inserted" dialog
- ALS works now - restored FXP auto-brightness values
- Removed WiFi Direct - chip driver doesn't support it at this stage - fixed WiFi hotspot
- Enabled Fast Charge support
- Removed solid blue led notification on recovery
- Improved memory management
- Coconut music light should work now
Will edit thread when build was uploaded
Download for haida and coconut: http://forum.xda-developers.com/devdb/project/?id=5840#downloads
Source code for our devices is included in omni's Github...why we dont got official nightlies?
Who knows ? @mikeioannina talked to omni devs, maybe we will got official nightlies soon.
as a flashoholic I'd love to test omni on my urushi.
Konstantinosj77 said:
Source code for our devices is included in omnis Github...why we dont got official nightlies?
Click to expand...
Click to collapse
pcfighter said:
Who knows ? mikeioannina talked to omni devs, maybe we will got official nightlies soon.
Click to expand...
Click to collapse
Unfortunately nightlies aren't enabled yet although I have tried to contact omni devs a lot of times since July. Last answer was that they were going to be enabled soon but still nothing.
I'm sorry but I give up on this, L is so close and I don't have the time to work on these devices anymore, they probably can't handle L properly anyway.
mikeioannina said:
Unfortunately nightlies aren't enabled yet although I have tried to contact omni devs a lot of times since July. Last answer was that they were going to be enabled soon but still nothing.
I'm sorry but I give up on this, L is so close and I don't have the time to work on these devices anymore, they probably can't handle L properly anyway.
Click to expand...
Click to collapse
I'm not sure I understood you correctly, you are stopping CM development for MDPI devices? Or you won't be developing android L for MDPI?
Well, if L will have higher minimum hw requirements then probably we will stop developing roms for xperia 2011 until google/CM/omni will end support for android KitKat.
Grof87 said:
I'm not sure I understood you correctly, you are stopping CM development for MDPI devices? Or you won't be developing android L for MDPI?
Click to expand...
Click to collapse
Both. I have no free time to maintain & build for 11 devices, there are known bugs that can't/won't be solved so there is no point in continuing this.
There is almost no external development help, understandable because they are 3 year old devices now and all the known devs have moved to new phones.
Latest builds can be considered as 'stable'. I will continue supporting LX until cm11 development is stopped. At the moment I am left with no testing device, so no new builds.
I'm not even thinking about L on these devices. Let's wait a few months to see how heavy it is compared to kitkat and then we can re-examine.
@mikeioannina
Well, I still have neo v for main phone
The first OMNI nightly builds for SEMC 2011 was on OmniROM downloads now ! Check it out on dl.omnirom.org
pcfighter said:
The first OMNI nightly builds for SEMC 2011 was on OmniROM downloads now ! Check it out on dl.omnirom.org
Click to expand...
Click to collapse
I'm using 20142810 build,I have to flash supersu.zip to have root access, other than that, this rom is very smooth.
Thanks dev.
Using the 1028 nightly.
some graphical glitches on instagram
offline charging not working correctly.I think this commit can help somehow https://gerrit.omnirom.org/#/c/9923/
Also tried OTA updating to 1029 nightly and it seems to work correctly(except the known kernel updating problem)
On build 1029 coconut backlight button always ON even if the screen is off, and can't find options to add quickpanel toggle, only enable - disabled there.
Ryo Kun(Momo) said:
On build 1029 coconut backlight button always ON even if the screen is off, and can't find options to add quickpanel toggle, only enable - disabled there.
Click to expand...
Click to collapse
About backlight button, setting>advance. I'm on 1028 build and the setting>advance let me turn off the backlight button.