Location services turn off by themselves?

I am using Android 14 Xiaomi theoretical. Even though I have turned on the settings related to location services and high accuracy in the Android application, they are disabled when I exit the application and enter again?


Did you give the app permissions for location?

I gave Android permissions to the application. I turn on the location from the utility settings. When I exit and log in, I find it disabled again.

Did you give it permissions when the app is open. It sounds like it.

Yes look at attached video please

do you turn off location or GPS at all?

No always opened

they only become disabled if the app loses permission

I am not changing the app permissions. When I checked, all of them were granted. There is a video above, if you can review it?

try the start fresh steps, looks like teh data may be corrupted

I deleted the entire application and reinstalled it to no avail. However, when I reinstall Android 12 on the other phone, everything works perfectly. I’m sure it’s a problem with Xiaomi or Android 14. If I find it, I will try it on another Android 14 phone.

check the app logs

settings > companion app > troubleshooting > show and share logs

--------- beginning of system
02-05 17:35:26.311 4899 4921 I ActivityThread: SetSystemFontMap done
02-05 17:35:26.413 4899 4921 I ActivityThread: Setup proxies done
02-05 17:35:26.420 4899 4921 I ActivityThread: SetupGraphicsSupport done
02-05 17:35:26.421 4899 4921 I ActivityThread: TrafficStats init done
02-05 17:35:26.426 4899 4921 I ActivityThread: Miui Feature Init done
02-05 17:36:40.762 4899 4986 W BpBinder: Slow Binder: BpBinder transact took 247 ms, interface=android.net.wifi.IWifiManager, code=41 oneway=false
02-05 19:27:49.119 4899 4988 W BpBinder: Slow Binder: BpBinder transact took 898 ms, interface=android.net.wifi.IWifiManager, code=41 oneway=false
--------- beginning of main
02-05 20:45:28.916 4899 4899 D LocBroadcastReceiver: Received location update.
02-05 20:45:28.925 4899 4899 D ForegrndServiceLauncher: Check if service HighAccuracyLocationService is running. Service running = false
02-05 20:45:28.925 4899 4989 D LocBroadcastReceiver: Last Location:
02-05 20:45:28.925 4899 4989 D LocBroadcastReceiver: Coords:(40.0231923, 27.0555335)
02-05 20:45:28.925 4899 4989 D LocBroadcastReceiver: Accuracy: 100.0
02-05 20:45:28.925 4899 4989 D LocBroadcastReceiver: Bearing: 0.0
02-05 20:45:28.925 4899 4989 D LocBroadcastReceiver: Begin evaluating if location update should be skipped
02-05 20:45:28.925 4899 4989 D LocBroadcastReceiver: Received location that is 26 milliseconds old, 1738777528899 compared to 1738777528925 with source fused
02-05 20:45:28.925 4899 4989 D LocBroadcastReceiver: Duplicate location received, not sending to HA
02-05 20:47:00.545 4899 4899 D LocBroadcastReceiver: Received location update.
02-05 20:47:00.551 4899 4899 D ForegrndServiceLauncher: Check if service HighAccuracyLocationService is running. Service running = false
02-05 20:47:00.552 4899 4989 D LocBroadcastReceiver: Last Location:
02-05 20:47:00.552 4899 4989 D LocBroadcastReceiver: Coords:(40.0231923, 27.0555335)
02-05 20:47:00.552 4899 4989 D LocBroadcastReceiver: Accuracy: 100.0
02-05 20:47:00.552 4899 4989 D LocBroadcastReceiver: Bearing: 0.0
02-05 20:47:00.552 4899 4989 D LocBroadcastReceiver: Begin evaluating if location update should be skipped
02-05 20:47:00.552 4899 4989 D LocBroadcastReceiver: Received location that is 21 milliseconds old, 1738777620531 compared to 1738777620552 with source fused
02-05 20:47:00.552 4899 4989 D LocBroadcastReceiver: Duplicate location received, not sending to HA
02-05 20:48:32.075 4899 4951 D WM-Processor: Processor cancelling 28ece1f8-1d1a-4ea1-9403-e4b70ae69667
02-05 20:48:32.075 4899 4951 D WM-Processor: WorkerWrapper could not be found for 28ece1f8-1d1a-4ea1-9403-e4b70ae69667
02-05 20:48:32.076 4899 4899 D SensorReceiver: Received intent: android.intent.action.SCREEN_OFF
02-05 20:48:32.082 4899 4899 D SensorReceiver: Sensor(s) [is_interactive] corresponding to received event android.intent.action.SCREEN_OFF are disabled, skipping

was this taken when the issue happened? looks like location is working if that is the case

It’s 20:45, but yes, it seems that the service is not working there and HA cannot be reached.
02-05 20:45:28.916 4899 4899 D LocBroadcastReceiver: Received location update.
02-05 20:45:28.925 4899 4899 D ForegrndServiceLauncher: Check if service HighAccuracyLocationService is running. Service running = false

02-05 20:45:28.925 4899 4989 D LocBroadcastReceiver: Begin evaluating if location update should be skipped
02-05 20:45:28.925 4899 4989 D LocBroadcastReceiver: Received location that is 26 milliseconds old, 1738777528899 compared to 1738777528925 with source fused
02-05 20:45:28.925 4899 4989 D LocBroadcastReceiver: Duplicate location received, not sending to HA

what makes you say that? you can see google sending the app a location update

and we apply our logic followed by

so working as intended we indeed do not send duplicate location requests

please check location history as well on the previous page you should see some skipped message and some success