[KERNEL-3.4.67] MT6589 / MT6589M / MT6589T

Search This thread
By:
Advanced…
Dr-Shadow

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
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
 
  • Like
Reactions: HusinSam, akbariajay, Mr.Ak and 52 others
Dr-Shadow

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
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.
 
Last edited:
  • Like
Reactions: madhavpokharel, Skolotaie, cadicvn and 7 others
Dr-Shadow

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
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.
 
Last edited:
  • Like
Reactions: Mr.Ak, Skolotaie, cadicvn and 3 others
Dr-Shadow

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
  • Like
Reactions: baran0119, fvpo, ahmyani and 3 others
GuneetAtwal

GuneetAtwal

Senior Member
Oct 6, 2012
2,421
5,327
27
Mohali
OnePlus 7T
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 ;)
 
Dr-Shadow

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
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).
 
  • Like
Reactions: hoanbt
GuneetAtwal

GuneetAtwal

Senior Member
Oct 6, 2012
2,421
5,327
27
Mohali
OnePlus 7T
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 :p 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 ?
 
Dr-Shadow

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
GuneetAtwal said:
gotcha :p 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 :)
 
GuneetAtwal

GuneetAtwal

Senior Member
Oct 6, 2012
2,421
5,327
27
Mohali
OnePlus 7T
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 ;)
 
TheDeadCPU

TheDeadCPU

Retired Senior Moderator
Jun 22, 2009
1,945
690
30
ಠ_ಠ
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! :/
 
B

bmw2k1

Senior Member
May 21, 2007
131
7
I have the Elephone P8, any support for this phone?

Sent from my P8 using xda app-developers app
 
You must log in or register to reply here.

Similar threads

bgcngm
[ROM][18-12-2013] ZTE V987 (MT6589) custom ROMs (JB)
Replies
2K
Views
571K
H
hamcam423
yuweng
  • Locked
[TUT] [TOOL] MT65xx ROM Porting
Replies
2K
Views
792K
justmpm
justmpm
superdragonpt
[RECOVERYs] [ROMs] [UNLOCK BL] ASUS Memo Pad HD 7 (me173x) [MT8125] [MULTILANG]
Replies
2K
Views
1M
k1dehner
k1dehner
kumar abhishek
[TUT] Instructions MTK6577 USB VCOM Driver Installation
Replies
67
Views
746K
Y
youthhustle
superdragonpt
[ROM] [ 7.1.1 | 7.1.2 ] Official madOS - Vernee Apollo Lite [MT6797]
Replies
3K
Views
546K
daitalos
daitalos

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 55
    Dr-Shadow
    Dr-Shadow
    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
    View
    10
    Dr-Shadow
    Dr-Shadow
    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.
    View
    7
    Dr-Shadow
    Dr-Shadow
    Guys, you are "spamming" my thread with requests actually ! This should be a dev discussion.

    For requests you can MP me (I'm replying to most of them - or replying in concerned thread).

    I'm not going to support "clones" or "rebranded" phones if manufacturer is not releasing the kernel source (this is GPL rules).

    So if you ask to support MMX A116, Xolo Q800 or others which have no kernel source from manufacturer itself (not another manufacturer), it won't be my priority and I will maybe never support those phones (I'm working on Omnirom for MT6589 phones too so I have a lot of work scheduled).

    Maybe you think it's easy to support those "clones" because kernel work on both phones (for example : wiko cink 5 and MMX A116) but there is kernel changes which are impossible to check without source (for example : best support of different sensors at same time for mtk drivers - see oppo R819 kernel source).

    For others phones (with manufacturer source) : I'm surprised to see people coming, sending requests and no one trying to send patches, reviews, docs about diff (see post #2). I'm not asking a "big work".
    View
    6
    Dr-Shadow
    Dr-Shadow
    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.
    View
    6
    Dr-Shadow
    Dr-Shadow
    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).
    View

New posts