yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Hello to you too patriot.

Here it is:

https://www.androidfilehost.com/?fid=457095661767159296

No it won't wipe anything. :)

Happy flashing!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Ogre6473:
Started having this issue the second I installed the update.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] helpmeroot:
Probably it's google music itself. v7.9.4920 was reported to crash. v7.9.4921 (released today) supposedly fixes it
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Upgrade A2017U from B15 to B25

Well, nobody directly answered my questions, so I went for the most optimistic solution and flashed the "Back To Stock" B25 bootstack from [MENTION=3044858]DrakenFX[/MENTION], wiping only the cache and dalvik. It turns out, this was all that was needed.

So, to answer my own questions:

Yes, you can just flash [MENTION=3044858]DrakenFX[/MENTION]'s A2017UV1.1.0B25_bootstack_by_DrakenFX.zip file and the LineageOS install will be unaffected.

You don't really need to wipe the data partition, as the instructions on [MENTION=3044858]DrakenFX[/MENTION]'s post indicate. This is only necessary if actually moving "Back to Stock."

Nope, [MENTION=3044858]DrakenFX[/MENTION]'s file is all that is needed.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] joemossjr:
Yes you are correct sorry nobody answered your question as I feel in this community a lot of people are mis informed... YES you CAN flash the b25 on any of these ROM and NOT be effected personally I've flashed almost every ROM on this forum trying out various combinations. The only difference I have seen in b25 bootstack is primarily in signal strength I find it allot more stable then b15. Another thing that might effect you is flashing weekly or nightly builds because some of them require b15 bootstack. A simple updater script edit can fix that. But as I learned last night flashing the new nuclearom it had some things from b25 in it and that messed up my screen to where I couldn't type. My phone has since been fixed thanks to the dev. But yes you can use b25 and your phone will not blow up.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Upgrade A2017U from B15 to B25

Is Daydream VR fully functional in any of the ROMs that you have tried? In LineageOS, about half of them (for example, "Horizons VR" ) don't work properly.

I haven't noticed any difference in signal strength. A more stable signal would be nice.

Thanks for your insights.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] joemossjr:
Haven't tried daydream as I think vr is nauseating lol but from what I hear daydream is still being worked on sadly.

---------- Post added at 05:36 PM ---------- Previous post was at 04:37 PM ----------

Haven't tried daydream as I think vr is nauseating lol but from what I hear daydream is still being worked on sadly.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sourbear:
Interesting. I checked the LOS CVE Tracker - https://cve.lineageos.org/devices - and the Axon 7 is at 0%. So are we really not getting the Android Security Patches even though in About Phone it says we're on the latest June 5 security patch? What say you [MENTION=4911249]Unjustified Dev[/MENTION] ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] WizeMan:
What's with LineageOS not having a keyboard if we do not install the stock openGApps package? Is there any way I can go minimal and have a keyboard when the setup wizard opens?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ssirK:
We have the android updates, but not the kernel related patches, so we are half OK ! :)

kernel patches are device specific and need to be merged manually
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sourbear:
Ah. Which aren't being done apparently or the OP isn't filling out the online forms that go along with making sure it's up to date on the LOS CVE Tracker. Thanks for the explanation. Still would like to hear from OP why this isn't being done. Too much work? Can't get ahold of the kernel patches? I was under the assumption that being secure was one of the main reasons to use CyanogenMod/Lineage.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
The operating system is chunked up into pieces of codes in different repositories. Some apply to everyone while others are device-dependent. The device-dependent ones are particular to getting your hardware to work.

Take a look here at the changes that happen in LineageOS:

https://review.lineageos.org/#/q/status:merged+branch:cm-14.1

All of the patches to repos starting with android_device_ or android_kernel_ are maintained by device maintainers.

the Gerritt page above looks at these repos https://github.com/lineageos

...and there's even more code that is kept separate for vendor drivers here https://github.com/themuppets - kept separately for legal reasons, I'm sure.

Now, take a look at the Android Security Builleting from June

https://source.android.com/security/bulletin/2017-06-01

little bit of stuff for media framework, libraries, and other generic stuff but once you scroll down and see kernel vulnerabilties - each phone has a kernel repo. Scroll down further and see how many of the vulnerabilities are Qualcomm... basically, a ton and, really, the most critical ones.

If Android was layered like a cake, the frosting we have patched but everything below that down to the crust is unpatched unless someone does it for our device. It's also about that proportional. Like, the stuff that is left unpatched is pretty much the majority of the cake. You can even see that in the bulletin I mentioned.

Also, the lineageOS CVE webpage is just a webpage. Like, the device maintainer would have to actually change that webpage to reflect how up-to-date we actually are.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ssirK:
Kernel commits for our device can be seen here : https://review.lineageos.org/#/q/project:LineageOS/android_kernel_zte_msm8996

No CVE related commits

OP is pretty busy it seems, but anyone else can contribute too ;)

im not skilled enough, so i cant complain! :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kdp162:
You can download the quadrooter app to check your security percentage
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
That's only 4 vulnerabilities from a year ago.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kdp162:
Use this to test

https://github.com/AndroidVTS/android-vts
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sourbear:
According to the first three issues reports on there, it doesn't work for Android N. Have you used it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kdp162:
Your absolutely correct.. I should learn to read lol the only way I guess is to look at the CVE commit list and check it against the kernel source... I know he's been busy and hasn't done much in the way of kernel work
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ogoxew39:
Hey!

This worked out for my A2017U model as well. Always had no receive or even my SIM card wasn't detected with other bootstacks or modem firmware. This is my baseband version TH.2.0.c1.9-00104-M8996FAAAANAZM; is this now the most recent version???
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] user7743:
Its also worth reading the comments on the redit post. My understanding is that there is a manual process to follow for the patches. So there is the potential for all relevant security updates to have been applied but if the dev doesn't update the list, it will still show 0%. Or it could be that none are applied. You would either need to manually check the code to see if patches are applied, or wait for [MENTION=4911249]Unjustified Dev[/MENTION] to comment.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Yeah I think that's the most recent one!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
Uhmmm, you guys talking about security patches, you do know that this device basically has no security except encryption, right? The firehose and a signed twrp are public. It takes very little effort to pwn this device no matter how patched the kernel is.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
I'm not worried about physical security vulnerability as much as software security- including kernel, application vulns, remote code execution, etc. The stuff that you might intentionally install as trusted software or unintentionally browse and pick up.

A firehose & recovery situation is the most obscure, targeted situation least likely to happen. That is, unless we all got duped already when we unlocked our phones.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Hehe if you talk like this, alomst no device is basically secure. Only that with locked bootloader but there is mostly also some vulnerabilitys that you can use to unlock them. But yea you are right.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] andr123a:
Hi all,

am I the only one with a volume (and speaker) issue during phone calls?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Lol no.

Search the thread this is a known issue and there is a lot of info about this here.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ogoxew39:
Just for Info guys: it seems very likely that since I installed this bootstack the caller/mute/loudspeaker bug is gone. Had several calls were I always had the issue with but it has now never come up since I applied the bootstack. Still testing but I'm quite sure it helped.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ongjingxian:
Anyone can help share or share a link of the 1st official nightly build of Axon 7 Lineage OS (February 13th)? This: https://web.archive.org/web/20170215161821/https://download.lineageos.org/axon7

I've tried everything but can't seem to find anything. For science.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Snaptraks:
I managed to download it from this link: https://web.archive.org/web/2017022...ineage-14.1-20170213-nightly-axon7-signed.zip

It is from the page you provided, so I'm not entirely sure where it goes wrong for you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ogoxew39:
False Alarm: just had it again minutes ago :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tomiga:
Any luck with more recent builds? I haven't had much time to test out Bluetooth with my Axon 7 and Nissan Versa.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] user7743:
I haven't retested yet in the car (will try today) but Mondays build brought no improvement on the Garmin side at least.

Unfortunately, both bugs have yet to be assigned anyone to look at them.

I'm currently researching if I'd be better switching to a OnePlus 3T and selling the Axon on. Generally I like the phone but no car kit is a big knock out and the standard ROM really doesn't do it for me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
Nah, trade in your Mercedes for a BMW. Works great on my E60. :)

Seriously though, here's the deal... u-dev seems to be too busy to do any device work lately. I am one of the backup devs and I don't have a lot of time either. I've got a family and a job that keeps me busy. Plus I prefer to run AOKP (not knocking LOS or the devs, I just like it better). Plus there is a boat load of CVEs to go through, and the LOS recovery is not usable and I'm the only one who can fix it because I wrote the UI when I was at cyngn. So I need to really prioritize bug fixes.

Is this the biggest issue at the moment? If so, I'll need logs of both stock and LOS to start. Or you can trade me your Mercedes for a few days... :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] user7743:
:D Nice try on the swap... Unfortunately BMW is not an option for me (down to the company policies ;) )....

More seriously - I am happy to try and work with anyone and everyone to get this (and other stuff fixed). I actually like the phone and would like to stay with it, and like you said, people have lives outside of the device and I very much appreciate people investing their own time to this. I come from a background of open-source and understand the company.

I am happy to pitch in where I can but there are limits to what I can offer and do these days - its a long time since I was working as a developer.

If you want to ping me about potentially moving this forward, I am happy to help out as best I can.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] user7743:
I have uploaded logs to the jira for this from two different configurations. Firstly, the latest build of LOS (03 Jul 2017) that was clean flashed - paired with the car and tried to connect after pairing. This does not connect successfully as we know from the bug. Second set of logs is with the stock ROM installed, device wipe and paired with the car. As stock, connection is successful and phone book synchronizes.

As I said yesterday, if there is a way I can help move this forward other than providing logs - please do ask. I am happy to help.

https://jira.lineageos.org/browse/BUGBASH-717
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Osama.Majeed:
Bug report

Lineage os doesn't show quick charging on lock screen. First i thought it just wasn't show quick charging but actually was quick charging so I check the charging mAh through ampere and also manually saw the time taken to charge....... And they both were slow. I'm on the latest lineage os that was released on 3rd July. I'm using ZTE Axon 7 A2017U. is there any way I could install quick charge 3.0??
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Quick charge 3.0 works fine with the stock LineageOS kernel. There is actually a kernel patch to show if the device is slowly charging if you charge it for example over the USB hub of your PC. There should be also a way to show the quick charging message. BTW quick charging only works up to 80℅ and afterwards it throttles down the charging speed for safety purposes.

Regards

OrdenKrieger
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Osama.Majeed:
Could you please link to the method to show quick charging?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
It's not a method. It's basically a commit that you apply to the kernel that work together with the healthd process that is located in the system folder.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DarkManX4lf:
My A2017U works fine with my Mazda 3 and another car with a Pioneer 8200nex head unit.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Can everyone rant about audio problems so we can get those out of the way
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Huh...?

Haven't seen much rant, only repeated and answered questions by new users.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] amphi66:
Welcome back!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
[EDIT: stock has this line also, continuing to look...]

Looking through your logs, it seems BT connects and disconnects several times on LOS. This may be the reason for the disconnect:

6-21 16:21:03.178 3249 3777 W ActivityManager: Unable to start service Intent { act=local_action cmp=com.google.android.gms/.car.InCallService2 } U=0: not found

I don't know what that is exactly, but it is obviously part of gapps. So your issue may be related to your gapps. Try switching to a different gapps and see what happens.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EasyTiger6x13:
Having a strange issue where every time I press and hold the power button the phone automatically restarts, no pop up menu or nothing. Anyone know a fix, latest build. Extended power menu is enabled.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] user7743:
Yes, after the initial "failure" to pair, both devices (phone and car) show each other in the devices list. What then happens is the phone gets connected for a fraction of a second, and then disconnects. And then just keeps on doing that... Over and over.

It would also surprise me if it was down to gapps as I use the same package on my Moto X, also running the latest LOS build. Its a good point though - I will try with the stock gapps package just for kicks. Just see if it throws anything different in the logs. I'll get that done tomorrow.

And yes,
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kleva94:
Sure :D

During every call the person I talk to hears me very badly, often the sound just disapears for a second. With loud speaker they hear me buch better, but still not very well and on my side only the top speaker works and is very quiet.

I already tested the mic. It works fine. I also tested it with very good signal...no difference.:confused:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sourbear:
Snark about the sound but nothing about the Android security patches... Nice. :rolleyes:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] weustenbakker:
Are you running Substratum?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EasyTiger6x13:
No sir/mam it's installed but no themes are enabled.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] weustenbakker:
I have the same problem... even without themes installed.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EasyTiger6x13:
Yeah I just uninstalled all my themes and Substratum, made sure none were enabled before hand, restarted the phone and the issue still persists. Even with Extended Power Menu enabled in developer settings and in LOS Button settings.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Bluetooth Car Audio connection issues

FWIW, I have seen a very similar issue with connecting to my JVC KD-X340BTS car stereo. The Bluetooth connection seems to be being re-established over and over again. However, I noticed that this only happens when it is the car stereo that is initiating the Bluetooth connection. If I turn off the ' auto connect' setting on the car stereo and initiate the connection from the phone, it appears to work properly. A workaournd I came up with was to make an NFC tag that initiates the BT connection. Tapping the phone to this tag is a lot more convenient than using the phone's Bluetooth settings to connect to the car stereo, but not as good as if the car stereo initiated the connection.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] weustenbakker:
That was the only solution I had. :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EasyTiger6x13:
Signal

I am 90% certain that my signal is much worse on the latest version of this ROM. I'm getting Edge to 3G in places where I usually have full LTE, specifically work. OR, sometimes I'll be sitting in a spot and have full bars, then with a snap of the fingers it's gone and I have absolutely nothing, without moving or anything. I could be sitting in a spot for 30 minutes with full bars and then suddenly nothing. That also didn't happen until I installed the latest version.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ssirK:
Nio change to the telephony stack in latest build, so i dont think its related to the ROM..
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] user7743:
Yes, I had read similar with regards to other Bluetooth issues. I had actually already given it a try (and initiating the pairing from both devices to see it it helps) but no dice.

I also tried with the full and stock open-gapps packages but same behavior.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dwnoel:
I m usiing the ROM on my A2017G from April, following the updates, with these issues:

- need to toggle often ON/OFF at the beginning of a call (no matter called or caller; about 50% of time)

- same behavior in my car (toggle to phone speaker, then back to BT; especially when I initiate the call)

- the BT will stay with a status "connected to Ford Audio" even at miles from the car !

- quite often the speaker said that (s)he can't hear me very well; even if the signal bars are OK. But I can hear speaker quite OK

Many thanks anyway for this great ROM :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] HansWursT619:
Maybe we need to put out a Bounty again^^
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lafester:
Good to know, thanks for testing.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] cms062407:
Ahh sweet. Just to verify, before I flash in a few minutes....I flash the bootloader and modem after I factory reset and BEFORE I install the actual LOS ROM?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Doesn't matter as long as you flash it before the ROM. The ROM checks the version of the firmware and will fail to install if it cannot find the N version.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] cms062407:
Perfect. Booting into recovery as I type this :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gpz1100:
Tried sim 2 without any sim in sim1? Still nothing?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
The fingerprint sensor will be included in the next build. Keep in mind it does crash on registering the first fingerprint and it's a little buggy, but it works so that's something. Also SeLinux is enforcing again so if something doesn't work let me know so I can find the denial. I also finally got around to merging the Lineage device tree changes which rename the device trees to Axon7 as seen on github . The next build will be named lineage-*-axon7.zip , same as AOKP builds it's compatible with all recoveries. On to official support...I would like to push official support when fingerprint sensor works without hiccups as I don't like hw issues to be one of the main bugs. I also have to wait on ZTE which shouldn't be too much longer. So that ends it for tonight. :good:

ps: Wifi calling may be added too if it performs well.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Try editing your build.prop find this line ro.telephony.default_network=10,10 and change it to ro.telephony.default_network=10
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] cms062407:
hmm, I factory reset, flashed the bootloader and modem zip, flashed LOS and then flashed GApps, cleared cache....hit reboot and it just went straight back into TWRP, didn't boot into LOS. So, I held the power button down to force the phone off..booted it back up, and I see the LOS boot screen, but then it just goes to a "enter your password" screen....am I missing something?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
What format is your data partition? Try formatting it as ext4 .
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kevinkuensken:
[MENTION=5082772]Unjustified[/MENTION]

Will Media Sound fix in next build?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
That's something ZTE has to fix. I don't have the tools and the members who can obtain it do not have the time plus I think it would be much easier for ZTE than it would for them since they know about the device. Also ZTE R&D won't be back until next week. Hopefully then they'll be able to work on it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] cms062407:
it says f2fs...I will try to change it to ext4.

---------- Post added at 12:34 AM ---------- Previous post was at 12:22 AM ----------

It is saying "can not mount data partition" and it will not let me manually mount it, either...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
reboot the recovery and try again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] cms062407:
okay, yes, that did fix the mounting issue.....and I changed the data to ext4.....should system also be ext4? because, I reflashed everything after changing the data partition to ext4 and it still just boots right back into TWRP and I see that "system" is unmounted..but, I can manually mount it, but it still boots into TWRP.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Just hard reset out of twrp. I'm not sure the exact issue with newer twrp as I have not upgraded.