yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Some information in case it's useful, as I've followed cheap Android VR for a good while...

If you want a non-Daydream headset that you can actually use for decent VR, I can recommend the Mojing S1, as it has a large FOV with Fresnel lenses that are better than the Daydream ones, and unlike the Daydream, it has focus knobs. Its only caveat is the Axon 7 can get very hot in it, so pay a lot of attention when you're playing with thermal configuration, and for the love of Lithium, never keep a back cover on.

Otherwise, and maybe better if you wear glasses, there is the BoboVR Z5, which unlike its predecessor, has an open design and so the Axon should not get too hot inside it; plus, it's made for Daydream so it comes with a compatible controller for cheaper than the original one, although I hear the controller is not nearly as good (note that many other VR headsets come with controllers that are not Daydream controllers, but just Bluetooth gamepads with or without mouse emulation functionality). The headset itself is good: it has sharper lenses and adds an eye distance knob, but it has lower FOV than the Mojing S1.

Of course this is all irrelevant if you don't care about using VR and just want the cheapest headset that will let you stick your phone to your eyes to try it out. In that case, I'd recommend a U Noton if you can get it for very cheap ($5-10), but it's uncomfortable and cannot be adjusted in any way, or a Ritech VR Max if that's $10-ish too, which should be better.

http://www.sitesinvr.com/viewer/viewer-calibration.htm has measured parameters and reasonably good QR codes for a few different headsets.

Low persistence did work, but on the other hand, VSync tended to be completely off in 14.1.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
Completely unrelated, but could you tell me if emulated daydream remote works? I've been trying that for a while on both a GSI and stock N, no go. I even changed the phone remotes.

You don't need a Cardboard to see if low persistence works though. As soon as Daydream starts on low persistence you'll see a huge amount of flicker, since it's sort of a black frame insertion thingamajig

Netflix VR is perfect to test this. Just select that you have a Cardboard under VR settings, and the app won't ask you to put the phone inside a daydream or connect a controller
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
I hadn't tried it in a while, since I bought an actual Daydream headset... I tried it now, and it doesn't work anymore for me, either. I'm on the official 15.1 release. Couldn't it be a change in Daydream itself, though? If you go to the controller's emulator web page, it calls it deprecated now; it didn't last time I had checked it. Maybe it'd work again with some older version of the Daydream app from APKMirror?

That's true, but if there's any tweakables (like changing the actual persistence time), they'd have to be checked out with a headset to make sure it causes neither obvious flicker nor blur. Without a headset, perhaps keeping the phone very firmly in your hands and in front of your head could give a rough idea, but... no more than that.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Choose an username...:
honestly I don't think there's any. it's good old black frame insertion. Maybe a duty cycle or something like that but I have no idea about the inner workings of it. by eye it seems like it's just one black frame then one normal frame, rinse, repeat. A slomo recording would be useful, I'm on B35, I might be able to ask a friend to record it at 900fps with a GS9+ tomorrow if that's useful fir something

Simply checking that the phone has insane amounts of flickering should be enough to ensure that the mode is working, that's for sure
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kripler7:
I fixed this issue by flashing a gapps package from mindthegapps on this page : https://wiki.lineageos.org/gapps.html

Just wipe dalvik cache and the flash the new zip over.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Penoro123:
I found what the issue was with every single browser crashing.

You only have to disable your browser and any app that crashes in the Privacy Guard menu. Just tap on the name of the app and it should disable Privacy Guard on them. Now, the only issue I have with the rom is that I can't use Airplane Mode without losing signal until a restart or by changing the preferred network type in the Mobile Network menu.

I also recommend removing AudioFX completely from the phone and installing Viper4Android. AudioFX makes the CPU go ballistic in usage when it's enabled, and it's enabled by default.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimhark:
Any specific recommendations for how to install AudioFX on Axon 7 LOS 15.1?

Thanks,

Jim
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
http://files.nwwn.com/~unjust/ forgot to say the build would automatically be copied here after being built. Let me know if GPS issue persists.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Penoro123:
Why would you want you want to install AudioFX on your phone, lol. It comes in the rom by default. I said to completely remove it, using a system app remover from the Play Store or using Ex File Manager.

If you meant Viper4Android, you can get it as a Magisk module, you just have to flash Magisk via recovery.

---------- Post added at 02:20 AM ---------- Previous post was at 02:17 AM ----------

Could you fix the Airplane Mode bug, by any chance?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jimhark:
Doh! Of course I typed AudioFX by mistake when I meant Viper4Android. I have Magisk installed. I'll search for the right module. Thanks.

Jim
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Penoro123:
Ah, you can download it directly from the Magisk app, just search for "Viper" and download the FX version. The XHIFI one causes too much noise, unless you have a dedicated amp, so don't download that one.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
Current bugs as far as I can see:

Vibration adjustment doesn't work in kernel apps and by default the phones vibration makes zapping sound but only with certain notifications.... And Not with other vibration like haptic feedback. It's almost like it's set too high... But only with certain notifications. Very odd.

Daydream has too much blur/blur reduction doesn't work.

GPS lock is slow.

AudioFX causes high CPU usage, I guess this isn't specific to our phone though.

Default volume adjustment is always media rather than ring.

There's an issue with different mobile network modes being set which results in the phone not returning to certain modes when toggling airplane mode. This has been described before as "no signal when toggling airplane mode" but if you look into the mobile network modes when testing the bug you see that the phone doesn't always get a signal when returning to "global" only. If you select something else it returns to that fine.

Random Mac Address (fixed in upcoming build).

Minor but perhaps not fixable: Gcam fails with 240fps slow mo mode.

Is that it?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
it worked, but it took some time to fix my location

gonna try more tomorrow out in the streets
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Stremon:
As I said in my previous post, none of the edl cable method works, and I tried them all.

It's like the EDL mode doesn't work at all.

---------- Post added at 04:21 AM ---------- Previous post was at 04:05 AM ----------

No I pushed on the light switch button of my bedroom :silly:

Of course I pushed the power button ;)

And yes I get the Linux small logo for few seconds and then it goes back to the bootloader.

I should mention I'm not a beginner with Android, I've been playing with custom ROMs and even making my own ones since the Nexus one, but one this particular case something got messed up when I flashed the bootstack and/or recovery obviously. I just wish it was clearly mentioned that this OP bootstack don't have normal EDL mode, I wouldn't have flashed it in the first place.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
Is there a way to swap recent and back buttons? Which version of magisk is everyone using and does anyone have Dolby installed? Mine doesn't show up after installing through magisk and rebooting

Edit - nvm found something through search and will try
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] nfsmw_gr:
Does anyone have the issue when you press the multitask button, the app you were using doesn't appear on the menu?

Steps to reproduce : you need to press the multitask button, since the app is missing press back button to close the menu, and press the multitask button again to show the menu, then app you were using would be there.

Attaching screenshots for example

As you can see I was on the xda labs app, I pressed the multitask button and the xda labs app wasn't there, the previous app I was using was there instead.

So I closed the multitask menu, pressed the multitask button again and mysteriously the xda labs app was on the list now.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Reverse back and recents buttons - Make sure to mount vendor

https://androidfilehost.com/?fid=1322778262903999789

Thanks Raystef!

For Magisk, use 17.2, which can be found by googling. If it doesn't appear after flashing, hop into your files and extract the magisk.zip that you went to flash in twrp. Go into the 'common' folder, and install the magisk apk.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
Thanks a lot I was wondering why vendor didn't show.

Wait it says pie. Also work with los 15.1?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
It should. If it doesn't, let me know

Also if vendor isn't showing in twrp, try flashing twrp again. Take the latest twrp .IMG file and flash it as recovery. Might do the trick
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ieuzwales:
No 4G

I've successfully flashed using the idiots guide on page ~126 from marshmallow stock. I have the A2017 Chinese version (6GB 128GB).

Problem is that I can no longer use mobile data 2G/3G/4G. I get normal service to call and text, but no data signal (I live in the UK).

I've tried flashing the A2017G modem which gave me no service whatsoever, and the A2017 modem leaves me in the predicament I'm in now.

Any help would be greatly appreciated.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Stremon:
So after bricking my phone with the OP bootstack, I still haven't been able to rescue it with EDL.

I just received a proper EDL cable today, but it still doesn't work with it, the same way as the 50+ test I did with other DIY EDL cables.

Since fastboot doesn't do anything when flashing and since I can't boot nor flash anything, I guess my phone is dead thank to the OP crappy bootstack.

So for everyone who got a A2017G like me (and maybe everyone else too), use a proper bootstack with EDL (like the one from Nfound) to avoid having the same problem.

Still can't believe this LOS release is "official" with the high risks of brick it involves.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tdm:
I know for a fact that every axon7, both U and G models, can enter EDL mode with method 3. If you haven't been able to enter EDL mode with method 3, perhaps you can talk to another G owner who has. Like this guy:

https://xdaforums.com/showthread.php?p=77730909

I can't speak to the G boot stack, as I have a U model. But many other people are succeeding in getting things working.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
Hmm I reflashed latest twrp 3.2.3-0 but vendor still doesn't show
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
If you have a proper edl cable, I think it's a timing issue. For me it's easier when the device is in dfu mode already. Try holding volume up, down, and power until you're in dfu mode. First plug the cable into the device obvious. Next while holding that button on the cable without letting go, connect the device to your PC maybe after 3-4 seconds after inserting let that button go and you should be in edl successfully.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
The edl cable from Amazon linked from oki's guide worked for me. Ships from China and takes about 2 weeks to arrive though. A bit more expensive than other cables but I wanted one that worked for sure and it does on U model
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
Magisk 17.2 is listed as the beta version on the Magisk download site. The OP here still points to 16.4. Is 17.2 'good enough' and necessary to use with the official LOS 15.1? I assume it attempts to fix whatever problems have come up with the transition to using a /vendor partition - is that the point?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BigMatza:
Radio off (no service)

I followed the procedure to a T from true B35 stock to the Oct 1 LOS 15.1 nightly (with Magisk added) on my A2017U. Everything works well, except that I can't get a cell signal at all. The phone was a refurb from the factory, straight from the package. I had to unlock the bootloader prior to doing all this.

I forgot where I saw it, but the screen flashed up "Radio off" at one point. I believe it actually did work at one point; and I assume this because the phone got the SMS notification from Cricket wireless to configure the APN. But is it possible that it wasn't true SMS, but instead the phone just interprets some stuff on the SIM, and spoofs an SMS message to itself? Because I was using Wifi to set up the phone, I hadn't actually attempted to use mobile data, or make any calls, until I had everything set up.

I did another full data/Dalvik/cache wipe, and reflashed the A2017U Oreo modem (from first post), but to no avail. I have tried all different data modes (e.g. WCDMA/LTE, etc), which did not help either. I even wiped the system and reapplied the ROM from scratch.

If I turn off the automatic network search option, I

immediately

get a toast error searching for networks. The phone does see the SIM, and it correctly displays the phone number on it. IMEI's for SIM1 and SIM2 also display correctly in settings.

I confirmed the SIM card is ok by trying it in another phone. I also tried another SIM. I also tried without a SIM, just to confirm that emergency calls won't even work.

There is definitely something up with the radio. I believe it's either defective, something deep in its config became corrupt, or there is some setting maintained outside the system and data partitions that is keeping it in the off state.

Very recently in this thread, I read about the issues with the network upon coming out of airplane mode. It seems too coincidental, even though I'm pretty sure I never put the phone in airplane mode, which is why I'm posting my issue in this thread.

Any suggestions are much appreciated.

If nothing works, my next step will be to restore back to stock B35. I assume for this that a standard EDL flash will repartition as necessary, removing the new

vendor

partition. Or is there something I need to undo first before this?

Much thanks for reading my novel :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Snaptraks:
One thing I will mention, is that using a USB 2.0 port seems to work best (I used the wire on pin 2 of the USB cable method). My phone was stuck in DFU mode, booting only to the bootloader warning screen, I could press the volume keys to select a boot mode (Recovery, Bootloader, System, etc) but it would only bring me back to that screen immediately. But yeah, I got stuck in DFU mode for hours when trying with the recovery and bootstack in the OP, upgrading from the latest official 14.1. I recommend using [MENTION=319057]Oki[/MENTION] EDL method to upgrade. Funny enough, I didn't wipe /data and kept all my apps and settings when upgrading from 14.1 to 15.1 official.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
This rom has been good for me on battery and performance. Able to reach 2hr sot every -30% on light~moderate usage latest 10/1 build with schwifty beta and jojoc. I hear audio is improved haven't tested yet, gcam working good, smooth and no slowdowns but did notice a few random shutdowns and mobile data turning off on its own which was fixed by a restart. Hopefully it was a one time thing and doesn't happen that often later on. Other than that, the rom is perfect once button swap is applied and i think the only thing it's really missing is Dolby. This could be better than stock oreo with a bit of slower charge about 1000ma less not a problem though if the drain is better. Thx to all involved in the work
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] FuzzyDunlop9:
Battery life for me is abysmal. Running stock lineage, no kernels or the joco script. Got magisk installed to get Google pay working with the config module and viper4android, that's it.

Is the audiofx issue I heard about causing the low battery life.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] austinalex23:
Some feedback

This is my first post, I've been following along with the development for the last month or so, thought I'd throw out some problems I'm having with the latest official update of LOS 15.1. For some background, I was previously on the unofficial build from August I believe, and then did a clean flash of the first official build, and did an OTA update to the build from this Monday.

First- Battery drain is terrible. It seems to be because of Wi-Fi. If I leave my phone unplugged overnight, I wake up and the battery has dropped 40-50%. If I turn off Wi-Fi overnight, the drop is less than 15%. This isn't necessarily a problem with the official build, battery drain was heavy on the unofficial for me as well.

Second- Magisk keeps breaking. I don't know if this would be better posted on a Magisk thread, but ever since I updated to the first LOS 15.1 official build Magisk has been breaking. I've installed both 17.1 and 17.2 and had the problem with both. I'll flash the build in TWRP, I'll set up the hide function and hide Magisk itself, and install the Magiskhide props module to spoof the device cert so I can pass the safetnet checks. However, after a while I'll open Magisk Manager and the app will just hang on the splash screen. After a reboot it will show 2 Magisk icons in the app drawer. Opening one will just hang on the splash screen, the other will prompt for a Magisk Manager install. I've used the uninstall utility through TWRP and reflashed Magisk a few times and it happens each time.

Third- Vibration sounds terrible, like it's broken. It has drawn me some strange looks.

Any help would be appreciated. Thanks to the devs for all their work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
It was actually bad for me as well after flashing. First charge cycle seems to be doing better and I'll be testing it more hoping it stays consistent. I get the feeling my battery is newer than a lot of people's though because I replaced it not too long ago and not many might want to open theirs up
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
After a few days of use I get about 3:30hs with medium brightness and more than 2hs of Bluetooth + Spotify + 4g/3g/E aka ****ty signal in this piece of sh*t country
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ArchangelPT:
Does anyone know how i can make Fate/Grand Order work with Lineage installed?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Masterjuggler:
You have to be creative with magisk hide. You must be on 17.2, hide both the app in the checklist, repackage the manager in settings, and I found I had to use props config module improved hide to hide the LOS base (I'm running Havoc).
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
Was that one of the apps that still wouldn't work even without root installed? I don't think magisk hide is enough there has to be more done like the other guy posted above

Charging is faster than I thought same as other aosp roms around 2500ma max instead of 3k like stock. I uninstalled some apps to see if any are messing with the random shutdown while screen is off because I missed some calls without realizing last time. I'm satisfied with the sot and performance just need to test idle drain
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ArchangelPT:
I found the solution on reddit:

Change in default.prop

>ro.debuggable=1 to ro.debuggable=0

>ro.secure=0 to ro.secure=1

Change in build.prop

ro.build.type=userdebug to ro.build.type=user
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
Thx for sharing. Does this work on other phones/roms as well?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Masterjuggler:
The reason I suggested the props config module is because it allows you to do exactly this, but more easily and systemlessly. Far better to edit systemlessly so its easy to disable if everything goes to hell.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Stremon:
I did exactly that.

It's not working. I can see that pushing the button does something since when I try booting in dfu mode with the button pushed nothing gets detected on my computer until I release it.

But when I release it, the device is seen as dfu no matter what.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
Instructions on the oki guide are a bit different if u want to try it another way
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Stremon:
Believe me I tried every possible way and method to make it boot in EDL, I spent 3 whole days doing almost only that.

Tested with 4 different cables and methods, tried to power the phone in any possible way, I even tried on a different computer and all USB ports (both 2.0 and 3.0, with or without hub), nothing works.

Sadly no matter how much people say EDL HAS to work no matter what, it won't help making it work.

During my research I found out that I'm not the only one that bricked a A2017G model this way and not been able to get it back from the dead even with an EDL cable.

Maybe (and that's just a wild guess at this point) there is something wrong between the A2017G and this bootstack.

---------- Post added at 08:15 PM ---------- Previous post was at 08:15 PM ----------

I used one like that. No result.

---------- Post added at 08:27 PM ---------- Previous post was at 08:15 PM ----------

Tried his method countless times, tried on both USB 2.0 and 3.0, on 2 different PC. It doesn't work...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] kg3:
Can you please link nfound bootstack? I can't seem to find it.

Did you use the 'new' v1 bootstack in the OP?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
https://androidfilehost.com/?fid=674106145207492480
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
17.2 will work on Lineage OS 15 and 16 without any problems. It fixes many problems found on Official 17.0 and 17.1, I personally changed over to 17.2 instead of 17.0 because of the search bug, making you unable to search. I would highly recommend using 17.2

Are you sure you have a vendor partition? That is the only other reason I can think of. Use Oki's PARTY tool and flash it in twrp. Make sure you have the settings

512 MB - AFTER SYSTEM.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] anon1135:
I'll try that actually I've never read about it before lol
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] runninghamster:
Would be quite funny if you were talking about your vendor partition if you didn't have one at all to start with :eek:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] ArchangelPT:
How can i get the weather to work on the cLock widget?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] killacam1989:
Has anyone found a workaround for having the phone power down completely with the battery logo charging?