Link: opensource*le*com
Replace * with .
As I am new xda isn't allowing to post link directly.
(I already posted this but reposting in this section as it might be helpful for the developers.)
Btw anyone having any idea if project treble will be supported for le x526 in future.
Related
@Darth @Heisenberg Open source is right For all :/ I learned from xda and if you all remember I had my first thread closed for it too. (Kernel thread) .... Well let's stop the intro and talk straight this Thread by @ED300 Cm13.0 by ed300 has all Obsolete and Non updated sources It doesn't even contains device tree :/ and Obsolate Kernel tree too if you check his kernel Compiled date. plus Vendor By floromu has no camera vendor And Blobs As well for adreno blah blah one have to use openssl concept for it ... That means the sources on ops thered are either not updated and I remember I read somewhere that GPL sources should be published but why op @ED300 didnt ? That's sad ! Am I fool trying to make Device tree from Lettuce Jalebi and Make ROMs For this device and open source it for public I just want to ask that when I will be able to see the correct device tree and Vendor source :/ on our OPs thread first of all let me Make few things clear Latest sources By Floromu 6-7month old are way obsolete than cm structure latest Structure is here check this
Link :- https://gitlab.com/dev-harsh1998/android_device_lenovo_a6000/tree/master
Well that means ROM can't be compiled On Floromu's tree
And as Says our op has elberry 6 latest Patch interesting
point 2:- Kernel sources :- dated 6 months old
Compiled Date xyz with unlocked freqs and wake Gesture.
I have No hate For @ED300 I just want our op to opemsource his GPL things And follow proper Rules
Sir,
You've reported nothing on this, using the proper report system. Also, accusations like this tend to fall under rule 12 here, http://forum.xda-developers.com/announcement.php?a=81
Have you privately brought this up to the person you're accusing? Did it not lead anywhere?
Then gather clear evidence and click report on the OP of the thread in question. That is the proper way to handle these things .
Creating drama in threads, or opening a thread like this is NOT how to handle these situations. And accusing mods and xda of not caring? Yet you've not followed the steps above? That's ridiculous I'd have to say.
Read rule 12, follow procedures listed and if you report it, bring evidence.
This thread is closed. And please don't stir up drama publicly in the future. :good:
Darth
Senior Moderator
dev_harsh1998 said:
@Darth @Heisenberg Open source is right For all :/ I learned from xda and if you all remember I had my first thread closed for it too. (Kernel thread) .... Well let's stop the intro and talk straight this Thread by @ED300 Cm13.0 by ed300 has all Obsolete and Non updated sources It doesn't even contains device tree :/ and Obsolate Kernel tree too if you check his kernel Compiled date. plus Vendor By floromu has no camera vendor And Blobs As well for adreno blah blah one have to use openssl concept for it ... That means the sources on ops thered are either not updated and I remember I read somewhere that GPL sources should be published but why op @ED300 didnt ? That's sad ! Am I fool trying to make Device tree from Lettuce Jalebi and Make ROMs For this device and open source it for public I just want to ask that when I will be able to see the correct device tree and Vendor source :/ on our OPs thread first of all let me Make few things clear Latest sources By Floromu 6-7month old are way obsolete than cm structure latest Structure is here check this
Link :- https://gitlab.com/dev-harsh1998/android_device_lenovo_a6000/tree/master
Well that means ROM can't be compiled On Floromu's tree
And as Says our op has elberry 6 latest Patch interesting
point 2:- Kernel sources :- dated 6 months old
Compiled Date xyz with unlocked freqs and wake Gesture.
I have No hate For @ED300 I just want our op to opemsource his GPL things And follow proper Rules
Click to expand...
Click to collapse
Also,
XDA doesn't require things like vendor files and device trees to be published, as they are not licensed under the GPL but rather Apache 2.0 (like the rest of Android). Apache allows you to close source things if you want, there is no publishing requirement, just that you still have the license applied to the file. Only kernel source is required to be published due to GPL.
Thanks @nathanchance :good:
@Darth @Heisenberg Open source is right For all :/ I learned from xda and if you all remember I had my first thread closed for it too. (Kernel thread) .... Well let's stop the intro and talk straight this Thread by @ED300 Cm13.0 by ed300 has all Obsolete and Non updated sources It doesn't even contains device tree :/ and Obsolate Kernel tree too if you check his kernel Compiled date. plus Vendor By floromu has no camera vendor And Blobs As well for adreno blah blah one have to use openssl concept for it ... That means the sources on ops thered are either not updated and I remember I read somewhere that GPL sources should be published but why op @ED300 didnt ? That's sad ! Am I fool trying to make Device tree from Lettuce Jalebi and Make ROMs For this device and open source it for public I just want to ask that when I will be able to see the correct device tree and Vendor source :/ on our OPs thread first of all let me Make few things clear Latest sources By Floromu 6-7month old are way obsolete than cm structure latest Structure is here check this
Link :- https://gitlab.com/dev-harsh1998/android_device_lenovo_a6000/tree/master
Well that means ROM can't be compiled On Floromu's tree
And as Says our op has elberry 6 latest Patch interesting
point 2:- Kernel sources :- dated 6 months old
Compiled Date xyz with unlocked freqs and wake Gesture.
I have No hate For @ED300 I just want our op to opemsource his GPL things And follow proper Rules
3 threads on same thing? Please don't create anymore. And see my reply here,
http://forum.xda-developers.com/len...-dont-mods-care-anymore-t3438745#post68173815
Thread closed.
@Darth @Heisenberg Open source is right For all :/ I learned from xda and if you all remember I had my first thread closed for it too. (Kernel thread) .... Well let's stop the intro and talk straight this Thread by @ED300 Cm13.0 by ed300 has all Obsolete and Non updated sources It doesn't even contains device tree :/ and Obsolate Kernel tree too if you check his kernel Compiled date. plus Vendor By floromu has no camera vendor And Blobs As well for adreno blah blah one have to use openssl concept for it ... That means the sources on ops thered are either not updated and I remember I read somewhere that GPL sources should be published but why op @ED300 didnt ? That's sad ! Am I fool trying to make Device tree from Lettuce Jalebi and Make ROMs For this device and open source it for public I just want to ask that when I will be able to see the correct device tree and Vendor source :/ on our OPs thread first of all let me Make few things clear Latest sources By Floromu 6-7month old are way obsolete than cm structure latest Structure is here check this
Link :- https://gitlab.com/dev-harsh1998/android_device_lenovo_a6000/tree/master
Well that means ROM can't be compiled On Floromu's tree
And as Says our op has elberry 6 latest Patch interesting
point 2:- Kernel sources :- dated 6 months old
Compiled Date xyz with unlocked freqs and wake Gesture.
I have No hate For @ED300 I just want our op to opemsource his GPL things And follow proper Rules
Ignore mistakes I am not good at English
3 threads on same thing? Please don't create anymore. And see my reply here,
http://forum.xda-developers.com/len...-dont-mods-care-anymore-t3438745#post68173815
Thread closed.
official sources released
Link : opensource.le.com
Start development
Give your replies don't just view the post
they have removed the files now...
here is a link for them (from letv.re)
LINK: drive.google.com/open?id=0B4vs8obBaVjPd25XQkZaR2NaZkU
Hi, I'm making this thread to centralize and make easier for devs to work on ZUK Z2(standard).
NOTE: Z2131 & Z2132 are the SAME device, just name and ZUI version different. So ROMs and Kernels are usable by both side, it's the same for ZUK Z2 Rio which is the lower storage z2(3/32)
There are many links and resources, but if you're a Dev who works on this device contact me in private, there is a group for all the devs, indeed Fedor917, Davidenavil, CallMeSuper, Flour_Mo, Frencesco Colella, Leo, scafroglia93 and Franko76 are working in that group.
Source Code by ZUK
LINK ALREADY WITH TRANSLATION
(The source of z2131(CN) & z2132(Indian) ZUIs can be found on the right list)
Dev's profiles for ZUK Z2 repositories:
https://github.com/Silentlys
https://github.com/cryscript
https://github.com/davidevinavil
https://coding.net/u/CallMESuper
https://github.com/mnemonyc
https://github.com/scafroglia93
https://github.com/zuk2plus
Kernel
https://github.com/Silentlys/android_kernel_zuk_msm8996 (original one)
https://github.com/scafroglia93/android_kernel_zuk_msm8996 (the most updated stock)
https://coding.net/u/CallMESuper/p/android_kernel_zuk_z2_plus/git (M-Kernel source)
https://github.com/cryscript/android_kernel_zuk_msm8996
Vendor
https://github.com/cryscript/android_vendor_zuk_z2_plus
https://github.com/davidevinavil/android_vendor_zuk_z2
https://github.com/zuk2plus/android_vendor_zuk_z2plus
Android Device
https://github.com/cryscript/android_device_zuk_z2_plus
https://github.com/davidevinavil/android_device_zuk_z2
https://github.com/Silentlys/android_device_zuk_z2
DualBootPatcher source
https://github.com/cryscript/DualBootPatcher
Hi KronozFX,
Thank you for the link!
I'm trying to compiling a kernel for CM14.1(Lineage OS now), which kernel should I use then?
Thank you!
riaqn said:
Hi KronozFX,
Thank you for the link!
I'm trying to compiling a kernel for CM14.1(Lineage OS now), which kernel should I use then?
Thank you!
Click to expand...
Click to collapse
U can find it on https://github.com/LineageOS
Just search for your chipset