yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] efan3719:
Here's the repo manifest - https://github.com/ezio84/pnmod-n_manifest

as far as building for shamu... i think it's supported on PN so you should be able to build it if you add the device specific things to your local manifest - https://github.com/PureNexusProject?utf8=✓&query=moto
[Android Builders Collective] harpin14789:
Thanks, I will try that.

Also, what kind of features are in ABC rom? Is it just like pure nexus mod we had before?
[Android Builders Collective] Phrodini:
Awhile back someone posted and is or was working on shamu ABC ROM but I'm not sure if he's still working on it or released any versions because I haven't seen any updates from him. Would be nice to have a whale joint.
[Android Builders Collective] harpin14789:
Whale point?

Well, I started the repo sync. Its my first rom, so lets see how far I get for shamu.

---------- Post added at 11:54 AM ---------- Previous post was at 11:46 AM ----------

Is it better to use a local manifest or a git clone?
[Android Builders Collective] efan3719:
i've only ever done it with a local manifest, but i'm super sloppy and lazy with my builds so it may not be good to take advice from me lol
[Android Builders Collective] Phrodini:
Shamu=whale.. Good luck on the build ..theres plenty of knowledgeable people in here that can assist,esp on rainy days. This video from android authority on how to build your first ROM looked intriguing and almost had me wanting to start the process but I don't even know the basics of coding
[Android Builders Collective] harpin14789:
As I am syncing, I am getting this line sometimes.

curl:(22) The requested URL returned error: 404 Not FoundB/s

I used the URL that was provided on ezio's github. Did I go wrong somewhere?
[Android Builders Collective] efan3719:
for your repo init? or syncing things from your local manifest?
[Android Builders Collective] harpin14789:
Umm.... I made a ABC/.repo/local_manifests directory

Then I made a local_manifests.xml using nano command.

Then I added the device, vendor and kernel lines.

Then I cd back to ABC directory.

Then the repo init, then repo sync.

The repo sync is going but it sometime gives the curl 22: error. I am now confused. If there is an error how does it keep going?
[Android Builders Collective] theesotericone:
If you think that your version is rude you wouldn't want to read my version. It's such an important message that I felt the need to not only quote you but to make it really big, bold and colorful. Maybe people will actually read it that way. Probably not but it's worth a shot.

There are a lot of us that have been here since the beginning. We've all learned to build together. We've nuked distros, suffered countless failures, laughed at the simple things we missed that made builds fail and banged our heads when something just didn't work right. The one constant in all that has been everyone's willingness to help answer questions related to building.

To all the new people here we will help you build. We won't add everything your asking for. We will get tired of hearing it. Luckily, [MENTION=2095315]ezio84[/MENTION] is a really good dude. I've talked to him and a few others about it. He won't say stop. I will. So please, stop asking for feature requests. Most of them will come in time.
[Android Builders Collective] efan3719:
ok that i think is ok. if it keeps going that is. i think you only need to worry if it stops and gives an error.
[Android Builders Collective] harpin14789:
Once I get everything synced, what command do I run to build the rom for shamu?

I checked the folders, the vendor, device and kernel have been downloaded. So, the local manifest did its job.
[Android Builders Collective] efan3719:
ok that part is outlined in the guide here - https://raw.githubusercontent.com/nathanchance/Android-Tools/master/Guides/Building_AOSP.txt under step 4.

it'd be

. build/envsetup.sh

lunch

pick your device, type nexus_shamu-userdebug

mka bacon if it's your first time building since there is nothing to clean.

then you sit back and wait. if something is missing or an error happens it'll stop part way through. sometimes it's a few minutes sometimes it's a hour into the build. but if anything happens post here and someone might be able to help. i'm really no good at fixing errors in builds usually lol.

but hopefully the build completes and you can give it a try. :good:
[Android Builders Collective] Ed St John:
If you can find the commits, I'll release a build for it if you want ;)
[Android Builders Collective] theesotericone:
It's normal. The server doesn't support clone bundling.

http://stackoverflow.com/questions/23300245/what-to-do-about-curl-clone-bundle-error-on-aosp-repo-sync
[Android Builders Collective] pkelly517:
I'd also make sure that you look into ccache before the build.

It cut my (make clobber) builds for bullhead from 3+hours to about 70 minutes.
[Android Builders Collective] harpin14789:
I tried building once. I tried building screwd ROM. I used Nathans guide to setup ccache (50gb) before I but screwd rom. It build fine without errors, took 130 min, flashed the zip and got stuck at google logo.

Do I need to do ccache again for ABC ROM?
[Android Builders Collective] DroidIt!:
:) If you pay for shipping I'll sell you mine for REALLY cheap if interested at all. I have two 7's and a 9 collecting dust in my house.;)
[Android Builders Collective] theesotericone:
Did you add this to your .bashrc?

export use_ccache=1

If so it will use ccache. I'd wipe the ccache first though.

ccache -C (Clears ccache)
ccache -z (clears the stats)
ccache -s (shows the ccache to make sure it's wiped
[Android Builders Collective] harpin14789:
Sorry. But totally a noob here. How do I know if I added that to .bashrc?

Thanks :good:
[Android Builders Collective] kantjer:
Yes, clear you're ccache when changing ROM build
[Android Builders Collective] efan3719:
hmm... maybe. my Flo battery is starting to suffer. maybe if can get something going on it as far as N is concerned.
[Android Builders Collective] harpin14789:
Where is .bashrc located?
[Android Builders Collective] efan3719:
in your home directory. it's a hidden file. you'll have to show hidden files to see it.
[Android Builders Collective] DroidIt!:
If interested at any point you could PM me if you want. Both are in top shape, but I could run both through their paces and see which is better. Really they're probably both about equally as fine. Just haven't done anything with either in awhile.;)
[Android Builders Collective] harpin14789:
Can I also look in on this offer?
[Android Builders Collective] Weetbix:
I've always been curious about building a rom, you've just talked me into it .... even if it is a device that has maintainers (angler). This outta be interesting....
[Android Builders Collective] harpin14789:
So I started building. I got these errors, I think. But after 15 seconds or so. It started going crazy with lines of code just running through terminal.

So its fine as long as doesn't stop right? [MENTION=2757264]efan3719[/MENTION]
[Android Builders Collective] a g bell:
Looks good to go worry about any red text hopefully you won't see any?

some may find my build simply unacceptable

please choose

wisely?
[Android Builders Collective] efan3719:
right. those are normal and will start to fly by. main thing you need to worry about is if the build fails completely and stops. :good:
[Android Builders Collective] harpin14789:
OK, cool.

What about this green stuff and the xx warnings generated? [MENTION=3846540]a g bell[/MENTION]

I also added the export ccache line to .bashrc

Is there anyway to know the progress of the build?
[Android Builders Collective] a g bell:
Looks good like [MENTION=2757264]efan3719[/MENTION] says if doesn't stop all is good?

some may find my build simply unacceptable

please choose

wisely?

No progress percentage removed forget why ??
[Android Builders Collective] harpin14789:
:fingers-crossed: that it won't stop and that I will boot when flashed.
[Android Builders Collective] DroidIt!:
PM'd ;)

---------- Post added at 03:21 PM ---------- Previous post was at 03:18 PM ----------

For any interested in xposed, new release today ;)
[Android Builders Collective] harpin14789:
Noooo. :( It stopped. Got red letters.
[Android Builders Collective] harpin14789:
Awesome. rovo said he will target nougat next!!! Thing to look forward to.

---------- Post added at 03:50 PM ---------- Previous post was at 03:25 PM ----------

How do I take this kernel and put in my local_manifest.xml?

https://github.com/nathanchance/shamu
[Android Builders Collective] Phrodini:
That's good news right there..maybe that's why the sun is out today
[Android Builders Collective] ezio84:
About the asking features thing: i'm fine with it, but like everyone i make the rom the way i like so don't expect i add everything :P

I tried them and switched back to 1 because it's the only value giving a real butter smooth effect for me ;)

Topse is building ABC for shamu.

The "dummy" file is a normal warning (from the "support" framework), not a thing to worry about.

If it doesn't stop, it's in progress :D

Jokes aside, "ninja" shows the progress but i've disabled it by default because it can give headaches when building on some environments, and there are no real benefits.
[Android Builders Collective] harpin14789:
Thanks for the info. :)

I will try and get a build out for shamu before Topse...hehe. Didn't see a build for shamu anywhere on thread, so I wanted to start building myself.

Thanks for making this such a friendly atmosphere for beginner builders.

That said, how do I add commits to the a build? All I know how to do right now is to sync repo, get the device, vendor, and kernel stuff for shamu and build.
[Android Builders Collective] ezio84:
6th post of this thread, under "Quick tutorials"

Then it's also good to have a good pleasant music in the background when building :D

An example:

[YOUTUBE]F1ctv7Thtw4[/YOUTUBE]

:D
[Android Builders Collective] johnb380:
Ya [MENTION=5587083]Topse[/MENTION] said his build environment got messed up so he has to fix some stuff then he'll build again. I haven't heard anything since he told me that and I'm not really wanting to bug him so I hope [MENTION=4957514]harpin14789[/MENTION] gets a solid build out soon!

I've been wanting to try out ABC rom but my Linux pc is just not new enough to even attempt to try a build. Tbh it would prolly overheat half way through!

Good luck Shamu builders may the force be with you!
[Android Builders Collective] harpin14789:
Well, I have been getting errors as saw in my last few posts. If I can get those fixed. It shouldn't be too long for a build.
[Android Builders Collective] johnb380:
Ya I'd hit up some people that know more maybe try the build Pure Nexus thread they may be able to help out more. Nathan [MENTION=5196311]flash[/MENTION] really knows his stuff.

http://xdaforums.com/showthread.php?p=69040994
[Android Builders Collective] harpin14789:
Will do.
[Android Builders Collective] buffal0b1ll:
Solved my own problem. Duh, why didn't I think of the battery percentage enabler apps on the playstore first? Finally it came to me like neon Dirk Diggler lights;) Clean flash officially averted....mwuhahaha
[Android Builders Collective] harpin14789:
When I am building the rom. I am getting a jack server permission denied error. How do I fix this?
[Android Builders Collective] efan3719:
might need to do killjack. also in the guide from Flash -

"#########################################

########### Jack issues ###########

#########################################

For those of you who are having jack issues (like saying you ran out of memory), follow these steps.

Type this into your terminal, substituting the # with how many GBs of RAM you have:

$ export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx#g"

Then go into the root of the source folder and type the following:

$ ./prebuilts/sdk/tools/jack-admin kill-server

$ ./prebuilts/sdk/tools/jack-admin start-server

This will restart the jack server to reflect your new heap limit."
[Android Builders Collective] ezio84:
The BoardConfig in your kernel source could have a wrong toolchain path:

https://github.com/ezio84/pnmod-n_device_huawei_angler/blob/n/BoardConfig.mk#L35

Kill jack before building like suggested by efan3719, it doesn't play nice in some environments.
[Android Builders Collective] VictorLapin:
It says no toolchain for the kernel. You sure you synced correctly?
[Android Builders Collective] donz_Simon:
What you mean brother?
[Android Builders Collective] parmafran:
Bloody hell. Just flashed Kantjers latest, and there is smart bar and pulse...
[Android Builders Collective] kantjer:
:D thank [MENTION=2095315]ezio84[/MENTION] for that :good::good:
[Android Builders Collective] rrrrrrredbelly:
Hey, thanks for taking the time to build this rom. I'm still on Nathan's last MM build, didn't want to come here and ask for N but was hoping it would happen.

Thanks

Dan
[Android Builders Collective] VictorLapin:
This is just a cosmetic bug. As for google logo - well, congratulations on your first bootloop :) Usually it means that something is not right with the build.
[Android Builders Collective] harpin14789:
How do I go about seeing what is causing the bootloop. Because all I did was repo sync ABC rom, then grab the vender, device and kernel files for shamu from purenexus using local_manifest. then I built it.
[Android Builders Collective] ezio84:
Ensure to have the correct vendor blobs. I suggest you to pick them from PureNexus.
[Android Builders Collective] harpin14789:
I used local_manifests.xml to grab the vendor and other stuf from purenexus. I don't know how to grab it manually.

this is what I have

<?xml version="1.0" encoding="UTF-8"?>
<manifest>

<remote name="pure"
fetch="https://github.com/PureNexusProject/" />

<project path="device/moto/shamu" name="android_device_moto_shamu" groups="device,shamu,broadcom_pdk" remote="pure" revision="n" />
<project path="kernel/moto/shamu" name="android_kernel_moto_shamu" groups="device,shamu,broadcom_pdk" remote="pure" revision="n" />
<project path="vendor/moto" name="proprietary_vendor_moto" remote="pure" revision="n" />

</manifest>

I did this before I repo synced and it synced the required files when I ran the repo sync.

Is that the correct code?

What are blobs?
[Android Builders Collective] Ed St John:
Tbh I do it a different way that works - involves making a roomservice.xml in local_manifests folder, adding device, kernel and vendor sources, after that add .mk file for your device, edit vendorsetup.sh and AndroidProducts.mk, and viola :)

Let me know if you want me to post this method in full
[Android Builders Collective] harpin14789:
Please post this method in full. I want to learn.
[Android Builders Collective] kantjer:
The vendor blobs are located in proprietary_vendor_moto

They are usually updated with the monthly security patch
[Android Builders Collective] Topse:
You have a working build of shamu? Of course it would be very interesting to know how you did that. :angel:
[Android Builders Collective] Ed St John:
I'm building for hh but I have all nexus phone files downloaded so it could also do that I think haha

[MENTION=4957514]harpin14789[/MENTION]

1. Go to ROM/.repo/ and make a folder called local_manifests

In this folder, make a new document. Name it roomservice.xml

Open roomservice.xml and copy this code:

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<!-- Nexus 5 -->

<project name="CyanogenMod/android_device_lge_hammerhead" path="device/lge/hammerhead" remote="github" revision="staging/cm-14.0" />

<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-14.0" />

<project name="CyanogenMod/android_kernel_lge_hammerhead" path="kernel/lge/hammerhead" remote="github" revision="staging/cm-14.0" />

<!-- /Nexus 5 -->

<!-- General -->

<project name="CyanogenMod/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="cm-14.0" />

<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.0" />

<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.0" />

<!-- /General -->

</manifest>

You will need to edit this for your device - locate the device and kernel repos in the CyanogenMod github, and locate the vendor repo from TheMuppets github. Look at the titles for these, and you should see how to edit my code to suit your device. If you get stuck or want to check it's right, post what you have and I'll help ;)

Press save.

Now we need to add / edit some files. For hammerhead or any nexus device, we go to the PureNexus github and find their repo called android_vendor_nexus. In this, open in separate tabs vendorsetup.sh, /products/AndroidProducts.mk and /products/nexus_hammerhead.mk (will be different for you - if you're on a nexus, follow the same thing but instead of nexus_hammerhead.mk use your device.

By copying and pasting, replace your current vendorsetup.sh file found in /ROM/vendor/nexus/products, and add your nexus_[name].mk file also to this folder. Replace the vendorsetup.sh file in ROM/vendor/nexus.

In terminal, type repo sync --force-sync

Then . build/envsetup.sh

Then breakfast

Then type in what device yours is from the list

Then type mka bacon

Ta daa.

I think that's everything I did :confused: if I think if anything else I'll edit this post ;)

Thanks to [MENTION=2095315]ezio84[/MENTION] for helping with the adding file part of this :)
[Android Builders Collective] harpin14789:
ABCrom for Shamu

I got a working build of ABC for Shamu. Only thing is that you need to flash a kernel after flashing system zip and gapps. For some reason, the kernel was messed up and ended up causing the bootloop. When I flashed nathan's kernel or any nougat kernel for that matter, rom booted. I don't know to how to make it use nathan kernel when it is building the rom.

[MENTION=2850780]rrrrrrredbelly[/MENTION] [MENTION=3556013]johnb380[/MENTION] Here is the ABCrom for shamu v1. Everything works, but

MAKE sure to flash a kernel after after flashing gapps. I suggest Flash kernel by nathan, but any nougat kernel for shamu will do.

. I prefer banks gapps but opengapps also work. I will try and fix the kernel in the next build so you don't have to flash a kernel to get it to boot.

Link to flash kernel: https://goo.gl/4d5DGK Link to rom: https://www.androidfilehost.com/?fid=457095661767102373

Sorry about that, first rom build. :)

Flash and tell me if you have any problems.
[Android Builders Collective] johnb380:
Awesome bro! I'll try it real soon. Did you happen to see if smart bar and pulse is working yet. Thanks alot for sharing your build I really appreciate it a lot!

Also I LOVE [MENTION=5196311]flash[/MENTION] kernel anyways I've been running it for awhile now and prolly would of flashed it regardless. Nathan is a beast on anything he builds!

I need to get a new pc so I can get building myself!
[Android Builders Collective] harpin14789:
This build is a repo sync from 2 days ago. As of now. There is no DUI as far I see, but I only flashed ROM to see if everything was working right, don't have time right now to do a clean flash. So I restored back to my purenxus setup. Will probably move to ABC tonight.

As far as I know. I don't think ezio is including DUI in base ROM and this is base ROM with what ezio added. I think I probably need to add a commit to get DUI in there. As I am still learning it might take some time.
[Android Builders Collective] johnb380:
Ok. Ya you can learn to play around with toolchains too. I wish I had a pc that's good enough to do all this Id prolly never sleep!

Good luck in your learning process and have fun! Don't forget SHARING MEANS CARING! Thanks again.
[Android Builders Collective] Topse:
I have also a build for Shamu with prebuilt kernel Image (since 1-2 weeks ago). I just wanna know how it works.. And what i did wrong.

Personally i dont need a Shamu build, its my Wife's Phone.
[Android Builders Collective] kantjer:
[MENTION=2095315]ezio84[/MENTION] pushed all DUI commits a few hours ago to the ABC git.

Sync and build will give you DUI, as far as I have tested it everything seems to be working perfect.
[Android Builders Collective] Spaulding89:
Yes everything is fine with DUI on your build from Today

Just enjoying Pulse by listening to Rise Against
[Android Builders Collective] vsot13:
But, but....We need it. Lol
[Android Builders Collective] rrrrrrredbelly:
Sweet, thank you. I should be able to flash it tonight.

Dan
[Android Builders Collective] Weetbix:
Yep, I can confirm this as well. Pulse was the thing I missed most from MM on DU - many thanks to [MENTION=2095315]ezio84[/MENTION] and [MENTION=3306843]kantjer[/MENTION] ! It doesn't seem to work for me using NeutronMP (nothing in logcat that I can see), but all is fine with BlackPlayer.

Well worth flashing over my own very first own build yesterday. Didn't want to do another until I had figured out how to drag in another kernel and pre-root it (although to be honest I hadn't done much searching for how to do those yet).
[Android Builders Collective] harpin14789:
Cool, will sync and rebuild again and hopefully I can get the Nathan's kernel incorporated.

---------- Post added at 10:03 PM ---------- Previous post was at 10:02 PM ----------

You could flash the shamu build I posted as you wait for [MENTION=5587083]Topse[/MENTION]. :D

---------- Post added at 04:14 PM ---------- Previous post was at 04:03 PM ----------

How do I know if I ubuntu is using ccache when building the rom? [MENTION=2095315]ezio84[/MENTION] is there anyway to turn on advanced reboot with reboot recovery, etc. Don't see it in dev settings or in Advanced settings.

Also what is difference between the lunch command for building and the breakfast command for build. Saw both on the thread.

---------- Post added at 04:16 PM ---------- Previous post was at 04:14 PM ----------

What went wrong?
[Android Builders Collective] ezio84:
DUI Pulse could work also with non compatible players if you install Arise mod.

Be sure to have this:

https://github.com/ezio84/pnmod-n_vendor_nexus/commit/5219e22203e54439e630fc7c312b17b1d97e2910

About build commands: https://wiki.cyanogenmod.org/w/Envsetup_help#lunch
[Android Builders Collective] harpin14789:
A full beginner here. I don't know how to add commits yet. How do I add that in? Do I add it in manually?
[Android Builders Collective] johnb380:
You could ask [MENTION=5196311]flash[/MENTION] about adding his kernel to a rom I'm sure he knows how. He may have his source setup so it only compiles by itself idk. But asking him is prolly your best bet!

Edit:

I found this article about cherry picking from gerrit it

https://www.google.com/amp/www.xda-...ick-useful-features-directly-from-gerrit/amp/

Hope that helps...
[Android Builders Collective] ezio84:
http://xdaforums.com/showpost.php?p=55178446&postcount=77

Or manually.

But if you are already using my vendor/nexus tree, it should be already in.

If it's in but you don't get yet the advanced reboot menu, ensure you are using the correct build commands:

https://github.com/ezio84/scripts/blob/n/build_rom.sh

. build/envsetup.sh
breakfast nexus_shamu-userdebug
make installclean
mka bacon

and you flash the rom final zip file, not the ota package.
[Android Builders Collective] harpin14789:
Well, I am syncing your repo and get my vender from purenexus.

When I build, will it use both vendor/nexus tree and vender/moto/shamu?

I think something happened to my repo when I resynced. There is no vender/nexus anymore.

How do I nuke my repo and resync everything again? Do I just delete my "working directory" folder?
[Android Builders Collective] vsot13:
You could flash the shamu build I posted as you wait for [MENTION=5587083]Topse[/MENTION]. :D

/QUOTE]

I saw it ( Big thanks for this), but I'll wait for guys to fix Multi Rom.
[Android Builders Collective] harpin14789:
Whats wrong with multirom?
[Android Builders Collective] vsot13:
N doesn't boot as secondary
[Android Builders Collective] harpin14789:
With MM as primary N doesn't boot as secondary.

But with N as primary, N boots as secondary. :laugh: