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.
Related
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
So I am a newbie in android development. I do root phones and play around with the system but I never cooked any rom yet. Now I am desperate to build cm12 for my pico. I have set up everything as per Galaxyfreak's guide.
Now I am confused with what should I take as sources? Should I use Kirmaniarslan's sources or wait for cm to officially release?
If I take Kirmaniarslan's sources,in the init repo command what should I link to? Local manifesto, device tree or something else?
Any guide would be helpful! Thanks
The developer site is still listing KitKat as the newest build, so here are the links to the instructions to build Lollipop using the official source:
Lollipop 5.0: http://nv-tegra.nvidia.com/gitweb/?...a=blob_plain;f=README;hb=rel-st8-l-r1-partner
Lollipop 5.0.1: http://nv-tegra.nvidia.com/gitweb/?...a=blob_plain;f=README;hb=rel-st8-l-r2-partner
Cheers mate. It is still listing the 1.2.1 OTA as the latest but just by changing the branch url i was able to find the newest.
Lets hope for some more development on this device. I'm going to PM you soon - I will be building my own ROM and/or Kernel.
berryman13 said:
Cheers mate. It is still listing the 1.2.1 OTA as the latest but just by changing the branch url i was able to find the newest.
Lets hope for some more development on this device. I'm going to PM you soon - I will be building my own ROM and/or Kernel.
Click to expand...
Click to collapse
You do realize those are the links posted above. There is no need to switch branch names or search for the current files. Just click the one you want.
twistedumbrella said:
You do realize those are the links posted above. There is no need to switch branch names or search for the current files. Just click the one you want.
Click to expand...
Click to collapse
Of course, mate!
I was saying that I found the proper page by changing the URL to hb=rel-st8-l-r2-partner, before this thread was posted. So I appreciate you enlightening other folks about it!
berryman13 said:
Of course, mate!
I was saying that I found the proper page by changing the URL to hb=rel-st8-l-r2-partner, before this thread was posted. So I appreciate you enlightening other folks about it!
Click to expand...
Click to collapse
Even without already having the branch name, it's just a matter of going to http://nv-tegra.nvidia.com/gitweb/?p=manifest/android/binary.git;a=summary to find it
Hi, @twistedumbrella could you please spare a second to help (or point me in the right direction) I've successfully built Lollipop for my Oneplus One using Ubuntu, but when I try to set up first repo sync; well see below:
When I run: repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r2-partner -m tlk/shieldtablet.xml
I get: fatal: manifest 'tlk/shieldtablet.xml' not available
fatal: remote github not defined in /home/diigimatrix/.repo/manifests/tlk/shieldtablet.xml
Please could you get me on my way. I love all your work and hope to gain further knowledge through your support.
Thanks in advance
Phil from Blackpool
diigibio said:
Hi, @twistedumbrella could you please spare a second to help (or point me in the right direction) I've successfully built Lollipop for my Oneplus One using Ubuntu, but when I try to set up first repo sync; well see below:
When I run: repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r2-partner -m tlk/shieldtablet.xml
I get: fatal: manifest 'tlk/shieldtablet.xml' not available
fatal: remote github not defined in /home/diigimatrix/.repo/manifests/tlk/shieldtablet.xml
Please could you get me on my way. I love all your work and hope to gain further knowledge through your support.
Thanks in advance
Phil from Blackpool
Click to expand...
Click to collapse
I'm trying to figure out what's up with it now. I know when I synced it was r1, and tlk/shieldtablet.xml was valid.
Hopefully I can track down why it is coming back invalid in r2.
Thanks @twistedumbrella, glad in a way its not just me. Thought I was running the wrong command. . Happy New Year!
diigibio said:
Thanks @twistedumbrella, glad in a way its not just me. Thought I was running the wrong command. . Happy New Year!
Click to expand...
Click to collapse
Same to you. It updated ok but now I have to see if it'll re-init. It may be a delay on their end. The readme for the portable was up a week before the source.
Cool. I'll give it another try once I've finished work. Been a member for years and helped a lot in the old windows phone days. But thought enough of just relying on other people, time to start getting my hands dirty again. But new to building Android. Need to read up on manipulation of ROMs rather than just building a stock ROM. Any tips on tools to manipulate ROMs? Am i right by merging commits then build, then manipulate ROM? I will read up on it but just thought you might have some pointers. Thanks
diigibio said:
Cool. I'll give it another try once I've finished work. Been a member for years and helped a lot in the old windows phone days. But thought enough of just relying on other people, time to start getting my hands dirty again. But new to building Android. Need to read up on manipulation of ROMs rather than just building a stock ROM. Any tips on tools to manipulate ROMs? Am i right by merging commits then build, then manipulate ROM? I will read up on it but just thought you might have some pointers. Thanks
Click to expand...
Click to collapse
Best bet is to either find something you like and merge it or try to find something similar and recreate it to start. Once you get comfortable, then start coming up with your own.
Building from source is mostly Java for modifying with some C for drivers and such. Usually when you have a device configuration already set up, though, the C part is already done.
Just wanna say a big thanks to @twistedumbrella. I set up a new ubuntu build environment and I'm now compiling my first Android build for Nvidia Shield Tablet EU-LTE. No mods yet other than stock, but hopefully with time.
diigibio said:
Just wanna say a big thanks to @twistedumbrella. I set up a new ubuntu build environment and I'm now compiling my first Android build for Nvidia Shield Tablet EU-LTE. No mods yet other than stock, but hopefully with time.
Click to expand...
Click to collapse
Glad to hear it's all up and running. Best of luck!
twistedumbrella said:
Glad to hear it's all up and running. Best of luck!
Click to expand...
Click to collapse
Hi! I'm trying to compile but get error trying no find:
./packages/apps/UnifiedEmail/src
After repo sync, I don't have "src" directory for this package.
Thnx in advance.
entelekia said:
Hi! I'm trying to compile but get error trying no find:
./packages/apps/UnifiedEmail/src
After repo sync, I don't have "src" directory for this package.
Thnx in advance.
Click to expand...
Click to collapse
It looks like they are still working out a few issues with new updates. I don't maintain the source, so the only advice I can provide is to keep on eye on nvidia's gitweb for when they publish a solution (or occasionally sync and try over), or attempt to fix it yourself (which usually only works if there is an issue with the code, not code missing altogether).
Compiled! I have resynchronized all the project from scratch from git repository.
I'm going to test the compiled ROM in my tablet, but I suppose, I have to provide almost the essential pack of Google apps (basic providers and play services).
I think to flash *.img files, except recovery.img (I'm on TWRP), and then install from TWRP PA Gapps. Is this approach correct?
Thnx in advance and regards.
EDIT: No luck booting custom rom (TWRP nor stock recovery...)
Seem's like there's a new source three version out:
repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r3-partner -m tlk/shieldtablet.xml
GethPrime said:
Seem's like there's a new source three version out:
repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r3-partner -m tlk/shieldtablet.xml
Click to expand...
Click to collapse
Anyone managed to build this one yet? Its not working for me..
Hi. I've always been curious to try to build a new aosp based ROM.
I know java but I don't know CPP... Only a bit. Anybody thinks I could start something? Even in a team, of course. Where to start?
enryfantasy said:
Hi. I've always been curious to try to build a new aosp based ROM.
I know java but I don't know CPP... Only a bit. Anybody thinks I could start something? Even in a team, of course. Where to start?
Click to expand...
Click to collapse
First of all, it depends on how much you already know.
There are numerous guides on how to build another existing custom ROM. I'd start with those first to be a little familiar with how a project is handled, but you could always just look for guides for building one from scratch AOSP if you wanted to.
There are plenty of guides on the internet, and if you run into an issue, someone else has likely already asked about it and received an answer.
Elluel said:
First of all, it depends on how much you already know.
There are numerous guides on how to build another existing custom ROM. I'd start with those first to be a little familiar with how a project is handled, but you could always just look for guides for building one from scratch AOSP if you wanted to.
There are plenty of guides on the internet, and if you run into an issue, someone else has likely already asked about it and received an answer.
Click to expand...
Click to collapse
Thanks. I'll try to look for something over AOSP
You interested in teaming?
DOBBY0 said:
You interested in teaming?
Click to expand...
Click to collapse
i am same as the guy who started this thread. and fyi im interested in teaming.
You can hit my up on Hangouts and we can discuss some stuff. My name is Michael Stevens. Hers my G+ page https://plus.google.com/u/0/+MichaelStevens_DOBBY0/about
burakd0gan said:
i am same as the guy who started this thread. and fyi im interested in teaming.
Click to expand...
Click to collapse
^^^^^^^^^^^^^
I'd also be interested in learning how to manage/develop a custom rom. Let's get Team n00b started up
I´m bumping this topic though the last answer is over one month ago
Creating, managing a Custom ROM of any kind is very time consuming and some people will always expect you to release updates as fast as possible and to work for free Even if you´ve set up your developing environment ( I use Linux ), you will need a lot of patience and a hell of a PC to compile stuff without waiting too long.
If I were you I would think twice if I want to a) build a ROM for yourself only or b) also go through the pain of maintaining a thread, webspace and online support.
The Nexus forums are crowded with AOSP based ROMs and I don´t think that one thread more or less would matter. What I build for myself simply needs to be reliable without 1000x different Mods or Themes.
Since I barely have any time for this hobby anymore, I stick to a) only and even by doing so, I will also waste a lot of time since sometimes there are unforeseen consequences
Yes. That's what I ended too. It would take too much time and resources. I just stopped thinking about that (because my linux pc is very old, too) and used a good ROM.
Thanks!
Quick question
I'm trying to build M developer preview from AOSP. I'm currently syncing the repo with the command:
Code:
repo init -u https://android.googlesource.com/platform/manifest.git -b android-m-preview
After this is synced I will add my device to the appropriate folder with the code:
Code:
git clone https://android.googlesource.com/device/lge/hammerhead.git -b android-m-preview hammerhead
After this will I be able to compile and build?
Am I on the right track?
t3al said:
Quick question
I'm trying to build M developer preview from AOSP. I'm currently syncing the repo with the command:
Code:
repo init -u https://android.googlesource.com/platform/manifest.git -b android-m-preview
After this is synced I will add my device to the appropriate folder with the code:
Code:
git clone https://android.googlesource.com/device/lge/hammerhead.git -b android-m-preview hammerhead
After this will I be able to compile and build?
Am I on the right track?
Click to expand...
Click to collapse
Correct me if I'm wrong, but you can just add the device specific code on the manifest (by modifying .repo/manifest/default.xml)
F4uzan said:
Correct me if I'm wrong, but you can just add the device specific code on the manifest (by modifying .repo/manifest/default.xml)
Click to expand...
Click to collapse
I didn't add my device on the manifest. I followed another guide specifically for my phone and AOSP.
Now, I'm stuck at this:
Code:
Header: out/target/product/hammerhead/obj/include/gps.utils//loc_log.h
make: *** No rule to make target `hardware/qcom/gps/utils/log_util.h', needed by `out/target/product/hammerhead/obj/include/gps.utils//log_util.h'. Stop.
make: *** Waiting for unfinished jobs....
Header: out/target/product/hammerhead/obj/include/gps.utils//loc_cfg.h
I used the Preview binaries from Google.
Does this mean the latest blobs do not compile for M?
Edit: Found my answer here
Hi! I own the Nexus5X and I am interesting in creating a custom ROM for the device. I have synced the AOSP source tree, gotten everything set up and flashed a build on to my device.
How can I start creating a ROM for the device? What are some general guidelines? How do I start tweaking apps, adding features, etc.
Also, if someone could take a look at these errors I am getting with my AOSP build that would be awesome: https://forum.xda-developers.com/nexus-5x/help/issues-aosp-built-source-bullhead-t3555439
Thanks
NateDev said:
Hi! I own the Nexus5X and I am interesting in creating a custom ROM for the device. I have synced the AOSP source tree, gotten everything set up and flashed a build on to my device.
How can I start creating a ROM for the device? What are some general guidelines? How do I start tweaking apps, adding features, etc.
Also, if someone could take a look at these errors I am getting with my AOSP build that would be awesome: https://forum.xda-developers.com/nexus-5x/help/issues-aosp-built-source-bullhead-t3555439
Thanks
Click to expand...
Click to collapse
Hello,
If you have interest in develop a custom rom, i suggest you start at XDA University to learn a bit of everything about Android.
You have some great guides on Android Software Development (look at stick posts)
I have my own guide which is not finished but I will teach everything you need to know about build a custom ROM from source, how to use github, git, mergetool etc... You can follow my progress HERE
FSadino said:
Hello,
If you have interest in develop a custom rom, i suggest you start at XDA University to learn a bit of everything about Android.
You have some great guides on Android Software Development (look at stick posts)
I have my own guide which is not finished but I will teach everything you need to know about build a custom ROM from source, how to use github, git, mergetool etc... You can follow my progress HERE
Click to expand...
Click to collapse
OK thanks, I will take a look at that. If possible, could you take a look at the errors I am getting with my AOSP build? I posed the link in the original post. Also, do you have to run extract-files.sh or can you simply download the vendor binaries from Google and run the extracting script? (AOSP)
NateDev said:
Also, do you have to run extract-files.sh or can you simply download the vendor binaries from Google and run the extracting script? (AOSP)
Click to expand...
Click to collapse
If you fork/download vendor binaries you don't need to run extracting script