Related
Hello everybody,
I'm back on the forums after being away for some time.
In the meantime I got myself my own LG Optimus G to be able to get to effective developing for this device.
My opinion is that this device is a powerfull device with a lot of "still to be unlocked" potential.
Before I bought the LG Optimus G I used the Samsung Galaxy S Plus, which had a very active and good developers which even today still perfectly support this old device.
When that phone launched it contained Android 2.3.6, but today it supports even the Android 4.4.4 builds (unoffical).
One of the most important steps in achieving this goal was to move from the Samsung provided kernel source to the CAF (Code Aurora Forum) based kernel source.
Because I wish the LG Optimus G the same future as my old device, I would like to get busy with bringing up the CAF kernel codebase on the LG Optimus G.
This will be a big project which is why I request fellow developers which are interested in this project to please join and form a development team with a common goal.
What needs to be done is:
- Obtain official LG Optimus G (Android 4.4) kernel sourcecode from: LGE975_G_Kitkat_Android_V20a_Kernel.zip
- Obtain latest CAF Kernel codebase (chipset apq8064) from: msm-5bfc8718998bedfeea1997d83838ffd1981cbf12.tar.gz (Last modification date: 30-06-2014)
- Extract added LGE Specific code and drivers from the official LG kernel source.
- Set-up a team Github with the clean CAF codebase, which all the driver and LG specific code will be added to.
If you're interested in helping with this project please contact me or leave a message over here.
Please no spamming etc.
Greetings PsychoGame
Hello everybody,
A little status update:
At this moment a 2-man team has been formed.
We have a team Github set-up for the development process this team will have.
The github link is: https://github.com/OptimusG-Dev-Team
If you are interested in giving us a helping hand with this project you're more than welcome.
Leave a message in this forum thread or contact me through a PM.
Experience with linux and also with the kernel is of course important.
Greetings PsychoGame
Bravo. Im hopeless in terms of what ever you code ninjas do, just wanted to let you know that i and most likely all in LGOG community greatly value this project. If you haven't already, perhaps PM some kernel devs as this would help in project gaining momentum and improved outcomes.
Happy to see that you're back psycho. Very brilliant idea. I hereby tag some devs to attract their attention. @faust93 @Loller79 , @jollaman999 , @Kevinjoa , @ThatKawaiiGuy , @xboxfanj , @JustinXu , @houstonn
Hey, I don't know much about kernel stuff, I'm learning Java atm so might be able to give tips. Not a lot though.
I don't have the Optimus G anymore (haven't since March), so I won't be able to do a ton, but I can help solve issues if/when needed.
akahroba said:
Happy to see that you're back psycho. Very brilliant idea. I hereby tag some devs to attract their attention. @Loller79 , @jollaman999 , @Kevinjoa , @ThatKawaiiGuy , @xboxfanj
Click to expand...
Click to collapse
I don't have kernel knowledge that much... I just referenced other dev's kernel sources and fix it to my style.
But thanks for mention to me.
It'll take some time, but I'm sure we get there.
Thank you for tagging some other devs inside this thread so it raises more awareness.
Everybody is welcome to join this project, for example clone the repositories, making changes and contribute.
That's exactly what opensource is all about.
And of course if you're interested in joining the team just send me a PM and I'll bring you up to speed on the progress/process and give you the needed information.
At this moment I'm also in contact with a official LG Developer which hopefully can provide me with some information that will help this porting process as well.
Greetings PsychoGame
jollaman999 said:
I don't have kernel knowledge that much... I just referenced other dev's kernel sources and fix it to my style.
But thanks for mention to me.
Click to expand...
Click to collapse
What about @houstonn ? Also I don't have any knowledge about this sort of thing really but I'll ask some other debs around to see if they want to join.
Sent from my LG-E975 using XDA Free mobile app
Generally, if you look at the branch of the libEGL_adreno file (using strings or hexedit), you can figure out what tag the OEM used (or branch) and then plop their source over that, then git pull the latest branch on top and fix any conflicts.
xboxfanj said:
Generally, if you look at the branch of the libEGL_adreno file (using strings or hexedit), you can figure out what tag the OEM used (or branch) and then plop their source over that, then git pull the latest branch on top and fix any conflicts.
Click to expand...
Click to collapse
Thanks for the information xboxfanj . I never noticed the branch information inside the LibEGL_adreno files.
This also helps a lot with the extraction of the LGE added code as the branch is now as close to the LG used sources.
This keeps the extracted LGE patches as clean as possble to almost only include the LGE added stuff.
PsychoGame said:
Thanks for the information xboxfanj . I never noticed the branch information inside the LibEGL_adreno files.
This also helps a lot with the extraction of the LGE added code as the branch is now as close to the LG used sources.
This keeps the extracted LGE patches as clean as possble to almost only include the LGE added stuff.
Click to expand...
Click to collapse
No problem. Let me know if you need help. Obviously, I can't test anything, but I should be able to help you get things building.
Oh, i noticed this thread just now.
I can help but i don't have much free time these months.
The idea is interesting from what i've seen, if you want another hand contact me via pm
Loller79 said:
Oh, i noticed this thread just now.
I can help but i don't have much free time these months.
The idea is interesting from what i've seen, if you want another hand contact me via pm
Click to expand...
Click to collapse
Sent a PM to you xda account
Today we've updated the proj-kernel repository with fully patched kernel sourcecode.
With a few small 'hacks' we are able to build the j1vd-perf_defconfig to the end.
What remains is getting the updated kernel to boot on the Optimus G boards.
At least the project is moving forward.
Just wanted to give everybody a update on the progress we're making.
Greetings PsychoGame
Here I'm back with some great news for everybody.
Today the kernel which was built using our sourcecode has succesfully booted on stock KK rom from LG.
The next steps we'll be taking will be getting the kernel to work with CM11 as well.
This way I hope we will have a perfectly stable and up-to-date kernel for the Optimus G which will work for Stock as well as CM based roms.
Greetings PsychoGame
PsychoGame said:
Here I'm back with some great news for everybody.
Today the kernel which was built using our sourcecode has succesfully booted on stock KK rom from LG.
The next steps we'll be taking will be getting the kernel to work with CM11 as well.
This way I hope we will have a perfectly stable and up-to-date kernel for the Optimus G which will work for Stock as well as CM based roms.
Greetings PsychoGame
Click to expand...
Click to collapse
very nice job mate. I think in this step @faust93 can help a lot.
Is this kernel work specific to E975, or will it be compatible with for example Sprint variant LS970?
dwielunski said:
Is this kernel work specific to E975, or will it be compatible with for example Sprint variant LS970?
Click to expand...
Click to collapse
At the moment it is based off E975 sources so it won't work on ls970 and similar.
Running it on my phone now and it works flawlessly.
Please thank a lot the team that made this possible and xboxfanj who helped with the project.
What's up guys? Is there anything we can help with? any test version or something?
If, like me, you despaired of CM ever releasing another "stable" version of CM-11, your wait is over.
I found out they had FINALLY done another M-SNAPSHOT code freeze, so I synced the source and built one of my own.
http://d-h.st/aihU
Link to Kernel source (if you feel you need it)
https://github.com/CyanogenMod/android_kernel_samsung_hlte
-blaine
Frankenbiker said:
If, like me, you despaired of CM ever releasing another "stable" version of CM-11, your wait is over.
I found out they had FINALLY done another M-SNAPSHOT code freeze, so I synced the source and built one of my own.
Link removed. Apparently we can't post links to builds any more without a full kernel code dump in the post.
If anyone is actually interested, PM me and I'll send you the link.
-blaine
Click to expand...
Click to collapse
This has been the case for as long as XDA has been GPL compliant. Any distribution of a binary (meaning kernel boot,img) that is not unmodified manufacturer's stock requires a link to kernel source, not a code dump. Anyone building CM from source should have no issues getting the link to source code and including it.
Frankenbiker said:
If, like me, you despaired of CM ever releasing another "stable" version of CM-11, your wait is over.
I found out they had FINALLY done another M-SNAPSHOT code freeze, so I synced the source and built one of my own.
http://d-h.st/aihU
Link to Kernel source (if you feel you need it)
https://github.com/CyanogenMod/android_device_samsung_msm8974-common
-blaine
Click to expand...
Click to collapse
There is no kernel source in that link. Please post proper kernel source.
Edit: Thank you for updating the link to kernel source
hi guys, we've got 5.1.1 officially but cm13, based on android 6.0, is even sweeter (doze, app permission control, etc) . did you hear any news from devs?
It looks like that Temasek and Joshndroid are already preparing an unofficial CM 13 Build for our SM-P600 Tablet.
Look at https: //github.com/temasek/android_packages_apps_Settings/commits/cm-13.0
&
https: //github.com/Joshndroid/device_samsung_lt03wifi/tree/cm-13.0-test-rebasecm12
I can tell you that the p600 will get official CM13 if @joshndroid, @ Shawn, and myself can figure out why we get a black screen after rebooting from recovery.
Sent from my SM-P600 using Tapatalk
we are trying as hard as we can. hopefully we all can come up with the goods, I have put a lot of time into it already pushing to cm's gerrit to fix broken things, but unfortunately i cant do it on my own. Shawn and orion116 are definitely assisting in getting this done, hopefully raymanfx comes to the party as well lol
joshndroid said:
we are trying as hard as we can. hopefully we all can come up with the goods, I have put a lot of time into it already pushing to cm's gerrit to fix broken things, but unfortunately i cant do it on my own. Shawn and orion116 are definitely assisting in getting this done, hopefully raymanfx comes to the party as well lol
Click to expand...
Click to collapse
How is the status? Any progress?
Stogie87 said:
How is the status? Any progress?
Click to expand...
Click to collapse
i am getting succesful builds but am getting black screen (back light turns on but nothing shows). unsure whether its kernel or vendor related or even tree related with something not activated? looking at some other device trees to see what they have changed
ok, this tricky problem still reamains. I have seen, that temasek released his second alpha build of cm 13. You don't want to use his source again for further releases?
Stogie87 said:
ok, this tricky problem still reamains. I have seen, that temasek released his second alpha build of cm 13. You don't want to use his source again for further releases?
Click to expand...
Click to collapse
best to work on the base cm rom first before working on derivatives. I will be releasing a temasek rom for cm-13.0. But we need cm-13.0 working first. More hands on a single distro makes hopefully better/lighter work. Once we get a cm happening, all the derivatives will come next so everyone wins.
SlimRoms is a custom android operating system. The main goal is to offer users a slimmed down but still feature rich alternative to other android operating systems.
The entire SlimTeam work together to bring you this tailor-made beauty straight from Android Open Source Project (AOSP) source code.
All of the sources can be publicly viewed through GitHub and you can stop by the public Gerrit to submit patches of any type.
Important links:
slimroms.org - The official webpage where you find everything you need to know about SlimRoms.
Downloads - Download the rom for S6 from here
Kernel Source - The source of your device's kernel.
Get in touch! - Contact SlimRoms at these places if you have questions, requests or feedback.
Google+
Twitter
Facebook
Thanks!
The entire team who helped with the device tree to make this device get CM. Hats off guys. Really appreciate your hard work.
For dual boot, kindly follow this link.
If you have any other queries, kindly see this link for any issues other users face before posting here.
Working and Not working:
Everything as in CM
/* Supported devices */
Galaxy S6 International (SM-G920F/I, zerofltexx)
Galaxy S6 SK (SM-G920S, zeroflteskt)
Galaxy S6 KT (SM-G920K, zerofltektt)
Disclaimer: SlimRoms are not responsible for any damages to your device.
XDA:DevDB Information
SlimRom 6.0 for Galaxy S6 , ROM for the Samsung Galaxy S6
Contributors
a2441918
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: Testing
Current Beta Version: 0.2
Beta Release Date: 2015-12-21
Created 2015-12-16
Last Updated 2015-12-23
No offense but you're the 3rd one to release a rom that has the exact same source as the original CM13 thread, and all others have been shutted down. You should invest your time helping the main branch fixing their stuff instead of dividing everybody. Releasing a ROM that is exactly the same with a different name is a total lack of respect to those who really worked hard to make this happen, plus your sources are not even public :/
virulentt said:
No offense but you're the 3rd one to release a rom that has the exact same source as the original CM13 thread, and all others have been shutted down. You should invest your time helping the main branch fixing their stuff instead of dividing everybody. Releasing a ROM that is exactly the same with a different name is a total lack of respect to those who really worked hard to make this happen, plus your sources are not even public :/
Click to expand...
Click to collapse
I have no sources. I have published the link to the kernel source. Every Rom is based off CM tree and it is not the same. Its SLIM.
a2441918 said:
I have no sources. I have published the link to the kernel source. Every Rom is based off CM tree and it is not the same. Its SLIM.
Click to expand...
Click to collapse
I'm pretty sure it's an XDA rule to publish the source of every rom/kernel. Otherwise it could contain malware/keylogger or could be fake. I took a look at SLIM's github and i didn't see anything related to the S6.
Dude you dont get it. According to XDA you should publish a source for the kernel and I did. Go ahead with the link I posted and it will direct you to the kernel source. It is not necessary that the kernel should belong to Slim.
I see no official source on your GitHub. Is this just a rebrand of CM 13 for S6?
Nevermind keep it coming
Sent from my SM-G920F using Tapatalk
bio4554 said:
I see no official source on your GitHub. Is this just a rebrand of CM 13 for S6?
Click to expand...
Click to collapse
Dude, I used Slim rom sources and this device kernel and vendor tree and built the rom. There is no need for sources in my github. And Slim and CM are different. I am not just rebranding. I am building this from source.
a2441918 said:
Dude, I used Slim rom sources and this device kernel and vendor tree and built the rom. There is no need for sources in my github. And Slim and CM are different. I am not just rebranding. I am building this from source.
Click to expand...
Click to collapse
It's like steeling the bigmac sauce's receipe to make your own burger restaurant, but saying that you use a different bread.
Omg whats the issue with you guys? I gave credit for the developers, linked to the kernel tree of the actual developer and now what is that you people need?
a2441918 said:
Omg whats the issue with you guys? I gave credit for the developers, linked to the kernel tree of the actual developer and now what is that you people need?
Click to expand...
Click to collapse
http://forum.xda-developers.com/gal...yanogenmod-13-galaxy-s6-t3269984/post64321767
Having a second ROM with same issues doesn't help at all. Why wouldn't you wait for it to be stable instead of releasing another alpha rom?
virulentt said:
http://forum.xda-developers.com/gal...yanogenmod-13-galaxy-s6-t3269984/post64321767
Having a second ROM with same issues doesn't help at all. Why wouldn't you wait for it to be stable instead of releasing another alpha rom?
Click to expand...
Click to collapse
You could have pointed that out in the first post itself rather than us spamming this thread. I will remove the download link and keep this thread closed for now.
virulentt said:
I'm pretty sure it's an XDA rule to publish the source of every rom/kernel. Otherwise it could contain malware/keylogger or could be fake. I took a look at SLIM's github and i didn't see anything related to the S6.
Click to expand...
Click to collapse
The only source required to be posted by GPLv2 and XDA requirements is kernel source. Also Slim and CM both have posted open permissions to build.
New build up. See OP for download link.
Download Link is dead for me.
a2441918 said:
New build up. See OP for download link.
Click to expand...
Click to collapse
ripv2 said:
Download Link is dead for me.
Click to expand...
Click to collapse
Try it out now mate.
Up and reachable Ill give it a shot!
a2441918 said:
Try it out now mate.
Click to expand...
Click to collapse
Any changelog ? and is this usable for edge version ? or it has same screen issue ?
bigbossclk said:
Any changelog ? and is this usable for edge version ? or it has same screen issue ?
Click to expand...
Click to collapse
I guess its usable. But a different build for S6 Edge is in the works.
Doesnt Boot on my 920f latest recovery clean install with and without gapps. Never finnishing Boot animation.
Hi,
this is the development thread for LineageOS development. The first release is out and this thread is for developer collaboration!
Everyone who knows C, Java and strace is welcome to participate. Please send git formatted patches!
HELP NEEDED
mixer_paths_tasha.xml and audio_platform_info.xml need tweaking
VoIP needs testing
WifiDisplay support
VoLTE (I can't test this)
Device Trees
https://github.com/cryptomilk/android_kernel_sony_msm8998
https://github.com/cryptomilk/android_device_sony_common-treble
https://github.com/cryptomilk/android_device_sony_yoshino
https://github.com/cryptomilk/android_device_sony_lilac
What about the bootloader?
blackknightavalon said:
What about the bootloader?
Click to expand...
Click to collapse
Just unlock it and have fun. Hopefully someone will be able to figure out a way to backup the DRM keys.
android_fury said:
Just unlock it and have fun. Hopefully someone will be able to figure out a way to backup the DRM keys.
Click to expand...
Click to collapse
And where, exactly, is the tutorial for that? It's not officially supported by Sony yet.
I think I read somewhere that you can select the XZ Premium on the list and follow the steps. Once a DRM backup is available, I may try doing that. By then, the actual XZ1C may already be on the list.
android_fury said:
I think I read somewhere that you can select the XZ Premium on the list and follow the steps. Once a DRM backup is available, I may try doing that. By then, the actual XZ1C may already be on the list.
Click to expand...
Click to collapse
I just checked a few minutes ago. XZ1C's not on there.
Good news ！
I've setup initial repositories, yoshino and lilac. yoshino is a common base shared between devices and I have a Kernel tree over the latest msm-4.0 kernel tree and already compiled it after fixing a log of build issues. I will create repositories in the next days and upload the sources once I have a recovery.
modpunk said:
I've setup initial repositories, yoshino and lilac. yoshino is a common base shared between devices and I have a Kernel tree over the latest msm-4.0 kernel tree and already compiled it after fixing a log of build issues. I will create repositories in the next days and upload the sources once I have a recovery.
Click to expand...
Click to collapse
Great news! Thank you so much for your efforts to bring us LOS for this really awesome compact beast.
Thank you so far, modpunk! Looking forward to it. The phone is great, but stock rom leaves some things to be desired...
Thanks bro, just do it!
Regarding unlocking: I selected X Compact and followed the instructions. Everything worked perfectly and I'm now running AOSP.
Code:
----- Made recovery image: recovery.img --------
#### make completed successfully (11:06 (mm:ss)) ####
modpunk said:
I've setup initial repositories, yoshino and lilac. yoshino is a common base shared between devices and I have a Kernel tree over the latest msm-4.0 kernel tree and already compiled it after fixing a log of build issues. I will create repositories in the next days and upload the sources once I have a recovery.
Click to expand...
Click to collapse
How much are you borrowing from Sony's AOSP repositories? They've been committing pretty heavily to their kernel in particular.
Gairtial said:
How much are you borrowing from Sony's AOSP repositories? They've been committing pretty heavily to their kernel in particular.
Click to expand...
Click to collapse
There was no Kernel release for msm8998 in kernel-copyleft, so I took the msm-4.4 Kernel tree and the tarball they dropped. I've fixed several bugs in the Kernel, I always wonder how the Smartphone manufacturers get their stuff compiled.
You can find the kernel source tree here: https://github.com/cryptomilk/android_kernel_sony_msm8998
I've also added exfat support already.
I've looked at the device repo for their AOSP trees, but started a yoshino and lilac device tree from scratch. I prefer clean repositories. I will push them in the next days, I did quite some cleanup today.
I haven't ordered the device yet. Need to wait till next week, I just came back from a long vacation
modpunk said:
There was no Kernel release for msm8998 in kernel-copyleft, so I took the msm-4.4 Kernel tree and the tarball they dropped. I've fixed several bugs in the Kernel, I always wonder how the Smartphone manufacturers get their stuff compiled.
You can find the kernel source tree here: https://github.com/cryptomilk/android_kernel_sony_msm8998
I've also added exfat support already.
I've looked at the device repo for their AOSP trees, but started a yoshino and lilac device tree from scratch. I prefer clean repositories. I will push them in the next days, I did quite some cleanup today.
I haven't ordered the device yet. Need to wait till next week, I just came back from a long vacation
Click to expand...
Click to collapse
Why the copyleft archive? It doesn't look like they've touched it since April while they touched the regular one 2 hours ago.
I had no issues compiling and running the kernel from https://github.com/sonyxperiadev/kernel, though that was integrated with their entire AOSP tree, which seems to package its own versions of gcc and clang. Perhaps LineageOS includes different prebuilt compilers and that's why you see issues.
Really curious to see how LOS runs though. AOSP has some annoying performance issues and crashes.
Gairtial said:
Why the copyleft archive? It doesn't look like they've touched it since April while they touched the regular one 2 hours ago.
I had no issues compiling and running the kernel from https://github.com/sonyxperiadev/kernel, though that was integrated with their entire AOSP tree, which seems to package its own versions of gcc and clang. Perhaps LineageOS includes different prebuilt compilers and that's why you see issues.
Really curious to see how LOS runs though. AOSP has some annoying performance issues and crashes.
Click to expand...
Click to collapse
I've just tried to build the aosp/LA.UM.5.7.r1 tree from the sony kernel repo. This one has a lot of compiler errors which need fixing first. However for me it looks like that the msm-4.4 tree is much cleaner in this regard so maybe also more advanced.
modpunk said:
I've just tried to build the aosp/LA.UM.5.7.r1 tree from the sony kernel repo. This one has a lot of compiler errors which need fixing first. However for me it looks like that the msm-4.4 tree is much cleaner in this regard so maybe also more advanced.
Click to expand...
Click to collapse
Also fellow LineageOS developers said that the sony 'kernel' repo is a Proof of Concept repo and not what they use in production. So I stick to the production release of MSM.
modpunk said:
I've just tried to build the aosp/LA.UM.5.7.r1 tree from the sony kernel repo. This one has a lot of compiler errors which need fixing first. However for me it looks like that the msm-4.4 tree is much cleaner in this regard so maybe also more advanced.
Click to expand...
Click to collapse
Huh, what kinds of errors are you seeing? I really suspect it must be something different between LOS and AOSP and I'm wondering what it is.
modpunk said:
Also fellow LineageOS developers said that the sony 'kernel' repo is a Proof of Concept repo and not what they use in production. So I stick to the production release of MSM.
Click to expand...
Click to collapse
This may be true but it's also the repo where the most work is done. We should at least pay attention to it in case they commit fixes that are useful.
Also probably getting ahead of myself but I wonder if we can merge EAS... It's in AOSP's common kernel, is it around in LOS anywhere yet?
Gairtial said:
Huh, what kinds of errors are you seeing? I really suspect it must be something different between LOS and AOSP and I'm wondering what it is.
This may be true but it's also the repo where the most work is done. We should at least pay attention to it in case they commit fixes that are useful.
Also probably getting ahead of myself but I wonder if we can merge EAS... It's in AOSP's common kernel, is it around in LOS anywhere yet?
Click to expand...
Click to collapse
You get the errors with -Wmaybe-uninitialized which is a relatively new gcc feature. The Sony 'kernel' repo is their Proof of Concept repository. Yes, sure they are working on it it makes totally sense to try things out there first!
I dunno what EAS is or means ...