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.
Related
Wow, this happened sooner than we expected - but Google just announced only minutes ago that the source code for Android 4.0.1 Ice Cream Sandwich is on its way to Google's AOSP tree right now. We'll update as we learn more. Here's the original post:
Hi! We just released a bit of code we thought this group might be interested in.
Over at our Android Open-Source Project git servers, the source code
for Android version 4.0 (Ice Cream Sandwich) is now available.
Here's how to get it:Follow the instructions at
http://source.android.com/source/downloading.htmlCheck out the
'ics-release' branch:repo init -u
https://android.googlesource.com/platform/manifest -b android-4.0.1_r1
That's it! However since this is a large push, please be aware that it
will take some time to complete. If you sync before it's done, you'll
get an incomplete copy that you won't be able to use, so please wait
for us to give the all-clear before you sync.
This is actually the source code for version 4.0.1 of Android, which
is the specific version that will ship on the Galaxy Nexus, the first
Android 4.0 device. In the source tree, you will find a device build
target named "full_maguro" that you can use to build a system image
for Galaxy Nexus. Build configurations for other devices will come
later.
Unfortunately we still don't have our Gerrit code review servers back
online. That remains our top priority though, and we hope to have them
back soon.
This release includes the full history of the Android source code
tree, which naturally includes all the source code for the Honeycomb
releases. However, since Honeycomb was a little incomplete, we want
everyone to focus on Ice Cream Sandwich. So, we haven't created any
tags that correspond to the Honeycomb releases (even though the
changes are present in the history.)
JBQ, on behalf of the AOSP team.
--
Jean-Baptiste M. "JBQ" Queru
Software Engineer, Android Open-Source Project, Google.
Click to expand...
Click to collapse
SOURCE
http://www.youtube.com/watch?v=QQ_fiepb2Mc
Excellent...muah-hah-ha!
So excited. I've only recently scratched the surface of rooting/flashing on my HP Touchpad, but I know enough to be damn glad that cyanogen will soon be working at a build for ICS on the TP. /anxiously awaiting the awesomeness.
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
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
I don't know about AOKP & AOSP?
Plz, Someone ,tell me.
Sent from my ST25a using xda premium
You could have Wiki'ed them anyways
AOKP (Android Open Kang Project) is an aftermarket custom ROM for many Android devices. A solid AOSP base with a multitude of features has made this ROM grow rapidly in popularity since it was first released in November 2011.
The Android Open Source Project (AOSP), led by Google, is tasked with the maintenance and further development of Android. If you find a custom ROM that is based on AOSP, that means it will be closer to the original, vanilla Android created by Google rather than the bloated software created by Samsung, HTC, LG, and Motorola.
Basically they both a ROM's
For more info Google Them
Thank If Helped
Paranoid Android Change Logs & Full Feature Catalog
PLEASE DO NOT POST FEATURE REQUESTS!
Note:
This post is meant to reflect the core changes made to the AOSPA source code.
These changes should be present in any device-build that is created using PA as the base.
Device specific tweaks (additions and/or removals) implemented on legacy builds or any non-official builds will NOT be listed here, these should instead be noted by the device maintainer/developer in the appropriate device thread.
In an effort to keep this concise, minor bug fixes and optimizations will be omitted. Those can be viewed on Github and/or Gerrit.
Major user-facing bug fixes would however be noted.
Download: get.aospa.co
Aospa 5.0 alpha1 <2015-02-02>
*The #WeAreBackBaby Edition*
It’s been a long time, but we’re finally back and ready to start tasting some lollipops. To start our lollipop journey, we added some goodies to improve AOSP’s state along with some tiny and useful features for a sweet daily use. Lollipop has changed almost everything, and we must think with a different mindset in order to create new features that can provide meaningful improvements over stock while following material design. We’re on it, so don’t worry. Our sauce will have new spices soon enough.
Precautions
First and foremost, if you are flashing from kitkat, stock, or any other ROM we highly recommend a factory reset first. Not doing so may cause strange issues, so if you don't you're on your own.
Second, Galaxy Nexus is not supported anymore on official branch from lollipop. If we manage we'll bring it up within legacy sauce but is not mantained by us anymore like it was before.
For OnePlus and Oppo users, you must flash the latest CM nightly before flashing this release. The CM nightly contains firmware updates necessary to avoid bootloops and broken sensors.
Also Oppo users, The device trees are now split into two variants: Find7s (QHD-2K) and Find7 (FHD-1080p).
Some 3rd party kernels have not yet been updated to include Theme Engine support. If Theme Engine breaks after switching kernels, simply re-flash the build and Google apps to revert to stock kernel.
Other than that, these builds are fairly stable and ready to be used in public, but this is still an alpha build. Hope for awesome buttery smoothness, be ready for a bumpy ride.
In this new iteration of Paranoid Android, super user access (rooting) will be left up to the user.
Changes
Update the baseline to AOSP Lollipop 5.0.2
Improvements to Heads Up, such as an option to disable heads up interruptions completely
Add Quick Unlock
Extend the power menu
Animate the volume panel in a more material manner
Make it possible to skip songs using volume buttons when the device is locked
Add CM12 Theme Engine
Fix various small annoyances from AOSP
Click to expand...
Click to collapse
#StayParanoid on http://get.aospa.co/
5.0 alpha 2
We are rolling out PA 5.0 Alpha 2 builds to the public right now, but first off, a big warning. As of right now, addon.d backup functions are not included in the build. This means you are required to manually flash GApps, SuperSU and all your other extras after flashing the Alpha 2 ZIP. Seriously, you have been warned - do not reboot without re-flashing the GApps package you use. (Unless you have backups.)
A large and fairly important part of the changes consists of Theme Engine improvements, but we are not skipping out on in-house changes. These builds feature the re-introduction of App Ops. Initially made available back in Android 4.3 as a hidden away feature that was later removed and left fairly untouched in AOSP, it has been revived for Android 5.0 and should make your permission restrictioning much easier to do. You can now also reorder your Quick Settings tiles. The layout for them is still the same - two expanded tiles at the top row and a slew of smaller tiles below that, but dragging tiles around allows you to pick their ordering manually instead of being restricted to the AOSP way.
Experiment with tile ordering and protect yourself against all the applications wanting to access all the things.
Changes
Quick Settings are now reorder-friendly
App Ops re-introduced in the Settings app
CM TE updates included
Click to expand...
Click to collapse
#StayParanoid and, as always, get your builds at http://get.aospa.co