Related
I just sent them this
Code:
Hello,
kernel source for 1.29 and 2.05 for HTC One X is still not available.
These delays are hindering community efforts to fix your inept software and are in breach of GPL. Please provide me the link to the source to to those 2 kernels and make sure that you release the source at the same time as the binary form.
I am ready to escalate this via gpl-violations.org unless your response satisfies me.
Regards
Jan Schermer
If anybody wants to chime in, you're welcome.
Samsung is just better at this.. look at the SIII it was released after the OneX but it has many many more custom truly cocked roms!
And i'm sick of such useless posts. They will release it when they will release it. Get a life.
Why would they publish the source for a test RUU? 1.29 OK but not 2.05 yet
zvieratko said:
I just sent them this
Code:
Hello,
kernel source for 1.29 and 2.05 for HTC One X is still not available.
These delays are hindering community efforts to fix your inept software and are in breach of GPL. Please provide me the link to the source to to those 2 kernels and make sure that you release the source at the same time as the binary form.
I am ready to escalate this via gpl-violations.org unless your response satisfies me.
Regards
Jan Schermer
If anybody wants to chime in, you're welcome.
Click to expand...
Click to collapse
you forgot one main thing
2.05 is unreleased and leaked
And now no more leaked test releases lol.
Well done!!! Demand source codes for versions that aren't even released yet.
Lmao what is going on here
Sent from eXoDiZeD rom
They have to provide source code for every binary to those who got the binary. So I assume those 2.05 testers have the source for their kernels, don't they? if they did, it would leak, and we would profit from it (it's our right because so does HTC!).
Also, what devs here do is illegal - I could demand the source code from them but they don't have it - is it okay to force them into illegality just because HTC are being ignorant?
And those posts are not meaningless, they are violating GPL and withholding source code for no real reason. All source-built kernels are still based on 1.28, but they fixed a lot of stuff on 1.29, and for me (a linux professional) those hacks show in lots of places.
What are you doing here if you really want HTC-built Sense then? Do you want to run slapped-together binary ROMs because there is no source for the latest update? This is called Android Development for a reason.
zvieratko said:
They have to provide source code for every binary to those who got the binary. So I assume those 2.05 testers have the source for their kernels, don't they? if they did, it would leak, and we would profit from it (it's our right because so does HTC!).
Also, what devs here do is illegal - I could demand the source code from them but they don't have it - is it okay to force them into illegality just because HTC are being ignorant?
And those posts are not meaningless, they are violating GPL and withholding source code for no real reason. All source-built kernels are still based on 1.28, but they fixed a lot of stuff on 1.29, and for me (a linux professional) those hacks show in lots of places.
What are you doing here if you really want HTC-built Sense then? Do you want to run slapped-together binary ROMs because there is no source for the latest update? This is called Android Development for a reason.
Click to expand...
Click to collapse
you can not demand anything from an internal leaked file! in fact your possession of the leaked rom might be illegal lol
hamdir said:
you can not demand anything from an internal leaked file! in fact your possession of the leaked rom might be illegal lol
Click to expand...
Click to collapse
That might be true. But AFAIK the 2.05 RUU was provided to some public testers as well.
I just opted to demand 2.05 as well in case it takes them a month to respond and it will be released by then, it did no harm in any case.
Also, we wouldn't have to have this debate if the development was actually transparent (that means - HTC working with community, not just pushing uncompilable sources for their old kernels). But I guess most managers can't grasp that concept without the proper buzzwords.
Sorry, I'm pissed at many more things than just HTC right now, but I directed my anger here
zvieratko said:
They have to provide source code for every binary to those who got the binary. So I assume those 2.05 testers have the source for their kernels, don't they? if they did, it would leak, and we would profit from it (it's our right because so does HTC!)....
Click to expand...
Click to collapse
You can demand open source codes not closed source and to get open source android, simply get AOSP sources. HTC will publish their sources when they want and after they finish.
EOT.
AdamLange said:
You can demand open source codes not closed source and to get open source android, simply get AOSP sources. HTC will publish their sources when they want and after they finish.
EOT.
Click to expand...
Click to collapse
You know that kernel is GPL and what that means, right? Or are you just trolling? HTC is obliged to provide source code - it's not a goodwill gesture, and they consistently fail to do that.
Or are you talking just about 2.05? In that case, the first tester outside HTC should get the source code and would be free to release it to us - closed beta or not.
Some parts of kernel may be closed (for example modules). They can post kernel without them. Its like AOSP android, you can download it, and compile and use, but you will not get Android Apps (gmail,youtube etc) included. cause they are CLOSED.
AdamLange said:
Some parts of kernel may be closed (for example modules). They can post kernel without them. Its like AOSP android, you can download it, and compile and use, but you will not get Android Apps (gmail,youtube etc) included. cause they are CLOSED.
Click to expand...
Click to collapse
Yes, but they don't even post the sources without blobs...
sorr932 said:
Samsung is just better at this.. look at the SIII it was released after the OneX but it has many many more custom truly cocked roms!
Click to expand...
Click to collapse
Pmsl
TRULY COCKED ROMS
pro tip, if you don't act like a self-entitled brat when asking for something which they are required todo you are more likely to get an informed helpful response.
if that really is the email that you sent I wouldn't be surprised if it was just moved to the email bin
AdamLange said:
And i'm sick of such useless posts. They will release it when they will release it. Get a life.
Click to expand...
Click to collapse
+1:good:
Patrick Volkerdings: Its finished if its finished
sorr932 said:
Samsung is just better at this.. look at the SIII it was released after the OneX but it has many many more custom truly cocked roms!
Click to expand...
Click to collapse
Frankly ,they can have x3 more custom rom`s but we have one who is better then all SIII ROM`s together , we are so lucky and really need to be proud with our original developers like Venom Team , so S3 performance without ROM like our ViperX is in vain.
Don`t worry be happy! :victory:
Thread now closed. This thread has become off topic. I have had to remove a couple of posts that had bad language. Remember people to follow XDA rules when posting.
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 all,
I've created an issue on Motorola's kernel-msm repo that is a request for them to release the kernel sources for the G 5 Plus (Potter).
The post is here - https://github.com/MotorolaMobilityLLC/kernel-msm/issues/104
Please feel free to reply with similar requests so as to get Motorola moving on a proper GPL source release.
-Rob
bob2600 said:
Hi all,
I've created an issue on Motorola's kernel-msm repo that is a request for them to release the kernel sources for the G 5 Plus (Potter).
The post is here - https://github.com/MotorolaMobilityLLC/kernel-msm/issues/104
Please feel free to reply with similar requests so as to get Motorola moving on a proper GPL source release.
-Rob
Click to expand...
Click to collapse
https://github.com/MotorolaMobilityLLC/kernel-msm/blob/MMI-NPN25.137-15/arch/arm/configs/ext_config/mot8953-potter.config
:good:
The sources are already out....
Oh really? My bad... Can I just pull from that kernel-msm repo mentioned in the original post? Or is there a different repo just for Potter?
It looks like the source release for NPN25.137-15 is tagged here:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-NPN25.137-15/
It's a bit older than the version shipped with my phone but it could work. I'm going to see if I can compile it later.
bob2600 said:
It looks like the source release for NPN25.137-15 is tagged here:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/MMI-NPN25.137-15/
It's a bit older than the version shipped with my phone but it could work. I'm going to see if I can compile it later.
Click to expand...
Click to collapse
All the best. :good:
rayzen6 said:
All the best. :good:
Click to expand...
Click to collapse
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
bob2600 said:
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
Click to expand...
Click to collapse
Man yes let me mention the guy who successfully able to build with Alberto's sources. He is @i.snehal.kiran.
He has done this to compile but unfortunately for some reason he doesn't able to get the device to test. His msg is below
basically i have taken addison device tree ...just change the kernel path and defconfig name in boradconfig.mk ..makes it build boot.img
the source provided by motorola on github is full of errors..so use alberto's kernel for addison till you get official kernel from moto
https://github.com/Alberto97/android_kernel_motorola_msm8953
I edited the post bcz I thought u want to work with custom kernel for stock rom. And I thought this might not be useful.
bob2600 said:
Why'd you edit your post? I took a look at Alberto's repo and it looks like it would be compatible with our phones.
Seemed like a decent course of action to take. Did you try it yourself? Did it work? Don't just provide no reason, let's get hacking...
Click to expand...
Click to collapse
So what happened next? Did you tried something?
Edit:- btw one of the guy has replied positively on issue. :Good: I think we'll have a separate source soon.
rayzen6 said:
So what happened next? Did you tried something?
Edit:- btw one of the guy has replied positively on issue. :Good: I think we'll have a separate source soon.
Click to expand...
Click to collapse
I got as far as getting the LineageOS sources pulled for 14.1, had to do it twice since it was too big for my home directory so I had to create a new volume and run repo sync again. Took forever, but at least I have the OS sources downloaded. Now we're at the point of getting that kernel and setting up a device configuration for our device. Once we get that, then I can see if we can build and flash.
bob2600 said:
I got as far as getting the LineageOS sources pulled for 14.1, had to do it twice since it was too big for my home directory so I had to create a new volume and run repo sync again. Took forever, but at least I have the OS sources downloaded. Now we're at the point of getting that kernel and setting up a device configuration for our device. Once we get that, then I can see if we can build and flash.
Click to expand...
Click to collapse
Cool. Good work man. I'm in for testing.
Kernel sources are up
https://github.com/MotorolaMobilityLLC/kernel-msm/releases/tag/MMI-NPN25.137-33
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 ...
Was wondering if anybody has worked on any type of a redmi 7 rom based on lineage since we just got a twrp solution.
My boot loader is going to be unlocked in 12 days, so if any developers are working on anything let me know and i can test it out.
Thanks!
Devs need from Xiaomi to open source the kernel at least to make things easier.
It is good that we are having TWRP now without source code.
The phone is still very new and it is already catching a lot of development attention.
mylove90 said:
Devs need from Xiaomi to open source the kernel at least to make things easier.
It is good that we are having TWRP now without source code.
The phone is still very new and it is already catching a lot of development attention.
Click to expand...
Click to collapse
Does xiaomi have a track record on how long they give an open source kernal?
mylove90 said:
Devs need from Xiaomi to open source the kernel at least to make things easier.
It is good that we are having TWRP now without source code.
The phone is still very new and it is already catching a lot of development attention.
Click to expand...
Click to collapse
Agreed. I'm waiting to build it too
Kernel to be open-sourced by the end of this month
My estimate is that the kernel will be open-sourced around the 20th of May, hopefully. I've got all the gear ready to build a custom ROM, for a Redmi device, for the first time. I'm looking to build Lineage (but I don't know whether I'd succeed). I got the device on the 8th of May, and still waiting for that 360h to go by, as my bootloader is still locked. In the meantime, I'm looking for what else I can try out!
looks like the kernel source is released
kernel source are released already
Anyone was courage enough to try to compile the kernel source on his own ?
The sources released are not official or final.
The sources released doesn't compile as is and some fixing because of some errors.