microg / microg/UnifiedNlp

Installation of UnifiedNlp GAPPS on FP Open OS loses backend activation after each reboot

Open
#160 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
1.1k
Forks
221
PR merge metrics
No merged PRs in 30d

Description

Here's a [description of my setup](https://forum.fairphone.com/t/a-guide-to-install-open-gapps-while-minimizing-google-dependency/40354/3) that follows on [M.A.K.'s instructions](https://forum.xda-developers.com/android/software-hacking/unifiednlp-gapps-patch-t3567887).
FP Open framework has an org.microg.nlp line item, so patching isn't needed. Google location stops scanning with the deactivation of two services, what allows for UnifiedNlp to bind the backends, but backend boxes need to be cleared and rechecked after every reboot. UnifiedNlp is installed in priv-app and backends as user apps, moving backends to priv-app doesn't change anything.
This setup is the only one that allows for all Google Location dependent apps that I have to run, so I cannot change which services can be reactivated or deactivated without breaking it. It has shown to be pretty solid except for the clearing and rechecking of backend boxes after each reboot.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked Fairphone and XDA setup instructions, then reproduce the UnifiedNlp configuration by rebooting the FP Open OS device. Done means the selected backend boxes remain enabled and UnifiedNlp continues binding its backends after reboot without changing the required Google service state.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.