Database Info

[source code]MT6577[kernel+ril]

hey guys......good news blu has released source code of its mobile which include mt6577 sources also
here take a look:http://forum.xda-developers.com/showthread.php?t=2650513
lets have some cyanogenmod and slimkat builds......
devsDark4Droid, @superdragonpt, @pratikmore, @bsuhas, @icoolguy1995, @khan_frd2002, @sagarwep, @mmxandy, @andiroxu, @yuweng @SuperDroid-BOND plz devs take a look

Sure MT6577 source is good, but only ICS.
Still its buildable for the Blue Device, you (we) still have to adapt the source to our phones.
But should be an great project.
In the mean time, i prefered to continue on the KitKat project for MT6589..
Regards

superdragonpt said:
i prefered to continue on the KitKat project for MT6589
Click to expand...
Click to collapse
Thanks Alot Sir i Am A Big Fan Of Your ROMs For MT6577... And Now i Own a MT6589 Device... its Good To Hear That You Will Work On Kitkat For MT6589 :victory: i Will Be Desperately Waiting For Your ROM To See in My Device (After Porting)...
Just Wanted To Ask You One Question... Will We Be Able To Use Our Stock JB Kernel 3.4.5 (Swapped Ramdisk) With Your Kitkat ROM? Just Like We Do With Your ROMs For MT6577?

As of now the Omni Rom project for the MT6589:
-kitkat 4.4.2 boots great without bugs
-wifi works (still not fully stable,but works)
-Calls (telephony) finnaly works, but with no sound.
So the worst part concerning framework sources (the Radio Interface Layer), is now being patched with great success.
Concerning your kernel 3.4.5 (BTW that kernel was made by Varun) it will require some patches for KK to work.
As for the rest, only time will tell .
Regards

[KERNEL-3.4.67] MT6589 / MT6589M / MT6589T

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

What to use to build Lollipop for M2 Aqua?

Hi all, I've been having a little hunt around for info on building AOSP 5.1 lollipop for xperia M2 aqua but have only found info and commits, device specifics etc for all other xperia devices apart from the M2 aqua so i'm now at a standstill 'cos I can't work out what's what. From what i've read the M2 aqua's codename is seahawk but the closest in name I found on the sonymobile developer site is seagull and there's no mention or info on seahawk! The only stuff I see on the sony dev site are for the following - amami aries castor eagle flamingo honami leo rhine scorpion seagull shinano sirius tianchi togari yukon , does anyone know where I should be looking or what to use to build 5.1 for m2 aqua? Once I've found the info i'd be willing to set up and build a 5.1 AOSP rom for the device as there isn't much out there for it. Many thanks in advance.

Build it from Eagle branch, that's the original M2

Would that work properly? Reason I ask is 'cos I asked in the Freexperia project thread if their rom can be used as it's a pre built 5.1 from AOSP sources but the message I got back is that it doesn't work on the M2 Aqua and they have an Eagle compiled rom in their lists! I don't fancy spending all that time installing linux, downloading the files etc and then compiling etc just to find out that the Eagle sources don't work.

[Sony] Xperia Open Devices Project

Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/

jerpelea said:
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.
For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.
If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Unified 3.10 kernel sources
https://github.com/sonyxperiadev/kernel
Project git
https://github.com/sonyxperiadev/
Click to expand...
Click to collapse
Awesome. Thanks very much. Yet another reason to choose Sony android devices on top of the excellent specifications and high quality of the products! ?

Now you have the opportunity to win Sony devices every 2 months
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/hero-open-source-developers/
Happy cooking

http://developer.sonymobile.com/201...-camera-available-for-experienced-developers/
enjoy
J

Hi all
We have published a new snapshot, zip v14, with camera update (improved quality and stability)
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Enjoy
J

jerpelea said:
Hi all
We have published a new snapshot, zip v14, with camera update (improved quality and stability)
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
Enjoy
J
Click to expand...
Click to collapse
I assume AOSP_L_MR1_151203_castor.zip has the v14 and therefore a working camara, right?
There was another issue with AOSP on Z2 LTE Tablet, namely that in Youtube some colors got psychedelic.
Has anyone verified if this is problem is gone.
I run latest FXP CM 12.1 FXP-cm-12.1-20150810-UNOFFICIAL-castor.zip and I am happy with it.
Is there perhaps a CM in the make with v14?

Hi all
I have some more exciting news
http://developer.sonymobile.com/kno...s/how-to-access-uart-ports-on-xperia-devices/
PS.if devices are not listed here they dont have the connector !
Br
J

New updates
http://developer.sonymobile.com/201...wider-range-of-unlocked-xperia-devices-video/
Enjoy
J

jerpelea said:
New updates
http://developer.sonymobile.com/201...wider-range-of-unlocked-xperia-devices-video/
Enjoy
J
Click to expand...
Click to collapse
I read in post
How to enable and enter recovery mode
1. Use the Flash tool for Xperia devices to install the latest generic software on your unlocked device.
2. Use the Flash tool for Xperia devices to install <device name> (Open devices) TA update.
so 2 questions:
- can one, instead of latest generic software, also have latest FXP AOSP software installed?
- where are the "<device name> (Open devices) TA update" files to be found?
(or does Flash tool for Xperia find those automagically?)
also: I have no Windows machine and use Androxyde on MacOSX or Linux. Will this work?

We have published new binaries
http://developer.sonymobile.com/downloads/tool/software-binaries-for-aosp-lollipop-android-5-1/
Br
J

Hi all
Blobs v17 are public
Happy easter
J
​

jerpelea said:
Hi all
Blobs v17 are public
Happy easter
J
​
Click to expand...
Click to collapse
Same for you. Thanks for bringing us good Xperia software.

http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
2016-04-22: AOSP Marshmallow binaries for Android 6.0 and AOSP Lollipop binaries for Android 5.1 updated with improved connectivity, stability and camera functionality. We’ve also added the second camera actuators for Xperia Z3 and Xperia Z4 tablet. In addition, we’ve added the camera actuator for the Xperia Z5 family for Android 6.0.

jerpelea said:
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
2016-04-22: AOSP Marshmallow binaries for Android 6.0 and AOSP Lollipop binaries for Android 5.1 updated with improved connectivity, stability and camera functionality. We’ve also added the second camera actuators for Xperia Z3 and Xperia Z4 tablet. In addition, we’ve added the camera actuator for the Xperia Z5 family for Android 6.0.
Click to expand...
Click to collapse
Thanks a lot !
will we see Marshmallow fxp builds on http://fxpblog.co/ ?

Hi all,
We have updated the build guide to support the latest features and security updates
http://developer.sonymobile.com/kno...aosp-marshmallow-for-unlocked-xperia-devices/
Enjoy
J

Hi,
We have updated the project page to reflect the latest progress
http://developer.sonymobile.com/open-devices/
Enjoy
J

[KERNEL][I9305][TW4.4.4][2017-06-16] ** TGPKERNEL **[v1.00][XXSFQD1-3.0.101]

TGPKERNEL​​
You can use Kernel Adiutor to change your settings.
TGPKernel Lite
This is a minial version of this kernel, with no extra governors, IO Schedulers, no F2FS, and SE Linux set to enforcing.
VARIANTS SUPPORTED
I9305
I9305N
I9305T
KERNEL INFORMATION
Built with: Linaro 4.9 Toolchain, optimized for cortexa9_neon (My custom build v1.01.20170615) - LINK
Kernel Base: I9305XXSFQD1
Ramdisk Base: I9305XXSFQD1
Linux Version: 3.0.101
FEATURES
Enabled hidden Governors and Schedulers
Added Insecure ADB
Disabled Secure Storage
Triangle Away Fix
Fixed charge off battery for old bootloaders
Updated LZO Compression
DOWNLOADS
DOWNLOAD VIA ANDROIDFILEHOST
CREDITS + THANKS
Samsung Open Source Release Center for the Source code
@Tkkg1994 for all his help and numerous code samples from his source
@morogoku for his help and advice
@osm0sis for Android Image Kitchen
Other devs that I have taken commits from which are credited in Github
XDA:DevDB Information
TGPKernel, Kernel for the Samsung Galaxy S III I9300
Contributors
djb77
Source Code: https://github.com/TheGalaxyProject/tgpkernel-s3.git
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: v1.00
Stable Release Date: 2017-06-16
Created 2017-06-16
Last Updated 2019-05-22

Reserved

Reserved

I've noticed that LinageOS is out for this device now too, so I'll make a version for that too. Stay tuned...

Nice kernel!!!
<3

Any way to get the Wolfson DAC to sound like the i9300?? I Will donate if you can trick it!

it'sup said:
Any way to get the Wolfson DAC to sound like the i9300?? I Will donate if you can trick it!
Click to expand...
Click to collapse
I can look into it, I have the source code from the AGNI kernel here so hopefully it's just a matter of picking out the code and inserting it into my kernel.
Another thing I want to look into soon is LinageOS support, since I see it's available on this device.

it'sup said:
Any way to get the Wolfson DAC to sound like the i9300?? I Will donate if you can trick it!
Click to expand...
Click to collapse
See how this goes...
TGPKernel.I9305.v1.00.Wolfson.20170625

I'm getting a constant bootloop after flashing your kernel. Os: RR remix 7.1.2 Nougut -Twrp latest custom recovery -i9305T device. I've tried wiping dalvik and cache but all of does is return me back to Twrp!?

it'sup said:
I'm getting a constant bootloop after flashing your kernel. Os: RR remix 7.1.2 Nougut -Twrp latest custom recovery -i9305T device. I've tried wiping dalvik and cache but all of does is return me back to Twrp!?
Click to expand...
Click to collapse
It's only been worked on to boot for a stock 4.4.4 TW ROM so far, I'll work on some variants soon

hello. could you build a 4.4.4 kernel for my sc03e to run i9305 TW rom?