yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] DroidIt!:
Well, things are finally starting to get back to normal here...starting to :) Sooo, open invitation today. Anybody who builds for flo or shamu if there's anything you want tested I should be able to test today. I just updated the wife's N5 so that's out. Just thought I'd throw that out there...and hope all are having a good day :)
[Android Builders Collective] Nucleonic:
Shamu build without the commits is fine. Tried building with only one commit, but compile errorerd saying it couldnt find things. Recompiling the build with both commits. To be clear, I used the lp5-caf commits for my OPO with success. Using the Lp5 commits for Shamu.
[Android Builders Collective] inffy:
With shamu and not picking those two battery commits everything runs smoothly.

Definately a shamu issue with those two commits. I haven't tested which one is the one that causes the system UI fc
[Android Builders Collective] Jax Teller:
I'll test and tell you the results. lol

Edit: I haven't flashed yet but from the zip I see it's the 1080.zip boot animation. I believe 1200.zip is the right one for flo.

Edit2: I flashed it and it works perfect. Maybe if it was the 1200.zip it would look a little better but it's fine.[emoji3]
[Android Builders Collective] Nucleonic:
Looks like the issue was noted on gerrit for both commits! Feels good to actually helped the team out today!!
[Android Builders Collective] ezio84:
Everybody can do it :P

But it's not "official" by us.

I'm also force pushing something today to fix/improve latest stuff.
[Android Builders Collective] ralpheboyo:
there is a reason why no one has posted a build here yet.../o\ ....as soon as we get the green light you will see all the various editions of abc being posted....
[Android Builders Collective] DroidIt!:
Hey guyzzzz :) Hope all are good? Wheelp, working on my build a bit more today. I've been keeping up with the thread and wondering what I should allocate for system resources for myself for building. I have an i7 6700 hq, GTX 1070 if that makes a difference :), 32 Gb memory and a Sammy 960 pro SSD. Just a ballpark for my hardware would be good enough. :)
[Android Builders Collective] ezio84:
That's a monstre config, you'll be fine :D

16GB ram are the minimum nowadays to build Android without headaches.
[Android Builders Collective] DroidIt!:
Oh ok cool. I was wondering about /swap and ccache. Good for both with just what I got in hardware though eh?
[Android Builders Collective] ezio84:
About swap i'm a noob, master [MENTION=264345]ralpheboyo[/MENTION] can tell you more :D

About ccache, i always get good results setting it to 20 or 50GB.
[Android Builders Collective] kantjer:
Like you I also have 32 GB memory, and an SSD. swap I never touched. ccache I have set to 30GB but last time I checked only 15GB is used (Oreo build)

My build times are:

Fist build about 2 hour

Make clean build 25 minutes

Make install clean build 2-10 minutes depending on number of changes
[Android Builders Collective] DroidIt!:
Oh wow! Lol, now all I have to do is finish figuring the right way to put sources in my base. :p Maybe what I'll do then is leave swap alone and set ccache to 30. I had read in a couple spots using ccache can actually slow build times, but didn't know if that was old info or not. :)
[Android Builders Collective] theesotericone:
Swaps out dated and not needed for anyone running more than 8GB. Linux used to really suck at memory allocation but it's gotten much better.

As far ccache goes, your first build will be slower with it. The system has to create the files in the cache and link them so they can be found in the future. Your second build will be a bit faster. By the 3rd build 95% of the ccache will be built and it will be way, way, way faster. Use it. Never wipe it unless you have builds failing.
[Android Builders Collective] yung40oz84:
Ya I was just going to say those beans ones I get Google FC on clean flash. Also is there a reason the not yet ready always on display was removed? It worked good for me... Thanks. One last thing you or anyone got a good guide to make a correct swap file? I have my cchache set at 100GB, but my builds go pretty dang fast and I can easily tell a difference if I lower that. But I need swap.
[Android Builders Collective] DroidIt!:
Gotcha. Thanks for the advice all. :)
[Android Builders Collective] theesotericone:
Why do you need swap?

Also 100GB is huge for ccache. That's a lot of wasted space. Check the size of it currently with:

ccache -s

I'm betting it's in the 40-50GB range.
[Android Builders Collective] ezio84:
Ye that FC is one of those fixed with latest package ;D

Always On mode is under power button settings.
[Android Builders Collective] ralpheboyo:
Sweet setup

yup 16GB will work comfortably

depending how many devices you are building for ...20GB for one device is a good start

cool

nope...info is inaccurate.. [MENTION=5451511]theesotericone[/MENTION] hits the nail on the head with ccache

My following tips would be with your particular setup:

depending what distro you are using locate

/etc/makepkg.conf

from there:

1) Change your MAKEFLAGS .....in terminal

[I]nproc[/I]

whatever the result +1 and amend eg

[I]MAKEFLAGS="-j9"[/I]

2) Utilize & take advantage of your 32GB of ram ...edit the

/etc/makepkg.conf

and change to

BUILDDIR=/tmp/makepkg

(just remember to clean once in a while)

"As compiling requires many I/O operations and handling of small files, moving the working directory to a tmpfs may bring improvements in build times. "

ccache -MXXGB

= set ccache size

ccache -C

= Clear the entire cache

ccache -c

= Clean up the cache by removing old cached files (not really req as ccache handles this automatically)

ccache -s

= shows stats

ccache -z

= resets stats to zero

I have 16GB of ram and set my swap to 8GB once again [MENTION=5451511]theesotericone[/MENTION] hits the nail on the head...Happy building and great to see you here ...(stop lurking in the dark...:)
[Android Builders Collective] kantjer:
​

ABCrom_angler-8.0.0-20170922

We recommend: install Oreo full factory img first and do factory reset without restoring apps with TiBu

If you don't want to go that route (but don't complain if thing don't work as expected)

September 2017 vendor image can be downloaded here

you will need to flash the september vendor.img after flashing the Oreo ROM, otherwise it won't boot.

ROM download

Recommended GApps

Installation, tips, info: check the 6th post of this thread

**** Huge thanks to [MENTION=2095315]ezio84[/MENTION] for his tireless work on both the ROM and GApps package during the last few weeks ****

If you have problems, call the A-team or clean flash
[Android Builders Collective] ralpheboyo:
whoop whoop....thats the green light we been waiting for.... @ezio84 a thank you doesnt even come close to all the hard work you have put in ...but its a start!!!! also a huge thxs should be mentioned to all involved in the process!!!!
[Android Builders Collective] mohican16:
ABCrom_bullhead-8.0.0-20170922

Download for Bullhead https://www.androidfilehost.com/?fid=673368273298988075
[Android Builders Collective] morfances:
up
[Android Builders Collective] Badger50:
Down
[Android Builders Collective] rohit25:
Middle.earth
[Android Builders Collective] DroidIt!:
Lol, will do...about lurking in the dark. :) Started my own business about 6 months back so been pretty busy. Trying to be on again more. Will play more with it today. :good:
[Android Builders Collective] icrunchbanger:
Running very smooth, great build. I had problem with my kernel on Linux so i had to do clean install, ill do repo sync tonight and try to build with your Nexus tree tommorow :)
[Android Builders Collective] ezio84:
As a side note for bloody Google dialer lovers :D

Since O, Google is pushing playstore dialer UI to the aosp one, so try the built-in aosp one (that has also the auto proximity speakerphone feature) :P

About custom leds: now like you can see you can customize the color and speed per-app, and also per-channel if the app (like Dialer, Google Messaging or Google +) supports the new notification channels system.

Someone also asked me why i didn't add the possibility to block the QS panel on secure lockscreen: not needed anymore, i've set sensible-data tiles (Airplane, Location, Data) to ask Pin/Pattern if the lockscreen is secure.

Navbar: in the abc navbar menu you can set autohiding keyboard left and right cursors, just fyi.
[Android Builders Collective] JaylanPHNX:
I know I should probably look at git, but do I need Andromeda for Substratum, or is there already support in the ROM for theming?
[Android Builders Collective] ezio84:
Substratum works out of the box.
[Android Builders Collective] davall:
Did the brave tour and dirty flashed.

Up and running fine :)
[Android Builders Collective] a g bell:
Excellent question there?Maybe but not at least until o comes to the op5 ?
[Android Builders Collective] ccferinxda:
Hammerhead is waiting:(
[Android Builders Collective] a g bell:
For source ??
[Android Builders Collective] DeathStroke:
[MENTION=2095315]ezio84[/MENTION] [MENTION=3306843]kantjer[/MENTION]

Ambient notifications not working on my angler for the apps, LED works. Lift to check works too.

Flashed as per instructions given. Is it known? or if it's me? ;)
[Android Builders Collective] buffal0b1ll:
Replicated and figured it out. At the moment if you have ABC Settings>Notifications and QS>Make Headsup Less Annoying on, it will stop Ambient notifications. Seems that Google has coupled ambient notifications with the ability of notifications to peek (heads-up). So for now pick one or the other and let's see if Ezio can fix it so ambient notification can work with heads-off in a future update:)

PS I cross tested the behavior with Rascarlo's Tiles app heads-off tile and saw same behavior.
[Android Builders Collective] ezio84:
Good teamwork guys, thanks both.

Fix being pushed in a while :highfive:

Like Bill suggested, till the next build just choose one option between Less boring heads up (which i love :D ) and Ambient (i prefer lift to wake).
[Android Builders Collective] DeathStroke:
Thank you both of you. ;)
[Android Builders Collective] formicae:
Took the plunge last night, looking really good, great work ezio and gang.

It's always cool to ground-floor on a new major-version ABC (and Slim before it) and watch it go from Stock+ to Stock++++ over time. Having to spend time with Stock+ really makes me appreciate all that ends up getting added, especially without bogging down our devices.

It's going to take a while to stop feeling like a dumbass when I swipe the fingerprint reader and expect the notification curtain to drop, though. :D
[Android Builders Collective] Tim Hughes:
It's under SYSTEM

Languages & Input

Advanced

in the gestures category.
[Android Builders Collective] ezio84:
Also under Settings - App and notifications - Notifications [emoji14]
[Android Builders Collective] formicae:
Great news guys! I figured out how to swipe the fingerprint reader to access notifications!

(I still feel like a dumbass, though)
[Android Builders Collective] ezio84:
Another little feature info, because someone already asked me :D

Navbar back button to kill foreground app is not available because now you can kill any app from the Recents panel in a safer way, just tap on the icon near the X one :D
[Android Builders Collective] buffal0b1ll:
Install the Gravity Screen app on the PlayStore. Pay for the unlock version. Join the beta. Get these fingerprint gestures. Profit.
[Android Builders Collective] buffal0b1ll:
I love that, but I still find myself accidently tapping the lock now when I try to open an app from recents. Muscle memory training is hard for me on that front.
[Android Builders Collective] ezio84:
Train more young padawan :D
[Android Builders Collective] mixerpilot:
Everything smooth like butter, until I ventured out. I cannot get data to connect. I have the APN for Verizon and show LTE with full bars. I did flash stock .19 before flashing ABC with BeansGappsMini-arm64-8.xx-unofficial-Oreo. Any ideas?
[Android Builders Collective] efan3719:
Clean flash?
[Android Builders Collective] buffal0b1ll:
I'm full of ideas... But firstly I'm confused what you mean by "cannot get data to connect" but also "shows LTE with full bars". Those seem contradictory to me.

You tried reboots and toggling everything you could think of?

Airplane mode, mobile data, preferred network type, roaming

Turn off Developer Settings>Mobile data always active

Pulling and reseating sim card

Making sure you have Carrier Services in system/priv-apps. Updating it on PlayStore. Installing if you don't have it already.

Double check your APN settings

Dial secret phone menu and see what the network settings are (and Google what they should be for VZW) at *#*#4636#*#*

Hope it helps.
[Android Builders Collective] DeathStroke:
I have installed google contact and dialer and *#*#4636#*#* returns nothing for me. I've to use another app to lock my network to WCDMA.

what should i look for?

Edit: aosp dialer does the job, not sure why google dialer cant. ?
[Android Builders Collective] Curiousn00b:
Few questions...

Decided to give AOSP dialer a try for proximity speaker after your last post with Google pushing updates to it, is it possible to get Nearby Locations?

Also, wondering if you plan to enable round icons or not? Looks like AOSP Dialer still keeps the original as well. For some reason, the Chrome icon looks kinda dope to me, lol.

Lastly, any chance to add an option to disable the 180° rotation? Sometimes when rotation is enabled and you're sideways for an example, the phone will go upside-down becomes of that. Maybe someone can tell me how to disable this as well when building if an option won't be available? [emoji848]

Thanks for the O release as well. Feels awesome to be back on ABC after coming back from stock. [emoji41]
[Android Builders Collective] ezio84:
Don't know about nearby locations.

Icons can now have any form you want, it's up to the app or the launcher. In Nova settings, for example, there's an Adaptive icons option where you can set everything.

I'll disable the 180° rotation upstream, i agree with you it can be annoying sometimes.
[Android Builders Collective] fracman:
Curious, how did you set your navbar like that?
[Android Builders Collective] Curiousn00b:
Awesome thanks!

I'll probably mess with the framework to enable them manually. I like to have them looking the same throughout the system(recent apps, settings, and so on). [emoji14]
[Android Builders Collective] ezio84:
I've already enabled round icons in the framework ;)

It's the launcher handling them that way eheh
[Android Builders Collective] Curiousn00b:
Looks like I'll have to play with my setup. I see some icons round, and some are square, lol. [emoji23]
[Android Builders Collective] ezio84:
I think the best would be to disable round icons in the framework to have uniform system icons, then the launcher can handle the shape according to user preferences.
[Android Builders Collective] Curiousn00b:
I loved that at one point, but then OCD kicked in and loved having Slim Recents icon packs match my launcher icon pack. Completely substituted CM and Substratum's(testing and eventually...maybe) icon pack feature.
[Android Builders Collective] rp158:
[MENTION=7157050]mohican16[/MENTION] and whole ABC-team: thanks for bullhead-oreo, great. Flashed clean, without GApps, restored user-apps with TiBu. Fine to find ABC-extra's again. All's working fine so far. I'll post again after a few days about battery-life.
[Android Builders Collective] Gunners_Classic:
I would like to know that too please :)
[Android Builders Collective] aoaleman:
Damn, guess it was my turn. I got the dreaded bootloop yesterday. In my case, TWRP is still accessible. Tried everything, clean flashed latest built sources of Ezio's Oreo but couldn't get anything past the Google boot logo and also clean flashed Google stock factory image and nothing. Then I searched XDA and found a custom stock O kernel with four cores and "old fstab". Finally was able to boot in but on stock image. Nothing else works, for now I hope. Just wanted to share.
[Android Builders Collective] mixerpilot:
Yes. 3 times from stock.

Tried all those with no luck. APN was grayed out. I did have carrier provision services f/c on first boots. Updating from playstore didn't help.
[Android Builders Collective] ezio84:
Very sad :(

I can't test anything with Verizon so i need at least a logcat of that Fc if possible.

Btw there are a few more carrier apk in the factory that i'll add to the build, maybe they'll fix those USA carriers issues.

---------- Post added at 12:56 AM ---------- Previous post was at 12:05 AM ----------

@mixerpilot added the new carrier vendor blobs, try to build if you can or wait for the new build and see how it goes :good:
[Android Builders Collective] Lawlrus:
[MENTION=3306843]kantjer[/MENTION]

8.0 build is running very well.
[Android Builders Collective] mslatter:
I had a bootloop issue too. It started because I wasn't paying attention after a successful clean install of ABC. I was heading out on a trip and realized my camera didn't work - so instead of thinking things through, I merely attempted to restore the stock backup. Bootlooped right into recovery. Girlfriend is standing at the door waiting on me - not a good time for this! So I dirty flashed ABC over the bootlooping stock. Started to boot! Jumped in the Jeep and started heading out... but N6P just kept rebooting.... Argh.

So wiped everything but storage. Flashed Vendor image, flashed ABC and the recommended Beans gapps, plus Magisk. Wiped cache and rebooted... perfectly. Titanium to restore apps EXCEPT camera. Then once at the resort, found the Nexus /pixel Google camera apk online, installed and back in business.

Now if I'd only thought to do the last step first, none of the other steps would have been necessary! Lol Complacency at its finest.

As always, thanks to all the builders for getting ABC Oreo out!
[Android Builders Collective] fracman:
Oreo on Angler is amazing so far. Thank you
[Android Builders Collective] Lawlrus:
Try toggeling airplane mode after rebooting at least once.

Its been working fine for me after i got it to connect.
[Android Builders Collective] Lawlrus:
Also i did cylce through preferred network type from global through the other two then back on global. And enabled data while romaing. Global is what i have it on currently.
[Android Builders Collective] JaylanPHNX:
Anyone else having issues with Bluetooth headphones controlling media playback? I'm wondering if there's some sort of setting or permission I'm missing.
[Android Builders Collective] Curiousn00b:
My Beats X are working fine here. [emoji41]
[Android Builders Collective] JaylanPHNX:
Maybe it's just me. Could be my fouled-up ARISE installation.

Edit: I also seem to be charging slowly regardless of charger/cable.
[Android Builders Collective] Weetbix:
I'm going to flash this tomorrow once I finally get time. But in the meantime - just to ask the probably silly question and make sure there's no misunderstanding for the recommended method...

Basically, follow the guide here to flash the factory image, then re-flash root/twrp as per here, before flashing ezio's hardwork?

Sounds like a breeze

Thanks!
[Android Builders Collective] Lawlrus:
You're flashing source built 8.0 you shouldn't need to spend all day over flashing.

Clean flash with the right vendor from 7.1.2 and it's done with.

I've never been on a factory 8.0 image and everything has been fine for me on a multitude of 8.0 roms.
[Android Builders Collective] tcat007:
I just came from another Oreo ROM. No issues at all.

1. Cleared cache, system, data.

2. Twrp, flashed ROM and Beans gapps. Switched twrp to install image and flashed .019 vendor, booted.

3. Setup a few apps and settings. All good.

4. Twrp, flashed magisk 14, rebooted, all good.

5. Set up remaining apps and titanium data.

So far looks good. Substratum and Arise next.
[Android Builders Collective] RomyRodriguez:
does the always on ambient display has the burn in protection?
[Android Builders Collective] kero68:
Anyone else having issues with using Substratum to centre the clock. Worked fine on stock but not liking something in custom ROMs.

Perhaps something that will smooth out in future builds...
[Android Builders Collective] Lawlrus:
I would assume it's because of data traffic yeah?

I've not had issues on it with other source built 8.0 roms
[Android Builders Collective] kero68:
Yeah perhaps. Entire system seems to crash and phone reboots into recovery so the Substratum rescue zip can be flashed.
[Android Builders Collective] tcat007:
I had that issue with nitrogen. If the status bar isn't a system font, you can't use Clock Tweaks. This ROM must set the font of the status bar. I was going to try that next, thanks!
[Android Builders Collective] kero68:
Interesting. I was only making the clock bigger and centring it but I have previously changed my system font via a flash let font zip...
[Android Builders Collective] Lawlrus:
It happens even if you only move it
[Android Builders Collective] tcat007:
Yeah, I just changed my font, and status bar did change, so I have no clue. I got the same black screen booted to recovery... flashing rescue disc while there fixes it quickly.
[Android Builders Collective] kero68:
Yeah, I just tried a couple of different options. Happening on all.

Anyway, not big deal considering how good this Rom is. Early days so status bar tweaks are only a matter of time, I guess.
[Android Builders Collective] tcat007:
Found an issue that was also on Nitrogen. Play button on Pmusic is black on black. Is ok on another Oreo ROM.
[Android Builders Collective] Lawlrus:
On one theme? Lol or is pmusic not play music ?
[Android Builders Collective] Weetbix:
Lol, yeah. There's so much I do on my phone that I don't need to do. Still trying to break the habit.

Thanks.
[Android Builders Collective] bdwilk:
You can try this. It was posted earlier today by a dev of 8.0 aroma mods. I haven't tested it as I'm on an 8.0 ROM that Iraqis theme works on.

https://xdaforums.com/nexus-6p/themes-apps/mod-center-left-clock-o-t3614824/post73920275
[Android Builders Collective] ezio84:
Mods like Arise can give hard to track issues [emoji14]

That's why I don't like to use them.

Charging values in lockscreen are real time, instead stock gives an average speed indicator that will be almost always "fast". They depend on the battery level, temperature and so on.

No, Google didn't provide it. They probably assume that ambient infos would not give burn issues.
[Android Builders Collective] RomyRodriguez:
ok then, i was asking because the post that was showing the commit was also showing how to add the burn in protection
[Android Builders Collective] ezio84:
Which one?

Nevermind found it, will add it too thanks (but i still think the always on feature is not so useful :P ).
[Android Builders Collective] tcat007:
Yeah play music. The notification pull down has the button, it's a widget on the homescreen that doesn't. I'll try a couple other themes to see if it's a theme issue.

Edit: tried 6 themes, all have black play button, white pause button. Definitely a ROM issue.
[Android Builders Collective] Lawlrus:
What overlay controls the widgit being blacked out ?
[Android Builders Collective] tcat007:
Just the play music overlay. You have to reboot to get the colors to apply to a widget. I also tried a different launcher, same issue.
[Android Builders Collective] Lawlrus:
I've got it doing it too now. I was using compound for play music,bt for whatever reason the widgit was white while the app itself was blacked out
[Android Builders Collective] RomyRodriguez:
i think is useful in a few moments, which in my case i go thru those moments in a daily basis, what makes u think is only available for normal ambien notification only? i mean is available for ambient display as a whole, so if modified will be applied to the feature it self, can you explain to me just alittle bit.