yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] MoistPicklez:
[MENTION=2095315]ezio84[/MENTION] Thanks for the reply, but how would I go about adding the device tree and blobs from another N ROM and append them to TipsyOS's source?

Edit: After some Googlin' I think I need to create myself a local manifest, but I can't find out where to place it or exactly how to build it as the guides I found were a bit outdated.. Will continue to peck away at it though, thanks for the help.

Edit 2: Found a local manifest for HH, again I'm guessing outdated, but I'm assuming I'm on the right path now.

<?xml version="1.0" encoding="UTF-8"?> <manifest> <project name="CyanogenMod/android_device_lge_hammerhead" path="device/lge/hammerhead" remote="github" /> <project name="CyanogenMod/android_kernel_lge_hammerhead" path="kernel/lge/hammerhead" remote="github" /> <project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" /> </manifest>
[Android Builders Collective] yung40oz84:
Can we get clear all fab [MENTION=2095315]ezio84[/MENTION] :fingers-crossed:
[Android Builders Collective] DroidIt!:
Hey ezio, thanks for the help. :) Just to be clear, run the RR build script or the Sammy one, I'm guessing RR. First time building and I'm not TOO sure how to revert a screw-up made by a build script. :angel:
[Android Builders Collective] ezio84:
Here's a nice tutorial about how to manage manifests: https://xdaforums.com/showthread.php?t=2329228

I don't know yet what I'll do with recents panel :P

If you use those Samsung folders from the zip, better to use their build script.

If something is wrong, you can just delete the OUT folder ;D
[Android Builders Collective] yung40oz84:
Lol, keep clear all fab In mind, I like bottom corner, lmao
[Android Builders Collective] DroidIt!:
Okies. :) Thought of a recovery experiment I want to do first in case my build is borked so I don't brick a new $600 tablet :eek::D
[Android Builders Collective] HamsterHam:
[MENTION=2095315]ezio84[/MENTION] can you link me the commits for running service icon in header please? Trying to help Dabug123 with implementing it. He has the icon but clicking it doesn't work. Thanks.
[Android Builders Collective] ezio84:
Everything is always in the list :D

https://github.com/ezio84/scripts/b...tips/Commits-list-with-links- OLD n2.txt#L562

PS: not for that feature but in general check also the new O list, because i rewrote/tried to improve a lot of stuff: https://github.com/ezio84/scripts/blob/o/My_mods-commits_and_tips/Commits-list-with-links.txt
[Android Builders Collective] DroidIt!:
Still playing on my end btw for any interested. Think I was making it more complicated than I needed to, just had to think about it a bit. :angel: Incorporating platform today into my base. Looks like there's quite the readme on the kernel side which I haven't looked at yet, but getting towards a RR base on the Tab S3. Reason I picked RR and not ABC initially is on the Tab S2, there was a working RR build so figured I'd start there. After I figure out what I'm doing, then I'll try my hand at an ABC build me thinks. :)
[Android Builders Collective] HamsterHam:
Awesome, nice one!
[Android Builders Collective] rohit25:
I might be killed for asking but any ETA's for ABC Oreo... I have been flashing ROMs since the past 2 weeks and none is to my liking .... Keep flashing and keep itching for something good
[Android Builders Collective] Natakranta:
I'm not in position to give any ETAs but Ezio is merging September security patches Google released yesterday, so I guess it's

Soon :)
[Android Builders Collective] theesotericone:
You won't be killed but we have a long standing tradition in this thread. Anytime someone, this time you, asks for an ETA the release is delayed for a week. The second time someone asks for an ETA the release is delayed for a month. The third time someone asks for an ETA I end up getting another infraction.:cool:
[Android Builders Collective] Fastrite:
https://youtu.be/ab1se0dkeCU

#whiteuimustdie
[Android Builders Collective] ezio84:
Wise choice ;D

When it's really ready :P

There are already some roms around though that picked a loft of stuff from abc source :P
[Android Builders Collective] spjetrovic:
The first thing I learned was my ABC
[Android Builders Collective] chykal:
1st Build Attempt

I am trying my hand at building PureNexus for Angler thanks to this thread and the people who are so willing to help others get into building ROM's.

My PC is a Dell Studio 1745 with plenty of disk space but just 4GB of RAM. The OS is Ubuntu 17.04 and it reports 3.8GB of RAM.

I followed the guide here and have already helped myself to a few fixes here and other sources found by searching the errors on Google. After setting up my environment I am following the final build commands found here.

These are the commands I use to start my build:

make clobber

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

export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx3g"

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

. build/envsetup.sh

repo init -u https://github.com/PureNexusProject/manifest.git -b o

repo sync

bash build.sh angler sync log jack 3

The error I am having difficulty with now is:

[ 46% 36084/77563] target thumb C++: camera.msm8994_32 <= device/huawei/angler/camera/QCamera2/HAL3/QCamera3HWI.cpp

ninja: build stopped: subcommand failed.

build/core/main.mk:21: recipe for target 'run_soong_ui' failed

#### make failed to build some targets (04:26:40 (hh:mm:ss)) ####

I have Googled this quite a bit but have not found anything that helped. I have also ordered am 8GB RAM kit from Amazon which will be here on Saturday.

Thanks for any help offered.

Bob
[Android Builders Collective] buffal0b1ll:
Try this commit. I had similar error on my bullhead using PN trees this morning and it did the trick.

https://github.com/ezio84/abc_device_huawei_angler/commit/73b1f25321d6e9d4061591e084d86ccceb72d57d
[Android Builders Collective] chykal:
I started reading about cherry-picking and it gave me a headache. I need some advice on how to try a commit. Or maybe some sleep and pick it up again in the morning. LOL
[Android Builders Collective] ezio84:
http://xdaforums.com/showpost.php?p=55178446&postcount=77

---------- Post added at 10:30 AM ---------- Previous post was at 10:18 AM ----------

Fyi, updated O version is up.
[Android Builders Collective] Ntress:
where's that ??
[Android Builders Collective] aoaleman:
Probably gotta build it! Hehe
[Android Builders Collective] icrunchbanger:
[MENTION=2095315]ezio84[/MENTION] like i7 , overclocked :)
[Android Builders Collective] yung40oz84:
This is like the first time I am getting errors since building ABC for O, but I am not really sure what to do, lol. Error at end of hastebin there.

https://haste.blamealexcruz.com/DJVr0ZPLfj.pl
[Android Builders Collective] Garrykd:
Force sync and then try building again.

repo sync --force-sync
[Android Builders Collective] yung40oz84:
Ok will do, thanks.
[Android Builders Collective] icrunchbanger:
Guys sorry for super noob question.

I've synced O repo from ezio. When i try to build i get this message

" breakfast bullhead

including vendor/nexus/vendorsetup.sh

ls: cannot access vendor/nexus/products/bullhead.mk: No such file or directory

build/core/product_config.mk:249: *** Can not locate config makefile for product "bullhead". Stop.

ls: cannot access vendor/nexus/products/bullhead.mk: No such file or directory

build/core/product_config.mk:249: *** Can not locate config makefile for product "bullhead". Stop. "

Iv extracted proprietary blobs to root folder.
[Android Builders Collective] pkelly517:
Ezio doesn't build for the bullhead anymore. Hence, no file to get it done.

Look around. There are a couple builders here that can probably help with required files (build.mk, vendor and kernel trees, etc).
[Android Builders Collective] icrunchbanger:
[MENTION=7157050]mohican16[/MENTION] a little help please :)
[Android Builders Collective] Topse:
You need a bullhead.mk in your product foulder. :)

# Copyright (C) 2016 The Pure Nexus Project

#

# Licensed under the Apache License, Version 2.0 (the "License");

# you may not use this file except in compliance with the License.

# You may obtain a copy of the License at

#

# http://www.apache.org/licenses/LICENSE-2.0

#

# Unless required by applicable law or agreed to in writing, software

# distributed under the License is distributed on an "AS IS" BASIS,

# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

# See the License for the specific language governing permissions and

# limitations under the License.

# Include pure telephony configuration

include vendor/nexus/configs/abc_phone.mk

# Inherit AOSP device configuration for bullhead

$(call inherit-product, device/lge/bullhead/aosp_bullhead.mk)

# Override AOSP build properties

PRODUCT_NAME := bullhead

PRODUCT_BRAND := google

PRODUCT_DEVICE := bullhead

PRODUCT_MODEL := Nexus 5X

PRODUCT_MANUFACTURER := LGE

# Device Fingerprint

PRODUCT_BUILD_PROP_OVERRIDES += \

PRODUCT_NAME=bullhead \

BUILD_FINGERPRINT=google/bullhead/bullhead:8.0.0/OPR4.170623.006/4286358:user/release-keys \

PRIVATE_BUILD_DESC="bullhead-user 8.0.0 OPR4.170623.006 4286358 release-keys"
[Android Builders Collective] icrunchbanger:
Much appreciated bro :)
[Android Builders Collective] yung40oz84:
Is anyone failing safety net now? Only the CTS profile is failing all the sudden, don't know if it's latest O build or safety net, lol. I know someone in Nitrogen thread said they failed in their latest build. Can some others check please? Thank you.
[Android Builders Collective] ezio84:
Yes CTS fails atm, Magisk will have another fight :D
[Android Builders Collective] buffal0b1ll:
Still passing here.
[Android Builders Collective] chykal:
I tried to cherry pick using your guide but I was not successful. I moved on to building ABC ROM but got the same error message.

Tonight I completely set up my build environment again and kicked off an ABC Nougat build. Hopefully I'll have a completed ROM in the morning.

I also installed the 8GB upgrade kit. Strange that it is only using 40% of it. Building Oreo with just 4GB It was maxed out almost all the time.
[Android Builders Collective] mohican16:
Sorry for delay, u can use my vendor/nexus tree for bullhead
[Android Builders Collective] pkelly517:
Did you remove the line in your setup to limit Jack to 3GBs?
[Android Builders Collective] chykal:
I was doing it from the command line using:

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

export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx3g"

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

For this build I changed it to -Xmx7g. It is probably set elsewhere but I can't find it. It is not set in the config.properties or the .jack-settings files. Can I set it in either of those files to override wherever it is getting set from?

And BTW my ABC Nougat build is at 28% right now.
[Android Builders Collective] JaylanPHNX:
Apparently even the stock OTA is breaking safety net for some users.

http://www.androidpolice.com/2017/0...e-safetynet-android-pay-nexus-6ps-theres-fix/
[Android Builders Collective] yung40oz84:
I think this is the issue, gotta move to .019, http://www.androidpolice.com/2017/0...e-safetynet-android-pay-nexus-6ps-theres-fix/
[Android Builders Collective] chykal:
The build that I mentioned in my earlier post completed successfully. I am writing this post on my phone running my first home built ROM. Thanks for all the help and to everyone who contributed to this very slick Nougat ROM.

Now I am trying the my luck at the Oreo version. The last one took 5:34 to build. This one should be done in the morning. I'll keep you posted.
[Android Builders Collective] chykal:
This morning, 13 hours later my ABC Oreo build is only 52% complete. I don't know why it is taking double the time of the Nougat ABC ROM build but at least it is still going.
[Android Builders Collective] nathanchance:
Google changed the build system somewhat significantly in Oreo (moving to Soong and Blueprint). Almost everyone's build times have increased.
[Android Builders Collective] chykal:
Thanks!

After almost 12 hours the build failed. Here is the build.log after the first Failed message.

https://pastebin.com/sizygURK
[Android Builders Collective] yung40oz84:
Hmm, I have not really had any failed builds, only one and I built like 20 times, lol

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

hey [MENTION=636871]ezio[/MENTION] anything to look for with the test beans gapps package? I wanna try it out

---------- Post added at 03:16 PM ---------- Previous post was at 03:16 PM ----------

hey [MENTION=2095315]ezio84[/MENTION] anything to look for with the test beans gapps package? I wanna try it out
[Android Builders Collective] chykal:
I did one build of ABC Nougat to test my system and build environment. It was successful. Is there anything I need to do different for the build environment for Oreo?
[Android Builders Collective] kantjer:
Uninstall any Google Play Service update, wipe system and flash ROM and GApps.

---------- Post added at 08:52 PM ---------- Previous post was at 08:50 PM ----------

Shouldn't be needed but building Oreo is much more resource hungry so it could be your build is failing due to that.

My initial build time doubled from 1 to 2 hour.

Builds with filled ccache are about the same as it was on Nougat.
[Android Builders Collective] Garrykd:
I have an old system with only 4gig of ram. On an initial build it will take over 12 hours and will fail. However, building again (and all subsequent builds) will be successful and take considerably less time. Try building again. ;)
[Android Builders Collective] yung40oz84:
OK, I am building some stuff, so I will test and report. Thanks.
[Android Builders Collective] chykal:
After I upgraded to 8GB of RAM I forgot to increase my /swapfile. I now have an 8GB /swapfile. I have also set ccache to 50GB.

Question for either of you:

How much swap compared to RAM and how much ccache do you have set?

Thanks for the support guy's!

Is it necessary to do a make clean or clobber with subsequent builds after a failed build?
[Android Builders Collective] Garrykd:
It's not necessary(and to be avoided at all costs:silly:). You could make installclean if you wanted but also unnecessary after a failed build (after fixing any errors , of course) .

The general rule of thumb is swap=ram.... I have a 12gig swap though because I only have 4gig of ram.

You should be fine with 8gig and a 50gig ccache (you could probably make it 30gig...I've never gone over that)
[Android Builders Collective] storm119:
Hey guys...

I successful built the ABCroms Oreo for angler ( [MENTION=2095315]ezio84[/MENTION] repo) ....flashing (Vendor/ROMS/gapps) went fine but it's stuck on the home screen with "Android is starting.....". Anyone have any idea how to get rid of this..."Android is starting"...? :D

TIA

P.s - syncing 3-4 hrs ago (working tree are up to date with OPR6.170623.019)
[Android Builders Collective] indian84:
Probably no launcher installed?

You can try to sideload apk for any launcher?
[Android Builders Collective] storm119:
Okay lemme try and thx for the tips ;)

P.s....Damn [MENTION=4570506]indian84[/MENTION] i luv you man....

p.s.s....I don't sideload instead swipe down the qs > Settings (gear icon) > Apps & notifications > Apps info > Look for Play store > scroll down > tap the App details > it's will bring up the Store apps > and Install the Nova launcher....golden!!!!
[Android Builders Collective] ezio84:
They are good to go, follow Kantjer's suggestions.

That happened because you used bad gapps that remove the prebuilt pixel launcher from the rom.

Use my test ones: EDIT: updated ones incoming in a while to fix some clean flash FC.
[Android Builders Collective] storm119:
Ahhh...thx boss I'll never know that btw I will kept this gapps securely on my device :good:
[Android Builders Collective] kantjer:
Hi all,

Google released the fix for the CTS not passing bug yesterday, and thanks to Ezio we now also have a stable GApss package. I think all showstoppers are now fixed.

[MENTION=2095315]ezio84[/MENTION] has been working hard to implemented what we think are the most important features in ABC ROM :good:

The ROM proved to be very stable for all testers.

I will check with Ezio but I think we will be releasing a first ABC Oreo build for Angler soon.
[Android Builders Collective] indian84:
Glad I could help.

Just my way of contributing to the amazing thread.

I don't do any builds, so i try and be nice to people here.

;)
[Android Builders Collective] ezio84:
https://www.androidfilehost.com/?fid=961840155545597612

Updated arm64 gapps package with some clean flash fixes and some fresh apk from Pixel like the new SetupWizard.
[Android Builders Collective] morfances:
Any build ABC for Op5?
[Android Builders Collective] Kaleshwar:
Your what?
[Android Builders Collective] Natakranta:
To heat up the waiting for ABC O release, I'll let you guys know that it is possible to dirty flash from ABC N to ABC O :D

It's totally not recommended. And don't you dare to report any bugs if you do so, but...

But I did ABC N nandroid and dirty flashed ABC O over it only wiping system, cache and dalvik in TWRP advanced wipe menu. I had few liitle hickups here and there with apps Force Closing, but managed to make it straight with clearing app cache and or data or reinstalling FCing app.

All I'm saying is that if you're in adventurous mood, it costs you nothing to do nandroid and dirty flash. If things go south, nuke it all and clean flash.

As a precaution i not only did a nandroid but as well backed up all user data (pictures, videos, movies, music, downloads, and so on) to PC, just in case things go very wrong and I need to fastboot flash full factory image from Google. Fortunately I didn't have to , and to spice it up, ABC O was fine even with N bootloader and radio, which I fastboot flashed later on.

Of course nice girls from good schools should run fastboot flash all script to flash O full factory image, then flash latest TWRP and than in TWRP wipe system, data, cache and dalvik and flash ABC O, Ezios moded O gapps and Magisk or SuperSu (both roots working, up to your choice).

tik-tak, tik-tak, tik-tak

:D
[Android Builders Collective] icrunchbanger:
[MENTION=2095315]ezio84[/MENTION] [MENTION=3306843]kantjer[/MENTION]

Someone released ABC?
[Android Builders Collective] ezio84:
The Slim merged code hasn't the battery icon/percentage feature you are using instead, so the Doze commit doesn't expect those "status bar battery" lines.

When GIT finds them in your code, it asks you: hey, i found those lines but they are not in the commit you are cherry-picking, what should i do?

You still need the battery icon/percentage feature, so keep the lines between <<<<<<< HEAD and =======. In less words, just delete:

<<<<<<< HEAD
=======
>>>>>>> b02ab35... [2/2] Settings: Doze (ambient display) timeout
[Android Builders Collective] Nucleonic:
Hey guys!!

I know I've asked this before but I continue to have trouble with making this happen. By default, my OTA package name is:

slim_shamu-ota-eng.larry.zip

I'm trying to get the compiler to spit out:

Slim-5.0.2-Alpha.91-Unoffical-20150108-0718.zip

I can change the filename manually after the fact but I'd like the compiler to do it to save me a step. It was pointed out that I should look here in vendor/config/common.mk:

# Versioning System

# SlimLP first version.

PRODUCT_VERSION_MAJOR = 5.0.2

PRODUCT_VERSION_MINOR = alpha

PRODUCT_VERSION_MAINTENANCE = 0.91

ifdef SLIM_BUILD_EXTRA

SLIM_POSTFIX := -$(SLIM_BUILD_EXTRA)

endif

ifndef SLIM_BUILD_TYPE

SLIM_BUILD_TYPE := UNOFFICIAL

PLATFORM_VERSION_CODENAME := UNOFFICIAL

SLIM_POSTFIX := -$(shell date +"%Y%m%d-%H%M")

endif

# SlimIRC

# export INCLUDE_SLIMIRC=1 for unofficial builds

ifneq ($(filter WEEKLY OFFICIAL,$(SLIM_BUILD_TYPE)),)

INCLUDE_SLIMIRC = 1

endif

ifneq ($(INCLUDE_SLIMIRC),)

PRODUCT_PACKAGES += SlimIRC

endif

# Set all versions

SLIM_VERSION := Slim-$(PRODUCT_VERSION_MAJOR).$(PRODUCT_VERSION_MINOR).$(PRODUCT_VERSION_MAINTENANCE)-$(SLIM_BUILD_TYPE)$(SLIM_POSTFIX)

SLIM_MOD_VERSION := Slim-$(SLIM_BUILD)-$(PRODUCT_VERSION_MAJOR).$(PRODUCT_VERSION_MINOR).$(PRODUCT_VERSION_MAINTENANCE)-$(SLIM_BUILD_TYPE)$(SLIM_POSTFIX)

PRODUCT_PROPERTY_OVERRIDES += \

BUILD_DISPLAY_ID=$(BUILD_ID) \

slim.ota.version=$(PRODUCT_VERSION_MAJOR).$(PRODUCT_VERSION_MINOR).$(PRODUCT_VERSION_MAINTENANCE) \

ro.slim.version=$(SLIM_VERSION) \

ro.modversion=$(SLIM_MOD_VERSION) \

ro.slim.buildtype=$(SLIM_BUILD_TYPE)

EXTENDED_POST_PROCESS_PROPS := vendor/slim/tools/slim_process_props.py

I don't see the actual line where the final output file name is being set to "slim_shamu-ota-eng.larry.zip". That is the line/value I wish to change.

Sorry for the double question.
[Android Builders Collective] ralpheboyo:
Guys can you pls do us a favour.... When posting terminal output,errors, manifest, or file content from slim source can you pls use php and hide?

Thxs So much... Keep the questions coming so we all grow stronger.. :highfive:
[Android Builders Collective] theesotericone:
Finally someone said it. lol
[Android Builders Collective] mcgi5sr2:
Is anyone else struggling to get bluetooth working on their devices with SlimLP?
[Android Builders Collective] Nucleonic:
I think I edited the post to hide the terminal stuff. Was that what you were looking for? Sorry about that. Too many buttons.

---------- Post added at 10:50 AM ---------- Previous post was at 10:48 AM ----------

Now that I can hide, not too sure about php. Is this some type of editing done in the terminal before porting the output here? Or is there something here we use in addition to hide?

---------- Post added at 10:55 AM ---------- Previous post was at 10:50 AM ----------

I've been trying cherry pick two commits regarding battery icon. I selected the following:

https://gerrit.slimroms.net/#/c/21767/

https://gerrit.slimroms.net/#/c/21914/

No other commits. After building and the ROM settled down, I couldn't really get past the first screen after boot-up (where it asks to select language). I kept getting a UI force close message. Only way to avoid it was to restore to a nandroid backup.

Are there other commits I should be cherry picking as well to make these all work?
[Android Builders Collective] letmedanz:
Here is the Stock Slim Bootanimation for those using my builds & want the original one back -

https://www.androidfilehost.com/?fid=95887005526788646

Added to my OP post as well

Thanks
[Android Builders Collective] inffy:
I have the exact same problem. I will test without those two commits, or have you [MENTION=4453916]Nucleonic[/MENTION] already tested are those the reason why System UI just gives FC
[Android Builders Collective] Nucleonic:
I am going to make a couple of builds. With both commits, I get the UI force close. I'll also make a virgin build, and two builds with just the one commit (1/2 and 2/2).
[Android Builders Collective] letmedanz:
Hmmm.. i have location reporting turned on & i have no issue

I am on a slightly older GAPPS

Maps version 9.2.0 is what am using...

Could you flash an earlier version and see if the problem persists?
[Android Builders Collective] Nucleonic:
I installed a build with the two battery icon commits on my OPO. Works fine. Still going to build a virgin shamu and one with both commits to see if the problem is with the Shamu commits.
[Android Builders Collective] ralpheboyo:
[MENTION=4453916]Nucleonic[/MENTION] was not directed at you at all....other people have been doing....Don't stress.... (took me like a year to figure it out... Lol).... Thxs for amending your post....

1+1
[Android Builders Collective] Jax Teller:
Can this be used for flo or is it only for shamu?
[Android Builders Collective] shadowdevil:
yup tried different old versions but still force closes..!
[Android Builders Collective] letmedanz:
Ideally it should work

Would appreciate if you could try it & let us know...

Pls do a nandroid though before you try it :D

---------- Post added at 11:19 PM ---------- Previous post was at 11:18 PM ----------

FRAK

I'll check on it.. Thanks for trying it out