I noticed the thread was closed and gone before I even had a chance to try it out. Anyone know what happened?
It was a work stolen from this Github repo: https://github.com/anomalchik/android_kernel_xiaomi_msm8953/ - that's why it was removed from XDA.
You can take this code and build the kernel yourself.
Related
Hello
Can anyone point me to a guide or summary of alternative kernels please?
You can check our work on the nook color linux kernels in this thread here. http://forum.xda-developers.com/showthread.php?t=1370873&page=285
I also have a guide on using the Git and the Gerrit code review down in cyanogenMod central for the nook color linux tree at this thread link here. http://forum.cyanogenmod.com/topic/50994-follow-along-with-me-trying-to-learn-how-to-code/
If you want to help and have experience on building linux kernels feel free to post a follow up in the first link I have posted. We are using the git and the github to commit code for our linux kernel tree. If you need help on getting up and going on using git, look through the second link I gave, I have all of the links on the github for our project and other helpful tips for you to get started. Right now the top developers are committing code to the jellybean branches. <fat tire> is our top developer and github maintainer for the nook color linux kernel tree, you can find him in the first link I provided and can help you also.
Thanks. I'm able to put a kernel together, but i haven't much experience in original development. I'll keep an eye on that thread though!
Right now we are looking for a few debuggers for the Jelly Bean Kernels. You know how to use debuggers? We need to check for kernel opps that are not being caught by the machines. Last year here there was a developer that rooted 2 kernel opps out and submitted them to Gerrit as a patch. Henk Poley , the developer for the Git extentions used his app and rooted out a few kernel opps on the cyanogenMod stable 7.1 at the time. Check out the my link on debuggers if you are not sure how. Not glamous work but it needs done, and I am getting up and ready to go back to school. Might do that if you want to help.
<Eyeballer> here is looking for someone to strip out all the unnecessary phone .apks for the nook color cyanogenMod builds, like the phone.apk and the telephony.apk along with the voicedialer.apk. I was going to get started on doing that but got sidetracked on getting a proper workflow going on the github. That second thread has links on how to submit work and patches down at cyanogenMod.
~~~~~~~~~~~~~~~
If you are up to a more difficult challenge the wi-fi module needs more work on the Jelly bean builds, they are still getting wake lock problems with it. A few months ago the developers disassembled and reassembled the wi fi module and could not find any code conflicts within the driver or the module. They can fill you in on that up in IRC at #nook color if you want to follow up on that.
Wow. Uh, I don't actually use a debugger, I'm pretty new to building kernels. I used to program C++ in Visual Studio, but so far haven't investigated the debugging process. In my own kernels I use printk, and that's about as sophisticated as it gets.
I wish I could help, but I need the device to available at the moment for my young daughter. Good luck with JB. I'll consider helping if my situation changes.
Hello everybody,
Before I jump into the compilation proces and uploading my build I want to ask everybody first if anybody is interested in a weekly build CM10.
I know that Ivendor is not changing his sources every week, but the base of CyanogenMod is under constant development, so changes in the CyanogenMod source will be up to date again.
Let me know if you're interested by replying to this thread.
Also if theres enough interest in a build with kernel 3.0 inside I'm also willing to upload this image as well.
Because already one person replied I'm willing to share my compiled image. After all it's already compiled.
This build is compiled against ivendors sources on his Github and the latest CyanogenMod sources which were available.
Of course this image is already tested on my phone and everything seems to work like it did on Ivendor's last build.
Because Ivendors sources haven't been changed, this build still has the same bugs as his build.
To be complete the following:
- Vsync doesn't work, because the current kernel doesn't support this yet.
- Panorama shots
- Also mobile internet has a little glitch, which only appears to happen if you have a Pin locked SIM.
Solutions to this are:
* Setting the phone into Airplane Mode and back to normal. This should load the needed module.
* A more clean solution is to use the patch provided at: d-h.st/BgH This patch can be applied through CWM.
- Also camera view is upside down, but this is not noticable in the final saved image. (Don't know if this is a new or already known bug I don't use camera that much).
You can download my build from: mediafire.com/?m765ok5mtly7l6h
You have to copy the links into you're adress bar, because I'm not yet allowed to post outside links.
If anyone has questions feel free to ask.
Greetings PsychoGame
a weekly build would be nice
i don´t use the 3.0 kernel because of the not working camera
i hope it changes soon
Hereby I updated my thread and put in the links to where you can download my build.
Greetings PsychoGame
PsychoGame said:
Hereby I updated my thread and put in the links to where you can download my build.
Greetings PsychoGame
Click to expand...
Click to collapse
Great idea. You can use 2 builds,one with 2.6 kernel, second with 3.x
it would be very great
Sent from my GT-I9001 using xda premium
I try to build the cm 13 for xperia z3
Does any one want to try?
https://www.androidfilehost.com/?a=show&w=files&flid=48494
The kernel in the this build unchanged from the cyanogenmod kernel
Source Code: https://github.com/CyanogenMod/android_kernel_sony_msm
Please provide links to your sources to remain GPL compliant.
I will give you a couple of days from this post to get it sorted.
If you are unsure about the GPL please read here
http://forum.xda-developers.com/showthread.php?t=2645321
and here
http://forum.xda-developers.com/showthread.php?t=2786244
The source to the unchanged kernel can be found in the sources you gave, but it is good practice to give a link to the exact repo or kernel and not let others search for it.
Thanks
@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:
I was browsing Lineage Gerrit the other day and CMTE was being ported to Lineage 14.1. Someone commented on the change asking why not use OMS, and the change author replied something like "well, if you want OMS support why don't you submit a change and we'll see how it works?". So, I decided to do it.
I've forked some Lineage repositories and applied some changes from SubstratumResources to them. I tried testing it but something went terribly wrong, resulting in my phone not booting up (it got stuck in the Lineage boot animation). Perhaps I've missed some important commit (such as the SEPolicy one) and it could've bugged out my build.
So, I'm posting "my" (not actually mine, I just rebased them so they could be applied to Lineage source) patches here if someone wants to try it out and/or help me fix the issues that prevent OMS compatibility with LineageOS.
Repositories
android_system_sepolicy
android_frameworks_base
android_vendor_cm
android_frameworks_native
android
I've updated the links to the changed repositories in the android manifest, so if you want to try it out, just download it and save as manifest.xml inside android/system/.repo (assuming you're following Lineage's instructions to build), then run repo sync --force-sync to update the repositories.
EDIT: just a disclaimer - I'm not responsible for anything bad that happens with your phone. If you decide to build with these patches in place, know that it is your responsibility what happens to your phone. Always have a backup in case things go wrong.
Been trying to get it working too, at the point of just giving up on that github repo and picking the changes individually
ibrokemypie said:
Been trying to get it working too, at the point of just giving up on that github repo and picking the changes individually
Click to expand...
Click to collapse
Do you have a link for your repo? And did you manage to get it working (if so I want to compare the changes you've cherry-picked).
I'll build today and hopefully it'll work this time (or not). Will update this post as soon as I test.
RockyTV said:
Do you have a link for your repo? And did you manage to get it working (if so I want to compare the changes you've cherry-picked).
I'll build today and hopefully it'll work this time (or not). Will update this post as soon as I test.
Click to expand...
Click to collapse
yeah if you check my github you can see the repos with the oms changes successfully merged into LOS source. Trying to get it up on gerrit now
ibrokemypie said:
yeah if you check my github you can see the repos with the oms changes successfully merged into LOS source. Trying to get it up on gerrit now
Click to expand...
Click to collapse
Hm, it's a bit harder to compare because you didn't cherry-pick
Anyways, if you manage to get it on Gerrit, I'm not so sure if not cherry-picking can make a difference.