Building CM10 - Galaxy Tab 2 General

I had been building CM for my Nook Color using the most excellent instructions from Fattire and group. I got a new p5113 and attempted to build using the instructions from http://wiki.cyanogenmod.org/index.php?title=Build_for_p5113
However, when I got to
Code:
breakfast p5113
there was no device p5113. p5110 was there, but not p5113. How I got it to work was to re-repo init using
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
rather than
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Once I did that I could successfully
Code:
breakfast p5113
and finish the process. It looks to be building as expected now, though I am sure it will be several hours before I know for sure. I will post back if the build stops.
Please forgive me if this is covered elsewhere, but a quick search didn't help me and I could not make a comment directly on the page linked above with the instructions. Hopefully this will help someone who is stuck at this same point.
Cheers

So I need to read more closely. The directions linked to in the OP for installing p5113 ("http://wiki.cyanogenmod.org/index.ph...uild_for_p5113") are really for p5110. But I was trying to breakfast/brunch p5113. However- all of the necessary code downloads when I repo sync '-b jellybean' and breakfast p5113.
Problem is that I had already installed one of the prebuilt CM10 nightlies, so the vendor files that I pulled are incorrect. At least I think that is correct. When I get home I will re-flash back to stock and try to pull the vendor files for p5113 and try to build again. Since the only difference AFAIK is the IR Blaster, maybe that is close to working.

Actually, CM10.1 still in developing. I think the cyanogenmod team will be bring their ROM in stable soon.

jamesh0317 said:
So I need to read more closely. The directions linked to in the OP for installing p5113 ("http://wiki.cyanogenmod.org/index.ph...uild_for_p5113") are really for p5110. But I was trying to breakfast/brunch p5113. However- all of the necessary code downloads when I repo sync '-b jellybean' and breakfast p5113.
Problem is that I had already installed one of the prebuilt CM10 nightlies, so the vendor files that I pulled are incorrect. At least I think that is correct. When I get home I will re-flash back to stock and try to pull the vendor files for p5113 and try to build again. Since the only difference AFAIK is the IR Blaster, maybe that is close to working.
Click to expand...
Click to collapse
You actually are almost correct... Recently they completely removed the 3113 and 5113 versions as the only difference was in the IR blaster, which doesn't work on CM anyways...
Sent from my XT907 using Tapatalk 2

Related

[DEV TOOL] EasyDev-v9 - "Roll Your Own" [8-28-11]

This is a continuation of the "Compiling CM6 for Eris" thread - http://forum.xda-developers.com/showthread.php?t=856215. But since Team ADX has really come together on this, we are releasing it in it's new form.
Thanks to workshed for working to get the Eris on the Official CM list and merged into the main repo. And also, thanks to workshed for most of the v6 --> v7 changes to EasyDev!
This script will grab CM7 source and compile a CM7 ROM for you using the official vendor tree that is built-in to the CM source. You have the option of including Google Apps or not.
Uses:
CM source - https://github.com/CyanogenMod/android.git
Conap's CFS kernel that's built-in to CM source - https://github.com/Conap30/htc_kernel_desirec_cfs
Requirements
-------------
1) 64- bit Linux -tested on Debian, Ubuntu 10.04, Linux Mint (if you have a different flavor of linux and easydev worked for you, please let us know so we can update this list)
2) An existing Eris ROM that the script will pull the proprietary files from.
INSTRUCTIONS
1) Download the script
2) 'chmod a+x easydev-v9.sh'
3) copy it to the directory of your choice or leave it where it is
4) copy an existing ROM to the same directory (tested with GSB, but most should work)
5) run it ('sudo ./easydev-v9.sh')
Possilbe future features:
Done.
Changelog
v1 - initial release
v2 - added squisher, made 'make clean' optional, added installation of dependencies, cleaned up output
v3 - uses existing ROM to pull proprietary files, renamed to 'easydev' for case sensitive linux admins
v4 - fixed file missing from list in unzip-files.sh in vendor tree, fixed move/rename of existing ROM, change 'make clean' option to default to no instead of yes
v5 - added 'apt-get update' to refresh repo list (should install dependencies now), swapped order of extract-files and unzip-files to fix 'chmod akmd' issue, tried not to break anything else
v6 - moved questions to beginning of script, added check to only init repo the first time, added check for existing ROM, modded vendor tree to fix compile issues
v7 - removed CM6 stuff, removed kernel compilation code, removed vendor tree code, changed from CM6 to CM7, fixed path bug, added 32-bit libs to dep list
v8 - added ALL official CM devices (mostly untested), minor update to dependency installer code (4-21-11)
v9 - added an extra check for correct Java version, fixed .zip rename issue
Download links:
v7+ --> https://github.com/gnarlyc/EasyDev-Eris
NOTE: If you have issues with google setup or not being able to pass andy the android at the beginning of setup, please delete Provisions.apk for system/app you shouldn't have a problem, but just incase, this will remedy it. -workshed
I'm all over this sh*t
Oh damn, I'm excited for this. good thing I use ubuntu!
Sent from my ERIS using XDA App
this should be fun once i get my new laptop.
Nice! I will be trying this later.
This is awesome! Thanks alot. What does the 'make clean' option do?
Skrip037 said:
This is awesome! Thanks alot. What does the 'make clean' option do?
Click to expand...
Click to collapse
The make clean removes everything that has been compile so far leaving only the original source.
Skrip037 said:
This is awesome! Thanks alot. What does the 'make clean' option do?
Click to expand...
Click to collapse
It removes any previously built ROMs, etc. It's not needed every time, so I've made it optional in the next version. The problem was that sometimes the script would be broken in some way and wouldn't build a ROM. But, there's so much text displayed to the screen, it's not always easy to notice. So, I was actually flashing the same test ROM over and over instead of getting a new build...
Great work guys. Going to try it out on Arch Linux and if anyone's interested I'll give details about how to get it working there (or just modify the script to detect Arch as opposed to Ubuntu and work accordingly.
<gripe>One complaint: commands (including scripts) should *always* start with a lowercase letter </gripe>
good work gnarlyc & conap.
this sounds great and i will be trying this when i get home. I have just one question. Why would i want to run this instead of conap's rom? Both being pure CM. I see alot of the other cm6 roms have stuff themed, but conap's rom doesn't. I'm assuming this is complete pure cm without little tweaks done by devs of the respective roms. Thanks in advance.
ngc604 said:
this sounds great and i will be trying this when i get home. I have just one question. Why would i want to run this instead of conap's rom? Both being pure CM. I see alot of the other cm6 roms have stuff themed, but conap's rom doesn't. I'm assuming this is complete pure cm without little tweaks done by devs of the respective roms. Thanks in advance.
Click to expand...
Click to collapse
Some people just like to "roll their own", more or less. If you like having someone else make improvements and fix issues for you, then you'll probably want to stick with another ROM.
I would love to make my own fixes and tweaks but i dont have the knowledge nor the time to gain said knowledge. guess i will just stick with the devs roms. thanks
Very very exciting. I am installing Ubunto 10.4 now. So does EasyDev-v2 pull from the CM6 nightlies or the stable version and can we change where it pulls from for the CM6 source. This is great.
Will have to check this out later. Always wanted to understand the compile process, always to busy with other software projects. Thanks for building this resource for the rest of us.
morrisdan said:
Very very exciting. I am installing Ubunto 10.4 now. So does EasyDev-v2 pull from the CM6 nightlies or the stable version and can we change where it pulls from for the CM6 source. This is great.
Click to expand...
Click to collapse
Hmmm. Someone correct me if I'm wrong, but I'm pretty sure that this is currently grabbing 'stable'.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b froyo
I'm thinking that to get the nightly, we'll have to change that to:
Code:
repo init -u git://github.com/CyanogenMod/android.git -b master
I'll try it as soon as I can. You got me to thinking that we could add that as an option, if I understand this correctly.
Nightly vs Stable
Yes, you answered my question regarding nightly and stable. I am having fun so far. I got all the necessary packages installed. That was pretty easy using the Ubunto package manager deal. So where do I find the proprietary.zip now? I am almost there to cook this sucker up.
morrisdan said:
Yes, you answered my question regarding nightly and stable. I am having fun so far. I got all the necessary packages installed. That was pretty easy using the Ubunto package manager deal. So where do I find the proprietary.zip now? I am almost there to cook this sucker up.
Click to expand...
Click to collapse
I was apparently wrong about the "-b master" switch, but I think I mostly got it right...
Right now, you'll have to grab the files listed in the OP and zip them up into a file called 'proprietary.zip'. Then place it in the same directory that you run the script from.
I'm working on a way that you can just place an existing ROM there, and it will extract the proprietary files for you. That should be in v3.
Proprietary.zip Files
Can I download CELB Froyo 3.8 and uncompress it and do searches for those files and pull them out and zip them up?
morrisdan said:
Can I download CELB Froyo 3.8 and uncompress it and do searches for those files and pull them out and zip them up?
Click to expand...
Click to collapse
Yes, that should work fine. Here's a list with the paths -
https://github.com/Conap30/android_device_htc_desirec/blob/master/extract-files.sh

[Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N7000

This is the port of Ubuntu Phone to the Samsung Galaxy Note GT-N7000
What works:
Wifi (fixed on 18-07)
GSM (only mobile connection)
Webbrowsing
Taking photos (fixed)
If you haveing trouble with GSM give it time to connect. If its still not working check this : https://plus.google.com/100264483712374857174/posts/3o1tjYo9Ghx
CREDITS
thanks to chasmodo for
manifest additions
camera driver
runtime intermediates files
thanks to Gerrett for
the hint to remove the GalaxyNoteSettings from build
fixing the wifi issue
The short way:
Download, push to sdcard, reboot to recovery, do a backup, do a full wipe and flash(keep the order of the files)
quantal-preinstalled-phablet-armhf.zip
Ubuntu n7000 nightly build
The long way:
Here is the official Canonical's Porting Guide
here we have the cm nightlies from wich we take the binaries for the base system.
Now, I will set up my building system how described in the Guide (Since I've already a working Ubuntu 13.04 x64 PreAlpha installation, I'll use that as base)
Seting up the development environment
What is not in the guide:
Code:
sudo apt-add-repository ppa:phablet-team/tools
sudo apt-get update
sudo apt-get install phablet-tools
sudo apt-get install bzr
sudo apt-get remove openjdk-7-jdk
sudo apt-get install openjdk-6-jdk
So, on the console
(if there are german speaking people following, this is how you can kill the waiting time http://www.youtube.com/watch?v=S_poaB9jLAc and http://www.youtube.com/watch?v=eMim3OV2cQE and http://www.youtube.com/watch?v=1-jbeV_kpaU have fun)
Code:
mkdir -p UbuntuTouch/GT-N7000 #at a location with 20 gigs of free space(yes, its a lot :D )
cd UbuntuTouch/GT-N7000
git config --global user.email "[email protected]" #needs this only once for
git config --global user.name "Your Name"
phablet-dev-bootstrap ./ #this will take a while, it will download all sources except the kernel if I understood right
Edit .repo/manifest.xml and add following at the same xml level where the other project tags are.
(First search for, maybe they are already in that file)
Code:
then again on console:
Code:
repo sync
Code:
adb devices #just a short check to see if the connection is working, if it's in the list, go further, if not check whats the problem
. build/envsetup.sh
brunch cm_n7000-userdebug #if everything is ok, this will take a while
put the zip you get in the output onto your sdcard, download saucy-preinstalled-phablet-armhf.zip
reboot your n7000 into recovery mode, backup and flash first the preinstalled and then the build.
Have fun
Sounds good...keep us updated
Thanks
I have the required changes ready in the files incase someone is interested
was waiting for beerbong but he seems busy... times like these u wish u werent building remotely ^^
maybe utacka or chas(with his new pc) can help..
AW: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
So what does that mean toxic? Do u already ported it? ??
no I'll try it this weekend
Re: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
You don't have to use cm, you can use AOSP.
You can even use Samsungs kernel source (I haven't bothered building the latest so no idea how good it is our not) and the binary blobs from the latest stock build.
I'm building it for one of my tablets at the mo from AOSP, using an old but working kernel.
Sent from my GT-N7000 using Tapatalk 2
fards said:
You don't have to use cm, you can use AOSP.
You can even use Samsungs kernel source (I haven't bothered building the latest so no idea how good it is our not) and the binary blobs from the latest stock build.
I'm building it for one of my tablets at the mo from AOSP, using an old but working kernel.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
First of all I'll use what the guide suggests. Playing games comes after.
Re: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
fards said:
You don't have to use cm, you can use AOSP.
You can even use Samsungs kernel source (I haven't bothered building the latest so no idea how good it is our not) and the binary blobs from the latest stock build.
I'm building it for one of my tablets at the mo from AOSP, using an old but working kernel.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
For a device such as ours, don't think deviating from CM is a good idea
Sent from my GT-N7000 using xda premium
Re: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
I was reading over the guide and would have to say there is a lot of set up involved
Sent from my GT-N7000 using XDA Premium HD app
Good luck man! Subscribed to the thread! i hope you'll make it!
Sorry, missed coming back to this thread.
For SUID changes, the mentioned file is found at -
device/samsung/galaxys2-common/rootdir/fstab.smdk4210
The Brightness settings dont need to be changed as those changes are already present I think.
AW: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
Yeah,seems to be server problems, i'm syncing since yesterday, but now i can the see the end
Edit: Seems like to many people are syncing now .. cant sync anything atm ..
Gesendet von meinem GT-N7000 mit Tapatalk 2
hey,
i saw this previews for the mako, i dont know if this will help you guys to port it for the N7000, afaik they can simply be flashed in recovery :cyclops:
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/
T1663R said:
hey,
i saw this previews for the mako, i dont know if this will help you guys to port it for the N7000, afaik they can simply be flashed in recovery :cyclops:
http://cdimage.ubuntu.com/ubuntu-touch-preview/quantal/mwc-demo/
Click to expand...
Click to collapse
they are for galaxy nexus, nexus 4, 7 and 10.
Yep, having sync troubles at this end as well. Must be lots of us trying to make this work. Good to know the GT-N7000 is so popular? Keep getting "fatal: The remote end hung up unexpectedly".
Re: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
Can we please get a dedicated section for ubuntu on the note mods?
Sent from my GT-N7000 using xda premium
Ok so i've been afk most weekend. How's it going? Any luck getting ubunutu on our notes?
This way I'll never have to change my device. You guys always keep bringing new stuff to it
Thanks a lot to all the amazing work all the devs around here are doing. Love you all
AW: [Ubuntu Touch] Porting the Ubuntu Touch Developer Preview to GT-N700
Repo is synced .. and all stuff done from ubuntus guide. But get build error. Will look at it tomorrow. Anyone got it to build?
Edit: okay, it only wants to build the note settings, needs to be removed from makefile.
Will now build overnight an hope its rdy in the morning
Gesendet von meinem GT-N7000 mit Tapatalk 2
fards said:
You don't have to use cm, you can use AOSP.
You can even use Samsungs kernel source (I haven't bothered building the latest so no idea how good it is our not) and the binary blobs from the latest stock build.
I'm building it for one of my tablets at the mo from AOSP, using an old but working kernel.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Forgive my offtopic, i'm interested of using Samsung sources for Galaxy SII i9100, instead of cyanogenmod 10.1, that isn't properly good for this device. can you tells me more about that?

Guide to build cm10 needed

Hi guys i'm getting an atrix to help out and play with. I don't have att instead i have Verizon so this is just for fun. I have a Galaxy Nexus and the forums are full of info to building roms and kernels so i figured i would start my own cm10 rom for myself and if at some point down the road others. I found this link http://wiki.jeago.com/index.php?title=Build_for_olympus and desided i would give it a go and at least have a base. However i ran into a problem, When i get down to the "lunch" command i do not have "cm_olympus-userdebug" listed? can anyone steer me on the right path or is this an old Link that has since been pulled? Thanks guys
Doesn't matter if it's not listed. As long as you have synced the right repo, "lunch cm_olympus-userdebug" still works as expected.
I think it pulls the list from the official CM10 repo (which does not include olympus), but the command will work with the files you've synced (which does include olympus).
quetzalcoatl2435 said:
Doesn't matter if it's not listed. As long as you have synced the right repo, "lunch cm_olympus-userdebug" still works as expected.
I think it pulls the list from the official CM10 repo (which does not include olympus), but the command will work with the files you've synced (which does include olympus).
Click to expand...
Click to collapse
Hi. Correct me if I'm wrong, but I guess that the official CM repositories doesn't have branches later than CM7 for the olympus. You have to get them somewhere else for CM9 and later.
Yes, that's what I said. The official CM10 repo does not include olympus.
Get them here: https://github.com/epinter/android/tree/jb-olympus
kicker22004 said:
Hi guys i'm getting an atrix to help out and play with. I don't have att instead i have Verizon so this is just for fun. I have a Galaxy Nexus and the forums are full of info to building roms and kernels so i figured i would start my own cm10 rom for myself and if at some point down the road others. I found this link http://wiki.jeago.com/index.php?title=Build_for_olympus and desided i would give it a go and at least have a base. However i ran into a problem, When i get down to the "lunch" command i do not have "cm_olympus-userdebug" listed? can anyone steer me on the right path or is this an old Link that has since been pulled? Thanks guys
Click to expand...
Click to collapse
I used "generic_olympus-userdebug" for the lunch command and afterwards the "cm_olympus-userdebug" appears among the options.
---------- Post added at 08:38 PM ---------- Previous post was at 08:30 PM ----------
quetzalcoatl2435 said:
Yes, that's what I said. The official CM10 repo does not include olympus.
Get them here: https://github.com/epinter/android/tree/jb-olympus
Click to expand...
Click to collapse
Ooops, read too fast, my apologies...
I forked vendor, device and kernel repositories from CyanogenMod-Atrix github, but these are pre-alpha repos with known (and unknown) bugs. (BTW, though it compiles fine, the recovery won't install the resulting zip on my Atrix, still figuring out what's wrong)
ok now i'm getting way lost here. how do i go about adding this to my current files?
ok guys i just noticed that the link i was following had me pulling ICS not JB...wow i'm slow today.
Wiped everything and starting fresh. anyone have a guide to pull the needed build. Atrix4g18 sugested i needed https://github.com/epinter/android/branches and jb-olympus-new. I'm going to start over and this time pull repo init -u git://github.com/CyanogenMod/android.git -b jellybean instead of the ICS and then i should be at least closer to what i need.
kicker22004 said:
ok now i'm getting way lost here. how do i go about adding this to my current files?
ok guys i just noticed that the link i was following had me pulling ICS not JB...wow i'm slow today.
Wiped everything and starting fresh. anyone have a guide to pull the needed build. Atrix4g18 sugested i needed https://github.com/epinter/android/branches and jb-olympus-new. I'm going to start over and this time pull repo init -u git://github.com/CyanogenMod/android.git -b jellybean instead of the ICS and then i should be at least closer to what i need.
Click to expand...
Click to collapse
I'm not sure how to use the default.xml file in the link that quetzalcoatl2435 gave us, but in my case I created a local_manifest.xml file (from here) with the extra repos I needed and copied to .repo/local_manifest directory in the source tree root.
EDIT:
I think I got it, someone who really knows please confirm: instead of the deffault CM repo init, issue this: repo init -u git://github.com/epinter/android.git -b jb-olympus-new. Is that right?
OK for the time being i'm going to start rebuilding my repo again. i scratched everything so have to download the JB repo now. anyone with more info to using the Default.xml file or where it should be placed? Thanks guys
After looking at the Default.xml it seems he just added the Atrix to the list so i would assume i will copy paste and rerun repo sync? should i copy first then run repo sync or no?
All i have to say is thank you Verizon LTE with unlimited data and free tether LOL.
Don't use jb-olympus-new. That's for the new kernel and does not have the proprietary files included. You need to search for and add them manually.
Use this:
repo init -u git://github.com/epinter/android.git -b jb-olympus
repo sync
Assuming you've already installed all pre-requisites correctly, next do:
. build/envsetup.sh
lunch cm_olympus-userdebug
brunch olympus
Sent from my MB860 using xda app-developers app
kicker22004 said:
ok now i'm getting way lost here. how do i go about adding this to my current files?
ok guys i just noticed that the link i was following had me pulling ICS not JB...wow i'm slow today.
Wiped everything and starting fresh. anyone have a guide to pull the needed build. Atrix4g18 sugested i needed https://github.com/epinter/android/branches and jb-olympus-new. I'm going to start over and this time pull repo init -u git://github.com/CyanogenMod/android.git -b jellybean instead of the ICS and then i should be at least closer to what i need.
Click to expand...
Click to collapse
No need to pull CyanogenMod's github. It's included in epinter's github. No need to mess with the xml files either, just repo sync, lunch, and brunch.
kicker22004 said:
Hi guys i'm getting an atrix to help out and play with. I don't have att instead i have Verizon so this is just for fun. I have a Galaxy Nexus and the forums are full of info to building roms and kernels so i figured i would start my own cm10 rom for myself and if at some point down the road others. I found this link http://wiki.jeago.com/index.php?title=Build_for_olympus and desided i would give it a go and at least have a base. However i ran into a problem, When i get down to the "lunch" command i do not have "cm_olympus-userdebug" listed? can anyone steer me on the right path or is this an old Link that has since been pulled? Thanks guys
Click to expand...
Click to collapse
Just curious. Is this ROM going to be public?
quetzalcoatl2435 said:
No need to pull CyanogenMod's github. It's included in epinter's github. No need to mess with the xml files either, just repo sync, lunch, and brunch.
Click to expand...
Click to collapse
I think for the most compatible with the new kernel will need to add 2 more branches
github.com/CyanogenMod-Atrix/android_device_motorola_olympus.git
github.com/CyanogenMod-Atrix/android_vendor_motorola_olympus.git
Xerox98 said:
Just curious. Is this ROM going to be public?
Click to expand...
Click to collapse
How about you read the other threads before asking?
mapkel said:
I think for the most compatible with the new kernel will need to add 2 more branches
github.com/CyanogenMod-Atrix/android_device_motorola_olympus.git
github.com/CyanogenMod-Atrix/android_vendor_motorola_olympus.git
Click to expand...
Click to collapse
No need to add android_device_motorola_olympus.git to jb-olympus-new. It's already included by epinter. You only need to add the vendor files.
BTW, I was talking about the jb-olympus branch, not the jb-olympus-new branch.
The new branch is not for daily use (yet).
Thanks you guys. I had a github time out earlier so will be starting fresh here soon.
Sent from my Galaxy Nexus using xda app-developers app
And the countdown begins..... I have another 8gb of ram i removed thinking it was causing Build issues for my Gnex (turns out it was missing some blobs...oops) i'll be putting that back in before i start building. Going to start with a clone copy of this rom, Anyone know what happens with the new kernel and this? Yes i know it's alpha but i'm testing so that's what i need to focus on.
ok guys i went over this a few times and I found a few errors that i was able to fix by installing packages that were missing (13.04 64-bit btw). But i'm stuck on this one. anyone have any idea? this is after the Brunch olympus command. After more hunting on google seems i might need (sudo apt-get install libxml2-utils) so starting the Brunch again we'll see.
ravilov said:
How about you read the other threads before asking?
Click to expand...
Click to collapse
? I have pritty well read every post in the Atrix forum. I just wanted to know if this ROM would be made public when ready, so that there is another CM10 rom apart from Epinters.
this is from epinter's source. The first post says that i'm building this for fun and to help out if i can, and at some point down the road MAYBE be a public rom, my skills are limited and i don't feel at this stage that i'm rdy to release a ROM to the public, that's not saying i won't..just not soon. As for now i'm thinking i should be building this on 12.04 LTS because i keep running into Compiling errors... now i've got another one that's im trying to figure out.
Anyone have any idea's what i'm missing now lol.

[Q] Building 4.4 for Manta

So I've updated all of my repo's to the 4.4 branch. I'm curious if anybody else has built 4.4 for the Nexus 10 yet? If so, did you get it booting? 4.4 OmniROM, of course. If you did, did you use TheMuppet's repository when you did, or was it just straight OmniROM/what local manifests do you have?
EDIT: Just saw the other thread on here about TheMuppets. Possibly solved. Resolving that. If I'vea lready repo sync -j4'd with that in my local manifests, can I undo that or do I start from scratch?
Just delete the blob repo from omni/.repo and from vendor/ and resync, you'll be fine.
iofthestorm said:
Just delete the blob repo from omni/.repo and from vendor/ and resync, you'll be fine.
Click to expand...
Click to collapse
I did get it booting
Sent from my Nexus 10

[Guide] [09/14/2015] Building AOSP 5.1.1_r14 for the Nexus 6-Continued!

Building AOSP for the Nexus 6 - Continued!​
Scott is no longer working with the N6 and he has graciously allowed me to continue his thread . We all owe @scrosler a special THANKS for his work on the original thread. Better yet please go buy him a beer!! I also want to personally thank all who contributed to the original thread. You all make it work!!
​
Preface
1. I want to start by saying that I am still a relative newb. I built my first aosp rom for my N9 using the the guide from the original thread and followed up with one for my N6. I hope that by moving this thread forward we can continue to help others get started while we continue our own learning.
2. All questions concerning the build process and setup are welcome. They may not all get answered but please ask.
This guide continuation assumes the following:
1. You have read the original thread's OP and scanned the remainder of that thread before posting here.
2. To get things started you can test a rom built from android-5.1.1_r14. Get rom below. Vendor blobs updated from here and include the updated LYZ28E blobs. I also added some missing build props.
3. I am also linking the github source for the rom. You can build your own. Get github source below.
4. I hope to add a short get started github tut in OP#2 and add a vendor folder setup discussion in OP#3. I'm still trying to figure out how @sykopompos did his. All help on this subject is welcome.
FYI TO ALL!!! All my testing is on USA Verizon netwok.
LINK TO ORIGINAL THREAD OP
Get ROM HERE
Get GIT SOURCE HERE
==========================================================================================================
The following copied from original OP with some minor editing.
This guide assumes the following
Have Ubuntu 14.04 or equivalent setup, fully operation, and up to date. Hard Machine or Virtual, makes no difference. Must meet the minimum specs for compiling. Info from Google HERE
Understand terminal command line entry as this is all command line processes.
Lets Begin!
Add Java
Code:
sudo apt-get install openjdk-7-jdk
Add Build tools (Adds the required packages at the time of this posting)
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386
Add Repo command (Syncs Google Repository with your local machine)
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Add bin folder to path for repo command (After you do this close Terminal and re-open to institute changes (easy way))
Code:
sudo gedit .bashrc
export PATH=~/bin:$PATH <-(add to end of bashrc)
Identify Yourself to the Repo (One day you may make commits so think about that when choosing your info!)
Code:
git config --global user.email "[email protected]"
git config --global user.name "yourpreferredusername"
Sync Repo (Download source... Sit back and grab a pop and a sandwich...)
Code:
mkdir ~/AOSP
cd ~/AOSP
repo init -u https://android.googlesource.com/platform/manifest -b android-5.1.1_r14
repo sync
Note: I use AOSP as my directory name. You can use what you want. You could use "aosp" or "Source" or "android" or "whateveryoulike"
Set up ccache (this makes subsequent compiling much faster!)
First: Close then re-open the terminal so you are in the home root
Code:
sudo gedit .bashrc
export USE_CCACHE=1 <-Append that line to .bashrc then save and close
cd AOSP
prebuilts/misc/linux-x86/ccache/ccache -M 25G <-I use 25 gigs but you can change that value to any size you feel appropriate)
fhem Alternate ccache setup.
Install ccache using package manager (I use synaptic)
set ccache size - One ccache for all directories.
Code:
ccache -M 35G (I use 35 gigs but you can change that value to any size you feel appropriate)
I do not edit my .bashrc I use the following before my final make command. See Readme Build It
You can choose to use or not use ccache for any build/operation from any directory.
Code:
export USE_CCACHE=1
ccache manual
Install proprietary binaries (Needed for things like GPS and Bluetooth, they are not Open Source like Android) (Install proprietary binaries from here in the root of AOSP folder (or whatever you called yours))
Code:
https://developers.google.com/android/nexus/drivers
Run envsetup.sh
Code:
source build/envsetup.sh
Choose Device
Code:
lunch aosp_shamu-userdebug
Build it!
Code:
make -j16 otapackage
Note: using -j16 means 16 worker threads. This is fine if you have 8 logical CPU's so you may need to adjust that to a smaller or larger number if you have more or less Logical CPU's. Example: I have an i7 K edition Haswell so I have 8 logical cores; so I build with -j16. If you have an i5 quad core CPU which is 4 logical cores then you may want to consider -j8 as the set number of worker threads. Oddly enough Google actually recommends 3 to 4 times the number of logical CPU's. When I do that I have nothing but build crashes. You may need to experiment to get the right blend of performance and stability during build!
If you use
Code:
make -j `getconf _NPROCESSORS_ONLN` otapackage
it may take a little longer but it won't crash.
Find it
Should be located here: /home/yourusername/AOSP/out/target/product/shamu
Congrats!
Your know among the elite enthusiast that can build from source! Pat yourself on the back!
Git Hub Tips
There is already much written on git use so I am not going to try and reinvent that wheel!!!! I will provide some usefull links for your reading pleasure. I will also provide some tips based on my personal experiences using git. I have found there are many ways to get the same result using git and there are also many ways to break your your work. I did a lot of trial and error and deleting to learn what works best for me. Start small, don't be intimidated, and stay patient -- it will come. The following assumes we are using a linux distro.
1. Open a GitHub account ----- its easy. Keep it simple. Follow the setup instructions and use recommended HTTPS connection.. I also suggest caching your login info - I use 60 mins for my default cache time.
2. Install git. It is easiest to install Git on Linux using the preferred package manager of your Linux distribution. I use Synaptic Package Manager. Keep it simple. Follow the setup instructions and use recommended HTTPS connection.
3. Git Tools: I prefer using Geany with terminal and File and Tree Browser and VC control plug-ins. There are many tools available and you may need to find one that works for you. You can install Geany and its plug-ins using your distro package manager.
4. ROM Tree Structure Very Important. I recommend keeping your rom GitHub tree structure in line with the Android Git Repositories.
Useful links:
1. http://git-scm.com/docs
2. http://gitref.org/creating/
3. http://forum.xda-developers.com/showthread.php?t=1877040 Thanks @eagleeyetom
4. http://forum.xda-developers.com/showthread.php?t=2763236 Thanks @jabza
5. http://forum.xda-developers.com/showthread.php?t=2329228 Thanks @Red Devil
I hope the above is helpful to getting you started on GitHub. Good Luck!!
reserved vendor folder discussion.
fhem said:
Building AOSP for the Nexus 6 - Continued!​
Scott is no longer working with the N6 and he has graciously allowed me to continue his thread . We all owe @scrosler a special THANKS for his work on the original thread. Better yet please go buy him a beer!! I also want to personally thank all who contributed to the original thread. You all make it work!!
​
Preface
1. I want to start by saying that I am still a relative noob. I built my first aosp rom for my N9 using the the guide from the original thread and followed up with one for my N6. I hope that by moving this thread forward we can continue to help others get started while we continue our own learning.
2. All questions concerning the build process and setup are welcome. They may not all get answered but please ask.
This guide continuation assumes the following:
1. You have read the original thread's OP and scanned the remainder of that thread before posting here.
2. To get things started you can test a rom built from android-5.1.1_r4 using Sykopompos vendor blobs for 5.1. Get rom below.
3. I am also linking the github source for the rom. You can build your own. Get github source below.
4. I hope to add a short get started github tut in OP#2 and add a vendor folder setup discussion in OP#3. I'm still trying to figure out how Sykopompos did his. All help on this subject is welcome.
FYI TO ALL!!! All my testing is on USA Verizon netwok.
LINK TO ORIGINAL THREAD OP
Get ROM HERE
Get GIT SOURCE HERE
Click to expand...
Click to collapse
Lots and lots of dark magic ?
Hey great to see you. I thought you were kyaking LOL. You coming back for M????
fhem said:
Hey great to see you. I thought you were kyaking LOL. You coming back for M????
Click to expand...
Click to collapse
I actually just ordered my kayaking last night so hopefully I'll have it in time for next weekend.
Just popping in really and checking M out and seeing how it develops
sykopompos said:
I actually just ordered my kayaking last night so hopefully I'll have it in time for next weekend.
Just popping in really and checking M out and seeing how it develops
Click to expand...
Click to collapse
Still waiting for the full platform on aosp. Hey did you diff the stock rom and aosp rom to get your vendor blobs. I was setting up with BeyondCompare to give it a look. LOL Enjoy your time off and your family. Life is too short.
fhem said:
Still waiting for the full platform on aosp. Hey did you diff the stock rom and aosp rom to get your vendor blobs. I was setting up with BeyondCompare to give it a look. LOL Enjoy your time off and your family. Life is too short.
Click to expand...
Click to collapse
For the most part, you can diff and find file differences but aosp has it's own files and stuff like that so you gotta be able to figure out what they do
sykopompos said:
For the most part, you can diff and find file differences but aosp has it's own files and stuff like that so you gotta be able to figure out what they do
Click to expand...
Click to collapse
I was afraid you were going to tell me that. :laugh: Oh well It will give my old brain and google a workout. hahahaha Thanks and enjoy yourself.
Hey @fhem! Glad to see you take over, you're always very helpful!
In your Repo Int code above, did you mean "android-5.1.1_r4"? I wanted to double check that part for the guide.
purian23 said:
Hey @fhem! Glad to see you take over, you're always very helpful!
In your Repo Int code above, did you mean "android-5.1.1_r4"? I wanted to double check that part for the guide.
Click to expand...
Click to collapse
Yep. That's the latest. That's what I built above if you look at the fhemaosp default manifest.
fhem said:
Yep. That's the latest. That's what I built above if you look at the fhemaosp default manifest.
Click to expand...
Click to collapse
Okay cool! Just trying to save some headache if someone grabs the guide one listed lol.
purian23 said:
Okay cool! Just trying to save some headache if someone grabs the guide one listed lol.
Click to expand...
Click to collapse
Fixed thanks for catching that typo.
sykopompos said:
I actually just ordered my kayaking last night so hopefully I'll have it in time for next weekend.
Just popping in really and checking M out and seeing how it develops
Click to expand...
Click to collapse
Hello @sykopompos, I am just glad to see you here! Thanks for all your contributions!
I let @fhem take over the thread since he is more active than I. But I appreciate all the help you have given and will continue to give!
Knowledge is TRULY priceless!
-Scott
EDIT: Can someone put that on my tombstone, lol
Can we have guide about building ROM from open source? e.g LG open source. Actually I was trying to build a M1 review ROM with the LG open source but it fails. I tried several times and finally give op due to errors. I downloaded the android source and then follow this guide and then download LG G4 ROM from following.
http://opensource.lge.com/osSch/list?types=ALL&search=H815
I set up the environment and then started building but it fails again and again. I think it will be very helpful for every one who interested in building ROM from open source. Thanks
Sent from my LG-H815 using Tapatalk 2
janjan said:
Can we have guide about building ROM from open source? e.g LG open source. Actually I was trying to build a M1 review ROM with the LG open source but it fails. I tried several times and finally give op due to errors. I downloaded the android source and then follow this guide and then download LG G4 ROM from following.
http://opensource.lge.com/osSch/list?types=ALL&search=H815
I set up the environment and then started building but it fails again and again. I think it will be very helpful for every one who interested in building ROM from open source. Thanks
Sent from my LG-H815 using Tapatalk 2
Click to expand...
Click to collapse
I have never worked with any LG source codes. I would suggest you start your own thread on the LG G4 Forum. It definately sounds like you got enough to get one rolling. Good luck with the G4.
Hello,
I am trying to build android 5.1.1_r6 for the Nexus 6 and was able to get it to build and install. Had a weird issue where gapps would not install, but I think I fixed that by flashing a different set of gapps. My issue is that I am unable to hear people through the handset speaker when I make phone calls. I have no idea what it is. Apparently they can hear me, but I cant hear them. I can use speaker phone, but even that seems lower volume than normal.
Also, side question, since I am building AOSP 5.1.1_r6 am I supposed to use the preview binaries found here: https://developers.google.com/android/nexus/blobs-preview
or just use the factory image binaries?
Thank you
KerryWood34 said:
Hello,
I am trying to build android 5.1.1_r6 for the Nexus 6 and was able to get it to build and install. Had a weird issue where gapps would not install, but I think I fixed that by flashing a different set of gapps. My issue is that I am unable to hear people through the handset speaker when I make phone calls. I have no idea what it is. Apparently they can hear me, but I cant hear them. I can use speaker phone, but even that seems lower volume than normal.
Also, side question, since I am building AOSP 5.1.1_r6 am I supposed to use the preview binaries found here: https://developers.google.com/android/nexus/blobs-preview
or just use the factory image binaries?
Thank you
Click to expand...
Click to collapse
I haven't been able to get _r6 to build due to errors in frameworks/opt ever since merging so good for you on that. As for the binaries It was found a while back that the Google one were incomplete. People were using The vendor files from chroma in their stead. I haven't spoken to fhem in a couple of days but it looks like his github is under construction atm. I forked the vendor repo from him since he had changes that fixed some no sound issues as well. Again I've yet to build _r6 successfully so no idea if these will solve your issue but you're welcome to try them out? You can get them from my github here: https://github.com/rockinroyle/platform_vendor_moto_shamu
Let us know how it goes? I'm trying again after I clone frameworks from scratch.
rockinroyle said:
I haven't been able to get _r6 to build due to errors in frameworks/opt ever since merging so good for you on that. As for the binaries It was found a while back that the Google one were incomplete. People were using The vendor files from chroma in their stead. I haven't spoken to fhem in a couple of days but it looks like his github is under construction atm. I forked the vendor repo from him since he had changes that fixed some no sound issues as well. Again I've yet to build _r6 successfully so no idea if these will solve your issue but you're welcome to try them out? You can get them from my github here: https://github.com/rockinroyle/platform_vendor_moto_shamu
Let us know how it goes? I'm trying again after I clone frameworks from scratch.
Click to expand...
Click to collapse
I had no luck with r6 either. I reverted back to r5. I looked at chroma/zephk on git and I don't think he took the whole r6 merge to his git repos - not sure what he did.
I'm sticking to to r5 for now.
I've been building r6 fine with zero issues. Did notice the speaker issue on call but fixed it with two commits from chroma in device/moto/shamu for audio. I've also been using the latest binaries posted by google on the aosp page, no issues that I can tell. WiFi calling/normal calling, sound all around, SMS/MMS, all works.
Sent from my Nexus 6 using Tapatalk

Categories

Resources