New Wrong network location.

[Kugumin]

So, somehow network location works wrong on my deivce. I've been testing it on other custom ROMs like "Masik" and others and it was working fine.
At the screenshot below you can see N (Network) and G (GPS) locations markers. Network marker is absoulutely wrong, 4G shows this. After switching to 3G mode it shows another city, which is 200KM+ away from the first city, which is TOO 200KM+ away from me. 2G shows most accurate location marker, but not so close to me as it should be. Please, fix this issue if this possible.



Device: Xiaomi Redmi Note 4X 3/32 (mido)
ROM: 8.7.26

UPDATE: Issue still present in 8.8.3
UPDATE #2: still present in 8.8.9
UPDATE #3: maybe it comes from "NetworkLocation" process?

 

[Kugumin]

UPDATE: Issue still present in 8.8.3

 

[Kugumin]

Please, someone from administration, pay attention to this problem. It is really annoying!

 

[Kugumin]

UPDATE #2: still present in 8.8.9

 

[Orpheus_9]

Same here

Device: Xiaomi Redmi Note 4X 3/32 (mido)
ROM: 8.8.3 & 8.8.9

 

[cobben]

Just curious, what is the practical result of a "wrong network location"?

What problems does it cause?

 

[Orpheus_9]

Just curious, what is the practical result of a "wrong network location"?

What problems does it cause?

I can not find my location at all in weather apps or weather sites in web browsers.

 

[ingbrzy]

Did you change region by yourself?

 

[cobben]

I can not find my location at all in weather apps or weather sites in web browsers.

But if GPS is working, isn't the network location just an additional help, not really needed?

 

[Kugumin]

Did you change region by yourself?

No, never did this

 

[Kugumin]

But if GPS is working, isn't the network location just an additional help, not really needed?

Some apps using only network location. Somehow weather won't work only with GPS, it asks for network location too

 

[ingbrzy]

No, never did this

run getprop command in terminal emulator and paste results here..

 

[Kugumin]

run getprop command in terminal emulator and paste results here..

Here it is.

 

[ingbrzy]

[ro.miui.mcc]: [9460]
[ro.miui.mnc]: [9999]
[ro.miui.region]: [CN]

delete content of your /cust partition in TWRP.. you have set wrong region..

 

[Kugumin]

[ro.miui.mcc]: [9460]
[ro.miui.mnc]: [9999]
[ro.miui.region]: [CN]

delete content of your /cust partition in TWRP.. you have set wrong region..

What I should do after this?

 

[Kugumin]

[ro.miui.mcc]: [9460]
[ro.miui.mnc]: [9999]
[ro.miui.region]: [CN]

delete content of your /cust partition in TWRP.. you have set wrong region..

So I did this and it shows same wrong network location

 

[ingbrzy]

So I did this and it shows same wrong network location

post getprop again.. to confirm correct region settings..

 

[Kugumin]

post getprop again.. to confirm correct region settings..

 

[ingbrzy]

yes, now its correct

[ro.miui.mcc]: [9998]
[ro.miui.mnc]: [9999]
[ro.miui.region]: [PL]

 

[Kugumin]

yes, now its correct

[ro.miui.mcc]: [9998]
[ro.miui.mnc]: [9999]
[ro.miui.region]: [PL]

It shows same wrong location

 

[Kugumin]

So, what's next? It isn't fixed issue.

 

[cobben]

It shows same wrong location
View attachment 20021

I just tried this on my Mi Max1 Prime (helium) in the LTE discovery app, and the difference between the GPS fix and the Network fix was "only" about 200 meters.

It took it over 10 minutes to do the Network fix, of course I have no idea how this works.

Maybe @GreasyMonkey1960 knows?

 

[Kugumin]

@ingbrzy, so, what's happening? Is it gonna be fixed or this issue is already has a way to fix?

 

[Kugumin]

Fine. Looks like this bug never gonna be fixed.

 

[cobben]

Fine. Looks like this bug never gonna be fixed.

I tried out the gps on my 3 Xiaomi phones, and the gps works fine on all 3, with the network position however off from 200 meters up to several kilometers at times, but it would after a time (10-20 minutes?) correct back to only a few hundred meters off from the GPS.

However I could not get the LTE Discovery app to do a GPS fix at all in my Mix1, but in Google maps it worked fine.