yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] raphi809:
Same here which sucks. RR has more features so it's the rom I stick with but I've been seeing soo much praise everywhere on the forum for this one I decided to try it out. It's almost perfect enough to become my new daily after running it for the last 3 days but I've got audio lag on YouTube, Instagram and Snapchat. A restart helps sometimes but usually by the end of the day it will go out of wack again for me. I also get the loss of audio when changing screen orientation. Can't wait until it's solved tho. Keep up the great work devs!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Infy_AsiX:
Does anyone get wifi disconnects often on AEX/RR? I got them pretty consistently in the days I've used them. I installed the wifi bonding magisk module from the manager and don't experience them anymore.

gave Daydream a test myself on RR. I used those modules (edited the pixelify one to Pixel 2 XL for fun). I think it works even better than stock.

On UB32 stock wouldn't be consistent for having the night filter mode off and restarting, fixing the issue. Also after launching daydream the CPU would be stuck at "sustained performance mode" where the CPUs all sit at 1200MHz except when switching apps, where Qualcomms detection temporarily boosts to max frequencies.

Meanwhile on RR I can just switch night filter off before launching VR. A downside though of the custom ROMS is they don't have the sustained perf mode. So unless you disable thermal throttling and set your own limit to 1200MHz, you'll instead be limited to 1000MHz by the default thermal throttle and VR performance will visibly suffer somewhat.

A caveat of using CF.lumen I talked about last post is it does have a similar issue affect even on KCAL. Having had it running it needs to be toggled cycled on off or vice versa after VR has started. I found having Lux's notification to toggle the plugin useful. The plus side here is with a little setup you can have a working night filter during VR combo.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kitcostantino:
is there going to be a thread for RR O eventually? Thank you for all you do!!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] NFound:
Why create 100500 threads? All the assemblies are in the "beta" stage because of the bug with two sims. In the rest all assemblies differ only in functionality, not more.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kitcostantino:
honestly, i just didnt want to keep posting/asking RR-O related stuff in the AEX thread, nothing more, man. I agree with that logic. Im still on RR N and was wondering if a2017U is compatible. also if official TWRP will work as the modded TWRP thread reads as if U model is not supported/ doesnt work. i read where U users have installed both, i just couldnt reference ROM specific install do/donts. Are AEX instructions applicable to RR-O as well? Thank you!!

EDIT: i see now. U model is supported.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Cablespider:
Never mind.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] NFound:
Em? What happened? What a sad tone ... everything will be fine :highfive: ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcdw:
Heh. You quote the post where he tells you to ignore that but then you still ask anyway. Just ignore it.

Got the same with crDroid on a Moto. Probably some new check or whatever that LOS introduced.

Moto G5S Plus XT1806, GZOSP_PixelExperience, MultiROM, Tapatalk 4.9.3
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Cablespider:
Lol I thought I had a DT2W problem with AEX but a reboot solved it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
Been well documented a bit further back in the thread. The dual sim bug is simple to reproduce.

You can only use the sim for calls if it's also the same sim you use for data. Switch data on the sim you want to call on and it works.

Sadly it's a bug that's probably not going to be fixed. Hopefully ZTE release some source if indeed they do release an official Oreo build.

With ZTE being banned from retailing in the USA I don't keep my hopes up anymore.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kingo64:
Wow I'm an idiot. Dunno how I missed that
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haoyangw:
Once again managed to patch HellsGate V2.1 for DualBoot Patcher compatibility! As before, HellsGate is integrated into this zip so no need to flash the hellsgate kernel zip again, just flash this and you'll have installed the complete HellsGate kernel :) Running this right now on my phone with AEX 0414 and everything is smooth and perfect, no crashes no lag no battery issues. Will update this post asap when I manage to patch the AEX 0421 kernel :)

Note: As before, both zips have been patched for primary, but that's no issue because you can just patch it again with DualBoot Patcher for whichever slot you want to use :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Briefly OT, but after revisiting the DBP thread I still can't tell: is it yet possible to keep stock B35 ('N') as primary with this kernel and one of these 'O' ROMs as secondary?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Nicz14:
I'm using the AospExtended-v5.4-axon7-20180421-0700 build and i'm wondering if the green tint in the lock screen and the quick settings is intended.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
yes, but you need to patch the kernel. Use the one in the Hellsgate thread, someone there patched it and posted it there

---------- Post added at 06:03 AM ---------- Previous post was at 06:02 AM ----------

yes, it's based on the wallpaper color. I have no idea why Google thought that would be a good idea
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kranoner:
1.yes its start but wrong have you read logs

2.i have no time to update all things i have no 4 arms

3.look off my github i start to update all blobs i dont need your blobs sry then we have alot of comparatively devices for it when zte relase o i kang it lol

4.Why you build all roms official from AEX to RR you are not a official maitainer for AEX you dont have any premisson to relase it official by rr the same you build weekly its only for offical devices and use please the right tags in your thread then your build is unofficial and not official

6.I respect your work for the axon7 and wish you all the best with your work
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] NFound:
My advice to you in life is to first learn to answer for your words, and then write such statements. I attach screenshots so that all users can see it. And I ask you not to write any more off-topic threads and discussing your kernel, discuss your assemblies and the kernel in your thread. Though in other, as they said above: :laugh:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] skdubg:
Peace [emoji111]️
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kranoner:
oh you're cool putin lol i don't want to argue here but you're just using ordenkreigers device tree with changes from msm8996 xiaomi and your own little chages

you can show all my news and do not bother me I think it's funny my kernel is now stable and work on device tree and vendor do your thing I mean because I live in a free country and can do what I want thank you and

I do not care what others think here :laugh::laugh::laugh::laugh::laugh::laugh::laugh:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choobilsky:
There is no benefit in joining this absurd debate you are trying to raise in NFounds threads, but as it starts to get annoying:

- NFound is right, you are the one off topic here

- you are the one with the poor behavior

- well, and in the past you were the one who abandoned/closed his threads after some people had issues with your kernels/ROMs stability or whatever.

I appreciated that you returned to continue your work on Hellsgate kernel. Guess, I was wrong.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] GabbaGandalf42:
Geez.. gonna switch to German real quick.

Alter kranoner hast du deinen Arsch offen? Beruhig dich und benimm dich wie ein Mensch. Ihr macht Beide gute Arbeit, gut ist.

Much love and peace

EDIT: Ich hoffe, dass du verstehst, wie rassistisch dein Post mit "Putin" etc war. Du hast kein Recht so mit irgendwem zu reden.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kranoner:
is ok too I learn from my mistakes and try to do better as in the past I do not want to argue here with nfound i respect his work

Therefore, I have said he does his and I think mine I will not comment further in this thread anymore but thanks for your criticism because I represent only my point of view
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kingo64:
Hey did you ever figure out what the cause was? I just upgraded from RR-N to RR-O w/ Hellsgate 2.1 and I am experiencing the exact same issues you were facing. No metadata readout or buttons working on my car headunit but audio works and can playback if I control it from my phone using Poweramp. I did not have these issues on official RR-N and was curious what the cause/solution maybe. Any ideas? Thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Ashevar:
Did this ever get resolved?

I'm on A2017U and I have no audio at all except for a short beep during boot right before it asks me for my PIN.

This is the case with the last two AEX5.4 builds. Multiple attempts with each, full wipes, B32 and B32+B10 bootstacks tried, with and without Magisk. Really puzzling that I can't get any audio though on a system/data/cache/storage wipe then install of the plain base ROM without anything else though.

No audio with NFounds RR-O 0421 build either.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Lycidias:
I still have this problem... It's Googles fault and we can't solve this as normal users i think
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Cablespider:
If you're using Hellsgate, you should be reporting in that thread. Nfound can't account for problems a third party kernel may be introducing. Take it to PM if need be. He puts work into his own kernel and expects tests/reporting to be based on the stock experience. Most devs expect that of testers.

I have nothing against Kranoner or Hellsgate. I use the kernel myself. I wouldn't dare report problems with a ROM unless I tested it with the stock kernel first. Kernel testing has its own procedures. Proper reporting is key to future development.

This applies to everyone...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Well said, bravo. :good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
Maybe you should go back to full stock, see if audio works, and start over
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Ashevar:
RR-N works just fine, I suppose I could try stock but I don't see what would be different there.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
It would be nice if you two guys stop this nonsense discussion. You are at this time the only active developers doing something really good for the community and it is sad watching this.

In a perfect world you two would be working together, sharing your knowledge and recognizing each other work and effort. 4 eyes see more than 2, and 4 hands type faster than 2. A little teamwork here always help. I hope it is till not too late for you two guys.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] christoophat:
That is an Oreo issue, not a ROM issue. I'm staying on Nougat for that selfsame reason (loss of metadata readout in the car using O)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AnonVendetta:
Can someone say if it is possible to dual-boot AEX 8.1.x and Lineage 7.1.x together? I'm planning to use Dual-Boot Patcher. I'm also using [MENTION=5492451]NFound[/MENTION]'s latest bootstack instead of the one that Lineage recommends, but I'm not sure Nougat will boot with it. Is the Oreo modem he provides fully Nougat-compatible? I want to run AEX with MicroG, and Lineage with official GApps so I can pass SafetyNet on the latter. MicroG and GApps are directly contradictory to each other, so they cannot be run together on the same ROM. I'll also be using BeastMode kernel with Lineage, and Hellsgate with AEX. My root solution will be SuperSU installed in systemless SBIN mode, with SUHide for hiding root. AEX will have Xposed installed but Lineage won't. If this combo won't work then I'll try Oreo AEX with Oreo Lineage or Resurrection Remix. I'm not experienced with Dual-Boot Patcher but want to try something different. This is still my favorite O ROM for the A7, [MENTION=5492451]NFound[/MENTION] and [MENTION=7790189]Kranoner[/MENTION] have done a fantastic job.

I apologize in advance for going a bit off-topic.

Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcdw:
[MENTION=7441667]AnonVendetta[/MENTION], I'm currently running AEX Oreo (w/Hellsgate) as a secondary along with B32 stock (primary) and AEX Nougat (microG).

I don't have/use any Oreo-related bootstacks and the like so can't comment on that.

So far, SuperSU has been a no-go with Oreo and DBP. Tried in the past with PNW and a couple of times with AEX. Not sure what the deal is yet.

I normally only use SU so all N secondaries were good to go.

And I know it's not an Oreo thing as I only use SU on the Oreo ROMs running on a Moto, with MultiROM.

Further discussion might be better over here...

http://xdaforums.com/showthread.php?t=3568727

[Guide] Dual Boot Axon 7 using Dual Boot Patcher

ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.5
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AnonVendetta:
[MENTION=6046143]marcdw[/MENTION]: I refuse to use a ZTE stock ROM, I much prefer to stick with AOSP/Lineage/CM-based ROMs. I'm not a fan of stock firmware at all, not just with ZTE, but with other Android devices I use too.

I think it would be safer to dual-boot 2 Oreo ROMs alongside each other, simply because they should be able to use the same bootstack and modem.

I too had trouble using SuperSU on an Oreo ROM (AEX and PNW) on the A7. It always worked fine in Nougat. I was helping a user here in the A7 forum some time ago, I discovered that the ROM can't boot because the SuperSU zip patches the DTB in the boot image (whatever it is, I don't know). By eliminating that from the flashing script, the ROM is able to boot. I use AROMA SuperSU Config and configure for SBIN mode. If you're interested, more details at:

https://xdaforums.com/axon-7/help/write-protection-t3761912

Strangely enough, SuperSU works fine with Oreo on my retired Note 4, ROM boots right up with no additional work required. I'm not aware of any compatibility issues between SuperSU and DBP, I guess I'll find out soon. Screw the Magisk bandwagon that almost everyone else is jumping on, it's caused me too many issues in the past.

I'll maybe continue this discussion in the DBP thread.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcdw:
Heh heh, I hear ya on the stock. I rarely boot into it and it's there mostly as a placeholder from when I started messing with DBP. One of these days I'll start over from scratch.

I'll look into that nodded SuperSU and see how that works. Thanks.

ZTE Axon 7 A2017U, AospExtended v5.4 ROM, HELLSGATE Kernel, Multiboot, Tapatalk 4.9.5
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] chris-t-an:
hey guys, is AEX oreo stable on A2017G at least as stock Marshmellow or Nougat?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
On the three cases my phone didn't move when left on my nightstand, hope that clears it out.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] chris-t-an:
Lol, I'm serious man.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] GhouLinux:
We really need some fun in this thread... But, yes, no problem here to use it as a daily driver...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
My gf bought a pixel after I bought this phone and it's been absolute trash. Being an iPhone convert it's been a nightmare hearing about how much android sucks.

However my axon costing half of a new iPhone/pixel Still goes strong.

Things may not be perfect but I feel like this is twice the phone her pixel is for a lot less.

Thanks to those great devs that keep this little beast alive.

The US government may have banned ZTE but it's their loss and probably to create a monopoly for Apple.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Axebladewarrior:
Thanks to the dev team of AEX we can still enjoy what this phone has to offer... Still a beast [emoji41]
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haoyangw:
Yes, I've personally tested it myself. Before I switched to AEX Oreo as primary, I was running VertexOS 7.1.2 as primary, while testing AEX Oreo(which is my data-slot-1). I flashed O bootstack and modem and both ROMs worked perfectly, no reboot problems or cellular data/signal or sim problems. Granted that was 3 months ago, but I don't think any recent changes would make a difference. And I definitely don't think it's just VertexOS that works, all AOSP Nougat ROMs should work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Curious, are you still on 0412? I have been using it since around the time you posted this, and it's still taking everything i can throw at it. Not sure if any of the updates after 0412 are worth the effort. Call me lazy. I'm really just enjoying 0412 and would hate to see something happen to it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] machetie:
Call me lazy too! Still on 0412. I'll be backing it up soon tho, going to try the RR with hellsgate kernel inbuilt from another thread. I'm really hesitant tho. Everything is running smooth here so I'm in the same boat as you!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Think I'll stick with it a bit longer then and keep checking in on what others are posting. Running 0412 with Hellsgate 2.1 and the Ghostpepper AKT. This is by far the phone I've held onto the longest, and my time with it looks like it's been extended. Pun intended.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
One more to report this.

I hear you guys, gonna stick to what I run for a while longer till some bugs get ironed out.

(I'm happy to help in any way I can if I can contribute though)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
Applied zhana balanced, what is this with cpu temps? Not even running a app. Or is this Just a qualcomm problem, they always Get Hot
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
I think Zhana works better with RR. I had the same problem with Zhana on AEX. Ghostpepper seems to be more balanced for me. Try using it and see if it gives you a smoother and cooler ride.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JvDsN:
Hi what's the difference between RR and AOSP?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Android4thewin:
RR had more features at the cost of being slightly more bloated.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JvDsN:
So which do you recommend for me , i play various games and take a lot of photos
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mameenbh:
AEX is the best to me hands down, I play clash royale all the time :D
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amaury48:
I've attempted to flash this room on my A2017u with no luck (was on stock B15 w/twrp 3.2.1.0) I have returned to B32 stock room via miflash with no twrp or root for now.... I am going to attempt to reinstall one more time following this procedure:

1. Flash twrp 3.2.1.0 with Axon7_EDL_Tool

2. Reboot into Twrp

3. Flash A2017X_Bootstack_B32_0.zip (select A2017U)

4. Flash AospExtended-v5.4-axon7-20180421-0700.zip

5. Flash Open Gapps Arm64_8.1_mini

6 .Flash Magisk 15.3

7. Reboot system...

Does this sound about right?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ttkian:
I think you have to use A2017X_BootStack_B32+B10.zip for the bootstack and magisk 16 works fine with the rom.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amaury48:
A2017X_BootStack_B32+B10.zip ? Where do I find that?

NVM....found it...thx
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mameenbh:
https://androidfilehost.com/?w=files&flid=246430
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amaury48:
Flashed the A2017X Bootstack_B32+B10....that was ok,

Then attempted to flash AospExtended in #3 and came back with:

"Updater process ended with error 7

error installing zip file 'external_sd/roms/AospExtended 8.0/ AsopExtended-v4.6-axon7-20180418-2230.zip"

??????

---------- Post added at 09:37 PM ---------- Previous post was at 09:08 PM ----------

Going to try and remove the assert line in the updater script and see what happens.....
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mameenbh:
In Twrp, under advanced wipe choose data and change the file system to f2fs
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Cablespider:
4.6 is Nougat. I'm not sure if that bootstack will work with Nougat even if you remove the check. You can try, of course.

AospExtended-v5.4-axon7-20180421-0700 is the latest Oreo build and will work with that bootstack.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
I'm using that boostack with nougat, I can confirm it works just fine.

(if you skip the check and all like you said. :) )
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] voetbalremco:
You're flashing Nougat instead of Oreo.

v5.4 is what you're after, unless you want Nougat.

But Oreo is stable enough.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jose_costa07:
Coming from stock nougat 7.1.1 B10 which Bootloader and modem should I install? Or is it not necessary to install any Bootloader and modem?

I'm using an A2017G. I have an unlocked Bootloader and twrp installed.

Thank you for your answers.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dhammika71:
Any idea why bluetooth not showing any devices?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JTruj1ll0923:
You need to flash either B32-0 or B32+B10. They should be either in OP or somewhere in the thread. Also make sure to be running at least 3.2.1-0 TWRP
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jose_costa07:
How am I supposed to know that I need these particular Bootloaders? It is not mentioned in the beginning of the thread. What about the other roms, how do I know which Bootloader and modem is needed?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JTruj1ll0923:
Underneath the download button for the rom "Download build Oreo" there is a button for "Bootstack for Oreo build". So, yes it should be explicitly said, but that's better than nothing. Bootstack is important and the rom won't run without it (iirc).

If you use any other Oreo rom to my knowledge you need the same Bootstack. However, if going to Nougat all need the original universal bootloader in Lineage thread (B15?) except for DarkRom which uses the same B32.

Edit: for modems, they are usually included with the Bootstack so it's only one TWRP flash.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jose_costa07:
Thanks for your answer man. Referring to twrp, can I just flash the 3.2.1.0 image over the one that I am using now (3.1.1.0)? Can I do that by booting into recovery mode and flashing it with twrp?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JTruj1ll0923:
Yes. It should be Install>Install Image>Find TWRP.img and flash like normal.

Also I would recommend doing this before wiping your current rom. Otherwise there is a chance you could end in a loop. So,

Boot into TWRP

(Backup if you want, but recommended)

Flash New TWRP

Reboot into recovery

Wipe System, Data, Cache, Dalvik

Install Bootstack and then rom of your choice followed by everything else you want.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jose_costa07:
Thank you so much man!! I just managed to upgrade twrp from 3.1.1.0 to 3.2.1.0. And I will install the rom on the weekend.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
Woow so big achievement - _ - lol:p