microg / microg/GmsCore

Additional UI indicators to help users figure out why push notifications don't work

Open
#641 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

☁️ Cloud / Push Messaging
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

First of all, thanks a lot for MicroG and especially the MicroG-infused LineageOS ROM. I had been dying to switch back to LineageOS and MicroG ever since I had bought a new phone this spring and now that LOS officially added support for my device, I could finally try it out!

Unfortunately, though, I spent hours trying to figure out why push notifications couldn't get through. I was already afraid that things simply weren't working – which wouldn't have surprised me, given that GCM is somewhat unreliable on stock Android, too, and that I still remember times when MicroG's GCM support would sometimes just break out of nowhere because Google had suddenly made some changes.

Luckily, however, this time I realized at some point that the "auto-block everything" setting in my firewall app had flipped somehow and thereby prevented MicroG from connecting anywhere. My own stupidity aside, though, I would really appreciate some additional indicators in the UI that will help me next time I'm debugging an issue with push notifications, such as:

  • an indicator in the "Self-Check" UI that indicates whether a connection to the Google servers has been established (or whether the Google servers could at least be contacted within the timeframe of the last X minutes).
  • an explanation in the "Google device registration" view that tells me not only what enabling "device registration" does but also why I would need it in the first place.
  • a popup message when enabling Google Cloud Messaging, that tells me that "Google device registration" has to be enabled as well (or which simply enables it for me). I had forgotten about enabling this at first and later found the crucial hint in the post-install instructions.
  • a button to test push notifications (i.e. one to send a push notification to see whether it comes back) – always useful
  • logs/debug output to see where connection attempts / push notifications get stuck

Again, thank you for all the hard work you've clearly put into MicroG! It works like a charm now! :)

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

No files, tests, or entry points are named. Start by locating the Self-Check UI, Google device registration view, and Google Cloud Messaging settings, then determine the existing diagnostics and notification flow; done would require an agreed, testable scope for the requested indicators and debugging output.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.