Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
https://developer.sony.com/develop/open-devices/
Unified 4.4 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Bug tracker
https://github.com/sonyxperiadev/bug_tracker/issues
Now you can build the latest Android with the latest 4.4 kernel
Vendor v11 is out
https://developer.sony.com/develop/open-devices/latest-updates
For user security dm-verity and File Based Encryption are enabled by default
Please keep them enabled for all user builds
Regards
J
I wish someone is working on android 9 for the xzs
Hello! Is there anybody out there?? I installed Ubuntu and followed the guide but every time it fails with some Ninja error!!
I know one of you @jerpelea can make it.
Desperately waiting for it.
All build guides are updated with the Security updates
https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/
Here is the list of all known bugs. If you find bugs you can always open a ticket in the bug tracker and we will check it ASAP.
https://github.com/sonyxperiadev/bug_tracker/issues
what's with XZs? why aren't there developers for this cellphone? I am jealous of the ever-expanding XZ and XZ premium
Related
About Carbon
CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look at, build, and use our code on CarbonDev GitHub. and on our Gerrit CarbonDev Gerrit.
We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.
Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.
Features
All of our features can be found on our site here:
Carbon Features
Here are some screenshots:
Carbon Screenshots
Carbon Updates
Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests, and more! Join our completely open Google+ community for insider conversation with devs and other users.
Download Carbon
All Carbon downloads and further information such as features, changelog, and FAQ can be found on our website.
Carbon Downloads
Changelog
For a detailed changelog, check out the changes made each night here:
Carbon Changelog
Support
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Ask a question on our IRC channel. Connect to #teamcarbon on irc.freenode.net or click here. You'll find several other Carbon fans and usually one or more devs as well. Please be polite.
Who is Team Carbon?
Find out here:
Carbon Team
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
[ROM][AOSP][Nightly/Release] CarbonRom KitKat [i9100], ROM for the Samsung Galaxy S II
Contributors
CarbonDev, Myself5
ROM OS Version: 4.4.x KitKat
Based On: AOSP
Version Information
Status: Beta
Created 2014-02-14
Last Updated 2014-06-07
Reserved
Reserved
Hello Guys.
I'm your i9100 device maintainer.
I meanwhile tweaked the Rom specially for the i9100 so its difference to our other devices is:
Compiled using SaberMod arm-eabi 4.7 (Kernel code) and SaberMod arm-linux-androideabi 4.8 (ROM code) toolchain compilers
Cross-compiled using those custom toolchains results in a more smoother, faster, and battery friendly ROM
F.A.Q.:
What is Toolchain?
In software, a toolchain is the set of programming tools that are used to create a product (typically another computer program or system of programs). The tools may be used in a chain, so that the output of each tool becomes the input for the next, but the term is used widely to refer to any set of linked development tools.
A simple software development toolchain consists of a compiler and linker to transform the source code into an executable program, libraries to provide interfaces to the operating system, and a debugger. A complex product such as a video game needs tools for preparing sound effects, music, textures, 3-dimensional models, and animations, and further tools for combining these resources into the finished product.
Click to expand...
Click to collapse
Source: http://en.wikipedia.org/wiki/Toolchain
What is SaberMod?
The term "SaberMod" is coming from:
SaberMod is a AOSP based ROM with some extra features added in and mostly from CyanogenMod. SaberMod started out pure AOSP when android 4.2.1 launched. Originally it was pure AOSP with a few extra features I ported over from CyanogeMod and linaro optimizations. Then I rebased everything off of rasbeanjelly because I liked many features found in rasbean. Since then I've modified a lot of the code so not much of it is rasbeanjelly based anymore. But you will still find some commonly used features found in rasbeanjelly. SaberMod is not a rasbeanjelly or CM clone, or KANG. Custom kernels are included for certain devices when available. These are personal builds we make for ourselves and originally became very popular in the nexus 7 forums. Features are very rarely added, and are built to SaberMod's team members liking. Currently there are two members of SaberMod working on this project. Myself and @jarjar124. Please understand our time is limited and we are only two people who have lives, and do not have 25-50 members like CyanogenMod to add things. And our goal is not to add a bunch of features that bloat the system of the ROM.
Click to expand...
Click to collapse
Source: http://forum.xda-developers.com/show....php?t=2158698
About GCC main compiler cflags
-O1
Optimize. Optimizing compilation takes somewhat more time, and a lot more memory for a large function. With -O, the compiler tries to reduce code size and execution time, without performing any optimizations that take a great deal of compilation time.
-O2
Optimize even more. GCC performs nearly all supported optimizations that do not involve a space-speed tradeoff. As compared to -O, this option increases both compilation time and the performance of the generated code. -O2 turns on all optimization flags specified by -O.
-O3
Optimize yet more. -O3 turns on all optimizations specified by -O2 and also turns on the -finline-functions, -funswitch-loops, -fpredictive-commoning, -fgcse-after-reload, -ftree-loop-vectorize, -ftree-slp-vectorize, -fvect-cost-model, -ftree-partial-pre and -fipa-cp-clone options.
-Os
Optimize for size. -Os enables all -O2 optimizations that do not typically increase code size. It also performs further optimizations designed to reduce code size.
Click to expand...
Click to collapse
Greetings
Myself5
Nice Work Dude !
Mine
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Whats Up Whith "Mine" ?
great ...thanks ....will try it surly
Great!! carbon finally arrived gonna try
Sent from my GT-I9100 using Tapatalk
im not able to see the download link in carbon page, i select our device but the links to download the ROM doesnt appear, can someone share the download link?
attack11 said:
im not able to see the download link in carbon page, i select our device but the links to download the ROM doesnt appear, can someone share the download link?
Click to expand...
Click to collapse
I have found that this link:
http://carbon-rom.com/downloads/?device=i9100&type=nightly&country=US
Showing some dates but still no luck with working link...
Послато са GT-I9100 уз помоћ Тапатока
Will this rom contain the tweaks/things that Myself5 added to his unofficial build?
It seems like we're currently having some issues with our download page getting accessed by mobile browsers. Please use your computer to download until we fixed it.
@GreekBlood: All in all the most tweaks I made were coommits from gerrit, so sooner or later they will be included
http://carbon-rom.com/downloads/?device=i9100&type=nightly&country=BE
Here i can see the downloads perfectly and they also work.
And here is the latest nightly for our SII :> http://eu1.dl.carbon-rom.com/files/i9100/nightly/CARBON-KK-NIGHTLY-20140215-0148-i9100.zip
congrats myself5 on getting to be the maintainer for this great rom on our s2.
i think i will just dl from the official carbon page,and then just use the updater to get all the improvements and fixes moving forward!!
well first hour whit this rom.and everything seems good after all! just one question,how i can enable wheater widget in the lockscreen? i cant find an option..
also some translations are missing (in spanish) i can help if you want.
also another question Halo will be added on the future?
i flashed newest rom all good.kernel included is not compatible with stweaks.
I plan on flashing gustavo 2\09 kernel.
will nightly updates flash a another kernel each update??
thnx
A little problem
I have a little problem,when i try to install gapps it says that i have insufficient space. How would i fix that? I`m using PA-GOOGLE APPS (FULL MODULAR PACKAGE) .
And another question. Previous versions that were unofficial had TWRP, how could I get that back too?
@attack11 the Weather Widget is called cLock. HALO will be added it just has some small bugs ATM we need to fix. Thanks for your help, I will later PM you all files you need to translate.
@saskrider: It will flash a new Kernel every Update. However when you later (as soon as it's working) use CarbonDelta to update there will be a option to add Custom Zip's to flash after the Rom (like GApps and Custom Kernels)
@Pecka40: the S2's Sytem Partition is to small for these GApps, use some smaller ones
Greetings
Myself5
Sent from my GT-I9100 using Tapatalk
Myself5 said:
@attack11 the Weather Widget is called cLock. HALO will be added it just has some small bugs ATM we need to fix. Thanks for your help, I will later PM you all files you need to translate.
@saskrider: It will flash a new Kernel every Update. However when you later (as soon as it's working) use CarbonDelta to update there will be a option to add Custom Zip's to flash after the Rom (like GApps and Custom Kernels)
@Pecka40: the S2's Sytem Partition is to small for these GApps, use some smaller ones
Greetings
Myself5
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply! And there is no way of making it bigger?
And could you please answer the other question. About how can I get TWRP on it.
Lineage CICD Project
This is my personal effort given to you, the community, which spends a lot of hours to craft a fully-functional and perfectly tuned ROM for our beloved Smartphones!
What is it?
This project aims to provide a Build system for Android Developers which will be able to build an Android ROM for a different set of Codenames given, automatically for you, ( by default ) every night. Not only built stock sources that are already available on LineageOS Github account, but feel free to build even your custom code thanks to the support of local_manifests/*.xml fully supported by this Docker.
Where can I find it
CICD
- Github: https://github.com/julianxhokaxhiu/docker-lineage-cicd
- Docker Hub: https://hub.docker.com/r/julianxhokaxhiu/docker-lineage-cicd/
OTA
- GIthub: https://github.com/julianxhokaxhiu/LineageOTA
- Docker Hub: https://hub.docker.com/r/julianxhokaxhiu/lineageota/
- XDA: https://forum.xda-developers.com/showthread.php?t=2636334
Why?
As you all remember the transition from CyanogenMod to LineageOS was not smooth. Even today we are not granted with Nightly Builds, but with Weekly, because of capacity issues on providing such an amazing plethora of supported Devices ROM ZIPs ready to be flashed.
Therefore this projects aims on providing an easy-to-use build system which may help you on providing a Ready-To-Flash ZIP at the end of each Build round.
How does it work?
This is a pre-packaged Docker system based on Debian, with all the dependencies in place to correctly build ( even in an optimized way ) any LineageOS codename ROM. A cronjob will take care to start the build script on the configured time ( by default 10:00 UTC ~= 02:00 PDT ), which then will take care to build every codename given with an environment variable to the Docker.
All you need from now on is just the Docker Engine installed on your favourite Linux distribution.
Bonus!
Of course the ZIP that will be produced needs to be transferred to the device in order to flash it. Such a boring task...what if we can automate it through OTA?
As you all know, my first big project I've ever started for XDA was the OTA Server which perfectly emulates all the required calls to make it working with ( old and deprecated now ) CyanogenMod ROMS, as well as with ( long life to ) LineageOS, right now, today!
All you need to do is to configure an Environment variable in the Docker to say where your OTA Server is located. The URL will the be added automatically for you inside the build.prop file as cm.updater.uri=$OTA_URL.
...but wait, there is more!
Since the OTA Server is written in PHP, you all know that is a headache to prepare the system to make it working. A lot of user complained in the original Thread that was difficult for them to understand how to setup it correctly, therefore a fully working autonomous Docker is there for you, ready to serve the OTA Layer for you built ROMs!
I want to use it right now!
I am pretty sure you want! The Docker has now been tested for a nearly a Month and I'm successfully installing my own builds for a couple of weeks on my devices ( really a great satisfaction! ).
If you want to run it as well, I suggest you to take a look at this Bash script that will run for you the Dockers, already talking to each other. Since the script has been studied to work on top of the "VPS Powered By Docker" project, I suggest you to take a look at it. Although nothing is preventing you to use it in your favourite way.
Requirements
See the detailed list on the project README.
What about License
All my projects are always developed with MIT license, which means feel free to do what you want with it. I don't really care if you do business with it, it was a great challenge for me reaching this autonomous entity to run, therefore I don't mind of possible outcomes of it. Although Issues are always welcome for improvements, if any found, of suggestion for a possible feature enhancements.
Future plans?
At the moment I have some ideas, which I may, or may not, be able to implement as I am not a professional Android Developer. Although some nice to have points are:
- Possibility to build ANY Android distro ( from AOSP to any fork of it )
- Possibility to have changelogs of every nightly build ( attached as *.txt and *.html format, next to the built ROM )
- Maybe a logo?
Thanks for Awesome Work
Thanks for awesome work.
CopperheadOS
A security and privacy focused mobile operating system compatible with Android apps
Code:
DISCLAIMER: NOT RESPONSIBLE FOR BROKEN PHONES OR LIVES
CopperheadOS - a hardened FOSS operating system based on the Android mobile platform. Its based on Android Open Source Project with added privacy and security features.
Prerequisites :-
Have latest factory image installed
Instructions :-
Download the UNOFFICIAL CopperheadOS ROM
Follow the install guide
Have a more private and secure phone
Features :-
Protection from zero-days
Prevents many vulnerabilities and makes exploits harder
Hardened C standard library and compiler toolchain
Catches memory corruption and integer overflows
Hardened kernel
Kernel self-protection and high quality ASLR
Stronger sandboxing and isolation for apps & services
Stricter SELinux policies, seccomp-bpf and more
Backported security features and quicker patching
Benefiting from upstream changes long before stock
Firewall & network hardening
Along with improvements like MAC randomization
Open-source and free of proprietary services
Uses alternatives to Google apps/services like F-Droid
Security-centric user experience changes
Better defaults, finer-grained permission control
Note :-
Copperhead is meant to be used with the bootloader locked with NO custom recovery installed and no GAPPS.
Credits :-
CopperheadOS team and razorloves for inspiration.
References :-
Copperhead homepage
Documentation
Instructions used to build
Last Updated 2018-02-28
If anyone wants to reupload to a better file hosting site please do.
For future updates.
I do realize this is in the Pixel XL section. Please feel free to remove it. The hope is that others would take up the process for the Pixel XL.
Can you please link to the kernel source, if not all repos used to build this?
jisoo said:
Can you please link to the kernel source, if not all repos used to build this?
Click to expand...
Click to collapse
They are located on the OP under "Instructions used to build"
jahrule said:
For future updates.
I do realize this is in the Pixel XL section. Please feel free to remove it. The hope is that others would take up the process for the Pixel XL.
Click to expand...
Click to collapse
MODERATOR NOTICE:
The development section is not a place to share ROMs or hope that someone will take up developing a ROM that you post here. In this section you are only allowed to post your own work, and it must meet the requirements for posting in the Development section as laid out in the sticky titled Device Forum Rules (Please Read before posting).
THREAD CLOSED
MoKee Open Source is the biggest non-profit Android Open Source development team in China, with members from all parts of the world. We follow the latest development from Google closely and improve various parts of Android according to the user habits. Being a non-profit organisation, we utilise our spare time and own funds to keep this passion alive. Therefore, the costs for the forum and servers are solely beared by us. In order to provide a good user experience, we only included a few preinstalls in the ROM. Along with the advertisements in the forum; we hardly get enough to pay for the bandwidth. The point is, those are our only source of income, however many developers choose to exclude them when releasing unofficial builds. Unlike CyanogenMod, we did not accept monetary help at the early stages, as in China, most people do not understand the meaning of “making a donation”. They would think of it as buying a service, which is conflicting with our objectives. Anyways, we still made it until today, and even started to provide third party developers a chance to utilise our OTA system. All of these are the fruit of our hard work and passion. We are proud of the happy users, and we are also proud of the support given to MoKee Open Source. Most importantly, we are proud of the improvements we have achieved all these while, and the advancements never stop.
What's working:
Almost everything
Known issues:
SELinux is permissive
You tell me
Instructions:
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Wipe Data/Cache
4. Flash the ROM
5. Flash TWRP installer ZIP
6. Reboot to Recovery
7. Flash GApps
8. Flash Magisk (Optional)
9. Reboot to System
Downloads:
Google Drive
MEGA
Source:
Kernel Source code: None, prebuilt kernel
Device Source code : mkq-mr1
ROM Source code: Mokee Source Code
Credits:
DtHnAme
Mokee Development Team
LineageOS
Big Thanks:grewal
Version Information:
Android Version: 10
Status: Unofficial
Last updated: 2021-03-10
DtHnAme said:
MoKee Open Source is the biggest non-profit Android Open Source development team in China, with members from all parts of the world. We follow the latest development from Google closely and improve various parts of Android according to the user habits. Being a non-profit organisation, we utilise our spare time and own funds to keep this passion alive. Therefore, the costs for the forum and servers are solely beared by us. In order to provide a good user experience, we only included a few preinstalls in the ROM. Along with the advertisements in the forum; we hardly get enough to pay for the bandwidth. The point is, those are our only source of income, however many developers choose to exclude them when releasing unofficial builds. Unlike CyanogenMod, we did not accept monetary help at the early stages, as in China, most people do not understand the meaning of “making a donation”. They would think of it as buying a service, which is conflicting with our objectives. Anyways, we still made it until today, and even started to provide third party developers a chance to utilise our OTA system. All of these are the fruit of our hard work and passion. We are proud of the happy users, and we are also proud of the support given to MoKee Open Source. Most importantly, we are proud of the improvements we have achieved all these while, and the advancements never stop.
What's working:
Almost everything
Known issues:
SELinux is permissive
You tell me
Instructions:
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Wipe Data/Cache
4. Flash the ROM
5. Flash TWRP installer ZIP
6. Reboot to Recovery
7. Flash GApps
8. Flash Magisk (Optional)
9. Reboot to System
Downloads:
Google Drive
MEGA
Source:
Kernel Source code: None, prebuilt kernel
Device Source code : mkq-mr1
ROM Source code: Mokee Source Code
Credits:
DtHnAme
Mokee Development Team
LineageOS
Big Thanks:grewal
Version Information:
Android Version: 10
Status: Unofficial
Last updated: 2021-03-10
Click to expand...
Click to collapse
Hey, any screenshots?
Why it is so hard for all to put some screenshots. Credits, Instructions, bla bla... but never screenshots
zlatko63 said:
Why it is so hard for all to put some screenshots. Credits, Instructions, bla bla... but never screenshots
Click to expand...
Click to collapse
Because maybe ia this project dead
DtHnAme said:
MoKee Open Source is the biggest non-profit Android Open Source development team in China, with members from all parts of the world. We follow the latest development from Google closely and improve various parts of Android according to the user habits. Being a non-profit organisation, we utilise our spare time and own funds to keep this passion alive. Therefore, the costs for the forum and servers are solely beared by us. In order to provide a good user experience, we only included a few preinstalls in the ROM. Along with the advertisements in the forum; we hardly get enough to pay for the bandwidth. The point is, those are our only source of income, however many developers choose to exclude them when releasing unofficial builds. Unlike CyanogenMod, we did not accept monetary help at the early stages, as in China, most people do not understand the meaning of “making a donation”. They would think of it as buying a service, which is conflicting with our objectives. Anyways, we still made it until today, and even started to provide third party developers a chance to utilise our OTA system. All of these are the fruit of our hard work and passion. We are proud of the happy users, and we are also proud of the support given to MoKee Open Source. Most importantly, we are proud of the improvements we have achieved all these while, and the advancements never stop.
What's working:
Almost everything
Known issues:
SELinux is permissive
You tell me
Instructions:
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Wipe Data/Cache
4. Flash the ROM
5. Flash TWRP installer ZIP
6. Reboot to Recovery
7. Flash GApps
8. Flash Magisk (Optional)
9. Reboot to System
Downloads:
Google Drive
MEGA
Source:
Kernel Source code: None, prebuilt kernel
Device Source code : mkq-mr1
ROM Source code: Mokee Source Code
Credits:
DtHnAme
Mokee Development Team
LineageOS
Big Thanks:grewal
Version Information:
Android Version: 10
Status: Unofficial
Last updated: 2021-03-10
Click to expand...
Click to collapse
Will it be this ROM with Android 11 , i found it as GSI but don't know how to install it
DtHnAme said:
MoKee Open Source is the biggest non-profit Android Open Source development team in China, with members from all parts of the world. We follow the latest development from Google closely and improve various parts of Android according to the user habits. Being a non-profit organisation, we utilise our spare time and own funds to keep this passion alive. Therefore, the costs for the forum and servers are solely beared by us. In order to provide a good user experience, we only included a few preinstalls in the ROM. Along with the advertisements in the forum; we hardly get enough to pay for the bandwidth. The point is, those are our only source of income, however many developers choose to exclude them when releasing unofficial builds. Unlike CyanogenMod, we did not accept monetary help at the early stages, as in China, most people do not understand the meaning of “making a donation”. They would think of it as buying a service, which is conflicting with our objectives. Anyways, we still made it until today, and even started to provide third party developers a chance to utilise our OTA system. All of these are the fruit of our hard work and passion. We are proud of the happy users, and we are also proud of the support given to MoKee Open Source. Most importantly, we are proud of the improvements we have achieved all these while, and the advancements never stop.
What's working:
Almost everything
Known issues:
SELinux is permissive
You tell me
Instructions:
1. Download the proper flashable ZIP for your device
2. Reboot to Recovery
3. Wipe Data/Cache
4. Flash the ROM
5. Flash TWRP installer ZIP
6. Reboot to Recovery
7. Flash GApps
8. Flash Magisk (Optional)
9. Reboot to System
Downloads:
Google Drive
MEGA
Source:
Kernel Source code: None, prebuilt kernel
Device Source code : mkq-mr1
ROM Source code: Mokee Source Code
Credits:
DtHnAme
Mokee Development Team
LineageOS
Big Thanks:grewal
Version Information:
Android Version: 10
Status: Unofficial
Last updated: 2021-03-10
Click to expand...
Click to collapse
Will we get Android 10?
We are happy to announce that we now have launched AOSP build instructions for Android 13!
The Xperia Open Source Project (Xperia Open Devices) is an initiative created to guide the developers step-by-step on how to build AOSP for their unlocked Xperia devices. Our instructions will show you how to prepare your environment, how to download all the necessary tools, and how to download and configure the code before you can build AOSP images and flash them on your own device.
New AOSP build instructions for Android 13 - Sony Developer World
developer.sony.com