yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ls117:
I'm glad people here clarified things, if removing that message means bricking my phone I can live with the message. Have no intention of locking the bootloader and safely reverting to stock either.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Diceroll:
Will I brick if I try to flash the b32 bootstack and the stock system by DrakenFX after being on Lineage OS?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
"OK Google" with screen off. Is it possible on the Axon 7 ? It doesn't work even when it's charging.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
No. Well, if you're wanting to stay on LineageOS you'll just flash the bootstack unless you're going back to stock.

But each time you want to install a LineageOS update you'll have to edit the zip file to change one line in the updater script. It does a check to make sure you're on the prior bootstack so you'd have to have it allow the newer version. I've posted on what to change in the thread.

I was doing this for a few months but decided to switch back to the version in the OP.

Eventually, the B32 bootstack should be required for LineageOS but I don't know when that will be.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Diceroll:
So this is fine to go to stock rooted. But if I want to go to Lineage I need to be on a different Bootstack?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
You need the one in the first post of this thread. I think it's the B15 version. If you are on the B32 bootstack you'd either need to downgrade or edit the LineageOS zip file to change the updater script to accept the newer B32 trustzone version. Otherwise, you'll just get an error code when you try to install LineageOS as it does a check to make sure you're on a recent baseband.

instructions are here https://xdaforums.com/showpost.php?p=72219295&postcount=2517
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Diceroll:
Is the 00325 still correct, or would that be different now?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
It's the same. The trustzone version didn't change between B25 and B32.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Ficus*:
each time i connect my phone to the pc, i cannot see the phone's content in windows explorer. to show it, i have to disable usb debugging, re enable it, and select MTP instead of charging. is there a way to set the behaviour default to MTP without having to go through all these steps each time?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
That would be a risk. Imagine someone steals your phone and manages to connect it to his computer and see all the contents of your phone...

It could be a good idea if the option was enabled as long as the phone is unlocked.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] williamthardy:
On Lineage OS once the phone is unlocked it remains unlocked. It's been a long time-is stock the same?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
On LineageOS It stays unlocked if you're using smart lock (trusted devices like bluetooth ones). But if you're only using fingerprint or pin code then no.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] williamthardy:
Thanks-I don't recall setting trusted place-but that was my problem.

---------- Post added at 07:47 PM ---------- Previous post was at 07:25 PM ----------

Thanks-somehow trusted places was set.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Ficus*:
Yeah, I can understand what you are saying, but I would like to decide whether take this risk or not.

For example, I don't use a pin/pattern/fingerprint lockscreen, because I don't want the hassle each time I turn on the screen. And thankfully I can choose not to have any kind of lockscreen. however, I cannot choose to set MTP connection as a default? so i have a completely open phone, but cannot save the MTP connection?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amaury48:
My A2017U was running on Drakenfx stock B32 w/ Magisk 14.0...decided to try LOS. Did the following:

1. Wiped system, data, dalvik, and cache

2. flashed the B15 universal bootstack (from los link)

3. flashed A2017U modem (from los link)

4. flashed 11/20 official build LOS

5. flashed recommended Gapps (from los link)

6. flashed Magisk 14.0

Booted into a screen which required my to enter a pin # before starting Android. I entered the pin I used on Drakenfx previously. Got a Starting Android screen followed by the los arc and moving circle....sits there for 5 mins, then justs shuts down....!!

Any help would be appreciated......
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] SilentEYE:
[MENTION=2166949]amaury48[/MENTION]

Start again with wiping data, system, cache.

After point 2.

Install latest twrp manager 3.1.1

(choose 'install image' to select the twrp.img file)

Reboot into recovery (to boot into latest twrp)

Continue with the other steps.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amaury48:
I will give that a try later today and report back....thx for the reply
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kallen:
LED Notifications

How much control do we have over the LED notification lights?

I searched on LIGHT and got to the LED Notification settings. I can't seem to set the color (red/green/orange). I can only set the blink rate.

I can change blink rate for phone and for voice mail, but not for email or text.

There's a section heading for "apps" but nothing underneath it.

Am I missing something?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] emepher:
I also went from a stock build from DrakenFX to Lineage, and I stumbled at first. I was sure I did everything right, and it turned out that I needed to flash a newer version of TWRP. I'd never had a problem with a less-than-latest TWRP before, on any device, so it didn't even occur to me to check for a new version.

I've always left TWRP alone once I got it working, which was a problem this time. After flashing the latest TWRP everything went just fine.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Knuxyl:
Does this rom have the same driver and libraries for the audio device? ie dolby atmos and all the features that stock has?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amaury48:
I tried that.....TWRP 3.1.1 Flashed after wiping and flashing the B15 bootstack and had the same results (not completely booting)....and took me 4 hours to get back to Drakenfx B32. Had a heck of a time getting back to square 1.... followed instructions to the T, but still could not get it to boot up completely...let it sit over night.... don't understand why....never had this problem before. Been flashing custom ROMs from day 1....After this experience, just going to sit on Drakenfx till Oreo drops.....
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
Same thing happened to me. I ended up on Drakenfx b32 as well. It was very frustrating. I originally was on stock and got to Los easily. I started having problems going to other rooms. I couldn't get back to Los and eventually settled here until Oreo.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Teet1:
All your problems and symptoms i had a while ago...happened when i went to stock and my system was encrypted. I flashed CandyRom and i could NOT leave that enter pin to start android screen. Fortunately, the default encryption password in TWRP worked. It was 11111, but did not work for Android, so I was able to move my internal storage out and then wipe internal storage and /data to ext4. It was set to F2FS. Doing so removed encryption and was able to flash custom ROMS with no problem again
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amaury48:
Yeah, I guess I could have gotten a logcat to see where it was going wrong, but got so frustrated then got hung up just trying to get a workable phone....
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Rcmz:
Is there any way to disable the fingerprint vibration?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Ficus*:
my status bar is white, which is fine with drawer and lock screen, as they are both dark, but not with desktop, as it is white. is it possible somehow to set a different color for the status bar only when i'm displaying the desktop? i checked in the options but i couldn't find anything useful
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] thafath:
Thank you for the explanation.

Concerning trust/security/spyware-less how do you compare devices from zte or others with devices from big names samsung/htc/lg when both run the exact same los version, and have same cpu (Qualcomm snapdragon 820 for example). Thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Meenaombo:
Can I get back to stock from this rom or will I brick my phone ?? Iam A2017G
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
If both a ZTE device and a Samsung are running LineageOS, you've stripped out all differences between a ZTE and a Samsung. The only security issues would be dependent on each device's LineageOS maintainers keeping device-dependent code up-to-date.

If there is a vulnerability in Android, both devices receive the fix. But if the vulnerability is in a driver or kernel, each device's maintainers would have to patch their device tree.

That's why [MENTION=4126377]tdm[/MENTION] was bouncing around on a few different phones' device trees a few months ago and patching like a madman. It's pretty awesome to have that sort've love.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] atakan33:
İs this rom has a random reboot problem?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] williamthardy:
I update every week and have never had a problem.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] atakan33:
so good thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] arecad:
I think your mileage may vary. I have random reboots (warm reboots) with this rom. Sometimes twice a day, sometimes once every 2-3 days. I have been spending months trying to figure out what is causing it but still don't know. It could be an app but I have yet to figure out which one. Never happened on stock with the same apps.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Motogeek:
I get the odd warm reboot. Background changes to the default. Its pretty random, I haven't found any causes. I use action launcher, it may be that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celticchrys:
I have the same problem, on Nova Launcher, disappearing wallpaper and all.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] arecad:
Same thing with the wallpaper reverting back to default as well.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hboa:
I'm experiencing the same exact problem. Often happens at night, when charging. Would be nice with a fix, if it is widespread.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Diceroll:
Same here. Back to stock wallpaper on Pixel Launcher
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xperiaatic:
i have experienced random reboots too and there is no obvious pattern or activity that causes it. sometimes the phone just lays on the table screen turned off and reboots.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Vurio:
Speaking of random reboots. My phone would just turn off and refuse to turn back on after the ZTE logo (flashing orange led). Only a fresh clean installation through TWRP would get my phone to start back again.

It happened a few times within a couple of months but for the last couple of months it's been running beautifully. It did get me in the habit of regularly backing up. :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
This happens on the stock ROM with superSU with me ever so often.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hboa:
Are there any log-files being written in the system, where one could see which app or process that's causing these soft-boots?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] wannaskoo:
I'm using Lineage along with BeastMode and didn't have any reboot, maybe the problem is kernel-related (dunno) as some time ago i tried some unstable kernels that made my phone reboot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] SilentEYE:
I am also having problems with random reboots.

Tried to switch to llama kernel and there are the same problems.

Therefore I did an extended log, hoping [MENTION=4911249]Unjustified Dev[/MENTION] or some other user has the time to look into this.

I also have the problems on other cm based roms. Therefore a possible fix will help a lot of custom rom users.

Just one strange thing: I

have the feeling, that there could be a problem with the battery. The RR happened really often between 40 and 45 percent battery percentage. Even 3 minutes ago the RR appeared at 40% again. It's just a thing I could find out. This could be important if no one can find the bug inside the logs.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ssirK:
No random reboots, using default kernel, launcher and few apps
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] williamthardy:
FWIW-No random reboots ever-Lineage with native Trebuchet launcher all Lineage apps replaced by GApps
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Drwankingstein:
my Issues with LOS

Whenever I try to update my Os from the settings page, it almost never works, then I have to go download the new firmware and manually update

EDIT: Also I am running magisk but for some reason even busybox fails to mount system as rw
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] SilentEYE:
@ ssirK Do you use magisk?

I am using it. Error happened on versions v14 / 14.3 / 14.4 / 14.5

@ williamthardy

I am using Nova launcher. The error happened mostly while watching videos or while pluged in. Even when the device is doing nothing the error occurs.

Generally, i have the feeling, that there could be a problem with the battery. The RR happened really often between 40 and 45 percent battery percentage. Even 3 minutes ago the RR appeared at 40% again. It's just a thing I could find out. This could be important if no one can find the bug inside the logs. ( I add this to my Log post too)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ssirK:
No magisk or superSU, i use original LOS root addon
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] arecad:
Is anyone that is having the random warm reboots not using Nova Launcher? I uninstalled mine to see if it could be the problem.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Motogeek:
Using Action launcher here. I have them
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hboa:
I use Nova. Does uninstalling stop reboots?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ileikpi:
I get warm reboots too using the pixel launcher so I doubt the launchers have anything to do with the reboots.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
I had random reboots on the last 2 builds, I'm not having reboots on the latest one though. Nova launcher here.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ssirK:
which root addons do you rebooters have ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] arecad:
Yup, confirmed it isn't Nova. had a reboot this am.

As for root addons:

Running Magisk 14:

w/ Greenify module

w/ Adaway module

w/ Busybox module

w/ Google Assistant enabler module
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] robertaramar:
I have no root, standard launcher and I'm experiencing reboots every now and then. My observation is, that it usually happens, when I put the phone into my shirt's pocket.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] SilentEYE:
Let's do some productive steps and create logs.

Here is the tutorial for you all.

1. Install and open once Kernel Adiutor, give it root permissions.

AFTER AN UNWANTED REBOOT

2. Go into settings and look for the debugging section

3. Click on logcat, last kernel message and driver message.

4. On your root directory of your sd card you can now find the 3 files: logcat, last_kmsg, dmesg

5. Create a zip and upload it here or upload the files on pastebin.com
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hboa:
Here's my log-files
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] youroddness:
Excellent tool kit
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] rogersa2k:
Sorry for this somewhat random question but what's the status of Daydream VR and the latest Lineage OS builds for this phone? I have never used Daydream but I'd like to upgrade from Cardboard to it this Xmas for my kids. The last search result in this thread was from almost 2 months ago and I'd hate to buy one of these phones if there are major issues.

Thanks!

- Aaron
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Infy_AsiX:
I just tried the difference with Daydream VR on stock. Most apps that use some graphics processing suffer stuttering visuals, practically unusable. Dual booting stock for VR is the only viable workaround.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nonamesl:
<3 Love you. It would be great if you added step by step instructions for each model.

The FAQ are missing the famous error 7. For example, it happened on the A2017G because you didn't install the A2017X universal bootstack before you tried to install lineage. It could also happen because of your TWRP version.

Question: What are the model specific modems for?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ibphantom:
So I've been having this issue for a while... While watching a video(or about to watch a video), my phone gets REALLY slow. Sometime the force close app is able to pop up and I can force it closed with that or just holding back(my hotkey for killing an app). I've noticed this happens mostly with Snapchat and Facebook while my phone is on charge The worst is when the whole phone freezes and I have to suffocate it with a 15second press of the power button, but other times I can be in the middle of watching something and my phone auto soft-reboots. This error happens every once and a while. Maybe twice a week. What can I do to catch the process in charge of this error because it's gotten quite annoying?

I currently run 14.1-20171211 build with BeastMode v88 Kernel. This has happened on both the stock and a 3rd party kernel as well.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
After you flash the universal bootloader you have to flash TWRP 3.1.1-0 again (have the .img around, then after you flash the universal bootloader press Install Image, select TWRP, select install to Recovery, install). Or you'll get an old TWRP that works like utter crap.

You have to flash the modem specific for your phone in order to have signal. The 3 phones have different NHLOS.bin, and they couldn't have bundled the modem files with the ROM because after flashing the universal bootloader your phone sort of becomes an A2017U. ofc the hardware does not.

The method to install this is the same for all 3 models, the only thing that changes is which modem file to use xd

---------- Post added at 04:44 AM ---------- Previous post was at 04:42 AM ----------

Try Kernel Adiutor, do the same that [MENTION=899471]SilentEYE[/MENTION] said on the previous page
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ShiverStorm:
Is 3.1.1-0 the most recent stable twrp for axon 7? There is a 3.2.1 out now. Would you recommend using one over the other?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] joaste:
I'm using 3.2.1 now without any issues. I'm not sure there is much that has changed. You can still use 3.1.1 without issue I think.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
3.2.0 had a reported backup restore issue that just didn't let you restore a backup. Don't know about 3.2.1 but it may have the same problem.

Anyways 3.2 is made for better compatibility with Oreo ROMs so it doesn't make much sense to use it now
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ShiverStorm:
This is what I was looking for, thank you!!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] atakan33:
How to fix android starting pin disable ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Knuxyl:
Bug

When calling someone or receiving a call, when you or them pick up the phone, it switches to speakerphone and phone doesn't say it is on speakerphone. I have to turn speakerphone On, then back Off for it to switch back to regular call speaker. I have not flashed any audio mods or anything of the sort.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] SilentEYE:
You mean probably the wrong system format. Check in twrp if you system partition is formatted to f2fs. Change it to ext4
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nonamesl:
OHHH! That explains so much. I wish there were step by step instructions that say this (or atleast an explanation on what to do lol).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
It's pretty damn straightforward. You have an A2017G, flash the universal bootloader, then the A2017G modem...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] SilentEYE:
Just wanted to inform you all, that I started investigating into the reboot problems.

Probably I already found a solution.

Reboot Bug Thread
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BlackAfghan:
This is not a problem of the ROM! As you already found out, it is caused by Magisk..

I've never had a random reboot in 9 months!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] SilentEYE:
I didn't said that it has something to do with the ROM, did I?

Most of us were using magisk. I used it due to open source magisk project. No one could found the reason for the reboot problem.

Glad that you didn't have any problems yet.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BlackAfghan:
I wrote that because, in your thread you said that no dev has found the time to investigate it. That sounded a bit like a complain to me.. ;)

But I wasn't referring to you especially! Rather to all the other posts here recently. You should post magisk bugs in the magisk forum, and not here..

The devs here are probably busy porting LOS15, and demanding fixes for other projects is very rude! But no offense.. :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] SilentEYE:
[MENTION=411194]BlackAfghan[/MENTION]

I didn't mean to complain. I don't do this kind of things.

I said "found no time" especially because I don't see the DEVs to be forced to look into our problems.

My post is still WIP and a side note to all the users here, having reboot problems. This will help others by using the mighty search button.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] effie.tardif:
random audio increases of 100%

Am I the only one who has random audio increases? It happens especially in spotify (in other apps too, but much less), as soon as I try to skip a part of the current song the audio increases to 100% for around a half second, which results in bleeding ears... Happens on all other LOS based roms :/
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] warBeard_actual:
I haven't had a single reboot since I started running this back in early November.

Each device is different, however. And it is important to take note of anything you have installed after the fact - like kernels. If you are running overclocked CPU's/GPU's, you're introducing variables that can causes stability issues. Reboots are a notorious side effect of overclocking.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dbloms:
I use spotify all the time to listen to music and didn't have this issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] effie.tardif:
May I ask, do you use the newest Spotify version or any of the previous versions? Which LineageOS version? I'd just install an old apk if this would fix this issue ^^

And no, my headphones aren't defective, this happens with several headphones + the internal speaker... :/

edit: looks like the Axon 7/LineageOS isn't compatible with the Spotify equalizer, disabling it fixed it for me