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
Hey devs. I've worked with some ROMs and now I'm willing to port Blisspop ROM for my device. And all I have is the official kernel source, AOSP device source codes and some vendor codes using scripts. Now my questions are:
1. Are these data enough to start building the ROM?
2. I tried it using AOSP and CyanogenMod 5.1.1r3. But I always keep getting some files missing or compiler issues.
3. How do I apply patches from a URL?(I'm not fond of git)
4. Any link to a tutorial can be provided.
Additional info:
I'm working on Ubuntu 14.04 x64 LTS in VirtualBox.
Allocated 4 cores and 4gb RAM.
I'm porting it to an x86 arch device.
VHD size is 400gb.
And the kernel source is said to work with AOSP 4.4.2 though it functioned will with AOSP 5.1.1r3.
Also I followed several guides but most of them are for arm devices. And did not workout for me.
Kindly help me out guys.
As title is saying, nothing less, not much more.
Samsungs official source can be optained on github
https://github.com/ASKSAP/android_platform_samsung_a32x.git
https://github.com/ASKSAP/android_kernel_samsung_a32x.git
I've created partially working dev tree using https://github.com/SebaUbuntu/TWRP-device-tree-generator
Available at
https://github.com/netbospl/android_device_samsung_a32x.git
Lookng forward to read what You think about this.
Unpackbootimg that I've used and is/was working was compiled from
https://github.com/osm0sis/mkbootimg
Source was release for A326U variant by Samsung, so I've uploaded it to github.
A326USQU1AUCF/A326USQU1AUD4 - SM-A326U_NA_RR_Opensource
GitHub - netbospl/android_kernel_samsung_a32xu: A326USQU1AUCF/A326USQU1AUD4 Samsung provided kernel Source SM-A326U_NA_RR_Opensource.zip
A326USQU1AUCF/A326USQU1AUD4 Samsung provided kernel Source SM-A326U_NA_RR_Opensource.zip - GitHub - netbospl/android_kernel_samsung_a32xu: A326USQU1AUCF/A326USQU1AUD4 Samsung provided kernel Source...
github.com
GitHub - netbospl/android_platform_samsung_a32xu: A326USQU1AUCF/A326USQU1AUD4 Samsung provided platform source SM-A326U_NA_RR_Opensource.zip
A326USQU1AUCF/A326USQU1AUD4 Samsung provided platform source SM-A326U_NA_RR_Opensource.zip - GitHub - netbospl/android_platform_samsung_a32xu: A326USQU1AUCF/A326USQU1AUD4 Samsung provided platform ...
github.com
Is anyone here knowlage-able in Andorid building process that's willing to walk through my out images for PitchBlack Recovery and AOSP R/11 images??
If there is no red flags, I should be able to do same for A32XU/A32XU1
Edit: also please note that device tree on my repo is not up to date/that I've used to successfully build AOSP, master should be fine for PitchBlack CWM A326B, and that's where I'll intentionally leave it for now
You got that AOSP ROM ready yet?
Good
I'm new to the android build system but have been running stripped kernels for years. I'm working on a custom rom for a TCL A30 (MT6762/MT6765).
I've looked at the AOSP code base and TCL source, for a similar device, and it looks like the TCL source generates the needed kernel .config file with scripts. There are multiple scripts for different archs and cellphone carriers. My TCL A30 has a Bangkok_CC (ConsumerCellular) tag and I found arch/arm64/configs/bangkok_TF_defconfig (TracFone). There do not appear to be any patches in the TCL source. The source I found:
TCL-Mobile on sourceforge
Has the Tracfone TCL A3:
Tracfone TCL A3x product link
That source contains Bangkok_TF_defconfig.
I was able to adb pull /proc/config.gz directly from the device and it's running 4.19.126+ released last month.
First question: Can I generate a bangkok_CC_defconfig from /proc/config.gz in the AOSP code base? It is mosttly monolithic
Code:
cat .config | grep =m > kernel_modules.txt
CONFIG_IKHEADERS=m
CONFIG_TCP_CONG_WESTWOOD=m
CONFIG_TCP_CONG_HTCP=m
CONFIG_SERIAL_OF_PLATFORM=m
CONFIG_BATTERY_MT6359=m
CONFIG_SND_SOC_MT6359_ACCDET=m
CONFIG_USB_DUMMY_HCD=m
CONFIG_MMC_SDHCI=m
CONFIG_MMC_SDHCI_PLTFM=m
CONFIG_MMSTAT_TRACER=m
At the time of this post the latest upstream is 4.19.244
Second question: Are most Android projects like Debian/RHEL where they back patch kernel vulnerabilites? Would the most up-to-date kernel result from the latest AOSP source and would building it just be a matter of dropping in my /proc/config.gz and setting the build environment that I found in the TCL source?
I suspect that AOSP is contributing back to kernel.org. Third question: AOSP vs Kernel.org source? Does Google backport like RHEL/Debian? Or would I get a more recent,, secure kernel using upstream kernel.org source?.
Last question Clang vs GCC. I've just setup my Arch Linux build box w/ arm64_gcc. Speed is less important to me than stable builds. What are the arguments for one compiler over another?
After reading about the fast kernel source release for the Xiaomi 12 and Xiaomi 12 Pro one could think that xiaomi did a good job at complying with the GPL v2 license and providing useful sources for developers of custom kernels. But appearances are deceiving: The provided kernel sources are incomplete and partially broken.
The most important issues are that xiaomi pushed incomplete devicetree sources which are neither provided by qualcomm anymore unfortunately and the touchscreen drivers are really out of date which leads to broken double tap to wake and under display fingerprint sensor. Additionally building the kernel isn't as trivial as it sounds anymore since many kernel modules are built outside of the kernel tree now.
During the past days i have spent some time on getting a source built kernel including modules and devicetree running on Xiaomi 12.
I have sucessfully booted the kernel and uploaded this work to github.com/xiaomi-sm8450-kernel.
Using this manifest one is able to compile the OSS kernel for Xiaomi 12 and Xiaomi 12 Pro.
I hope that this can help other developers working on the Xiaomi 12 and Xiaomi 12 Pro!
For instructions to build the kernel and more details about missing sources please refer to the manifest on github.
Note that double tap to wake and fingerprint sensor don't work as is on the stock ROM.
Also note that the OSS display-devictree for Xiaomi 12 Pro is missing the configurations for some referesh rates which were supported on MIUI. This could be dumped and included from the stock dtbo.img with some effort.
If you encounter issues with this OSS kernel feel free to ask me and i will give my best to help.
To finish this thread i want to draw further attention to the fact that this is not a one-time issue with the OSS kernels for Xiaomi devices and the situation seems to get even worse. The newer Redmi K50 gaming got kernel sources which don't include any external respositories, as in no techpack drivers and no devicetree sources at all. The new Xiaomi 12S series still has not seen any open source kernel release.
I hope this project helps to set a better starting point than the xiaomi oss release to other developers for the Xiaomi 12 and Xiaomi 12 Pro.
Thanks for thus clarification Arian. Sad story....To be continued... Quo Vadis Xiaomi?
ti think the xiaomi 12 has suffered a performance squeeze... this is not because of the heat.... i have tried thermal unlocking and overclocking the CPU GPU and updating the driver 617 the result shows the real performance is vastly different many
Can you tell me which version of clang can be used to build the kernel from the sources for lineageos 20? And which commands to use? I would like to build a kernel for Kali Nethunter, but when using any of the defconfig I get compilation errors
Can you explain how to flash built kernel..? I built the kernel and I get the kenrel image but I don't know how to flash it to the device...
Would you know if this is also the case for Mi11 Ultra tree?
The OSS for the 12S and 12S Pro has just been released recently if anyone is interested in looking at it:
GitHub - MiCode/Xiaomi_Kernel_OpenSource at mayfly-s-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
I would be interested to hear if the kernel source for the 12S family is also incomplete, like the regular Xiaomi 12 series
pj_ said:
Can you explain how to flash built kernel..? I built the kernel and I get the kenrel image but I don't know how to flash it to the device...
Click to expand...
Click to collapse
You need to pack the boot, vendor_boot, vendor_dlkm and dtbo images, the easiest way is to do that within the LineageOS tree.
KeepingKeyes said:
The OSS for the 12S and 12S Pro has just been released recently if anyone is interested in looking at it:
GitHub - MiCode/Xiaomi_Kernel_OpenSource at mayfly-s-oss
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
I would be interested to hear if the kernel source for the 12S family is also incomplete, like the regular Xiaomi 12 series
Click to expand...
Click to collapse
Yes, unfortunately this devices source situation is even worse. On all the recent releases xiaomi did not release the audio, display and camera drivers. The released touchscreen driver does not compile either, though i fixed that by guessing and the driver works now: https://github.com/xiaomi-sm8450-ke...3b9d0f69ecd2ba01674a0dc29cfdc86782bb7c9d6c3da