yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] whoiswes:
Confirming this worked for me, with one additional step needed - post boot, I opened the Dolby control panel and made sure the power indicator button was OFF (or you can disable the app). After that, speakers, headset, and bluetooth music/notifications all sound relatively close to stock (not doing any critical listening beyond does-it-sound-like-crap). Phone earpiece volume is still very loud but not distorted, and the microphone sounds like it's picking up voice fine for the other side of the call. With phone volume all the way down things were tolerable in testing (holding one phone to each ear and alternately muting - fun times).

Just wanted to add my experience as this seems to be at least a partial workaround for some of the audio issues that are outstanding.

Thanks [MENTION=1485752]lanco[/MENTION]rt for posting!

Thanks [MENTION=4911249]Unjustified Dev[/MENTION] for maintaining!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
Hey thanks bro...good update and testing
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcusah123:
Hello,

Flashed in B29 bootloader. I have to say no change on navigation on google navigation it's still 2 to 5 minutes and won't activate inside, I have to be outside or in my vehicle. A side note I leave the location information ( GPS stuff ) off until I need it to save battery just like I did with my Galaxy Note 3. Should I have cleared cache or anything?

Thanks for the help any other suggestions would be nice. Maybe I need B09 or B27. I don't know but it's a tad maddening to have to wait 5 minutes for the GPS to start up and get a signal and start navigation. On a side note my bootloader and baseband versions are a dash without a number when I reboot to bootloader and I didn't know if this mattered. Could it be how I unlocked my bootloader?

I just want to know what's going on to cause this behavior.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Abiram26:
No, I never had such issue... Did you change something that would cause errors within the Android system maybe?

2 questions;

1. Does it fix stereo on the phone's speakers? Easiest way to test this is by watching a YouTube 'left and right stereo speaker test' video. The 3,5" audio jack output always worked fine for me; also stereo... But with the phone's speakers one of the two channels doesn't get played for me and it's just playing the same channel over both speakers which isn't really stereo...

2. Do you still hear distortions with the phone's speakers when having the volume up to max?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] whoiswes:
1. Nope. Good catch. I'm getting left channel only, confirmed from multiple sources.

2. Yep but it doesnt start distorting until it's almost at max. With Dolby enabled it distorts at under half volume.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
Nah it doesn't help much with the distortion at max volume through the speaker.....Slight improvement but I can't call it a fix....But it's great though the headphones....Gives u stock-like quality.....I'll try to find a fix for the speakers tho
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shia786:
I think the best option would be Togo back to stock and flash both those files, bootstack and systems

After booting to stock ROM, test if GPS works, after that go back to TWRP and wipe everything and flash cn13 build 28th of December

Then flash Gapps, I did micro

And then try if GPS works,

Those are the steps I did,

You can't flash b09 as you have a U model and that's for G only, you can flash the system but not bootstack but there is no point in that

Maybe try b27, I haven't tried on U variant as I have G,

Basically, I was on cm12 build 28th to test if GPS worked for me

After that it didn't so I went to a custom ROM Z.A.m.X or something like that which is based in stock so there shouldn't be any issues

I needed to tether which never worked so I though maybe it's aROM issue, later that same day I tried GPS and it wasn't working on the custom stock ROM either,

I then thought that it has to do with firmware as this should of worked, I updated to the latest as suggested by other members and then flashed cm12 28th December build with Gapps micro and GPS worked like a charm so it was definitely firmware issue or bootstack or whatever
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
Nice! BMC initialized an Official LineageOS repo for the Axon-7. :-]
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
What's ur source of info??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
Ehm... obviously this?

https://github.com/LineageOS/android_device_zte_axon7
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kdp162:
I'm friends with a Lineage official DM and can confirm builds for lineage 6.01 will be starting
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
Oh thanks....Y no 7.1 tho??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kdp162:
It'll get there, be patient.. If you can believe ZTE there should be N in the next few weeks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] FadeFx:
Have you seen anyone working on 7.1 for the a7 yet? No, because nobody did. There was a 7.1 build on a shady website, but it was not functional.

Gesendet von meinem ZTE A2017G mit Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bkores:
never mind
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcusah123:
Maybe I need to update my gapps? I'm really not sure, the GPS works, it just takes 5 minutes approx to even start navigation which is annoying. This occurs when I have not had "high accuracy" turned on ( GPS off ) for an extended period of time which shouldn't happen. It's maps version 9.42.3.

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shia786:
Yeah maybe you need to update Gapps

I am not having that issues mine locks straight away

And before it wasn't locking or was being laggy
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcusah123:
I was indicating that NAVIGATION takes 5 minutes to get a lock and start navigating which means the GPS isn't getting a fix quickly. Remember I have GPS turned OFF most of the time and turn it on only when I need it. This saves battery.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] FadeFx:
GPS Doesnt drain battery if it isn't used just because it's enabled. If you have apps that use GPS in background, these are faulty as they should use network location instead. Also a fix from non used but enabled GPS takes the same time as from disabled GPS.

My guess is that there is either a problem with time servers for agps or there are devices with different GPS chipsets.

Gesendet von meinem ZTE A2017G mit Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcusah123:
What happens is that it takes 5 minutes to start navigation. It uses data to get a location but navigation only starts after 5 minutes. If I navigation to work, then after that if I start navigating an hour or two later it goes much faster and does not have to wait. I understand the chip issues etc, but I don't understand why this is happening for me and not others. A fix would be REALLY nice. I can't get a GPS lock inside and so I don't understand.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
My understanding is that GPS lives in the snapdragon so no differences there whatsoever
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dbekan%5:
Could be. Is there a tool to read the usage? Task manager and RAM Option in Settings doesn't show me the correct and actually usage.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sounreal:
Are you 100% sure?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] FadeFx:
I had GPS enabled permanently on all my devices and never had a battery drain due to this. So yes, I am sure GPS only drains battery when in use. And I am sure that apps should not use GPS in background because they should not need so accurate location data. If they do, they are to be considered malicious.

Gesendet von meinem ZTE A2017G mit Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
+1

If I was having trouble picking up location I'd check to make sure I'm on the latest baseband

Baseband: M8996FAAAANAZM-1.68528.1.71432.1

Make sure time is correct

And test if a GPS app shows a bunch of satellites

If that didn't work I'd go back to stock
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcusah123:
The GPS test app shows satellites inside but isn't actually showing signal strength. Maybe I need an updated radio driver. I bought my phone in November of 2016 and it's the A2017U version.

I have the same baseband version as you suggested. Would clearing cache help at all?

Thanks and going back to stock would screw up my settings and my apps and data probably. I'll see about that. Although the bootloader does not say what version it is when I boot to bootloader would this be an issue?

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
In regards to nomenclature, the baseband is your radios (GPS, Bluetooth, cell) firmwares.

and the bootloader is sort of a pre-boot partition so all a bootloader does is serve to start Android. So it's not really too important except if someone says you need a newer bootloader.

If you use this app https://play.google.com/store/apps/details?id=com.chartcross.gpstest

How many satellites are you seeing? You should see both circles and triangles. The circles are U.S. satellites and the triangles are GLONASS (Russia's GPS satellite network.) Like if you're seeing 7 or more it's finding satellites well enough. It might actually be a hardware/power issue if it couldn't get a lock but I dunno.

As for not seeing the version strings when you're actually in the bootloader- mine doesn't either. I'm thinking ZTE must not've exposed the version strings or something- maybe just forgot or something. I know I've had ROMs not show it in the Settings/About screen as well until someone fixed showing it so it's there but something isn't showing it to us.

I don't think clearing cache would do anything.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcusah123:
Hello,

Right this second inside I get 23 satellites seen, no signal strength and no fix at all. Basically I can't get a fix inside and navigation won't start for up to 5 minutes outside regardless of lock or no lock apparently.

Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ChazzMatt:
Because you are turning off GPS and other people don't do that?

As for getting a lock inside, depends on building material to obstruct satellites. Best way is outside in clear view for GPS lock.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
What he said. If you're toggling your GPS off- no one does that anymore because it doesn't conserve anything. Plus, if you're indoors I don't think you'll get a lock unless you turn on all of the location accuracy settings that try to guess where you are via what Wi-Fi, call and Bluetooth is around you (they supplement GPS to guess if you're indoors.) Other than that, it would be nice if we could port Qualcomm's iZat feature which the stock ROM also leverages. Regardless, if you're seeing more than 8 satellites I'd say GPS is very much working for you.

It's just where you are trying to get a lock. Google how GPS works. It requires line of sight to 4 or more satellites.

To supplement GPS look at the high accuracy option as well as the Wi-Fi and Bluetooth scanning options in the 3 dot menu in the upper right corner of the location setting screen. Google, Microsoft, Apple, Firefox, Qualcomm, and others all collect names of wireless networks around you to supplement their location services for the exact reason that you're in (being indoors.) By using land-based signals your phone go "well, I can't see a bunch of satellites but these cellphone towers are around and those Wi-Fi access points are around. Someone else was around these things and did get a GPS lock. You must be here." Make sense?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcusah123:
Hello,

Sure thing, I will try leaving the GPS on. I have to note that regardless of turning GPS on or off on my Galaxy Note 3, it never had THIS issue EVER. I'm not sure why I am having this issue NOW with the same behavior with my new device and not on the old. Side note is that even if I get a GPS lock with GPStest, it still takes 5 minutes to start navigating. If I successfully start navigating and switch it off and back on say an hour later I do not have this issue.

Thanks for all the help.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
Yeah. Aside from that it's all hardware. Like this phone gets better Wi-Fi than my Nexus 5 but the cell signal isn't as good and the GPS is ok I guess.

Some people try an app called FasterGPS or similar apps which let change some little things with how GPS works you pick more local time servers and stuff. That may help.

https://play.google.com/store/apps/details?id=org.fastergps
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
Do you have any details on the timeline? Wouldn't mind getting January security update :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kdp162:
No I haven't heard but I'll ask around
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] spacemanvt:
what does that mean exactly?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kdp162:
It means there will be official nightly builds for the Axon 7 from LineageOS
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TheBigG:
That would be awesome [emoji106]
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] spacemanvt:
This will be different from what unjustified is doing correct?

Any timeline or official word of this?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kdp162:
Haven't heard when it's starting but I'll ask around
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimbo77:
Correct me if i'm wrong but i belived Unjustified is helping with this as well if you see the github it seems he has send a few commits to the code :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] vizzze:
The code on lineage's repository is unjustified's, they just moved everything there and started renaming the project name in the code.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Yes, the majority of the device bringup had been done by me, but now we have other contributors from the team you all have yet to meet. Two or more have already commented in the thread.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Darkguy:
That's awesome! Has there been any contact with ZTE whatsoever or any info on when/if they will make good on their promise for support?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I haven't been in contact with ZTE for over a month. For now everything has been done by the team.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gachmuret:
Is there a certain reason why you don't strengthen the contact with ZTE so they may help out with their insider knowledge (as for the purpose of sound distortion) instead of searching fixes out in the dark?

And I don't ask to offend you... Just to understand....

And IMHO you should become official LineageOS dev for our device :good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
I want to ask a question. I'm sorry if it is forbidden to ask. You can delete my post if it is.

Why Marshmallow, not 7.1.1?

---------- Post added at 01:05 ---------- Previous post was at 01:01 ----------

I think he is or will :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ChazzMatt:
That is probably ZTEs choice not his. ZTE doesn't understand why we don't just like their stock software.

Plus ZTE has proprietary audio stuff they can't give out to him
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] thefiqs:
Sorry for asking if it is already answered. I just checked OP and the last update is 23/11/16 is it correct?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gachmuret:
Well, most of the drivers we use on computer systems are closed source... But the developers can show us, how to implement their proprietary stuff properly... As they integrated their stuff in open source android themselves
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] project_86:
Is anyone else having issues with their voices sounding really distorted to callers? I spoke with my fiance this evening and she said I sounded like I was talking through a phonograph.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
Yes....It's a known bug
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] p_shad0w:
So i have been following the github and saw some commits related to audio last week. Are those related to the distortion?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
Yeah I would assume so....But what u could do is try calling through a headphone cause there's no distortion when playing audio through the headphones (for most people)....Then we'll know for sure
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] FadeFx:
The question is, will you be the device maintainer?

Gesendet von meinem ZTE A2017G mit Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
Because we don't have a stock 7.1.1 ROM yet to pull needed files from, or the matching kernel source. Some of the stuff can be pulled from other devices, but some can't.

The big trick will be what happens if ZTE ends up releasing only 7.0 and not 7.1 (or with a big delay).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
it is not about stock Rom.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] keessonnema:
I'm tired of MiFavor, but I wait for cm13/lineage/cm14 idk what comes on my path, when the audio is completely fixed, I'm afraid the sound recordings will be really bad, just like on every cm build, ever.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
I can't say that I ever noticed particularly bad sound performance on cm aside of the axon (for known reasons) and I have used cm on at least 4 devices aside the axon
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
U don't have to wait.....U could back up stock with TWRP then flash CM, if u dont like it.... Restore. That's wat I'm doing, that way u could practically run both OS side by side.....Considering u back up the one not in use, then u can restore whichever when required
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
I actually use Cm13 as daily so...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
I do too....But if I ever need stock....It's backed up....U should give it a try
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
I do but ultimately backing up data and then restoring a weeks old backup is fairly pointless
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
How so??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
Well by definition the data will be old. Most will sync from the cloud bit still it is a hassle
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] judsonzhao:
Thanks for the awesome Rom!

Have 1 quick question, is there a way to swap recent and return button just like the stock ROM? Not using on screen navigation buttons, just swap the native capacitive buttons.

thanks a ton!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] KyJelly69:
please search the thread this has been asked quite a few times already.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
No.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aaronDroid80:
I think this is what they're referring to. https://www.google.com/amp/www.tech...-to-get-official-cyanogenmod-support-soon.htm

Who knows where this relationship stands now that cyanogen has dissolved. Having official status is a good start.

And another: https://www.google.com/amp/s/9to5go...n-official-cyanogenmod-rom-to-the-axon-7/amp/

Sent from my (insert Nougat adjective) G2 (D800): the Nexus 5 I never had.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shoxxy:
lineageos

dont wanna spam this thread:

just for playin around, i compiled a lineage cm-13 build. i tryed different things, but couldnt fix (audio/robovoice) bugs. i hope unjustified or someone fix it soon. i dont have the knowledge maybe ;)

LineageOS cm-13 Axon7

full credits to: [MENTION=4911249]Unjustified Dev[/MENTION] & [MENTION=4919097]BMc08GT[/MENTION]

Cheers
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
So it boots.....And audio works fine??...Just the calls??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Twiggy000b:
I'll test! Way to go!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] shoxxy:
I think there should be the same bugs like the cm13 build..... But iam not sure
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
Ok....one last thing.....im about to try it but...whats the difference between this and the current cm 13 im already running??? is it just the branding??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Twiggy000b:
If it was built using lineage then there should be some improvement. Especially if he used bmcs GitHub source.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
Yes i would assume so but...it would b nice to have some more details......or a screenshot....u know.....as an incentive to try it
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Twiggy000b:
Update so far, flashlight on quick toggles still doesn't work. Audio seems good so far, better... But still distorted, not so much when audiofx was turned off, right channel still doesn't work, and Snapchat works.

Edit: GPS locks on pretty fast, still roaming icon up at the top. But from my understanding that's a bug with dual sim phones and marshmallow. I DID notice when I got my a7 and went (flash happy)... That the lineage build on AFH (7.1) did NOT have the roaming indicator, so maybe when we get nougat we can move to 7.1 and move away from MM.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
Flashed it, no obvious changes except some lineage branding, also still December patch level
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
That's because Google has not released an Marshmallow security update for January 2017 and probably won't for a while. Nougat is on Pixel's and Nougat is where they have it's security updates and general updates focused at.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nupi:
Thanks for the explanation, I wasn't aware of that. Google is starting to annoy me with their Pixel strategy
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Abiram26:
Can you dirty flash the Lineage ROM over the CM13 ROM?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Iancort:
Yes works fine.....If you're running Xpose, u might have to flash it again cause mine stopped working ... Probably SuperSU too.... Mine worked but I couldn't update the binary and kept prompting me too
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WesTD:
İ've installed this rom there arena still same bugs.

Actually I've wondered one bug more. Signal bar is not stable.

Edit2: fingerprint sensor does not work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] marcusah123:
I'm coming back again, since I still have a 5 minute delay on google navigation starting. Does anyone here have an A2017U phone with this issue? If not, what is your phone running? If I turn the GPS on, and successfully navigate somewhere then, turn it off it will work instantly an hour later. I still have to be outside. People stating that they are getting signal locks inside make me wonder if I am alone in this? I understand it appears to be time related I suppose, however additional information would be helpful.

Thanks

---------- Post added at 05:20 PM ---------- Previous post was at 05:18 PM ----------

@Unjustified Dev are you experiencing my specific GPS issue and if not, what might you suggest I do?

Thanks