yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
You could also just read the message and then short/once press the power button to continue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
Tried that and I managed to get into TWRP. I'll start over from scratch and let you know if my results yield some success.

EDIT: Looks like that did the trick. I was successful and it started to boot up with the Lineage Logo. I was wondering if this was a driver error or something, but it looks like Twrp 3.21-6 has an issue where half of the screen will look like static. Don't know if thats me or anything
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
You can also boot into the rom that way. That cmd that I posted earlier is only to remove that notification.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
Is f2fs format for cache supported/recommended?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
It's supported, but I'll always recommend ext4.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DarkQuark:
So far so good. What about Dolby? Is there support? Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Maybe, but not from my side.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
Flashed and everything is okay for now.

I was on B01 (Oreo Global).

Followed instructions on OP. Reboot and got red line.

Flashed command from cmd on TWRP and booted fine. Just need to format data.

Now everything is okay. Restored all apps.

Will try tomorrow and give feedback more.

HDR+ and Portrait mode on selfie camera is working good with Google Camera.

Subs doesnt working without reboot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DarkQuark:
I can confirm the Oreo Dolby from the b01 and b12 threads break los. So that one does not work for sure.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] trevor68:
Is there a root addon like 14.1, or just use supersu?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Yes. https://download.lineageos.org/extras
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
That's odd. Viper4Android seems to be working, but that doesn't
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] youngz89:
I have found an issue of the rom that I suppose it was not already reported.

Smart lock with trusted devices does not work. When I try to add a device, the system does not reveal anything.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Wi-Fi hotspot not working

Well, I did another 'clean' flash as well as forget any Wi-Fi info from devices that connect to my Axon 7.

Still, the Wi-Fi hotspot doesn't work. Devices connect and get assigned a 192.168.x.x IP address but they cannot get onto the Internet. Oh boy, this is frustrating.

Am I using the right modem for my A2017U? It's baseband is .2.0.1.c8-00030-M8996FAAAANAZM-1
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Try adding net.tethering.noprovisioning=true to your build.prop
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Wi-Fi hotspot not working

Thanks for the suggestion. It didn't fix it.

USB tethering works OK. My PC is assigned 192.168.42.#.

Wi-Fi hotspot doesn't work properly and I get assigned an address on a different subnet: 192.168.43.#

Is there a logcat capture I can run that might shed some light?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] apokolok:
Sorry to say, but Wi-Fi hotspot works fine here on 0809 build, using it right now.

It must be something specific to your phone / network setup.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
What exactly did you do after the clean flash? Is your data working? Are you using a VPN? Which carrier are you using for the data? Are the settings correct in the data settings?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Wi-Fi hotspot

I ran through the setup app, restoring apps from a previous cloud backup. I suppose I could try two more clean flashes, one without restoring apps and one without PicoGApps.

Yes. So is USB tethering and Bluetooth tethering. It's just the Wi-Fi hotspot, for some reason, that work.

No VPN. Using a T-Mobile plan that allows for tethering (which is probably why both USB and Bluetooth tethering work).

I checked the Access Points and the preferred network type. Both are what I have been using with Wi-Fi hotspot for many years.

I would like to have confirmed that I am using the right modem. I have baseband .2.01.c8-00030-M8996FAAAANAZM-1
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kleva94:
did you try it out?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
I didn't find time to switch to LOS 15.1, so no.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Wi-Fi hotspot

So far, I have tried:

Skip app restoration: Wi-Fi hotspot doesn't work

No GApps: Wi-Fi hotspot doesn't work

Wipe everything, including internal storage: Wi-Fi hotspot doesn't work

Try other release dates of of LineageOS: Wi-Fi hotspot doesn't work

Remove SD card: Wi-Fi hotspot doesn't work

Re-flash modem: Wi-Fi hotspot doesn't work

Try NFound's bootstack and recovery: Wi-Fi hotspot doesn't work

I am out of ideas.

I am in hell.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
[SOLVED: Wi-Fi hotspot]

My two-day journey to get the Wi-Fi hotspot working again after upgrading to LOS 15.1 has finally come to an end.

It started working again after installing [ROM][8.1.0_7.1.2]AospExtended ROM V5.6_V4.6 [OMS/DUI]. This involved installing yet another bootstack and the NFound TWRP recovery 3.2.1-8. One thing I did differently was to wipe the caches after installing GApps but I don't think this was the culprit because it was failing without any GApps on LOS15.1.

So now I have more hours of restoring everything that was wiped and such. At least I have a working system. It's too bad that I willl have to wait before going back to my preferred LOS. I have been using it since before it was even Cyanogen.

Anyway. Thanks for the suggestions. (I was close to buying a new SIM -- just to rule that out).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] josetann:
I've had a similar issue with wifi hotspot not working or working intermittently with two completely different carriers (Verizon in the US, Optus in Australia). Adding "dun" (no quotes) for APN type fixed the issue for me. Might be something to look into if you run into this again. Do note I haven't used this ROM in particular, I had the issue on stock.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] robertaramar:
First of all, thank you Ordenkrieger et. al. for doing all that work for us.

I am running the 06/15-build for some days now and there seems to be an issue with Google. First of all, it does NOT recognize "Ok Google" on any screen. It does understand my commands once I click on the microphone symbol, though.

Second, every now and then (sometimes never, sometimes three times a day) Google crashes.

Anybody else having that same or a similiar issue?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haoyangw:
Haven't tried Ok Google voice access but I also have occassional 'Google' FCs('Google has stopped'). Unfortunately I feel like it might be a LOS(ROM) bug though, not a device bug that our devs can fix but I might be wrong
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] apokolok:
Do you have 2017G?

I have .2.0.1.c8-00024-M8996FAAAANAZM-2

Maybe this would have been the quicker solution.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] :
APNs get lost

After restarting my APNs got lost twice. Didnt matter if I restartet hot or cold. Reflashing 0609 restored them...

Note: when the apns were gone I could not manually create a new one.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kleva94:
I don't know how to get these files. Could you ulpoad them? Then I'll ry it out.

---------- Post added at 01:06 PM ---------- Previous post was at 12:33 PM ----------

I found a solution for the Daydream Problem.

Basicly you just have to follow this guide: https://www.xda-developers.com/force-daydream-vr-compatibility/

But in build.prop you don't write "sailfish", but "ailsa_ii".

Now everything in Daydream works as intended, even with the up-to-date version. [MENTION=5027381]OrdenKrieger[/MENTION] is it possible to impliment it in a future build?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
That's not that hard to get them:

mkdir -p rr_test
cd rr_test
wget -c https://de1.androidfilehost.com/dl/3IMVaCZ2lScOADSYfpBAmw/1529810918/962339331459002172/RR-O-v6.1.0-20180620-axon7-Weekly.zip
unzip RR-O-v6.1.0-20180620-axon7-Weekly.zip
brotli --decompress system.new.dat.br
wget -c https://raw.githubusercontent.com/xpirt/sdat2img/master/sdat2img.py
python sdat2img.py system.transfer.list system.new.dat system.img
mv system.img system.zip
mv system system.org
unzip system.zip
cd system/vendor/etc/
ls |grep 'audio_platform_info\|audio_policy_configuration\|mixer_paths'
...
audio_platform_info.xml
audio_policy_configuration.xml
mixer_paths.xml
...

You need of course 'brotli' and 'python' installed.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kleva94:
doesn't work on windows. needed half an hour to install brotli and it stil doesn't work really and i am not sure how to translate all of the commands from unix.:eek:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
So I just wonder, how do you intent to replace those files in the read only /system/vendor/etc folder without knowing basic bash? Wouldn't be easier to backup /system and /data using TWRP and test RR for yourself? RR-O-v6.1.0 is basically the same as LOS15.1. Nevermind. Files attached :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kleva94:
No, dont't get me wrong. I understand everything except the python and brotli stuff (we had to use it in our pragamming courses in university :D ), but i had no idea how execute it in windows. Thanks a lot for the files.

Anyways, I could exchange the files with the Solid Explorer. After rebooting the system there seems to be no echo while calling.:good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haerwu:
[MENTION=5027381]OrdenKrieger[/MENTION] any plans for new build?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sirizak:
Judging from the fact you have 160 posts, you're not new here. But maybe you need it spelled out. Don't ask for ETA's.

There will be a new build, the developers haven't had this out for long, and the last release was seven days ago.

Be patient.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Victor13f:
Jesus why are you so sensitive? He didn't ask for an ETA. He just asked the developer if he had any plans for the new build..
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Cablespider:
It's a question that should never be asked. Of course more releases will follow. It's a given unless there is an indication it will be abandoned. It's just as bad as an ETA. Pestering the Devs ranks high on the don't list.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] izzyfanto:
By chance do you use Verizon on one of them?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] attilalovesfun:
I can confirm doing the same worked for me too. In call echo seems to be fixed :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
Thanks for testing. So OrdenKrieger can add those config files in his next build.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
[MENTION=5027381]OrdenKrieger[/MENTION]

It would be nice if you could take those files into account in the next build. Thanx in advance!

https://xdaforums.com/showpost.php?p=76877740&postcount=406
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
[MENTION=5027381]OrdenKrieger[/MENTION] please don't just use these files as is. Something in there fixed the echo in calls for me, yes, but it broke HiRes output or something with the internal audio processing. I ran "dumpsys media.audio_flinger" while playing back a .flac file with PowerAmp Beta 709.

Before the "fix":

"Sample rate: 192000 Hz" and "Processing format: 0x6 (AUDIO_FORMAT_PCM_24_BIT_PACKED)"

After the "fix", same file, same everything, one reboot:

"Sample rate: 48000 Hz" and "Processing format: 0x1 (AUDIO_FORMAT_PCM_16_BIT)"

Something messed up...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
Has anyone experienced a case where you're speaking with someone on a mobile call and the mic seems to shut off for a few seconds?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] h3ndrik:
Shouldn't be too hard to figure that out!? At least it makes the in-call volume adjustable on my phone.

Btw: Can I decrease the minimal in-call volume by editing one of those files? It's a bit too loud for me. (Had this problem also on 14.1)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Pruikki:
Hey!

Quick question!

-Can anyone do buildProp edit screen res to 4k, and see if youtube enables 4k playback?

thank you!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] twistedbox:
Here are some issues I am having:

1) NFC based my bank's tap to pay app is not working (Magisk passes safetynet checks)

2) Google app and some other apps randomly crash

3) If I set selinux to enforcing, bluetooth keeps crashing and fingerprint reader becomes unavailable.

4) When I am in a call, person on the other end of the phone call hears echo of their own voice.

5) When I encrypt my phone and try to boot into TWRP, the pincode/pattern does not work.

edit: looks like rooted phones are not supported by my bank's app, sorry should have checked first.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haoyangw:
Here are some suggestions

1) Perhaps you can try toggling on 'Magisk Hide' for your bank's app? It's a feature made just for apps like Android Pay and the like(you can even try hiding Magisk Manager under the settings of Magisk Manager)

3) Don't set SELinux to enforcing. If you have Magisk installed, it will already fool apps into thinking SELinux is enforcing even though it's permissive, so no need. As for why not enforcing, the SELinux framework has changed a lot since Android Nougat, so lots of SELinux policies need to be updated otherwise many of Android's functions won't work(because of permission denials, as Google tightened security once again). It will take a lot of effort to update SELinux policies, which is not worth it right now since as you can see, there are a few other bugs that are definitely more urgent. The additional security provided by SELinux can wait(if you want more security, just encrypt. And be careful what you download on your phone). So I'm afraid this won't be fixed anytime soon, and don't attempt it again

5) I'm not super sure what you mean by this, but I'll assume you mean you cannot enter your passcode to decrypt your data in TWRP. Perhaps you should try installing NFound's 3.2.1-8 TWRP? Heard it works fine with encryption done by B12

2) and 4) are known bugs so I shall not comment
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
If SELinux being set to enforcing isn't fixed anytime soon, though, that automatically means there won't be an official LineageOS 15.1 release anytime soon, either... which may well be the case, but I was kinda hoping that given the caliber of this unofficial one, it'd turn official soonish.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] twistedbox:
1) I just tried magisk hide with both paypal app and bank's app and it didn't work.

3) okay

5) yes that is what I mean, and I will try nfound version

2) and 4) thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] GodOfPsychos:
You mean "sys.display-size=3840x2160"

Yes it should work on literally every rom because YouTube app reads that entry and the Axon 7 supports the VP9 codec. Of course you gotta reboot after adding that line to build.prop manually.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] meter1060:
I had a 911 call go weird. I dialed 911 and it refused to connect or go to the call screen. It never showed up in my dialer log either. 911 services did get my call and eventually called me to confirm whether or not I was calling. [MENTION=5027381]OrdenKrieger[/MENTION]
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
Encryption is only physical security and does nothing to replace SELinux.

And fooling apps to think SELinux is enforcing sounds dumb. Why I would want to pretend to have it is silly.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Pruikki:
Yes, ut can anyone try it?

it would be a reason for me to Root and do the things to get TWRP AND such

CHeers! (i got stock axon on B9 G model)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BlackAfghan:
Yeah SELinux is the most important single security related feature, and has nothing to do with encryption. Please put that on top of your list!

No way it will ever become official without it, and 14.1 maybe will loose official status soon, due a number of other security related issues.

And please publish proper sources on Github, so that at least somebody else can look into it! #trust

---------- Post added at 07:17 PM ---------- Previous post was at 06:52 PM ----------

@OrdenKrieger can you please add speaker rotation support to your next build?

Please add to /system/vendor/etc/mixer_paths.xml (preferably after the "speaker"-entry):

<path name="speaker-reverse">
<ctl name="SLIM RX2 MUX" value="SB1_PB" />
<ctl name="SLIM RX1 MUX" value="SB1_PB" />
<ctl name="SLIM_0_RX Channels" value="Two" />
<ctl name="PORT2 Sync Domain" value="slimbus" /> <ctl name="SDTO2 Source Selector" value="SBI1" />
</path>

And to the build.prop:

ro.audio.monitorRotation=true
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Wolfblade1215:
I have this weird issue with my apn settings. Sometimes when I disconnect from WiFi my phone can't connect to lte. Every time this happens I have to switch my apn settings back to the Verizon one from the straight talk one. This has been happening for like a week. Something strange though is that I can't 'discard' the straight talk apn. Every time I tell it to discard it does nothing. No one else is reporting this but it never happened on any of my old Roms. I am running the latest 6/15 build.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] :
Actually I reported something similar. My apns get lost after restarts. Not always, but twice until now. After that I am unable to create and save my apn. The system just doesnt save a manually created apn. There is no error message. The only thing that helps is reflashing the rom.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
There are better ways to do this, i.e. with iYTBP, which has an option to override resolution checks. You also can see HDR video up to 720p60 (But the phone struggles a lot)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haoyangw:
Oh I meant that since some apps won't work with SELinux permissive(and hence won't work on this ROM), by hiding SELinux status you can use those apps again. I don't mean that this is supposed to improve security

You're right SELinux is a better security measure than encryption. But really it's super tedious(I speak from personal experience), especially if you want strict and truly secure SELinux. Device-related bugs have to be fixed first. Don't mean that security is not important, but a ROM would have better UX with less device-related bugs than with better security

Don't want to be mean but I don't think it's nice to ask for official status, as it's ultimately up to the devs to choose what they want. There are merits to official status, but it's very tedious and tiring because of the strict requirements nowadays(LOS raised their requirements). Unofficial status is more manageable because devs can work OTOT
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Pruikki:
Thank you! this is what i wanted! Thank you so much!

i got now 2160p :D on my 1440p screen,haha.

on my axon 7 , Cant see HDR anywhere but still, im am happy!

Thank you! downloaded YouTube Vanced 13.23.59
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
HDR wouldn't work anyways, since the panel isn't HDR capable.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
-UPDATE-​

Changelog

:

Remove stock acdb ids

Enable ZRAM https://source.android.com/devices/tech/debug/jank_jitter#page_cache

Disable MTP over functionfs (BUGBASH-1642; adding mass_storage to usb functions causes instant reboot)

LineageOS repo sync

DOWNLOAD
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
AFAIK HDR capability is not a black-and-white thing. Displays can be HDR certified but that doesn't necessarily mean that non-HDR displays can't display decent content. Of course common LCDs can't, but since we have AMOLED we have the low light level thing covered, and the maximum brightness is sort of okay for HDR. (We don't reach HDR10 but it's close enough)

The Pixel XL has the exact same panel as this phone and Google made a specific "software HDR" for it and the smaller Pixel. It's on iYTBP, and it works, though the phone wants to die at 720p60 since it's all processed by the CPU.

Most of that comes from the creators of iYTBP like KevinX8
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kaplah:
Greetings all,

Just installed this Thursday. My current big issue is that I cannot modify the Phone call volume. The phone comes through at max volume at all times. Volume up and down have no effect. This is true on speaker, handset, and headset modes. Is there any way to fix this issue?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sklaes:
I have got the same issue, but with the latest build I am able to adjust the call volume that reduces the echo.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] apokolok:
Phone call volume seems to be fixed in last build.

I just did a test call and was able to change in call volume.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
Just clean-flashed the latest build and I have double vibration on each press, what the hell?

And I also got the annoying boot warning about the device not being safe or whatever.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] imregy:
I confirm, It's fixed! :good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Hille2001:
i losed overview , which Bootloader or Bootstack for G Modell is to use which actual Update?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
With both latest LineageOS 15.1 and NFound's AEX (I was using an older AEX build from April or so), my phone is suffering from many random reboots. I have magisk 16.4 installed.

How can I track down the problem?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
On AEX, I have zero random reboots. Some questions:

Did you do clean install (full wipe)?

Did you follow install instructions to the letter? Eg in AEX there are detailed instructions as a link to a post (towards end of OP) [MENTION=8456254]EBeatFLA[/MENTION]. Did you follow those?

Are you switching between N and O?

Try the latest AEX. Figuring out why an old one does not work has little value add.

Please specify exact phone hardwsre (G/U/Chinese), bootstack, ROM version/date.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
Of course it was a clean install. I wiped system, both caches, internal storage and data. A2017G variant. And I followed all the instructions. ROM versions? I already said it, the latest builds up until today. And my previous ROM was also android 8.1 based.

Ok Google recognition not working either.