yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JTruj1ll0923:
Hmm... Well since there is a boot.img in the Lineage zip I would imagine that is the right one to flash but take a backup of your working system first as I may be wrong since I'm no expert. Then once your backup is done I would try flashing just that boot.img with either TWRP or Flashify. Good luck!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mulle01:
Does the official version of this fully support A2017G? I'm getting Error 7 when flashing, so the checks doesn't seem to like me having the G model...

Or could I just modify the updater-script, in case A2017G is supported?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dwnoel:
Did you installed both "A2017X_B15_Universal_Bootloader" and "A2017G_N_Modem" ? (usual to get error 7 if not)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mulle01:
I'm new to android modding and stuff, but a quick and nooby question; is that needed if I was on 7.1.1 (1.2.0B04) before unlocking and installing twrp?

And no, I didn't. Have I ****ed up big time? Do i need to revert to stock and all that pain now? lol
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Nah just flash them over and you should be good to go :)

---------- Post added at 11:02 AM ---------- Previous post was at 11:01 AM ----------

the G model is supported, I'm running it on my G just fine and yes you can just edit and delete the first lines of the updater script and be ok
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mulle01:
Thank you.

Edit: I think it's stuck in the boot animation...

Edit2: Nevermind, it works, but it says "Welcome to your A2017U", normal?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] name2:
That's strange. When I play a 24/96 flac over speakers, I get:

07-31 11:24:44.546 712 16437 I audio_hw_utils: audio_extn_utils_update_stream_app_type_cfg Allowing 24-bit playback on speaker ONLY at default sampling rate
07-31 11:24:44.546 712 16437 I audio_hw_primary: select_devices Selected apptype: 69940
07-31 11:24:44.546 712 16437 D soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_id 3 of type 0 for Event 3, with Raise=0
07-31 11:24:44.546 712 16437 I audio_hw_utils: audio_extn_utils_send_app_type_cfg PLAYBACK app_type = 69940, acdb_dev_id = 207, sample_rate = 48000
07-31 11:24:44.546 712 16437 D msm8974_platform: platform_can_split_snd_device: snd_device(2) num devices(1) new_snd_devices(0)
07-31 11:24:44.546 712 16437 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 207, path = 0, app id = 0x11134, sample rate = 48000

When I play the same file with headphones connected, I get:

07-31 11:25:07.377 712 16454 I audio_hw_primary: select_devices Selected apptype: 69940
07-31 11:25:07.377 712 16454 D soundtrigger: audio_extn_sound_trigger_update_stream_status: uc_id 3 of type 0 for Event 3, with Raise=0
07-31 11:25:07.377 712 16454 I audio_hw_utils: audio_extn_utils_send_app_type_cfg PLAYBACK app_type = 69940, acdb_dev_id = 207, sample_rate = 96000
07-31 11:25:07.378 712 16454 D msm8974_platform: platform_can_split_snd_device: snd_device(8) num devices(1) new_snd_devices(0)
07-31 11:25:07.378 712 16454 D ACDB-LOADER: ACDB -> send_audio_cal, acdb_id = 207, path = 0, app id = 0x11134, sample rate = 96000

However, when I play a 32/192 wav I get

07-31 12:58:36.936 712 1049 I msm8974_platform: platform_check_codec_backend_cfg:becf: afe: Codec selected backend: 0 updated bit width: 16 and sample rate: 48000
07-31 12:58:36.936 712 1049 I msm8974_platform: platform_check_codec_backend_cfg:becf: afe: Codec backend needs to be updated. new bit width: 16new sample rate: 48000 new channels: 2

for both speakers and headphones. The file plays back fine, though. Not sure what's happening here. And not that it matters anyway, see http://www.androidauthority.com/why-you-dont-want-that-32-bit-dac-667621/.

Anyway, in /system/etc/mixer_paths.xml in the section

<path name="headphones-hi-fi">
<ctl name="AKM HIFI PW" value="on" />
<ctl name="AK4490 BICK Frequency Select" value="64fs" />
<ctl name="AK4490 Lch Digital Volume" value="255" />
<ctl name="AK4490 Rch Digital Volume" value="255" />
</path>

if you lower the "digital volume" you get no headphone output at all. This seems all the proof you can expect that the AK4490 is actually being used for headphone-out.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
[MENTION=4911249]Unjustified Dev[/MENTION]

Any reason my commit https://review.lineageos.org/#/c/176689/ hasn't made it into the roster yet?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Totally normal, you're good to go man, enjoy :)

P. S. there is a button to say ths thanks ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] pinkywinky:
The HIFI DAC is always used (thats how it was set up in the roms). However it is up to the individual apps on whether or not the will support playing the high quality songs or not. While the audio is going to the HIFI DAC, which sounds great), unfortunately android apps will lower the quality if they don't detect a HIFI phone. PowerAmp currently does not (as you can see by it being "snapdragon 24") play true HIFI. I'm hoping that they add it, but there currently is a way to get around it and play 16bit 192Khz (no way to get 24bit yet). You need to add ro.lenovo.hifi_support=true to your build.prop file.

There may be other apps that play the audio correctly, but from I know only the original ZTE music app will correctly play a,ll the HIFIfiles.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] name2:
I'm afraid nothing of this is correct. The use of the AK4990 is "hardcoded" in Lineageos. Every app that sends audio to the headphones automatically uses it. I have verified this for Vanilla music player, Shuttle music player, the stock Android music player, Odyssey music player, VLC, and the Newpipe Youtube app. You can verify it (as I said above) by changing <ctl name="AK4490 Lch Digital Volume" value="255" /> in /system/etc/mixer_paths.xml. I'm listening to 24/96 flac files here. I also got a 32/196 wav test file to play flawlessly, only the log said it was playing it as 16/48 (see my above post). I don't know what's up with that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] pinkywinky:
Ok maybe what I said was badly worded... but thats exactly what I explained (or atleat tried to). The HIFI DAC is

always

used, however its up to the music apps to play the file in high quality, and if they don't believe the phone is capable of it they won't, which is why you are only getting it to play in 16/48.

Unfortunatley with our phone being unpopular I'm not sure if any app will at all, but the build.prop tweak does get you 16/192, and I'm sure once they get the lenovos working it will play 24/192, however we will have to wait for that.

Regardless of what the DAC is capable of, if the music app doesn't think it should play the audio in high quality, it will convert it. Its a limitation of android (or so I've come to understand). If you want to play true HIFI, you currently have to use the original ZTE app.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] name2:
So what you're saying is, the good dac is in fact being used but the audio players decide to alter the audio information found in the audio file? I don't think it's up to a music player app to decide on downsampling or downsizing the bit depth of audio data; I'm sure that happens at driver level. Try playing a 24/96 file and do a logcat. For me at least, it reports playing at 24/96, regardless of the player. (Even if it does downsample and change bit depth, it doesn't matter because at the time of playback you won't hear the difference.)

The reason that on the stock rom only the zte music player could use the akm dac is probably because zte didn't make it properly accessible by the android audio hal/framework/api/whatever.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] pinkywinky:
Yes I believe the music app does decide the whether or not to downsample or not, much like how it would downsample if it was truly not capable of playing the file. If you read through the PowerAmp forums you'll see that its a big issue that true HIFI is not supported on many devices, but unfortunately it seems like its not a priority for them to fix it. Instead they are fixing the UI (there's only one programmer so I don't blame him for being overworked).

I saw in your logcat that it was playing at 96000 but no bit depth? i couldnt get ti to display at all on my device so Im not sure how you got that... I think I have a lot of my logs turned of by using war_mod, I'll probably turn it off sometime just to see what I get.

Honestly I could be entirely wrong with this, but I got my information reading through http://forum.powerampapp.com/topic/...e-using-poweramp-build-704-before-requesting/

Specifically quotes like this are what brought me to this conclusion:

just out of curiosity i'm attaching my audio policy, FYI i do have to toggle a switch to actually activate the sabre DAC. maybe that's whats causing the problem.

The debug Poweramp build now has support for Lenovo HiFi 16bit/192khz output (Android 6.0). It's much better than standard output, even with just 16bit resampling. When Hi-Res output is activated in that debug Poweramp build, HiFi output is used, no matter if the HiFi system switch is enabled or not.

From what I understand, ZTE configured our audio path a little weird, so any app will have to have the correct tweak in order to stop them from re-sampling, but we don't have a popular device.... Its the same reason why no audio mods truly work like AINUR or V4A (but V4A will always re-sample your audio, it kinda sucks).

Only real way to test if its working is do sine sweeps and check them at the output, but thats way beyond me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] name2:
Lol sorry, I failed to paste all relevant lines. So when I play a 24/96 file with headphones plugged in, I get something like

08-01 01:00:45.552 712 5133 I msm8974_platform: platform_check_codec_backend_cfg:becf: afe: bitwidth 24, samplerate 96000 channels 2, backend_idx 0 usecase = 3 device (headphones-hi-fi)
08-01 01:00:45.552 712 5133 I msm8974_platform: platform_check_codec_backend_cfg:becf: afe: Codec selected backend: 0 updated bit width: 24 and sample rate: 96000
08-01 01:00:45.552 712 5133 I msm8974_platform: platform_check_codec_backend_cfg:becf: afe: Codec backend needs to be updated. new bit width: 24new sample rate: 96000 new channels: 2
08-01 01:00:45.552 712 5133 I msm8974_platform: platform_set_codec_backend_cfg:becf: afe: bitwidth 24, samplerate 96000 channels 2, backend_idx 0 device (headphones-hi-fi)
08-01 01:00:45.553 712 5133 D msm8974_platform: platform_set_codec_backend_cfg:becf: afe: SLIM_0_RX Format mixer set to 24 bit for 1b000000 format
08-01 01:00:45.553 712 5133 D msm8974_platform: platform_set_codec_backend_cfg:becf: afe: SLIM_0_RX SampleRate set to KHZ_96

whereas without headphones I get the line that tells me about the speakers only supporting 48 kHz in 24 bit depth (I did paste that).

No idea why you're not getting that info from logcat. I'm not doing anything special, I get it both in a terminal on the phone and over the adb shell.

By the way, it seems that alsa is being bypassed by our rom since when you try to read the alsa /procs at /proc/asound/card*/pcm*p/sub*/hw_params, you only get 'closed'. So in my understanding that means that the audio is fed to the hardware in a somehow more direct way. . .
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] pinkywinky:
Yea, it seems like the way our ZTE was developed it ran down a different audio path than normal. Apparently there are some proprietary files that were needed to get the audio fully working. But I guess I was under the assumtion that there was some software interface needed to play the files correctly, but I honestly could be wrong.

Are you on lineage using poweramp experimental to get this? Because mine never seemed to work without the build.prop tweak. I honestly think I'll buy an analyzer like MusicScope just to actually see what kind of output I'm getting, though I'm not sure how accurate it is. Might play around with it sometime seeing how it is really cheap.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] hjjiang:
what build.prop tweak did you do to get it working?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dhammika71:
I also have the same issue. Looks like a bug.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mart Son:
Yesterday 49%, today already 56% done. Thanks alot. When it is done i will be back to lineage. Great work!

Gesendet von meinem ZTE A2017G mit Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
Just so you know there are not many issues that are unpatched. This is largely an exercise in verification.

That said, it's more secure then stock already and will continue to improve daily.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kdp162:
I'm sure everyone appreciates the effort Tom
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ssirK:
a CVE patch a day keeps the hacker away! :)

thx again [MENTION=4126377]tdm[/MENTION]
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Zephyre14:
Tl;dr?

No offense to anyone, i am a big proponent of telling people to read whole threads, but this is 318 pages long.

Can someone give me a tl;dr of what I need to know that is not straight on the first two posts? (Links to any important posts or at least which page it is on would be great too)

I am new to the forums and am looking at getting the Axon 7 and considering it would be for Verizon (since I get no service with any other carrier where I live), which means I will need a ROM to make everything work "perfectly" on the network. I have been recommended this the LineageOS. Sooooo any advice/help/anything of the sort, would be wonderful.

Thank you all.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
I have the phone running Verizon as well. The ROM has been Rock solid since I have been using it. I get hdvoice when calling other Verizon callers but can't use wifi calling (I don't use that feature anyway).

The most important thing is to get a nano SIM activated with another phone. Verizon can't activate the axon 7. Use a friend's phone or another available phone. Once its activated , you can put the Sim in the axon 7 and it will work.

On your Verizon account it will show as a non Verizon device but things will work fine. Good luck.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
Pic for info
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
Seeing all of the work on the CVE's makes me wish we had a real vulnerability testing thingy for all devices.

The closest I've ever seen is this https://github.com/AndroidVTS/android-vts

made by a legit security company but it got kicked out of the Play Store. To actually test vulnerabilities you kinda have to trigger them- which is what they did I think.

At an old job we ran Nessus scans on all of our devices. I volunteered to remediate desktop issues. It's funny because we had these little print servers connected to printers and one day we had a bunch of printers start printing out pages and pages of gibberish until they unplugged the printer.

Firmware patch plugs the hole but it'd be nice to point to a tool that pointed out to manufacturers what their devices are really like. Besides, I suppose it'd make work like what [MENTION=4126377]tdm[/MENTION] is doing much easier.

Phones are kinda the redheaded step child of computer security. It's like we've resolved that it could be inconsistent. Right now it looks like checking by hand is the only way to go. I dunno if Nessus or OpenVAS have tests for mobile vulnerabilities or if it's even possible.

Rambling
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
Yes I've thought of making a vuln scanner/verifier on occasion. It would be a rather large undertaking, though. Even larger than my current project (documenting and patching vulns across 3 kernels), which seems like it will take some 4 weeks or so.

Some vulns are easier than others to verify. Information leaks are relatively easy to verify. Race conditions are a bit harder. Some require potentially destructive behavior (eg. DirtyCOW). Some require access to the network or even a remote system (certain WiFi bugs).

So a general vuln scanner (even with root access) isn't quite so easy. But with a fair amount of work, it could be done and it could check most non-network vulns. Unfortunately, I don't have the time or interest for that right now. But it would be a cool thing, I agree.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Pippinkid:
I need a lot of help here. Any help at all really. I have tried everything just to get my data to work on this damn phone but since I got it I have been unable to make a single damn call.

I just got this phone like a week ago from the warranty plan from a cracked screen so I really don't want to take it back again. So I'm trying everything just to get service. It's super frustrating man. I have MetroPCS and another phone (Note 4) and it works perfectly on that so I know that's not the problem. I tried stock from marshmallow's b20 to the latest 7.1.1 with no success. So since then I've obviously gone through the whole rooting phase and installed LineageOS and prayed that I would receive service but still nothing...

Am I boned at this point or is there any hope? Thanks in advance for any help!

Edit: Do I have to call Metro and register my IMEI? Just read online I might have to do this could this fix my problem?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JTruj1ll0923:
Yeah I believe calling them would fix it. I worked at a cell phone repair shop and I believe Metro needs the IMEI tied to the account. Good luck!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Pippinkid:
Finally got my sim card working by calling Metro! ... Everything works texting, data, even calls... For the most part expect when I'm on the phone people can hear me but I can't hear anything. There's no ring, no sound at all. No nothing!

Has anyone else had this problem? If I could get this fixed it will be the PERFECT daily driver! Any tips??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] soren25:
Yes, this is a common problem which has a workaround, but no actual solution. Next time it happens, toggle speakerphone on and off again, and it should work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
Finally hitting actual unpatched issues, starting around 70% (currently at 73%). The fixes are coming pretty steadily now. Maybe I can get this done next week.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JTruj1ll0923:
I could never get that to fix it. I simply had to play music at full volume for a few seconds and then retry the call. It would then work for a long time. So hopefully either of these will work for you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TimoVerbrugghe:
I can now confirm that while running LineageOS 14.1 (based on Android 7.1.2) on the phone, my XBOX One Controller DOES NOT WORK while connected over OTG, even more, I experience the reboot loop issue.

Xbox One Controller does work when connecting over bluetooth.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] borijess:
It is. Did you see this post.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BritSwedeGuy:
Thanks - I was looking for "Daydream" not "VR" ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kebuder:
Thank you for the great work! I have been running lineage for 3 days now and must say its blazing fast and very good.

I have some minor problems that i think no one has brought up yet:

- clock app crashes on boot. I installed a thirdparty one that works.

- camera focus on tap (or focus in general is bad)

im running a 2017G version.

Rest works perfect :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ChickNrippR:
Sorry for off topic:

Is there any hope for ZTE Axon 7 mini to get such a fantastic ROM? :crying:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I don't own the device I can't say. If you have twrp, I'd say yes.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Wipe data of the clock app. Gapps might be replacing it with google version.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
It gets hot because I can't handle ZTE thermal changes it depends on a property that isn't set normally. It's something that can be looked into later.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] cms062407:
Hey, so, lastnight, I couldn't play around with the new OS..but now that I am awake, I can :)....under the main settings screen, under Storage, it says I have -35.34 of 14.92GB available....how do I have MINUS 35GB available?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimbo77:
That's a known issue for now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tjablonowski:
Flashed Last Night

The procedure to get unlocked bootloader on this device is a pain.

Rom itself looks good stable and power efficient. Only bug I have found is that the Bluetooth state is not carried over during a reboot. It always comes back from a reboot in the off state. Audio thru my Google Auto in a Ford Escape is great.

Everything else looks good, waiting on the fingerprint scanner fix...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] cms062407:
alright, thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] XCristiano1992:
Great ROM! More than 7:30h of screen on time is no Problem with this!

Gesendet von meinem ZTE A2017U mit Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jim262:
Is fp scanner fixed as reported in another thread?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimbo77:
Yes, but the new build with the fix hasn't been published yet. Search the thread before posting non dev related in this thread, that should be reserved only for the one in the Q&A Section.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mart Son:
Is there a possibility to revert back also on the G variant like b29 for the US model?

Gesendet von meinem ZTE A2017G mit Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
Just little info, FP problem is been found and fix is been in place and kernel Sources of LOS will be available as soon Official N start rolling out.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Android4thewin:
Good to know, thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Snaptraks:
I'm curious as how you flashed the stock zip, with TWRP or the stock recovery? I'm almost certain TWRP doesn't handle stock update.zip, but I'm still unsure.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
The zip isn't an update so it's not checking validity of any partition. It's just an original firmware zip and can be flashed from TWRP or stock. Doesn't matter as it will flash your recovery to B29.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] crazynitro:
i flashed it with twrp then i reflashed twrp and rooted after i logged into my apps. everything works perfectly.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] thehebrewhammer:
I posted a few pages ago offering to help implement wifi calling, if I knew what the issue was. unjustified dev, could you shed some light?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
I think we are just missing the WiFi calling settings in framework overlay in general.

For example:

https://review.lineageos.org/#/c/159439/

Don't forget that all features have to be tested/reviewed. Maybe Carl has no WiFi calling feature with his provider and therefore didn't enable the feature yet?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] thehebrewhammer:
Awesome. If it really is a matter of enabling it in settings, I'm sure one of us can merge the files from the op3 build into this one. I haven't experience here, but I'll see what I can learn on my own. In the meantime I encourage the community to try a "transplant" from that build and see what that produces.