microg / microg/GmsCore

"MicroG Services keep stopping" error

Open
#2,386 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

Describe the bug
"MicroG Services keep stopping" error keeps popping even with location permission granted.

To Reproduce
Steps to reproduce the behavior:

  1. Install LineageOS 21
  2. Install Magisk 27.0
  3. Install LSPosed 1.9.3 module
  4. In LSPosed install FakeGapps
  5. Install MicroG Installer revived 3.4.4 module
  6. Reboot

Expected behavior
MicroG working normally on my device

System
Android Version: 14
Custom ROM: LineageOS 21
MicroG Services version: 0.3.2.240913

Additional context
I saw another bug report from march very similar to mine and in that case it was fixed by giving app the location permission, but in my case it didn't help

Logs:
FATAL EXCEPTION: main Process: com.google.android.gms:ui, PID: 6100 java.lang.NullPointerException: Attempt to invoke virtual method 'android.content.res.Configuration android.content.res.Resources.getConfiguration()' on a null object reference at android.app.ConfigurationController.updateLocaleListFromAppContext(ConfigurationController.java:266) at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7187) at android.app.ActivityThread.-$$Nest$mhandleBindApplication(Unknown Source:0) at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2337) at android.os.Handler.dispatchMessage(Handler.java:107) at android.os.Looper.loopOnce(Looper.java:232) at android.os.Looper.loop(Looper.java:317) at android.app.ActivityThread.main(ActivityThread.java:8501) at java.lang.reflect.Method.invoke(Native Method) at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:552) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:878)

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 reported reproduction steps and the FATAL EXCEPTION stack trace, especially ConfigurationController.java and ActivityThread.java on Android 14. Compare the crash with the listed MicroG, LineageOS, Magisk, LSPosed, and FakeGapps versions; done means identifying a reproducible project-side cause and validating a fix or confirming the compatibility boundary.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.