yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] oeffoeff:
Short Review of 20180615 build on A2017G

Thanks for your work.

I did a completely fresh install today

Fresh format + WIPE with twrp-3.2.1-0-axon7

Flash ZTE_A7LOSv1_UniversalBootStack

Flash A2017G_OreoModem

Flash lineage-15.1-20180615-UNOFFICIAL-axon7

Flash open_gapps-arm64-8.1-pico-20180615

In the short time I tested it, it seemed to work really well.

Right from the start I noticed the following things:

Vibration intensity is too high: If you press one of the capacitive buttons or keyboard buttons the resulting vibration is pretty strong for my taste. This makes it also a little loud, so people around you notice the constant vibration noise. Even when setting the vibration intensity to 1ms in the AOSP keyboard settings, it is still rather strong but somewhat usable still. For the capacitive buttons there seems to be no option to change this, except to turn it off completely.

Phone shows wrong Models: E.g. in "About phone" it shows "ZTE A2017U" although I have the 2017G version. Furthermore if you enter the settings the first time a little window says to finish up installation of your "pixel". :)

Backlight option: Is available in the settings and set to 5s on default. A7 doesn't have back-lit buttons though.

Non-swap-able buttons: Another minor issue. But if you are used to have the "back"-key on the right, this is rather annoying. There doesn't seem to be any option to change this back. Perhaps this is not in the scope of the ROM though. :(

Everything else seems to work fine so far: Phone calls, mobile, wifi, camera, ...:svetius:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] s0be:
People with echo during speaker phone calls, try this command:

setprop persist.axon7.amp_hal_device_map "16,2;17,2;18,2;19,2"
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
[MENTION=753345]s0be[/MENTION]: Many thanx for trying to help!

Unfortunately it still echoing on the other call side, after applying the property. :(

adb shell
getprop persist.axon7.amp_hal_device_map
16,2;17,2;18,2;19,2

axon7:/data/property # ls -la
total 92
drwx------ 2 root root 4096 2018-06-17 08:51 .
drwxrwx--x 40 system system 4096 1970-01-07 20:47 ..
-rw------- 1 root root 19 1970-01-07 21:08 persist.axon7.amp_hal_device_map
-rw------- 1 root root 5 1970-01-07 21:08 persist.bluetooth.disableabsvol
-rw------- 1 root root 1 1970-01-07 21:08 persist.camera.actfw.version
-rw------- 1 root root 0 1970-01-07 21:08 persist.logd.logpersistd
-rw------- 1 root root 5 2018-06-17 08:50 persist.net.doxlat
-rw------- 1 root root 1 1970-01-07 21:08 persist.radio.airplane_mode_on
-rw------- 1 root root 17 1970-01-07 21:08 persist.service.bdroid.bdaddr
-rw------- 1 root root 9 2018-06-17 08:50 persist.sys.dalvik.vm.lib.2
-rw------- 1 root root 0 2018-06-17 08:51 persist.sys.gps.lpp
-rw------- 1 root root 5 1970-01-07 21:08 persist.sys.locale
-rw------- 1 root root 1 1970-01-07 21:08 persist.sys.root_access
-rw------- 1 root root 13 1970-01-07 21:08 persist.sys.timezone
-rw------- 1 root root 3 1970-01-07 21:08 persist.sys.usb.config
-rw------- 1 root root 9 2018-06-17 08:50 persist.sys.webview.vmsize
-rw------- 1 root root 1 2018-06-17 08:50 persist.vendor.radio.adb_log_on
-rw------- 1 root root 5 2018-06-17 08:50 persist.vendor.radio.eons.enabled
-rw------- 1 root root 1 2018-06-17 08:50 persist.vendor.radio.msim.stackid_0
-rw------- 1 root root 1 2018-06-17 08:50 persist.vendor.radio.msim.stackid_1
-rw------- 1 root root 1 2018-06-17 08:50 persist.vendor.radio.ril_payload_on
-rw------- 1 root root 1 2018-06-17 08:50 persist.vendor.radio.sglte_target
-rw------- 1 root root 1 2018-06-17 08:50 persist.vendor.radio.stack_id_0
-rw------- 1 root root 1 2018-06-17 08:50 persist.vendor.radio.stack_id_1
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] s0be:
forgot to mention, gotta reboot after that prop change.

---------- Post added at 03:08 AM ---------- Previous post was at 03:01 AM ----------

I guess I should also add, that's a fix for *SPEAKER PHONE* calls. If you're having problems in regular calls, can't help you there.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
[MENTION=753345]s0be[/MENTION]

well I did reboot. I even tried it by wiping dalvik an cache. Still no joy. :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] s0be:
Just to bring it back to the head of the thread, this may help the devs to fix the problem better than "I tried a thing with no description of how I reproduced the problem and no logs". I'm just someone who has been building his own builds of this tree and has been providing logs that has helped get it this far. I can't reproduce any of the in-call echo issues, so my logs aren't going to help anyone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
I've already provided one with the previous LOS build: https://xdaforums.com/showpost.php?p=76814030&postcount=309

I'll make a log again. This time with the latest build. I can even provide logs from both sides of a call if it'd be useful?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] s0be:
Your log is for voice-handset, so not speaker-phone. The fix I provided was for speaker-phone usecase only. So no, it wasn't expected to fix your problem.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
I see.

OK I've tested all types:

- voice-handset - echo very strong

- speaker-phone - echo very strong

- head-set call (jack) - echo existent, but not very strong

- bluetooth car radio call - no echoing

I think it's all about background noise. The top mic seems to be more sensitive than the bottom one. I'd like to try to disable "noise cancellation". [MENTION=5027381]OrdenKrieger[/MENTION], [MENTION=4911249]Unjustified Dev[/MENTION], [MENTION=3044858]DrakenFX[/MENTION]: Do you know maybe how to disable "noise cancellation" in the build.prop?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sirizak:
Check this post for a mod to swap the back/recent buttons.

https://xdaforums.com/axon-7/themes/extras-add-ons-lineageos-15-1-t3800443

I agree on the vibration, I turned them all off.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] king1990:
[MENTION=6056215]lichtblitz[/MENTION]

Try to do the following :

Reboot to recovery

Flash bootloader from OP

Wipe everything including internal storage

Format data

Wipe everything again

Reboot to recovery

Flash ROM,Gapps,Root

Test and see this always worked for me
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
[MENTION=4896610]king1990[/MENTION]

It's the next thing I was planing to do. However I did all that before installing LOS 15.1 for the first time. I hadn't that issue on LOS 14.1.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] oeffoeff:
Thanks. For the Vibration Problem I installed kernel adiuter and changed Vibration intensity from 67% to 30%. Works pretty gold.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mow4cash:
Can you confirm this fixed the in call echo issue or is this just a recommendation?

Does anyone have "ok/hey google" working from any screen?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
.

[*]Phone shows wrong Models:

Reason of this is because is base on U variant ( newer blobs, etc,etc) and unless the dev creates a build per device won't be possible to change ....

You can go to build.prop and change it if that bothers you.

[*]Non-swap-able buttons:

You can use button mapper from play store (using as we speak)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haerwu:
Settings FCs:

06-17 22:37:52.907 6616 6616 D AndroidRuntime: Shutting down VM
06-17 22:37:52.908 6616 6616 E AndroidRuntime: FATAL EXCEPTION: main
06-17 22:37:52.908 6616 6616 E AndroidRuntime: Process: com.android.settings, PID: 6616
06-17 22:37:52.908 6616 6616 E AndroidRuntime: java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.settings/com.android.settings.Settings}: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.Toolbar.setOnClickListener(android.view.View$OnClickListener)' on a null object reference
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2778)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2856)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at android.app.ActivityThread.-wrap11(Unknown Source:0)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1589)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at android.os.Looper.loop(Looper.java:164)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6494)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:440)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:807)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.Toolbar.setOnClickListener(android.view.View$OnClickListener)' on a null object reference
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at com.android.settings.SettingsActivity.onCreate(SettingsActivity.java:328)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7009)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at android.app.Activity.performCreate(Activity.java:7000)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1214)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2731)
06-17 22:37:52.908 6616 6616 E AndroidRuntime: ... 9 more
06-17 22:37:52.912 970 3058 W ActivityManager: Force finishing activity com.android.settings/.Settings
06-17 22:37:52.918 970 1042 I ActivityManager: Showing crash dialog for package com.android.settings u0
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
That's not a problem I will solve. That belongs to LineageOS or AOSP, can't tell since the log is that short.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ITenson:
Hey! Great call on Kernel Adiuter! Axon 7's vibration has always been one of my least favourite part of the phone and I have been leaving it turned off until now! Nice to have a phone with usable hepatic again!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
Last night I really did that nonsense! I've wiped everything, again! Then Installed only bootstack, modem, TWRP and lineage-15.1-20180609-UNOFFICIAL-axon7.zip. All from OP. No open gapps nor addonsu, magisk whatsoever. But guess what. It did NOT work! Still Echo in Call.

So I've restored my TWRP-backup, (un)tared my files to /sdcard (internal). Then wiped dalvik, system and cache and installed RR-O-v6.1.0-20180617-axon7-Weekly.zip, open_gapps-arm64-8.1-pico-20180608.zip and addonsu-15.1-arm64-signed.zip. This RR release works btw. with bootstack and modem from OP but one can also install A2017X_BootStack_O_B12.zip which contains modem selection for installing proper modem. There is no difference to Los 15.1 UNOFFICIAL, at least not for me because 'coz I use nova launcher. The only thing I had to replace were ui-sounds and bootanimation, which was easily extracted from lineage-15.1-20180609-UNOFFICIAL-axon7.zip. But most important it worked for me. No nasty Echo in Call anymore. :laugh:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
You went back to 14.1 to "fix" your issue? Good for you, but this is relevant how?

We aren't even 10 updates in and people constantly complain about the SAME, well known bugs. Subscribe to the thread, sit tight and come back when [MENTION=5027381]OrdenKrieger[/MENTION] pushes a new release, then see if it's fixed.

OR

Actually be helpful to the Dev, post debug logs if the bug is reproducible and contribute to getting it fixed that way.

On an somewhat related note: people should keep feature requests to themselves or actually take them where they belong; to the LOS team. It's pretty ****ty behaviour to ask for some obscure features you miss from whatever other ROM you're coming from. People are doing >>FREE<< work here after all, so there are no deadlines or goals to hit other than the ones they assign themselves.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
14.1? FYI it's based on 15.1. Check the screenshot. And according to [MENTION=5492451]NFound[/MENTION], he's got the sources from [MENTION=5027381]OrdenKrieger[/MENTION].

I did: https://xdaforums.com/showpost.php?p=76814030&postcount=309

And it ain't feature it's a bug. Why don't you read before you post?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haerwu:
nevermind
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
The echo bug is not only an OREO problem, it also exists in LOS 14.1 if you don't use B15 bootloader but B32 posted by DrakenFX, you will run into that problem too. Perhaps this helps finding the cause of this problem.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
As far as I remember I was never on B32. I've always used B15 with LOS 14.1 and never experienced the echo bug. Now I'm using B12, TWRP 3.2.1-8 Exclusive and RR-8.x: https://androidfilehost.com/?w=files&flid=250370. So I'm happy 'coz no echoing at all. However I'll test B15 with the next LOS 15.1 release.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] atakan33:
dont test B15 with LOS 15.1.You'll maybe break your phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
Thanx for the warning!. But what do you mean? Will B15 not boot into fastboot or into TWRP?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Netflix

I just followed the instructions on the OP and managed to get this working after only a few hiccups.

However, Netflix in the Play Store is listed as 'not compatible with your device'. What the heck?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haoyangw:
I'm not sure about fastboot, but it definitely won't boot into TWRP 3.2.1-8 by NFound or 3.2.1-0 by OrdenKrieger. Both of the above TWRP was built with B12 source code so anything other than a B12 Bootstack they will not boot. Please don't attempt! I've tried booting into TWRP 3.2.1-8 by NFound with B32 Bootstack and just got a black screen with 3 led flashes. I could boot into fastboot mode then but any fastboot command gives error 'command not recognised' so fastboot mode was useless
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
The latest variety of 'exclusive' TWRP revisions (-6, -7, -8 & - [more?]), coupled with the latest bootstacks (B12, B15) and the various revision levels of these custom and BETA Stock OEM ROMs (RR, LOS, AEX, -01, -15) are becoming quite the mix. It gets even more complicated depending from where one is upgrading from.

Is there a chart or spreadsheet available that lays out the acceptable combinations?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
WiFi Hotspot doesn't work

Looks like the WiFi Hotspot doesn't work. Devices connect but cannot resolve any hosts on the Internet. Strangely enough, USB tethering seems to work properly.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ITenson:
Hey, I just tested my WiFi Hotspot and it seems to be working with no problem.

A2017U model with June 10's build.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Wifi Hotspot

Interesting. I am also using an A2017U but with the 15-June build. Do you mean the 9-June build? I could try that to see if it makes a difference.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
Can anyone please check if echo is gone when using NFounds B12 bootloader and modem plus LOS15.1?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
Well I never had issues using fastboot yet (fastboot version 5943271ace17-android) from macos or linux. Don't ask me for windows. I don't even own a copy of it. If booting into TWRP breaks then I take the official TWRP https://dl.twrp.me/ailsa_ii/twrp-3.2.1-0-ailsa_ii.img.html and boot it by using fastboot.

fastboot boot recovery twrp-3.2.1-0-ailsa_ii.img

I also always use this one for wiping the phone before upgrading to LOS 15.1. Then I install twrp-3.2.1-6 and wipe it again. Finally I install twrp-3.2.1-8. Btw. I always use /ext4 filesystem for data and never encrypt.

Classification according to NFound https://xdaforums.com/axon-7/development/twrp-3-1-0-2-t3591075

- 3.2.1-6 for android 8.x (new bootstacks and supports decrypt partition /data)

- 3.2.1-7 for android 6.x, 7.x (old bootstacks)

- 3.2.1-8 for android 8.x (new bootstacks)

AFAIK the first one is inside B12 bootstack and the last one is some kind of upgrade to it. However I don't know if it supports decrypt partition /data.

No it's not gone. On LOS15.1 the there is an echo in call. In RR (LOS15.1 based) it is gone. Both with NFounds B12 bootloader.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Alex_Lema:
Sorry, I know that it's a dumb question, but I'm kinda insecure today, and the question just pops out of my head and didn't disappear...

If I install the latest build, I know that I have to reinstall Magisk, but do I need to reinstall Gapps if I am not wiping anything?

Thanks, and again, sorry.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
There are no dumb questions only dumb answers. AFAIK if you dirty flash from LOS 15.1 to LOS 15.1-new than you don't have to re-flash open-gapps, but of course you can do so. Just test it. If this won't work you can always boot into recovery again wipe dalvik, system, cash and then install clean the latest LOS 15.1, open-gapps and magisk. Your settings won't change, coz /data and /sdcard won't be touched. However I've never used magisk.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] pjones11:
Bluetooth track information

Much like the stock Nougat ROM, I'm having trouble with track information being sent to my car's stereo. Interestingly enough, the Oreo beta from ZTE actually worked...despite years of ZTE claiming it was a Google issue rather than their build.

So far, I've had virtually no other issues with this LineageOS build...bravo. I will have to try to adb she'll setting to get rid of the "corrupt system" message...very annoying.

Any suggestions to resolve the Bluetooth track issues or when it might be resolved, or information that I can provide to assist in resolving...it would be greatly appreciated.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] olus:
updating los15.1 to los15.1 no wiping needed. just dirty flash. no need to flash gapps or magisk again. they will "survive" dirty flashing because of scripts.

[MENTION=6056215]lichtblitz[/MENTION]

you dirty flashed from los15.1 to rr?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
I always wipe dalvik, system and cache even when updating LOS 15.1 to LOS 15.1 although it's not needed. Installing pico gapps and addonsu doesn't take much time so I do it anyway. Same for RR. I've wiped dalvik, system and cache and installed RR, pico gapps and addonsu.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sauerkraut17:
Actually......ZTE was correct by saying it was a Google issue as Google updated the BT profile for Android 7. While the new profile brought some benefits, it also had a severe drawback in that it caused many of car infotainment systems to no longer accept or read the BT metadata being sent. The reason some stock roms never had this issue is that they did not update to the newer BT profile. The lineage os team also found this out and reverted to the previous BT profile in mid to late 2017. Somewhere in the commits for LOS 14.1 you'll find it if you look.

So yeah, actually google's issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
[MENTION=5027381]OrdenKrieger[/MENTION]:

there seems to be 2 files at the wrong location.

/system/vendor/vendor/etc/audio_output_policy.conf and /system/vendor/vendor/etc/audio_effects.xml should reside in /system/vendor/etc/

Perhaps this fixes echo problem.

EDIT: okay sorry this was already fixed in last LOS build...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Wi-Fi hotspot / USB tethering not working

I just tried the 10-June build. Still doesn't work.

I also tried two different boot stacks (ZTE_A7LOSv1_UniversalBootStack.zip and ZTE_A7_UniversalBootStack.zip) still doesn't work.

I tried two different TWRPs (twrp-3.2.1-0-axon7.img and TWRP_3.2.1-8_axon7-Oreo.img) still doesn't work.

I tried changing the 'Preferred network type' to LTE, GSM/WCDMA/LTE, and Global) still doesn't work.

Well, at least now neither the USB tethering nor the WiFi hotspot works for me. This is incredibly frustrating. I need the WiFi Hotspot to work.

Which Bootstack, TWRP, and carrier are you using? I am on T-Mobile.

I noticed that I don't have an /etc/resolv.conf file on my phone. Is this normal?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ramonjp:
I have NFounds version since march and I can't reproduce echo issue.

Regards.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
ok guys I compared some files from NFounds RR with LOS 15.1 and it seems some of the audio configuration files differ.

If you extract the RR zip file there's a system folder, no need to extract the system.new.dat.

It would be worth trying to replace the following files from that folder with those on LOS 15.1:

/system/vendor/etc/audio_platform_info.xml

/system/vendor/etc/audio_policy_configuration.xml

/system/vendor/etc/mixer_paths.xml
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
You don't have to reflash gapps nor magisk if you are dirty flashing.

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

Was this from a dirty flash or clean install?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Wi-Fi hotspot / USB Tethering not working

It was originally from a clean (AFAIK) flash. I wiped System and Data. I suppose I could try a clean flash again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
Were these devices connected to the phone before?

Did you try forgetting them from the devices and try to reconnect?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Wi-Fi hotspot / USB tethering not working

Yes.

No. I am re-trying a 'clean' flash. If it still doesn't work. I will try that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
You can't install GApps after you started once. Either you install them with the rom at the same time or not, otherwise you will face that issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
Which bootloader are we suppose to install? When I go to the page, I can't find the exact one to download
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
In the OP is one AFH link which contains one bootloader zip "ZTE_A7_UniversalBootStack.zip" and 3 modems from which you choose the right one for your device.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
Ah, I must have gotten confused with the name showing as Bootstack. Thank you for the help

EDIT: Oh, I have one last question: Are these builds using the Oreo Blobs?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
Which TWRP should we use? For Oreo one or Nougat one from NFound?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Which ever you want, but there is one included in the bootloader zip.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
Looks like I seem to be in a pickle. I flashed them all and thought I could reboot it, then get back into recovery to do the adb reboot procedure since I can't get into TWRP now. I'm currently stuck at the red message and the device keeps rebooting. Anybody manage to get out of this situation?