yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
That only happens if you touch the photo, touch more to the left. I think it's intentional.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choobilsky:
My device is a Chinese A2017 4/128 showing up as A2017U since it was rooted. I never had muted calls, but an overall poor call quality, which improved a lot with last updates. Stereo speaker sound was fixed some 4 or 5 weeks ago.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CraiZJak:
I'm on A2017U with a clean install of this ROM and the war_mod "tune". I have stock kernel and no audio mod as of now and tested the muted call issue with and without the war_mod "tune"... same result :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jw1985:
I have the A2017 G version european model
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcscorpio76:
I also have war_mod installed along with Llama Sweet Kernel .04 and the sound issue is completely fixed in the latest AEX update. I dirty flashed from the previous build, wiped the cache from the phone app and all works perfect. No FC, no sound issue. Calls sound clear, crisp, and loud over top and bottom speakers. Not sure why some have issue and others don't. If you clean flashed the latest build, try a factory reset in TWRP and wipe Davlik/Art, System, Cache, Data and flash again. I never wipe Internal nor external. Maybe that will help. In TWRP factory reset, System isn't wiped I don't believe. Make sure you back ALL your data FIRST in case something goes awry.

---------- Post added at 11:19 AM ---------- Previous post was at 11:15 AM ----------

Yes, the stereo speakers was fixed a long while back. Although that resolved the sound issue in both speakers while streaming music, the speakerphone would still only play from the top grill and the sound was very low unless you cut the screen on and off in call then the bottom grill would activate but that was hit or miss. This last update completely fixed it for me and surprisingly on a dirty flash over the early July build. I didn't even bother flashing the last 2 builds before 7-17 until I saw [MENTION=5492451]NFound[/MENTION] fixed the speakerphone issue.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CraiZJak:
I had the same build as you in the previous and also performed a System, Dalvic, Cache, and Data wipe before installing it. On this update I just dirty flashed it and yet the issue still persist. The call stays muted until I double tap the speaker button and sound then comes through. So every time I make or receive a call, I double tap it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MMoodyB:
Does it stay audible for the whole duration of the call, or do you need to double tap the speaker button at some point later on?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcscorpio76:
Man that sucks! I remember having that issue and I just dealt with it until the latest build 7-17. I suggest you give it another shot and clean flash and see what happens. Did you wipe the cache and data in the phone app? I also did that immediately after dirty flashing!

---------- Post added at 11:35 AM ---------- Previous post was at 11:25 AM ----------

When I did have the issue, I would have to double tap again at some point because it would jump back to single top speaker. That issue is no longer for me. It sucks that it's not working for some. This is the greatest resolve since the stereo speaker issue while streaming. Very satisfied with this now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CraiZJak:
Always do... except this time. Whoops. I'll give that a try and if it doesn't work I will do all the wipes mentioned including internal data (ohhh boyyy) and see if that puts a bandage on the issue.

---------- Post added at 03:37 PM ---------- Previous post was at 03:36 PM ----------

For the whole duration. [emoji106]
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcscorpio76:
Make sure to backup your internal storage before you proceed or you won't have anything to flash [emoji6][emoji6][emoji6]
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CraiZJak:
Already did ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
There is still no sound bug when rotate screen.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcscorpio76:
[MENTION=5492451]NFound[/MENTION], I found a bug and I haven't seen anyone else mention it. I can connect to WIFI, but there is no data. I tried multiple browsers and I continuously get an error message. I'm on the latest build from 7-17. Can you please look into it? Screenshot attached.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
I am on the latest version as well and have no issue with data via wifi.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcscorpio76:
I've tried clean flashing after a full wipe and still my WiFi is screwy. I've been on the 7-17 build since it was released and I didn't notice until I tried to update apps in the Play Store. I also reflashed the B19 modem and still the same result. I'm perplexed at what could be causing it. [emoji848][emoji848][emoji848]
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
There seems to be confusion with the word "sound bug".: it seems there are 2 different ones. The one that [MENTION=8066894]CraiZJak[/MENTION] seems to be referring to is low volume and only 1 speaker used when taking a phone call on the speaker phone. This one seems to be solved. Then, there is another one, where you cannot hear the caller at all and she cannot hear you (call not on speaker phone) and the workaround is to switch to speaker phone. I can confirm that this second bug is still there with the latest release.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CraiZJak:
Nope, the bug I'm encountering is the same one as yours. You cannot hear anything from the other end. Only when you tap the speaker button twice to turn it on then off instantly which for some reason activates the sound.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dcscorpio76:
I found the culprit. I had to flash the latest Gapps and that fixed it. Not sure why that interfered with the wifi but all is well now. Thanks!!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Glad you found it. That is the value of XDA - providing a baseline to find where the problem is and avoiding dead ends - I have benefited many times from such feedback. Enjoy, it is really a good ROM.

---------- Post added at 07:56 PM ---------- Previous post was at 07:55 PM ----------

Interesting, because my sound bug is not fixed on the latest release.

---------- Post added at 08:02 PM ---------- Previous post was at 07:56 PM ----------

I can also confirm that selecting the USB configuration under developer options does not change the default configuration in the pop-up window when I connect my phone to my desktop PC via USB. The pop-up always comes up with "Charging", even when I set it to MTP in Developer Options/USB Configuration. Also, the options in that menu are different from the pop-up upon connection.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] thedauntlessone:
So I had a few bugs and one that was pretty messed up.

1) Rotation no sound (someone mentioned it)

2) Ear piece not working in voice calls (50/50) turning speakers on and off helps

There was one problem that I DO NOT KNOW if the rom caused.

What happened: I tried installing this rom and it gave me an error. Someone mentioned flashing the bootstack from the Lineage thread so I did. Flashed and no problems. Less than a week (starting Jul 13) I racked up nearly 3 GB of data, and went $50 over my data cap. I was browsing Reddit earlier at lunch for maybe 30 minutes and I used 700-800 MB just from that. It has never happened and I've always used the official Reddit app. Maybe its the bootstack, maybe its the ROM, maybe its the computer gremlin. No clue. I have never encountered this problem and have never went over my 6GB cap since I've gotten it 10 years ago.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
Nah I don't have that problem, it was someone else. But i used to have the huge 100% thing on my moto g and once with the axon 7. Using that calibrator app by NèMa fixed it every time, while rebooting did not.

But I never tried charging in recovery. Usually the battery level on the recovery is wrong though.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] chrisrodsa210:
No sir, not I
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
Screenshot edit? I don't have that option.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
I'm not entirely sure but i think it's the button that appears on the screenshot notification, i.e. after you take the screenshot, that says edit. You can select which app to use to edit it from Extensions
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
[MENTION=7799420]Choose an username...[/MENTION]

I don't have that button, only share and delete.

Maybe Nova launcher is somehow interfering as I noticed the name of this app on the generated files, hmm...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
Probably, but try to select the edit app as gallery
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
Screenshot of the screenshot here
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
That did the trick, thank you. It had been a long time since I last visited the extensions menu.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Abiram26:
I would like to install this ROM but the dualSIM is the only thing stopping me from doing this. (My mobile internet data goes through the second SIM card)

Does anyone know what exactly is the dualSIM bug? Or it is basically that the system doesn't recognize the second SIM card at all...

Would be nice to know if this will be a thing that will be fixed soon too (I think some other 8.0 ROMs don't have this dualSIM bug, so hmm..?)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JTruj1ll0923:
The DualSim bug, to my knowledge, is that while having two sims in you can not hear anything at all while on a call. I don't know of any other bug that comes from this. So if you can use another app to call such as Signal, you should be fine I believe.

All 8.1 roms for our phone (as far as I am aware) are built off of the same source. So unless someone such as [MENTION=7790189]Kranoner[/MENTION] on another rom has fixed it, I am pretty sure all have the bug.

I was trying to look at the logs I took a while back but I don't have a computer at the moment and it is too hard on just my phone. [MENTION=5492451]NFound[/MENTION] does not have enough time or know how to fix it without a lot of trial and error so I don't believe he is actively working on it. Unless some other dev is looking into it we are going to be stuck until the official release comes out and the roms can be rebuilt from there.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Krystalmyth:
NP love. Something I've liked recently is the Arise Army vdc. Its a bit extreme (as in test it out with low volume) but it seems to push frequencies frequencies that I simply can't emulate in any eq or combination of settings like it can by itself. I'm not sure why this DDC can do this but take a track like Hyperballad by Bjork and you will never hear a phone ever be able to reproduce the bass frequency in that song over speakers, even ours.

But here you can just ever so barely notice it (its that deep). Bjork made that song with the weirdest intentions because many people don't even always know the bass is there until they put good headphones on, then its omnipresent. So this is a pretty awesome DDC. Like I said. Turn off all other settings and keep your volume at 50% to start. This did allows me to keep as many modules on Viper off except for dynamic bass/monster which I drop to like 15%. (Extract to SD/Viper4Android/DDC. Remember to test it on its own and with It locked to Headset in settings)

I also now see why everyone loves Atmos so much. But can't figure out how to get it to work with Viper at the same time so I default to the above atm. Really wish I could figure out why this sounds so unique.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Teet1:
As far as I know, to get both to work you're supposed to get AML. with guitardedhero's Oreo dolby atmos port unity version and [MENTION=5357345]ahrion[/MENTION]'s viper4android for magisk you can get both working fabulously. Though I for one don't need viper4android. I prefer dolby all the way. In my opinion, too many modules just ruin the sound and uses unnecessary power. Now if only we can get hi-fi playback working on these Oreo roms....I would go back to AEX. I'm at stock for now as I've been experiencing call issues and the hi-fi playback not working since PNW's release.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] NFound:
Hi! In the latest version moved blobs (from the last Chinese oreo) and fixed configs in particular sound, by the sound of our expert only you.

Thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] machetie:
You're the best
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Krystalmyth:
Thanks I'll give that a shot. I've never actually been on stock myself. Been on custom ROMs since I bought it on Swappa. Kind of scared of going to stock and lose my internal or something lol. Hopefully ZTE updates the phone but who knows. Heaven knows they're not compelled to for a phone shafted by carriers and labeled spies by the US govt. I wouldn't blame them at this point.

I'd probably switch back if I had call issues too but I don't even have a carrier. I use VoIP for everything ATM he he. Not glamorous.

Hardly an expert. I don't even know what the DAC sounds like. My ear is blessed in swathes of ignorance. So for now I choose to enjoy all the little bits of love they can get and we've you all to thank for it. ~
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Thanks hun, I'll most likely PM you because I don't wanna hijack the thread haha.

Maybe you should start an audio lovers thread, could be great ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Teet1:
You said you have a pair of ATH-M50x right? So do I! You should give stock a try. It has usage of the DAC in its purest form. It has a toggle to turn on the super high quality DAC. You'll know it's on when you hear a small static noise and you'll notice the music becomes louder and not distorted. If you listen to hi-fi music with sample rates of 192khz and above, you'll notice such a HUGE difference in sound. Having the high quality DAC on turns off Dolby though. Having it on with Dolby forced gives it so much noise and not worth it. Fortunately if you have it on it'll turn off by itself when you play music with headphones and turn back on if you use the speakers. I love Dolby Atmos through the speakers with surround virtualizer on

If your data is unencrypted, you can install stock by using DrakenFX's back to stock files. I recommend using B32 and not the latest version B35 as B35 for some reason stops using hi-fi playback. After you clean flash B32 just install Magisk and then reboot after and your internal won't be encrypted and deleted. Of course, back up your stuff just in case ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] NFound:
To correct work DAC AK4490 we flashing is new BootStack, based on Chienes Oreo 8.0.0 B10

Download

temporary no recomended to install
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Oki:
BEGIN OFFTOPIC

I see you like deep bass, but you are applying that V4A profile only partially. The V4A ARISE Army profile (not just the DDC) delivers a massive amount of bass. You can download my full collection of V4A profiles from here. Complete ARISE profile is there, it configures the irs file, and all the other parameters. You just need to unzip the contents in your internal SD, then go to V4A, tap on the hamburger menu and select load profile. ARISE Army is one of them, but you can find also other profiles for testing, audiophiles, and my basic one. Food for your soul via soundwaves.

END OFFTOPIC

It would be nice to substitute the AudioFX by Viper4Arise. I really do not know why it is not common to find V4A as the default audio processor in custom roms.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dwnoel:
It is working on STOCK 8.0 roms only, where many others things are not at AEX level ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kossie12:
I installed new bootstack on my G and rebooted fine.

When trying to update AEX I get an error, i attached the TWRP log.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Draygon:
Is Dual SIM working correctly with the new B10 Bootstack?

Since this one is based on the official Axon 7 oreo, this could fix the call bug.

Sadly I cannot test it right now. Would be nice to get feedback of someone who can.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Soyunamortz:
How do I use these new bootstock on my axon 7 u version ?

Do I flash the bootstock

Flash ROM

Gapps

Magisk ?

It's that the right way to do it ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jrotaetxe:
Hi

The new bootstack freezes my Axon...

Have to go back to the old bootstack.

and

Error 7 if instaling new boot and then AEX...

So installing old BS, then AEX and then new BS to see if then runs ok

Regards
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Cablespider:
I flashed the new bootstack on my U running 4/10. It booted fine. No problems to report as of now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Chiko-HH:
+1
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
A2017U "American Boy"

Tried to start clean on the first try, not working. Bootstack flashes fine. But, AEX gives me "Error 7". Looked like "tz." something was not compatible.

Sorry I did not get a log, I have never done one. It's the middle of the day here and I needed my phone working to research. I can recreate the issue later if a log is needed.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kitcostantino:
"tz" is trust zone. i have seen this error when trying to install an "x" rom that requires "y" bootstack.

edit: seeing the b10 no aboot bootstack makes that make a bit more sense. now i gotta read more. ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Teet1:
Since it is now based on official ch inese Oreo, do we have to use your TWRP exclusive -6 for official oreo, or are we able to still use -7?

edit: after clean flashing, phone LED blinks three times and turns off and no boot

edit again: okay well so first I clean flashed the bootstack and then the latest AEX and got error 7. I removed the trustztone line from the installer script for AEX and installed successfully. After reboot, I saw the new green ZTE logo which shows me it was successfully installed. however, the LED blinked 3 times and the phone turned off. It kept doing that after a few starts and nothing happened. I went to TWRP and noticed it was at -6. I reinstalled the B32 oreo bootstack and reinstalled AEX and TWRP -7. Phone booted fine. I set it up and went to TWRP again to flash the new Oreo bootstack. It doesn't seem to be working now as the ZTE logo isn't green anymore and the recovery is still at -7. I tried to play hi-fi music sampled at 192khz and it still could not play it, so I assume it was not installed correctly. What is wrong?

after wiping everying and flashing the bootstack first like the first time, it is no longer installing although the aroma installer says its successful. It doesnt seem to have changed because i can install a fresh downloaded zip of AEX just fine without error 7, meaning that I still have the previous B32 bootstack installed.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Aviver:
Thats 100% correct, thats what happens with me too.

I think this bootstack is only for the stock rom
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kingracer:
You've just had to install it over b32 bootstack and installed aex without changing twrp or anything. For me it's working just like it should
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Fixing the update issue is really simple, go to install script inside the ROM and remove the trustzone lines.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Teet1:
I did multiple times. If it's working, did you get a green ZTE logo and did TWRP change to -6?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kingracer:
Neother of that, but it think logo becomes green only on cn model?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] QuantumFluxx:
New Bootstack works great so far on A2017U. Already had 20180410 installed when I flashed. One caller familiar with the ongoing echo problem when using loudspeaker at high volume reported that the echo was greatly reduced. Thanks, NFound.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Teet1:
Nope. It turns green because of nfounds edit. I looked at the splash logo for oreo boot stack and it is green. So that means if you booted fine and the logo is blue then it didn't work. Mine did at some point but did not boot
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kingracer:
Lol, but how is it possible if the script succeeded?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Teet1:
Possibly it says it succeeded but didn't do anything. Now that I think about it I was on TWRP-6 when I flashed it and it worked... But right now I cannot test it
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kingracer:
Well ok I'll ask NFound about this strange behavior in tg group... I'm very interested in such thing) because it looks like it worked...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Teet1:
It didn't look like it did. Because I installed AEX after flashing and it was supposedly successful and didn't give me a trust zone error which means it was still on B32 boot stack. Idk if it's only me. And if the boot stack fixes the DAC then it should let me play 192khz songs. But it didn't work still
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kingracer:
It should not give you an error because it's still made for aex 5, but about DAC I'm not quite sure...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Teet1:
But maybe aex wasn't made for this boot stack. The first time i flashed the boot stack I did get the error. I had to remove the tz like to be able to flash. After I did that I rebooted and saw a green ZTE logo that was a bit off center similar to nfounds exclusive TWRP. Then the screen turned off and the LED blinked three times and then nothing. That's all it did until I went to twrp and clashed the b32 boot stack and twrp-7 and everything went fine except now it seems flashing the new bootstack doesn't seem to do anything anymore.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kingracer:
Ok then, I'll wait for dev to response :) but still i hope that it's working :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] chrisrodsa210:
U version....Flashed the new bootstack on top of 4/08 went smooth until I realized there's 4/10. Tried dirty flashing 4/10 but got error 7 in TWRP. So I flashed B32 bootstack, then dirty flashed 4/10, rebooted and flashed the newer "O" bootstack. All is well, and works fine. No green logo, still blue btw.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] greencartim:
So I have two Axon 7's, one with the B10 bootstack running AEX and the other running RR N with an unkown bootstack. They both can play 24bit/96hz flacs fine. Also the B10 phone has a blue ZTE logo at start up. They are both A2017U.