yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] robertaramar:
I have also done a clean wipe and have installed the 15/06 and since today the 25/06 build. I do have Magisk 16.4 installed. I am NOT suffering from reboots, neither with the 06 nor with the 25 build.

Since 25, I don't have Google crashes any longer.

Ok Google still does not work.

Battery drain is significantly higher than with 14.1.

All summed up, I am a happy user. I don't want to brag, I just want to add to the information in this thread that some issues reported by others don't seem to be inherent to all installations.

[MENTION=5027381]OrdenKrieger[/MENTION], thanks for the new build.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kaplah:
Volume working... Bluetooth blew up... :(

Well... The phone volume is working great now. Unfortunately now Bluetooth isn't working. I had it working in the previous version. To get it working I set Bluetooth to not have battery optimizations and set the AVRCP to 1.6. After the update bluetooth crashes after about a minute post reboot and won't come up. I've changed the AVRCP, cleared the Bluetooth Data and Cache, and wiped all the paired devices. I have a Bluetooth Speaker, a Asus Zenwatch 1, and a Google Daydream. This issue occurs with any of those devices. Am I missing some magic here?

Dalvik Cache wipe on upgrade? Yes

AVRCP: 1.6

Bluetooth Cache Cleared

Bluetooth Data cleared

Wipe all devices

Reboot.

Bluetooth crashes after a minute.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
Bluetooth works fine for me in 25 build. I was using the build of the 9th (or so) and I feel like the battery was much better... Did not install any new app in between. Looks like something is draining... I'll investigate!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] dr3am_r:
Would this be Lineage supported in the future? Would be great...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] robertaramar:
doesn't seem so

had only a few calls, nobody complained. Was on car bluetooth, though.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Hille2001:
i installed last Build and got stuck in red Warning Screen

was only able to boot in fastboot and always stucked in red screen

phone does not recognized by laptop

last way was in red warning screen to push power button and then a linux sign flashed short , next time pressing power ,linux sign stayed longer and then started TWRP in normal way

then in Terminal App i was able to sign with the Code in Post2 and my phone started fine at next boot *puuuhh*

phone call loudness adjustment is working and my call partner does not mentioned any echo

seems to be fixed
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kaplah:
Volume working... Bluetooth blew up... :(

How did you update? I didn't blank the phone again to a clean slate before installing build 25. I'd hate to do this as it means setting everything up again.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Hille2001:
Here is BT working out of the Box
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haerwu:
Settings FCs again but I plan to spend a bit of time to check does it work when flashed cleanly (with or without gapps etc).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Liquid5n0w:
My bluetooth is fine, I'm running the latest and I dirty flashed it over the previous version. I also am running the hellgate x5 kernel.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
FYI if you experience random apps crashing in the background I'd avoid using the new theme engine.

Settings / Display / Advanced / Style

Like I wouldn't even touch it.

Theme engines always mess with apps that don't play well with them. If anything, maybe try that feature a few months from now once someone else fixes the bugs. All I know is I clean installed the ROM and didn't touch those styles this time and have not experienced one background app crash yet.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
Dirty flash the ROM, flash gapps recent version, flash magisk, wipe cache dalvik. Reboot.

I now reverted to the build.of the 9th where the battery seems better.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Thunderfalcon:
Hi xda community

i have a problem with calling people.

I clean flashed yesterday the newest Version ROM and everything seemed fine.

My Phone is connecting to the cellphone provider and 4G is working fine.

Now when i try to call somebody i get "Servererror, please try again later".

If someone tries to call me, its working fine. Strange...

Does anybody had this problem before?

Oh and i have installed the following bootloader: ZTE_A7LOSv1_UniversalBootStack.zip

and the following Modem: A2017G_OreoModem.zip

Even more strange is, that now only one number worked to call to... but no other number at all :(

Edit: Solution found: i had to disable the extended lte mode. Now calling works fine.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nodea:
A2017G. B12 from nfound. Clean install latest build (wiped dalvik, system, cache). No Magisk. SElinux permissive. Bluetooth ok even with car radio. No echo.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
I found a bug in msm kernel modul preventing activation of low persistence (VR) mode.

echo 1 >/sys/class/graphics/fb0/msm_fb_persist_mode would switch this mode, but a cat on that handle shows it's still 0. how to enable kernel debug messages and where to find them?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Narada2XK:
For the lockscreen notifications being turned off, this option is available. When I choose this option, as I do not want notifications on my lockscreen period, the setting never sticks. The notifications still come fast and furious on the lockscreen.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jcian135:
Hi [MENTION=5027381]OrdenKrieger[/MENTION] & everyone else.

I decided to flash LOS 15.1 (20180625) after awhile being on AEX. I did a clean flash. Wiped System, cache, data & internal. Everything went smoothly except now that the camera doesn't work at all (default & Pixel Camera). Anyone with the same problem?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
It is easy to get this wrong. There is a link to a guide by [MENTION=8456254]EBeatFLA[/MENTION] in the OP of the AEX thread as you need to use the - 7 and - 8 twrps with the right bootstack.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] aLexzkter:
So...am I the only one having double vibration bug?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] eaponte23:
I haven't used edl but look in it's folders and find where the other .imgs get stored at and rename the new one with the one you're replacing. Then flash like you would normally
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
to answer myself, I found the reason why the switch won't work:

In kernel drivers/video/msm/mdss/mdss_dsi_panel.c lp_on_cmds and lp_of_cmds

These try to load "qcom,mdss-dsi-lp-mode-on" and "qcom,mdss-dsi-lp-mode-off" from dtsi file.

However for over panel these entries are missing.

[MENTION=5027381]OrdenKrieger[/MENTION]:

Can you please copy those entries from dsi-panel-s6e3ha3-amoled-dualmipi-wqhd-cmd.dtsi into dsi-panel-zte-samsung-s6e3ha3-5p5-wqhd-dualmipi-cmd.dtsi

The following entries are missing:

qcom,mdss-dsi-on-command-state
qcom,mdss-dsi-off-command-state
qcom,mdss-dsi-lp-mode-on
qcom,mdss-dsi-lp-mode-off
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Yes, you need to use EDL tool as per https://xdaforums.com/axon-7/development/tool-axon7toolkit-t3573108. It is pretty automated. I first used the toolkit to get the regular twrp and then used that to flash -7. Just do not get nervous - this is eminently survivable. Once you have the regular twrp installed, you can copy the -7 .img to your sdcard or your regular memory. You can even use a usb-stick to flash from (OTG).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Liquid5n0w:
I was previously running the bootstack that is linked in the OP. I haven't changed it since I first upgraded to 15.1
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BlackAfghan:
SELinux fix

Sorry, I don't want to be rude! But I didn't ask for an official LOS status. I'm a developer on another device, and I know how hard it is to become official nowadays! And for some reason they are particularly picky when it comes to those SELinux rules. But that doesn't has to mean you need disable it completely. Here is a quick way to generate the rules automatically (see https://source.android.com/security/selinux/implement):

increase the dmesg-log buffer by changing CONFIG_LOG_BUF_SHIFT in the deconfigs, to something more useful (e.g. 20)

boot the phone, use everything a bit and export the dmesg-log to your (Linux-)PC together with the sepolicy-file

than run something like "audit2allow -d dmesg.txt -p sepolicy", which should create reasonable rules automatically

remove all rules requested by user apps

This should allow enabling SELinux without breaking anything. Probably won't satisfy the LOS-guys, but gives us 99.99% of the benefits, without breaking anything.

Hope I could help.. And thanks for your work! :good:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
I run f2fs without a problem.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
No, but honestly, I thought it was simply a slightly changed vibration pattern in Oreo compared to Nougat.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Thunderfalcon:
I still have the problem, that when i try to call somebody i get the message "Server Error: Please try again later".

It happens with this and aex rom, so is it maybe a Problem with the Modem? On Lineage 14.1 before it worked fine.

I have the newest bootloader and bootstack installed. I'm trying on suisse provider Swisscom. If i search manually for networks and choose a network from the same provider i can make 1-2calls, then i have to search and switch again.

I already tried:

- Reboot

- Calling with/without 4G enabled

- Modem 2017G from nfound

- AEX Oreo ROM (same result)

Does somebody have a hint for me?

Edit:

Solution found:

I had to disable extended lte under mobile settings. Now calling other people works fine.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mow4cash:
Has anyone found a fix for "ok google" or can shed some light on the issue?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haoyangw:
Yes it is slightly faster in writing speed and automatically trims storages so performance is consistently high. However it is a very new filesystem compared to ext4, and so in comparison it's not as stable/safe. For example ext4 has very sophisticated filesystem repair and checking tools that can handle most data corruptions very well, so data loss is rare even if things like random reboots occur. On the other hand f2fs(if I'm not wrong) has no legitimate filesystem repair program, so if you face more serious data corruptions, your data is lost. You'll have to wipe the partition to use it again(I speak from personal experience, had lost data once due to random reboot before). And this is just one example that I know of, I'm very sure there are a lot more. There's a reason why Linux OSes still stick with ext4/ext3 even when they detect an SSD and f2fs is fully implemented in the kernel for a few years. And also why Samsung(the creator of F2FS) never used it in any of their flagships in recent years. But perhaps over time, as F2FS becomes more sophisticated like ext4 now is, it will become more common and become recommended :) Though by then an ext5/6 might have emerged that matches/beats f2fs(right now ext4 is already very close in performance to f2fs). But if you backup your data regularly and/or don't face random reboots feel free to try f2fs, it does feel faster(I'm using it right now :)) and well it is supposed to be flash optimized(unlike ext4), so I'm sure there are still merits ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] robertaramar:
I hope this will not end up in any rant.

I am NOT asking for a date, but

I am asking the question whether any of the developers involved in the Axon7 LOS builds intends to make this an official ROM sometimes.

If there are no intentions or motivations for that, I would highly appreciate, if someone says so.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AceNovel:
Hi, anyone noticed a bug - battery drain when listening music?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haoyangw:
You have to be more specific lol, about how many percent per hour? Using bluetooth or headphones? What kernel(stock or others)?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] AceNovel:
Headphones, stock kernel.

I'm talking about this bug https://xdaforums.com/showpost.php?p=76940480&postcount=3681 or something like that.

Have you seen something like this here?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Well did you install that stupid "DAC patch" that does nothing?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jawz101:
I think this is a fair question.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Maybe, I can't tell for now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] koftheworld:
Anyone else on Verizon notice no volte in the latest release?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
"I can't tell" is one of those subtle English expressions that I find very handy because it may mean either "I don't know" or "I know but something prevents me from saying" and the distinction, which is not a small one, is somehow there in an unobtrusive way.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
Yea or I just don't know, if I want to put any effort in this device? Who knows.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
The problem is that the "Google" app isn't installed as system app. If you open ththe google app and go to settings -> Google Assistant/Settings -> Devices/Smartphone -> Voice Match

You will see that this option is greyed out.

Install magisk modul systemize. From shell you start systemize, choose "google" app and systemize to priv-app

I had to increase the size of magisk.img before to make it work, because the google app was too large for the magisk image.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] mow4cash:
Voice match is not grayed out for me and both assistant and the google app are priv-app. I still don't have "ok google" working. Is it working for you?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] haerwu:
Looks like next phone will have to be from more popular vendor :(
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
Could we please address the "Google keeps stopping" issue, it's definitely linked to "Ok Google"-detection not working.

When I restart my device, the few seconds before the error message pops up, voice detection seems to be working briefly.

I say "Ok Google / Hey Google", I get the white frame around my screen, Google assistant pulls up from the bottom and in that instant the error appears.

What I've done so far:

wiped everything (System, Data, Caches) and reistalled LOS with the files from the OP (using Open G-Apps Mini)

wiped the caches of Google, Google Play Services then wiped their data, restarted the phone and went through the resulting setup process again

checked if the Google App and Google Play Services are system apps via TitaniumBackup (as expected, this was true)

almost tossed my phone at the wall after wasting a good 2 hours on this s**t :mad:

[MENTION=4531278]_phk_[/MENTION] The setting you described has always been available for me. Does your voice detection really work form any screen?

Would Magisk be a necessity to check / enable this? Because TitaniumBackup shows the same info and allows me to force an app to become system app.

It is however ALREADY a system app, so the problem seems to lie elsewhere.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] gregfrankenstein:
This tells me there are more than just a few kernel blobs and ZTE wrote a large portion of the OS itself. Given their track record of spyware, this is not comforting.

The Linux kernel has vendor blobs. They still release the source.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ITenson:
Hey, my battery took a dive with the build on the 25th as well. I've been playing around and I seems to have mitigated it a little bit with the following setting adjustments:

- CPU set to Efficient (instead of Balanced)

- Wifi Scanning to off in Location

Don't know if it will help your case but something to try anyways.

Cheers!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] 2000impreza:
I seem to have a fairly bad echo issue with the latest build when using the speakerphone. I don't hear any echo on my end and but it is fairly bad on the other end. Even with the volume all the way down it seems to be happening. Anyone else have this issue?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] oeffoeff:
I would also be interested in contributing. I wrote OrdernKrieger about this but got no reply.

(I'm a embedded sw engineer but new to android)

What do I need to rebuild the releases posted here?

If I understand correctly:

LinageOS official source - CHECK

Axon7 Oreo Kernel Sources - CHECK

Axon7 Oreo driver blobs (can be extracted) - CHECK?

Axon7 device specific configuration (like here but for for OREO) - UNCHECK

Is this correct? And without the last part we can't rebuild OrdenKriegers images?

I think to be able to set up a proper build is a mandatory requirement if we want to contribute based on OrderKriegers work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Az Biker:
* * * Thread Cleaned * * *

Please keep discussion in this thread directly related to the development, or troubleshooting of this Rom.

If you'd like to argue about GPL license, source code, or whatever else, please start a thread in the DISCUSSION or GENERAL sections.

If you believe a source code violation ( or any violation ) has occurred, please REPORT it, and allow Moderation staff to look into it.

Thank you.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BlackAfghan:
Excuse me? I surly never accused him of breaking any agreement! He doesn't "has to do" anything, but there only ever can be a official LOS 15.1, if those stuff gets public. And I have contacted him privately, like many other people here.

And concerning etiquette: it is considered good etiquette here to release your sources! So that other developers and people who are interested in it can benefit from it.

And I don't think it's good etiquette to publish only the bare minimum, only after several people begged for it, so that this thread here doesn't get deleted. At least not under normal circumstances..

One of the main reasons I use LineageOS, is because it is Open Source (except vendor blobs). It may not mean anything to you, but it means a lot to me and many other people.

And I think OrdenKrieger as a respected developer, understands perfectly well, what I'm trying to say here. And it's not meant to be disrespectful or ungraceful in any way! The current situation is just not sustainable in the long run. I just asked for clarification when that might change. :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
I didn't notice this error any more, however I'm on AEX now and I installed Google Assistant from Play store additionally.

So does "ok google" work for you at all?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
Not at all, I've pretty much tried everything at this point, wiping, uninstalling, reinstalling and resetting multiple things.

I'm busy for the next few weeks, but after that I might switch ROM. Let's hope we get a fix until then.

Or even better; some ingenious forum member posts a how-to-fix before that. ;)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] _phk_:
What happens if you open the Google APP and press the mic button next to the search box? Does voice detection work there?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] robertaramar:
For me it does, though also no ok Google detection on any screen
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Surge_:
[MENTION=4531278]_phk_[/MENTION] Yes, it works from there, everything else microphone related works fine too. The problem seems to be some essential background process the voice detection needs that keeps dying after startup ...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] eaponte23:
I have PixelExperience installed with bootstack from this OP and Google Assistant works fine so far. ROM has gapps baked in.

I remembered your post after installing this ROM and getting the prompts at setup (Ok Google). Figured I'd let you know my setup is fine.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] :
You forgot to use the @

Enviado desde mi K88 mediante Tapatalk
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xXDomXx:
Dear all,

somebody here who has Dolby Atmos getting work with LineageOS 15.1 on Axon 7?

I always getting bootloops with every version from guitardedhero (https://xdaforums.com/android/software/app-dolby-atmos-axon-7-oreo-port-t3740508/).

I tried it with clean flash and no other modules on Magisk 16.0 (and Beta 16.4).

Installed AML and other Mods like VA4, Ainur Sauron etc. are all working well.

I'm thankful for each hint and support from you guys.

Best Regards,

xXDomXx
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] raystef66:
Try this version : https://androidfilehost.com/?fid=5862345805528039633

Working smooth on AEX5.6 and Magisk 16.4. Never tried it on Los15. Just give it a try and see ;)

Install it within magisk /modules +
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xXDomXx:
Many thanks for your post. Unfortunately same Problem as in the other versions --> bootloop.

Maybe it will be fixed in the next weeks - I hope so cause I loved Dolby Atmos on LOS 14.1 but won't go back cause of nice HDR+ features with working GCAM on LOS 15.1.

Best regards,

xXDomXx
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
Is the sound bad without Atmos?

While I'm at it, does the network based location service work. It was broken on B35 and B12.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ITenson:
It's a bit blend with just AudioFX that is baked into LineageOS but Atmos is just one option to try to make the phone sounds better. I think a lot of us are using Viper4Android which is working perfecting with our phone and LineageOS. It does take some playing around with the settings but I think it sounds just as good as Atoms if not better due to the extensive settings that could really make it sound just the way you like it.

As for location services, I use battery saving mode most of the time which uses network based location and it's been working fine but I never had trouble with it on B35 so I can't say that it won't have problem for your phone still. It's working for me on the latest build thou.

Hope this helps.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] xXDomXx:
I used Dolby Atmos only to make the sound better from the front Speaker. The difference with and without Dolby is huge.

Of course V4A is great, but in my opinion only when you play music via Headset, Bluetooth or Dock.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
same and I agree. for Dolby front speakers u can notice some differences mostly louder max volume. I like leaving surround, dialogue on and intelligent open. volume leveler got too loud at times and I couldn't hear bass enhancer much. v4a for headset though will have more settings and that's probably when it's better and noticeable
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
...that's not exactly legal lol. i won't say anything but there's been trouble between two devs since one just pointed out that gapps can't be baked in and the other one accused him of reporting him. would be better if [MENTION=5492451]NFound[/MENTION] could just see to it before anything bad happens

again, i won't say anything ?