Hi guys
Just wanted to get some thought out here - how difficult is it to port the lollipop aosp kernel to hook into LG media drivers : it is really heartbreaking to see the camera quality difference between stock and aosp.
Rather than ask xcam developers to port their framework ... I'm thinking if it is possible to port the kernel to use lg drivers. We will write a set of patches that will modify aosp kernel to use LG's framework.
More importantly, has this been attempted by any one else on xda...on other phones?
interestingly, there is a similar project on the LG Optimus L7 - http://forum.xda-developers.com/showpost.php?p=56231080&postcount=146
they have a stock driver github also being maintained at https://github.com/weritos666/proprietary_vendor_LG by @weritos. I wonder if a similar effort will work for Lg G2.
And some initial source code released by LG
I want to say the HTC Sensation has something like this. I know they had AOSP kernels that were based off official HTC Sense code and AOSP like ROM's based off Sense ROM's, but I'm not 100% on the inner working of them.
here's an effort by @manups4e in the G2 forum for porting the Camera2 HAL to AOSP http://forum.xda-developers.com/lg-g3/devs-only/camera-hal-caf-t2981136
sandys1 said:
here's an effort by @manups4e in the G2 forum for porting the Camera2 HAL to AOSP http://forum.xda-developers.com/lg-g3/devs-only/camera-hal-caf-t2981136
Click to expand...
Click to collapse
^^ it's for G3, not yet working and highly experimental
manups4e said:
^^ it's for G3, not yet working and highly experimental
Click to expand...
Click to collapse
oh yeah - very sorry. I was actually hoping someone from the G2 kernel developers (like the Render kernel) can collaborate with you on some of this work. I think the G2 and G3 driver frameworks are very similar and any progress on G3 can be ported to the G2 (or vice versa)
this is not only a kernel thing but driver too that's more complicated than you (and I) thought
manups4e said:
this is not only a kernel thing but driver too that's more complicated than you (and I) thought
Click to expand...
Click to collapse
correct - but this will happen after the release of stock lollipop which should have the Camera2 API. So I still have hope that your work will be useful to get a fully functional camera on AOSP camera (both in G2 and G3)
G3 doesn't use camera2 api neither camera 3 hal in its drivers i don't think g2 will be different and even knowing if it will.. we will never have LG source codes... only kernel sources
Related
Hey guys. So would anyone like to help me out in building an AOSP ROM for the LG Optimus S?
Currently, I have compiled the LG AOSP 2.2 kernel (zImage), and compiled the Android 2.2 AOSP system. Apparently now I need to get the LG vendor tree so I can compile that too into a working system? Can anyone help me out with that? This is my first time ever building a ROM from source code.
i hope someone will listen your help request
I hope so too... I hope so too.
I hope so too, would be nice to have another ROM option for the Optimus S. And this is a stepping stone to CyanogenMod on it
I'm also interested to create a fully working build of 2.2.2 AOSP Froyo.
But I'm new to the Android's world. I need that someone teach me how to build android from source. Also I need to know how to port the LG's drivers.....
I'm willing to help, but I can't program in any language. However, I know the basics, I can compile stuff, can do fairly well with the command line, I use Arch Linux as my main OS (so I can pretty much do compilations and stuff without a problem), etc.
I still don't know much about Android at this time, and contributing to this "project" may be my way of getting to know things
Count be in.. i m good with C,C++ ,shell scripts .tell me wat to do..i m new to android
Building Android from source can be quite tricky when proprietary software must be compiled in. I'm compiling since 2 months on gingerbread and nothing but phone is working... no USB,no camera, no bluetooth ... its now simply a phone^^
But, if your are lucky with Froyo you need only the source from android 2.2.x and the one shipped by LG (I know there are some sources for Optimus One, but don't know about Optimus S). Put it all together and compile the code - while/after compiling you will see lot of errors, there must be fixed by yours.
Have a look at cyanogen CM6.1, there have many fixes built in. If you would like to build a brand new system from scratch by yourself, i'll wish you many luck and lots of time
andy572 said:
Building Android from source can be quite tricky when proprietary software must be compiled in. I'm compiling since 2 months on gingerbread and nothing but phone is working... no USB,no camera, no bluetooth ... its now simply a phone^^
But, if your are lucky with Froyo you need only the source from android 2.2.x and the one shipped by LG (I know there are some sources for Optimus One, but don't know about Optimus S). Put it all together and compile the code - while/after compiling you will see lot of errors, there must be fixed by yours.
Have a look at cyanogen CM6.1, there have many fixes built in. If you would like to build a brand new system from scratch by yourself, i'll wish you many luck and lots of time
Click to expand...
Click to collapse
So in your opinion it would be a lot easier to just build a CyanogenMod 6.1 ROM? Sounds like a plan. I read that I could just pull stuff from the Legend and use that as well? Could you help me with that stuff (pulling from the Legend source, that is)?
Legend stuff is less compatible then i thought. You can't use nothing from there.
As my work at 2.3 is now stopped (I haven't bugs related to working stuff, I have no idea what to do with 3d and gps and I too lazy to patch libcamera now) I hope to start work on CM6 next holiday's.
mik_os said:
Legend stuff is less compatible then i thought. You can't use nothing from there.
As my work at 2.3 is now stopped (I haven't bugs related to working stuff, I have no idea what to do with 3d and gps and I too lazy to patch libcamera now) I hope to start work on CM6 next holiday's.
Click to expand...
Click to collapse
We'll work on it together then? I started a GitHub. github.com/mrinehart93
mrinehart93 said:
We'll work on it together then? I started a GitHub. github.com/mrinehart93
Click to expand...
Click to collapse
As I already got working GSM/Audio/WiFi/Bluetooth/USB/Sensors in 2.3 (port to 2.2 is easy) I will continue work in my repo https://github.com/mik9
Ypu can send your patches via "pull request" functionality.
mik_os said:
As I already got working GSM/Audio/WiFi/Bluetooth/USB/Sensors in 2.3 (port to 2.2 is easy) I will continue work in my repo https://github.com/mik9
Ypu can send your patches via "pull request" functionality.
Click to expand...
Click to collapse
I won't have any time to work on CM tonight or probably the rest of this week, but as soon as I do I'll set up my Github.
Hi!
I just want to vent my anger
Has anybody noticed that there are a minimum of four "parties" that work on an android kernel tree?
First there is the android open source project.
Then there is the CodeArora project.
There is also a kernel tree at Cyanogenmod.
And last but not least we have the "manufacturer" kernel tree.
AOSP has got a common tree and an individual tree for each architecture- just like Cyanogenmod.
CodeAurora has got multiple(!) trees for a single architecture.
The manufacturer seems to use some of CodeAurora's trees in the majority of cases.
Ah- I forgot the "original" linux kernel tree
This way we never get the most efficient and most stable kernel.
Just my two cents
you're right, but not only the kernel is used. LG takes code from codeaurora project - have seen this in code from the frameworks base tree^^
but on the other side: better they use community code as own code that didn't works perfect
WTF? LG really takes his sources from CodeAurora?!?!?
Well since code aurora is dedicated to qualcomm SoCs if i were a kernel developer i wud start with that tree..one question though does codeaurora contain gb kernel (.35) source for our msm7227 ??? u guys checked it out ???even if they theres a lot of other hardware that are going to need proprietary drivers i guess... THird world peripherals make porting tougher.. its just my take correct me if i m wrong
sarfaraz1989 said:
Well since code aurora is dedicated to qualcomm SoCs if i were a kernel developer i wud start with that tree..one question though does codeaurora contain gb kernel (.35) source for our msm7227 ??? u guys checked it out ???even if they theres a lot of other hardware that are going to need proprietary drivers i guess... THird world peripherals make porting tougher.. its just my take correct me if i m wrong
Click to expand...
Click to collapse
my kernel patches are taken from the codeaurora .35 source, but i can't adopt the complete kernel. there is a "must understand" and "must have many time" to do that
andy572 said:
my kernel patches are taken from the codeaurora .35 source, but i can't adopt the complete kernel. there is a "must understand" and "must have many time" to do that
Click to expand...
Click to collapse
That is exactly the problem!
I cannot really judge which patch from which tree is good- because I have not the time to read through Qualcomm's manuals (if they are public at all) and the kernel source.
If they would concentrate on one tree everything would be fine (ok- if you look at the "chaos commits" in the git repositories you become sick )
@caveman u working on a P500 kernel ??? how is porting so friggin easy for HTC devices..Do they have open source driver /generic hardware or what i mean a few of em even got a honeycomb partial port forget 2.3 ....
sarfaraz1989 said:
@caveman u working on a P500 kernel ??? how is porting so friggin easy for HTC devices..Do they have open source driver /generic hardware or what i mean a few of em even got a honeycomb partial port forget 2.3 ....
Click to expand...
Click to collapse
LG have some specific (old) hardware - they are using qualcomm hardware, but it's to old for newer kernel sources. the other problem is low cost hardware like the display - ms6000 is never used today, new devices are using samsung displays.
look at the wlan/smd chip - bcm4325 is never supported, bcm4329 is newer and is in kernel .38 too ... do you know, what i mean?
old hardware drivers are rare in kernels - never used drivers gets removed from tree, so there is no chance to bring it back.
ofcourse that's why it's called EVOLUTION
so it looks like u were right about getting a new phone
ciolnadu said:
ofcourse that's why it's called EVOLUTION
so it looks like u were right about getting a new phone
Click to expand...
Click to collapse
yes, it's marketing strategy and its ok - but why should i buy me a new device, when my is doing a good job?
andy572 said:
but why should i buy me a new device, when my is doing a good job?
Click to expand...
Click to collapse
+1 agreed 100% with andy.
andy572 said:
LG have some specific (old) hardware - they are using qualcomm hardware, but it's to old for newer kernel sources. the other problem is low cost hardware like the display - ms6000 is never used today, new devices are using samsung displays.
look at the wlan/smd chip - bcm4325 is never supported, bcm4329 is newer and is in kernel .38 too ... do you know, what i mean?
old hardware drivers are rare in kernels - never used drivers gets removed from tree, so there is no chance to bring it back.
Click to expand...
Click to collapse
Do you mean the drivers sources were in the old kernel and are removed in the new one? If so, I mean we have the old sources, why is it so difficult to port them to the new kernel sources? I am not a kernel developer so probably I am missing something
rivett said:
Do you mean the drivers sources were in the old kernel and are removed in the new one? If so, I mean we have the old sources, why is it so difficult to port them to the new kernel sources? I am not a kernel developer so probably I am missing something
Click to expand...
Click to collapse
code isn't moved but deleted.
Has anybody found out the CodeAurora git commit on which LG's V10r is based on?
LG G3 Lollipop system dump & kdz
http://forum.xda-developers.com/lg-g3/general/kdz-lollipop-5-0-android-l-t2931192
Someone tag our dev and let them know
Lets port this to g2
we need the g2 lollipop kernel to have a port...
buski said:
we need the g2 lollipop kernel to have a port...
Click to expand...
Click to collapse
It may be possible to use a 4.4 sourced kernel on lollipop, its been done with previous versions of android. For instance GB source is being used for KK ROMs on Galaxy S1 (very big gap), and my Opt G has L using a 4.x kernel as well. (Best ex would prob be the G1, which ran most versions of android up to ICS, incl sense, motoblur, etc)
Wait a few weeks and perhaps someone will port this w/o L source for D80x.
Sent From Capsule Corp.
AmalD said:
LG G3 Lollipop system dump & kdz
http://forum.xda-developers.com/lg-g3/general/kdz-lollipop-5-0-android-l-t2931192
Someone tag our dev and let them know
Lets port this to g2
Click to expand...
Click to collapse
be warned...ppl have already bricked their devices with this...(see g3 forum) and yes it is possible to use the current kk kernel BUT its not just build and expect it to work...code changes are needed for the compensation...this stuff is already being worked on by a few devs...including me...wont give eta's but it is in progress
Hello! (Warning: n00b)
I just rooted my LG K7 with Kingroot, and was disappointed to not find a custom rom for it. I was just wondering, can stock android be used without any modifications, just compiled and flashed to a phone? I couldn't find anything on this.
Thanks all
Nope. LG would have to release the source code and a developer would have to take interest in it to compile AOSP and merge the drivers and such from the LG source code. Chances of that happening are almost nil. The G4/G5 etc are much more popular and they don't even have decent versions of stock android and some variants don't have anything beyond stock LG based mods.
es0tericcha0s said:
Nope. LG would have to release the source code and a developer would have to take interest in it to compile AOSP and merge the drivers and such from the LG source code. Chances of that happening are almost nil. The G4/G5 etc are much more popular and they don't even have decent versions of stock android and some variants don't have anything beyond stock LG based mods.
Click to expand...
Click to collapse
That sucks. Thanks for the info!
Hi
Please build or port an Aosp rom to our great devices.
If somebody agree with me, please strengthen in it.
Thanks
zsolt
There are people working on CM and AICP ports. You can see here: http://en.miui.com/thread-407842-1-1.html
prismk said:
There are people working on CM and AICP ports. You can see here: http://en.miui.com/thread-407842-1-1.html
Click to expand...
Click to collapse
yes i know, i have seen these posts
thanks
If you already knew then why did you start a new thread?
Why do some people think that asking for a ROM will make it magically happen faster or something?
Sent from my Redmi Note 4 using Tapatalk
Do you use AOSP rom if that rom don't have fingerprint function (because RMN4 use FPC1035 with MTK TrustSonic enabled, it's so hard to port it unless Xiaomi release kernel source code) ?
Most people asking for porting rom from other devices but also demand porting rom have full functions working like original rom which impossible to make it happen...
longnt2007 said:
Do you use AOSP rom if that rom don't have fingerprint function (because RMN4 use FPC1035 with MTK TrustSonic enabled, it's so hard to port it unless Xiaomi release kernel source code) ?
Most people asking for porting rom from other devices but also demand porting rom have full functions working like original rom which impossible to make it happen...
Click to expand...
Click to collapse
Yep. As I said in the X20 kernel thread, it's only just the beginning because that's only generic X20 kernel source. ODM's *always* add their own hardware that is not covered by the original kernel source.
Typically, Camera and Sensor drivers were the most difficult to port (with blobs and reverse-engineering stock firmware). But TrustSonic sounds like it will be the biggest task.