yashsingh1/xdaforums huggingface dataset:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
No sir, that's a whole unofficial build that fixed NFC. I'll remove my leftovers when I get home some people want to revert back so I try to keep builds that we're good online.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] clementinox:
ok I see. the fix is not included in the vendor zip? when i flashed unofficial yesturday then I wiped all except vendor, I flashed treble rom but nfc wasn't working.

I just tried flashing the vendor file you uploaded but it says "cannot flash image"
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
A Pie GSI right?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] clementinox:
yes
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Link me to one and some instructions. I may be able to fix it without breaking lineage, but let's try to create a new thread in discussion area.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Who actually uses hand wave with ambient display? It's not broken in latest build I purposely disabled it due to battery drain.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] clementinox:
Will do thank you very much!

I used it for a bit but only for a day then forgot about it. For me I don't really use it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] blackpac:
Signature Spoofing....?? :fingers-crossed:
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
That keydisabler might fix the problems I have with missing nav bar that appears one times every 2 unlocks. Prevents the fingerprint unlock to work properly...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
If you have a model that has no physical buttons then this probably will help.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
Yes it s a warranty return and I lost the hardware buttons in that new phone

(Sucks).... im on official so probably will have to move to non official.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Honestly 15.1 is abandoned all work is going into 16.0 so until official is stable there's no benefit
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
I meant going on 15.1 unofficial and the benefit is to unlock my screen as it s supposed to.. I did not try 16.0 yet. Is that ported to 16.0? I may as well jump to 16 directly.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I'm not sure the exact issue with fingerprint could you go more in depth. You're saying it's related to the navigation bars?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] FuzzyDunlop9:
I'm gonna move from the official to your unofficial build, found the instructions on how to do this several pages back.

Just checked on your download page a vendor image. Do I need to Flash this as well to move to the latest unofficial or just flash rom zip
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
So this is what happens: I flashed straight from nougat stock unrooted as soon as I received the new phone from warranty. I used oki's kit + magisk and gapps. It s a clean flash.

First time I booted the phone, I did not have the navigation bars as the phone I now have does not have hardware keys. So I installed the xiaomi a1 navigation bar module using magisk and got the nav bars after reboot.

The problem: if I lock the phone using power button, screen goes off (normal). If i press it again, the navigation bars are missing. I can interact with the notification bar (toggle flashlight etc) but can't open any app from the launcher. If I press twice the power button (turn off screen and on again) nav bar is here and everything work ok.

If screen is off for a long time, fingerprint does not work anymore. I have to turn on screen using power button, turn off because I have no nav bar and then go works.

By nav bar, to be clear I mean the 3 buttons at the bottom, back home and recent.

I updated the fingerprint props and phone passes safety checks. My guess is that something is conflicting between vendor and system keylayouts.

Also, info to take with a grain of salt, when I wipe cache and dalvik, phone behaves as expected few first hours (it seems, hard to confirm).

Thanks!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] misterz100:
[MENTION=4911249]Unjustified Dev[/MENTION] I just recently bough myself a new phone, I am giving my Axon 7 to my mom, what is the best ROM I can use for battery life? unofficial? official? should I just put it to stock Oreo? Any recommendations?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] clementinox:
You don't need to flash vendor, it's related to something else.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] les_paulde:
I was using it a fair bit as I find it an elegant way of checking for new msgs or the time etc. Thanks for clarifying that it's disabled now as that explains a lot... ;) Is there no way to have it always-on like on Samsung phones, or will it simply drain too much battery?

And a BIG thanks to you, your hard work is well appreciated and makes this phone super exciting again!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jrotaetxe:
I was. Thank you for the heads up. Wonder in it was the reason of my warming "problem".

Checking new version. TK, sir.

Regards
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] [armitage]:
Post removed...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mart Son:
for me it fixes the location in maybe 3 seconds...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] [armitage]:
M̶a̶y̶b̶e̶ ̶i̶t̶ ̶d̶e̶p̶e̶n̶d̶s̶ ̶o̶n̶ ̶w̶h̶e̶r̶e̶ ̶y̶o̶u̶ ̶l̶i̶v̶e̶ ̶(̶E̶u̶r̶o̶p̶e̶,̶ ̶U̶S̶ ̶e̶t̶c̶.̶)̶ ̶,̶ ̶a̶s̶ ̶a̶n̶o̶t̶h̶e̶r̶ ̶g̶u̶y̶ ̶c̶o̶n̶f̶i̶r̶m̶e̶d̶ ̶t̶h̶e̶ ̶p̶r̶o̶b̶l̶e̶m̶s̶ ̶w̶i̶t̶h̶ ̶t̶h̶e̶ ̶l̶a̶s̶t̶ ̶v̶e̶r̶s̶i̶o̶n̶ ̶a̶s̶ ̶w̶e̶l̶l̶.̶ ̶M̶a̶y̶b̶e̶ ̶e̶v̶e̶n̶ ̶t̶h̶e̶ ̶b̶o̶o̶t̶ ̶s̶t̶a̶c̶k̶ ̶a̶s̶ ̶s̶o̶m̶e̶ ̶i̶n̶f̶l̶u̶e̶n̶c̶e̶ ̶o̶n̶ ̶i̶t̶.̶.̶.̶ ̶I̶ ̶d̶o̶n̶'̶t̶ ̶k̶n̶o̶w̶.̶ ̶A̶n̶y̶w̶a̶y̶,̶ ̶I̶'̶m̶ ̶o̶n̶ ̶t̶h̶e̶ ̶l̶a̶t̶e̶s̶t̶ ̶u̶n̶o̶f̶f̶i̶c̶i̶a̶l̶ ̶(̶o̶b̶v̶i̶o̶u̶s̶l̶y̶)̶ ̶w̶i̶t̶h̶ ̶D̶r̶a̶k̶e̶n̶F̶X̶'̶s̶ ̶B̶2̶0̶ ̶B̶o̶o̶t̶s̶t̶a̶c̶k̶ ̶a̶n̶d̶ ̶i̶n̶ ̶g̶e̶r̶m̶a̶n̶y̶,̶ ̶i̶f̶ ̶t̶h̶e̶s̶e̶ ̶i̶n̶f̶o̶s̶ ̶h̶e̶l̶p̶ ̶a̶t̶ ̶a̶l̶l̶.̶
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Mart Son:
I have exactly the same setup, same location....

weired
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] [armitage]:
Your post might have just fixed it. LOL

As I have no other explanation for this.

I just tried again, and I promise you I tried all morning and a lot with the last version and nothing worked.

I just opened maps again after reading your post, just to double check and it moved from the 2 kilometers away position to where I actually am.

Weird indeed.

I'll edit my other posts so that udev doesn't get pinged and goes on a wild goose chase.

EDIT: Aaand it went back to being about two kilometers off. I really don't get it.
[MENTION=4911249]Unjustified Dev[/MENTION] sorry to @ you, but if you could maybe take another look at this, as it was working fine a couple of versions ago. Or maybe someone could give me a hint what I could try, or what info I could provide to solve this, as I really need this for navigation a lot.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jrotaetxe:
Still "warming" with the new version.

Regards
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BJHiltbrand:
50% battery bug still here on 11/10 unofficial. I don't know if this was supposed to address that or not. Just thought I'd report back.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] reasonablebasis:
Could I use unofficial 15.1 as a daily driver or are there too many issues? I'm currently using AEX 5.8 and still undecided whether to switch to Lineage or to wait for Lineage 16 to be stable.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] blackpac:
Is it somthing to do with the bootloader warning screen?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] OrdenKrieger:
No, that will never go away. Unless you mean the corruption screen, there is a comment on that right after the op.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
The guy above has a china stack that works very good and offline charging works with the dev bootloader I got from ZTE. That's what I use and will probably will recommend that one. Just to let people know the Oreo bootloader with fastboot came from an internal build I received when the first Oreo beta dropped and it's using an older TZ version this could be the reason why offline charging doesn't work in combination with the newer stack
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I just threw my phone at the computer. I have no freaking idea and your device is one of the Original Axon 7 devices when it first came out? I really think there's some different revisions. There's actually some better logging to the kernel message. If it happens again just run dmesg from a terminal emulator and send it to me. dmesg > /sdcard/dmesg.txt
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BJHiltbrand:
Sorry man, I don't mean to cause undue stress. I actually don't know how old the current phone that I have is. I had one of the original ones, but that one kept corrupting SD cards on me, and this is my second warranty replacement. Anyway, this is an ongoing issue with me. ever since flashing from stock, using the OP as guidance (not the Oki MiFlash package), it has only reported 50% battery life. I have noticed, however, that the battery life in TWRP occasionally says "50%+", usually while I'm flashing something, then it goes back to just saying "50%".

Anyway, here is my latest log. Thank you so much for all that you do!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Looks like healthd is only reporting 50% but the driver seems to report just fine. If you're still stuck at 50 try reading capacity

"cat /sys/class/power_supply/battery/capacity"
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BJHiltbrand:
It reports 50
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I'll have to look more when I'm at home, but that's the best log so far.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BJHiltbrand:
Sounds good. Again, thank you so much!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] tprfd:
You're doing a fantastic job. Please don't get discouraged. This work you're doing will save many phones from the garbage tip and if you throw too hard, more than one phone will follow yours there.

TWRP reports 50% battery for me. Lineage latest official is reproting battery stats fine. Using Oki installation, 2017g version.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Penoro123:
I'm still on 20181001 Official and don't have any issues with the battery reading stuck at 50%.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] GiZZy:
I also have the 50% battery bug with LOS (on A2017U)

I decided to try flashing Schwifty Kernel R4 and it actually made the battery work again (although now I am getting a vendor mismatch message, but everything seems to work correctly)

Edit: This was happening to my first Axon 7 which i got when they were first available in NA, and my current phone is a replacement I received using advance exchange about 6 months ago.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
Viper4android 'harmful' message?

I'm on the latest official LOS 15.1 with Dolby installed as recommend in this thread - including v4a installed via magisk 17.2.. Today I got a 'harmful app' message from Google play suggesting I disable the app. I ignored that and went to the magisk app, which showed an update available - so I installed that.

Just trying to determine whether this is normal. Is there a cat and mouse game that goes on between Google and various magisk modules?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] BJHiltbrand:
I get that on my Head Unit that is running V4A. I think Google warns you because Viper 4 Android allows for modifications that can potentially push speakers too hard and damage them. I've always ignored the message.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bedroidapp:
Same warning here. But no update available in magisk...
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
[MENTION=5082772]Unjustified[/MENTION]_Dev is it possible to add external USB/microsd storage support for other file systems like exFAT or NTFS to the kernel or vendor?

I think this is what would enable it to work: https://github.com/LineageOS/android_system_vold?files=1

But I'm not sure if it's a rom feature, kernel or vendor.

Right now I can't use my USB or microSD both in twrp unless I use the FAT file system and that has the 3gb file limit.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] -Duir-:
I can't speak for USB-OTG as I don't use it, but my sdcard is ExFAT and it works just fine.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
That probably means support is added at a rom level and explains why it doesn't work with certain GSIs. I was wondering if it was possible to add support to kernel or vendor level instead so it can be used across the board with our device and not only with los15.

---

Never mind I figured out the issue is due to a bug with the pie GSIs which prevents ext storage when selinux is set to enforcing. Sorry to waste any time.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
So when I say ther are battery's problems,ppl ignore me...and this guy with his 50% battery bug (from 2year ago) is taken seriously.

People are just funny,but very sad at the same time.They keep lying to others and themself.

I'm not taking this xda community seriously anymore,its sad...very sad
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Your battery problems are your own. Stop wasting time and acknowledge it's a battery problem and go buy a new one.

And don't worry, no one is taking you seriously.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
Why dont't you just flash Los 14.1 or a stock firmware in order to check wherether it's a battery problem or a firmware one?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] h3ndrik:
Hey, i'm currently on unofficial-1110, A2017G and this rom proves to be an excellent daily driver. But I got 2 questions:

Does VoLTE work for anyone? My phone always switches to GSM for calls although my provider (Aldi Talk / Germany) should support this and i've added 'ims' to the apn settings. Just want to know if it's possible with recent firmware changes. (Or if i should stop worrying;)

Just installed the Daydream App but it's only 2d (single-full-screen) and without gui. Does it work for you? Could be because I opted out on installing gapps? Or do i have to take additional steps to make this work?

Thank you!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] SaintZ93:
?? We have told you thousands of times your junk is junk, replace it.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Works for me, but while I don't have the GApps, I do have at least microG... I'm not sure it will work without *anything*. You will also have to install the Google VR Services app. If you don't have the GApps, you may also need (or want, anyway) to edit /data/data/com.google.vr.vrcore/shared_prefs/VrCoreSettings.xml and set "DaydreamSetupComplete" to "True".

One thing that doesn't work is low persistence mode, so Daydream apps will be rather blurry.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
Hey guys I'm running the latest official 11/12 build and I have noticed that the only way I can get location information is when I have GPS signal.

Location via WiFi networks and cellular information doesn't appear to be working. This was working on the previous build I had. Anyone else having this issue? If not what logs would help diagnose the problem? Thanks guys
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] littlenoodles:
Sudden Battery Drain symptom

False alarm. Never mind. Silly me - somehow I had the 'lock' icon selected. I.e. the app had been manually locked into memory. I must've hit that accidentally. By the way, can I delete a message here instead of embarrassing myself ;)

I've been experiencing sudden spikes in battery consumption in the last few Official 15.1 releases - don't think it was happening in the 1015 release, which was the last one I sideloaded via adb, rather than having the LOS upgrader download it.

Anyway, most of the time my phone stays pretty cool, and battery usage is okay. But occasionally the phone heats up, and the battery percentage starts dropping precipitously. And if I catch it and go to the multitasking screen and hit Clear All, it stops and the phone cools down.

It just happened, and I noticed something odd. BetterBatteryStats showed Zynga Words with Friends using a lot of battery, so I went to the multitasking screen and tried to stop just that app. It wouldn't stop - hitting the 'X' did nothing, and when I tried to swipe the app away, it bounced back. But Clear All got rid of it - and then the phone returned to normal. Is this a significant clue to anybody out there? Is there a way for an app to lock itself into memory and refuse to go dormant - is that one kind of a 'wakelock', and if so, what in the OS could cause an app to get stuck like that (I'm assuming Words with Friends isn't seriously buggy in that way)?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Hille2001:
Today i got a New Build Message Form 13.11

Is it necessary for last unofficially Version to flash the Bat ZIP and IMG vor are they included in last build?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
For me the 11/12 is a total mess. I went back to 10/29.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
Update... It appears that under location settings in stuck on "device only". When I try to chose a different setting like high accuracy, it doesn't stay set. Thoughts anyone?
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] [armitage]:
Well, it stays on high accuracy for me, but, as mentioned before, my location (at least most of the time) is way off and I haven't found any way to fix this so far and I tried a lot (from apps to changing the gps.cfg, calibrating, every possible mode and in many different locations).

I'm pretty much out of ideas, but as hardly anyone seems to have the problem with the latest versions, it doesn't get addressed.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] jrotaetxe:
... and that fits very well with my "warming" observations. I second also the assertion " But occasionally the phone heats up..." But I am of UnjustifiedDevs Unnoficial... A common mode?

Would like to have more knowledge to be able to help more, but without a "guide to debug for an idiot user" I would not be able...

Regards
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Zobat:
I can confirm this
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
Strange... Things were working fine until I updated my rom to the latest official... The official lineage was working fine from about a month ago. Unfortunately I don't have a backup to revert to as I was being lazy...??*♂️
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] lichtblitz:
Why backup? just wipe dalvik, cache, vendor and system then install an older version. The last 5 are still online. For me the 10/29 works perfekt beside the power drain from display and not working android beam.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
Thanks for the tip!!! Tried that last night and a couple previous builds and still couldn't aquire or select an location other than gps (no cell or wifi location and no Google location history)

To resolve had to factory reset ie. Delete data partion as well and flashed the latest unofficial 15.1 and now I can get location from all sources. Thanks again everyone for trying to assist!
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Dodgexander:
My feedback/bugs using the vendor from this ROM with schwifty kernel and havoc pie correspond with some posts reporting issues using also the los ROM.

1. GPS barely works. Battery saving mode (Bluetooth and WiFi scan location) doesn't work, GPS itself on high accuracy doesn't work either. Could it be the fact that the option "device only" being removed has broken this? It seems to be related more to reporting the found location (by any means) to apps rather than GPS not working at all.

2. Bugs with the kernel and small cluster. This happens with both stock kernel and schwifty based on the same sources, the small cluster locks to full frequency when the screen is touched. Also it does not respond to tuning. For example you cannot set a different max small cluster frequency without it bouncing back to a default value.

But apart from this I've seen great improvements in battery and performance with the most recent release which is great to see. Thanks for your great work.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
I find it odd almost no one have calibration issues with los15 bootstack and los15/16 rom.

The cpu cluster bug i have it too,its fine to live with....but these calibration issues making me frustrated.

I clean flashed again (also reinstall vendor part).When their is no OS installed,the charging is all fine in TWRP....but as soon i installed the os and boot it up,the calibration is messed up again.

My phone was sitting on 1%,installed accubattery and set it up.Ive put it on the charger and not it looks it charge normal.First % it charges with 200% a hour,after that it charge with 70-90% a hour,but when it reach 1 higher % (from 8 to 9) the charging % a hour goes up.How higher i charge,how lower this become.

When it passes 30%,the charging % a hour stays like 87%...according to accubattery
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] bornlivedie:
Fast charging charges faster the first few %. Don't know the exact numbers but it's something like 0-30%
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Predatorhaze:
I believe this is wrong.After it reach 30 it wil go reach its designed charging speed (fastest),and again this will lower when its reaching 85-90%.

It should never charge with 100% a hour.

I'm on los16 now,I let the battery completely drain.Put it on charger,phone booted...and it was charging normal from 1% with the speed off 60% a hour.When it reached 30% battery...the charging went to 70-80% a hour.These are the speeds I know on a good calibrated battery (stock)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Now that Official is released on a daily basis, wouldn't it be nice to have some of the important changes there are in Unofficial ported there? With the faster rollout, testing should become easier and any showstopper problem can be corrected in just one day.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Gachmuret:
+1
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] piet8stevens:
Let's not get carried away : the dev decides how fast things are fixed, not the release schedule. :)
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] LuccoJ:
Yes, that was totally me getting "carried away", as I reread it, it definitely sounds like I was telling the dev what to do, sorry.

In my defense, there is the fact that in a number of discussions I've read about the reasons behind making the 15.1 builds daily, there is the hope it will help devs with testing due to the faster turnover.
[ZTE Axon 7 ROMs, Kernels, Recoveries, & Other Deve] Young Gunna:
I concur that there is something going on with Location services. I'm running the latest unofficial 15.1 with v1 boot loader from original post on US version of axon 7.

GPS seems too lock fine, and cellular location works ok, but location using WiFi takes several minutes if it ever can find my location at that level. What logs could I provide to help troubleshoot this? A few official versions ago location was operating ok.