• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.
Sign in to follow this  
Followers 0

An experiment: Sony Xperia S and AOSP

2 posts in this topic

Posted

Do you own a Sony Xperia S, are you interested in getting AOSP running on it natively? Jean-Baptiste Queru has added an experimental tree for the Xperia S in the Android Open Source Project and is looking for your help in populating it.

I cant explain this better than JBQ can, so to quote:

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

The original thread is here in the 'Android Building' Google Group.

I will be following this with great interest as the Xperia S is a very powerful device (as confirmed by Paul when he reviewed it back in April).

[Via: Android Building]

9fbd4be66f946d8018d3aa6ad341dd5d.png

Click here to view the item

0

Share this post


Link to post
Share on other sites

Posted

I am now seeking a used one of these :-)

0

Share this post


Link to post
Share on other sites
Sign in to follow this  
Followers 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.