Slatedroid info

Sony has built a reputation as developer-friendly device manufacturer, and in aiming to show their continued support for the extensive Android developer community, the company has decided to create an Android Open Source Project (AOSP) for its 2013 flagship device, the Sony Xperia Z. The Sony Xperia S was the first device from the company to be a part of the AOSP “experiment,” and even though that support was pulled a short while later, the project continued. Now, Sony is hoping to get developers excited about using and contributing to a similar project for the Xperia Z.

Like with the Xperia S, developers can go to Sony’s GitHub page to access the source code related to the Xperia Z. Granted, it’s not entirely open, since some of the binaries are proprietary files provided by Qualcomm to use with the Snapdragon S4 Pro processor powering the device. You can download these software binaries here, after agreeing to an EULA that state how the files can be used, and what limitations exist.

The software can’t be used as your daily driver just yet, but there is a lot that is working already, including boot up, SD card, Wi-Fi, Bluetooth, GPS, LED Light, and some sensors. Currently not working are the camera and modem, although Sony has both running internally, but is unwilling to publish the proprietary binaries required. This, of course, means that when the AOSP release is installed, the device will not function as a smartphone and as stated before, is not yet ready for everyday use.

Check out the video below of the Android Open Source Project for the Sony Xperia Z -

Next up for the project is replace some of the binaries with source code, and also make available binaries to get NFC to work. If you’re interested in contributing, you can head on over to the project page here.

Are you excited about AOSP being available for the Sony Xperia Z? Share your thoughts in the comments section below.

Sony announced today that they have opened the software code for their Sony Xperia Z smartphone to the Android Open Source Project. The software has been uploaded to Sony’s GitHub. Between that and information available at Sony’s Developer World site, external developers should have everything they need to get started. The project will be overseen by the same people who were over the Sony Xperia S AOSP. Sony points out that the software is not intended for everyday use and several apps and services one might expect on a standard smartphone are not present. Hit the break for a short video about the project and some shots of what is included in the code.

Click here to view the embedded video.

source: Sony Mobile

Come comment on this article: Sony Xperia Z released to AOSP

The Android Open Source Project (AOSP) is Google giving the entire community (manufacturers, enthusiasts, developers, etc.)  the necessary building blocks to bring what many refer to as “stock Android” (more accurately “vanilla Android”) to a device. The inherent problem with this is that the manufacturers are often the roadblock to such endeavors. Too often manufacturers (like HTC, Samsung, etc.) and suppliers (like Qualcomm) all claim that they can’t release certain drivers, and label them as “proprietary” so that no one can use them. Of course, since there’s nothing really “new” under the sun, this just serves to hinder innovation and development. And often times manufacturers will claim it’s the suppliers who are really hindering things, but who is it that chooses the suppliers? I’ll let the obvious rhetorical question be obvious.

In this mix, it’s refreshing to see a mainstream company attempt to shuck all of these trends and actually release the AOSP source for a device, with the Xperia S being the first non-Nexus device to be included in the AOSP device tree. This experiment ended on a positive note, with Sony moving the source for the Xperia S into their own managed GitHub repository. But Sony hasn’t stopped there.

While companies like Samsung, which used to be rather developer-friendly, now moving away from being open to the community, Sony instead is welcoming them with open arms. Their latest flagship device, the Xperia Z, has joined the Xperia S with having its AOSP source files available on their GitHub. They even posted a lot of information over on their Developer World blog, listing SD Card, WiFi, Bluetooth, GPS, LED light, and sensors working (partially), and they state plans to include NFC in the future. They also have a link to the proprietary Qualcomm binaries needed in order for this to work. You can see the video below, and visit their blog post for more information.

Sony has launched their latest Android Open Source Project. This one is for the Xperia Z, however a similar project was launched for the Xperia S back in August of 2012. In fact, the reason behind the Xperia Z AOSP project was due to what Sony is calling the “great interest” they saw for the Xperia S. Reasoning aside, this basically means the software from the Xperia Z will be open and available for developers to use.

On the flip side, Sony is also looking and hoping for contributions from those developers. The key key here, while this is open and available, this is not software that you will be running on a daily basis. Basically, that is to say that while the software has quite a bit of function, there are some key pieces missing. For example, Sony has said that while the modem and camera are functioning internally, they both require proprietary software that cannot be published.

Putting that aside, Sony has said they are using this project as a way to further show their commitment to the open Android community as well as as a tool to “facilitate and verify contributions to AOSP on the MSM8064 Qualcomm Snapdragon S4 Pro platform.” If you are a developer and looking to get involved, you will be able to find the code on Sony’s GitHub page using this link.

Otherwise, while we already mentioned the issues surrounding the modem and the camera, Sony has said that they have “a lot of things working.” Sony further clarifies that statement by mentioning the handset is able to boot up with the SD card, Bluetooth, Wi-Fi, GPS and LED light working. In addition, the sensors are said to be partially working. Bottom line here, Sony has put this out there, now it is time for some developers to actually make things happen.

[via Sony]

Jean-Baptiste M. “JBQ” Queru has announced that Android 4.2.2 Jelly Bean has been officially released into the Android Open Source Project along with the matching proprietary binaries. The release of the source code started soon after Google released the 4.2.2 firmware images for its Nexus devices, however Queru’s announcement confirms that the push to the AOSP has been completed.

Along with the source code, which is tagged as build JDQ39, the binary drivers have also been released for the different chip sets (like the Wifi and NFC chips) used in the Nexus devices. Through the Android Open Source Project Google releases the source code for Android, however some chip sets need proprietary binaries. This means that the chip maker doesn’t release the source code but has released a driver, akin to the drivers installed on a PC for a graphics card or a network card.

This is the first time that all the Android 4.2 compatible Nexus devices have all the matching binaries available in AOSP. This is particularly great for Nexus 4 owners since 4.2.2 marks the first release of the binaries for that device. It is also the first time that the drivers have been released for the 3G version of the Nexus 7.

The post Android 4.2.2 Jelly Bean pushed to AOSP along with matching proprietary binaries appeared first on Android Authority.

Great news for Nexus users, AOSP is pushing Android Jelly Bean 4.2.2 binaries for several devices in the Nexus product lineup.  The build, JDQ39 (tag: android-4.2.2_r1), is the same as the one currently being rolled out to Nexus devices.

As listed on the Google Developers site, binaries are available for the following devices:

• Nexus 4
• Nexus 7 (both WiFi and 3G versions)
• Nexus 10
• GSM Galaxy Nexus (both takju and yakju versions)

Google continues to show its unwavering support to Nexus followers, and there’s no question that purchasing Nexus devices is the smart way to go for any Android fan.

If you need the latest files, hit the source link for downloads and instructions.

Source:  Google Developers

Come comment on this article: Roll Your Own Android: Android 4.2.2 Code and Binaries pushing to Android Open Source Project (AOSP)

Google began pushing the Android 4.2.2 code to the Android Open Source Project (AOSP) a short while back, however as of today it looks like that roll-out has been completed. Simply put, this means you will be able to grab builds for all the current generation Nexus devices. What we are looking at is Android 4.2.2 with build number JDQ39.

Specifically this includes the Nexus 10 and Nexus 7 tablets as well as the Nexus 4, Galaxy Nexus (GSM/HSPA+) and Galaxy Nexus (Verizon Wireless) smartphone. Still missing however are some of the older devices including the Nexus S and Nexus S 4G smartphones along with the Motorola Xoom tablet.

The details of this update were posted by Jean-Baptiste Queru and interestingly enough, this marks the “first time that any device has all its binaries available for AOSP.” This is in regards to this AOSP release including the full set of proprietary binaries for all variants of the Nexus 7 as well as the Nexus 4.

Otherwise, many of the older binaries remain available. Also worth noting, Queru has said that they also tweaked the Froyo, Gingerbread and ICS-mr1 branches so they can now be compiled on Ubuntu 12.04. Bottom line here, if you have been looking for any Nexus related binaries – follow the link at the bottom of this post.

[via Google Developers]

Google has released the Android 4.2.2 “JDQ39″ binaries and will now begin pushing the code to the Android Open Source Project. These files, available for the full range of Nexus devices, will greatly benefit anyone looking to make their own ROM’s and or anyone hoping to see new ROM’s completed for any number of devices should [...]



Click the post title to continue through and join the conversation!

Android version 4.2.2 of Jelly Bean has arrived on the Nexus line up’s door step. That can mean only one thing: It is time to cue the onslaught of mainstream technology journalist statements about the “fragmentation” of Android. They proclaim this fragmentation hurts Android, that non standardized hardware and different OEM customized versions of Android will be the downfall of Google’s mobile operating system. These people have perhaps drank a bit too much iKool-Aid.

The different options of Android handsets are what make Android a success. If I want a 5.5 inch phone screen, there is the Samsung Galaxy Note II. If I want a water and dust proof phone, there is the Sony Xperia Z. If I want a phone that I cannot unlock and has some of the most difficult bootloaders to crack, there is almost every Motorola and HTC device. In this episode XDA Developer Producer azrienoch gives us the 5 myths of the custom OEM Android software ecosystem.

Be sure to check out other great XDA Developer TV Videos.

• Sony Car Launcher and the SIM Unlocking Petition Needs Your Help! – XDA Developer TV
• Android 4.2.2 Rolling Out to Nexus Devices, Sony Xperia Z Kernel Source Released – XDA Developer TV
• App Review: Gesture Control Showdown! LMT vs. Trigger – XDA Developer TV
• Paranoid Android 3 out for Nexus Devices, Open Source Privacy Mod for Android – XDA Developer TV
• HTC Thunderbolt Gets ICS OTA Update, XDA Changelog Now Available – XDA Developer TV

The latest version of Android, Android 4.2.2 Jelly Bean, is now being pushed to AOSP. It was only earlier today that the Android 4.2.2 update began rolling out to select Nexus devices. If you have a takju Galaxy Nexus, Nexus 7 (Wi-Fi), or a Nexus 10, you should be able to update to Android 4.2.2 if you haven’t already. The update should be available through your settings page, but if not, just sit tight.

In AOSP, the build number for Android 4.2.2 is JDQ39 and its tag is android-4.2.2_r1. The Android 4.2.2 push is still fresh, so throughout the day, the source directories will continue to be updated. Here is a list of current directories that have been updated:

/device/common/+/android-4.2.2_r1
/platform/dalvik/+/android-4.2.2_r1
/platform/build/+/android-4.2.2_r1

This is great news in terms of roms. We should be seeing Android 4.2.2 pop up from a variety of developers like CyanogenMod and AOKP soon. This isn’t as ground breaking as when Android 4.2 was pushed out to AOSP, but it’s still pretty great. Android 4.2.2 is just a minor update that offers improved performance and stability, but who’s complaining?

The Android Building Google Group should have a post by Jean-Baptiste Queru, the chief Android release engineer, as soon as the push is completed. There will also be a full developer changelog available. We will have additional details as soon as they surface, but in the meantime, you can check out our timeline below to keep up to speed with the Android 4.2.2 update.

[via Android Police]