Database Info

[Kernel] MediaTek MT6575 3.0.13 Kernel Sourses

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

[TUTORIAL] Everything You Need to be a Kernel Dev

Welcome everyone, I was asked by a friend from my old slice of XDA to write kernel tutorials on everything I know about them. So, here we are!
First, you MUST learn C coding. It is not hard, once you begin; XDA Senior member mhrsolanki2020 has written a tutorial for it here on XDA.
So now that we know C, lets try basic step one. We need to compile it!
Go to this tutorial I have written here to learn how to do that. To compile a kernel for your device if you don't own the one v just get your own source, and then use your own defconfig. You will be golden from there.
What do we plan on teaching
Compiling of the source
Making a boot.img for your device
Use fastboot to test your kernel
Debugging the kernel
Using ADB to your advantages
Trick of the fastboot-fu
All about a ramdisk
Adding drivers
More?? You tell me

RESERVED

Reserved for tools

[Question] Kernel Compilation for Modules

First post in the Dev section but this seemed to be the place to talk about kernel compilation and module development.
I have twice now, and am working on my third kernel compilation for the purposes of custom module building for the TF700 and the TF201.
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all. Is this normal for kernel compilations? I would have thought that it would be fully compilable out of the box ( so to speak). Is it ASUS or just android/Linux in general that works out this way?
Is there a better way to do it? Should I use some generic source with the same version numbers? The current source is just not working at all. I am using an Ubuntu distro. Have the cross compile tools etc... but it just fails. I have already resolved two missing definition references and it just keeps on failing in new places
Hopefully this question doesn't offend developers. I have moved from WinPhone to here and want to better my understanding of how this should all work but need to start with some basics before I can make a meaningful contribution.
Thanks.
P.S... I looked and didn't find a "Compiling android kernels for dummies" book

hx4700 Killer said:
I looked and didn't find a "Compiling android kernels for dummies" book
Click to expand...
Click to collapse
"Dummies" doesn't write a book on kernel dev. Too wrapped up in telling people how to download iTunes.....
Use your "Google". And when you find it, Google XDA University.
There, you will find steps for setting a build environment and kernel and cross arm.
Understand, all kernels are different, but a good place to start. Plus, you learn how to use Google. An added bonus.
Oh... and... as an extra bonus, I will move this to Q & A, as this post has no development work attached. :silly:
MD

My question wasn't HOW to cross compile. I have done it.
My question is WHY are there so many errors that need correcting when compiling the ASUS downloadable kernels and if this is typical of the source from any device or just ASUS?

hx4700 Killer said:
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all.
Click to expand...
Click to collapse
I had to fix exactly one pair of quotes vs. angle brackets somewhere in the RIL - get the patch pack from my kernel and apply the ril include fix. Then it should compile. If not, you are doing something wrong.

Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou

alexcass4 said:
Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou
Click to expand...
Click to collapse
Step 1: Get a suitable ARM toolchain. I can't help you here with Ubuntu because I'm using Gentoo and their crossdev tool (http://www.gentoo.org/proj/en/base/embedded/handbook/?part=1).
Step 2: Cross-compiling the kernel works just as for native kernels (make menuconfig, make), but you have to pass parameters to each make, e.g. make ARCH="arm" CROSS_COMPILE="arm-gentoo-linux-gnueabi-" (or whatever your toolchain is called)
Step 3: For the TF700-specific blob stuff I have written a detailed tutorial here: http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4

[Q]Porting MT6582 to MT6572

Hello Guys,I searched for Lewa Os 5 for MT6572 but I didn't find any.So,I thought to download MT6582 as these chips are in combination like MT6589 to MT6577.I downloaded Wiko darkmoon . @superdragonpt created or ported it.I want it for my use,If got successful then I will take permission from him.I patched the rom with my stock files.The updater-script was just fine with exactly same mount points as in my Xolo A500s.I unpacked boot.img with michfood's packing and unpacking tools ,but the thing that I am worried is the boot.img of 6 mb shrinked to 4 mb!I just edited init.rc and added bootclasspath of lewa.
But,it didn't boot.I think I need to replace my ram disk in my boot with wiko dark moon's boot ram disk.Could I port this way?
Is it possible to port MT6582 to MT6572?It's my first time of cross-porting.
Please,I need some help on this!

Hi
A: Rom was built from scratch ( not an port ), i used LeWa patchroom ( just like MIUI's patchroom).
LeWa patchroom is Closed Source (proprietary) so i can't help you with that
B: You should be able to "port" it to your device, concerning kernel:
- Use ( mandatory) LeWa's ramdisk
- If your kernel after repack is smaller, thats rather normal , its just an question of compression %.
Also since we are talking about port of diff SoC's there are other things that you'll need to fix:
- SoC ID on updater-script; ramdisk: build.prop; etc.
- Also keep in mind that LeWa itself its an themed rom, so its uses an 2nd framework ( lewa-res) that works under the main one, you may need to patch other things in the process.
--> For this, check the MT65xx porting thread, its very usefull.
Regards

superdragonpt said:
Hi
A: Rom was built from scratch ( not an port ), i used LeWa patchroom ( just like MIUI's patchroom).
LeWa patchroom is Closed Source (proprietary) so i can't help you with that
B: You should be able to "port" it to your device, concerning kernel:
- Use ( mandatory) LeWa's ramdisk
- If your kernel after repack is smaller, thats rather normal , its just an question of compression %.
Also since we are talking about port of diff SoC's there are other things that you'll need to fix:
- SoC ID on updater-script; ramdisk: build.prop; etc.
- Also keep in mind that LeWa itself its an themed rom, so its uses an 2nd framework ( lewa-res) that works under the main one, you may need to patch other things in the process.
--> For this, check the MT65xx porting thread, its very usefull.
Regards
Click to expand...
Click to collapse
Thanks for your infomative reply.Ok,I done most the things.Rather than replacing ram disk,I added bootclasspath in init.rc
How can I make lewa from scratch?I haven't heard it before.

Give a try to This
nightwalker said:
Thanks for your infomative reply.Ok,I done most the things.Rather than replacing ram disk,I added bootclasspath in init.rc
How can I make lewa from scratch?I haven't heard it before.
Click to expand...
Click to collapse
Using unpack tool by Michfood unpack your stock boot.img and boot.img of the rom u want to port ... then only replace kernel and kernel header from base to port and repack the image ... and try to flash the rom

navneetasnavi said:
Using unpack tool by Michfood unpack your stock boot.img and boot.img of the rom u want to port ... then only replace kernel and kernel header from base to port and repack the image ... and try to flash the rom
Click to expand...
Click to collapse
I knew it won't work,as I knew that we need to replace ram disk.I did it and I have managed to come till boot anim.

So what ?? At least give a try to the way i suggested It booted up the oppo rom for my device. :/

navneetasnavi said:
So what ?? At least give a try to the way i suggested It booted up the oppo rom for my device. :/
Click to expand...
Click to collapse
Sorry,you were right too.

nightwalker said:
Sorry,you were right too.
Click to expand...
Click to collapse
Did it worked??????
if yes then please press thanx : )

navneetasnavi said:
Did it worked??????
if yes then please press thanx : )
Click to expand...
Click to collapse
Haven't tried it not yet

There were actually lewa OS5 for MT6572. Even OS6 also existed today.
I ported it myself from different SoC.

[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.