[KERNEL-3.4.67] MT6589 / MT6589M / MT6589T

Search This thread
By:
Advanced…
m@nish123

m@nish123

Senior Member
Aug 17, 2013
594
2,190
Mumbai
mmx a110q {canvas 2 plus}
stock source nt there

Sent from my Micromax A110Q using XDA Premium 4 mobile app
 
luckasfb

luckasfb

Senior Member
Oct 7, 2012
168
110
And what about working builded modules for video-card?

Sent from my GT-I8160 using XDA Premium 4 mobile app
 
Dr-Shadow

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
luckasfb said:
And what about working builded modules for video-card?

Sent from my GT-I8160 using XDA Premium 4 mobile app
Click to expand...
Click to collapse

They work ;)

See my build.sh, I found how to reduce size of modules
https://github.com/Dr-Shadow/android_kernel_mt6589/blob/master/build.sh#L18

See my Makefile too, I found how to prevent modules being compiled with debug stuff
https://github.com/Dr-Shadow/android_kernel_mt6589/blob/master/Makefile#L8

(one of the reasons is here : https://github.com/Dr-Shadow/androi...rm/mt6589/kernel/drivers/gpu/pvr/Makefile#L35)
 
  • Like
Reactions: Geek-DROID and kashifmin
KopiJahe

KopiJahe

Senior Member
Jun 25, 2010
768
452
Pasuruan
I wish you all the luck in the world on this project :D

So, can we enable certain disabled features (like OTG, even if it'll need external power like nexus 4), or add more governor and scheduler, or add new features (while I don't like it, but there's so many people asking about LG's "knock-on" feature)?

And will it be usable on stock rom?

Sorry if this sound noobies
 
  • Like
Reactions: St3ve32
Dr-Shadow

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
awaaas said:
I wish you all the luck in the world on this project :D

So, can we enable certain disabled features (like OTG, even if it'll need external power like nexus 4), or add more governor and scheduler, or add new features (while I don't like it, but there's so many people asking about LG's "knock-on" feature)?

And will it be usable on stock rom?

Sorry if this sound noobies
Click to expand...
Click to collapse

Yes this should possible to activate disabled features with conditions : OTG needs GPIO information (and board should be compatible), for governor and/or scheduler it needs some work as the actual governor is hotplug and this is not a common one.
 
  • Like
Reactions: KopiJahe
Dr-Shadow

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
Update :

Switch to arm-eabi-4.7
Enable some optimizations
Fix kernel config generation
​

Update for Oppo R819 - still a WIP :

Ported all modifications in kernel source
Porting drivers (structure is really different, it will be complicated...)
​

Update for Wiko - still a WIP :

Starting soon for Wiko Cink Five (diff is done)
​
 
  • Like
Reactions: deyv and ct_moi
arnabbiswasalsodeep

arnabbiswasalsodeep

Senior Member
Jan 26, 2013
461
403
Mumbai
I know you won't support overclocking but try to include mtk6589t too. They only have an OC'ed kernel AFAIK

Also a question-
If the kernel version is 3.4.5 which is already good for Kit Kat (moto G has 3.4.11 I guess) so shouldn't we focus on kit Kat building (getting the original sources first) and then the kernel after the kernel is outdated

Press :highfive: thanks :good: if helped
 
KopiJahe

KopiJahe

Senior Member
Jun 25, 2010
768
452
Pasuruan
arnabbiswasalsodeep said:
I know you won't support overclocking but try to include mtk6589t too. They only have an OC'ed kernel AFAIK

Also a question-
If the kernel version is 3.4.5 which is already good for Kit Kat (moto G has 3.4.11 I guess) so shouldn't we focus on kit Kat building (getting the original sources first) and then the kernel after the kernel is outdated

Press :highfive: thanks :good: if helped
Click to expand...
Click to collapse
But, if the kernel is so messed up, porting a rom will be so much harder, I guess
 
Dr-Shadow

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
awaaas said:
But, if the kernel is so messed up, porting a rom will be so much harder, I guess
Click to expand...
Click to collapse

This kernel is compatible with CM11 and Ominrom (which is kitkat too)

This kernel is initially for MT6589T (Faea F2S) - The OC is encoded somewhere in the phone ;)

This kernel is a fake 3.4.5 ^^

The real base version is 3.4.0 with some merged commits (not all).
 
Last edited:
KopiJahe

KopiJahe

Senior Member
Jun 25, 2010
768
452
Pasuruan
Dr-Shadow said:
This kernel is compatible with CM11 and Ominrom (which is kitkat too)

This kernel is initially for MT6589T (Faea F2S) - The OC is encoded somewhere in the phone ;)

This kernel is a fake 3.4.5 ^^

The real base version is 3.4.0 with some merged commits (not all).
Click to expand...
Click to collapse
I mean the original stock kernel is messed up, not this :)
 
Dr-Shadow

Dr-Shadow

Inactive Recognized Developer
Sep 15, 2013
454
560
NANTES
Update :
Add options for 'cat /proc/config.gz' to run
Add mediatek-configs to default dependency in Makefile so config is generated everytime we build with make
Add the ability to append mtk header to zImage through Makefile so we don't need to mkimage (it's done automatically)​

This update is simplifying build process
 
  • Like
Reactions: acuicultor, EnerJon, kashifmin and 2 others
anonimo95

anonimo95

Senior Member
Mar 25, 2011
236
86
Dr-Shadow said:
Update INFO :
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)​
Click to expand...
Click to collapse

So what if we could spoof the thing that gets the values from the board? It reads from the board, but i imagine its kind of software.. just curiosity
 
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
570K
H
hamcam423
yuweng
  • Locked
[TUT] [TOOL] MT65xx ROM Porting
Replies
2K
Views
791K
justmpm
justmpm
superdragonpt
[RECOVERYs] [ROMs] [UNLOCK BL] ASUS Memo Pad HD 7 (me173x) [MT8125] [MULTILANG]
Replies
2K
Views
1M
D
davidsummers
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