Complete Source for the MediaTek MT6589 is available at Sony Open Source Archives
I have confirmed that it is full and shows only warnings while building and builds without errors.
What Next?The config?
It is the full source for the Xperia C. :good:
dev0xteam said:
Complete Source for the MediaTek MT6589 is available at Sony Open Source Archives
I have confirmed that it is full and shows only warnings while building and builds without errors.
What Next?The config?
Click to expand...
Click to collapse
I believe the config file is device dependent so will be different for a116......
still if anyone takes up the project of building it for a116 he has to modify the config :fingers-crossed:
here is kernel source of mmx canvas HD aka fly iq451
https://disk.yandex.ru/public/?hash=VJjzmkQPL8/elQ2+VKi89/k0nd//iBWRDiIhNZOCrzg=&locale=ru
Dj_Ignatius said:
here is kernel source of mmx canvas HD aka fly iq451
https://disk.yandex.ru/public/?hash=VJjzmkQPL8/elQ2+VKi89/k0nd//iBWRDiIhNZOCrzg=&locale=ru
Click to expand...
Click to collapse
Is it complete?
dev0xteam said:
Is it complete?
Click to expand...
Click to collapse
i think yes..
Ok. The sony source is not fully complete but.enough to build a kernel. Still there is some problem in config or something else which is not allowing the kernel to compile..
Sent from my A116 using xda app-developers app
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
konnorrigby said:
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
Click to expand...
Click to collapse
A general question :- i previously had mmx a75 which of course didn't had the sources but overclocking through mtkcpu from playstore was achieved..!! So why our device can't be overclocked using the same app..??
Sent from my A116 using xda premium
Hopefully this means we get cyanogen based ROMs soon
Sent from my Canvas HD running X-flare V2 ROM
axis.meister said:
Hopefully this means we get cyanogen based ROMs soon
Sent from my Canvas HD running X-flare V2 ROM
Click to expand...
Click to collapse
Did you read the thread?
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
konnorrigby said:
Did you read the thread?
Sent from my Evo 3D CDMA using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Read the OP and got my hopes high. Read your post now and ...
lets hope Mediatek actually releases full sources in the future.
konnorrigby said:
As many people have pointed out, this isn't full source. There has yet to be a "release" of FULL source yet. There are a lot of kernel stuff around, but kernel isn't a problem at this time because mediatek and its vendors are fairly good about upgrading kernel. What I and many others want is the missing Android build end of the source. Even Sony didn't release this piece. There is a list of whats missing in the sauce. They have a script that packages the stuff that will build only a kernel and it pulls out the MediaTek crap. look in
Code:
16.0.A.0.36/mediatek/build/android
to see what i mean. its just a basic skeleton but no actual android stuff. CD into tools and you'll see the script
Code:
filter.py
has a list of all the sources they wont release. So when people say stuff like "FULL SOURCE FOR MEDIATEK" look into it first. AFAIK MediaTek has never released this source to anyone but its partners. IE: sony, zte, cubot, etc. Sony may have released the most complete source, they havent released all of it. And i dont think anyone ever will. I've sent MediaTek countless emails and have never recieved a response. Anyway this source is a good start if someone wants to look into overclock(which i dont believe is possible at this time with the source we have) but again i havent looked at it yet. but i digress.
Click to expand...
Click to collapse
http://www.hacktohell.org/2013/07/mediatek-mt6589-complete-source.html#.Ui5G3sanojp
can this be the full source? i am not a dev so idk anything about it there is a link in the link i gave u maybe u can see it and tell us
so any good news about custom kernel?
Is this enough to build a custom kernel atleast?
Sent from my Micromax A116 using Tapatalk
Related
Hi Developer's,
It's really great to see a lot of great roms for Samsung Galaxy Ace releasing day by day.....Why don't you guys work together and bring up an AOSP rom for SGA....Please try concentrating on developing an AOSP rom...
THANKS
Somebody did it but decided not to share because the forum is full of thieves who take others' work and change a little to release it as their own.
He mentioned that he's got ASOP working with a week standby battery life. Don't know if it's true but I believe it's possible. But now we need a developer to do this, not just rom cookers. Still it seems like nobody is interested.
consegregate said:
Somebody did it but decided not to share because the forum is full of thieves who take others' work and change a little to release it as their own.
He mentioned that he's got ASOP working with a week standby battery life. Don't know if it's true but I believe it's possible. But now we need a developer to do this, not just rom cookers. Still it seems like nobody is interested.
Click to expand...
Click to collapse
ASOP stands for ? (I'm considered quite a new use LOL)
Sent from my Ultima Weapon using XDA App
EmoBoiix3 said:
ASOP stands for ? (I'm considered quite a new use LOL)
Sent from my Ultima Weapon using XDA App
Click to expand...
Click to collapse
It's supposed to be AOSP sorry. It's android open source project. Such roms have no bloatware nor brand additions. The rom package can be as small as 40 mb. But integrating the functions like touchscreen and lights and connectivity may be a problem so we need somebody willing to compile!
consegregate said:
It's supposed to be AOSP sorry. It's android open source project. Such roms have no bloatware nor brand additions. The rom package can be as small as 40 mb. But integrating the functions like touchscreen and lights and connectivity may be a problem so we need somebody willing to compile!
Click to expand...
Click to collapse
Wow that's a small package
That's the only advantage ?
EmoBoiix3 said:
Wow that's a small package
That's the only advantage ?
Click to expand...
Click to collapse
with AOSP, we'll have a pure google phone no touchwiz
EmoBoiix3 said:
Wow that's a small package
That's the only advantage ?
Click to expand...
Click to collapse
Small, but also extremely lightweight so I presume it'll be fast. With that as base custom roms should be better and faster.
If sod is really a firmware bug both AOSP and Cyanogenmod should stomp it off...
AOSP is android in its purest form without samsung's desecration. It is how android was meant to be. It is a base for ROMs like MIUI in many cases. Besides one can use the latest android sources(android 2.3.5) or the older stable sources to build it.
But building it is not easy. The android source code itself is like some 2 GB. Compiling and integrating the source code into a device is like building something from scratch. It would take a lot of time,effort and patience to build an AOSP rom.
skynet28 said:
AOSP is android in its purest form without samsung's desecration. It is how android was meant to be. It is a base for ROMs like MIUI in many cases. Besides one can use the latest android sources(android 2.3.5) or the older stable sources to build it.
But building it is not easy. The android source code itself is like some 2 GB. Compiling and integrating the source code into a device is like building something from scratch. It would take a lot of time,effort and patience to build an AOSP rom.
Click to expand...
Click to collapse
Wow.....THAT IS AWESOME !
Unfortunately I know nothing about code , otherwise I would've worked on it . LOL
skynet28 said:
AOSP is android in its purest form without samsung's desecration. It is how android was meant to be. It is a base for ROMs like MIUI in many cases. Besides one can use the latest android sources(android 2.3.5) or the older stable sources to build it.
But building it is not easy. The android source code itself is like some 2 GB. Compiling and integrating the source code into a device is like building something from scratch. It would take a lot of time,effort and patience to build an AOSP rom.
Click to expand...
Click to collapse
Though what i've heard of is that miui was based on cyanogenmod, which was also built from scratch.
I have Ubuntu....but I'm a fail at programming XD HAHAHAHA
Anyone wanna make an AOSP ROM with me ?
consegregate said:
Though what i've heard of is that miui was based on cyanogenmod, which was also built from scratch.
Click to expand...
Click to collapse
Of course both cyanogenmod and aosp have to be built from scratch. Cyanogenmod,pure AOSP and MIUI are all based on Original AOSP source code and so have the maximum speed and utilize the hardware to its fullest. This is unlike samsung stock which has incorporated some closed source code with the open source one which limits its development.
...and all AOSP ROM should have no SOD issue
I set to work on it....but I didn't go far . FML
Sent from my Ultima Weapon using XDA App
For anyone interested, here's a tutorial that might help...
http://forum.xda-developers.com/showthread.php?t=1183832
adiles said:
For anyone interested, here's a tutorial that might help...
http://forum.xda-developers.com/showthread.php?t=1183832
Click to expand...
Click to collapse
It helps , but how do I configure USB for Ace ??
Sent from my Ultima Weapon using XDA App
EmoBoiix3 said:
It helps , but how do I configure USB for Ace ??
Sent from my Ultima Weapon using XDA App
Click to expand...
Click to collapse
I guess you are using ubuntu..
Go to a terminal,connect the Galaxy ace via usb and type
$ lsusb
This will list various bus devices..Find Samsung electronics...mine is something like this...yours should be something like this-
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
Here "04e8" is vendor id and "689e" is product id.
Type in terminal-
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
In the blank file type
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", ATTRS{idProduct}=="689e", MODE="0666", OWNER=""
Save the file and type
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
and restart udev.
edit.. wrong forum
skynet28 said:
I guess you are using ubuntu..
Go to a terminal,connect the Galaxy ace via usb and type
$ lsusb
This will list various bus devices..Find Samsung electronics...mine is something like this...yours should be something like this-
Bus 002 Device 009: ID 04e8:689e Samsung Electronics Co., Ltd
Here "04e8" is vendor id and "689e" is product id.
Type in terminal-
Code:
$ gksudo gedit /etc/udev/rules.d/51-android.rules
In the blank file type
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="04e8", ATTRS{idProduct}=="689e", MODE="0666", OWNER=""
Save the file and type
Code:
$ sudo chmod a+r /etc/udev/rules.d/51-android.rules
and restart udev.
Click to expand...
Click to collapse
Thanks a bunch
It's hard t do such things on a VM , you know ><
Sent from my Ultima Weapon using XDA App
Hi guys,
I went to check for the HTC DX source code on htcdev.com, and saw there were around 31 sources, but they're are all CRC's...
Could anyone please explain to me, what is a CRC? I tried googling it, but it didn't really help.
Sent from my HTC Desire X using xda premium
kernel source
Lloir said:
kernel source
Click to expand...
Click to collapse
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
infernal77 said:
I have been reading up on making roms, mostly about AOSP and CM, since they have best info and tutorials and such. But at some point, they both say to port to a new device you need to have the proprietary files (non open source device-specific software) to be able to build a working rom, using ./extract-files.sh or ./proprietary-files.sh.
From what I've read, identifying these files is mostly educated (not my case, lol) guessing, trial and error,... But I was wondering : is this CRC source code what they are talking about and would there be a way to get all the necessary proprietary files from it ?
Click to expand...
Click to collapse
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Yasir Javed Ansari said:
Search for vendor protou github.
Google it. You'll find proprietary files.
Regards
Sent from my Desire using xda app-developers app
Click to expand...
Click to collapse
Thanks, Yasir, I know lli0r made a device and vendor tree, but he said the vendor tree might be incomplete. He tried to make us a CM9 but hasn't got the device itself. I also read you can extract the files from a running device, but for that you need extract-files.sh or proprietary-files.sh, which isn't in there. I'm sure I can google and find one of those files from another device and try to run them on mine, but they're probably device-specific as well. And there isn't one of those files in lli0r's github. I checked that I'm sorry, I am ompletely new to Android, let alone building roms, but I love to just experiment a bit
Btw, when are you getting your Desire X ?
Google has recently released the 3.10 linux kernel for Android. and CodeAurora has also got it. I was wondering if it's realistic to port in this phase. I tried to but I failed hard lol. Main reason to port the 3.10 series is that it should have a great battery life. I'm not sure whether it will run on KitKat since it's supposed to be for Android 5.0.
Links:
Google Kernel: https://android.googlesource.com/kernel/common.git/+/experimental/android-3.10
CodeAurora Kernel: https://www.codeaurora.org/cgit/quic/la/kernel/msm-3.10
Anyone else attempted? If anyone could give me some more info about this I would be very happy!
Thread cleaned
How many times do we have to say it?
Keep this damn soap opera drama OFF XDA and stick to your Google +
How rude to bring all this crap in here to the OP's discussion
Next talk of secret kernels or banned members will be...trouble.
If you have no respect for XDA, then leave XDA...please!
Thank you for your cooperation
Friendly Neighborhood Senior Moderator
From my experience i know that binary compatibility between linux kernel versions (even between minor versions) is the latest thing developers care about. Even if you make this kernel work on i9505 i doubt u will be able to use binaries (those /system/lib/*.so files) from any existing ROM and thus u won't be able to make ROM with this kernel.
Need to wait when Samsung will move to this kernel version, but i'm affraid it won't happen on any existing phone. Usually, Samsung stick on the kernel version phone launched.
sorg said:
From my experience i know that binary compatibility between linux kernel versions (even between minor versions) is the latest thing developers care about. Even if you make this kernel work on i9505 i doubt u will be able to use binaries (those /system/lib/*.so files) from any existing ROM and thus u won't be able to make ROM with this kernel.
Need to wait when Samsung will move to this kernel version, but i'm affraid it won't happen on any existing phone. Usually, Samsung stick on the kernel version phone launched.
Click to expand...
Click to collapse
It's possible that CAF updated their repos or AOSP for the 3.10 kernel. There's references to 3.12 at master in bionic.
broodplank1337, what happens if you build a recovery and fastboot boot that?
xboxfanj said:
It's possible that CAF updated their repos or AOSP for the 3.10 kernel. There's references to 3.12 at master in bionic.
Click to expand...
Click to collapse
Doesn't AOSP use any libraries from stock ROM?
I didn't try AOSP, but CM usually required many libraries from stock ROM last time i've tried (couple years ago).
sorg said:
Doesn't AOSP use any libraries from stock ROM?
I didn't try AOSP, but CM usually required many libraries from stock ROM last time i've tried (couple years ago).
Click to expand...
Click to collapse
Yeah, there's a bunch of proprietary files specific to the SOC.
It's not as simple as the code existing on CAF, the device branch for your specific SoC needs it as well.
Of course, one could do this manually, but the effort and skills required is not trivial.
LLStarks said:
It's not as simple as the code existing on CAF, the device branch for your specific SoC needs it as well.
Of course, one could do this manually, but the effort and skills required is not trivial.
Click to expand...
Click to collapse
True. Caf does have some 3.10 device branches but none for 8960/8064, since those are not supported. Not sure why since they do support weaker chips such as 8226 and 8610. They do have some ramdisk changes for 3.10, but even with all that, I have no adb and no ramconsole on the optimus g (nexus 4).
Sent from my Optimus G using xda app-developers app
The only things I'd really want out of a >3.4 kernel is dma_buf support, the msm drm, and Freedreno
Maybe it would be easier to backport these features since by themselves they go a long way to making desktop Linux on our phones easier
LLStarks said:
The only things I'd really want out of a >3.4 kernel is dma_buf support, the msm drm, and Freedreno
Maybe it would be easier to backport these features since by themselves they go a long way to making desktop Linux on our phones easier
Click to expand...
Click to collapse
my s3 3.4-drm kernels supports it - patches came from here ==>
(s4 kernel is a WIP)
https://github.com/freedreno/kernel-msm/
That stuff's outdated
Real magic is here: http://cgit.freedesktop.org/~robclark/linux/refs/heads
Additionally, I wonder if anyone has attempted to boot Linux off the Hexagon DSP which is a pretty much like a 2nd CPU in your phone that's waiting to be used
LLStarks said:
That stuff's outdated
Real magic is here: http://cgit.freedesktop.org/~robclark/linux/refs/heads
Additionally, I wonder if anyone has attempted to boot Linux off the Hexagon DSP which is a pretty much like a 2nd CPU in your phone that's waiting to be used
Click to expand...
Click to collapse
We have offloaded all audio processing and mp3 decoding to the DSP. Thus allowing all 4 primary cores to sleep while playing audio. Media player app itself may use CPU cycles for UI updates when the screen is on. Working on WMA decoding...
Sent from my GT-I9505G using XDA Premium 4 mobile app
please make this kernel work with miui rom!
So I'm using one of the kitkat roms and I can't seem to get USB OTG and USB charging to work at the same time? Is this just not possible? Or do I need to do something special? I bought one of the OTG Y cables that allows the hookup of a charger and a USB device and it's still no go, it'll show it's charging for a minute or so after a USB device is mounted but then the charging icon goes away?
Someone had mentioned to me that a custom kernel may be needed?
Yep you would need a custom kernel.
ThatFrigginAzn said:
Yep you would need a custom kernel.
Click to expand...
Click to collapse
Any documentation around on how to build this kernel to do what I need?
Hdale85 said:
Any documentation around on how to build this kernel to do what I need?
Click to expand...
Click to collapse
Look in my signature for a guide. For the specifics, you will need to find a kernel on github that has what you are looking for and port it to your build. My roll your own kernel guide will get you started. You will need a partition with Debian Linux to complete the guide. I suggest AntiX.
sleekmason said:
Look in my signature for a guide. For the specifics, you will need to find a kernel on github that has what you are looking for and port it to your build. My roll your own kernel guide will get you started. You will need a partition with Debian Linux to complete the guide. I suggest AntiX.
Click to expand...
Click to collapse
Can it be a kernel from another device? or does it need to be similar?
Also how about Ubuntu? I'm familiar with Ubuntu, but I'll look at AntiX
From what I gather I only need USB host mode so that the USB port is not outputting power.
Hdale85 said:
Can it be a kernel from another device? or does it need to be similar?
Also how about Ubuntu? I'm familiar with Ubuntu, but I'll look at AntiX
From what I gather I only need USB host mode so that the USB port is not outputting power.
Click to expand...
Click to collapse
Ubuntu should work, though the names of the dependencies might be off. Easier to just partition off and install Antix. Damn good distro. I went with stable for the guide, but you can easily switch later to testing or unstable by changing up the sources list.
For what you need, you may find it as an option when adjusting the menuconfig during the make process.
The second post in the thread tells a bit about changes necessary for the 500 device, as I originally made the guide for the 510.
There are currently two other kernels for the 500 that were successfully made using the guide. One of them also has a decent install through recovery script
sleekmason said:
Ubuntu should work, though the names of the dependencies might be off. Easier to just partition off and install Antix. Damn good distro. I went with stable for the guide, but you can easily switch later to testing or unstable by changing up the sources list.
For what you need, you may find it as an option when adjusting the menuconfig during the make process.
The second post in the thread tells a bit about changes necessary for the 500 device, as I originally made the guide for the 510.
There are currently two other kernels for the 500 that were successfully made using the guide. One of them also has a decent install through recovery script
Click to expand...
Click to collapse
What's the difference between the 500 and 510?
Hdale85 said:
What's the difference between the 500 and 510?
Click to expand...
Click to collapse
The 510 is the Google play edition, whereas the 500 is the lg version. If you didn't buy it through the play store, you have the 500.
The best way to learn would be to follow the guide all the way through, copy and paste, and then figure out what you are doing while you are doing it!
Also, this should be posted in the questions thread rather than development if a moderator would be so kind to move this post.
Oh ok the 510 is the google play edition. Either kernel should work right? They are the same device... I'm not running the stock rom as I wanted a basic 4.4 rom as this is eventually going in my car.
Well you posted right before me lol, but I made the post here because I know there are a couple other people looking for the same thing so I was hoping we could develop a kernel for everyone.
Hdale85 said:
Oh ok the 510 is the google play edition. Either kernel should work right? They are the same device... I'm not running the stock rom as I wanted a basic 4.4 rom as this is eventually going in my car.
Click to expand...
Click to collapse
Unfortunately no, there are some differences, mostly with naming, but that can be important.
There are two parts to the boot image for our device, the ramdisk, and the kernel itself. The ramdisk plays a key roll in deciding certain options for the device, while the kernel controls more common options you may find on any device.
Most of the install from recovery scripts, repack the kernel zimage with the existing ramdisk from the device. But this doesn't really matter either.
All of the multi device kernels tend to be larger than necessary and have problems they shouldn't.
Long story short is that each device has it's own kernel source, which has supposedly been optimized for its device. This isn't exactly true, and the list of changes I've made to better the 510 device's kernel is astounding.
If you follow my guide, all of this will become apparent.
Alright thanks I'll look over it.
So what makes the510 different?? Is the firmware different? Obviously they didn't change the hardware so could one somehow convert the 500 to a 510? Only reason I'm interested is because some of that stuff you said doesn't work on the 500 it seems? Such as fastboot?
Hdale85 said:
So what makes the510 different?? Is the firmware different? Obviously they didn't change the hardware so could one somehow convert the 500 to a 510? Only reason I'm interested is because some of that stuff you said doesn't work on the 500 it seems? Such as fastboot?
Click to expand...
Click to collapse
Lg specific drivers mostly. Fastboot requires an unlocked boot loader, which the V500 does not have. An exploit is used to bypass the boot loader on the 500. Loki.
The gpe is pure android, with just a couple of perks thrown in, as it uses an Lg platforms. Our device , that being the V510 most closely resembles the Nexus 4 (Mako) version, and was probably based off that device. The items I have added to the 510 kernel as enhancements, mostly came from a mako kernel with the rest simply being tweak corrections to the existing source code.
Those changes alone made huge improvements in performance and battery.
sleekmason said:
Lg specific drivers mostly. Fastboot requires an unlocked boot loader, which the V500 does not have. An exploit is used to bypass the boot loader on the 500. Loki.
The gpe is pure android, with just a couple of perks thrown in, as it uses an Lg platforms. Our device , that being the V510 most closely resembles the Nexus 4 (Mako) version, and was probably based off that device. The items I have added to the 510 kernel as enhancements, mostly came from a mako kernel with the rest simply being tweak corrections to the existing source code.
Those changes alone made huge improvements in performance and battery.
Click to expand...
Click to collapse
Yea I just found the long thread about converting, its strange they can't seem to get it to work? Quite strange... Well I'll have to research the other bits I guess from others that have made V500 kernels or something.
maybe this commit is what you need
https://github.com/oubeichen/android_kernel_lge_v500/commit/ee86db750adf2bb7b4f7b988ba6937d92551373b
I havent tested yet but this is ported from a nexus4 kernel thread. v500 and nexus4 have the same power management ic
Sent from my LG-V500 using XDA Premium 4 mobile app
oubeichen said:
maybe this commit is what you need
https://github.com/oubeichen/android_kernel_lge_v500/commit/ee86db750adf2bb7b4f7b988ba6937d92551373b
I havent tested yet but this is ported from a nexus4 kernel thread. v500 and nexus4 have the same power management ic
Sent from my LG-V500 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If anybody wants this, I'll compile it into the V510. Looks pretty straightforward. Thank you for the link.
Hdale85 said:
Well you posted right before me lol, but I made the post here because I know there are a couple other people looking for the same thing so I was hoping we could develop a kernel for everyone.
Click to expand...
Click to collapse
Indeed! :fingers-crossed:
treetop777 said:
Indeed! :fingers-crossed:
Click to expand...
Click to collapse
I'm going to take a stab at a custom kernel, but I have to setup linux on my desktop again so I'm not sure when I'll get around to it lol. Might be able to this week sometime.
If I can't get USB Host mode with charging enabled I'm going to have to look into a wireless HD solution or something, and even then that won't fix the setup I wanted to use for high end sound.
news ????
And finally Our device, Redmi 3S (Land), with Treble ported... @TeamMex has brought in initial Treble support to Redmi 3S just like it was done on Redmi Note 4, using Cust as the Vendor partition... Hope He has great success in it...
Source: https://plus.google.com/u/0/+klozzjesus/posts/5REcrMxfq67
Let Us all hop into discussion and questions related to it here, rather than pollute other Development Threads...
Keep things polite and simple, varying opinions are all expected but lets not end up hurting anyone with Our Words... Be Responsible Guys...
Wow great news hope to see android p based roms without much problem in near future
amazing
Wow amazing
Wow ?
I need to ask something can anyone point me where are the drivers for soc lies i mean in a rom it is stored in /system/vendor folder but where does Qualcomm publishes its drivers for its different soc? Because project treble can only come to live if our land uses the project trebled compatible drivers from Qualcomm am i right? Please correct me of i am wrong and elaborate how these things goes
Ash225 said:
I need to ask something can anyone point me where are the drivers for soc lies i mean in a rom it is stored in /system/vendor folder but where does Qualcomm publishes its drivers for its different soc? Because project treble can only come to live if our land uses the project trebled compatible drivers from Qualcomm am i right? Please correct me of i am wrong and elaborate how these things goes
Click to expand...
Click to collapse
Can't get you
fxsheep said:
Can't get you
Click to expand...
Click to collapse
Look in windows we need to download drivers for windows 10, windows 7 etc etc and those are simple drivers which user can install right but in android there is vendor folder which contains all drivers for our soc camera ril etc. I want to know where does Qualcomm releases such drivers i mean in git or anywhere else. There must be a source from where mobile phone manufacturer get those vendor files and use it to build the rom for their devices Right? Take it in this way for buildings a custom rom we need source code which is available in git which devs can clone and compile to make a rom similarly where does we get these camera libs, soc, etc related files found?
Ash225 said:
Look in windows we need to download drivers for windows 10, windows 7 etc etc and those are simple drivers which user can install right but in android there is vendor folder which contains all drivers for our soc camera ril etc. I want to know where does Qualcomm releases such drivers i mean in git or anywhere else. There must be a source from where mobile phone manufacturer get those vendor files and use it to build the rom for their devices Right? Take it in this way for buildings a custom rom we need source code which is available in git which devs can clone and compile to make a rom similarly where does we get these camera libs, soc, etc related files found?
Click to expand...
Click to collapse
maybe you mean CAF(Code Aurora Forum)?
fxsheep said:
maybe you mean CAF(Code Aurora Forum)?
Click to expand...
Click to collapse
What is that and does it serves ?Okay can you tell me one thing does Qualcomm and other vendors who makes parts like soc, camera module etc for smartphone also makes drivers for the same or not? Or is the mobile phone company who makes all drivers for the components used in the phone? Intel makes processor and releases driver for the same does it gos well for manufacturer like Qualcomm?
Ash225 said:
What is that and does it serves ?Okay can you tell me one thing does Qualcomm and other vendors who makes parts like soc, camera module etc for smartphone also makes drivers for the same or not? Or is the mobile phone company who makes all drivers for the components used in the phone? Intel makes processor and releases driver for the same does it gos well for manufacturer like Qualcomm?
Click to expand...
Click to collapse
caf is the offical release of qualcomm's opensource
@TeamMex you are simply awesome dude
When we will also able to use project treble for land?
Any new about it where is @TeamMex gone?
abhishekpandey7148 said:
When we will also able to use project treble for land?
Any new about it where is @TeamMex gone?
Click to expand...
Click to collapse
Dont demand... You are not paying Him anything to ask Him like that... It will be done when He does it... Be patient...
abhishekpandey7148 said:
When we will also able to use project treble for land?
Any new about it where is @TeamMex gone?
Click to expand...
Click to collapse
Just wait for him to do the magic
abhishekpandey7148 said:
When we will also able to use project treble for land?
Any new about it where is @TeamMex gone?
Click to expand...
Click to collapse
I working in something's but I can release the old version xD presented in my screens
But have some message every boot and the camera take some time until the daemon is released
Sent from my Motorola Moto Z Play using XDA Labs
@TeamMex
Many thanks for your hard work.
Can you maybe release your software on github?
I want to used it for the Motorola G5s. Its almost the same device only I need not suc as vendor but OEM as vendor. But that can I fix if I have your code.
GoldeneyeS2 said:
@TeamMex
Many thanks for your hard work.
Can you maybe release your software on github?
I want to used it for the Motorola G5s. Its almost the same device only I need not suc as vendor but OEM as vendor. But that can I fix if I have your code.
Click to expand...
Click to collapse
Yeah I have it for Moto Z play too but u need to wait until my isp fix my internet issues , so for now I can't upload the source sorry
I hope it can be fixed in 3 days
Can somebody explain me what is treble for?
vandasche said:
Can somebody explain me what is treble for?
Click to expand...
Click to collapse
Just Google it... You can find a lot of really good explanations in it... I'll link a few in the OP very soon...