Related
Cyanogenmod has released the device specific Sources
Device Tree : https://github.com/YUPlayGod/android_device_yu_tomato
Kernel Source : https://github.com/YUPlayGod/android_kernel_yu_msm8916
Get ready for the development that is about to begin with the Kernel Source Codes.
Many ROM's And Custom Kernel's Are On The Way To Play With The God :angel:
is there any way to change F2SF to ext4 to compile rom with ext4 partitions?
I got the device dude tell me how to get the vendor source i will get if for you
janajackie said:
I got the device dude tell me how to get the vendor source i will get if for you
Click to expand...
Click to collapse
Don't Worry My Friend I've Got The Vendor Blobs And Yu Yureka Will Get Custom ROM's And Kernel's Soon From My End!
What would it take to see a base AOSP ROM put together for the LG G4? I know there's some folks working hard at bringing CM to the G4, but what about an AOSP unmodified ROM with drivers, of course? I've always wondered if that is a better option than say a ROM like CM which has loads of known bugs and issues.
Maybe an AOSP super-stock setup which we could modify after via Xposed / Mods to add in what we want would be a better option?
CJ-Wylde said:
What would it take to see a base AOSP ROM put together for the LG G4? I know there's some folks working hard at bringing CM to the G4, but what about an AOSP unmodified ROM with drivers, of course? I've always wondered if that is a better option than say a ROM like CM which has loads of known bugs and issues.
Maybe an AOSP super-stock setup which we could modify after via Xposed / Mods to add in what we want would be a better option?
Click to expand...
Click to collapse
After we finish the device tree and everything is working, it can be then used to build whatever Rom you desire
You rock, thank you for the quick response! I'm not even sure what kind of rom I desire. I just know it would be neat to go full on basic AOSP and add from there without some of the clutter and bugs introduced with CM's stuff, although CM has always been an enjoyable experience. Whoot for guys like you!
I know this is old thread... but what source tree are we talking about here? Obviously not AOSP itself, i think... right?
CM source?
Maybe i'm missing something about branches of AOSP... and other trees..
many thanks
mythos234 said:
After we finish the device tree and everything is working, it can be then used to build whatever Rom you desire
Click to expand...
Click to collapse
thenextdon13 said:
I know this is old thread... but what source tree are we talking about here? Obviously not AOSP itself, i think... right?
CM source?
Maybe i'm missing something about branches of AOSP... and other trees..
many thanks
Click to expand...
Click to collapse
They talked about device tree here. An example for a pure AOSP one for the device LG H815 is here:
https://github.com/cile381/android_device_h815
See this for an explanation :
http://wp.me/p6ZeCY-3p
AOSP source contains the sources to build a ROM which are the same for all devices and a device tree is a device specific description on how to build or as the above link states:
“A device tree is a tree data structure with nodes that describe the physical devices in a system”
.
Sent from my LG-H815 using XDA Labs
Thank you, steadfasterX.
That provides some clarity, although I think there is still a bit missing for me--
Ugh, i can't post links because of spam rules.. :-/ makes describing things harder.
How did you find the github cile381/android_device_h815 as being the AOSP tree for that phone? My understanding was that the AOSP main repo is here:
android.googlesource.com
And so related to my question previously.. i guess i'm confused specifically who the 'we' is that mythos234 references, and where that source would be located...
many thanks!
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.
Resurrection RemixResurrection Remix ROM is the ultimate full featured, stable rom combined with the best features of open source roms .
We are also providing lot of awesome original Resurrection Remix ROM add-ons in the builds. It includes the best of performance, customization, power and the newest features on your device! It is one of the most customizable ROMs out-of-the-box!
This version is almost the same as official one
But, without "Lucky" Control
Last Build is here: https://drive.google.com/open?id=0B57Q-f4sogZ_YjhDVFhGcExCWGs
Sources:
https://github.com/ResurrectionRemix
https://github.com/murigny64/proprietary_vendor_motorola-RR
Enjoy :fingers-crossed:
Thanks!!!
What's lucky control btw?
Droidphilev said:
Thanks!!!
What's lucky control btw?
Click to expand...
Click to collapse
Look at official RR thread and find "lucky"
Droidphilev said:
Thanks!!!
What's lucky control btw?
Click to expand...
Click to collapse
murigny64 said:
Look at official RR thread and find "lucky"
Click to expand...
Click to collapse
If you're referring to "Lucky Patcher detection" which Silesh uses in InvictaOS, than unless it's in RR sources officially, it's not in my official builds either. Also, unless you're using my device and kernel trees, and are compiling the kernel with Linaro, than these builds aren't the same as mine. If anything, I would assume they're the same as ///TheNexus/// nightly builds.
Jleeblanch said:
If you're referring to "Lucky Patcher detection" which Silesh uses in InvictaOS, than unless it's in RR sources officially, it's not in my official builds either. Also, unless you're using my device and kernel trees, and are compiling the kernel with Linaro, than these builds aren't the same as mine. If anything, I would assume they're the same as ///TheNexus/// nightly builds.
Click to expand...
Click to collapse
Sources are only official RR and modified Themuppets vendor tree.
Don't know about yours. Sorry, I thought you had to keep this functionality from silesh.
So, my build is useless.
murigny64 said:
Sources are only official RR and modified Themuppets vendor tree.
Don't know about yours. Sorry, I thought you had to keep this functionality from silesh.
So, my build is useless.
Click to expand...
Click to collapse
No worries! Silesh uses his own tweaked device tree and MM kernel in his builds. When I took over, I switched over to Lineage trees. I have a few extra commits here and there but nothing too serious and the only commits I've made in the vendor tree (at this time) is for the removal of "Device is HD Capable" notification that everyone hates lol.
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 ...