yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
[MENTION=4911249]Unjustified Dev[/MENTION]

I can't see this really discussed anywhere which is surprising to me but I wanted to report what I believe to be a major issue with our phone when using a vendor partition.

Since moving over from my previous setup (Nfound Vendor+AEX 5.8) to LOS/AOKP or any ROM built using the LOS15 vendor sources battery drain, particularly idle drain has been awful. Since moving to LOS15 I have tested with both the b12 universal bootstack from DrakenFX and the new B20 one.

To give an idea, the phone seems to be entering deep sleep okay, there are no troublesome wakelocks or alarms preventing the phone from sleeping, yet the screen off drain is as much as 5.1% per hour overnight.

If I return to my old backup, or to stock for example this is reduced to a figure closer to 0% per hour and its not unusual to drain as little as 1-2% during an 8h sleep compared to 40%.

What is it that could be causing this and is it possible to provide you with anything that will help troubleshoot the issue? I did mention this also too [MENTION=4126377]tdm[/MENTION] in the AOKP thread but I didn't see it discussed here and I know that LOS itself is where most other builds are copying their sources from.

Edit # just did some testing playing a game. Went from 51% too 17% in 20 mins.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] NyQuilXT:
Hello,

with actual official build 20181015, I'm having huge battery drain. system_server seems to have significant load all the time...anyone else also have this problem?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kg3:
Can Nfound non treble TWRP be used? Or is the treble version required? Reason for Nfound over official is the ability disable the inscriptions/warning that the loader is unlocked.

https://xdaforums.com/axon-7/development/twrp-3-1-0-2-t3591075
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Does anyone have a file of the separated vendor partition for 15.10.18 build? Thanks anyways.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] olli196:
My Axon is getting very hot in every App and battery drains fast with newest Build (clean Install). Any other with this problem? Thanks
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TheWaterBug:
I wonder why only certain people are having these issues, even with clean installs? I dirty flashed from the previous build, wiped cache + dalvik, and rebooted. The only thing I'm noticing is some apps would stop randomly and occasionally, including play services.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Infy_AsiX:
that's a typical load for system_server.

Complaints about heat. Seems thermal throttling isn't enabled on these recent Treble. Also related to that is device runs maximum speed much more without this restriction. Depleted old batteries are particularly prone to bad life from these.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
So the wifimac address issue began as SeLinux denials by the kernel

1.) It needed to be able to read wifimac.dat from persist

2.) If wifimac.dat didn't exist, it needed to generate a random mac and store it to wifimac2.dat

3.) Read wifimac2.dat and never generate a random one again

Somehow it appears there's a flaw in the code. It was hardcoded to only read wifimac.dat when deciding if it should generate a random mac or not. Testing a fix that allows it to check for both wifimac.dat and wifimac2.dat before deciding if it should generate a new persistent mac address in wifimac2.dat in the absence of wifimac.dat.

edit: Confirmed it's now fixed
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Yes, the thermal configuration is still pretty much B32 and it isn't that great nor up to date and tuned.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
I know what my original mac address was. To fix it, I would need to change the address in wifimac2 to my original address and then flash the fix/patch or fixed ROM? I've been trying to follow, but haven't seen how to get my original back and for it to stay.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
If you don't have wifimac.dat in /persist then you need to edit wifimac2.dat with your original mac address then rename it to wifimac.dat.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
I'm sure I've tried this, I'll give it another go. Perhaps I tried, but was still using an unfixed version of LOS 15.1. Thanks for the quick reply.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] atakan33:
latest 1019 build doesnt bootup somehow
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Dev only build. I'll publish one later on. Probably best not to flash unannounced builds I make so many per day under the same file name.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mart Son:
Yesterday I tried to build from source, just for fun.

I noticed that there are a lot of proprietary libs used,

which could not be extracted from my phone and

I copied them from an extracted vendor image of the latest lineage rom.

After some trying I gave up, because of low ram on my computer.

Have you already tried to use the libs of the new official Oreo ROM?

Regards
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
They should extract just fine if you already have the vendor synced from TheMuppets github. I don't think you can extract without it because we have pinned files from other devices such as GPS and graphis etc which are more up to date than the ones ZTE ship on stock 8.0. Also yes, there wasn't really much of an update to what we already have

https://github.com/C457/proprietary_vendor_zte/commit/fce1e63762dbba4c0d3430f4ebc8f5215c82510a
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Thanks again. This method worked for me. Flashed a new ROM, looks like it's persisting now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] atakan33:
which build did you flash ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
It should work on the latest official as that one fixed the SeLinux permissions. The next one will fix the issue where a random mac address is generated every reboot if /persist/wifimac.dat doesn't exist.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] williamthardy:
Trying to answer several recent related questions:

1. New battery

2. Clean install

3. Flashed:

ZTE_A7LOSv1_UniversalBootStack.zip

A2017U_OreoModem.zip

lineage-15.1-20181015-nightly-axon7-signed.zip

open_gapps-arm64-8.1-stock-20181016.zip with many LOS app exclusions and GApps replacement

##	STOCK GAapps Exclude

GoogleCamera

PixelLauncher

PixelIcons

VRService

CalculatorGoogle

GoogleNow

FaceDetect

FaceUnlock

GooglePlus

Docs

Sheets

Slides

Fitness

Keep

Books

PlayGames

Movies

Music

Duo

VRService

NewsStand

NewsWidget

WebViewGoogle	# System Web View Included in Chrome

YouTube

skipswypelibs

# Keep from LOS

+Launcher

# Delete from LOS

Email

CMFileManager

CMMusic

CMAudioFX

Browser

CalendarStock

LRecorder

CalculatorStock

Results:

Battery down 18% in 24 hours-very light use. No heating.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
October 19 Unofficial Release notes

Device changes:

Imported B20 changes

Imported GPS configuration from Pixel XL

Update GPS blobs from BQ Aquarious X Pro

Moved GPS blobs to vendor partition

Revert Lineage Vibrator HAL

Import Pixel 2 XL VR HAL and Pixel XL thermal configuration (no low persistence yet I'm working on it)

Disable button backlight settings

Kernel Changes:

Fixed reading temp mac address file in the absence of factory version

Updated to latest 8.1 caf tag kernel+wlan

Revert Essential PH-1 changes to vibration

Imported B20 changes

Revert several ZTE power manager changes

Download:

Click Me
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Very early feedback on this: I am normally on the official builds, so when I switch to the unofficial to test things, most apps don't work, and this limits what I can try... but I ran the VR game Minos Starfighter for a bit, which generally gets the phone quite hot, and it stayed only moderately warm. I didn't run it for a long time, but my feeling is that the thermal management is an improvement. Before, the battery could go past 50°C and the phone's exterior would get almost too hot to touch.

Caveat: I had to try this with a non-Daydream headset, because the Daydream View's NFC would make the Google VR Services crash (due to the mentioned thing), so that may also have an effect on the overall temperature.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] okmikel:
This should work switching between official and unofficial without losing apps:

https://wiki.lineageos.org/signing_builds.html#using-a-script

If done this on my Z00L many times.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] okmikel:
Tested it myself, it also works on the Axon 7. Change from the latest official to udev's latest unofficial without losing apps. To work in TWRP with adb the script needs a little modification. I attached it to this post. I used oki's TWRP with integrated adb.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] CryptMan:
Hi,

I have installed the 15.1 (20181015) on one of my phones and if I'm running Pokemon Go on them it gets really really hot (~70°C if I can trust HWMonitor Pro).

It's so hot that it's near the point where you can't touch it any longer. With Linage 14.1 this was not the case.

I have wiped the phone an reinstalled everything but this did not changed anything.

Any suggestions?

Best regards.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
I was wondering about this too. I have gcam as loaded via the 'stock' version of gapps (which is what the link at the top of this forum points you to). Recently tried taking a photo with flash, and it came out totally black (which I sort of remember being the issue). Is the gcam included in gapps not the right one to use - and if so, can I install the right one over it? I.e., is it possible to get the best version of gcam without having to wipe and re-flash my phone to get rid of the one that installed with the 'stock' gapps?

Oh, and now that the official ZTE oreo release is out, is anybody working to get a version the ZTE camera app for LOS users?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Penoro123:
Download any ported Gcam apk. The pic quality is much, much better than the stock app, it feels like a totally different phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
As I was getting ready to flash, I noticed part of the issue -- the official bootstack in the OP includes flashing persist.img, which is always going to overwrite people's default MAC.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I informed Draken he's going to remove flashing it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] messi2050:
I wonder how no one has reported the existence of buttons backlight option till now ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Your commit actually didn't work I merged it by mistake meant to push a patch first guess that's what happens when you sleep too much. It belongs in the default framework base overlay
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] messi2050:
Ouch my mistake for not testing it before push, sorry.. guess i need more sleep in my case xd
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
Well, that was not exactly a clean process from 7.1.1 stock unlocked. The biggest problems I hit were not knowing which unlock method to use (they all share the same fastboot.img, but the emmc_appsboot.mbn was different between them). I ended up using the N version from the axon7toolkit but flashed manually (to use a portable MiFlash rather than installing).

The biggest issues were:

TWRP -- still not sure which versions have which benefits (had to end up using Oki's Lab to get everything to flash correctly) -- Which ones support Oreo device encryption? Only Oki's Lab b12 one (which loses adb)?

flashing LineageOS and getting error 7 -- something is wrong with the install script in the case where there isn't already a /vendor created. It would create the vendor, but then it wouldn't ever let you mount it or flash the image. The only way I could get it to work was to use Oki's PARTY tool (done via his TWRP) , create the partition first, reboot, and then mount /system and /vendor and then install Lineage (as other people said to do)

So, outstanding questions:

TWRP versions -- see above

How do I enable the on screen buttons? -- I still use an old app that needs the menu key, and the only way I could use it on stock was with MiPop. I searched the options and it pulls up the one under "Buttons" but when it goes to the menu, those options aren't present. It would be nice to be able to select SW or HW ones.

https://xdaforums.com/axon-7/themes/a2017g-navigation-bar-enabler-disabler-t3740817

it would be nice if we could just have the Lineage built in options to enable it (since they seem to exist) rather than having to alter the build.prop file.

do any of the TWRPs/systems support exFAT? exFAT is supported in 15.1 and at least Oki's TWRP
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Borgodoc:
I followed Oki's instructions, which worked very well. However, for some reason my device is still recognized as A2017U, even though I switched the modem package with the 2017G version. Anyone have any idea what might cause this or how to fix it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
That's a known "issue". It doesn't really matter as long as you have the correct modem -- all Axon 7's on Lineage will show up as the U.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Zobat:
correct
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
This doesn't work for me. I've tried it in adb and TWRP - with and without the dash in dm-verity and with and without the quotes. the phone reboots, but the warning screen still comes up. Not a big problem, but since this command is supposed to make the warning screen go away, I'm wondering what factors could make it not work.

Is "dm-verity enforcing" a function of the bootstack? If so, should I try flashing another one. The bootstack I'm running was given to my by DrakenFX (in the form of an EDL script to unlock my phone while I was still on the ZTE Oreo beta last summer). I had assumed that script had simply unlocked the oreo bootloader that ZTE had already installed as part of the beta (and that my bootloader was the same one Draken posted here), but who knows... (or is there some string on the fastboot screen that would tell me for sure?)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
The warning will always come up. The dm-verity command stops that little orange link from turning red, and it is so you won't have to hit the power button to continue booting every time.

There are ways of removing the warning completely, but many keep it because you can easily access a menu to get into fastboot or recover if needed. Removing it means you might get stuck if button combos don't work for whatever reason.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
On the new A2017U bootstack, is anyone able to actually get fastboot to work? Any time I try to boot into that from the bootloader unlock warning menu or from adb reboot bootloader, it just boots into system like normal .
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] pingouin47:
From this morning there is a new A2017x_LineageOS15.1_UniversalBootstack_v2_by_DrakenFX.

What are the difference with A2017UV2.1.0B20v01_Bootstack_by_DrakenFX?

Which one should we use?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
New bootstack removes persist.img , which overwrites default MAC Address. Use the V2 one. Unjustified mentioned this a page back.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gachmuret:
[MENTION=3044858]DrakenFX[/MENTION] Thanks for new bootstack v2, would be good if you could also make it working with EDL boot combo as [MENTION=319057]Oki[/MENTION]'s bootstack... or maybe you did this already in v2 and can confirm it here
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mart Son:
Thanks, after getting some more ram for my old laptop, the SSD ran out of space... I am glad tonight it compiled just fine until the end. :good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jntesteves:
From the buttons configuration you can configure any of the hardware buttons to open the menu on double tap and/or long press.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
Thanks. Boy, the various suggestions that the dm-verity function gets rid of the extra boot menu screen are sure misleading (or I'm sure dense). Yeah, I kind of do like having a menu to easily access fastboot and recovery - except for when I hate it ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
The universal stack v2 is file identical (via MD5) to the v1, just without the persist.img (which is what I found was wiping so many people's MACs). EDL support will be the same as before

The B20 based stack is the same as the official A2017U files (except for fastboot), so those should support EDL should be the same as stock. I know for sure you can adb reboot edl as I did it a ton. I didn't try the hardware combo key. The cable/motherboard method should always work as pointed out.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DrakenFX:
[MENTION=1905846]Gachmuret[/MENTION]

Both zips DON'T HAVE persist , and by which to flash , depends on the build you want to flash....

I know [MENTION=4911249]Unjustified Dev[/MENTION] unofficial build have B20 blobs and if I'm not wrong Official still uses B18.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] attilalovesfun:
I just experienced the above issue last night as well. Battery indicator stuck at 50%, tried a reboot and then the indicator rapidly reduced to 44% in 30 seconds then it was stuck there instead. I'm on the latest official from the 15th of October.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Only thing I can say is maybe it's a different revision of devices. You all would have to get kernel messages because I have not yet to run into this issue so there's no way I can reproduce it. adb root then adb shell dmesg > battery_stuck.txt
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] attilalovesfun:
Thanks udev, next time i get the issue ill do a dmesg dump and post it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Shadee13:
Could someone verify if OIS is working on this ROM, or any other Oreo / Pie ROMs?

I have been running NFound's non-treble Oreo since June and yesterday I noticed that my camera is not stabilized.

For all I know the OIS might have been "disabled" since day 1, but that's why I would like to ask someone on Lineage if the issue affects everyone or only my camera is broken.

The easiest way to visually verify OIS is to turn on the camera, flip the phone and start tilting in back and forth. You should see the lens moving left and right trying to compensate for your hand movement.

I am not a developer but in the output of the Camera2 Test app I saw an interesting line:

android.lens.info:
- availableApertures = [1.8]
- availableFilterDensities = [0.0]
- availableFocalLengths = [4.216]
- [COLOR="Red"]availableOpticalStabilization = [0,0] [/COLOR]
- focusDistanceCalibration = 2
- hyperfocalDistance = 0.20253555
- minimumFocusDistance = 10.0
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Same on stock
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gachmuret:
As fas as I understand the method of Optical Image Stabilisation it is a physical mechanism (at least for smart phones) means it is hardware not software ergo software won't have any influence on it... except if you meant electronic/digital image stabilization (EIS) and wrongly referred to it as OIS...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Shadee13:
I will most likely not use the correct terminology, but:

Moving hardware parts, for example little motors inside the lens, require software to run.

Every hardware needs software to run, but I don't know if OIS is implemented into the camera's controller or it's somewhere higher in the stack. (somewhere where the devs can touch it)

By design OIS is only activated when you open the camera - meaning it gets started up by software, so theoretically there is a way to disable it by software.

Either way, if you are running Oreo or Pie, could you please verify if it's working for you so that we can isolate the issue?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anildzs:
Hi Oki - Need your help. I installed the Hellsgate Kernel , but on boot, phone says that Vendor Partition is outdated. Maybe it does not match the Hells Gate Kernel.

ZTE works great on the EDL package that you had created for LOS 15.1.

Very simple and thanks for your help. Now I am just tweaking to improve performance and battery.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Hellsgate isn't compatible with Treble. The only other kernel to use is Schwifty.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anildzs:
Tried installing Schwifty. Phone wont boot. Do you have the latest Schwifty Treble kernel
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] EBeatFLA:
Lol I'm so sorry, actually Schwifty isn't working with the latest LOS builds. It is being updated to do so though. You'll have to use an older build of LOS 15.1 or wait for Scwifty to be updated. Not sure which LOS build was the last one to work with Schwifty, you may want to ask in the Schwifty thread.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Soyunamortz:
How can I show battery % on status bar ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
Ok I've tested the last two official builds for couple of days. Everything seems fine to me. But guys, the battery drain sucks on all 3 Axon 7 we own. :eek:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Go into settings and battery. Then hit "Show battery percentage"
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JKSurf:
Sounds like you had the issue and it went away. Consider yourself lucky. I believe I have a recent rev cuz I sent it back twice for warranty replacement.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] attilalovesfun:
Very lucky :) Definitely has gone away for now as it didn't occur again during yesterdays 100% > ~25% discharge cycle.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I'll change the fingerprint to 7.1 next week if that helps everyone out and someone mentioned before you need a certain gapps build date or it won't work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] atmos929:
Issue is with GAPPS... I dunno what's the soonest version that doesn't have this issue,, but I went as far back as August 12 and Android Auto works fine on it.

---------- Post added at 11:09 PM ---------- Previous post was at 11:07 PM ----------

Does anyone else have issues with occasional gaps when playing through Bluetooth headset?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TeutonJon78:
I just had someone on stock Oreo check, and it's passing Play Store certification with that same fingerprint, so there must be another reason it's failing right now. That 8.0 fingerprint "should" work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Which 8.0? Official or beta?