Secondary User -> forces Factory Reset

Same problem with ‘latest greatest’ version available.
And same recurrent error in the logs:

10-25 21:21:02.838 18923 18969 E AndroidRuntime: FATAL EXCEPTION: android.fg
10-25 21:21:02.838 18923 18969 E AndroidRuntime: Process: com.qualcomm.location, PID: 18923
10-25 21:21:02.838 18923 18969 E AndroidRuntime: java.lang.SecurityException: Not allowed to bind to service Intent { act=com.android.location.service.v3.NetworkLocationProvider pkg=com.google.android.gms cmp=com.google.android.gms/com.google.android.location.network.NetworkLocationService }
10-25 21:21:02.838 18923 18969 E AndroidRuntime: 	at android.app.ContextImpl.bindServiceCommon(ContextImpl.java:1838)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: 	at android.app.ContextImpl.bindServiceAsUser(ContextImpl.java:1783)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: 	at android.content.ContextWrapper.bindServiceAsUser(ContextWrapper.java:782)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: 	at com.android.server.ServiceWatcher.rebind(ServiceWatcher.java:339)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: 	at com.android.server.ServiceWatcher.onBestServiceChanged(ServiceWatcher.java:310)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: 	at com.android.server.ServiceWatcher.lambda$register$0$ServiceWatcher(ServiceWatcher.java:282)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: 	at com.android.server.-$$Lambda$ServiceWatcher$K66HPJls7ga1t3t859fKACfAgZc.run(Unknown Source:2)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:938)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:99)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:223)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: 	at android.os.HandlerThread.run(HandlerThread.java:67)
10-25 21:21:02.838 18923 18969 E AndroidRuntime: 	at com.android.server.ServiceThread.run(ServiceThread.java:44)

From what I can read online, such an unauthorized access could trigger a soft reboot as this one!

My best guess is some permissions are missing for the non-admin users, possibly related to location services…

1 Like