[KERNEL-3.4.67] MT6589 / MT6589M / MT6589T

Search This thread

superdragonpt

Recognized Developer
Apr 27, 2013
4,952
19,354
Lisbon / Taiwan / USA
www.caixamagica.pt

DerTeufel1980

Inactive Recognized Developer
Jul 31, 2011
10,368
27,668
There does not seem to be source available for your phone.
Without source its useless to ask in this thread for help
 

shoxxy

Senior Member
Sep 8, 2013
724
1,076
Stadt
Hi @ all

i just saw theres an Asus Memopad HD7 ( MT8125/MT6589 ) kernel update from 16/09/2014 Link

until now I have only build preconfigured Qcom kernels in context with an rombuild.

It would be very very nice, if someone can get a look. for me in my case i need an kernel as small as possible, only needed to get more space for different custom recoveries...


Thx in advance for help

Greetz
 

nefescalanadam

Senior Member
Aug 27, 2012
196
27
İstanbul
Actually gionee devices are not compatibility for custom kernel. Because gionee devices (like gionee e3, General Mobile Discovery) has some custom drivers (i mean like lcm driver)

Bad news..
 

michiil

Senior Member
May 28, 2013
486
262
Salzburg
i tried building for r819 but it doesnt boot.. coud you help me? i am also trying to build omni (after it boots oc :D) and need some help on setting up the device tree.
 

sd_shadow

Recognized Contributor / XDA Welcome Team
Sep 21, 2011
18,972
2
9,989
South Dakota
goo.gl
Motorola Droid X
Amazon Fire
Notice: A New Q & A thread has been created in the Q&A, Help & Troubleshooting Sub-Forum.
New Discussion and Q & A Tabs have also been created, located just under threads Title, when viewing in a Browser.
Posts from members with less than 10 posts will automatically be posted in the new Q & A thread.
Please check it out, and see if you can help out someone with a question about this Topic.
 
  • Like
Reactions: KopiJahe

chiragjn

Member
Mar 2, 2013
33
56
28
Mumbai
Help with kernel issue

I compiled a kernel from Acer e2 sources using Acer e2 ProjectConfig.mk and got it booting on my Xolo q800.
There are many things not working for now,
but main problem is lcd backlight stays on all the time
Xolo Q800's lcm doesn't match acer e2's lcm
Xolo Q800: tm9608_qhd_dsi_cmd_truly
Acer E2 : otm9608a_qhd_dsi_vdo_yunshun

Colors and resolution are all okay and lcm works but backlight stays on.
Any Idea what should I do solve this?
 

ajituchiha

Senior Member
Aug 24, 2014
239
236
24
Kathmandu
I was wondering if we could do something like CAF (what Linux Foundation and bunch of others did for Qualcomm MSM) for MediaTek. We could build a nicely formatted source code repository with support for as many boards and drivers possible. We can also add support for hwcomposers, audio and other HALs as time runs on, for as many boards possible.

I am currently working on my phone powered by a MediaTek MT6572, unfortunately my manufacturer doesn't have the source code themselves, and MediaTek is asking a really big amount of money for that. So, I quite decided myself to explore MT6572 sources published across the web, and to diff them with each other to see what goes where and how.

check this out man https://blukitkat.wordpress.com/mt6572/life-advance-4-0/ they say it is a rom but it is full of kernel. i have downloaded it but i kow nothing about compileing a custom kernel hope it helps you i think this kernel 3.4.67 since it is kitkat i hope you make a kitkat custom kernel soon so i can get away from this 4.2.2
edit : here is 3.4.67 kernel https://github.com/4Fwolf/huawei-u8836d-kernel-3.4.67/blob/master/mediatek/dct/MT6572_NP.fig
 
Last edited:

uinod3

Senior Member
Jun 27, 2014
141
26
Vijayawada
kit kat

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 ;)

Hi sir iam also using MT6589T(Karbonn Titanium x) IT WAS RUNNING AT ANDROID 4.2.2 ONLY i have ported so meany roms which are android 4.2.1 & 4.2.2
what am asking is how to port your kitkat rom can you please provided me the tutorial it will really helpfull to me...
i need to develope kitkat kernal...
please try to understand......

---------- Post added at 05:25 PM ---------- Previous post was at 05:13 PM ----------

Update :
Improved build script (now able to create flashable.zip)

I started beta build for kernel here : http://dr-shadow.eu/release/ (to get latest, just sort by date)

I used those ramdisks (see README) : https://bitbucket.org/Dr-Shadow/ramdisk

If you use another ROM, it's possible that the kernel won't boot because I use specific ramdisks (see above), I'm not using any kernel updater because mtkbootimg repacking is specific (I will check this later).

As always before flashing : BACKUP YOUR ROM

Oppo R819 is BETA : maybe it won't boot, I can't test as I don't own a Oppo R819

Please submit all issues here

Flashable zip are named with $DEVICE_NAME - $KERNEL_VERSION - $GIT_SHORT_SHA1

Be aware that those 3.4.5 are still fake 3.4.5 (this is almost base mtk kernel)

Everyone which want to help, to test, to submit patches is welcome

iam submiting my stock rom which is running at MT6589T
Os : Android 4.2.2
Kernak : v3.4.5
phone : Karbonn Titanium X (mt6589t)
link : http://www.mediafire.com/folde:cryingr/a5js4jvnsmm45/Karbonn_Titanium_X_Stock_Rom
 

Top Liked Posts

  • There are no posts matching your filters.
  • 55
    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
    10
    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.
    7
    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".
    6
    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.
    6

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