yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] Reechings:
Oh **** really? I have that zip already because someone said it can fix vendor mismatch message but no one ever told me to do that to fix this error. I'll try it out tomorrow ???
[Android Builders Collective] kantjer:
​

ABCrom_angler-8.1.0-20180615 - (June 2018 patch level)

Download

Recommended GApps

Image files

Telegram users can use this bot "@ABCrom_angler_bot" to be informed about updates

If you have problems, call the A-team or clean flash
[Android Builders Collective] ezio84:
And Berkeley build:

https://www.androidfilehost.com/?w=files&flid=270450
[Android Builders Collective] reference2myself:
Sweet, let's see this swanky new boot animation.

Edit: love it
[Android Builders Collective] reference2myself:
So does substratum no longer require root with this update?
[Android Builders Collective] buffal0b1ll:
Yes
[Android Builders Collective] fKm:
In case someone wants to try something new for his taimen: https://androidfilehost.com/?fid=818222786056038203 (Validus for taimen)

Gapps included

Note:

- The vendor mismatch error will be fixed in next build. I just forgot to cherry-pick one commit :)

- activate the NavBar at settings after first boot. It is not there for any reason

- as far as I know everything works as expected
[Android Builders Collective] ezio84:
Don't know Validus code, btw be sure you have this line:

<bool name="config_showNavigationBar">true</bool>

in the device tree overlay path (overlay/frameworks/base/core/res/res/values/config.xml)
[Android Builders Collective] Reechings:
Thanks for this and can I beg you for a crdroid build? ???
[Android Builders Collective] fKm:
Sure. I will look at it this weekend I think. Don't know if I can handle it but I will try my best.
[Android Builders Collective] Reechings:
That would be epic! There is an unofficial build from the 27th on AFH but it has some issues. The setup wizard crashes if you try to restore, the spacing between battery and mobile signal is too small on status bar and the battery is too close to the right side, there is no option in developer settings to force enable themes or whatever that is called, the system ui crashes any time you change options and you have to clear data on play services to get downloads from play store working. Besides that it's perfect ???
[Android Builders Collective] fKm:
Phew, that are a lot of issues. I bet it won't even boot when I build it :silly:
[Android Builders Collective] Reechings:
Well if it doesn't work there's always RR, only issue I can remember from last build was that saturation option didn't work.
[Android Builders Collective] fKm:
New Validus build for taimen with fixed NavBar and fixed vendor mismatch error: https://androidfilehost.com/?fid=746163614322272636
[Android Builders Collective] theprincekhan:
Sorry noob quiry but what's different between berkeley build and kantjer build?
[Android Builders Collective] ezio84:
"Berkeley" (berkelol for friends :D) is the device name of the Honor View10.

Builds are the same, kantjer's one is for "angler" (nexus 6p).
[Android Builders Collective] neekless:
I've only just realized this but Do not disturb mode also silences media as well. Is this intended? [MENTION=2095315]ezio84[/MENTION]

Edit: Okay apparently this is intended in stock android as well... Though it doesn't make sense to me since I don't consider my media as disturbances..
[Android Builders Collective] Roger.T:
LOL!

Berkelol ?

I have never heard of it until now...?
[Android Builders Collective] ezio84:
I agree with Google on that instead.

Because once you enable the "Total silence" mode, it must be a real total silence mode, without the possibility to get unwanted audio events in specific situations (e.g. an important business meeting).

If you still want to play audio, there's the "Priority mode", or you can just disable dnd (once you can disturb people around you with a media event, dnd doesn't make sense anymore in that situation).

You can even enable the priority mode and disable the ringer volume to avoid unwanted calls.

More or less they covered all situations.

PS: i think they made it worse on Android P though, because they dropped those modes and you must set each time dnd options according to the situation.
[Android Builders Collective] neekless:
Yeah my bad I was in total silence mode not priority mode.

Btw I just did a clean flash and the screenshot problem is still happening. It only happens in the Settings app... Out of ideas :crying:
[Android Builders Collective] neekless:
[MENTION=2095315]ezio84[/MENTION] I finally found the cause of the screenshot problem!

The problem was when appending the app name "Settings" to the screenshot file name, it gets messed up. I thought it might have to do with my device language, since I was using English (US Virgin Islands). I changed it back to English (United States) and the problem doesn't happen anymore. So yeah. You might wanna find out why it does that on other English variations though.
[Android Builders Collective] ezio84:
Uh nice catch! Will try to fix it, thanks ;) EDIT: fixed

PS: cant' find that Virgin Islands language in the list, how is it called? EDIT: nevermind, found it
[Android Builders Collective] Stevica Smederevac:
Click English,then variation of English and British Virgin islands;)
[Android Builders Collective] ezio84:
Thanks :good:
[Android Builders Collective] DJesri13:
i need help, I try to wipe system and cache, then install latest rom from kantjer com for my nexus 6p (then flash OpenGapps for 8.1 arm64). It just gets stuck on the boot animation screen though. "THE ABC ROM" with the lines flowing underneath.

please help,

Nevermind, I think I got it
[Android Builders Collective] bdwilk:
Did you wipe data? You need to wipe data. Make sure you're on latest vendor also from kantjer.com
[Android Builders Collective] TRIUMF:
Don't use OpenGapps. Use Beans as suggested somewhere in this thread. With OpenGapps I thought everything was working fine until I tried to install Android auto. Ended up with wipe and reflash and lesson learned:)
[Android Builders Collective] mohican16:
ABC_ROM_bullhead-8.1.0-20180617

Download https://www.androidfilehost.com/?fid=962339331459001082
[Android Builders Collective] DJesri13:
I got it it just kind of feels limited compared to AICP and Resurrection Remix. I also thought it wasn't L-OS based. But I really like the eq better than the one that comes with the other ROMs. Is there a way for me to get it (or the stock one that comes with my Nexus 6P) on a different ROM

Probably wrong thread but IDK
[Android Builders Collective] paolocorpo:
Thanks so much as usual dear [MENTION=7157050]mohican16[/MENTION]

Is OK the vendor image OPM6.171019.030.B1.img ??
[MENTION=2095315]ezio84[/MENTION]: do you have a new update of the gapps ?

Inviato dal mio Mi A1 utilizzando Tapatalk
[Android Builders Collective] Josh:
June gapps and flash june vendor. Search little bit before ask ;) ?

https://androidfilehost.com/?fid=674106145207491329
[Android Builders Collective] Roger.T:
My current setup ?

I love ABC ?
[Android Builders Collective] neekless:
Thanks for the quick fix!

I found the screenshot problem when I was trying to take a screenshot of another problem: all my data usage is counted as background, even when I actively used the app in the foreground. For example, after I watched a video on YouTube using mobile data, the data usage is counted as background (shown in screenshot). This happens to all my apps, even after a clean flash. Can you check if it happens to you?
[Android Builders Collective] Maibol:
psssss....... any abc GSI around ????

i would gladly try it on my one plus 6 :cowboy:
[Android Builders Collective] ezio84:
Same here but that's an aosp/Google thing, no idea how it works :p
[Android Builders Collective] neekless:
Ah I see. Was wondering if it was due to the rom since this didn't happen when I was on stock android few months ago. Maybe google screwed it up in recent updates.
[Android Builders Collective] drugo732:
thank you.. as always!

but sometimes a changelog? or when nothings it's write are only security update?

according to you in a dirty flash, when there are new gapps from ezio, it's raccomended to flash also? or it's the same from playstore?
[Android Builders Collective] fKm:
Hey ezio84, do you consider adding now playing (ambient music) feature to ABC? I really like that feature on my Pixel.

Corresponding commit is here: https://github.com/CarbonROM/android_frameworks_base/commit/7cb81341eb8054447e753914bd623dff17b05ed9
[Android Builders Collective] jerethi:
You can always see the changelog posted at www.kantjer.com.
[Android Builders Collective] Schiben:
Brand new to this ROM. I can't seem to find DT2W anywhere, but I swear I saw it was an option.
[Android Builders Collective] ezio84:
ABC has its own ambient music ticker stuff for local and remote playing music (not music recognition): https://github.com/ezio84/scripts/b...and_tips/Commits-list-with-links WIP.txt#L515

:cowboy:

dt2w is a kernel/device specific feature.

On 6p, stock kernel and abc kernel at default (EDIT: but you can enabled them with a kernel app) don't have it.
[Android Builders Collective] fKm:
Yeah I know, but I mean the music recognition. Is that a feature which can be easily be integrated? I really like that on my Pixel.
[Android Builders Collective] ezio84:
I don't plan to add it. Iirc Pixel 2 has a specific low energy stuff for that feature, and at least for me apps like shazam or the Google sound recognition tile are enough.
[Android Builders Collective] dafreaking:
Weird issue on angler. If my Battery is between 25-35% the phone reboots if a timer/alarm goes off
[Android Builders Collective] ezio84:
PS: the other reason is that feature relies on closed source code, and i don't like the idea to add a feature that Google could break anytime server side changing how that code works.

PS2: Carbon guys work has been awesome though, and my ambient music ticker stuff is based on their commit.
[Android Builders Collective] Natakranta:
Its battery is dying. End of life :(

Kantjer recently replaced battery in his N6P and it's like new phone again, back to good battery life.

Be careful with ebay batteries, usually they're worse than the old original one you have.

I'd recommend doing what kantjer did, go to good trustworthy phone repair shop, pay more, but let them do the job and take responsibility for (not) braking the phone during disassemble and for quality of new replacement battery.

---------- Post added at 11:25 AM ---------- Previous post was at 11:22 AM ----------

What? I aware I had DT2W few months ago on my N6P running ABC with its karnel. Just had to enable it in EX karnel manager.

Or is my memory foggy?
[Android Builders Collective] ezio84:
Yes, i meant at default. WIth a kernel app you can enable them even on abc kernel, added Elemental X wake gestures are still in :D
[Android Builders Collective] Natakranta:
Ufff, you scared me I'm starting to get dementia :D
[Android Builders Collective] pkelly517:
Hmm. I didn't see anything in [MENTION=2095315]ezio84[/MENTION] quote that would DISprove dementia.

[emoji16] [emoji23]
[Android Builders Collective] ezio84:
Well, i even forgot to mention the kernel app thing, so the first one who should check himself it's me :D
[Android Builders Collective] Roger.T:
If I remember correctly, this option would be in the system UI tuner. But it is disabled in ABC...?
[Android Builders Collective] fKm:
Finally my ABC build fpr Pixel 2 XL runs smooth too. If someone is interested: https://androidfilehost.com/?w=files&flid=276928

Flashing procedure is like davalls build: factory reset, flash ROM, flash TWRP, reboot into recovery, flash disable-verity.zip, boot into system.

My build is bigger than davalls because I include some Gapps from the start. Have fun.
[Android Builders Collective] Roger.T:
Then I remembered wrong ?

Maybe that was at the pixel 2xl ...?
[Android Builders Collective] ezio84:
Likely :D

Afaik on Pixel 2 xl you have the double tap to wake option straight in the System Gestures menu.
[Android Builders Collective] Roger.T:
I had a P2XL for a short time.

I had probably confused something (I'm getting old) ?
[Android Builders Collective] ezio84:
Welcome in the club :cowboy::D
[Android Builders Collective] Roger.T:
LOL!

Subsequent congratulations to your birthday ?

Was yesterday, right?

I turned 51 a week ago...?
[Android Builders Collective] kantjer:
Yep, my 6P got a second life after the battery replacement, feels like new again.
[Android Builders Collective] ezio84:
Eheh happy birthday to you too then :D
[Android Builders Collective] Badger50:
Wow! 51....youngster! Happy B-day Wallpaper God! ??
[Android Builders Collective] Roger.T:
Haha!

You are not that much older. ?

But thanks ?
[Android Builders Collective] mohdschizo:
I really missed [MENTION=5379942]setiawanjimmy[/MENTION] very much [emoji26]
[Android Builders Collective] pkelly517:
These kids act like not dying is such a big deal.

They should really get off my lawn! [emoji16][emoji23]
[Android Builders Collective] abhimba1586:
How did you resolve this issue? Even I am stuck at boot animation.
[Android Builders Collective] DJesri13:
I didn't, I switched back to AICP.
[Android Builders Collective] abhimba1586:
Does this build specifically require wiping of data? Is dirty flash not enough?

I am stuck at the new boot animation after dirty flash. Wiping data would mean installing the apps all over again.

I am on latest TWRP, beans gapps and latest June vendor.

---------- Post added at 04:50 PM ---------- Previous post was at 04:35 PM ----------

Yeah updating newer builds in AICP is a cakewalk. Never faced any issue.

Have had some trouble updating ABC with each new build. But I love the stability and functionality of ABC. Worth the trouble during updating builds.
[Android Builders Collective] Roger.T:
Dirty flash always works for me. I have never had problems with ABC and updates...

Wiping data or system is usually only necessary if you come from another ROM..
[Android Builders Collective] buffal0b1ll:
Everyone here dirty flashes all the time.

What device are you on?

What ROM version did you have installed before dirty flashing?

Did you wipe system, cache, and dalvik?

What are all the zips you are trying to dirty flash?

Do you have substratum installed? Maybe you have an overlay issue at boot and the rescue zip can fix it.

Help us help you. Provide details.
[Android Builders Collective] abhimba1586:
I've been facing little trouble while updating the new builds of ABC for a while now. on my angler.

1. Everytime while dirty flashing the ROM, I get error "Failed to unmount /system. Device or resource busy". But the magisk preserve script runs successfully

2. To overcome this I repair the system partition in wipe menu. Then convert the system partition to exFAT and again convert it back to EXT4. This allows the ROM flashing successfully. But then magisk preserve script does not run and I have to manually re-install magisk.

3. Build updates would work perfectly after this everytime. But the 06/15 build gets stuck at the new boot animation. Someone suggested to another person facing the same issue that data needs to be wiped. But that would mean re-installing apps all over again. I don't think data wiping is absolutely necessary here.

Any help/suggestion from the developers or other experts would be deeply appreciated. I really love this ROM.

I am on the latest June vendor, and latest TWRP.

---------- Post added at 05:25 PM ---------- Previous post was at 05:15 PM ----------

I am really sorry for my incomplete query. I am still learning to be adequately specific.

I am on Angler. Currently I am on 06/05 build of ABC and I failed during updating to the latest 06/15 build.

I did dirty flash wiping cache and dalvik (Should system need to be wiped too while dirty flashing?)

I just dirty flash the latest ROM zip followed by Elemental X kernel and Magisk

Yes I do have substratum installed but I make sure to disable all the overlays before I upgrade the ROM

I have given more details about another problem that I face while updating the ROM in the post just above this one. Maybe its just me, but there's always this issue while updating.

I appreciate your kind response.
[Android Builders Collective] kantjer:
Next time try booting with stock kernel first and make sure to use the recommended gaps. Wipe system if you are currently using an other GApps package.

I mentioned this many times, I flash almost daily and never wipe anything. I do one clean flash per year when there is a major android update, after that flash and forget.
[Android Builders Collective] buffal0b1ll:
Wow. It sounds like you're doing everything right. You shouldn't have to wipe system too, because the ROM installer will wipe it anyway after running the backup tool scripts to preserve hosts, Gapps, and Magisk. I was just curious.

That system repairing step you're mentioning needing to do occasionally sounds scary though. First time I've heard about that issue.

If I were you I'd try wiping system, cache, dalvik and flash 6/15 angler, June ezio beans Gapps and see if it will boot.

Then go back and flash ex and Magisk afterward if things go well.
[Android Builders Collective] ezio84:
Dirty flashing since Nougat here.

If you use stock kernel, stock partitions (ext4), latest official twrp, recommended beans gapps, there's literally no possibility to get a bootloop.

Once you flash additional things like kernel, Magisk modules, themes, xposed or whatever and the rom doesn't boot, just try to skip them one by one (wiping system comes in handy).
[Android Builders Collective] abhimba1586:
Thanks to your and [MENTION=3306843]kantjer[/MENTION] 's advice I just flashed the 06/15 build without flashing anymore zips like custom kernel or magisk. I was able to boot, but on unlocking the phone, a number of apps started crashing one by one with error "the app has stopped". I flashed the 06/15 build again followed by June Beans Gapps this time (though I was already on this Gapps from 06/05 flashing), but to no avail, with the same app crashing issue.

I'm even quite embarrassed asking when no one else seems to be facing these issues. If nothing works, I don't mind going back to the Nandroid back up of 06/05 build and wait for July's security update and see if that brings some sunshine for me. Or just wipe the system partition as the last resort.
[Android Builders Collective] VictorLapin:
First, I'd like to reinforce the point that if you switch gapps packages, system wipe is mandatory. Also, crashes could be due to some play services dark magic.
[Android Builders Collective] buffal0b1ll:
Even if you're using the same Gapps as you used on 6/5, i'd still give wiping system, cache, dalvik and flashing ROM and recommended Gapps only first another try. Wiping system first can't hurt. It can only help to ensure that backup tool isn't restoring any old Gapps residue that may have been hanging out from many many flashes ago if you hadn't wiped system in a while.
[Android Builders Collective] bdwilk:
Well you didn't specify what ROM you we're currently on before trying to flash ABC. I assumed (as I only could) you were coming from another ROM. Do/did you have any themes applied? That's the only other reason I could think of it not booting other than a corrupted zip. Disable all overlays or flash the subs rescue zip if you get a loop and overlays are enabled.
[Android Builders Collective] Roger.T:
I think it's time for a fresh start for you...

Install the factory inage and then twrp, rom and everything else..

I think you did not delete the data.

It may be that after formatting the system partition twice with different formats, the apps will not have exactly the same installation path after installation as before..

The data will then search in the wrong path and crash...??
[Android Builders Collective] Bobbaloo:
I'm pretty sure I've seen the dev(s) here have stated that, to update all one has to do is dirty flash the rom alone. It doesn't get any simpler than that. Me? I do a semi clean flash each time and I come back to ABC again and again. It's where I am now. Stability, speed and simplicity. Straight out of the box.

---------- Post added at 04:24 AM ---------- Previous post was at 04:23 AM ----------

There ya go
[Android Builders Collective] Reechings:
Other people have said flash the rom then reboot to recovery and flash disable verity zip. Is that only the process for Pixel 2?
[Android Builders Collective] Badger50:
Yep :good:
[Android Builders Collective] Roger.T:
Added new wallpapers...?

To download as always here:

https://goo.gl/v2NjSA

Please enjoy it ??
[Android Builders Collective] Bobbaloo:
Thanks! Did you do the new boot animation?
[Android Builders Collective] Roger.T:
Of course...??
[Android Builders Collective] Bobbaloo:
Shoulda known. Nice. It's the first time in a long while I didn't change my boot animation
[Android Builders Collective] Roger.T:
Lol!

Tahnk you ??
[Android Builders Collective] Bobbaloo:
A nice animation has to also take into account the limitations of our aging device. Don't want to fry the phone while booting up lol
[Android Builders Collective] Roger.T:
lol ?

The boot process gets shorter with each new Android release. Since you have to adjust over time, the animation..

The ugly Puxel2 animation does not even play right to the end...?

Since the Google guys have focused on something else..?
[Android Builders Collective] abhimba1586:
Followed your advice. Gave a fresh start with full system and internal storage wipe with factory image installation. Then flashed ABC ROM. Things working perfectly now.

As stated by you, I guess the root of all my problems was the weird behaviour of system partition while flashing.

Just a little clarification from the developers [MENTION=2095315]ezio84[/MENTION] . After the clean flash, during the setup process of 06/15 build of angler, the google account login screen gives only voice input as a method of input by default. After a while a figured I had to change default language to English(US) for AOSP virtual keyboard to be displayed. Is this intended behaviour?
[Android Builders Collective] ezio84:
No, i use italian and the keyboard is showing correctly during the setup. Did you use recommended gapps or opengapps?

If the first, which language were set?
[Android Builders Collective] abhimba1586:
Yes I did install the recommended Beans Gapps provided with the ROM link.

By default on ROM installation, the language was set English(India) which is my home country.
[Android Builders Collective] ezio84:
New phonograph mod:

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

Uh than it can be language specific, will take a deeper look.
[Android Builders Collective] indian84:
I wish it supports Android Auto..
[Android Builders Collective] dadoc04:
running great... thanks man

edit... tried making calls and cant hear any audio. No ringing or the other person. This was on cellular and wifi both.... weird.

edit 2 because i CLEARLY didn't give enough info... this was a clean flash From Stock June factory image. Strange enough after not getting any audio during phone calls, i booted into twrp, factory reset and flashed Davall's build which is working fine.

hope this additional info helps some
[Android Builders Collective] kantjer:
​

ABCrom_angler-8.1.0-20180624 - (June 2018 patch level)

Download

Recommended GApps

Image files

Telegram users can use this bot "@ABCrom_angler_bot" to be informed about updates

If you have problems, call the A-team or clean flash
[Android Builders Collective] JaylanPHNX:
I'm having real issues with my Taiman. I was running stock and so I factory reset, flashed abcrom and twrp, rebooted recovery, flashed disable-varity, then booted to system. Except it never got to system, instead going straight back to recovery. I tried again with the same results. I then restored by twrp backup and now it boots straight into bootloader. I can get it to boot to recovery, but it's like there's no system. Any ideas?

Update: TWRP says I have no OS if I try to reboot after just flashing the rom.

Update 2: Fastbooted factory image without the -w, then restored Data from nandroid and I'm back up and running on stock at least.