microg / microg/GmsCore

Reconnect service when it gets disconnected

Open
#1,732 1 comment 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
Randomly the service status changes to Disconnected and we have to manually reconnect it. In the meantime notifications fail.

To Reproduce
I couldn't find a way to reproduce the problem, I don't know why the service gets disconnected

Expected behavior
Reconnect automatically so that notifications will work again

System
Huawei P40Pro with latest updates

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 by locating the service status and disconnection handling, then trace how notifications depend on that service. The issue names no files or tests, and the failure is not reproducible; done means the service reconnects automatically after a disconnection and notifications resume.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile-dev
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.