yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcs4:
Hey, just a quick question for whom have this ROM installed.

I've notice that the "50%" brightness on this ROM is a bit dim. I have youtube vanced and I put the brightness at 50% there and when I return to home screen I notice the difference. Does someone have this "problems" too?

Thank you anyways

Ps: I've checked and I don't have the adaptive brightness on.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] king1990:
it will work

The brightness curve is one thing I'm trying to find a solution that will suit everyone. for now you can increase the brightness above 50% if it is dim for you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] :
So, can this work with Magisk? :confused:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcs4:
It's working for me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] :
After following the installation guide, do you just flash Magisk through TWRP? After I flashed it, I don't pass SafetyNet at all, not even basicintegrity. I also installed the Viper module but it doesn't show up in my app drawer.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Follow these steps by EBeatFLA. (Magisk v18 & BusyBox for Android NDK worked just fine):

"Lets set up Magisk and pass SafetyNet

At this time I recommend Magisk 17.2

Find it, download it, and flash it in TWRP

Once booted, in Magisk search for the module “MagiskHide Props Config” and install it.

Then search for BusyBox module by Osmosis and install it.

Reboot

Using a terminal app (not in TWRP) like Termux, type “su”

Grant root privileges

Then type “props”

You should be greeted with a menu

Select 1 to Edit fingerprint

Select F to Pick a Certified fingerprint

Then follow the menu to select ZTE and Axon 7

Then yes and yes to reboot."

Good luck
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] :
Props not found :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
What bootstack are you using?

Make sure your are using this one

https://androidfilehost.com/?fid=11410932744536985259

And flash your modem after flashing bootstack.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] :
Never mind, I just reinstalled everything. But thank you very much :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Just thought I'd mention, a little tip. Since some have been claiming problems about not having internal storage. If you are claiming this because you are not seeing internal storage in the default File app, you're wrong. The option in the app is off by default. Just select the three dots in the corner of the app and then select "Show Internal Storage".
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ibphantom:
Does it show you have a connection to a cell tower and data isn't connecting? Or it's not even registering with the tower and saying no connection in general?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Arbelzapf:
It does register and I can do calls and sms. But there is no internet connectivity whatsoever.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ibphantom:
Under your mobile network settings, do you have Mobile Data and Roaming enabled as well as a preferred network type selected?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Arbelzapf:
Sure. All settings look right as far as I can tell
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
I think it might just be a bad flash.

Go to twrp, and wipe your vendor and system partitions. Flash your vendor zip again, and flash the system image again, reboot to twrp and flash the same gapps package you used in your first install.

Reboot to system, and check if the problem has been fixed.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Arbelzapf:
Nothing helped. I tried to clean install a couple of times. Thank you for your time, but in the end I had to restore my backup and now it is working again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] juniorD:
So now any time i reboot my phone it boots to black screen. Then I have to wipe and start over. Sigh.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hjjiang:
What vendor r u using?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] juniorD:
I used NFound's vendor at first I think. But thing is the ROM was working fine just a couple of weeks ago until I tried to update. I never flashed the vendor just the data and system so I dont understand why it's doing this now. Only thing that I can think of is the 2 latest updates being the issue for my phone. :confused:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
You're using NFound's vendor still?

Use Speedy 6.2, it's like a full year newer
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] juniorD:
Thanks I'll hunt it down. Is this vendor specific for the Axon or just works better for Liquid?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
All vendors are specific for the phone they are made for, they are the specific files in the Treble system. Vendor is what makes GSIs possible, the stuff in the vendor is what links your ROM to the hardware like the camera. A bad vendor means hardware working badly.

speedy works very nice for GSIs. You can get Speedy from some Telegram groups
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] juniorD:
OK thanks. I found Speedys page on Android File Host and he has a few files there Im going to try on my next GSI update. Im on Bliss now and its not that great but it works.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] juniorD:
Found Speedys vendor and boots to black screen. Other vendors gave me a mismatch message. Only one gave me no problems. Which is why I asked are vendors phone specific or ROM specific.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
The mismatch message is not important, just an error in the vendor version name thing. which absolutely doesn't matter because it's not like ZTE made it, it's been put together here.

You clearly have to be doing something wrong to have Speedy boot to a black screen... What bootstack are you using? Try flashing the B20 bootstack from the LOS thread (any of the two, open the link to download and you'll get a file list from afh)

I've never heard abt a black screen with Speedy. Almost 100% sure that it's either your ROM or bootstack or maybe whatever else you flashed right after
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] juniorD:
May have been the ROM. I switched ROMs and clean flashed using Spedys combo vendor and there was no problems. Not even a vendor mismatch issue. Im using the latest Arrow OS GSI and while its not my fav it works for now until I can find another port.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
Just use official AEX or Havoc or OmniROM. doesn't matter that much which, all get awesome battery life with baddar kernel and speedy
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] iyancoolbgt:
Hello can anybody please share this rom boot.img please? I installed custom kernel and now want to back to stock liquid remix kernel. I lost my backup so I can't restore my kernel.

Any help appreciated ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
GSI ROMs don't have boot.img. They only flash system.

To restore your original kernel, flash your vendor again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xboxbr:
I always used nfound and it's working very fine for me. why speedy is better? do you have any changelog?

and I also had blackscreen after boot. A2017U B20
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
NFound's vendor is extremely makeshift (it was the first), and has high CPU usage on idle, bad camera, no OIS, hit-and-miss fingerprint sensor, and of course the kernel is ancient and horrible (unless you flashed Schwifty which is marginally better)

All of this ends up giving you (very) subpar battery life, excessive heating on not too demanding tasks...

I don't have a changelog, but it's pretty obvious that you should get out of there anyways. Hell, there was Kranoner's vendor too, and it was better than NFound's but had a couple of bugs when trying to change the systemui color and that stuff, nothing too bad. it's also very old already.

and about the black screens, i can't help you but you bet it's your own problem, probably because of the old vendor. I haven't had a random DFU reboot or a normal reboot or (sudden, not battery related) shutdowns in about half a year
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] iyancoolbgt:
Can't download the rom from the link. I think it's broken :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Guido83:
New Builds 2019-06-24

A-only: https://www.androidfilehost.com/?fid=6006931924117902001

A/B: https://www.androidfilehost.com/?fid=6006931924117902036
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] foggydew88:
Thank you very much once again Guido. :good:

I would like to see your builds archive, the one linked in your signature, but it say Access Denied.

Cheers!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Guido83:
you are right, I pasted the wrong link. Sorry for that. I fixed it now

https://androidfilehost.com/?w=files&flid=282409
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ls117:
anyone been able to get viper to work on this rom? legacy and 2.7 will not process using headphones.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] foggydew88:
Viper FX Legacy 4.3 (2.5.0.5) is full working for me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
try using compatibility mode on 2.7 or just install audio modification library
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ls117:
Both don't work. Any simple fix I've already tried, this is v4a, so I've had these issues switching roms before. I already dropped liquid for lineage and I'm magically having the exact same issue. Phone speaker will process, Headset refuses to process.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
then i guess you should talk to Thomas, over at the v4a telegram group - he might be able to help you on this if you provide the necessary stuff
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lightspeedx:
What's the difference between A stock and AB stock? Thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] atakan33:
if you have a axon 7 flash A !!!A/B is not for axon 7
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lightspeedx:
Hi, when updating to the latest build version of the ROM from an older build, is there a way to not have to wipe everything (aka lose all apps and settings)? Is there .a way to update to the latest build edition with just flash the ROM to System? If yes, please can you outline the steps that should be taken? Thank you much!!!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Zobat:
wipe caches and flash rom. Maybe gapps aftewards.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Guido83:
That's not true. I'm running it with DotOS vendor and got no issues at all
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Are you using Schwifty or Hellsgate? DotOS vendor alone didn't work when I tried it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Guido83:
yes I am using schwifty together with it
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jayrome876:
Well I must say this ROM is pretty impressive. It can be used as a daily driver; all the essential stuff (and more) work as intended. I'm running Magisk, Dolby Digital Plus, Ainur Sauron and Viper4android -- no issues so far. Considering it's a first release I can tell great things are in store for future releases.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xShottaZx:
what does A-Only stand for?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
A/B devices have a thing called "skip_initfs". In older A-only devices like ours, we have the kernel ramdisk in boot partition. But in A/B devices, the boot ramdisk is only for recovery - when booting the system, the system actually contains the initramfs instead and it gets mounted to / (rootfs) instead of /system.

In short, A/B devices have init and ramdisk all in the system partition. This means Treble ROM's for A/B devices can easily have their own initfs, which makes things a little easier.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] pahoa:
I tried and found this ROM very good with about everything working. But had to go back to AEX 5.7 because my phone keeps freezing. It seems to be heat related even though highest temp was around 45. I tried it's stock kernal and also swifty and hellsgate as well as both B20 and B12. Nothing fixed this freezing problem.

Then this has been my problem with all treble ROMs. Does anyone know a fix.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Are you using the NFC Hotspot fix? If not, you should try, it's been known to solve that issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] pahoa:
I did try it with the NFC Hotspot fix but was the same. The only way I could get it to install and work for a while was to start the process first thing in the morning while phone cool or leave it in the freezer for a minute first. I've tried everything, but still no dice. Maybe if had more time before phone freezes and knew better kernel settings I could try that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] king1990:
ROM updated

check the changelog for details
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Zobat:
works good. nothing broke ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Guido83:
themer still not working here
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Zobat:
had not checked the camera, don't know where's the error but installed some old (probably}) gcam (non magisk) and it's ok now
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcs4:
Is there anyway to know what build do we have, I didn't clean install the new update.

I wanted to know if the update was successful.

The build number doesn't appear to be any of the 2 builds we have.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Your build number is same as mine, and I'm still on the first one.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hjjiang:
Tap on android version and ull get this screen with the build date
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcs4:
Ty, I'm on the newest build, did you use substratum to have a dark theme ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CASEY_K:
There's probably a fix somewhere on the other threads but system UI dark mode doesn't work for me. Or is this something normal?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hjjiang:
nope, im just using the built in one

Display > Advance > System Theme Section

My setup is

B20 bootstack by verequies splash no message

mokee vendor

Liquid remix

schwifty R5

Magisk v18
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Zobat:
my buildnumber is the same and i'm on the second build.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
We are still trying to narrow down what is triggering the theme engine to break. The following are things that have been reported to break the theme engine. Not all have been completely confirmed, so feel free to confirm the issue yourself and report:

+Restoring TWRP backup (even if the backup had a working theme engine). Thus EDL backups are recommended to be able to restore to a point where the theme engine was working.

+Flashing a vendor or flashing a kernel at some point (yet to be determined) after the initial clean flash.

+One report of simply flashing Magisk 18.

+"Sometimes" when applying a Substratum theme.

Unfortunately there is no easy fix, and the only known fix is to start over with a clean flash. Because of this, if the theme engine is important to you, I recommend the following:

Follow the instructions in the OP to do a clean flash. On the first boot into system, before flashing Gapps, check that the themer is working.

Then flash NFC Hotspot fix, your Gapps and then custom kernel if applicable. Boot again and follow setup wizard, but do not restore any backup of settings or app data.

Then flash Magisk and perform the Magisk Props Config instructions to pass SafetyNet. Check themer again, it should still be working.

Then, set up all of your apps and settings to a point you feel would be an acceptable place to make your EDL backup.

Having this EDL backup will be a big time saver to you, just in case you ever trigger whatever is breaking the theme engine. Because, again, once it's broken, you'll have to start all over.

If anyone has the time to experiment and help narrow down this issue, it would be of great help. Thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CASEY_K:
Thank you so much for taking the time to respond with this. I should be able to give this a shot tonight. It's good to know there isn't an obvious fix that I just completely over looked too. :)

edit: did all the steps above and for my case I'm going to have to go with the magisk deal, although it did not happen on the initial install. Sometime in the near future I will go through my modules one by one and see if I can narrow it down more. For now I'm going to try the patch [MENTION=8296974]Link500X[/MENTION] recommended. Hopefully the little bit of info I have provided can help the whole though.

Awesome freaking ROM btw. Feature packed but the one thing i have missed in so many roms is the gradient battery bar!! Thanks soooo much!!!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
From AEX I wiped system & cache, but receive an Error 255 when atempting to flash this system.img. Using the same data and vendor. What am I missing? I did the same thing when going from the previous version of LiquidR to AEX.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Link500X:
https://xdaforums.com/showpost.php?p=77609098&postcount=554

works for me with that patch
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] king1990:
Enjoy the ROM

This issue is related to the vendor. use nfound vendor or use substratum.

Dirty flash is not recommended , check the build date not the number , I forget to edit the build number before building the ROM.

[MENTION=8456254]EBeatFLA[/MENTION] Thanks for the explanation , just note that almost all the broken theme issue came from users used non-nfound vendor, I'm using his vendor since two weeks with liquid without any themes problem and this while doing many changes in vendor partition by editing files or even deleting them which result sometimes in bootloop but simply wiping and re-flashing the vendor everything return to normal including the themes.

I suggest using unmodified nfound vendor to narrow down the issues whether its coming from the vendor or from somewhere else.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Link500X:
Any chance that either slim, omni, or grid recents will be made available? I've seen omni and grid available on other pie roms (although can be a little laggy), so hopefully shouldn't be too hard to port. Slim recents on pie would be great if possible...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] raystef66:
Bootanimation wasn't using the full screen so a made a new flashable one

A2017X_bootanimationflash_LiquidRemix
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Sketso:
Someone faced a problem, it is impossible to swap back and recent buttons? I click the slider swap buttons in Liquid Lounge menu, but nothing changes.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
The option in the ROM does not work, true. But there is a zip by [MENTION=1965130]raystef[/MENTION]f66 that will work every time:

https://xdaforums.com/axon-7/themes/mod-soft-key-reverse-using-synapticsdsx-t3827574/post77295390
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] king1990:
Thanks for the boot animation

check this thread

https://xdaforums.com/axon-7/themes/mod-soft-key-reverse-using-synapticsdsx-t3827574

and use magisk module or manual one
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CASEY_K:
Thank you, will give it a shot
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Regarding the Theme Engine. Just discovered that if Dark Mode is enabled in Google Messages app, the Light theme will not work and will be Dark. Dark and Black themes still act normal.

This isn't the solution to the issue of the Theme Engine breaking, because when disabling Dark Mode in Messages, all of the themes will again act normal. Just thought I'd share so this isn't mistaken for the issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Still seeing TWRP error 255 when attempting to flash system.img for the

update. My original LiquidR install still runs fine after restore. Any ideas?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
New build flashed fine for me today, but I clean flashed. Have you tried clean? Maybe bad download or bad extraction?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Good call. Download/extraction #3 seems to have done the trick!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] pahoa:
Installed new build with nfound vendor and NFC fix. All is now working on my phone. Also installed Magisk v18 and Dolby. Battery is very good on my phone for my use. This ROM really rocks and is what I've been waiting for to use for my everyday pie.

Much thanks for all your effort and great work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Link500X:
I've found an issue, and am wondering if anyone else can test and see if they experience the same thing. I got a new SD card, so had to transfer all my music to it. It stops transferring and the USB interface temporarily breaks after about the 15th FLAC file (so a fairly large amount of data). I tried it 2x each on exFAT (formatted from previous ROM) and vFAT (formatted on this ROM), with the same result. It transfers fine from recovery (and I'm assuming it would work if I put the card directly in my PC). I installed the ROM according to the directions (including NFound's vendor).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HeikoNote3:
Hello there and Merry Xmas. One Question: Is it possible somehow to use the Sounds App for the Ringtones or Notification Settings? Everytime I try to change the Ringtones, the Sounds App crashes on my Axon 7.

BTW, all the other Things working nice so far, seems better than Havoc Os 2.0 to me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] king1990:
Nice to hear that , enjoy the ROM and report and problem you faced :good:

How big is data ? I just sent .iso file abut 2GB size, while it look like its stuck at the end , it completed after few minutes later but it never break or crash. I remember this happening with other ROMs so more testing is welcome

just give storage permission for the "sound app" and it should work.

happy to hear that the ROM working for you :good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Link500X:
I think the batch I was sending was about 2.5 GB, and failed around 1 GB.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Another strange question for you: my A2017U running B35 connects to the PC via USB and is recognized as MTA for data transfer.

OTOH, my 'testbed' A2017U running LiquidRemix is not recognized when connected by the same USB cable. The phone & ROM run just fine otherwise.

Does the 'device fingerprint' of the phone with PIE require different PC drivers?

Merry Christmas!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] king1990:
OK, I think I found the solution , go to developer settings and disable "Tethering Hardware Acceleration"

you need to select "file transfer" from the phone when you connect it to PC

Please don't reply to him.

How is the ROM so far with you ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HeikoNote3:
just give storage permission for the "sound app" and it should work.

Yep, that worked. Thanks!