microg / microg/GmsCore

Show package name and/or version code on all app pages

Open
#2,288 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hi.

Sorry for bad english.

Since revanced devs are not going to rename their microG fork https://github.com/ReVanced/revanced-discussions/discussions/1035#discussioncomment-8970687

It would be nice to have a neat solution on how to quickly determine from the screenshot provided by the user which microG variant is used, not to waste time asking leading questions.

My suggestion is to show somewhere in the corner or else packageName and/or versoinCode of the app.

Screenshot_20240401-090650_microG Services

It might also make sense to add the number of successful checks on the main page.

Screenshot_20240401-123109_Gallery

These are not perfect solutions, but both can make the process of helping users easier.

Perhaps someone has more elegant suggestions.

thank you for your attention

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 or tests are named. Start by locating the entry points and layouts for the app pages shown in the screenshots, then find how the package name and version code are exposed; done means the selected metadata is visible consistently on all app pages, with the successful-check count treated as a separate scope decision.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java, kotlin
Domain
mobile
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.