yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
FYI my aptx earbuds showed it was using aptX when they were connected so I think all is well

My known issues are:

I can no longer charge the device when powered off. As soon as I plug the power cord in my phone starts up. Kinda weird.

If I disable WiFi on a system app settings force closes. I mentioned it in an earlier post. Logcat appears to say it's a permission issue with ifconfig.

Example: disable WiFi for Default Print Service, email, gallery, Google partner setup, media storage, print recommendation service, etc.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mow4cash:
Can someone confirm if they have "Ok Google" voice activation working from any screen? I'm trying to narrow down the issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] attilalovesfun:
So decided to do a full wipe/reset and install the latest build to keep it 'clean'. Unfortunately it seems the in call volume issue causing the person on the other end to hear their voice echo'd persists. How do we go about providing the correct logs to capture this issue for the dev's?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
You may try an app like alogcat or run a specific adb command to extract the logcat and send it to Oden (CF OP).

Alternatively, don't use encryption.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] attilalovesfun:
I've read encrypted installs are causing the no sound issue. Is this also the case with the Dialer in call volume issue?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
Not sure. But I'd try to format as ext4 the /data partition if not already (or report their format) and be unencrypted for now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
[MENTION=5027381]OrdenKrieger[/MENTION]: in LOS 14.1 we had this /lib64/hw/lights.msm8996.so + /lib/hw/lights.msm8996.so

to switch to low persistence mode. This library seems to be completeley missing in LOS 15.1 and I'm sure it's the reason why daydream mode won't work as in 14.1.

Can you please add the version from last Oreo beta into your build?

BTW is there a repository with the binary blobs or is that stuff all local on your environment? Can't find that stuff on TheMuppets. repo
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] attilalovesfun:
How do you change to unencrypted? Or are you saying by partitioning the data partition as ext4 it will install as unencrypted?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haoyangw:
Oh this is probably because SELinux is permissive so this ROM doesn't pass SafetyNet. To fix this try installing Magisk(16.0 or 16.4 should both be fine), it should make the ROM pass SafetyNet. But make sure that you don't install Xposed
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Druboo666:
[MENTION=5027381]OrdenKrieger[/MENTION]

are you going to release the device and vendor tree??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
I will take a look at this. We still build the lights HAL but the binderized O HAL. Maybe I can kang the vr HAL from some Google device which works with the binderized light HAL. It's always hard since that also requires a custom thermal HAL which didn't work well in the past. That will be some work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Raffelberger:
how did you get into twrp again?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] h3ndrik:
you're at the new o bootloader prompt?

choose "recovery" by hitting the one volume button that works

press power. bootloader will restart and give you the same prompt as before.

don't choose recovery again. just press power

i hope this will get fixed. took me some time to get into twrp the first time.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TPMJB:
Hey [MENTION=5027381]OrdenKrieger[/MENTION], any chance you could provide the speaker fix as a standalone zip? I like LOS, but LOS-based roms currently provide a few more features that I use day-to-day. Would be cool if I could use these and also have speaker functionality.

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Raffelberger:
This did the job, thanks a lot
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] GodOfPsychos:
Lol all those thumbs up. I don't get it. Is this a hint or something?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Black_Rose999:
It's just recognized developer
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Jealous? No sir lol I'm just subscribing myself trying to catch up on things I just came back from a 21st birthday vacation. I do want to wait around and see what all issues people find that we couldn't. To be fair about battery life etc we didn't get the latest and greatest Oreo kernel source I received a bad beta with horrible overheating and battery life. I decompiled the dtb (device tree blob) from the prebuilt B12 kernel and that helped a lot as you can see no one hand is burning which is what I experienced before. Hopefully we can get everything solved and worked out eventually. I'm basically handing everything over to OP I'll continue to contribute though so I'll probably be getting back in touch with everyone on Hangouts soon to see if I can get some of the small necessary things out of the way like SELinux, offline charging mode, and the flip cover. At this point there's no reason to report anything previously reported, I've read every single comment and page just be patient
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] J0nhy:
Hey not trying to bother but am i the only one who cannot hear anything when i receive a call? Everytime i have to hang up and return the call so i was wondering if that's a known bug if it is is there a way to fix it? Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
Okay I see there have been some changes starting LOS 15.1.

It seems for our device the switch of the /sys/class/graphics/fb0/msm_fb_persist_mode is missing. The new kernel sources you provide already create this file. In the old nougat kernel source it was done via ioctl.

I think you could kang it from here https://review.lineageos.org/#/c/LineageOS/android_device_xiaomi_msm8996-common/+/203384/

I'm sure latency should be much better.

About thermal hal, this commit sounds interesting for me:

https://review.lineageos.org/#/c/LineageOS/android_device_leeco_msm8996-common/+/212464/

don't know why they called the file vr-8998.c

Edit: ok there's a bug in the commit: in vr/Android.mk he also asks for 8998:

ifeq ($(call is-board-platform-in-list,msm8998), true)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] s0be:
If you can reliably reproduce audio bugs, this will catch the logs to help the developers solve them:

adb logcat --pid=$(adb shell pidof android.hardware.audio@2.0-service)

Without logs, no fixes can happen. Helpful details: How the call was received(volte, voip, H+, cdma, etc), whether you were using a headset or using the phone as a handset, were you connected to wifi at the time, etc. Logs after the fact are useless, the logs need to start from before the problem happened, and last until after.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
I've had some overheating issues. Device wouldn't boot up until I reflashed everything or maybe it just needed time to cool down :/
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xoroi:
Hi again! The only issue I have right now is the loud in-call volume of the speaker during a call. I can't lower the volume and all the people around me are staring at me as if I was a bit deaf. Lol!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
That's a known issue. We will try to fix this asap.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Liquid5n0w:
I went and flashed that module from the post and it fixed daydream for me. Would your version make any difference?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
What do you mean by "it fixed Daydream"? Daydream does work for me, at least with the module changing the device codename. Low-persistence screen mode (without which, the Daydream experience is distinctly subpar) is what doesn't work.

I see developers in posts above are discussing the lack of a low-persistence toggling API in the Oreo version of things, so I assume just tweaking some build.prop options can't enable this.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Liquid5n0w:
Sorry, I meant that I was getting the DPI issue with the distortion, but with the magisk module it fixed the DPI issue. The low persistence is definitely a more serious problem, but I am hopeful they can fix it!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
has anyone noticed the new color profiles option under Display > Live Display? I guess I like the 6400k ones.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Oh, right. Well, my version would probably make no difference to Daydream, it's just that I thought changing the codenames to the stock Axon 7 ones, rather than to ones belonging to an entirely different phone model, was less likely to result in side-effects unrelated to Daydream (you know, other apps or Play or things thinking I'm using an entirely different phone and acting accordingly).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
I just noticed something interesting. I have the sound hound widget on my home screen, it claims "unable to use microphone". If I go into the app, it's fine. Shazam is fine. Can anyone else test this? View attachment 4525228
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] atakan33:
maybe ungranted permission ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
No, it's granted, hence why they work when I open the apps. I also realised that when I wanted to record an voice note on Telegram, it didn't work either, the counter stayed at 0:00
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] soleen:
What is the process of getting the official lineageos 15.1 support? So we could get over air updates?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Liquid5n0w:
Yes please share it, because now my phone shows up as ZTE Pixel 2 XL.

There are others who would want it as well I suspect.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
Purpose, not process.

OTA updates would be the most insignificant reason.

It also implies our hardware is getting active support by a device maintainer. (I mean, it is right now but a year from now is a different story.)

SELinux would have to be enforcing which it currently isn't yet.

To be official, LineageOS encourages developers keep up with patching the device tree and kernel for security updates. If it's not looking like a device is getting maintenance on CVE's the project will remove it from their list of supported devices.

Also, people who submit code to the actual project have to sign a Contributor's Agreement which probably includes phrasing on not inserting malicious code or something.

And patches to the official repos have more eyes on them and there's more approval process for changes.

And finally, with all of that said, the maintainer doesn't have to manage building and deploying to us because the official build servers handle it.

OTA updates is just a consequence of the above things. Personally, I don't even use the built-in updater because I like to keep my latest installer zip on an external sdcard.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Liquid5n0w:
My understanding is that LingeageOS changed the build policy to require the maintainer to build it and upload to the official repo on the weekly build date.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Well okay, but I've changed it a number of times and I have no guarantees it sports the most appropriate codenames and signatures and all that... especially not for 15.1, given it was made for 14.1. Also, it works for me with Magisk 16, I don't think it will work with the 16.4 beta.

Anyway, the version I think I've been using most recently is attached.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Uh.... thereby removing any hard guarantee from the LineageOS team at large (especially their build server managers) that what's uploaded corresponds to the sources provided?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] h3ndrik:
No. I believe they are built by jenkins.lineageos.org you can watch the status at: https://www.lineageoslog.com/build (at least the weekly builds)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] robertaramar:
Hi, I did a fresh install yesterday. Wiped everything and installed the 06/09 build and gapps arm64 mini.

At the very first screen an overlay states that Google has crashed.

In addition, I cannot log in with my Google ID. Although providing correct credentials, the wizard always starts newly at the "This device was wiped and an ID must be provided that was once used on this device" screen.

Anyone having a hint how to overcome this?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gregfrankenstein:
I'm fairly certain that wiping data would leave the partition encrypted and you would have to format /data to decrypt it entirely.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TPMJB:
It depends. If you decrypt it first, yes it remains encrypted. If you don't decrypt it and wipe, it clears everything.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
For my Axon7 A2017G I've installed:

- ZTE_A7_UniversalBootStack.zip

- A2017G_OreoModem.zip

- TWRP_3.2.1-6_axon7-only_official_oreo.img

- lineage-15.1-20180609-UNOFFICIAL-axon7.zip

- open_gapps-arm64-8.1-pico-20180608.zip

- addonsu-15.1-arm64-signed.zip

- all my Apps from PlayStore. No further patches or system hacks whatsoever.

and in that order.

Beside a nasty echo on the other side during a call (tested with all three here: Vodafone Germany, O2 Germany, Telekom Germany) is everything as supposed to be, even bluetooth. Axon7 connects perfectly to my VW car radio. I can navigate and play music, make calls using car wheel buttons and even sync contacts with images. Just perfect! Nice work guys! Vielen Dank OrdenKrieger!

So concerning the "echo" effect. It only happens on GSM and LTE calls. WhatsApp and Telegram calls are not affected. It doesn't matter whether wifi is on or off. Only the other side of the call is affected. The echo effect stops only when I mute the micro of Axon 7 on my side of the call.

Log attached

thx
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
[MENTION=6056215]lichtblitz[/MENTION]: Nfound already fixed this issue in his roms.

I wonder why vendor + proprietary tree is still closed source on all axon7 Oreo roms
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xoroi:
Have you tried using the Google unlock option in TWRP. Once you are in the TWRP recovery, go to Advanced > More... > Unlock > Google. You can also try with Lockscreen. I don't know which one I used but it worked in my case.

;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Arbelzapf:
I can confirm the issue with echo in calls
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Liquid5n0w:
You should post that here, and maybe PM the OP to add it.

https://xdaforums.com/axon-7/themes/extras-add-ons-lineageos-15-1-t3800443
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
are many still having mic problems?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aionsmith:
I still have mic problems
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Killerdog:
Hi,

i follow the steps in OP to flash Lineage 15.1 over the Stock Oreo B01 and now my phone doesn't boot.

i can boot in fastboot and flash again the recovery, but it don't boot into recovery after.

when i try to go to EDL mode my device don't appear as Qualcomm EDL but ZTE Handset Diagnostic Interface(DFU) (COM3), and it's not visible with miflash or Axon7_EDL_Tool.

I try to reboot and surprise, lineage boot and i can setup it. I reboot to finish configuration and now it's block again with Red g.co/ABH and shutoff after 30seconds.

Did someone have a solution for me please.

EDIT : i found a way to boot, just press power key when i see this red message, i see a linux pinguin and it boot after, but how to revert this ?

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Pastinakel:
Either press the power button when g.co/ABH turns red or follow instructions in second post of this thread. My data wasn't wiped, your mileage may vary.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrGit:
Of course the blobs are still closed source, even if the devs were to upload them to GitHub, which is what I assume you meant. If you really want to compile form source, you can always pull the blobs from the Oreo build in the meantime. I would like the devs to release sources for the device tree too, but I presume they have reasons to delay making that source public - possibly because of a request from ZTE or something. For what it's worth, the Apache license, which Android uses for nearly everything except the Linux kernel, does not require modifications to be distributed in source form, unlike the GPL. So technically, the devs are not violating the license by not releasing the Android vendor sources. I do wonder whether the kernel sources linked in the OP actually correspond to what is in the latest build though - if not, that is a violation of the GPL.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] pezdev90:
I had similar issue after trying hellgate kernel, i uninstalled ZTE handset driver, reinstalled qualcomm and just connected again, it eventually booted into recovery and I reflashed this rom and modem, and no data wipe occurred.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
Read op. There is a solution
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] FunkyRasta:
Does LDAC work on our device though? Since it was pushed to AOSP? Or we still need special blobs? Asking before I buy Shanling M0 DAP
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
Would it be possible to make the bluetooth out a little louder?

I have to turn up and down my car audio system when I am making handsfree calls.

The Google Assistant would be load enough on level 32 then, I'd have to raise the volume up to like 42-45.

If I plan to use GA again, I'd have to quickly turn down the volume to 32 again as it will be very loud.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] beastobadness:
I am on AEX atm...was going to go to LOS but I needed the customisations. LDAC working perfectly for me...actually sitting with my 1000XM2's on right now using LDAC. Would imagine if LDAC works on AEX, I am sure it will on LOS also
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Killerdog:
Thanks, my bad i don't see the second post :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
On LOS 15.1 LDAC does show up alongside aptX in the developer settings, I don't have a device that supports it tho, so I can't test functionality.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xoroi:
I don't know if it has to do with the audio bug, but whenever I record a video, the recorded sound comes and goes. And then, when I try to open the video with Google Fotos, the app exits or gives an error. Maybe it's everything connected?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
Fwiw I also saw a screenshot on Reddit that you also see something indicating a choice to use LDAC on an LDAC-capable device if you click the cog wheel for that connected device. These were screenshots from a Galaxy S8, though, so that may not actually be stock Oreo configurable in that spot as well.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] greyhamism:
While we're on the audio front, wondering if anyone has had success with playing back "Hi-Res" audio files back at their native rates?

I'm running the B01 Beta atm and loving it, but its been pointed out that regardless of playback configuration (Neutron HighRes Enabled/PowerAmp Direct mode/Stock Player/UAPP) files are downsampled/truncated to 16bit/48khz.

Running the following in a terminal window while playing back said hires files should inform you what sample/bit rate files are being played back at

su
dumpsys media.audio_flinger
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ssirK:
hi all,

i want to flash 15.1 , coming from 14.1 on my G variant

im on first step, i update twrp from OP, but i cant reboot to twrp, i have the orange blinking twice and it shutdowns

i tried the adb reboot "dm-verity enforcing" and reflashing twrp, but no luck.

any idea ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
-UPDATE-​

Changelog

:

Revert thermal changes from O [test]

Fix a path issue where 2 audio configs wouldn't be stored in the right place

Kernel updated to LA.UM.6.6.r1-08900-89xx.0

LineageOS repo sync

DOWNLOAD
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
This build would have been already up yesterday, if AFH wouldn't be down all the time.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Install TWRP from here https://twrp.me/zte/zteaxon7.html and then flash the O bootstack. After that you can update your TWRP with that from the OP.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
[MENTION=5027381]OrdenKrieger[/MENTION]: Thanx for that, but are you still onto micro/echo problem? Not only this release didn't fixed it, it's even worse. The echoing got stronger. :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
After the update today PowerAmp lets me enable Direct HD HiRes Output from within it's settings.

I also did a dumpsys while playing back music, but I don't know what to look for in the resulting command line output... And the output is too long to fit the terminal window so I suspect it cuts off some critical info.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] greyhamism:
The info you need can be found with a search for the "standby=no" part of the log, to see the settings in the active channel.

For example, last run I did whilst playing a 24bit 96khz file in Neutron & UAPP with HiRes drivers used returned this (as well as a large amount of other information, you have to dig through to find the "standby=no" section) :

Output thread 0xe4783400, name AudioOut_D, tid 1689, type 0 (MIXER):
I/O handle: 13
Standby: no
Sample rate: 48000 Hz
HAL frame count: 1920
HAL format: 0x1 (AUDIO_FORMAT_PCM_16_BIT)
HAL buffer size: 7680 bytes
Channel count: 2
Channel mask: 0x00000003 (front-left, front-right)
Processing format: 0x1 (AUDIO_FORMAT_PCM_16_BIT)
Processing frame size: 4 bytes
Pending config events: none
Output device: 0x8 (AUDIO_DEVICE_OUT_WIRED_HEADPHONE)
Input device: 0 (AUDIO_DEVICE_NONE)
Audio source: 0 (default)

Which shows that despite the sample rate/bit depth that both Neutron & UAPP where reporting they where playing back at, audio was being delivered in a downsampled & truncated 48khz 16bit format.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
Here's the dumpsys from during PowerAmp playback:

Downloaded a .flac sample from some Sony website just to make 100% sure my files aren't the problem. This looks promising to my amateur eyes ... :p
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nodea:
To much static and echo in call. Not good at all. Is it a modem or other problem? Does echo occurs only on A2017G?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] greyhamism:
Hey hey hey, this does indeed look very promising :D