yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
You're doing the Lord's work.

Seriously, I appreciate it. Especially since we're probably not one of the bigger name devices.

To what [MENTION=4911249]Unjustified Dev[/MENTION] said, I think I've always recognized [MENTION=4126377]tdm[/MENTION] the username myself, but just noticed that he seems to hop around doing stuff here and there. My memory is foggy but my last 2 devices were the Nexus 4 and Nexus 5 and I think I've seen the name TDM from those days.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
Well, yeah, I've been around for a while. My devices have been vm670/ls670/p500, marquee, mako, vs920/p930, find5, e980, find7, bacon, axon7. While I was at cyngn, I mostly did recovery work and internal tools, though I did do work on devices -- mostly bacon, tomato, and kipper.

The internal tools related to device programming and debugging -- EDL, ramdump, fastboot, efs backup/restore, and such. I have a cross platform command line tool to do all that and more. I was working on a nice cross platform factory backup and restore GUI when cyngn imploded. Too bad it will never be released, it would have been pretty awesome.

But alas, now I'm back to playing around with Android in my "spare" time. One of these days I'll get CM/Lineage recovery back in order...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
Was that the LG Optimus p500? And were you on Android Central at the time?

My first Android phone was an LG Optimus V which was like its twin for a different carrier. At the time it was when Francisco Franco was just playing with tweak scripts and then started doing kernels. It seems like a few people started on those Optimus phones. My only contributions to Android were a little debloater zip file script and a kernel which was just cherry picks from his kernel. Lol

Those little phones would not die. Like we started on Froyo and the last time I looked I think people had cm12 running on them.

I think it was you, drewwalton, mrg666, and a few other random usernames I vaguely remember.

Well, if you ever bend anyone's ear anymore these days I'm going to throw it out there that someone keep looking at Privacy Guard. I just have this vibe that it has some behavior inconsistencies, could maybe not be up-to-date with newer permissions, and... I dunno... could maybe take some things a step further such as checking for permissions abuse that can be declared but not your standard permissions. Like I have no idea if some app reads my sensor data for no reason or just random things I wonder flies under the radar.

Anyways, take care man.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sandibhatt:
That would be a good sandwich... Bacon, Tomato, Kipper (maybe add some pickles and have it with beer)... Sorry couldn't resist :p:p:p

On a serious note, totally appreciate what you do, kind sir...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
Yes and yes. That was my first android phone, the VM670 aka OV. Still have 3 of them sitting in a box in my closet. All with altered ESNs and all probably boot and run still. :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
I sincerely did not know that.

Thanks for everything tdm, you deserve more credit. :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
Well dang it. I kept editing with wishlist stuff in that post since you mentioned the whole cyngn thing lol

I googled the VM670 because it sounded like it was the Optimus V... Brain fart. I think I threw mine away or it's lost somewhere in a box.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
I noticed that the B19 modem would for unknown reason prefer the HSDPA cells even though i know LTE(4G) is around.

Try this. I was able to fix that with the following settings changes:

Dial: *#*#4636#*#* then go to phone information and change "Set Preferred Network Type" from:

"LTE/CDMA/UMTS auto (PRL)"- which was default for me while encountering that behavior to:

"LTE/UMTS auto (PRL)"- it now barely switches to HSDPA for me.

I was able to verify that behaviour. By actually walking the same way and back i do when i pick up my groceries.

Once without the change and once with the changes.

Without the change it would stick to HSDPA cell's for longer and quite prefer it.

Really weird.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Druboo666:
[MENTION=4126377]tdm[/MENTION] he's the one of many who maintaining the AOKP project and also back then worked [MENTION=378056]cyg[/MENTION]yn and now working on Axon7

you guys should be great-full to have him in our forum.and like [MENTION=4911249]Unjustified Dev[/MENTION] said he is one of lead developer who made possible to bring up CM on our device so fast.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
So we finally know who the anonymous developer is :P
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Well no he's never been anonymous lol just no one has paid enough attention. Honestly the anonymous dev has posted too. *Shrugs* it's been so long no one would remember.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ArgonautPollux:
lol
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Druboo666:
lol blame gboard :silly::silly::silly::silly:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
[MENTION=4911249]Unjustified Dev[/MENTION]

Any chance we can merge this for the next weekly build?

Been testing it for the past 6 weeks on LOS without any issues.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MatreyuC:
Does anyone know what DAC is used for what? Is the super DAC always used, is only the less good one used, etc. Also, is it configurable somehow? And how can I edit things like gain for the speakers, screen saturation, headphone jack volume steps?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] baconboy:
I'd like to know this, because as far as I know the DAC only works with stock. And I didn't buy this phone to get rid of its best feature! (I'd love to try out this ROM)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MatreyuC:
I tested this rom, ended up reverting to stock cause the speakers sound better there. Couldn't get the Axon's specific version of Dolby Atmos working (see this thread, it may be compatible at some point or I could have done something wrong: https://xdaforums.com/android/apps-games/soundmod-axon-7-dolby-atmos-t3412342 ). Also a couple other preferences I'm pretty sure I probably just don't know how to change. Headphone output sounded good, cause both the DACs in this thing are good, but without a direct comparison like you can do on stock I couldn't tell which was being used.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] name2:
The AK4490 is definitely used for headphone-out, but I believe is also the default DAC for speaker-out (see /system/etc/audio_platform_info.xml, acdb_id="207" seems to be the AK4490).

I have not found a way to configure it in any way, not even the volume. In /system/etc/mixer_paths.xml below the line <path name="headphones-hi-fi">, if you set the volume to anything less than 255, it's just off. For speaker gain (they are really plenty loud already) I assume you'd have to look at that file, but as long as the AK4490 is being used it seems you can’t change it. If you want them softer, you can try changing the volume curves in /system/etc/audio_policy_volumes.xml and /system/etc/default_volume_tables.xml (set the last curve point to a value < 0).

As for volume steps, add a line ro.config.media_vol_steps=<some number> to /system/build.prop, with <some number> being the number of steps you want, obviously.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Jesus christ the xda app sucks, I'm trying to quote another fellow and it quotes a completely irrelevant post.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
I read the commit but I'm not sure I understood, what does this improve/fix/help with mate?

P.S. I've been meaning to quote you this evening but the xda app was misbehaving again so I couldn't do it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] baconboy:
That's interesting! So the DAC is used by default? This is the first I've read about this, and that's pretty awesome.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
Read the commit message. It states what it is for.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MatreyuC:
Thanks for the info! Any idea on where to edit screen saturation?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Helacornio:
Hey there, I was wondering if there is a way to adjust the screen saturation, mine looks too bad, almost like a generic phone.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
[MENTION=4911249]Unjustified Dev[/MENTION]

Is gonna have to incorporate kcal control in order to change saturation levels.

https://xdaforums.com/android/software-hacking/dev-kcal-advanced-color-control-t3032080

But I admit this will be extremely useful because I won't ever have to flash a custom kernel on a lineage based rom.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Helacornio:
Thank you, I hope Kcal gets added on future uupdates, the rom is awesome :D
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Can you point me to where/how I can modify my device to use both trust zones?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DarkManX4lf:
You can't. If you are on the latest bootloader then you have to edit the update script in the Lineage OS zip to trust zone 325. For the time being you have to do this each time you update or clean flash Lineage OS.

Also doesn't seem like you can edit the update script on Android. I've tried but never can get the file to update in the zip. You have to do it on a PC.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Yes. That is exactly the info I seek. I did a grep of the unzipped latest LineageOS and found:

META-INF/com/google/android/updater-script:assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1");
system/build.prop:ro.build.expect.trustzone=TZ.BF.4.0.1-00315

Should I merely change these both to TZ.BF.4.0.1-00325, re-zip and flash?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DarkManX4lf:
Yeah pretty much.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
I actually did it with rar on my device with no need for a pc but it sucks doing it every single update.

I think the b25 trust zone will be supported soon if I remember correctly.

But I personally fail to see the reason of having it on the updater script altogether, if anyone can tell me why is it there I'd be greatful.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DarkManX4lf:
How did you do it on your phone? Extract all, update and rezip?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Because the blobs are not compatible with all versions. For example you can't use B20 M firmware with N. We want everyone to be on the same trust zone to match their blobs for the best experience.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Something like that, yeah.

It works just fine really, try it.

EDIT: I actually extracted the updated script, edited it with qedit (I think) and added the file on the zip again.

I see, thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DarkManX4lf:
I tried unzipping the whole archive, editing the script and rezip. When I went to flash it gives me an invalid zip or archive error (something like that). When I try and edit the script using rar it won't open the file as it says "can't open file".
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
https://play.google.com/store/apps/details?id=com.rarlab.rar&hl=en

https://play.google.com/store/apps/details?id=com.quseit.qeditor&hl=en

These are the apps I use bro.

Can't help more than that really. :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Thanks. Unzipping the update, changing those two text files, re-zipping and flashing worked.

Now if I could just figure out what to modify so that I don't have to enable SELinux permissive mode to use Viper4ARISE.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] DarkManX4lf:
It works when using qedit. When I used solid explorer built in text editor, it didn't work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] RedJHoN:
Problems whit the memory my phone is A2017 4giga/128giga and now it's say is A2017u and I only have 64giga
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] sToRm1nG:
You don't have to change the field in the build.prop, at least I didn't.

I simply replaced the line you mention inside updater-script by the following:

assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315", "TZ.BF.4.0.1-00325") == "1");

But of course replacing "TZ.BF.4.0.1-00315" by "TZ.BF.4.0.1-00325" will also do the trick.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] TimoVerbrugghe:
Anyone able to confirm if the kernel in this custom rom allows for connecting an xbox one controller without the phone going into a reboot loop?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mario972:
It's like that on all devices. It does not matter, you still have 128GB of ram, and the model name is not important.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] RedJHoN:
I have it but i cant use it thats mi problem if we see the screen shot now i only have 60 giga of internal storage not 128 giga
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dwnoel:
Root and Magisk 13

Historically I have rooted my device (Super SU 2.79), then install LOS. I have kept SuperSu...

and everytime I update my LOS, on weekly basis, I have to reflash SuperSu2_79.zip

Now, because I'm banned by Safetynet from some apps on the Store, I would like to try to Magisk 13

But Magisk asks first "Make sure to remove any other root and restore your boot image back to stock"

2 questions please:

1. do you think I can simply install magisk just after a LOS update ? (since superSU looks removed) ?

2. do you see a risk about the "boot image back to stock" ? (I saw some user, on this forum, using Magisk 12, but better to ask first :) )
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mario972:
You CAN use it. It's just an error in displaying it. You start with "negative" amount of space. If you lay it on numerical axis and count the distance you will see you have ~120 GB. LineageOS shows ~28GB of space for me, but I know that I can store ~60 GB on it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ((RayDar)):
Thanks for the info.

Do you know what I could change in the archive so that Viper4ARISE will work without using SELinux Permissive Mode?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] SantiHurtado:
Works perfectly for me. Using an Xbox One S Controller with latest firmware and paired through Bluetooth
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Reindhardt:
After installing LOS rom, my axon7 only use 2 low performance cores most of the time, is that an error? How do i use my high performance cpu core? After restart it turns back on but back to sleep after awhile.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
This is intentional If you want your cores to be active longer/always in cost of battery time of course. Go to settings and search for "device performance" and move the slider all the way to the right.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Super.Alberto:
I also observed this behavior.

After a reboot all 4 cores reported active.

After a sleep, only 2 cores reported active.

I think it's a bug in the *reporting* of the individual core frequency and does not affect performance.

Using AnTuTu I get 150,696 with 4 cores and 150,575 with "2 low performance cores".

If only only 2 low performance cores were active, the result would be much lower.

I have the battery performance profile set to "Balanced" (default).

I suspect LineageOS is not reporting core frequency correctly after sleep.

Trepn Profiler (QualComm), CpuFloat and a few others report only 2 cores active.

Multi-Core Observer (MediaTek) seem to report the 4 cores correctly.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kgptzac:
With recent development of xposed on Nougat, has anyone tried it with this rom?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] troy5890:
I have, it had some bugs described from the xposed thread itself, but overall it ran a few modules pretty well. I did noticed that the fingerprint scanner became a little sluggish so tread with caution
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
Anyone else checked for battery drain overnight?

When the device supposedly should be in doze?

This is what I got from a full charge before sleep and when I wake up.

Running latest nightly build.

Why is the significant motion detector keeping the device awake for 30mins even though the device hasn't been moved at all?

Shouldn't the SMD handle the doze on/off?

So it ate 8% battery overnight.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Reindhardt:
Thanks for your info, so turns out it was only the software fault, i tried using the multi-core observer and saw 4 of the cores all working, thanks alot!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] chrispayne:
I finally bit the bullet and flashed , and now have no audio on calls as well. I have the same symptoms as you did, no Enhanced LTE option in settings for the SIM, although I don't think my provider (Telus) has VoLTE support where I live yet..

Did you figure this out or another way to get call audio working?

Thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
The audio during calls/when calling is a know issue. And from what I read the audio dev is onto it.

The VoLTE issue however. I checked the settings in overlay for the rom and everything is properly set.

VoLTE will be enabled/disabled depending on a provisional flag when you log-in with your card into your providers network.

Unfortunately for me my provider only enables VoLTE for branded carrier phones. The Moto Z Play for example I had for testing was one. The Axon 7 is not on their list. So it is not enabled. No VoLTE for me on the Axon 7.

I talked to some LOS devs on slack if there is a way around and how they (the provider) check what OEM brand is requesting the provisional flag.

It goes through the modem binary which is closed sources and there is no way around it.

So basically it has to be allowed by the provider itself. Either they allow it for all phones or have an "white list" by OEM.

I can think former is just a another way for them to make money. Like if a OEM wants to provide that feature in a specific country, they would have to pay for some "Licensing fee" to get onto the whitelist.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MatreyuC:
Is this the right place to suggest stuff? There are several features I think we could all agree should be added, kcal, dark mode, the stock Dolby Atmos software, and I also don't think LOS can fingerprint unlock with the screen off right?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Snaptraks:
Actually it is able to do so! I use it every day, and if the phone is not far into deep sleep, it is pretty fast. Might take 2-3 seconds sometimes to unlock my phone (Axon 7, latest LOS nightly) in that case.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] MatreyuC:
Ok cool!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dwnoel:
Difficult to answer precisely to your question (maybe impact of "ambient screen" ?)

On my side I succeed to reach a consumption between 0.3 and 0.4 %per hour with -of course- plane mode, and also 'ambient screen' disable; localisation OFF ; and all apps stopped ('kill -9 -1' or at least all in the tasks view)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
I guess yeah, but I doubt anyone will consider adding something like that, the focus seems to be on bugs right now.

But even if fixed I still don't think they'll add anything, lineage os tends to be...wel...full stock. :P

I can't answer about fingerprint because I don't use fingerprints myself.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
I don't use "ambient screen" it was on airplane mode during sleep and wasn't touched/moved.

I read that doze only works properly when it can reach the "cloud service". So my guess is that doze never fired due to airplane mode never being able to reach Google's cloud service.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] chrispayne:
Yeah, I'm not so much interested in VoLTE as I am in working call audio. Toggling the speaker phone does not work for me, so I was just searching/trying other work arounds and don't have this selection to try.

I've searched the thread, these are the only 2 suggestions I found. Are there any other work arounds to try while audio work is underway? Unfortunately I can't really use the Rom without at least a work around.

Otherwise everything seems great, thanks to all the devs!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mario972:
You don't have to flash universal bootloader if you are on B25 stock. You will have to remove the assert that checks for Trustzone version.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mario972:
You only have to flash LineageOS zip.

Open the zip and edit

\META-INF\com\google\android\updater-script

and remove a line that says

assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1");
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mario972:
Yup. I recommend Magisk for rooting though.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mario972:
There apparently is a call bug but it's fixed or super rare. Haven't had it in a long while.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] celoxocis:
I still have it on every call on B19 A2017U base. Latest nightly LOS. I need to toggle speaker on/off to fix it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dwnoel:
Replace SuperSU with Magisk on our ROM

I found this topic which seems pretty clear to replace SuperSU by Magisk.

https://xdaforums.com/axon-7/how-to/replacing-supersu-magisksu-a2017g-t3614024

But it indicates that we are supposed to replace the boot img file by the one of our LOS ROM (base of the discussion is on B04 B05, means Stock ROM I guess?).

I found a file boot.img in "lineage-14.1-2017xxxx-nightly-axon7-signed.zip".

is it the right file? is it safe to try ? since I succeed to backup the boot under TRWP 3.1.1 ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JTruj1ll0923:
I've always just gone into SuperSU and at the bottom of settings there is an option for full unroot. Then it asks to restore boot image and some other things to which I always said yes. Then just reboot before booting into recovery and flashing magisk. Worked for me the last few phones I did it on, latest being about a month ago.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] thehebrewhammer:
Hi I was hoping I could inquire into the wifi calling hurdles, so that someone on here (or myself) could possibly work together to get it working.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dwnoel:
I did the change from SuperSU to Magisk 13 ... which working well, including the "hide" option that bring back apps like netflix on the Store.

BUT .... from the time I did the SuperSU uninstall; I can't patch the nightly LOS update !? TWRP fails claiming "ZIP Verification failed"

that means even for the Magisk upgrade, I had to retrieve the "boot.img" from current ROM zip, because Magisk was claiming the BOOT image was not the original.

now my system is working, with root, but I can't update LOS anymore !?

any idea how I could fix it please ?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Jeremy-X:
Hello,

I'd like to know which line of logcat should I grep to see when the AKM DAC is being used.

I have Poweramp build 704, with high res output. The output is showing Snapdragon 24 but it seems in the log that the sound is routed to the hi-fi headphone device. When I use OpenGL or Audiotrack output with 32 bit RAW PCM it seems the DAC is in use but [MENTION=1983515]16bit[/MENTION] 48Khz (My test file is FLAC 24/96).

Thanks :)