topic Re: Xperia S AOSP update. in Other/General

Xperia S AOSP update.

sharique007 — Wed, 31 Oct 2012 15:07:24 GMT

Hello,

Actually I want to know that is the xperia S AOSP project still on because haven't heard any news about it and yesterday google announced the NEXUS and i am tempted by its price tag so should i swap it or wait? I am getting impatient so somebody please let me know if this project is still on?

Re: Xperia S AOSP update.

Uliwooly — Wed, 31 Oct 2012 20:49:30 GMT

you should get the Nexus 4, the camera it's amazing and the phone it's quite cheap

as for AOSP, Sony won't be working on it

Re: Xperia S AOSP update.

dime — Wed, 31 Oct 2012 23:03:14 GMT

You uliwooly are talking like you know something or ?

Also we already bought this phone ,wait for the end of software updates we will see how sony will look on this device and if sony fails my next phone won't be sony for sure i think that many others thinks like me...

Re: Xperia S AOSP update.

Uliwooly — Wed, 31 Oct 2012 23:06:27 GMT

https://groups.google.com/forum/#!topic/android-building/zji_sQGN9Oo

I'm going to try an experiment.

Over time, AOSP has added files related to various hardware targets.

We started with just a few scripts on a web page (1.0), then we had a

git project (Cupcake), then we released some of the exact source files

that were used on retail flagship devices (Froyo), then distributed

proprietary binaries (Gingerbread), then we were able to run on

PandaBoard (Ice Cream Sandwich).

For a new challenge, I'd like to try to go one step further, and to

target some hardware beyond the usual categories. I've added a git

project for the Sony LT26, i.e. Xperia S. This seems like a good

target: it's a powerful current GSM device, with an unlockable

bootloader, from a manufacturer that has always been very friendly to

AOSP.

That git project is currently empty. I'm open to suggestions about the

best way to populate it. I think I'll start by putting together a

skeleton set of makefiles, followed by a kernel. Contributions are

strongly encouraged, and there should be more freedom than usual to

submit experimental changes since that won't impact the devices that

Google is most directly involved in.

I don't know how far that'll go, and there are so many unknowns that

the only way to know is to try it.

As usual, please be very careful about handling any proprietary files,

for Xperia S or any other device. Don't copy them, use them, or

distribute them without an appropriate license. Obviously, don't

upload them to AOSP if you don't own them. When in doubt, please ask

ahead of time, it's easier to answer an email than to fix things in an

emergency.

JBQ

Jean-Baptiste M. "JBQ" Queru

Technical Lead, Android Open Source Project, Google.

Questions sent directly to me that have no reason for being private

will likely get ignored or forwarded to a public forum with no further

warning.

Re: Xperia S AOSP update.

Uliwooly — Wed, 31 Oct 2012 23:12:46 GMT

http://developer.sonymobile.com/2012/09/03/sony-release-binaries-to-support-jbqs-vanilla-android-xperia-s-project-download/

https://android.googlesource.com/device/sony/lt26/+/master

From Sony side, we welcome the project and support it with resources and contributions.