http://www.androidauthority.com/android-5-0-lollipop-source-code-563560/
Well what do we have here, Android Lollipop being uploaded to AOSP as we speak! As you can imagine, a code dump like this takes a great deal of time, and it could be hours before everything is completed. At the moment, the branch is being referred to as “lollipop-release” and it carries a build number of LRX21M, though its official release tag should be android-5.0_r1 when it ‘fully hits’.
Even more exciting, it’s also only a matter of time before device-specific repositories for all Nexus hardware shows up, and at least a few have already surfaced including the Nexus 7 (2013) LTE ‘deb’ and Nexus 7 (2013) Wifi ‘flo’. It is worth noting that a new repository for Android TV is also available now, though it is hard to say whether or not the full code will be uploaded.
Once everything is uploaded, it’ll only be a matter of time before developers and many others begin playing around, bringing us hidden goodies and so much more. And before you ask, no the Nexus factory images are not up yet. Patience my friends, all in good time.
Click to expand...
Click to collapse
Its been published.
Sent from my Xperia L using XDA Free mobile app
The last time i checked, Lollipop source was still pushed but still it hadn't had key files to compile it for any device like manifest etc. It was giving an error. These files usually take few hours.
And the source code being published is for Nexus 7 , 5, 6 and 9.
There still wasn't anything for Nexus 4 or 10 or any other device.
However few sites cited that the manufacturers were handed the source to Lollipop and they were working on it as well.
I'm not sure how much time it would take to make their sources public.
As for Xperia L, I can't say when exactly but I'd say roughly about one to two months before any development is to be seen. The nexus 7 and 5 still haven't got OTA or Nexus Factory Images yet as I'm watching it closely.
Sony is surely not releasing lollipop for L so we would just have to wait for Aosp and Cyanogen to combine few lollipop sources to current device tree to give you somewhat of Android L which our device is capable of.
I hope this information be enough for now
Update
Source code is now complete. You can compile it for the above mentioned nexus devices. Still No official OTA or nexus factory images.
Little update :
Nexus Media Player and Nexus 9 Factory Images have been pushed. Still nothing for Nexus 7 or 5. Neither for Nexus 6.
Although source code have been pushed but I don't see any binaries yet for any Nexus devices which means that custom ROMs are still not possible. Although if you try to compile a custom ROM, you'd have glitches/problems due to missing binaries.
What this means is that unless Qualcomm doesn't release binaries for it's Snapdragon processors, we won't be able to get a ROM fully stable.
We can get some features to be merged in our device tree but I am not sure how lollipop would work perfectly without binaries/blobs.
Last time, I remember the graphics glitch was sorted partially by using Xperia Z blobs but still it didn't was as affective as it could be if it was for Xperia L itself.
What Xperia L need is binaries from Qualcomm and source code from Sony for Lollipop.
Let's hope for the best
Update 2
It is now rumored that update for the remainder of Nexus devices would come on 12th Nov as Google found some last minute bugs and wants to send of more polished and refined bug free android L.
For Xperia L, you can only wait for binaries from Qualcomm and source code from Sony.
source code published
source code published
Related
ORIGINAL: techradar.com/
Here's what we know about Android 5.0 so far
Google's showing no signs of slowing its pace of Android development, with Android 4.0 appearing on the Galaxy Nexus late in 2011, followed in July of 2012 by the Android 4.1 Jelly Bean release that arrived powering the super Nexus 7.
But, forward-looking, update-obsessed people that we are, we can't help but imagine how Google's going to maintain the pace of innovation in its next version of its mobile OS, Android 5.0.
All we know so far is that Google's working away on the K release of Android, which it's developing under the dessert-related codename of Key Lime Pie. Regarding the version number, it's likely that the Key Lime Pie moniker will be given to Android 5.0. We thought we might find out on 29 October 2012 but as yet there is no official word from Google.
Android 5.0 release date
Google has announced that its next developer conference - Google IO - will take place from May 15 to May 17 2013, a month earlier than 2012's June dates. Given that Google announced Android 4.1 Jelly Bean at 2012's IO conference, it's not unreasonable to expect to see Android 5.0 at this year's event.
On 31 January, a Google IO showing of Android 5.0 looked more likely when screengrabs of a Qualcomm roadmap were leaked, showing Android 5.0 as breaking cover between April and June 2013.
On 24 April 2013, we read that Key Lime Pie may not make its debut at Google IO after all. Apparently, "trusty internal sources" told a site called Gadgetronica (a site we hadn't previously heard of) that Google has decided to delay Android 5.0 for two to four months to give hardware makers the chance to properly roll out Android 4.2 Jelly Bean.
We'd take this rumour with a pinch of salt and add another pinch of salt for good measure, as even if Google decides not to ship the finished build of Android 5.0 until later in the year, that doesn't preclude the company from talking up the new OS at what is, after all, a developer-focused conference.
However, the notion of Key Lime Pie being off the menu at Google IO raised itself again on 26 April when Android 4.3 surfaced in server logs over at Android Police. Those log entries supposedly came from Nexus 4 and Nexus 7 devices running an updated version of Jelly Bean - Android 4.3 - and apparently the IP addresses of those devices trace back to Google HQ. So might that point to a delayed Android 5.0 arrival?
Android 5.0 phones
Rumours of a new Nexus handset started trickling in during the third quarter of 2012, as we reported on 1 October 2012. There was speculation that this phone would be sporting Key Lime Pie, but sources who spoke to AndroidAndMe correctly claimed that the handset, which turned out to be the Google Nexus 4 would be running Android Jelly Bean.
While the Nexus 4 didn't appear with a helping of Key Lime Pie, speculation that we reported on 21 January 2013 suggests that the Motorola X Phone is the Android 5.0-toting handset that will be revealed at Google IO. According to a post on the DroidForums website, the phone will also feature a virtually bezel-free, edge-to-edge, 5-inch display.
So now as we wait on official news of the Android 5.0 release date and features, we can start to pull together the Key Lime Pie rumours from around the web, with the first sighting of Android 5.0 on a benchmarking website, apparently running on a Sony smartphone. There has previously been speculation that Sony is in line to produce the next Nexus phone, which may lend some credence to this rumour.
The same leaked Qualcomm documents cited above also made mention of a two new Snapdragon devices, one of which will be, unsurprisingly, a new Nexus phone.
That Nexus phone is most likely the Google Nexus 5, though we'd be surprised to see it break cover at Google IO, given that the Nexus 4 only went on sale at the end of 2012.
On Monday 18 March, supposed images of the Nexus 5 surfaced, with the handset apparently being manufactured by LG. If the accompanying specs, leaked along with the photo by the anonymous source, are true, then the Nexus 5 will feature a 5.2-inch, 1920 x 1080 OLED display, 2.3GHz Qualcomm Snapdragon 800 processor and 3GB of RAM.
While a sighting of the Nexus 5 at Google IO is unlikely, rumours that we wrote up on 19 April reckon that there will be an Android 5.0-powered Nexus 4 launched at the event. Apparently, the revised handset will also feature 4G capability and improved storage of 32GB.
Android 5.0 tablets
The original Nexus 7 tablet was unveiled at Google IO 2012, so it's possible that we'll see a refreshed Nexus 7 2 at Google IO 2013. The speculation is that Google will team up with Asus for this, as it did with the original Nexus 7. We expect an upgraded display on the new Nexus 7 tablet, while Digitimes is reporting that the 2nd generation Nexus 7 will have 3G service and and range in price from $149 to $199.
Samsung's Android 5.0 upgrades
Although Samsung is yet to officially confirm its Android 5.0 schedule, a SamMobile source is claiming to know which phones and tablets will be getting the Key Lime Pie upgrade. According to the source, the devices set to receive the upgrade are the Galaxy S4, Galaxy S3, Galaxy Note 2, Galaxy Note 8.0 and Galaxy Note 10.1.
Android 5.0 features
For 24 hours, it seemed as though the first kinda, sorta confirmed feature for Android 5.0 was a Google Now widget, which briefly appeared in a screenshot on the company's support forum before being taken down. As it was so hurriedly pulled, many people assumed it was slated for the big five-o and accidentally revealed early.
As it happened, the following day, on 13 February 2013, the Google Now widget rolled out to Jelly Bean.
On 28 February 2013, we learned from Android Central that Google is working with the Linux 3.8 kernel, which gives rise to the notion that this kernel might make it into Android 5. One improvement that the 3.8 kernel brings is lowered RAM usage, which would mean a snappier phone with better multitasking.
Android Geeks has reported that Google Babble will debut on Key Lime Pie. Babble is, apparently, Google's in-development cross-platform service and app with the aim of unifying its various chat services which include Talk, Hangout, Voice, Messenger, Chat for Google Drive and Chat on Google+.
Android Geeks' source also said that Google Babble will be supported by devices running Android 2.3 and above, which would make sense given that Google will want as many people as possible on the platform.
A screenshot that we were sent from a Google employee on 8 April confirms that not only is this unified chat service on the way, but that it is now called Google Babel not Babble. Babel will come with a bunch of new emoticons and Google+ built-in so you can jump from Babel chat to hangout. A leaked Google memo on 10 April provided a few more juicy details including talk of a new UI and synced conversations between mobile and desktop.
Following an 18 April tear-down of the Google Glass app MyGlass by Android Police, it now looks as though there may be an iOS Games Center-like service coming to Android 5.0.
Android Police found references in the code to functionality that doesn't exist in Glass, which suggests that developers accidentally shipped the full suite of Google Play Services with the Android application package.
The files in the package contained references to real-time and turn-based multiplayer, in-game chat, achievements, leaderboards, invitations and game lobbies.
So it seems that Google Games (or whatever it ends up being called) is real, and we may find out more about it - and whether it will ship with Key Lime Pie - during the Google I/O conference. As Android Police points out "It being including in a shipping product suggests that it's finished and freely floating around Google HQ."
Android 5.0 interface
While this is pure speculation, we're wondering whether Android 5.0 might bring with it a brighter interface, moving away from the Holo Dark theme that came with Android 4.0.
Google Now brought with it a clearer look with cleaner fonts, and screenshots of Google Play 4.0 show Google's app market taking on similar design cues. Is this a hint at a brighter, airier look for Key Lime Pie?
[...]
is this real? do you have a homescreen screenshoot?
Sent from my Xperia Tipo using xda app-developers app
xrhstospro said:
is this real? do you have a homescreen screenshoot?
Sent from my Xperia Tipo using xda app-developers app
Click to expand...
Click to collapse
What are you talking about this is a thread that was made to highlight known info about Key Lime Pie....
It's seems like that it will be very nice update. So I'm waiting for it.:fingers-crossed:
Here's a screenshot of a key lime pie theme
Sent from my One X using xda app-developers app
I've hear about the Nexus 5... No official release date but it supposedly to be later in 2013.... Nexus 5, Android 5!?!? Maybe Key Lime Pie will be released the same date of the Nexus5!
Sent from my Optimus G (RootBox 4.2.2) using xda app-developers app
Hi,
I'm planning to buy Xperia Z3. I really like this phone but I've read here that camera on AOSP ROMs has this fisheye bug because Sony hasn't released sources for the camera yet.
Is there any hope that Sony will release them? And can this problem be fixed someday without relying on Sony?
Also does Z2 have this problem? If not, is it because Sony released sources for the Z2 or somebody just figured out how to solve it?
Z3 and Z2 have the same camera (almost) so if this problem is fixed for one it should be fixed for the other, right?
No one?
No one has released source code for mm-camera and no OEM ever will, because it's Qualcomm proprietary.
Unfortunately, Sony's newer blobs have had issues in the past. The end result is that the entire rhine/shinano family (Z1, Z2, Z3) are all using 4.3 rhine camera blobs. The distortion profile of the Z1 blobs is wrong for the Z3.
There are two potential solutions:
1) Some progress was made on getting newer stock blobs to work, but this was put on hold because
2) The Sony AOSP internal team are working on creating a set of blobs that can be used with AOSP proper. Although I'll personally be resuming work on item 1 in the next week or two if the Sony guys don't have any concrete news by then, as I need a working camera for Photospheres in early September
Entropy512 said:
No one has released source code for mm-camera and no OEM ever will, because it's Qualcomm proprietary.
Unfortunately, Sony's newer blobs have had issues in the past. The end result is that the entire rhine/shinano family (Z1, Z2, Z3) are all using 4.3 rhine camera blobs. The distortion profile of the Z1 blobs is wrong for the Z3.
There are two potential solutions:
1) Some progress was made on getting newer stock blobs to work, but this was put on hold because
2) The Sony AOSP internal team are working on creating a set of blobs that can be used with AOSP proper. Although I'll personally be resuming work on item 1 in the next week or two if the Sony guys don't have any concrete news by then, as I need a working camera for Photospheres in early September
Click to expand...
Click to collapse
Thanks a lot. That was very informative.
Does this mean that if it gets fixed before Sony releases the new blobs, it will be fixed for the entire Z family?
Today I just discovered Samsung's opensource release center.
I am not a good developer so I'm just trying to seek attention of other Awesome and respected developers.
With the source let's get out note's features on other roms.
Examples :-
Samsung Camera app for AOSP
Samsung's S-Pen features for AOSP
S health for AOSP
I haven't downloaded the whole source code due to lack of high speed internet.
May they just included basic framework and drivers and libraries in their source, but i think xda has grown up enough to redesign drivers and frameworks and etc stuff that is required to run sammy apps on other roms.
here is the link for SM-N9005 :- SM-N9005(Qualcomm) csc variants.
here is the link for SM-N900R4(US Cellular N3) :- US Cellular Note 3
for other variants just visit opensource.samsung.com and search your device model.
If any mistake I'm sorry.
Nice thought, but that's just the kernel source. Modern versions of Touchwiz and Samsung's proprietary apps are not open source.
Check out other sections on that website... i saw that they have released whole source code for galaxy camera.. may be they have released one for our note too...
harshal10398 said:
Check out other sections on that website... i saw that they have released whole source code for galaxy camera.. may be they have released one for our note too...
Click to expand...
Click to collapse
I've looked through Samsung's Open Source Release Center quite a bit. If they made any recent version of Touchwiz fully open source, it would be huge news. Unfortunately, I don't believe that will happen any time soon.
Here we go again 7.1 is out for 5 x and up. Anyone working on this is it possible? Or hard like it was with 7.0 beta?
Seems like it's more smooth, i think they are increased the touch sensibility.
I hope you realize that developers need source code to port the OS to a new device... There is only one developer preview for 7.1. I'm sure that as soon as source is released, people will work on it, just like they did with android 7.0... Official release is expected in December, so we'll have to wait...
Will there be any Android O custom rom for Nexus 5 because some people said that Android O might not support 32bit device. I actually consider to buy Nexus 5 since it cheaper than 5X. If Android O only support 64bit device I might get Nexus 5X.
ares_NBP said:
Will there be any Android O custom rom for Nexus 5 because some people said that Android O might not support 32bit device. I actually consider to buy Nexus 5 since it cheaper than 5X. If Android O only support 64bit device I might get Nexus 5X.
Click to expand...
Click to collapse
The source code of android 0 is not released yet so we do not yet know if there will be rom custom android O
ares_NBP said:
Will there be any Android O custom rom for Nexus 5 because some people said that Android O might not support 32bit device. I actually consider to buy Nexus 5 since it cheaper than 5X. If Android O only support 64bit device I might get Nexus 5X.
Click to expand...
Click to collapse
I think it's better to save some more and get the Nexus 5X because Nexus 5 it's starting to become a legacy device
Why do people always jump on these developer previews and request them being ported to other devices? We're currently at the very first dev preview, this is not even a beta, and just about nothing is finalized right now.
We're going to see whether the Nexus 5 could be supported by third-party-ROMs when the source code for O drops. Until then, there's not really a point discussing it.
If you're looking for a cheap phone, I would consider getting a newer budget phone, like the Moto G5 /G5 Plus, or one of those cheaper Sony ones. You'll get better battery life, a much better camera and maybe even Android N/O, depending on the OEMs' willingness to update. Or just go with one of the Android One devices, if they're available in your market.
Unless you already own one, I don't see any benefit in getting a four-year-old phone.
If Google is testing Android Or for nexus 6, on got its code might be available. CNA we use it to port it to nexus 5??
GopalKaul said:
If Google is testing Android Or for nexus 6, on got its code might be available. CNA we use it to port it to nexus 5??
Click to expand...
Click to collapse
We cannot. The hardware specs are completely different.
GopalKaul said:
If Google is testing Android Or for nexus 6, on got its code might be available. CNA we use it to port it to nexus 5??
Click to expand...
Click to collapse
If they would publish an official build for the n6 and with it sources, but since it is internal testing they most likely wont.
I've heard the update schedule for the Moto Z Play is promising Android O updates later down the line and the device has a 32-bit processor. Of course I believe that there's clever devs on here that could make something special happen
Nyoir said:
I've heard the update schedule for the Moto Z Play is promising Android O updates later down the line and the device has a 32-bit processor. Of course I believe that there's clever devs on here that could make something special happen
Click to expand...
Click to collapse
The Snapdragon 625 is not a 64-bit CPU. The phone itself does run a 32-bit ROM, however.
Now can it be built?