{All 2011}[GUIDE][DEV] How to build CyanogenMod 12.1 - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

This thread is intended for devs & advanced users only.
Here you can learn how to build CyanogenMod 12.1 for any of the 2011 xperia devices.
I will use 'smultron' as an example device, you should replace the codename with the device you want to build.
For the first time you try to build CM12.1
Follow this guide up to "Initialize the CyanogenMod source repository" step (don't execute this step).
http://wiki.cyanogenmod.org/w/Build_for_smultron
Initialize the CyanogenMod source repository
Enter the following to initialize the repository:
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
Get the required local manifest
Code:
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.githubusercontent.com/LegacyXperia/local_manifests/cm-12.1/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
Download the source code
Code:
repo sync
Setup the build environment
Code:
. build/envsetup.sh
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
ln -s vendor/extra/updates.sh updates.sh
./updates.sh
Setup the build environment & prepare the device-specific code.
Code:
cd ~/android/system
. build/envsetup.sh
breakfast smultron
Build the ROM (takes long time)
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-12.1-DATE-UNOFFICIAL-LegacyXperia-smultron.zip
The next times you want to build, you only need to do the following:
Sync the repositories & make sure you are using the latest local_manifest.
Code:
cd ~/android/system/
curl https://raw.githubusercontent.com/LegacyXperia/local_manifests/cm-12.1/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
repo sync
Setup the build environment
Code:
. build/envsetup.sh
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
./updates.sh
Build the ROM
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-12.1-DATE-UNOFFICIAL-LegacyXperia-smultron.zip
Steps to build only the kernel:
Sync the repositories.
Code:
cd ~/android/system/
repo sync
Setup the environment
Code:
. build/envsetup.sh
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
./updates.sh
Build the kernel
Code:
breakfast smultron
make -j4 bootimage
If the build finishes successfully, you will find the boot image here:
~/android/system/out/target/product/smultron/boot.img
Some suggestions for faster builds:
* Enable ccache
* Use the fastest hdd on your pc to store the source, build output & ccache
* You can also buy an ssd, if it's not large enough to hold everything, just store the build output & ccache
* mount /tmp on tmpfs (RAM).
The above have greatly improved my dirty build times with removed /out/target from 1h30m to 30m.
Mounting /tmp on tmpfs made the biggest improvement for me.
Credits: Thanks to hnl_dk for the initial CM9 & CM10 guides.

---

Reserved

---

getting insuficiant storage aviable in pa gappps (pico/micro) packages

---

Druboo666 said:
getting insuficiant storage aviable in pa gappps (pico/micro) packages
Click to expand...
Click to collapse
yes...same here
from build of 21st...i am getting this error
and even other zips are not getting flashed

---

TWRP
delete

---

Other than a fast HDD, does you computer need to be fast to build it? (Running a 2007 Core 2 Duo...)
Theonew said:
More cores are better. Here are the requirements to build it from source:
- 6GB of download.
- 25GB disk space to do a single build.
- 80GB disk space to build all AOSP configs at the same time.
- 16GB RAM recommended, more preferred, anything less will measurably benefit from using an SSD.
- 5+ hours of CPU time for a single build, 25+ minutes of wall time, as measured on a workstation (dual-E5620 i.e. 2x quad-core 2.4GHz HT, with 24GB of RAM, no SSD).
Click to expand...
Click to collapse
And I would say that a fast internet connection is also recommended, since the full source for initial sync is more than 10GBs (on ICS it already was, probably like 20GBs for lollipop).

---

brunch build error 12.1
Hi,
I am trying to build the image from the sources as per the build instructions to make my own test build.
After repo downloads, while building i am getting error "init/Kconfig:953: can't open file "usr/Kconfig"" in the brunch smultron command.
I am following these commands:
1) repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
2) curl https://raw.githubusercontent.com/Le...-12.1/semc.xml > /tmp/android/system/.repo/local_manifests/semc.xml
3) repo sync
4) ln -s vendor/extra/updates.sh updates.sh
5) ./updates.sh
6) . build/envsetup.sh
7) breakfast smultron
8) brunch smultron
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you tell me whats wrong.
Thanks.

---

joshipallav said:
Hi,
I am trying to build the image from the sources as per the build instructions to make my own test build.
After repo downloads, while building i am getting error "init/Kconfig:953: can't open file "usr/Kconfig"" in the brunch smultron command.
I am following these commands:
1) repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
2) curl https://raw.githubusercontent.com/Le...-12.1/semc.xml > /tmp/android/system/.repo/local_manifests/semc.xml
3) repo sync
4) ln -s vendor/extra/updates.sh updates.sh
5) ./updates.sh
6) . build/envsetup.sh
7) breakfast smultron
8) brunch smultron
Can you tell me whats wrong.
Thanks.
Click to expand...
Click to collapse
Delete the folder ~/android/system/kernel
repo sync again and make sure you get no errors
run make clean
try to build again

---

@Langes
hi.. just wanted to know.. any guide to Build for AOSP 5.1.1 Lollipop for Xperia Devices 2011 like cm12.1 here
and silly question time.. lol
is it possible that AOSP Android M source can also be built for Xperia Play (2011 Devices) .. I mean changes made by Mike (the AOSP Mike) + Source of Android M .. will it give us some output or :/

---

I built this rom today with new 3.10 kernel. It seems to be improved in some points (what isn't neccessary because of kernel), but with new kernel I can't use wifi and mobile data seems to be not working too. To build I fetched the new kernel and cherry-picked following commits:
Code:
#msm7x30-common: Update USB configuration for 3.10
cherries+=(LX_594)
#Use common msm7x30 kernel
#cherries+=(LX_422)
#msm7x30-common: Use common msm7x30 kernel
cherries+=(LX_421)
#mogami-common: wl12xx updates for 3.10
cherries+=(LX_407)
#media/msm7x30: Update for 3.10 support
cherries+=(LX_403)
#display/msm7x30: Update for 3.10 support
cherries+=(LX_402)
#audio/msm7x30: Update for 3.10 support
cherries+=(LX_401)
#kernel
#usb: Import msm charger changes from 6.2.B.0.200
cherries+=(LX_430)
#usb: msm72k_otg: Remove userspace events [REVISIT]
cherries+=(LX_428)
Is there something I missed to get working internet connection? (I didn't really test the rom for other things so far)

---

Getting this error when building AOSP rest all goes fine..
build also starts but getting this error.. any suggestion ?

---

Hey Mike, I tried to build CM14 and it fails. After some investigation it seems that imgdiff is missing. This was fixed on CM13: http://review.cyanogenmod.org/#/c/135193, which can't be applied to CM14 (no RECOVERY_PATCH_INSTALL).
I hope this helps.

---

zweif said:
Hey Mike, I tried to build CM14 and it fails. After some investigation it seems that imgdiff is missing. This was fixed on CM13: http://review.cyanogenmod.org/#/c/135193, which can't be applied to CM14 (no RECOVERY_PATCH_INSTALL).
I hope this helps.
Click to expand...
Click to collapse
I already have a cm14 zip for anzu, just unable to flash it because it's about 330MB and device runs out of memory when attempting to flash. Will try to find a solution/hack on the weekend

---

I managed to build cm14 zip for mango (installation fails as expected).
I modified build/core/Makefile, I don't fully understand how these dependencies work, but maybe there is a dependency issue.
There are dependencies: imgdiff <- RECOVERY_FROM_BOOT_PATCH <- INSTALLED_SYSTEMIMAGE <- BUILT_TARGET_FILES_PACKAGE (where make_recovery_patch is called, which needs imgdiff)
Now INSTALLED_SYSTEMIMAGE is defined before RECOVERY_FROM_BOOT_PATCH, but dependencies of INSTALLED_SYSTEMIMAGE are defined after that. Could this cause an issue?
After moving
Code:
INSTALLED_SYSTEMIMAGE := $(PRODUCT_OUT)/system.img
SYSTEMIMAGE_SOURCE_DIR := $(TARGET_OUT)
from line 1284 to line 1314 build was successfull.

---

mikeioannina said:
I already have a cm14 zip for anzu, just unable to flash it because it's about 330MB and device runs out of memory when attempting to flash. Will try to find a solution/hack on the weekend
Click to expand...
Click to collapse
I managed to flash cm14 after disabling dex-preoptimization. Zip size decreases to ~260MB. I didn't do extensive testing - messaging seems to work, dialing a number causes restart (system, not kernel), the only sounds I noticed were dialing sounds, i miss a browser and other apps - but it seems nice for a first impression.
Concerning my problem with imgdiff: After reading some make documentation I have no clue why it isn't built. Maybe these dependencies aren't tracked because RECOVERY_FROM_BOOT_PATCH is set to an empty string when BOARD_CANT_BUILD_RECOVERY_FROM_BOOT_PATCH is defined?
I can manually call 'make imgdiff' as workaround.
I tried some things that could have affected imgdiff before my last post, and I'm not sure if I cleared output directory. Did you try a clean build or could imgdiff come from a previous build on your machine?

---

bro, How much space does it need to sync the repo??
& if I want to port a ROM based on CM (Like Resurrection Remix or Liquid Smooth), would I have to use the command "repo sync"?

---

I'm trying to build CM14.0, but jack server is giving me a bad time with out of memory error. I have tried changing jack.server.max-service to 1, heap size to 2g, 3g and 4g, even to build without ninja, but always getting out of memory. In CM13.0 I could build without jack, but now the built is failing without it. I'm using Ubuntu 16.04 on an i3 with 4g RAM and 8g swap, I've seen cases with machines with better specs failing (e.g. i5, 8g RAM). Is it a bug with jack, or my specs is the limiting factor?
Edit: I guess this is the EOL for me :crying:.

---

azakosath said:
I'm trying to build CM14.0, but jack server is giving me a bad time with out of memory error. I have tried changing jack.server.max-service to 1, heap size to 2g, 3g and 4g, even to build without ninja, but always getting out of memory. In CM13.0 I could build without jack, but now the built is failing without it. I'm using Ubuntu 16.04 on an i3 with 4g RAM and 8g swap, I've seen cases with machines with better specs failing (e.g. i5, 8g RAM). Is it a bug with jack, or my specs is the limiting factor?
Edit: I guess this is the EOL for me :crying:.
Click to expand...
Click to collapse
Jack troubleshooting
If your computer becomes unresponsive during compilation or if you experience Jack compilations failing on “Out of memory error”
You can improve the situation by reducing the number of Jack simultaneous compilations by editing your $HOME/.jack-server/config.properties and changing jack.server.max-service= to a lower value.
Description with default values follows:
jack.server.max-service=<number> Maximum number of simultaneous Jack tasks. Default is 4.
jack.server.max-jars-size=<size-in-bytes> Maximum size for Jars, in bytes. -1 means no limit. Default is 100 MiB.
jack.server.time-out=<time-in-seconds> Time out delay before Jack gets to sleep. When Jack sleeps, its memoryusage is reduced, but it is slower to wake up. -1 means "do not sleep".Default is 2 weeks.
jack.server.service.port=<port-number> Server service TCP port number. Default is 8076. Needs to match theservice port defined in $HOME/.jack-settings on the client host (SeeClient section).
jack.server.admin.port=<port-number> Server admin TCP port number. Default is 8077. Needs to match theservice port defined in $HOME/.jack-settings on the client host (SeeClient section).
jack.server.config.version=<version> Internal, do not modify.

---

Mardon said:
Jack troubleshooting...
Click to expand...
Click to collapse
Thanks for answering, but I have already read these. I tried several combinations (max services and "-Xmx") without luck. Even:
Code:
export USE_NINJA=false
to build without ninja. The result was always the same, jack server was hanging and failing after 30 or more compilations.
P.S. I did use the changes that are not merged yet, but I don't think this is related.

---

You also can try
breakfast devicename
And after that
make -j1 bacon
To force 1 job compiling only
Gesendet von meinem GT-I8190 mit Tapatalk