yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
It's not very clear to me that the GApps can be legally distributed at all, as opposed to it being something tacitly tolerated by Google after CyanogenMod, back then, agreed to stop outright "baking them in" and having an independently-distributed package was a solution that Google seemed perhaps alright with.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kaplah:
Volume working... Bluetooth blew up... :(

I've still got this issue. Quick question: What is magisk? I'm not familiar with it.

The issues I'm having with LineageOS 15.1 on my phone are as follows:

1) The aforementioned Bluetooth crashing. I can seem to clear this up by wiping the cache and data from any app that uses bluetooth, formatting my dalvik and cache, then rebooting. This clears it up for a few days before bluetooth starts dying again. This alone is making me consider switching back to stock.

2) Music and podcast apps stop for no reason. My best guess is battery optimization is being overly aggressive. I've turned it off for the apps I use and this alleviates the issue somewhat. I'll be listening to something and it will stop for no reason.

3) Chromecast audio streaming does not work. I have the chromecast audio and I cannot seem to connect to it. However I can connect to my google home mini. Odd issue.

4) "Google" stops randomly at startup. Sometimes it works great. Sometimes it just stops working. It's driving me mad.

5) Netflix. I can't install netflix. :(

I've not tried "ok google" detection as I rarely use it with my watch and my google home mini being with me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
I have no idea. But we both know it's like that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Waancho:
Hi,

Currently i have latest AEX installed on my 2017U.

I want to try out LOS 15.

Do i need to flash the modem?

And is the LOS battery life better compared to AEX?

Thanks.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Cablespider:
I assume you're using Nfound's B12 bootstack. If so, a modem install is not necessary. Should you decide to flash the universal bootloader linked in the OP, you will need to flash the modem afterwards.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kaplah:
[RESOLVED] Volume working... Bluetooth blew up... :(

Ok, I've fixed my issue, but I'm afraid the way I did it was by basically starting over with a different rom and a different set of instructions. I followed the instructions here:

https://xdaforums.com/axon-7/how-to/guide-axon-7-custom-oreo-roms-newbies-t3786693

And I wound up with a fully functional phone. None of my issues above have surfaced so far. I'm starting to wonder if the bootloader package was flawed because my volume buttons didn't work correctly on the boot selector (Up did nothing, down went up, start selected). The new setup also allows me to install netflix and watch my purchased Youtube videos. I've not tried wifi calling yet, but so far so good.

I'm not sure the issues I was encountering were bugs in the lineage OS rom, or if they were the result of a bad bootloader image, or even an issue with the standard kernel ( I switched to hellgate). The one I got from the link above is chugging away happily. Thank you guys for your help. Hopefully anyone else having issues will find this solves their problem.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] brian117:
Yes, if you can please try WiFi Calling and let us know if it works or not. The lack of information regarding WiFi Calling, even from the dev himself, has yet to be given on this ROM. I've been wanting to jump ship to this ROM but WiFi Calling is a must in my situation. Nobody has reported yet if it works or not. Please let us know.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] brian117:
Thanks for confirming. Guess this ROM will sit on the backburner. Bummer.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Is there anyone who can just list all the current problems?

I just fixed "Ok/Hey google" so the assistant is working properly now from all screens.

I also know about the VR low persistent mode issue, but those values are not tuned for our device they are tuned for the nexus 6p aka Angler from which that configuration file was made according to the commit history.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
[MENTION=4911249]Unjustified Dev[/MENTION]

Disable WiFi for locklock and see what happens. I submitted a bug on jira but it got rejected for being an unofficial build.

https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-1927

https://www.reddit.com/r/LineageOS/comments/8uey5g/los_151_bug_when_toggling_wifi_on_system_apps/
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kingo64:
Is camera flash working correctly? I've heard it is broken on most Oreo ROMs.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
Hi Udev! Great to hear Form you.

According to filename Angler should use exactly the same panel right? So is there really special tuning necessary?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Yes, although it's the same panel we probably have a different revision (newer). And you have to factor in the device wiring and the processor difference. Then you have to factor in zte configuration there's display changes in mdss as well. I'm not familiar with configuring it for our device, but I'm sure I can find someone from Lineage with that info.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
Wow, I didn't know that it is so complicated. However the switch is done in the old kernel in some mdss file. It should be possible to convert this infomation into the dtsi file.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ssirK:
is this availaible in this build on your androidhost ?

https://androidfilehost.com/?fid=5862345805528045697
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
That's great! Thank you for the awesome work that you do. Is the bug that you fixed related to the random Google app crashing that happens? A few things I've noticed:

1) volte on Verizon isn't working. I get the LTE+ symbol and enhanced 4g is enabled, but I lose data during calls. I'm using the recommended bootstack and modem. It worked in prior builds.

2) phone info menu is only accessible through an app and not through secret code (not that important but interesting)

3) battery drain. The latest build using battery at a good clip more than any other build I have been on.

4) signal loss. I notice this is in the car a lot, but the phone losses and regains signal very frequently while driving.

5) sometimes the phone rotation gets stuck. I have to rotate the phone the opposite landscape way to unstick it.

6) the wallpaper sometimes crops itself after these sticking events

7) I sometimes get slower charging using car chargers/cords that I know I've gotten rapid charging with before with earlier builds.

Thank you again for your help. I'll write in if I see anything more.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Sadly for batter the kernel is a mess I'm really counting on zte to eventually give us something. Might have missed the post where I explained the latest kernel source for Oreo is from an old beta with horrible battery life. I reversed the dts (device tree source) from b12 which made things a hell of a lot better because the phone was giving a warning about the heat and you could go from 100 to 0 in less than 45mins. Could also be the issue with charging as well. Also to remember anything cosmetic on Lineage is purely their issue I've seen a few commits up for testing that might address some of your other problems.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I think so. Hopefully that's the one that boots I uploaded several because I ran at least 5 builds today and the last one didn't boot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I'll see about bringing back those changes they were completely stripped in the Oreo kernel source.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
Yes, flash is working just fine in the standard, preinstalled Snap camera app.

I tested some version of GCam ("GoogleCamera-Pixel2Mod-Arnova8G2-V7.9.5.apk") for it's auto-HDR mode (worked fine) but flash timing was messed up there. So if you plan to use third party camera apps you'll probably experience the bug.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
Understood regarding the kernel. Any thoughts on the volte situation I mentioned? I am pretty sure it was working in prior builds.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
At&t doesn't allow volte on byod so I'm out of luck. I already talked with zte they won't give the axon 7 certification so volte doesn't work for me on Cricket as it isn't implemented in the modem.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ssirK:
i tried it, it boots at least ! will check the other stuffs later

thanks ! :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kaplah:
Wifi Calling

Hello,

I've given wifi calling a try and I'm not seeing it come up. My test methodology was as follows:

1) Turn on wifi calling

2) Turn on airplane mode

3) Manually turn on wifi and connect to my network (Essentially assuring that I'm not tied into my 4G LTE network

4) Attempt to make a phone call.

To be fair to the devs, Wifi calling is an issue on most custom roms. I've had this issue with my Mytouch 4G and my Samsung Note 3 with Cyanogenmod. Wifi calling while baked into the OS now still requires some proprietary code from the carrier to work. They don't always push that code out to custom roms. Now I've heard that if your phone and plan support "T-Mobile Digits" and their "Digital sim" you can use that for sending your calls over wifi. On top of that it's supposed to get better call quality than the older wifi calling.

Gotta tell you that this used to be the killer feature for me too as my house's aluminum siding creates a perfect Faraday cage. 5 bars T-mobile service outside, 0 indoors. Same issue with TV signals and Radio. My solution there was to mount a rooftop antenna. However even with full wifi signal sitting ontop of my T-mobile router I'd still get a very poor audio call with wifi calling. My solution for T-Mobile was a microcell attached to my router.

I'm not talking about the rebranded Asus 1900AC that Tmobile offers for wifi calling (great router by the way!), or the cell signal repeater. The microcell (This device. https://support.t-mobile.com/docs/DOC-36766) ties into your home broadband internet and provides a full 5 bars. This has worked far better for me than wifi calling. T-Mobile offers up to two devices free to their existing customers. So I have the wifi router and the LTE Microcell. If you're on T-Mobile this is a better solution for you. Other providers... not sure. Verizon charges a hefty price for their microcell even to customers on contract who've been there for years. Sprint and AT&T I'm not sure.

Sorry I don't have the results you're looking for. I hope these alternatives get you over the hump and where you need to go. For me the stability I've now got with the RR rom is well worth giving up the wifi calling feature.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
It works okay on this rom?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Did you get a chance to check it out? Assistant works from the lockscreen and all other places for me.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] JTruj1ll0923:
1) Try to flash the APNList file from [MENTION=319057]Oki[/MENTION]. I am not using LOS, but on AEX 5.7 my Verizon Volte is working fine. You might need to enable it in the phone info menu and then trigger carrier provisioning.

2) Works with Google phone on AEX at least. But yeah, not the stock one.

Other than that, I'm sure our awesome devs will figure things out
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] apokolok:
Yes, assistant works as supposed, everything else seems to work as good as in prior releases.

Thanks mate!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
ok I checked the meaning of the dtsi file vectors in kern/Documentation/devicetree/bindings/fb/mdss-dsi-panel.txt and after comparing with the old kernel it seems I can refind some of the commands, although there are so many differences to old kernel's mdss_dsi_panel.c. I don't even think this would work properly on the Nexus 6P

The first byte for example must be 0x29 instead of 0x39, so the dtsi file is wrong in many commands.

So all we need to do I copying the commands from the structs dsi_cmd_desc R_AID_config_cmd(_1..5) structures as they are called by their calling functions into the dtsi file and it should just work fine :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Wow.

I'm glad people like you exist, I don't really get much of this, but apparently some of you do, and that's great.

As long as everyone helps with their own way we can push forward. :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AxonVeezy:
Thanks unjustified for this update. From the start ok Google wasn't working or any voice typing. After the June update I was getting more crashes. This July update fixed ok Google from any screen, voice typing and no more random app crashes so far at least for me.

Greatly appreciated
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
Hey guys,

Just did a clean install of lineage and getting a random out of memory error on my phone when Google photos trys to sync my online photos to my phone (only photos on phone are the ones locally stored none that are online).

I'm not running any custom kernels just the latest magisk, could that be it, I don't think so because it was running fine when I was on AEX. ?

Attached a log and a few screen shots of issue thanks in advance.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
About the phone rotation it may be the sensor HAL. Could you test if pickup sensor and hand wave works for you in doze? If anyone can test that, let me know if it works. With the recent changes I made, I now have those features as it wasn't working for me before.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
Hi, I'm currently running the 20180625 build. I tested the Ambient Display functions using Force Doze (with the "don't disable sensors on screen off" option ticked, as far as I understand that emulates the default Doze mode the closest).

I turned my screen off, waited 3 minutes each time (to make sure the app kicked in) then performed the Ambient Display gestures. Afterwards I checked the Force Doze stats to make sure the phone really was dozing during that time (it was, according to the in-app stats).

My conclusion: all three Ambient Display gestures (pick-up, hand wave and pocket) work as expected during Doze mode.

However pick-up has about a 2 second delay before activating which makes it feel very sluggish, it's almost unpractical to use for a quick glance at the clock IMO.

Hope this helps.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
You don't need to actually force doze. It should just work pick up and hand wave once enabled from settings even if you don't have a notification. I just ran a clean build without my sensor changes and I'm going to test again to make sure.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
Ok, got it. I don't usually use Force Doze, I just wasn't sure if those gestures would behave differently when the phone is in that "deep sleep" mode.

Is there any way to shorten the pick-up delay to screen on? I reckon it's a Lineage issue, so they'll probably have to fix it ...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BlackAfghan:
[MENTION=4911249]Unjustified Dev[/MENTION]

Welcome back! Would be great if you could add speaker rotation support to your next build.

Please add to /system/vendor/etc/mixer_paths.xml (preferably after the "speaker"-entry):

<path name="speaker-reverse">
<ctl name="SLIM RX2 MUX" value="SB1_PB" />
<ctl name="SLIM RX1 MUX" value="SB1_PB" />
<ctl name="SLIM_0_RX Channels" value="Two" />
<ctl name="PORT2 Sync Domain" value="slimbus" /> <ctl name="SDTO2 Source Selector" value="SBI1" />
</path>

And to the build.prop:

ro.audio.monitorRotation=true

Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
[MENTION=4911249]Unjustified Dev[/MENTION]

I converted the commands from old Nougat kernel into the dtsi file:

qcom,mdss-dsi-lp-mode-on = [
29 01 00 00 00 00 03 F0 5A 5A
29 01 00 00 00 00 03 F0 5A 5A
29 01 00 00 00 00 02 B0 0D
29 01 00 00 00 00 02 B1 08
29 01 00 00 00 00 02 B0 08
29 01 00 00 00 00 03 B1 30 56
29 01 00 00 00 00 42 CB 10 01 80 00 00 80 60 00 00 06 05 00 00 00 00 0D 00 15 9A 00 00 00 00 10 00 00 00 00 9D 00 00 CA 0A 0A 03 C5 84 CA 0A 0A 0A CA CA CF D1 CD C3 C5 C4 0A 0A 0A 0A 0A 0A 00 00 0C 01 7B 4D 00 00 10 00
29 01 00 00 00 00 02 51 50
29 01 00 00 00 00 02 51 50
29 01 00 00 00 00 02 F7 03
29 01 00 00 00 00 03 F0 A5 A5
];
qcom,mdss-dsi-lp-mode-off = [
29 01 00 00 00 00 03 F0 5A 5A
29 01 00 00 00 00 03 F0 5A 5A
29 01 00 00 00 00 02 B0 0D
29 01 00 00 00 00 02 B1 80
29 01 00 00 00 00 02 B0 08
29 01 00 00 00 00 03 B1 20 03
29 01 00 00 00 00 42 CB 10 01 80 00 00 80 60 00 00 06 05 00 00 00 06 05 00 15 9A 00 00 00 00 04 00 00 00 00 9D 00 00 CA 0A 0A 03 C5 84 CA 0A 0A 0A CA CA CF D1 4D C3 C5 C4 0A 0A 0A 0A 0A 0A 00 00 0A 01 7B 4D 00 00 08 00
29 01 00 00 00 00 02 F7 03
29 01 00 00 00 00 02 F7 03
29 01 00 00 00 00 03 F0 A5 A5
];
qcom,mdss-dsi-on-command-state = "dsi_lp_mode";
qcom,mdss-dsi-off-command-state = "dsi_hs_mode";
qcom,mdss-dsi-default-command-state = "dsi_hs_mode";

I think that's the only thing that needs to be done, editing/replacing those values in arch/arm64/boot/dts/qcom/dsi-panel-zte-samsung-s6e3ha3-5p5-wqhd-dualmipi-cmd.dtsi

However I'm not sure if the values for mdss-dsi-on-command and mdss-dsi-off-command are right and perhaps we should use these values. In this dtsi file also 0x29 is used as command byte like zte did it in the old kernel for most of their commands. https://android.googlesource.com/ke...rm64/boot/dts/htc/dsi-panel-s1m1-s6e3ha3.dtsi
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] 2000impreza:
Just wanted to add one more issue.

- Echo on the other end of the call when using speakerphone. Essentially when on speakerphone, the other person hears a echo of their own voice. Almost like the mic is too sensitive or mic gain is too high. I tried editing the mixer_paths with no success.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lllGurulll:
I was hoping that was fixed by now. So no progress at all or is it getting better?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dhammika71:
I guess no.

20180625 built is worse. No sound in calls at all.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
But have you tried my build?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dhammika71:
Do you mean 14.1? If not, share the link.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
14.1? Why would I be building that? Someone posted the link might be a page or two back.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lllGurulll:
I could guess at the post you are referring to but it would be nice to know which post so I don't download the wrong one. Is it the one for 711?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Yeah the one that fixes ok Google probably fixes the echo issue as well.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lllGurulll:
Has anyone installed the 711 file and confirm the echo is gone. I'll switch now if it is.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
I don't have any echo on that build.

---------- Post added at 04:48 AM ---------- Previous post was at 04:20 AM ----------

Two questions-are we sure that the apn settings are filled out right for Verizon, and how can I edit/add to the current? My apn settings seem to be locked out.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lllGurulll:
Thanks. Just curious are you using a custom kernal and which bootstack are you using? Universal or B12
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] olus:
you are alone! no one has no sound in calls in this build. build isnt worse, but your install is. try clean flash without custom kernels etc

echo during normal calls and not adjusting incall volume is fixed for at least 2 weeks now.

this guy is talking about echo when you make calls with speakerphone. seems like another bug.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lllGurulll:
Nope. I was referring to speakerphone a well. Are you saying that isn't fixed on 711
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
Talking about build 0625 here:

There is a slight echo on the receiving end when cranking up speakerphone to the last two notches. But I've never had a phone or ROM where that wasn't the case. I would imagine that at some volume levels this audio just becomes impossible to filter out from the actual conversation via software... but what do I know?

Everything else sound-related is working fine on my end.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lllGurulll:
Sounds good to me. Which bootstack did you use
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
The one provided in the download section of the OP, the file is called "ZTE_A7LOSv1_UniversalBootStack.zip".

So far there are no complaints about this bootstack-ROM-combination in this thread. I know AEX is a clusterf**k when it comes to info about what kernel / bootstack to use... which is why I've been reluctant to give it a try.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] olus:
ah ok, sorry then.

dont know, im still on 0625 and i never make speakerphone calls, sorry.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lllGurulll:
Thanks for the reply. I'm currently running dirty unicorns on b12 and hellsgate Kernel. I feel like hellsgate improved my battery life but it can only be used with the b12 boot stack. Curious if anyone had done that on Los.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
I wasn't using a custom kernel until today and I was on the universe bootstack listed in the op.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] okmikel:
The bootstack provided here called "ZTE_A7LOSv1_UniversalBootStack.zip" is B12 and I am using LOS 15.1 0711 with Hellsgate X12.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Kleva94:
Is it possible to implement this to fix daydream in the next build, [MENTION=4911249]Unjustified Dev[/MENTION]?

Edit: changing to "ro.product.device=ailsa_ii" in build.prop should be enough. Ediiting “handheld_core_hardware.xml” leads to crashes of basicly every app, escpecally trebuchet. It did not lead to errors on the first unofficial build, though.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Works for me on my build for today. Must have been some on Lineage side
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] olus:
do we have a chance to get this "build for today"? [emoji6]
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
Try restarting, wiping cache and dalvik. Had this issue too, after a few restarts it worked again for some reason ...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Changing the device name just makes some Daydream apps that would otherwise start in 2D mode start in VR instead. That's the first step, but we were doing that already with LineageOS 14, problem is with LineageOS 15, so far, there is no way to engage the AMOLED screen's low-persistence mode, making it blurrier than a 1970 movie edited by a 18 year old who was using motion blur for the first time.