Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unified Nlp Backends are not started after the boot while network location is enabled #960

Closed
Iey4iej3 opened this issue Oct 22, 2019 · 0 comments

Comments

@Iey4iej3
Copy link

Iey4iej3 commented Oct 22, 2019

I refer to this post for a background, especially a filtered logcat.

microG version: 0.2.8.17785-4 (06c8b76)

From the logcat message:

10-21 10:26:43.717 1258 1327 I ActivityManager: Start proc 4762:org.microg.nlp.backend.ichnaea/u0a81 for service org.microg.nlp.backend.ichnaea/.BackendService
10-21 10:26:43.795 4762 4762 D IchnaeaBackendService: No instance found active.
10-21 10:26:44.335 2915 4786 D NlpLocBackendHelper: Binding to: Intent { act=org.microg.nlp.LOCATION_BACKEND pkg=org.microg.nlp.backend.ichnaea cmp=org.microg.nlp.backend.ichnaea/.BackendService }
10-21 10:26:44.342 2915 4787 D NlpLocBackendHelper: Not (yet) bound.
10-21 10:26:44.344 4762 4762 D IchnaeaBackendService: No instance found active.

Seemingly Nlp backends are started only after manual disabling and re-enabling in the settings of Nlp backends in microG.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant