Kernel Sources released!! - Spice Dream Uno

Let us all petition Spice Mobile and Mediatek to release kernel sources!!
Visit THIS thread (remember to thank the OP)
We don't just want stock Android L now, do we??
EDIT: So, kernel sources HAVE been pushed...See this LINK

The Dork Knight Rises said:
Let us all petition Spice Mobile and Mediatek to release kernel sources!!
Visit THIS thread (remember to thank the OP)
We don't just want stock Android L now, do we??
EDIT: So, kernel sources HAVE been pushed...See this LINK
Click to expand...
Click to collapse
We Can't Live Without CM's and Custom Kernels! I'm With ya!

Neither can I CM ! is what we need !

Related

[WIP] [CM12] [DEVS ONLY] Cyanogenmod 12 for Moto G (2nd Gen)

Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
N.K.V. said:
Okay Guys,
I am working hard to bring up Cyanogenmod to our beloved moto g.
But i am a bit Noobish in this field.
I have been reading guides and following the process.
So far I have setup the build environment and synced the latest repo from CM sources.
Now, further most imp step is Vendor, Kernal and Device tree.
I have found this so far, by searching this forum only,
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/kitkat-4.4.4-release-titan
Now, reading further some guides, they say kernel and device tree will require some modification to work with CM12, but i couldnt find about this modification.
so I request all developers to guide me on this.
We can surely do this together. :fingers-crossed:
Click to expand...
Click to collapse
I love your initiative! Unfortunately I'm not a developer...
Send from my XT1068 using Tapatalk.
nice work mate.... developers are needed urgently....
Why do you think developers will find you and this thread? It works the other way. You need to find developers and ask for help. I suggest you start here and here
I keep my fingers crossed for the success of the project :highfive:
Yes, I am reading all possible guides given by the developers.
By that only i have reach this far.
But for device tree and kernel, device specific modifications are necessary, and I really need help of some one who has actually done this before.
If this is successful , we can have an alpha build of CM 12 , in 3-4 days.
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
k2wl said:
@ N.K.V.
ok i will help you with this..
first we need to set up device tree and vendor trees....
there is 2 ways to do this
first:- get a official motorola stock lollipop update for your phone.
(unfortunately it not yet released for all variants)
examine the similar device trees like falcon or htc a5 (desire 816) of lg l90 or sony m2 or sony e3
compare the kernel sources of falcon and titan (these are kitkat sources so may be in future motorola will release updated lollipop kernel source)
there are various major differences.
set up a basic device tree from falcon with msm8226 common of cm repos.
take vendor blob list from falcon
adapt it for titan
extract vendor blob from phone.
compile the rom
second:- from existing 4.4.4 rom
repo sync kernel from github
make changes to falcon and msm8226 device tree to adapt titan
extract vendor blobs with falcon list
compile
problem with second approach is that you have to make many changes to kernel and other things
but if we get official moto update of lollipop with kernel source then it will be little easier...
still if you are going to compile and want to make a cm12 from 4.4.4 i am with you ...i will set up device trees and other trees to set up things in motion.....
and then we can change vendor blobs and kernel to lollipop when it get released...
Click to expand...
Click to collapse
This is great news. A team effort can do anything.:good:
Thanks to NKV and Kewl. Great initiative. God Bless You.
Sent from my Nexus 7 using XDA Free mobile app
okay guys,
let's keep this thread clean for developers.
you can always hit like to appreciate
UPDATE: @k2wl is working on kernel and device tree, it will take him some days.
@k2wl and N.K.V.
Thx for your time and work :good:
I wait for the right Software on xt1068!
I have a little bit of knowledge and i can learn really fast, if you guys need help, you can count on me
which model will this be for? (please say xt1064)
Bobboman said:
which model will this be for? (please say xt1064)
Click to expand...
Click to collapse
Doesn't matter. It will be for all variants!
absolutely brilliant, i wish i knew a lick of programming so that i could help get this done faster (i'm tired of seeing a SU update in play store and not being able to use it because it sends my G into a bootloop)
Thanks man, lollipop official update have a bug while playing music via bluetooth when screen is lock, can you fix it on this rom?
Ha ha...Let's make the ROM first..
Bug fixing in Second task.
Now that lollipop soak has started in India....i think Work should go fast. :beer:
Waiting for it. Please keep updated though!
I'm interested in helping with this.
Sent from my A0001 using XDA Free mobile app
Hope to See this soon! Thanks guys!!
Nice intitiative...but i think making device tree and vendor for this device will not be tht easy....still hope for best

[Github Organization] Xiaomi Hermes Devs

Hello devs, I think before to split some developers for own project to regroup all ppl want and can working on this device to one place.
The only requeriment are working with apache v2 license (much better gnu because is required to post credits) or any derivate.
For a moment I create this on github, I send the invite to the best developer in this moment (nofearnohappy) and when him give time to reply to me to loki, everyone want partecipate it's free to write here, I'm happy to add to this group for share our knowedge
I love the opensource and I want to share and respect the current copyright for every works.
Thanks for attenction
Ivan said he already posted his sourcecodes on Android6.0 at github, I think you can make it much better, and also thanks for supporting heremes ,thank you very much.
Sent from my Redmi Note 2 using XDA Free mobile app
Namaless said:
Hello devs, I think before to split some developers for own project to regroup all ppl want and can working on this device to one place.
The only requeriment are working with apache v2 license (much better gnu because is required to post credits) or any derivate.
....
Click to expand...
Click to collapse
I think you should first pay attention to a Chinese developer who work in Xiaomi, ivan19871002
here's his repo about Hermes : https://github.com/xiaomi-dev/android_device_xiaomi_hermes/tree/cm-12.1
You will notice branch is based on nofearnohappy's work, which is based on bule's.
and he was developed on any Xiaomi's device which use Qualcomm's SoC.
RN2 is his first trial, he only use a week to learn MTK and he already updated a most stable CM on github.
I think there's no body know this news(I'm from Taiwan, so I know all the latest information from China. If you wanna contract with Chinese developer like ivan and bule, you can ask me in PM. I have privately way to contact to nofearnohappy and bule )
By the way, ivan may keeps maintaining this device...
PS. Pay more attention to ivan's patch folder, you'll find all the solution in it.
I check the ivan repository but him fork the nofearnohappy repository only, no one changes...
Nice to know, if you can contact bule and ask him if wanna working on team is the best way
Namaless said:
I check the ivan repository but him fork the nofearnohappy repository only, no one changes...
Nice to know, if you can contact bule and ask him if wanna working on team is the best way
Click to expand...
Click to collapse
You have to switch to his branch which named "cm12.1" that is 22 commits ahead, but not "master" branch.
ivan and bule have team up already... but I'll ask him about this.
jwchen119 said:
You have to switch to his branch which named "cm12.1" that is 22 commits ahead, but not "master" branch.
ivan and bule have team up already... but I'll ask him about this.
Click to expand...
Click to collapse
if they have a team related to hermes we can switch to this if is not for personal choice
I mean to ivan not to xiaomi-dev, this I see the modifications thanks
Gogo guys ill can do the beta testing hehe
Hello Namaless,
I'm novice but I'm interesed in the integration of the ANT+ support currently in CM. If I can help you...
In this moment i follow the aicp ROM, this working fine for me, its useless have many projects without one complete.
When we have a source for aicp we can integrate

What happened to all the yoga 2 threads from ionioni and workdowg??

Hey guys, today after a long time i came back around to this subforum to see if there are any news for my yoga 2 380f but all i found were closed threads?! wtf happened?
after so many months of waiting one could finally unlock the bootloader and install a custom recovery - but now even the posts in these threads are empty.... why?
I am in the mids of gathering all the files that I did manage to get before they were removed. My tab is 1050f. Have all the stuff somewhere fore it
Sent from my SM-G901F using Tapatalk
I suspect a New dedicated forum
New TWRP 2.8.7.0 for YT2 1050 soon !
Hello !
Was CLOSED because not respected XDA rules about GPL !
Almost all work here on XDA require open source code ... he preferred to erase everything he did here instead to provide source code
About TWRP :
A recovery image does contain a Linux kernel which is under GPLv2, and the TWRP source code is under GPLv3 (see the license header in https://github.com/omnirom/android_b...d-6.0/twrp.cpp)
Click to expand...
Click to collapse
On the other hand, tomorrow I'll provide a new TWRP 2.8.7.0 UI 6.0 for Yoga Tablet 2 1050 !
I already managed to fix kernel issue on Stock Lenovo Kernel Android L .
I already pushed all my work on my github : twrp-yt2 for TWRP 2.8.7.0 and also for kernel ! I'll update kernel very soon , because right now is stock one .
Also in a short time I'll try to make a cm-13.0 for our device .
Best regards !
surdu_petru said:
Hello !
Was CLOSED because not respected XDA rules about GPL !
Almost all work here on XDA require open source code ... he preferred to erase everything he did here instead to provide source code
About TWRP :
On the other hand, tomorrow I'll provide a new TWRP 2.8.7.0 UI 6.0 for Yoga Tablet 2 1050 !
I already managed to fix kernel issue on Stock Lenovo Kernel Android L .
I already pushed all my work on my github : twrp-yt2 for TWRP 2.8.7.0 and also for kernel ! I'll update kernel very soon , because right now is stock one .
Also in a short time I'll try to make a cm-13.0 for our device .
Best regards !
Click to expand...
Click to collapse
Can I ask what device you are using as a Base or are you building a vendor folder from scratch
Thanks for your work. Looks like you have implemented pixel finger, I will try this later
pug1 said:
Can I ask what device you are using as a Base or are you building a vendor folder from scratch
Thanks for your work. Looks like you have implemented pixel finger, I will try this later
Click to expand...
Click to collapse
Yes, was started from scratch... should be OK for all YT2.
Also pixelflinger for _X86 are implemented, twrp works fine. ... and sure will work on stock Lenovo kernel for Android L.
Best regards.
I take it you will solve the vendor blobs as you build to find them out?
I have twrp 3.0.0-0 source so will try with that.
You said the kernel is solved? It will build if I sync your github? Have you built a kernel yet? If so what toolchain are you using? I couldn't get it to build as it could find my toolchain.
From the branch 5.1 on your github, it won't work with cm13 source?
Again thanks for your work matey
pug1 said:
I take it you will solve the vendor blobs as you build to find them out?
I have twrp 3.0.0-0 source so will try with that.
You said the kernel is solved? It will build if I sync your github? Have you built a kernel yet? If so what toolchain are you using? I couldn't get it to build as it could find my toolchain.
From the branch 5.1 on your github, it won't work with cm13 source?
Again thanks for your work matey
Click to expand...
Click to collapse
Kernel and also twrp must be compiled along with cm-12.1.
As I already said , my kernel source cannot be compiled ...( Lenovo do not provide a complete one ), but I'll update today later in order to fix all Lenovo issues.
Best regards.
New TWRP 2.8.7.0 for YT2 - 1050 ! Source code already available !

SlickScript for LP/MM

I have decided to release an all-in-one package to turn any LP/MM Rom into SlickROM (Fulmics/Blacksoul have done a great job with LP/MM and it's pointless to waste bandwith).
This package features:
Init.d Support
Debloat with slim replacements for essential apps
An init.d script with every tuned parameter I've used in SlickROM (governors, schedulers, deep level kernel parameters, etc.)
Other secret goodies
Uploading!
XDA:DevDB Information
SlickScript, Tool/Utility for the LG G3
Contributors
nygfan760, nygfan760
Version Information
Status: Testing
Created 2016-03-01
Last Updated 2016-02-29
Mine.
Maniakk said:
This is only stock rom?
μDryka Silva 1.1μ
Click to expand...
Click to collapse
Many of the scripts will work with any ROM/Kernel, I will label the packages specifically.
Look forward to testing it out.
nygfan760 said:
I have decided to release an all-in-one package to turn any LP/MM Rom into SlickROM (Fulmics/Blacksoul have done a great job with LP/MM and it's pointless to waste bandwith).
Uploading!
Click to expand...
Click to collapse
lol.. NO
Please do not post placeholders in Development.
Please let the forum moderators (for your section) know when you actually have a ROM to be posted in the Dev section:good:
Hey admin, just curious what is this slickscript and what does it do? Decided to check this out.

OOS N Sources are out!

Hi, the N kernel source code is live at: https://github.com/OnePlusOSS/android_kernel_oneplus_msm8996/tree/oneplus/QC8996_N
Let the fun begin :victory:
Hope for a LineageOS support now.
Thread closed, existing thread here: Kernel Sources

Categories

Resources