Cloud messaging disconnecting even with setting correct.
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 14.6k
- Forks
- 3.2k
- Avg merge
- 12d 11h
- Merged PRs (30d)
- 4
Description
So I am using Huawei HarmonyOS right now and MicroG services Core doesn't appear at in the battery settings as an app.
The checkbox in the Microg settings is ticked bit as soon as the system closes the app automatically or you do it yourself, the service is disconnected.
As microg is a necessary part of a western user to be able to use HMS android (without Google Mobile Services), having MicroG stay running and connected is a necessity.
The app launch setting allows you to set apps to prevent the system from managing the app from launching.
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 report names no source file, entry point, or test. Start by reproducing the disconnect on Huawei HarmonyOS with the MicroG battery and app-launch settings enabled, then trace the cloud-messaging service behavior; done means the service remains connected after the system or user closes the app.
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