Hi all,
I just wanted to check - all of those using Cyanogen's 5.0.7/5.0.8 mod for your ROM base.....where are you getting this source code from? I know that a user name Elemag ported it over, and I have his git tree bookmarked, but is it an up-to-date source? (In other words, is it the 5.0.7 port?)
Here is the github URL in case you are interested:
github link
To me, this looks like the 5.0.7 port, which therefore leads me to my next question. Where can I find the 5.0.8?
Thanks in advance!
Mr P.
MrPadie said:
Hi all,
I just wanted to check - all of those using Cyanogen's 5.0.7/5.0.8 mod for your ROM base.....where are you getting this source code from? I know that a user name Elemag ported it over, and I have his git tree bookmarked, but is it an up-to-date source? (In other words, is it the 5.0.7 port?)
Here is the github URL in case you are interested:
github link
To me, this looks like the 5.0.7 port, which therefore leads me to my next question. Where can I find the 5.0.8?
Thanks in advance!
Mr P.
Click to expand...
Click to collapse
gu1dry's github is 5.0.8 port. if you want the newest, you can get it from cyanogen's github
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.
@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'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
If you are eager to Void your Warranty please Mind and Acknowledge that every modification only affects you and your contract and noone else.
custom rom
http://forum.xda-developers.com/xperia-xa/development/f3112-f3116-cyanogemod-13-project-t3488890
Silversniper said:
I'm here to question the device owner. There are few sources around about this device. They are raw and they are as common always experimental. Does anyone need them?
Furthermore, I can sum up here any sources I or other get to find about this device or its periphery.
Click to expand...
Click to collapse
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
rrvuhpg said:
Very good thing, I'm trying to build a CM13 rom from sources and I'm not sure if I have all required sources. For now I have, kernel sources with some "vendor" files from Sony and I found all build parameters like offsets/adresses and correct cmdline (no thanks to Sony because never released or mentioned them), the device tree dumped from my device, and I will dump the vendor tree too.
Now I need the defconfig for CM (very not sure if the stock one will work) , and some files like the boardconfig and some config files. I'm using the Elephone P9000 sources for sample, almost the same device (hardware side) and source files.
If I have some time I will try to upload files to git but I never tried before (sync only)...
Click to expand...
Click to collapse
Don't need to hesitate. I'll try to put the directions I've gathered here up today so it is done.
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
cool.. if work I would like to have it on my f3111 !!
rrvuhpg said:
I finished to upload my files to Github:
https://github.com/rrvuhpg
You will find the device, kernel and vendor files to build CM13 for F3112/F3116. For now it will not work, it's just to share and help. I successfully built and booted the Cyanogen recovery with the kernel from sources, the doors for porting new roms are open?? :fingers-crossed:
My next step is to finish the device tree, verify the vendor tree and build the rom
Click to expand...
Click to collapse
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Silversniper said:
Can you publish some brief preview?
Need to say the sources I had just seem to be down, so can't share them.
Through which Program are these to flash? If you're that far I can hold a look at it and may join in your development.
Verification of the Vendor Files is something I was not very good at it, not even a yolk I managed.
Click to expand...
Click to collapse
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
rrvuhpg said:
For now the only preview I can publish are the CM13 boot and recovery "as is", I'm not sure if it can help but I will release them if someone want to port others MTK Roms on XA. ( Never booted any ported rom with the stock kernel, stuck at Sony logo)
Flashing is easy: the recovery with fastboot and Rom/boot in a single flashable zip on the SD.
The kernel sources are coming from 33.2.B.2.95 open source archive from Sony but built from the lastest CM13 and Google git sources.
The vendor tree from 33.2.B.2.93 dumped from my phone, only common files with the P9000 are on my git for now.
The device tree from P9000 sources (from @Deepflex git) but seem OK.
CM13 have Android 6.0.1, I don't know if the security patch is the last one but August for sure.
I'm not so far from a finished build (not mean fully bootable), for now I successfully build a full CM13 for the Elephone P9000 (the twin of the XA, I'm using it as base). It mean my "kitchen" is working Now I'm trying to identify the last proprietary files from all others stock/cm13 libs, modify make files and cross my fingers it will fully build without errors.
You can join me no problem all people are welcome because I can't do all alone
Click to expand...
Click to collapse
good work , but I am noob to create rom with kitchen .. only zip edit I know
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
rrvuhpg said:
Yesterday I successfully built CM13 for XA from sources
But news are not good, the CM recovery is fully working as expected but the rom is stuck just after the Sony logo (Mediatek screen with "loading...") like on my previous attempts to port other roms. The kernel built from CM kitchen do the same... I will upload my git and my rom to see if someone have an idea on the problem. Now I will focus on the "vendor" files, but I'm not sure if it's the real problem. Can it be a locked preloader/kernel or something like that?
EDIT: I think the boot problem is related to the defconfig file from Sony kernel sources, I will try to change some settings. (the door for adding kernel features :good
Click to expand...
Click to collapse
Love you!
I will buy this phone thanks to you :highfive:
Thank you for your work on our phone, it's very cool.
I would have helped if i could develop myself. If you need help get in touch with me i know some great devs who could maybe help you
any news @rrvuhpg ?
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
rrvuhpg said:
Yes I have some news but I want to create a dedicated thread for the CM13 project with updates, explanations and downloads to avoid off topic here. I am on holiday on next week and I will have time to work on it and give explanations. For now I'm stuck on boot because of Sony extra settings in the boot process, it's the first time I see a bootstrap and TA partition mount on a MTK device. If you know a dev for helping me passing the Sony part in the boot init it can be great :angel:
Other thing, I updated my git with parts of the update made by @Deepflex on the P9000 sources and my recent changes.
Click to expand...
Click to collapse
sorry first time I use sony ... I wish you to have nice holiday !
Hi, I followed relatively all the steps on android open source project, and I managed to build on an image of rom (predicted as aosp) but I was nowhere told where and how to enter drivers and etc, and I did not do so, in the absence of documentation, we didn't find anywhere else, somewhere at the beginning of the guide we wrote that we would need proprietary files to use, but not how. I read on a thread on xda (but it was strictly about sony devics) that simply, after I had to give flash to the picture.
Will it boot? without any changes ?
I haven't found any guide anywhere, if you have one, please give it to me.
Thanks in advance
you must add davinci kernel source to your sync aosp source (with local manifest).
davinci open source kernel for android r is here:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/phoenix-r-oss
Learning about local manifest and repo tool here:
https://forum.xda-developers.com/t/learn-about-the-repo-tool-manifests-and-local-manifests-and-5-important-tips.2329228