yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] okmikel:
Official build faild, see https://jenkins.lineageos.org/job/android/15904/console:

[1384/1384] including ./vendor/zuk/ham/Android.mk ...
hardware/qcom/media-caf/msm8996/mm-core/Android.mk: error: libOmxCore (SHARED_LIBRARIES android-arm64) missing libgpustats (SHARED_LIBRARIES android-arm64)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
hardware/qcom/media-caf/msm8996/mm-core/Android.mk: error: libOmxCore (SHARED_LIBRARIES android-arm) missing libgpustats (SHARED_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
hardware/qcom/media-caf/msm8996/mm-core/Android.mk: error: libmm-omxcore (SHARED_LIBRARIES android-arm64) missing libgpustats (SHARED_LIBRARIES android-arm64)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
hardware/qcom/media-caf/msm8996/mm-core/Android.mk: error: libmm-omxcore (SHARED_LIBRARIES android-arm) missing libgpustats (SHARED_LIBRARIES android-arm)
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/core/main.mk:732: error: exiting from previous errors.
09:56:18 ckati failed with: exit status 1
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] docentore:
Cheers mate, not looking for punching bag, just trying to report that the bug is still there but no one seems to care about. True about my misunderstanding re 0912 build - [MENTION=319057]Oki[/MENTION] - my apologies, I jumped the gun and behaved like a angry kid.

Regarding AudioFX - Orden mentioned disabling aFX for speakers and headphones in LOS16 thread, which I did. Freezing part was part of reply to some user asking if uninstalling would make a difference. Then I was referred to same post by Orden. This pissed me a bit (it shouldn't, it is just a phone for god sake ;)) as I wouldn't be saying anything about the AudioFX freeze if I haven't done steps provided by dev.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
NOOOooo :crying:

Week ruined, life devalued, gonna kms. /s
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
No offense taken, don't worry. Just be patient, official LineageOS 15.1 for the Axon 7 was scheduled for today. The Lineage 15.1 source for the Axon7 device tree is also available for all those wanting to release custom ROMs based on LOS15.1.

Regarding the build error due to the missing libgpustats, I hope [MENTION=5027381]OrdenKrieger[/MENTION] or [MENTION=4911249]Unjustified Dev[/MENTION] could fix it on time and rescheduled for another day sooner than next Monday. Or.. maybe you guys could bring us a last unofficial build with the included wifi MAC and audioserver CPU bug fixes.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Fuilares:
After update to 20180911 safetynet fails, ctsprofile is false (I've got Magisk, before update everything was working well). I've dirty flashed Magisk again, but that didn't help. Any ideas?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
Use the module "magisk hide props config" and follow the instructions to install a spoof certificate.

Seems Google now trips safety net if the fingerprint isn't whitelisted so we have to do this all the time now. Luckily theres an axon 7 one available to spoof but if you want to you can use it to also trick Google into thinking you have a different phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
Don't panic, I'm working on getting the build fixed and restarted. The Lineage build queue is 25 deep right now, so it will be a while. But hopefully no more than 10-15 hours or so.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ITenson:
I know that the build is not up yet but I would like to clarify before it is out. Would the official build be a trebled rom or just a regular rom. Do we need to create a vender partition before flashing the official LOS? Any clarification would be great! Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Starting from 15.1 every generation will be Treble only, and assuming every other rom base on lineageos they will be Treble also.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
Adding to what [MENTION=3044858]DrakenFX[/MENTION] says, yes this is a treble ROM. You do not need to do anything to prepare, it will automatically detect if you have a vendor partition and, if not, it will create one for you by slicing off a portion of the system partition.

The system partition size in Lineage and AOKP has been updated from 6gb to 3gb to accomodate this change on both the 14.1 and 15.1 branches. So you can flash both the latest 14.1 builds and 15.1 builds with no issues (assuming you take care to use the matching boot stack and modem). I don't use any other ROMs so I cannot vouch for them.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
A seemingly stupid question but will GSI roms work with the aforementioned implementations of treble?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Yes. They already do with the latest unofficial build.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Good to know, thanks.

Last question.

Any significant bug with GSI's?

Or are they good to use on a daily basis?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Sorry, last build left out the audio patch previous builds before 9/11 had it. I would recommend waiting till next week for the official build to get ironed out. For now I'll be dropping a build in a few hours with the latest lineage source + a few patches before we submit it for next week's build.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Thanks Unjustified Dev, having an unofficial build from you with the high CPU consumption in the audioserver and the MAC fixes will be very welcome for a lot of Axon 7 users in these forums. Even more if you include all the latest patches for the LineageOS.

Thanks

---------- Post added at 19:27 ---------- Previous post was at 19:21 ----------

Yesterday I spend some time testing different Pie configurations. Using LOS15.1, and then flashing ArrowOS Pie GSI, provides a nice and highly customizable system able to be used as a daily driver. Nonetheless since I was using the 9/11 unofficial LOS 15.1 , The Audio CPU bug was still there. Other than that, everything I tested was working fine. I am waiting for the audioserver CPU bug to be fixed in LOS15.1 to use it as a daily driver and do a deeper testing on newgrounds.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
WiFi mac fix is merged already. We just need to ensure this audio patch works and I'll see to getting in merged after tdm tests.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
LOS16 unofficial build had that audioserver bug fixed. I thought you guys applied the patch to LOS15.1 too. Whatever you did to LOS16 is working fine.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
it's not, i reported it being there after orden said it was fixed, on the latest build and all. Also disabling audiofx didn't work.

Memory leak is fixed but not cpu usage.

Someone else reported a lot of tfa9890 errors too, just not sure if it was in the los16 thread or 15.1.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Not me..the audio dev. We might have to ping him on that issue if he's not busy, but if we can improve it before official by merging that patch he gave us that's a start. So this drain issue isn't related to headphones it's also with playback from the speaker?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
I couldn't duplicate it in LOS16. It was an evident issue in latest unofficial LOS15.1

How did you duplicated the issue in LOS16?

---------- Post added at 01:49 AM ---------- Previous post was at 01:44 AM ----------

It is only related to the headphones. Audioserver takes around 70% of the CPU when any audio app is working. The normal drain in this configuration is about 6% for the audioserver. I used Spotify to easily duplicate the issue and top through and to get the cpu readings.

It doesn't happens when using speakers.

It doesn't happens when using LOS16 (not in my case) even when using headphones.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Headed home now to check if the build is done and I'll see about debugging the issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Awesome!!!!

I can add that the audioserver thread is the android.hardware.audio@2.0-service related one. It can be duplicated with any audio app. I have tested with several players playing local MP3 and AAC and it is the same.

A logcat of the affected thread returns this in an endless loop while the headphones are plugged:

09-24 23:21:33.228 14818 14972 E TFA9890 : exTfa98xx_speakeron: mode 0, setmode 0, audio_mode 0, dev_mode 0
09-24 23:21:33.228 14818 14972 E TFA9890 : zte: change to channel
09-24 23:21:33.228 14818 14972 D tfa98xx : Loaded container file speaker_on /etc/settings/stereo_qcom_spk.cnt.
09-24 23:21:33.228 14818 14972 D tfa98xx : tfa start with volume 0.
09-24 23:21:33.279 14818 14972 E TFA9890 : tfa98xx_start: tfaRunSpeakerBoost err 5
09-24 23:21:33.279 14818 14972 D tfa98xx : start use case failed
09-24 23:21:33.279 14818 14972 D tfa98xx : error is number 5
09-24 23:21:33.280 14818 14972 D tfa98xx : handles 0
09-24 23:21:33.280 14818 14972 D tfa98xx : [NXP] exTfa98xx status reg is 0x025d
09-24 23:21:33.280 14818 14972 D tfa98xx : [NXP] exTfa98xx has no clock input
09-24 23:21:33.281 14818 14972 D tfa98xx : handles 1
09-24 23:21:33.281 14818 14972 D tfa98xx : [NXP] exTfa98xx status reg is 0x025d
09-24 23:21:33.281 14818 14972 D tfa98xx : [NXP] exTfa98xx has no clock input
09-24 23:21:33.284 14818 14972 D TFA9890 : FUNC: tfaRunMuteAmplifier, LINE: 646 status = 0x025d
09-24 23:21:33.289 14818 14972 D TFA9890 : FUNC: tfaRunMuteAmplifier, LINE: 646 status = 0x025d
09-24 23:21:33.290 14818 14972 D tfa98xx : start failed then stopping device
09-24 23:21:33.296 14818 14972 D axon7-tfa98xx: tfa9890_set_amp_state: Failed turning amp on 48 times

Then when I unplugged the headphones everything returned to normal, and this was the logcat while returning to normal behavior:

https://pastebin.com/SAHKxHu3
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Latest build is located here (I've tested and was unable to reproduce the problem)

http://files.nwwn.com/~unjust/
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] [armitage]:
Thanks so much for your work, guys. It's really appreciated. :)

One question, tho...

Shouldn't the patch be in this week's official build as well? As far as I see it has been merged and the build starts in a couple of hours.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Yes, I went ahead and merged as soon as I could confirm I didn't run into the issue. A side note for people with Mac address issues as [MENTION=4126377]tdm[/MENTION] has found out /persist/wifimac.dat is written at factory if you don't have this file instead wifimac2.dat will be generated with a random mac, but it will/should persist regardless if you change ROMs or reboot. I am one of the unlucky people who don't have /persist/wifimac.dat anymore. On the latest build the wifi HAL was denied permission to write to /persist. So what this means is if you don't have /persist/wifimac.dat you'll still be in the same boat as before. I'm working on simplifying and tightening the sepolicy that reads and writes the mac address.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bYOndo:
Great, thanks [MENTION=4911249]Unjustified Dev[/MENTION] ! Dirty flash as usual? maybe "wipe dalvik/cache" before reboot?

Massimo
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] docentore:
I can confirm that with this build audioserver CPU bug is fixed, CPU usage below 15% with connected headphones.

Thank you very much.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xerocopy:
Confirming aswell, it's finally fixed. Thank you devs for staying with us and our phones. I appreciate your time.

No more endless tfa error in logcat and it's showing to switching to hifi mode.

disable_audio_route: reset and update mixer path: deep-buffer-playback headphones-hi-fi
hw_info_append_hw_type : device_name = headphones-hi-fi

Mine audioserver stay around 1-5% cpu usage, try to turning off (effects) AudioFX or even delete it, somehow it hit cpu usage to 20% (It happend to me when I plug headphones and cpu usage drop when I turn off effect in AudioFX)

After dirty flashing, Viper4Android stops to work, I figure out it was caused because of AudioFX.

On 9/11 I didn't need to delete AudioFX to make Viper4Android to work. On this release, it's required to make it work again.

However, input boost (1593mhz) on little cores is still there and main load is on big cores. Doesn't main load should stay on little cores and big cores should be used for heavier tasks?

Right now when I just texting with someone via SMS, big cores flying around 1.5ghz and little ones also staying on 1593Mhz due to input boost.

It makes phone little warmer than it should be and affect on battery. I will wait for fix on schwifty kernel for now.

Świetna robota!

Wonderful work!

Отличная работа!

Edit: Just tried HavocOS GSI, I has a little hope, that DAC somehow will work on it.

I moved tinymix binary from LOS to HavocOS and it report AK4962 on 1912 line.

If I may ask a stupid question, would it be possible to create a patch (binaries, libraries, xml files) from current LOS15 system.img (by catching file differences between both images)? It may not work on AOSP based Roms but it will work on LOS15 based like Havoc, RR, AICP? Just want to stay on havoc and try to fix dac but I'm not sure it is worth of time.

EDIT2: Edit:

Edit:

I was wrong, AK4490 DAC is working on GSI roms. It will kick in after playback.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] [armitage]:
I think something went wrong with compiling the latest build again. It was running for the last couple of hours and now it's gone with no Rom available.

Don't know how to get to the latest log, but maybe [MENTION=4126377]tdm[/MENTION] or [MENTION=4911249]Unjustified Dev[/MENTION] could take a look if they have time.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
You mean the official build? It just finished. It should show up on the download page soon. Give it an hour to sync everything.

Edit: apparently the download site is broken also. Lineage admins are aware and will fix it soon.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] [armitage]:
Oh, I'm sorry then for pinging you. Got a little too impatient there I guess. :D

Thanks for clarifying.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
Seems like download.lineageos.org is down, I get a Code 500 Internal Server Error.

What did you guys mess up now? :p:laugh:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] okmikel:
Try https://ftp.fau.de/lineageos/full/axon7/, it's a mirror and the new build is already there.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Of the many different flavors available, is there a specific version of TWRP required to make the jump from Stock B35 & TWRP 3.2.1-0?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Soyunamortz:
I'm on the same boat and would like to do the same jump I was actually scared to ask ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
That build broke some things on my end (dirty flash).

Apps were not starting and some settings were reset.

Do we have to do a clean flash when switching to Official LOS?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
I haven't personally flashed the official build. But in theory dirty flash from unofficial should work. If you decrypt data in twrp, you'll likely have to manually delete /data/system/packages.xml, but that should be the only issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
The Official build is probably signed with different keys, maybe that's an issue?

SIM settings, LOS Trust / Privacy Guard were reset, most permissions also. Only GApps installed via flash were working, everything else crashed.

Restored to 0911 via TWRP and manually updated to 0924 again, everything back to normal.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] okmikel:
Done a dirty flash with decrypted data and everything is working fine so far. No problem here. I was coming from latest official 14.1.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
Do not look at the line number of the tinymix report because it is different depending of the configuration The AK4962 is not a valid output for that configuration value. The correct command to get the actual DAC and driver routed to the headphones is:

tinymix -v "AKM HIFI Switch Sel"

I won't be able to test anything at least in the next 4 hours. If you can, just let us know.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Failed to open mixer :confused:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
1. Install a B12 bootloader (Universal, NFound or mine)

2. Install TWRP 3.2.x (recommended TWRP Labs Mod, TWRP 3.2.3-0 in the OP or NFound 3.2.1-8)

3. Depending on the encryption, you may need to wipe userdata.

4. Install LOS15.1 + Gapps + Latest Magisk (17.2 at this time)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] [armitage]:
Yeah same here. Good to read that I wasn't just being an idiot about it. :D

Guess just a dalvik/art, cache wipe flash is not an option on this one (also tried wiping /system and reinstalling gapps as well, but that didn't do the trick either).

I flashed Udev's latest for now, till I have time to do a clean one (all good and no FCs on this one).

Btw, device wasn't encrypted at any point so not sure if deleting "/data/system/packages.xml" would help...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mllora81:
Time to change the title of the thread? :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] voetbalremco:
A mirror isn't needed anymore, Lineage website is back up:

https://download.lineageos.org/axon7
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimhark:
[MENTION=3336455]amphi66[/MENTION], [MENTION=6740092]luisaet82[/MENTION]

When I first attempted upgrading from the last non-Vendor lineage-15.1 UNOFFICIAL from late July it failed. The log had his error:

Create /vendor partition failed.

I had TWRP_3.2.1-8_axon7-TREBLE.img installed as my recovery. I switched to twrp-3.2.3-0-axon7.img and install succeeded. For me, this version of TWRP was required.

Jim
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] okmikel:
Just flash again without reboot and it will succeed. So it was for me. I used TWRP Labs Mod.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xerocopy:
It was my mistype. HavocOS Oreo report AK4961 is used while headphones are plugged in. GSI ROMs still needs a patch for HI-FI mode.

However, I'm really thankful that we have stable LOS15.1 with working DAC and fixed audio server bug.

Edit:

I was wrong, AK4490 DAC is working on GSI roms. It will kick in after playback.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] wannaskoo:
Clean flashed the new release, it sounds reeeally good and without any kind of overheating/excessive battery drain. Thank you devs.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimhark:
I upgraded from lineage-15.1-20180911-UNOFFICIAL-axon7 to lineage-15.1-20180925-nightly-axon7-signed. After saving a copy of the file, I followed [MENTION=4126377]tdm[/MENTION]'s advice to remove /data/system/packages.xml. Dirty flash install + open gapps went smoothly. Possibly (porobably?) as a result of removing packages.xml, all my apps were gone. (packages.xml lists all my installed apps.)

UPDATE: [MENTION=4126377]tdm[/MENTION] reports below that packages.xml is just a cache that should auto regenerate. I recommend you have your apps backed up before upgrading to LOS 15.1 official.

/UPDATE

Only LOS default apps + open gapps were available on my device. No problem, I have a recent-ish Titanium backup and I've enabled Google's android backup.

On first start I went through setup. I chose to restore from backup and selected a recent backup . After more than an hour, the Pixel Setup notification still says "Installed 1 out of 84 apps". Not sure if this is stuck or slow. So I started Titanium backup but immediately got, "Titanium Backup has stopped". Doh!

UPDATE: Starting with no apps meant I didn't have Magisk Manager installed. That may have been the problem (I can't go back and test without a lot of work). I noticed this when I tried to get Titanium to do a restore and it couldn't get SU. Manual install of Magisk Manager will be required in any event.

/UPDATE

XDA to the rescue:

This worked for me. Now I'm going to Titanium restore a couple apps while waiting for Pixel Setup. Later, if I give up, I'll reinstall all my apps using Titanium backup.

Thanks to all the devs for pushing this to release and not abandoning 15.1 for 16. I'm sure it wasn't fun working on both 15.1 and 16 at the same time.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
packages.xml is (should be) just a cache file that is generated at boot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mb0:
wiped / formatted everything and did clean install:

device: A2017

recovery: 3.2.1-8 for android 8.x (new bootstacks) by: [MENTION=5492451]NFound[/MENTION]

1. ZTE_A7LOSv1_UniversalBootStack.zip

2. A2017Chinese_OreoModem.zip

3. lineage-15.1-20180925-nightly-axon7-signed.zip

4. open_gapps-arm64-8.1-nano-20180925

5. Magisk-v17.1.zip

reboot!

the boot time is so fast :)

i was very surprise when i hit "reboot" and after 10' sec' it was back and ready.

two things i don't understand:

1. under "System" it's say the i have A2017U; why? i don't mind. is this going to be a problem for me?

2. seems like i can't Shutdown the phone and connect it to charger; it's keeps to turn on; where can i change this setting?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
1. This is a unified build for both A2017U and A2017G. It doesn't bother detecting which actual model you have, everything reports A2017U. In theory we could add model detection by examining the modem partition, but that is really not necessary.

2. No Android phone stays off when charging. It always boots. Normally it boots to a special mode called "offmode charging" where only the battery charge screen is shown and Android does not boot. I don't know exactly why it's not doing this, but I recall u-dev saying something about the beta boot stack not passing the proper kernel command line to detect it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] docentore:
Is the patch available or it needs to be coded yet?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
It is included in the current official LOS15.1
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gregfrankenstein:
Does the bit about deleting packages.xml if decrypting /data only apply if migrating from unofficial or should I do this if I'm moving from official 14.1 as well?

EDIT: Whoops, this was answered.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
Only from unofficial. Because official builds use official signing keys, and the lineage installer has an old key check from the cyngn days that really should be removed.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrGit:
I was able to upgrade from Lineage 14.1 to 15.1 without updating my bootstack from B35, and have not run into any missing functionality so far besides fastboot being disabled on B35, which I can live with. I'll have to do some more testing over the next few days, because I'm sure there are good reasons to require the Oreo bootstack, but I just thought I'd mention my failure to upgrade the bootstack didn't brick my phone.