Hi,
I was working since a while on this :
android_kernel_mt6589
For releases (beta builds - maybe unstable/not working), see here
I'm trying to support other devices too. Please send me your mt6589 device name and his kernel source (stock source !!)
Actual features :
Built commit history (patches cherry-pick from AOSP inside mtk kernel)
Mtk generate&build scripts moved into kernel directory
Merging meditatek sources (some devices will benefit from others kernel changes)
Removed a lot of unusued debug
Cortex A7 Optimizations + NeonV2 + FPV4
Built with sabermod (4.8.3) arm-eabi 4.8
Can be used into Omnirom build process (kernel and modules)
Future releases :
Support for multiple devices
Mtk commits for kernel source (with comments or docs)
Improve mediatek source ?
Suggestions welcomed
Supported devices :
Faea F2S
Requested devices :
Oppo R819 - WIP
Wiko (MT6589 devices) - need check for GPL compliance (OTA and updates on kernel source)
Lenovo P780 - need check for GPL compliance (OTA and updates on kernel source)
ZTE V967S - need check for GPL compliance (OTA and updates on kernel source)
Acer Liquid E2
Requested devices but no stock sources :
Xolo Q800 - need GPL compliance
Micromax A116 - need GPL compliance
Info about compatibility :
Kernel should be compatible with MT6589/MT6589M/MT6589T because the OC is hardware dependent (it gets the values of the board to detect which generation it is)
What I won't do :
Support overclocking for MT6589/MT6589M to act like MT6589/MT6589T
XDA:DevDB Information
[KERNEL-3.4.67] Source for MT6589 / MT6589M / MT6589T, a Kernel for the Android General
Contributors
Dr-Shadow
Kernel Special Features: Full source for kernel with commit history
Version Information
Status: Stable
Stable Release Date: 2014-03-04
Created 2014-03-04
Last Updated 2014-04-13
Reserved
So I implemented a way to build easyly the kernel
All you need is repo, git and dependencies as described here : https://github.com/Dr-Shadow/android_kernel_mt6589_manifest
So if you want to build latest kernel from my git :
For Faea F2S : ramdisk from stock ROM - almost stock kernel should be "stable"
Code:
repo init -u https://github.com/Dr-Shadow/android_kernel_mt6589_manifest.git -b master
cd kernel
./build.sh
For Oppo R819 : ramdisk from stock colorOS stable (V1.0.0i 140120) - BETA
Code:
repo init -u https://github.com/Dr-Shadow/android_kernel_mt6589_manifest.git -b r819-release
cd kernel
./build.sh
Next branch (released) :
For Faea F2S : ramdisk from stock ROM - BETA real 3.4.67 (should be stable)
Code:
repo init -u https://github.com/Dr-Shadow/android_kernel_mt6589_manifest.git -b devel-upstream
cd kernel
./build.sh
I improved the build.sh like this, you don't need to worry about vars and others.
Reserved
Any help is welcomed for this kernel tree.
What you can actually do :
Check if you can compile actually suported devices
Do pull requests to add devices or drivers
Check changes between your original stock source of your device
Adapt configuration files (Remove drivers not added or not working, add missing var)
Create a build script with a var for TARGET_PRODUCT which would be able to check env, build kernel and modules to out/ (my build.sh is a example for e960 - Faea F2S)
Actually, I'm merging Oppo R819 sources and I saw there was differences on mediatek drivers (some things were added by Oppo)
For example, I got this diff :
https://docs.google.com/document/d/1OGQS_HWRG9LbSiBCwWilKIQ-Wo_Asbz49IREXeZFJEA/edit
So for merging I'm replacing VENDOR_EDIT by OPPO_R819 so when kernel is compiling it should be able to keep Oppo changes only for Oppo R819 (thank you preprocessor for your hard work).
Of course, I'm not merging debug stuff.
The other idea would be to create documents, to document a specific change between another mtk source like those changes :
https://docs.google.com/document/d/15Bexb9ytPsYbvwo871u0mifmh9NqDJd6Oo1rXZiDiCg/edit
The focus of doc would be to show if the changes would be interesting for system part (better app for photos for example)
Example of new var introduced by recent mtk source (MAIN_SENSOR_ROTATE_DEGREE_X see config files) :
https://github.com/Dr-Shadow/androi...hal/camera/camera/cfg_setting_imgsensor.h#L52
Ok this is for hal but it's still interesting to check changes and this is actually my focus.
Awesome
You finnaly got the time to released it
:good:
Kernel source code Acer E2 Duo v370:
http://global-download.acer.com/GDF...E2&Step3=V370&OS=ALL&LC=fr&BC=ACER&SC=EMEA_13
Extracted kernel:
https://www.mediafire.com/?anywf4e9d1mb755
That's what you want?
I'm starting with the kernels ...
Matx13 said:
Kernel source code Acer E2 Duo v370:
http://global-download.acer.com/GDF...E2&Step3=V370&OS=ALL&LC=fr&BC=ACER&SC=EMEA_13
Extracted kernel:
https://www.mediafire.com/?anywf4e9d1mb755
That's what you want? :good:
Click to expand...
Click to collapse
Thank you for your sources
I will reconsider working on this device if Acer updates the kernel source (I got a discussion for it with Acer - need some time to find a solution).
There is a working kernel by @kashifmin, please check his gitrepo : http://d-h.st/zdN
Device : Micromax A116
this kernel have few bugs.
eagledipesh said:
There is a working kernel by @kashifmin, please check his gitrepo : http://d-h.st/zdN
Device : Micromax A116
this kernel have few bugs.
Click to expand...
Click to collapse
Yes but this is not a stock source.
Dr-Shadow said:
Yes but this is not a stock source.
Click to expand...
Click to collapse
Great work sir. Check your pm for stock source links
I see that you cherry picked many commits but still can you provide a Changelog (With Major changes from Stock MTK Kernel and Features )
This will help me atleast for development of kernel for other MTK Chipsets
Btw Great work i always like development and i also bought a MTK Phone based on MT6572
I suppose these are from the THL W8:
https://github.com/C3C0/MT6589_kernel_source
Adding the iOcean X7 woukd be nice, but I think sources aren't available..
GuneetAtwal said:
I see that you cherry picked many commits but still can you provide a Changelog (With Major changes from Stock MTK Kernel and Features )
This will help me atleast for development of kernel for other MTK Chipsets
Btw Great work i always like development and i also bought a MTK Phone based on MT6572
Click to expand...
Click to collapse
I think you didn't understand what I have written ^^
I cleaned kernel of debug and added the commits MTK injected in kernel so it's like stock mtk kernel with few changes and fixes (android binder for example).
Dr-Shadow said:
I think you didn't understand what I have written ^^
I cleaned kernel of debug and added the commits MTK injected in kernel so it's like stock mtk kernel with few changes and fixes (android binder for example).
Click to expand...
Click to collapse
gotcha sorry for incovience created by first Page moreover have you tried Dynamic Fysnc Control by Faux123 that is nice and any way to update source with the mainstream updating source ?
GuneetAtwal said:
gotcha sorry for incovience created by first Page moreover have you tried Dynamic Fysnc Control by Faux123 that is nice and any way to update source with the mainstream updating source ?
Click to expand...
Click to collapse
Yeah I should be able to update with mainstream updating source and it should be easier than mtk stock kernel as I fixed a lot of whitespaces, useless comments and others (around 400 or more files).
Actually I'm porting oppo R819, it will introduce some new features which could be interesting
Device : Micromax Chd A116
Kernel Source stock link : Updating...
Kernel Source Modified (kashifmin) : ADDED
Dr-Shadow said:
Yeah I should be able to update with mainstream updating source and it should be easier than mtk stock kernel as I fixed a lot of whitespaces, useless comments and others (around 400 or more files).
Actually I'm porting oppo R819, it will introduce some new features which could be interesting
Click to expand...
Click to collapse
Hmm Now i got it thats why the source was very smooth as earlier in Novem. i tried to compile Oppo kernel source and it compiled with no probs but your source is very smooth with some(actually many) warning but no Errors with the default drivers but when i introduced other phone's config and drivers it gave errors in aee :/ but will fix that
Thanks for Awesome Work will try and help by adding commits after my exams
Hey
Alcatel One Touch Hero (OT-8020D) / TCL Hero N3 (Y910)
This is supposedly the sauces.
SourceForge link (this will start the download automatically, sorry about that. Is a huge tar! :/
Update : Add support for GSLx680 touchpanel driver for Faea F2S
I have the Elephone P8, any support for this phone?
Sent from my P8 using xda app-developers app
bmw2k1 said:
I have the Elephone P8, any support for this phone?
Sent from my P8 using xda app-developers app
Click to expand...
Click to collapse
Hi
When requesting, do it with your phone stock kernel sources please
If you don't own kernel sources for your device, there's nothing he can do.
Regards
Hi, i have a ZTE Device v8200+ (Qualcomm msm8625, 512Mb Ram, 4",8mpx Main camera, 0.3 front camera android 4.0.4, Kernel version 3.0.21) (released in Venezuela)......
I wants to know if i can port a cyanogenmod rom or another rom (JB, KK) with my stock kernel (3.0.21)...Can i?
Hi Rvrjei,
Yes you can use a prebuilt stock kernel with some modifications to run CM on your device.
I've done a quick search on Github for your chipset and found quite a few hits, check it out!
Here are a few links to start building Cyanogenmod and setting up the device tree:
How To Port CyanogenMod Android To Your Own Device
[ULTIMATE GUIDE] [A-Z] Using Android Source Code/ How to Compile
[NOOBFRIENDLY] [HOWTO] Create a device tree for MTD devices
Cheers!
Hello XDA Developers
I Wanted To Ask about something confusing
Now To Build An AOSP ROM You Need The Source Code OF The Phone
What I Wanted To Know What's The Difference Between Device Tree And Vendor
And Last Thing If My Phone Running Kernel 3.4.67 Can I Change It To Be Like 3.10.72 (If There's A Source Available )
Sorry For Asking But I Haven't Seen How The Source Looks Like And Thanks In Advance :good::laugh:
I have a BLU Energy X 2 running the MT6580 chipset, with kernel version 3.10. I was looking into porting CyanogenMod12.1, however there is no device tree, as the kernel version is not updated enough. Is it still possible to port the ROM? I also don't have the vendor tree, how would I get that?
Thanks, Nate
NateDev473 said:
I have a BLU Energy X 2 running the MT6580 chipset, with kernel version 3.10. I was looking into porting CyanogenMod12.1, however there is no device tree, as the kernel version is not updated enough. Is it still possible to port the ROM? I also don't have the vendor tree, how would I get that?
Thanks, Nate
Click to expand...
Click to collapse
Hello,
You need to generate the blobs for the vendor. Also you need a working device tree and kernel for it.
You can refer here Guide to Port MTK Roms for more information.
Regards
Vatsal,
Forum Moderator.
Can anyone help me find my device source tree.... I have "10.or G" i couldn't find it... I am confused now .... What should i do?
Kernel sourse for this device has been released for nougat.... How can i use it to build roms based on oreo... Or even recovery?
I am a noob in developing roms .... I have some knowledge of flashing and using them... Now i want to develop my own since this device has no developers . Also ,no information on github(device source tree )
Device info:
SoC: Snapdragon 626
Sources available : android nougat kernel source code
Current android os : android 8.1
Treble support : no
Any help will be appreciated