Database Info

[KERNEL] Samsung Galaxy Y (GT-S5360) make & tweak with original sources

since the kernel sources for the GT-S5360 were published by Samsung. now folks can build their own kernels and flash them.
building is supposed to work in Win and Linux, but Linux seems to be faster to do.
since even unpacking the win sources get u into trouble,
so rather download it into a mint12-debian system.
following the readme and running make in /kernel/common fails due to missing /opts/...toolchain dir
HOW TO BUILD KERNEL 2.6.35 FOR GT-S5360
1. How to Build
- get Toolchain
Visit codesourcery. com , download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI.
Extract kernel source and move into the top directory.
$ cd kernel/common/
$ make bcm21553_totoro_05_defconfig
$ make
2. Output files
- Kernel : kernel/common/arch/arm/boot/zImage
3. How to make .tar binary for downloading into target.
- change current directory to kernel/common/arch/arm/boot
- type following command
$ tar cvf GT-S5360_Kernel_Gingerbread.tar zImage

Hey! Why are you not doing it?

up... can someone follow this up?

I will try it.But I dont Have the Device.I have created a tweaked Kernel for Optimus Me p350 with CPU Governers for more performance.Someone have to test the kernels.can anyone provide the link to the source

vivekkalady said:
I will try it.But I dont Have the Device.I have created a tweaked Kernel for Optimus Me p350 with CPU Governers for more performance.Someone have to test the kernels.can anyone provide the link to the source
Click to expand...
Click to collapse
please create a custom/tweaked kernel for us. we would be very greatful to you if you can do it

there are now 4+ custom rom's around. the cranium project offers a good tutorial. pls follow up there.

vivekkalady said:
I will try it.But I dont Have the Device.I have created a tweaked Kernel for Optimus Me p350 with CPU Governers for more performance.Someone have to test the kernels.can anyone provide the link to the source
Click to expand...
Click to collapse
here it is.
https://opensource.samsung.com/index.jsp;jsessionid=561ED613C70155D054F4934A262820B6

[DEV] LANYU 910 / Airpaid RK2918 - Kernel / ICS WorkInProgress

Working on porting ICS to the Lanyu 910 / X10 Airpad MID-910. I think the kernel sources used for the Pascal2 could possibly work with the 910 after some config changes.
Basically with the 910 we have no stock kernel source available for reference, no stock configuration, no detailed hardware inside the device.. We know it uses the rk2918 rockchip and I know it uses the SWL-2480 / Marvel 8686, simply from observing the identifying markings on the chip. Other than that, all we know is that it uses a 2.6.32 kernel with android 2.3, has an unknown 7" capacitive touch screen, unknown camera, etc. In order for ICS to work with the 910 we'll have to use a 3.0.8+ kernel or backport all of the required components from 3.x to our working 2.6.32 sources -however we don't have the patched sources for the stock firmware, so we are better off to just use 3.0.8 kernel that the source is available for on many rk2918 devices - of course we'd have to make configuration changes to our specific hardware, and possibly patch the sources with modified/new source code for our specific hardware (if we can obtain it).
Pascal 2 has a realtek based wireless chipset.. 910 uses the SWL-2940 / Marvel 8686, the module for this is also included in the kernel sources. The 910 has an unknown touchscreen, so the kernel for the pascal2 may or may not work with the touch screen settings. It is quiet difficult to work on the kernel without in depth knowledge of all the hardware. The 910 has Lanyu printed on the motherboard, and I'm not successful in finding any detailed hardware information for the board on the 910.
Also I am concerned with the memory mappings since the 910 only has 512mb ram and the pascal2 has 1GB+
Really wish these Chinese tablet manufacturers would follow the rules of GPL and release their source code, it would help A LOT with getting ICS to work with the 910.
As far as the rockchip and the ICS rom that vurrut has put together, I am almost 100% sure that the system.img that he used will work with the 910 as long as I get a working 3.0.8 kernel for ICS reconfigured/recompiled and implement some changes in the boot.img for the init services relating to hardware.
If anyone has the X10 airpad (rk2918 based) or the Lanyu 910 and has some important information regarding the internal hardware, please contact me with details, as I can probably get a working kernel for our device in a matter of hours.
Needed:
Gsensor/Accelerometer MFG/Model
Input Keys Controller - MFG/Model
Battery Sensor Chip - MFG/Model
TouchScreen/Display - MFG/Model
Other mainboard chipsets - MFG/Model (excluding RK2918 Rockchip SoC)
It would be of much help if there was someone here knows the MFG/Model of any of the above hardware, and it would also be a great help if anyone knows what linux kernel drivers are used for any of the components inside the 910.
When I was working with the Kindle Fire kernel I had found a very helpful information page on the internal parts of the device, with very detailed information - it was really helpful. I know that with these generic Chinese tablets finding such info may be much more difficult due to lack of interest and lack of popularity when compared to major brand tablets such as the Kindle Fire - but if anyone out there has ran across similar information it would give us GREAT progress in developing an ICS ROM for the 910. Here is a link to the breakdown of components in the Kindle Fire:
http://www2.electronicproducts.com/Amazon_Kindle_Fire_D01400_Tablet-whatsinside_text-123.aspx
The thread to the ICS ROM for Pacal 2 (rk2918) device is here: http://forum.xda-developers.com/showthread.php?t=1734181
A big thanks to Vurrut for all of his work! Hopefully we can use parts of his ROM to get ICS running on our Lanyu/Airpad!

Pls open a terminal, type "dmesg" and upload the log. Then we will see
If you have luck your build has also the kernel config file. You will find it under /proc/config.gz.
- Oma -

Oma7144 said:
Pls open a terminal, type "dmesg" and upload the log. Then we will see
If you have luck your build has also the kernel config file. You will find it under /proc/config.gz.
- Oma -
Click to expand...
Click to collapse
Do you honestly think I would be working on a Linux kernel without a knowledge of the existence of dmesg or config.gz? Did you also forget to remind me of adb shell logcat -d >> logcat.log ?
Sent from my A100 using xda premium

linuxsociety said:
Do you honestly think I would be working on a Linux kernel without a knowledge of the existence of dmesg or config.gz? Did you also forget to remind me of adb shell logcat -d >> logcat.log ?
Click to expand...
Click to collapse
Sry. You've been asking for touch, sensors etc.. In the named logs you will find all that.
- Oma -

Oma7144 said:
Sry. You've been asking for touch, sensors etc.. In the named logs you will find all that.
- Oma -
Click to expand...
Click to collapse
Only partial information can be obtained in this manner as it will only show what device modules are loaded, the information I was wanting was precise model information of the chipsets used in the tablet. And the config for the stock kernel is not included in procfs anyway as the developers must have not said =Y to CONFIG_IKCONFIG
Sent from my A100 using xda premium

]
Code:
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879_I2C is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_I2C_LZ300 is not set
CONFIG_I2C_LZ300_ST=y
# CONFIG_I2C_SIS809 is not set
# CONFIG_INPUT_MISC is not set
CONFIG_INPUT_GPIO=y
#
# Magnetometer sensors
#
# CONFIG_COMPASS_AK8975 is not set
# CONFIG_COMPASS_AK8973 is not set
CONFIG_G_SENSOR_DEVICE=y
# CONFIG_GS_MMA7660 is not set
CONFIG_GS_MMA8452=y
# CONFIG_GS_L3G4200D is not set
# CONFIG_INPUT_JOGBALL is not set
# CONFIG_LIGHT_SENSOR_DEVICE is not set
With the Model (SIS809, MMA8452, AK8975 etc.) you have all what you need. This you will also find in the dmsg log.
That's enough to compile from sources.
Anyway.
- Oma -

Oma7144 said:
]
Code:
CONFIG_INPUT_TOUCHSCREEN=y
# CONFIG_TOUCHSCREEN_AD7879_I2C is not set
# CONFIG_TOUCHSCREEN_AD7879 is not set
# CONFIG_I2C_LZ300 is not set
CONFIG_I2C_LZ300_ST=y
# CONFIG_I2C_SIS809 is not set
# CONFIG_INPUT_MISC is not set
CONFIG_INPUT_GPIO=y
#
# Magnetometer sensors
#
# CONFIG_COMPASS_AK8975 is not set
# CONFIG_COMPASS_AK8973 is not set
CONFIG_G_SENSOR_DEVICE=y
# CONFIG_GS_MMA7660 is not set
CONFIG_GS_MMA8452=y
# CONFIG_GS_L3G4200D is not set
# CONFIG_INPUT_JOGBALL is not set
# CONFIG_LIGHT_SENSOR_DEVICE is not set
With the Model (SIS809, MMA8452, AK8975 etc.) you have all what you need. This you will also find in the dmsg log.
That's enough to compile from sources.
Anyway.
- Oma -
Click to expand...
Click to collapse
Mr. Oma, I am sorry but I think you may be in the wrong thread, the Lanyu 910 only shares one thing in common with the other common RK2918 based tablets, and that is the RK2918 its self, the rest of the hardware that makes up the full system is different on the 910/Airpad than the more popular tablets that are using the RK2918. For example you probably use a RTL based wifi chip in the config you are using also, where the 910/AP uses the SWL-2480 which uses a Marvel 8686 driver in the linux kernel or you can use the libertas driver in more recent kernels. What exactly is the config you pasted here from? At this point I know the internal hardware enough to get a proper config file for the 910/Airpad, however there are compile issues with certain components and without resolving the compile issues there is no kernel image going to be generated unless I disable the problems at hand in the config, if you want more up-to-date information then head over the the x10 forums and check the original thread for 910/AP kernel development: http://forums.x10.com/index.php?topic=27184.0

Have you seen this?
Here is another Tab using SWL-2480 (looks like an Aoson M12).
Here is another 3.0.8 source, originally from a Chinese Tab named Xinboa.
Maybe that helps.
- Oma -

Oma7144 said:
Have you seen this?
Here is another Tab using SWL-2480 (looks like an Aoson M12).
Here is another 3.0.8 source, originally from a Chinese Tab named Xinboa.
Maybe that helps.
- Oma -
Click to expand...
Click to collapse
I appreciate your effort in helping me find info, but I have already researched most the possibilities and am already aware of the sites you linked. The problems aren't finding hardware specs, the problem now is getting 3.0.8 sources to compile with the Airpads hardware selected in the configuration, as I posted in the x10 forum, it doesn't appear that any 3.0.8 kernels have been successfully compiled for other devices using the same board-config as the 910, in fact the link you specified with the swl-2480 is the only device that has similar hardware aside from the rk2918 that I have found. The wifi and audio both fail to compile with Ody.se sources. I have decided to put most of my work now into testing/development of Jelly Bean for the Acer Iconia Tab, as it doesn't seem that many others are interested in the 910/Airpad development. Thanks again

Ok.
Odys-Xpress sources? That's kernel 2.6.32.27, isn't it?
But try the sources from above link. Could search for that
A library for Marvell 8686 SDIO WLAN devices.
So far, the following modules have been verified:
(1) Samsung SWL-2480
(2) Azurewave AW-GH321
(3) USI WM-G-MR-09
(4) Murata SP-8HEP-P
I don't know if they will compile.
- Oma -

Oma7144 said:
Ok.
Odys-Xpress sources? That's kernel 2.6.32.27, isn't it?
But try the sources from above link. Could search for that
A library for Marvell 8686 SDIO WLAN devices.
So far, the following modules have been verified:
(1) Samsung SWL-2480
(2) Azurewave AW-GH321
(3) USI WM-G-MR-09
(4) Murata SP-8HEP-P
I don't know if they will compile.
- Oma -
Click to expand...
Click to collapse
They won't compile with 4.2.0 or 4.4.0 arm eabi toolchain in 3.0.8 sources, i tried them, since 3.0.8 it has been replaced with libertas instead of mv8686, i've done looked into all of it man

linuxsociety said:
They won't compile with 4.2.0 or 4.4.0 arm eabi toolchain in 3.0.8 sources, i tried them, since 3.0.8 it has been replaced with libertas instead of mv8686, i've done looked into all of it man
Click to expand...
Click to collapse
Use gcc 4.5.2 or higher.
- Oma -

Oma7144 said:
Use gcc 4.5.2 or higher.
- Oma -
Click to expand...
Click to collapse
I also tried gcc 4.6.2 and 4.6.3 natively setup with cross compile in Gentoo / Funtoo - I get the same same errors with the wifi and the audio as using the appropriate eabi-arm toolchains.. I tracked down the problems though, it is a dephell with major code changes in common headers. The headers that are included in the sources have changed from 2.6.32.27 and to 3.0.8 and porting everything up to current is quiet more code changes than I am willing to work on. Like I have said though, I am no longer working on this kernel for the generic devices 910/AP, I have more work on my slate now than I need working on the Acer Vangogh / Vendetta kernels for Jelly Bean to incorporate Tiny HAL and newer tegra changes keeping compatability with the only Acer source we have available. But at least I am not limited to products that aren't following the GPL appropriately, and the use of uncommon hardware that makes debugging damn near impossible. I almost have the Vangogh board and Acer specifics ported over to 3.1's grouper from the nexus project and it's much more smoother than working with that chinese developed tab

Ok, than have a good time!
Greetings to Southern Kentucky.
- Oma -

linuxsociety said:
If anyone has the X10 airpad (rk2918 based) or the Lanyu 910 and has some important information regarding the internal hardware, please contact me with details, as I can probably get a working kernel for our device in a matter of hours.
Click to expand...
Click to collapse
Here you go: eboda-TS, MV8686 WLAN, MMA8452Q Sensor, WM8988 Audio, ANX7150 HDMI, HYM8563 Clock, APX192 Powermgt.
Could you pls compile a kernel?
- Oma -

MT6516 kernel and other files

Find here the source code of MT6516 kernel and other important files.
Kernel source code MT6516:
http://sourceforge.net/projects/alcatel/files/?source=navbar
Select this file: OT_890D_20120725.tar.xz

ajparag said:
Find here the source code of MT6516 kernel and other important files.
Kernel source code MT6516:
http://sourceforge.net/projects/alcatel/files/OT_890_20120110.tar.xz/download
More coming up soon
Click to expand...
Click to collapse
can this unbrick my phone????
what to do after downloading this??

ajparag said:
Find here the source code of MT6516 kernel and other important files.
Kernel source code MT6516:
http://sourceforge.net/projects/alcatel/files/OT_890_20120110.tar.xz/download
More coming up soon
Click to expand...
Click to collapse
Hi.
The above sources are total incomplete for the mt6516 Platform.
It miss several important Files like the makeMtk Perl Script.
I am looking my self for the mt6516 Linux Kernel Sources now for several weeks to rebuild the Linux Kernel for my self.
If somebody has the complete linux source for the mt6516 please tell it me.
Thanks in advance.

ARAN said:
Hi.
The above sources are total incomplete for the mt6516 Platform.
It miss several important Files like the makeMtk Perl Script.
I am looking my self for the mt6516 Linux Kernel Sources now for several weeks to rebuild the Linux Kernel for my self.
If somebody has the complete linux source for the mt6516 please tell it me.
Thanks in advance.
Click to expand...
Click to collapse
Try this link: http://sourceforge.net/projects/alcatel/files/?source=navbar
From here download this version - OT_890D_20120725.tar.xz
ATB!

[GUIDE]Building Mediatek boot.img{Appending headers}

Guide to Mediatek Building(Guide 2:=boot.img)
A common misconception on XDA is that mediatek devices have boot.img similar to qualcomm.. I'll try to explain why it isn't and how to make one.
Mediatek appends a header to its Ramdisk(initramfs) and its kernel so that the board can figure out that its a ramdisk/kernel. Without these headers the boot.img you build will won't work; If you've been getting bad results when making a boot.img this could be one of the reasons
Requisite
Any Linux based system
the mkimage i've attached in the post
Adding the MediaTek header
A executable named the 'mkimage' is needed for this(attached in post). If you're one of the kernel devs or for the ones who have the mediatek kernel source, this file is present in the kernel_source/mediatek/build/tools/mkimage.
What does it do?
it appends the mediatek header to the first 512 bytes of your ramdisk/kernel
Adding the meditek header
For the kernel,
Code:
mkimage kernel KERNEL > kernel_with_meditek_header
For the ramdisk,
Code:
mkbootfs ./root/ | minigzip >ramdisk.gz
mkimage ramdisk.gz ROOTFS > ramdisk.img
Removing the MediaTek header
If you want to remove header from kernel,
Code:
dd if=kernel of=kernel_without_header bs=1 skip=512
If you want to remove header from ramdisk
Code:
dd if=ramdisk of=ramdisk_without_header bs=1 skip=512
the bs tells dd how many bytes to read and write at a time.
the skip tells it that how many bytes to skip at start. here its 512 since the mediatek header occupies 512bytes. we can use count if you want
Here's how you manually pack boot.img after adding headers
Code:
mkbootimg --kernel zImage_with_header --ramdisk ramdisk_with_header.img -o new_boot.img
You can now use this boot.img to flash to your phone
Modules!!
Modules are very important, Read previous guide(Building kernel) about how to build modules(Guide attached to signature). Modules are very kernel specific and the rom wont boot if you don't push these modules to the /system/lib/modules replacing the ones currently there.
Extra Information!
to delete parts of file from the end of file which is 100 bytes. for example:
Code:
dd if=file of=file1 bs=1 skip=10 count=85
/*count=filesize-startsskip-endskip*/
here,count=100-10-5=85.
Hope this guide helped you.
All questions are welcome in the thread
Regards and Good luck
Links to my next Guides
Building the ROM{MediaTek}
Building the Kernel{MediaTek}

Nice guide
... but that was already explained on this thread
The thread was for the MT6577, but concerning this issue (and others) its also valid for the other's MT65xx ; MT81xx ; MT83xx SoC's.
Also this thread is the best resource on @xda concerning Mediatek kernel / issues , etc.
But this should help, the users that are new on the "Mediatek" Platform.
Regards

superdragonpt said:
Nice guide
... but that was already explained on this thread
The thread was for the MT6577, but concerning this issue (and others) its also valid for the other's MT65xx ; MT81xx ; MT83xx SoC's.
Also this thread is the best resource on @xda concerning Mediatek kernel / issues , etc.
But this should help, the users that are new on the "Mediatek" Platform.
Regards
Click to expand...
Click to collapse
I'm making a guide for building an rom from source step by step for the new developers. I've started off with the boot.img. Not sure if that's the way to go, but I'll try my best to make people understand the build process and how mediatek works
Sent from my Moto G using XDA Free mobile app

MasterAwesome said:
I'm making a guide for building an rom from source step by step for the new developers. I've started off with the boot.img. Not sure if that's the way to go, but I'll try my best to make people understand the build process and how mediatek works
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
Your more than welcome we are only an few working with Mediatek's.
We all know how MTK works, and their Closed Source / Anti-GPL Atittude...
Best Regards

superdragonpt said:
Your more than welcome we are only an few working with Mediatek's.
We all know how MTK works, and their Closed Source / Anti-GPL Atittude...
Best Regards
Click to expand...
Click to collapse
My aim is to increase that number
Sent from my Moto G using XDA Free mobile app

W0W its good to see more Devs started to work for MTK devices ^_^ nice guide

EnerJon said:
W0W its good to see more Devs started to work for MTK devices ^_^ nice guide
Click to expand...
Click to collapse
You're quite welcome :laugh:

Kernel Development guide coming today

MasterAwesome said:
Kernel Development guide coming today
Click to expand...
Click to collapse
i am kind of porter and developer of a110 aka micromax canvas 2 community.....
i would love to learn about making kernal and mediatek code....
waiting for it.....
thanks in advance..:laugh:

Avenger4droid said:
i am kind of porter and developer of a110 aka micromax canvas 2 community.....
i would love to learn about making kernal and mediatek code....
waiting for it.....
thanks in advance..:laugh:
Click to expand...
Click to collapse
I've added the links to my signature. Be sure to check it out

MasterAwesome said:
I've added the links to my signature. Be sure to check it out
Click to expand...
Click to collapse
thank you...Checking....

Suggestions for new guides are welcome and I'll try my best to do them.
Sent from my Moto G using XDA Free mobile app

Nice tutorial but still not clear for me. So i have built zImage, and then what? I need to use mkimage on zImage I have to produce boot.img, then push boot.img to my device?

giaur said:
Nice tutorial but still not clear for me. So i have built zImage, and then what? I need to use mkimage on zImage I have to produce boot.img, then push boot.img to my device?
Click to expand...
Click to collapse
yes you apply mkimage on the zImage and ramdisk The we mkbootimg for converting it into a boot.img and then you push to device.
MasterAwesome
Sent from my Moto G

Should I add mediatek headers to zImage and ramdisk and then pack them into boot.img?

giaur said:
Should I add mediatek headers to zImage and ramdisk and then pack them into boot.img?
Click to expand...
Click to collapse
Yes use
Code:
mkbootimg - -kernel zImage - -ramdisk ramdisk.img -o boot.img
Sent from my Moto G

Thanks, I think now it's clear. I think it would be useful for newbies if you also add this to first post. Also - don't I need any modules (.ko) also to push to device?

giaur said:
Thanks, I think now it's clear. I think it would be useful for newbies if you also add this to first post. Also - don't I need any modules (.ko) also to push to device?
Click to expand...
Click to collapse
Yes, you need to push the modules to your phones since they are kernel specific. To reduce size strip them off of unneeded assembler messages.
Regards
MasterAwesome
Sent from my Moto G

More information about pushing boot.img to phone and important stuff added to first post
Regards
MasterAwesome

WOW! good guide, I only have one problem, if I have a premade boot.img and I want to change the kernel, how do I do that? Thanks for this guide

[GUIDE] Build LineageOS 14.1 for flamingo

Hello there!
Many of you want to get a nougat working rom for our Xperia E3. We have kernel sources, vendor files, device... So if you wanna try to make the rom this guide is for you.
Prerequisites
64 bit computer with 64 bit Linux OS installed (or virtual machine)
At least 4gb of RAM and about 100GB of free storage (more if you enable ccache)
Much patience (the process will be long)
Getting started
Android SDK
You can setup android SDK by running
Code:
sudo apt-get install adb fastboot
Installing required packages
For that you can follow the steps on https://wiki.lineageos.org/devices/nicki/build#install-the-build-packages
Setting up directories
Create a folder in which android source will be downloaded
Code:
mkdir -p ~/android/lineage
Note: "~/android/lineage" is an example, you can create whatever folder you want, but in the next steps be sure you change paths.
Install the repo command
Like before you only need to run
Code:
sudo apt-get install repo
Initialize the LineageOS source repository
Now we can start to prepare sources download. Enter the following to initialize the repository:
Code:
cd ~/android/lineage
repo init -u https://github.com/LineageOS/android.git -b cm-14.1
And we need to prepare local manifests:
Code:
git clone https://github.com/rmnhg/local_manifests.git -b cm-14.1 .repo/local_manifests
Download the source code
To start the download of the source code to your computer:
Code:
repo sync
Note: This process will be long (over 30gb are going to be downloaded) and can be longer if your connection is slow so be patience.
Prepare the device-specific code
After the source downloads, ensure you’re in the root of the source code, then type:
Code:
source build/envsetup.sh
breakfast flamingo
This will prepare flamingo sources to be compiled.
(Optional) Turn on caching to speed up build
You can setup ccache if you want to speed up subsequent builds by running:
Code:
export USE_CCACHE=1
and adding that line to your ~/.bashrc file. Then, specify the maximum amount of disk space you want ccache to use by typing this from the top of your Android tree:
Code:
prebuilts/misc/linux-x86/ccache/ccache -M 50G
where 50G corresponds to 50GB of cache. This needs to be run once. Anywhere from 25GB-100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s Android build environment initialization page.
You can also enable the optional ccache compression. While this may involve a tiny performance slowdown, it increases the number of files that fit in the cache. To enable it, run:
Code:
export CCACHE_COMPRESS=1
or add that line to your ~/.bashrc file.
You can also change ccache files path by running:
Code:
export CCACHE_DIR=[COLOR="YellowGreen"]<path of your choice>[/COLOR]
or add that line to your ~/.bashrc file.
Configure jack
Jack is the new Java compiler used when building LineageOS 14.1. It is known to run out of memory - a simple fix is to run this command:
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
Adding that command to your ~/.bashrc file will automatically configure Jack to allocate a sufficient amount of memory.
Start building
Now you can start compiling LineageOS. You can start running:
Code:
croot
brunch flamingo
NOTE: If terminal tells you "croot/breakfast: command not found" just run
Code:
source build/envsetup.sh
and try again.
NOTE 2: If you receive the error "SSL error when connecting to the Jack server. Try 'jack-diagnose'" check this post for a fix.
This will finally compile LineageOS for flamingo :good:
If it finishes succesfully, you will have in out/target/product/flamingo two files:
recovery.img, which is the LineageOS recovery image.
lineage-14.1-<date>-UNOFFICIAL-flamingo.zip, which is the LineageOS installer package.
You have to flash ano and copy installer zip into the phone.
Then reboot into recovery (Power+Vol down) and install this zip.
You can flash flash recovery running
Code:
sudo fastboot -s 256M flash recovery <pathtorecovery.img>
Thanks to @infus for his trick (-s 256M) with fastboot commands for big images.
I hope this guide has been useful for you
PD: If you want to discuss about development of this ROM, you can join our Telegram group here.
Join now​

UPDATES
[06/13/2017] Guide successfully builds Lineage, but we have to fix kernel becouse it's not booting. I've also updated my local_manifests repo, so you need to run in android/lineage this
Code:
cd .repo/local_manifests && git pull origin cm-14.1 ;
cd ../..
[06/23/2017] Booted! But there are some bugs, we will upload ROM when that bugs are fixed
[07/25/2017] After a month we got this working for all variants, with basic hardware working (no camera yet) and with latest TWRP working . I'm working now on getting camera working and other small projects (on Xperia E3 also) but I am being slower to release new things because I have not much time and internet to work, I'm sorry.
[09/01/2017] Camera driver is now working! I have ported stock camera driver to renaissance kernel (LA.BF.1.1.3.. CAF) in another folder with the tag CONFIG_MSMB_CAMERA_FLAMINGO
Camera is still not working because of the HAL but it is nearer
[12/15/2017] I'm sorry we paused releasing updates for the compiled ROM, but I've changed much code and worked hard on camera (which is published on another branch named cm-14.1-cameratesting). Soon I will get some things finished and continue some other projects I had for this device. By the way I wish you a merry Christmas!

Reserved.

First of all I'm thanking you that at least you started to create the ROM for our device...
I really want to help you but I can't, due to internet connection, I don't have much data that I can download those sources (over 30gb)
But I really appreciate your work and hope someday you develop the ROM....

Hello! First of all, this version of Lineage is a very good thing for the Android Community ! I saw in the title that you are facing some difficulties, I'll try to help you. I have a friend who have the phone you talk about. We will probably try it on Wednesday. Did you need a log or something after you did ? Do you have the phone, or do you want my friend's one to test it ? Do you think that your ROM is compatible with your variant ? Or mine ? Thanks for passing some time on the gid build ! Have a good day !

infus38 said:
Hello! First of all, this version of Lineage is a very good thing for the Android Community ! I saw in the title that you are facing some difficulties, I'll try to help you. I have a friend who have the phone you talk about. We will probably try it on Wednesday. Did you need a log or something after you did ? Do you have the phone, or do you want my friend's one to test it ? Do you think that your ROM is compatible with your variant ? Or mine ? Thanks for passing some time on the gid build ! Have a good day !
Click to expand...
Click to collapse
The problems I have are related to system libs when compiling. Some of them fail to compile and I have to fix them manually, becouse of that system.img is not ready. All I have are LineageOS recovery and boot img files for LTE variants (for me that is not working but maybe for your phones things go well). On friday I can upload that imgs for you for test (remember that I have not system compiled so you can install recovery, boot.img may not work with other roms.

With my friend (who owns the xperia e3 d2203) we have started the step currently on the step of 30gb download
You can make a group with telegram to avoid polishing xda to speak and try to solve the problem encountered if you want it by giving the invitation link

infus38 said:
With my friend (who owns the xperia e3 d2203) we have started the step currently on the step of 30gb download
Click to expand...
Click to collapse
Cool, tell me if you start compiling process and, if you have errors, oleaje tell me what errors are given by terminal
infus38 said:
You can make a group with telegram to avoid polishing xda to speak and try to solve the problem encountered if you want it by giving the invitation link
Click to expand...
Click to collapse
Good idea! I'm going to do that
EDIT: Created a telegram group. You can join here https://t.me/xperia_e3

Hello ! After trying to compile the build, it stops and says that the error 1 has occurred. I tried many times but I always got this error (the only thing that changed is the time before the error occurs). I maybe didn’t correctly write the part with java and jack, but I just started to rewrite all from the beginning, I will keep you informed !?

I will prepare a computer to do this. It is almost done, just need a mouse I will download all these sources and start asap. Any help is much appreciated
EDIT: I have a Xperia E3 ready to test anything you want to. Just PM me for better contact info.. I'm here to help the development of this ROM.
I'm still using CM11 ;-; (can't live without camera)
---------- Post added at 11:36 PM ---------- Previous post was at 11:31 PM ----------
@AmulyaX please see this

jpzex said:
I will prepare a computer to do this. It is almost done, just need a mouse I will download all these sources and start asap. Any help is much appreciated
EDIT: I have a Xperia E3 ready to test anything you want to. Just PM me for better contact info.. I'm here to help the development of this ROM.
I'm still using CM11 ;-; (can't live without camera)
---------- Post added at 11:36 PM ---------- Previous post was at 11:31 PM ----------
@AmulyaX please see this
Click to expand...
Click to collapse
Best of luck. I don't have the E3 now but if you need any help or ask about any error, feel free to PM me. ??

@jpzex, @infus38, @rmnhg, I think you all have D2203. So, will you Port this ROM for D2212 after development of this ROM?

Ｄｈｒｕｖ said:
@jpzex, @infus38, @rmnhg, I think you all have D2203. So, will you Port this ROM for D2212 after development of this ROM?
Click to expand...
Click to collapse
For now I am at the build of the rom with the help of rmnhg if you want to come help us you been free under the agreement of rmnhg to come on the group telegrame create for this purpose ??

Ｄｈｒｕｖ said:
@jpzex, @infus38, @rmnhg, I think you all have D2203. So, will you Port this ROM for D2212 after development of this ROM?
Click to expand...
Click to collapse
Yes, that is not difficult. I think that a little kernel change and some build.prop tweaks could do the trick, but first we need to complete a single build for D2203, which is the main model.

rmnhg said:
Yes, that is not difficult. I think that a little kernel change and some build.prop tweaks could do the trick, but first we need to complete a single build for D2203, which is the main model.
Click to expand...
Click to collapse
can i join too ?

Nicklas Van Dam said:
can i join too ?
Click to expand...
Click to collapse
Of course! Everyone is useful and will be welcomed

rmnhg said:
Of course! Everyone is useful and will be welcomed
Click to expand...
Click to collapse
Which source that you used as device and kernel tree? And are you building nougat? I'm D2202 user
anyway, for D2202 only available source for cm12.1 when i see from @hell_lock. Will our device run with that device tree?

Nicklas Van Dam said:
Which source that you used as device and kernel tree? And are you building nougat? I'm D2202 user
anyway, for D2202 only available source for cm12.1 when i see from @hell_lock. Will our device run with that device tree?
Click to expand...
Click to collapse
We are using this kernel with this device tree. That sources are mainly designed for LTE variants, but in yukon repo there is more support for D2202/12 devices (see this commit).

rmnhg said:
We are using this kernel with this device tree. That sources are mainly designed for LTE variants, but in yukon repo there is more support for D2202/12 devices (see this commit).
Click to expand...
Click to collapse
Okay, thanks sir. I was recently trying to fix for D2202 too. i'm using different source code, this for device tree device tree & this for yukon platform yukon tree. anyway for kernel itself i don't know which source that i must using it, i'm using xperia open kernel device by jerpelea and using yukon codename. but i'm still not compile it yet since i've problem with los 13.0
---------- Post added at 05:35 AM ---------- Previous post was at 05:30 AM ----------
rmnhg said:
We are using this kernel with this device tree. That sources are mainly designed for LTE variants, but in yukon repo there is more support for D2202/12 devices (see this commit).
Click to expand...
Click to collapse
and anyway, when i check your kernel source that is for D2203 mode (arima_8926SS) for single sim. can we use that kernel? since i'm using same config too?
I'll try to using your source and report it back

Nicklas Van Dam said:
Okay, thanks sir. I was recently trying to fix for D2202 too. i'm using different source code, this for device tree device tree & this for yukon platform yukon tree. anyway for kernel itself i don't know which source that i must using it, i'm using xperia open kernel device by jerpelea and using yukon codename. but i'm still not compile it yet since i've problem with los 13.0
---------- Post added at 05:35 AM ---------- Previous post was at 05:30 AM ----------
and anyway, when i check your kernel source that is for D2203 mode (arima_8926SS) for single sim. can we use that kernel? since i'm using same config too?
oh ya, and vendor source? when i saw from themuppets. Flamingo only updated until cm-12.0 and after that in cm-13.0 until cm-14.0 flamingo doesn't exist in that branch?
Click to expand...
Click to collapse
For vendor I'm using https://github.com/kj77/vendor-yukon on cm-14.1 branch
I think you need to include some device tree files for D2202/D2212 in kernel, since as you said that kernel is specific for D2203. I could try to make basic support for it.