I'm sorry if this has been answered somewhere else, but I have not been able to find this solution after a few days of searching.
I am building CM10 from source for Galaxy S II (I9100) with my own changes on a Linux system. It builds and runs fine using UserDebug signatures.
I wish to build the release version not the userdebug one, and I wish to use my own keys/certificates/Signatures (e.g. release.x509.pem)
After setting everything up, I build the ROM using the commands
. build/envsetup.sh
lunch 27
./build.sh i9100
Is there options or settings to trigger the Release build?
How do I get the build to use my own Signatures?
I understand how to re-sign an existing ROM, but wish to have my signatures be used for internal parts (media, platform, shared, etc.) plus use the builder to do everything automatically without any post processing.
I have not found or understood the Android nor Cyanogenmod documentation. I might be missing the key document.
Thank you for your time.
.
looking at make files and buildspec.mk.default
I'm still looking into solving this myself, but I'm not making much headway.
The search for android build_new_device gave me a links to look at and it is helping me understand the build a bit.
I am trying to understand how buildspec.mk.default is used. I've tried to find where TARGET_BUILD_VARIANT is set for the cm build of i9100 but apparently I am exceeding the limits of grep
Anyone have a suggestion or pointers for this?
Build a release version of cm10 for i9100 and use my own certificates/keys
(not userdebug or eng, but just user)
Thank you.
randombitsca said:
I'm sorry if this has been answered somewhere else, but I have not been able to find this solution after a few days of searching.
I am building CM10 from source for Galaxy S II (I9100) with my own changes on a Linux system. It builds and runs fine using UserDebug signatures.
I wish to build the release version not the userdebug one, and I wish to use my own keys/certificates/Signatures (e.g. release.x509.pem)
After setting everything up, I build the ROM using the commands
. build/envsetup.sh
lunch 27
./build.sh i9100
Is there options or settings to trigger the Release build?
How do I get the build to use my own Signatures?
I understand how to re-sign an existing ROM, but wish to have my signatures be used for internal parts (media, platform, shared, etc.) plus use the builder to do everything automatically without any post processing.
I have not found or understood the Android nor Cyanogenmod documentation. I might be missing the key document.
Thank you for your time.
.
Click to expand...
Click to collapse
Try posting this in your device forum
In the General section
That would give you more help I believe !
Sent from my MT11i using xda premium
Related
Hi there,
Now, I understand that there's a thread or two and a few web pages directed at compiling Android and its kernel from source.
However, the thread in question is months old, and didn't fully explain the process.
As for the web pages, they are mostly outdated and don't include enough information, not to mention desire specific instructions.
I think that, properly explained, building Android shouldn't be daunting, and everyone should be able to attempt it, if they wanted to.
So, I hope to compose a comprehensive guide on how to do just that.
The problem is that I myself have not been able to put enough instructions together to be able to complete a build. And there is no point digging up old threads.
So, If anyone who knows the ropes (that is, compiling android and a kernel from source) would be willing to lead the way, I'd happily turn it into an easy to understand guide.
Josh.
fllash said:
Hi there,
Now, I understand that there's a thread or two and a few web pages directed at compiling Android and its kernel from source.
However, the thread in question is months old, and didn't fully explain the process.
As for the web pages, they are mostly outdated and don't include enough information, not to mention desire specific instructions.
I think that, properly explained, building Android shouldn't be daunting, and everyone should be able to attempt it, if they wanted to.
So, I hope to compose a comprehensive guide on how to do just that.
The problem is that I myself have not been able to put enough instructions together to be able to complete a build. And there is no point digging up old threads.
So, If anyone who knows the ropes (that is, compiling android and a kernel from source) would be willing to lead the way, I'd happily turn it into an easy to understand guide.
Josh.
Click to expand...
Click to collapse
I followed this guide here and successfully compiled a modified HTC Kernel and I had very little Linux and Android experience.
Obviously instead of cloning the Cyanogen git, you just use the gits you wish to compile
Mekrel said:
I followed this guide here and successfully compiled a modified HTC Kernel and I had very little Linux and Android experience.
Obviously instead of cloning the Cyanogen git, you just use the gits you wish to compile
Click to expand...
Click to collapse
Thanks for the link
Though i don't fully understand the whole 'git' thing. Where do i find them? And how to i know which ones are the ones i want to use?
Josh
EDIT: Also, how do you 'edit' the kernel (i imagine it is somewhat like make menuconfig?). Also:
- Are these sense kernels?
- How do you add modules like OC and UV?
fllash said:
Thanks for the link
Though i don't fully understand the whole 'git' thing. Where do i find them? And how to i know which ones are the ones i want to use?
Josh
EDIT: Also, how do you 'edit' the kernel (i imagine it is somewhat like make menuconfig?). Also:
- Are these sense kernels?
- How do you add modules like OC and UV?
Click to expand...
Click to collapse
A git is a repository for source code, developers upload their source code there and can commit changes. The commit can allow descriptions of what was changed and also details the files changed.
The git system allows other people to add to the source if they have permission, or allows others to read the changes and download the source code.
Git links are usually posted by people who release software, as Android is GPL licensed so people have to release their source code if they're distributing their work.
Editing the kernel, take a look into the git and the commits and it will show you which files were changed and how exactly they were changed. That will give you the best understanding.
UV/OC is done by changing the acpu table in the architectures files and changing the minimum/maximum voltage figures in the board_bravo.c file.
The Cyanogen kernels are not Sense kernels no, it's a modified Google Kernel.
Thanks for the explanation. I followed the guide and built the rom, and it works (always a plus )
Now, the next thing is the kernel. How do I build a kernel with the CM tweaks integrated? I understand that all i would be doing is rebuilding the same one that is already installed, but im doing it to learn.
So, if i synced the GIT, does that include the CyanogenMOD kernel source? If it does, where is it and how do i rebuild it. If not, where do i find it?
Thanks,
Josh.
Hi,
Im new with android develoopment so please bear with a n00b. can someone guide me how to build ics rom using the source provided by samsung..
I have downloaded the original android ics source and samsung's source.. I can build the android source but I dont know how to plug in the samsung code. Unfrotunately, sammy's documentation is insufficient probably about 10 lines, just says to overwrite the android source and do a make. But when I run make I get errors...
I've been looking at the forums most of them build from the cm10 source, but I want to build using the original. Figured I would learn more if I tried to build it from the actual sources..
Appreciate any help. If I learn, I would definitely pay it forward by contributing whatever I can to the community..
Thanks
You need to post this in the Galaxy Note phone section.
Wrong section. 1) Dev sections are for builds and modifications. 2) wrong device thread. This is for the galaxy note 10.1 tablet.
Sent from my GT-N8013 using xda premium
n00b13 said:
Hi,
Im new with android develoopment so please bear with a n00b. can someone guide me how to build ics rom using the source provided by samsung..
I have downloaded the original android ics source and samsung's source.. I can build the android source but I dont know how to plug in the samsung code. Unfrotunately, sammy's documentation is insufficient probably about 10 lines, just says to overwrite the android source and do a make. But when I run make I get errors...
I've been looking at the forums most of them build from the cm10 source, but I want to build using the original. Figured I would learn more if I tried to build it from the actual sources..
Appreciate any help. If I learn, I would definitely pay it forward by contributing whatever I can to the community..
Thanks
Click to expand...
Click to collapse
Wrong forum and building pure AOSP for Samsung non-Nexus devices is impossible, too many framework changes needed. Android userspace is Apache licensed so this is unfortunately legal.
Sent from my GT-N8013 using Tapatalk 2
Thread Moved
Please post in the correct section.
First post in the Dev section but this seemed to be the place to talk about kernel compilation and module development.
I have twice now, and am working on my third kernel compilation for the purposes of custom module building for the TF700 and the TF201.
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all. Is this normal for kernel compilations? I would have thought that it would be fully compilable out of the box ( so to speak). Is it ASUS or just android/Linux in general that works out this way?
Is there a better way to do it? Should I use some generic source with the same version numbers? The current source is just not working at all. I am using an Ubuntu distro. Have the cross compile tools etc... but it just fails. I have already resolved two missing definition references and it just keeps on failing in new places
Hopefully this question doesn't offend developers. I have moved from WinPhone to here and want to better my understanding of how this should all work but need to start with some basics before I can make a meaningful contribution.
Thanks.
P.S... I looked and didn't find a "Compiling android kernels for dummies" book
hx4700 Killer said:
I looked and didn't find a "Compiling android kernels for dummies" book
Click to expand...
Click to collapse
"Dummies" doesn't write a book on kernel dev. Too wrapped up in telling people how to download iTunes.....
Use your "Google". And when you find it, Google XDA University.
There, you will find steps for setting a build environment and kernel and cross arm.
Understand, all kernels are different, but a good place to start. Plus, you learn how to use Google. An added bonus.
Oh... and... as an extra bonus, I will move this to Q & A, as this post has no development work attached. :silly:
MD
My question wasn't HOW to cross compile. I have done it.
My question is WHY are there so many errors that need correcting when compiling the ASUS downloadable kernels and if this is typical of the source from any device or just ASUS?
hx4700 Killer said:
The question I have has to do with the compilation process. Every time I have gone through this with the downloadable Asus Kernel zip I run in to several issues. Either missing references in code or portions that won't compile at all.
Click to expand...
Click to collapse
I had to fix exactly one pair of quotes vs. angle brackets somewhere in the RIL - get the patch pack from my kernel and apply the ril include fix. Then it should compile. If not, you are doing something wrong.
Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou
alexcass4 said:
Can you post any links or names of everything ill need to get started on cross compiling a kernel for my tf700t I download the source and get my config.gz and am running a ubuntu distribution but if you could post a link to a tutorial that has detailed instructions that will work for the infinity that would be greatly appreciated thankyou
Click to expand...
Click to collapse
Step 1: Get a suitable ARM toolchain. I can't help you here with Ubuntu because I'm using Gentoo and their crossdev tool (http://www.gentoo.org/proj/en/base/embedded/handbook/?part=1).
Step 2: Cross-compiling the kernel works just as for native kernels (make menuconfig, make), but you have to pass parameters to each make, e.g. make ARCH="arm" CROSS_COMPILE="arm-gentoo-linux-gnueabi-" (or whatever your toolchain is called)
Step 3: For the TF700-specific blob stuff I have written a detailed tutorial here: http://forum.xda-developers.com/showpost.php?p=36925180&postcount=4
Hi there,
as I don't have permission to write on the Unofficial Rom Project Thread, I am asking here for a GUIDE to setup a jenkins server that automatically builds ROMs for my Sensation aka Pyramid.
Is anyone here who can help me to get into the build process for the first time on an continious integration server.
What did I already did?
I have set up Java 1.6 to build a Cyanogenmod 11 and I m not sure if it should be Java 7?
I downloaded the entire sources from github. I m sorry I m not allowed to post a link.
via
so I hope that isnt the wrong way as I am following multiple guides to accomplish my target.
So I wanted to set up it all for the first time to run a compilation without jenkins then I 'm stuck at the point where I integrate the UnORom files - I only could set up a
Code:
git clone https://github.com/UnORoms/android_device_htc_pyramid.git
and then i succesfully executed
Code:
./extract-files.sh
so it downloaded a couple of files from my phone.
But when I do a
Code:
lunch
there don't exists a cm_pyramid?
So I m stuck at this point and I m politely asking for help.(Maybe to accomplish my personal goal of using a continious integration server at least
Thanks in advance for your replys
Nobody knows how to build a android rom for a specific device?
In my case the HTC Sensation?
I would be glad if there where some tutorials of implementing the necessary files into my cm11-tree.
Could anyone please give it a try?
chiefdome said:
Nobody knows how to build a android rom for a specific device?
In my case the HTC Sensation?
I would be glad if there where some tutorials of implementing the necessary files into my cm11-tree.
Could anyone please give it a try?
Click to expand...
Click to collapse
I'm not 100% familiar with building roms, but I once compiled them completely from source for testing purposes.
Do you have device files and kernel in your local manifest to sync them from somewhere or did you take what you need from your phone? Not sure if it's required or not.
When I had everything ready I had to run
Code:
./device/htc/pyramid/repo-patcher.sh
then I could run
Code:
lunch cm_pyramid-userdebug
and it worked.
Not sure if it works same way here too, since I did that when I used Team-Sennyc2 device tree.
First off, I just want to say I don't mean to step on anyone's toes. Thanks for all the work so far from digitalhigh, bracketslash, santod040 and everyone who has posted information about or commits to the CM12 build tree. This is not my code, all I have done is disable enough stuff to get it to build and boot. A LOT OF STUFF IS BROKEN. This is intended for developers only right now. I will try to update the builds as I can but please don't expect true nightly builds.
DISCLAIMER: I am in no way responsible for malfunctioning or bricked devices if you run this software. If you do not agree to these terms, DO NOT DOWNLOAD. Again, this is seriously broken right now.
What doesn't work:
-Almost everything
What works:
-Wifi
-Touchscreen
-Sound
Changelog:
Merged (compare to build date)
Open (not in build yet)
Installation notes:
As I have yet to find a way to easily disable NFC for the builds, you will have to remove the /system/app/Nfc to stop those force closes. I just went to TWRP, mounted system, then ran "rm -rf /system/app/Nfc" to disable NFC for now.
Downloads:
2014-11-17: Download (Android File Host)
Edit: Please see bracketslash's thread for future downloads: http://forum.xda-developers.com/ver...ment/cm12-unofficial-unstable-builds-t2941198
bring it on bro
This saved me some time. Guess I'll see what I can do.
There was a new commit added to the open section that "adds dependency on device/qcom/sepolicy"
http://review.cyanogenmod.org/#/q/status:open+project:CyanogenMod/android_device_htc_m8,n,z
That was fast!
krazie1 said:
There was a new commit added to the open section that "adds dependency on device/qcom/sepolicy"
http://review.cyanogenmod.org/#/q/status:open+project:CyanogenMod/android_device_htc_m8,n,z
Click to expand...
Click to collapse
Thanks for info. I'll probably just wait on that one to get merged as so much is broken already. I doubt selinux will be the cause of frustration right now Also for anyone interested I made the following modifications to the cm12.0 branch to get this to build:
1) Created local_manifest.xml with muppeteers 12.0 branch
2) Commented out DotCase line in device/htc/m8/device.mk (has issues building)
3) Commented out ro.cwm.forbid_mount and ro.cwm.forbid_format lines in device/htc/m8/system.prop (too long)
4) Added missing overlay resources to main resources (copy the missing variables from build/overlay/frameworks/blah.xml to frameworks/blah.xml)
Ive been patiently waiting for cm12 on this beast
This should be in HTC one m8 original development not the Verizon section. If you want more attention and to help people out repose there
jake.99x3 said:
This should be in HTC one m8 original development not the Verizon section. If you want more attention and to help people out repose there
Click to expand...
Click to collapse
Given the intro post on the "original development" forums, I feel my topic is still more applicable in this section.
http://www.xda-developers.com/android/introducing-original-development-forums-for-more-devices/
djh816 said:
Given the intro post on the "original development" forums, I feel my topic is still more applicable in this section.
http://www.xda-developers.com/android/introducing-original-development-forums-for-more-devices/
Click to expand...
Click to collapse
Good point so then move it to android development. Cm is for all device variants not specifically verizon and won't get Much attention here.
jake.99x3 said:
Good point so then move it to android development. Cm is for all device variants not specifically verizon and won't get Much attention here.
Click to expand...
Click to collapse
While I agree it may not get as much attention, I still think this is the proper place. Android development (not m8 android development) is more for universal android projects or new code bases or ROMs for devices that don't have their own sub forum. That being said, this is a build of already existing code so it should go into a "development" section and given that I only plan to get this working on Verizon variant (as that's what I have) I avoided posting to the generic m8 sub forum. Mods can move as they feel fit but I think it belongs here Feel free to repost any info I have here though.
I'm trying to build and I'm getting stuck on the proprietary binaries.
Specifically this:
Code:
make: *** No rule to make target `vendor/htc/m8/proprietary/bin/adsprpcd', needed by `/home/build/cm12/out/target/product/m8/system/bin/adsprpcd'. Stop.
Any advice?
-xdadevelopers-user
xdadevelopers-user said:
I'm trying to build and I'm getting stuck on the proprietary binaries.
Specifically this:
Code:
make: *** No rule to make target `vendor/htc/m8/proprietary/bin/adsprpcd', needed by `/home/build/cm12/out/target/product/m8/system/bin/adsprpcd'. Stop.
Any advice?
-xdadevelopers-user
Click to expand...
Click to collapse
Hmm I didn't run into this. I just used the get-prebuilts command and didn't have any issue after. I followed these but modified for 12.0 branch:
http://forum.xda-developers.com/ver.../how-to-build-cm11-htc-one-m8-082714-t2860056
Just make sure your local_manifest.xml file has the 12.0 muppeteers branch as shown in example on page 6 of that thread.
djh816 said:
Hmm I didn't run into this. I just used the get-prebuilts command and didn't have any issue after. I followed these but modified for 12.0 branch:
http://forum.xda-developers.com/ver.../how-to-build-cm11-htc-one-m8-082714-t2860056
Just make sure your local_manifest.xml file has the 12.0 muppeteers branch as shown in example on page 6 of that thread.
Click to expand...
Click to collapse
@djh816
Hi compile ROM cm11 for a different device
Could you tell me which Java version are you using to build cm12, since you have just built cm12?
I tried to built cm12 yesterday and I got an error for Java so I installed OpenJDK7 and the it started building but I am getting a lot of non-device related error saying "internal compilation error"
I even tried removing all java version and re-installing OpenJDK7. Set alterantives too but no luck.
So please could you let me know which Java Version are you using for building cm12?
OpenJDK7 or Oracle/sun 7
Thanks
macs18max said:
@djh816
Hi compile ROM cm11 for a different device
Could you tell me which Java version are you using to build cm12, since you have just built cm12?
I tried to built cm12 yesterday and I got an error for Java so I installed OpenJDK7 and the it started building but I am getting a lot of non-device related error saying "internal compilation error"
I even tried removing all java version and re-installing OpenJDK7. Set alterantives too but no luck.
So please could you let me know which Java Version are you using for building cm12?
OpenJDK7 or Oracle/sun 7
Thanks
Click to expand...
Click to collapse
I started with clean ubuntu 14.04 lts x64 and added the packages from bracketslash's thread here. Then I just installed openjdk-7-jdk and openjdk-7-jre after that.
djh816 said:
While I agree it may not get as much attention, I still think this is the proper place. Android development (not m8 android development) is more for universal android projects or new code bases or ROMs for devices that don't have their own sub forum. That being said, this is a build of already existing code so it should go into a "development" section and given that I only plan to get this working on Verizon variant (as that's what I have) I avoided posting to the generic m8 sub forum. Mods can move as they feel fit but I think it belongs here Feel free to repost any info I have here though.
Click to expand...
Click to collapse
HTC One M7 has fully working CM12 build, and that is in ANDROID DEVELOPMENT SECTION The Op said that he has working CM12 rom for M8, you might ask him for advice, how to make your build more stable and with less bugs. That's my opinion anyways. You can check the build for M7 here http://forum.xda-developers.com/htc-one/development/5-0-lollipop-unofficial-cm12-android-5-0-t2943826 :good:
djh816 said:
Thanks for info. I'll probably just wait on that one to get merged as so much is broken already. I doubt selinux will be the cause of frustration right now Also for anyone interested I made the following modifications to the cm12.0 branch to get this to build:
1) Created local_manifest.xml with muppeteers 12.0 branch
2) Commented out DotCase line in device/htc/m8/device.mk (has issues building)
3) Commented out ro.cwm.forbid_mount and ro.cwm.forbid_format lines in device/htc/m8/system.prop (too long)
4) Added missing overlay resources to main resources (copy the missing variables from build/overlay/frameworks/blah.xml to frameworks/blah.xml)
Click to expand...
Click to collapse
You don't need to do all of that.
There's one commit and everything works just fine.... nothing's broken.
http://review.cyanogenmod.org/#/c/76760
...and you may just want to thank invisiblek in your original post. He's the only one that did all of the work to bring up the device.
Gunman84 said:
HTC One M7 has fully working CM12 build, and that is in ANDROID DEVELOPMENT SECTION The Op said that he has working CM12 rom for M8, you might ask him for advice, how to make your build more stable and with less bugs. That's my opinion anyways. You can check the build for M7 here http://forum.xda-developers.com/htc-one/development/5-0-lollipop-unofficial-cm12-android-5-0-t2943826 :good:
Click to expand...
Click to collapse
calling @santod040 for some cm love for m8vzw
munchy_cool said:
calling @santod040 for some cm love for m8vzw
Click to expand...
Click to collapse
if someone wants to make a donation to me, i will cherry pick a commit and brunch a completely working build (apart from universal cm issues).
ajrty33 said:
if someone wants to make a donation to me, i will cherry pick a commit and brunch a completely working build (apart from universal cm issues).
Click to expand...
Click to collapse
Welcome to XDA ..
Lollipop Red M8