Related
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
I have good news - Acer fixed kernel sourses for E350!
I complitely unpack this and get Mediatek folder. This is it's folder:
Code:
narod.ru/disk/63330748001.505f7027fe3648263f598fa74cd1e92a/mediatek.zip
Instructions for unpacking:
All actions must be on Linux OS (for example Ubuntu 12.04)
1. Download Acer Kernel Sourses:
Code:
global-download.acer.com/GDFiles/Document/App.%20Guide/App.%20Guide_Acer_1.0_A_A.zip?acerid=634873347782030348&Step1=SMART%20HANDHELD&Step2=LIQUID%20GALLANT&Step3=E350&OS=ALL&LC=en&BC=ACER&SC=PA_7
And put this to Desktop
2. Open Terminal and input this commands:
Code:
cd /home/user_name/Desktop
Where user_name is name of your User.
Code:
unzip ./App.\ Guide_Acer_1.0_A_A.zip
Code:
cd ./App.\ Guide_Acer_1.0_A_A
Code:
tar -xf Acer_AV041_E350_1.000.18_WW_GEN1_opensource.tar.gz
If all right, you get folder Acer_AV041_E350_1.000.18_WW_GEN1_opensource with content:
Code:
bootable external kernel mediatek prebuilt system
I don't know how to work with kernel sourses, but i think there are people who know.
P.S. Sorry, but my stats don't allow me to insert the links.
back37 said:
I have good news - Acer fixed kernel sourses for E350!
I complitely unpack this and get Mediatek folder. This is it's folder:
Code:
narod.ru/disk/63330748001.505f7027fe3648263f598fa74cd1e92a/mediatek.zip
Instructions for unpacking:
All actions must be on Linux OS (for example Ubuntu 12.04)
1. Download Acer Kernel Sourses:
Code:
global-download.acer.com/GDFiles/Document/App.%20Guide/App.%20Guide_Acer_1.0_A_A.zip?acerid=634873347782030348&Step1=SMART%20HANDHELD&Step2=LIQUID%20GALLANT&Step3=E350&OS=ALL&LC=en&BC=ACER&SC=PA_7
And put this to Desktop
2. Open Terminal and input this commands:
Code:
cd /home/user_name/Desktop
Where user_name is name of your User.
Code:
unzip ./App.\ Guide_Acer_1.0_A_A.zip
Code:
cd ./App.\ Guide_Acer_1.0_A_A
Code:
tar -xf Acer_AV041_E350_1.000.18_WW_GEN1_opensource.tar.gz
If all right, you get folder Acer_AV041_E350_1.000.18_WW_GEN1_opensource with content:
Code:
bootable external kernel mediatek prebuilt system
I don't know how to work with kernel sourses, but i think there are people who know.
P.S. Sorry, but my stats don't allow me to insert the links.
Click to expand...
Click to collapse
Unable to compile module. Some files still missing.
legale said:
Unable to compile module. Some files still missing.
Click to expand...
Click to collapse
May be, but no one said it would be easy...
In the directory mediatek for me miss the sub directory build-----> mediatek/build/......
I have try to compile this source but have more problem. When start with make i see that miss this directory mediatek/build/kernel/Makefile
I have try to change the line include ....mediatek/build/kernel/Makefile with include ....mediatek/source/kernel/Makefile but when start with compile i have error with other thing.
bye.
MT6575 working sources device TCL E928
sourceforge.net/projects/alcatel/files/TCL_E928_20121114.tar.xz/download
i've successfully compiled cifs.ko kernel module for my philips w732 (vermagic '3.0.13 preempt mod_unload armv7', almost without changing kernel config.
Hi legale
Thank you for your link but i have this problem:
../mediatek/build/Makefile:13: *** TARGET_PRODUCT/PROJECT is not set.
I have copy the miss directory into acer kernel but i have this problem.
Where i must set target product for you?
erlucky said:
Hi legale
Thank you for your link but i have this problem:
../mediatek/build/Makefile:13: *** TARGET_PRODUCT/PROJECT is not set.
I have copy the miss directory into acer kernel but i have this problem.
Where i must set target product for you?
Click to expand...
Click to collapse
you should enter PROJECT parameter.
e.g. make PROJECT=jrdsh15_td_ics
legale said:
you should enter PROJECT parameter.
e.g. make PROJECT=jrdsh15_td_ics
Click to expand...
Click to collapse
Ok good.....
but now the problem is missing directory mediatek/build and custom for acer liquid gallant duo......
jrdsh15_td_ics is for alcatel device not for my phone....:crying:
I have send email to mediatek for this.
legale said:
you should enter PROJECT parameter.
e.g. make PROJECT=jrdsh15_td_ics
Click to expand...
Click to collapse
What About Missing Directoery ?
pradeep_kus said:
What About Missing Directoery ?
Click to expand...
Click to collapse
In the acer source missing some directory into mediatek/
I dont have mediatek/build
mediatek/source
The proprietary driver for acer liquid gallant duo in this two directory......
If i try to make kernel i have error.
I hope mediatek reply my email.
Yeah!
Demeter from china-iphone, complitely compile kernel and working boot.img for Philips W732!
Code:
forum.china-iphone.ru/viewtopic.php?f=31&t=23637&p=894418#p894418
His sourses: https://github.com/Demeterp/w732_kernel_src
So what should be released from Acer to help developers create custom roms, especially jelly bean ones?
jorgoxl said:
So what should be released from Acer to help developers create custom roms, especially jelly bean ones?
Click to expand...
Click to collapse
About Jelly Bean i don't know, but it must help to tune cpu governor (in default cpu works on deep sleep, 166 and 1001, but don't use 250 and 500), may be it help to solve the problems with proximity and light sensors... etc.
In theory you can take JB original sourses from Google and mediatek sources for ICS, and may be you can run JB from other device (for example last firmware from JY G2 MT6575)... But so far no one has yet tried to do it... Sorry for my English
Ok guys!i would appreciate it if you could solve the problem with governor!(ondemand mode 166,250,500,1000)!it works only 500-1000!A new custom rom maybe?thaks!
Sent from my E350 using xda app-developers app
Can this src work to build jb?
Could any help make a ics or jb kernel for the
Alcatel t pop 4010x and does anyone know of a Rom also
Sent from my SK17i using xda app-developers app
Can i used thsi kernel on mtk6575 x401 mobile phone?¿
Can anyone help port this to Alcatel 4010 t pop its spec it mt6575 CPU powervr gpu 512ram 150mb Rom please help also id like to port xperia sytle Rom
Sent from my SK17i using Tapatalk 2
So I dived into the N7100 kernel, and tried a defconfig with Samsung's config. After a couple of setbacks in the form of toolchain related errors, I got it to create a zImage with the NDK/gcc4.4.3. But on booting, I noticed that the capacitative touch keys would no longer work. I'm guessing that I'm missing something in .config.
So where should I be looking in .config and the source tree for code related to the capacitative buttons?
I'm thinking we might work on a collaborative wiki for N7100 kernel source tree.
Samsung didn't share that with ANY of the "note II" variant source drops. However, you can pull the source directory from the i9300 kernel source. I forget the exact path (I'm at work atm), but it's something like drivers/input/keyboard/cypress
Take care
Gary
garyd9 said:
Samsung didn't share that with ANY of the "note II" variant source drops. However, you can pull the source directory from the i9300 kernel source. I forget the exact path (I'm at work atm), but it's something like drivers/input/keyboard/cypress
Take care
Gary
Click to expand...
Click to collapse
You grab it from the n8000 source which is full of updates for our devices. Or check my t889 kernel on github. I put the cypress drivers in a clean commit you can then create a patch from.
garyd9 said:
Samsung didn't share that with ANY of the "note II" variant source drops. However, you can pull the source directory from the i9300 kernel source. I forget the exact path (I'm at work atm), but it's something like drivers/input/keyboard/cypress
Take care
Gary
Click to expand...
Click to collapse
Except the HK source?
I was just looking into your git and found cypress in your initial commit and that you'd actually based the git on the HK source drop.
I untarred the HK source and found cypress there too. What did Samsung think? That international users could do without the capacitative buttons?
Edit: Compiled without a single error. Thank you.
Droidzone said:
I was just looking into your git and found cypress in your initial commit and that you'd actually based the git on the HK source drop.
Click to expand...
Click to collapse
You quoted me in that response... but I don't have any HK source drops in my github. The only Note II source drop I have is the SGH-i317 drop (and it's missing the cypress drivers as well.) Hmm..
garyd9 said:
You quoted me in that response... but I don't have any HK source drops in my github. The only Note II source drop I have is the SGH-i317 drop (and it's missing the cypress drivers as well.) Hmm..
Click to expand...
Click to collapse
lol..Sorry, I must've confused your repo with someone else's.
Anyway, check out the HK N7100 repo. It is complete and is about 10 MB more than the international stuff.
Droidzone said:
Except the HK source?
I was just looking into your git and found cypress in your initial commit and that you'd actually based the git on the HK source drop.
I untarred the HK source and found cypress there too. What did Samsung think? That international users could do without the capacitative buttons?
Edit: Compiled without a single error. Thank you.
Click to expand...
Click to collapse
Hi I'm having your problem, I'm download kernel source's and try bulding my First kernel for Gt N 7102, workinkg all except touchkeys.
Help me ?
Thanks bro
Sent from my GT-N7102 using Tapatalk 2
Did you use the HK source? What's the error?
Edit: Missed the N7102 part. See if cypress is present
Code:
cd /pathto/kernel
find . -iname cypress -type d
Droidzone said:
Did you use the HK source? What's the error?
Edit: Missed the N7102 part. See if cypress is present
Code:
cd /pathto/kernel
find . -iname cypress -type d
Click to expand...
Click to collapse
In original samsung source's cipress is not present but, I'm download from other source and insert in the correctly tree.
I'm modify kconfig file.
Try make menuconfig and cipress comparte to device input-->keyboard.
Make and install new kernel but touch keys not working.
Excuse my English and 'horrible.
Emblema said:
In original samsung source's cipress is not present but, I'm download from other source and insert in the correctly tree.
I'm modify kconfig file.
Try make menuconfig and cipress comparte to device input-->keyboard.
Make and install new kernel but touch keys not working.
Excuse my English and 'horrible.
Click to expand...
Click to collapse
Check your makefiles, and see that cypress has been asked to build.
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
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.