Cloud messaging (notification) is disconnected when gmscore is killed
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
Describe the bug
We are using microg to get notification on huawei phones. After setup, the microg will be killed by a app named powergenie if the screen is locked for a period of time. Then microg doesn't reconnect the cloud messaging untill we enter cloud messaging and manually switch the on/off once.
To Reproduce
Steps to reproduce the behavior:
- Kill microg at the background.
- The cloud messaging will show disconnected.
- Pressing on/off once will bring up the cloud messing
Expected behavior
Microg restarts the cloud messaging when it's restarted.
Screenshots
If applicable, add screenshots to help explain your problem.
System
Android Version: [e.g. harmony OS2]
Additional context
If it's really hard to solve, can the switch of on/off be done once by command lines or restarting the services. Please advice us a workaround.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests; start by reproducing the cloud messaging disconnect after GmsCore is killed in the background. Trace the cloud messaging service restart and reconnection path on Android, including the reported Huawei power-management scenario. Done means cloud messaging reconnects after GmsCore restarts without manually toggling the setting.
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
- Mostly clear
- Newbie friendliness
- 28/100